[Standards] UPDATED: XEP-0325 (Internet of Things - Control)
Peter.Waher at clayster.com
Mon Apr 21 14:55:01 UTC 2014
I've on my to-do list a working item to write just such a document. It has been on the list for a while, and in XEP-0323 & 0325 it is called:
Defines how efficient publication of sensor data can be made in sensor networks.
But it seems to be the logical next step to write that document now... I'll write it and publish it to the list. Any comments and suggestions are welcome.
From: Teemu Väisänen [mailto:uolevi at gmail.com]
Sent: den 20 april 2014 14:34
To: XMPP Standards
Subject: Re: [Standards] UPDATED: XEP-0325 (Internet of Things - Control)
As Peter mentions in LinkedIn thread
"If you don't have the full JID of the sensor, you can publish a <set> command (XEP-0325) to a node on a pubsub server, instead of embedding it in a <message> or <iq> stanza to the sensor. If the sensor subscribes to the node, it will receive the set command and perform the action."
Has anyone defined best practises for such or will them be defined in the next version of XEP-0325? I could see pubsub very useful in use cases when there are, e.g., one million sensors that require the same command to be executed as fast as possible. So they all just get the command from a pubsub node right after they come online, but what would be the best mechanism to tell this node to all the sensors?
2014-04-07 23:53 GMT+03:00 XMPP Extensions Editor <editor at xmpp.org<mailto:editor at xmpp.org>>:
> Version 0.3 of XEP-0325 (Internet of Things - Control) has been released.
> Abstract: This specification describes how to control devices or actuators in an XMPP-based sensor network.
> Changelog: [See revision history] (pw)
> Diff: http://xmpp.org/extensions/diff/api/xep/0325/diff/0.2/vs/0.3
> URL: http://xmpp.org/extensions/xep-0325.html
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Standards