15
edits
PeterWaher (talk | contribs) |
PeterWaher (talk | contribs) |
||
(11 intermediate revisions by the same user not shown) | |||
Line 50: | Line 50: | ||
== Interoperability Specification == | == Interoperability Specification == | ||
In all networks that combines information from different systems over business and technology borders the crucial thing is to get interoperability. And there is no other way to do this than creating specifications that adds the "common good practices" to make things speak the same language. The interoperability spec will be a moving target with constant elaboration to enable true interoperability between systems | In all networks that combines information from different systems over business and technology borders the crucial thing is to get interoperability. And there is no other way to do this than creating specifications that adds the "common good practices" to make things speak the same language. The interoperability spec will be a moving target with constant elaboration to enable true interoperability between systems | ||
Latest working material: [http://htmlpreview.github.io/?https://github.com/joachimlindborg/XMPP-IoT/blob/master/xep-0000-IoT-Interoperability.html xep-0000-IoT-Interoperability] | |||
Defines guidelines for how to achieve interoperability in sensor networks, publishing interoperability interfaces for different types of devices. | |||
== Enhancing Specifications == | == Enhancing Specifications == | ||
When you have realised that this is the way to go and would like to create more advanced network solutions and collaborative IoT systems you need do expand a bit further. The need for these xeps are that the normal PubSub, Eventing, etc are somewhat limited since they are meant to be used in people to people communication and therefore lacks some functionality. Instead of squeezing machine to machine into the existing xeps. | When you have realised that this is the way to go and would like to create more advanced network solutions and collaborative IoT systems you need do expand a bit further. The need for these xeps are that the normal PubSub, Eventing, etc are somewhat limited since they are meant to be used in people to people communication and therefore lacks some functionality. Instead of squeezing machine to machine into the existing xeps. | ||
=== Discovery === | |||
Defines the peculiars of sensor discovery in sensor networks. Apart from discovering sensors by JID, it also defines how to discover sensors based on location, etc. | |||
=== Events === | |||
Defines how sensors send events, how event subscription, hysteresis levels, etc., are configured. | |||
=== Multicast === | |||
Defines how sensor data can be multicast in efficient ways. | |||
=== Publish/Subscribe === | |||
Defines how efficient publication of sensor data can be made in sensor networks. | |||
=== Battery Powered Devices === | |||
Defines how to handle the peculiars related to battery powered devices, and other devices intermittently available on the network. | |||
== Supporting Specifications == | == Supporting Specifications == | ||
=== Color Field Types === | |||
Link: [http://xmpp.org/extensions/xep-0331.html XEP-0331: Color Field Types] <br/> | |||
Latest working material: [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-DF/blob/master/color-parameter.html GitHub] | |||
Defines extensions for how color parameters can be handled, based on Data Forms. | |||
=== Dynamic Forms === | |||
Link: [http://xmpp.org/extensions/xep-0336.html XEP-0336: Dynamic Forms] <br/> | |||
Latest working material: [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-DF/blob/master/dynamic-forms.html GitHub] | |||
Defines extensions for how dynamic forms can be created, based on Data Forms, Data Forms Validation, Publishing Stream Initiation Requests, Data Forms Layout. | |||
=== Event Logging === | |||
Link: [http://xmpp.org/extensions/xep-0337.html XEP-0337: Event Logging over XMPP] <br/> | |||
Latest working material: [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IOT/blob/master/eventlogging.html GitHub] | |||
Defines extensions for how dynamic forms can be created, based on Data Forms, Data Forms Validation, Publishing Stream Initiation Requests, Data Forms Layout. | |||
=== EXI === | |||
Link: [http://xmpp.org/extensions/xep-0322.html XEP-0322: EXI]<br/> | |||
Current working material: [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-EXI/blob/master/exi.html GitHub] | |||
Defines how to EXI can be used in XMPP to achieve efficient compression of data. Albeit not a sensor network specific XEP, this XEP should be considered in all sensor network implementations where memory and packet size is an issue. | |||
=== IoT Chat === | |||
Latest working material: [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IoT/blob/master/xep-0000-IoT-Chat.html GitHub] | |||
This is a very useful extension to facilitate integration with humans and other systems. Via plain chat messages this defines a easy extendible syntax for interacting with devices, reading values and setting parameters and control values | |||
edits