Sensor Network - Revision history

Summakor: Moved to Previous Projects

2016-12-16T03:21:01Z

Moved to Previous Projects

← Older revision		Revision as of 03:21, 16 December 2016
Line 32:		Line 32:

	Discuss your ideas!		Discuss your ideas!

			[[Category:Previous_Projects]]

Tslagle at 15:26, 4 April 2012

2012-04-04T15:26:21Z

← Older revision		Revision as of 15:26, 4 April 2012
Line 1:		Line 1:
	~~{{RevisionNeeded}}~~		[[Category:Proposed_Projects]]

	The goal of this project is: ____________________		The goal of this project is: ____________________

ITechGeek at 21:21, 3 April 2012

2012-04-03T21:21:59Z

← Older revision		Revision as of 21:21, 3 April 2012
Line 1:		Line 1:
			{{RevisionNeeded}}

	The goal of this project is: ____________________		The goal of this project is: ____________________

66.92.168.58: /* Wire Language */

2010-09-28T00:56:52Z

Wire Language

← Older revision		Revision as of 00:56, 28 September 2010
Line 8:		Line 8:
	The wire language will be device-specific. Devices can speak any language they want as long as someone has written a "driver" to translate that language to/from the chosen format that will transmitted/received over XMPP.		The wire language will be device-specific. Devices can speak any language they want as long as someone has written a "driver" to translate that language to/from the chosen format that will transmitted/received over XMPP.

	[JeeMesh] protocol is being worked on to extend the [http://cafe.jeelabs.net/sw/library_-_rf12/ RF12] frame network to support datagrams up to 1022 bytes over a mesh of [http://cafe.jeelabs.net/lab/jn5/ JeeNodes]. The goal is to support up to 4 hop meshes of up to 26 nodes plus 4 servers/gateways each.		[[JeeMesh]] protocol is being worked on to extend the [http://cafe.jeelabs.net/sw/library_-_rf12/ RF12] frame network to support datagrams up to 1022 bytes over a mesh of [http://cafe.jeelabs.net/lab/jn5/ JeeNodes]. The goal is to support up to 4 hop meshes of up to 26 nodes plus 4 servers/gateways each.

	=== Message Format ===		=== Message Format ===

66.92.168.58: /* Wire Language */

2010-09-28T00:56:07Z

Wire Language

← Older revision		Revision as of 00:56, 28 September 2010
Line 8:		Line 8:
	The wire language will be device-specific. Devices can speak any language they want as long as someone has written a "driver" to translate that language to/from the chosen format that will transmitted/received over XMPP.		The wire language will be device-specific. Devices can speak any language they want as long as someone has written a "driver" to translate that language to/from the chosen format that will transmitted/received over XMPP.

	JeeMesh protocol is being worked on to extend the [http://cafe.jeelabs.net/sw/library_-_rf12/ RF12] frame network to support datagrams up to 1022 bytes over a mesh of [http://cafe.jeelabs.net/lab/jn5/ JeeNodes]. The goal is to support up to 4 hop meshes of up to 26 nodes plus 4 servers/gateways each.		[JeeMesh] protocol is being worked on to extend the [http://cafe.jeelabs.net/sw/library_-_rf12/ RF12] frame network to support datagrams up to 1022 bytes over a mesh of [http://cafe.jeelabs.net/lab/jn5/ JeeNodes]. The goal is to support up to 4 hop meshes of up to 26 nodes plus 4 servers/gateways each.

	=== Message Format ===		=== Message Format ===

66.92.168.58: /* Wire Language */

2010-09-28T00:55:41Z

Wire Language

← Older revision		Revision as of 00:55, 28 September 2010
Line 7:		Line 7:
	=== Wire Language ===		=== Wire Language ===
	The wire language will be device-specific. Devices can speak any language they want as long as someone has written a "driver" to translate that language to/from the chosen format that will transmitted/received over XMPP.		The wire language will be device-specific. Devices can speak any language they want as long as someone has written a "driver" to translate that language to/from the chosen format that will transmitted/received over XMPP.

			JeeMesh protocol is being worked on to extend the [http://cafe.jeelabs.net/sw/library_-_rf12/ RF12] frame network to support datagrams up to 1022 bytes over a mesh of [http://cafe.jeelabs.net/lab/jn5/ JeeNodes]. The goal is to support up to 4 hop meshes of up to 26 nodes plus 4 servers/gateways each.

	=== Message Format ===		=== Message Format ===

Sitwon: Created page with 'The goal of this project is: ____________________ == Implementation == === Diagram === [ Device ]<--- ? Wire Language ? --->[ Driver ]<--- ? Message Format ? --->[ XMPP server ]…'

2010-08-06T03:11:22Z

Created page with 'The goal of this project is: ____________________ == Implementation == === Diagram === [ Device ]<--- ? Wire Language ? --->[ Driver ]<--- ? Message Format ? --->[ XMPP server ]…'

New page

The goal of this project is: ____________________

== Implementation ==
=== Diagram ===
[ Device ]<--- ? Wire Language ? --->[ Driver ]<--- ? Message Format ? --->[ XMPP server ]<--- ? Message Format ? --->[ XMPP client ]

=== Wire Language ===
The wire language will be device-specific. Devices can speak any language they want as long as someone has written a "driver" to translate that language to/from the chosen format that will transmitted/received over XMPP.

=== Message Format ===
Since XMPP messages are already XML, I think it makes sense to use an XML vocabulary as the message format.

Possible candidates would be:
* [http://www.eeml.org/ EEML]: Extended Environment Markup Language
** Very simple
** Widely deployed.
** Not a true standard
** No namespace
* [http://en.wikipedia.org/wiki/SensorML SensorML]: Open Geospatial Consortium's Sensor Markup Language
** More complex
** Possibly not an open standard
** Not as widely deployed.

Based on my quick research I'm not entirely pleased with either one. A third option to consider would be designing our own XML vocabulary.

The reason for having a standard message format is to encourage collaboration and interoperability between devices and client applications. Use of the message format would be opt-in.

Discuss your ideas!