Excellent.
Regarding distinction between fields and control parameters:
Fields provide sensor-data along three axes: Field Name, Node ID and Time. A
single parameter can result in many thousands of fields across time. A control
parameter is more direct. Control parameters exist along two axes:
I almost would say the only important factor is interoperability ;-)
Well also that it is suitable for the IoT devices that we believe is
going to make use of XMPP. In my perspective it would be good if
we consider even very small devices to be candidate for actually
running a complete (subset) of
PS: Forgot to mention relating to the discussion regarding unit conversion in
devices:
One important factor in the design of the IoT XEPs is interoperability between
devices. If support for unit conversion were to be added to XEP-0325, a
mechanism for publishing supported units would also be ne
Jag kollar på Git skall nog lösa det
Den 14 jan 2014 17:16 skrev "Peter Waher" :
> PS:
>
>
>
> While I figure out how to update the extensions on the xmpp.org site, the
> latest revisions can be found here:
>
>
> http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IoT/blob/mast
PS:
While I figure out how to update the extensions on the xmpp.org site, the
latest revisions can be found here:
http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IoT/blob/master/sensor-data.html
http://htmlpreview.github.com/?https://github.com/joachimlindborg/XMPP-IoT/blo
