Difference between revisions of "Tech pages/IoT XepsExplained"

Jump to navigation Jump to search
Line 11: Line 11:
At a first glance this can seem hard to grasp with many extensions but it is really simple.
At a first glance this can seem hard to grasp with many extensions but it is really simple.


We need to access and control nodes and if nodes are behind a complex technology we need to find them behind a concentrator and then be able to put a device in use we need the provisioning. When creating more advanced systems discovery and pubsub and eventing will be needed but if you just started concentrate on the [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IoT/blob/master/sensor-data.html data] and [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IoT/blob/master/xep-0000-IoT-Control.html xep-0000-IoT-Control] xeps
We need to access and control nodes and this is basicly done through two xeps the [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IoT/blob/master/sensor-data.html IoT sensor-data] and [http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IoT/blob/master/sensor-network-Control.html IoT-control]
 
Other extensions just cover more complex structures and ways of abstracting lower level transport protocols and hardware.
 
and if nodes are behind a complex technology we need to find them behind a concentrator and then be able to put a device in use we need the provisioning. When creating more advanced systems discovery and pubsub and eventing will be needed but if you just started concentrate on  xeps


== Base Specifications ==
== Base Specifications ==
16

edits

Navigation menu