Re: [Standards] UPDATED: XEP-0325 (Internet of Things - Control)

2014-04-23 Thread Teemu Väisänen
Hi Peter.

That description looks like the information goes from sensors to pubsub
nodes and from there to subscribers. We have been using mostly SOX protoxep
for that purpose.. I meant controlling, configuring, etc. sensors with
pubsub. Should there be two different XEPs are will that one handle both
directions?

-Teemu



2014-04-21 17:55 GMT+03:00 Peter Waher peter.wa...@clayster.com:

  Hello Teemu



 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:



 xep--IoT-PubSub

 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.



 Best regards,

 Peter Waher





 -Original Message-
 From: Teemu Väisänen [mailto:uol...@gmail.com]
 Sent: den 20 april 2014 14:34
 To: XMPP Standards
 Subject: Re: [Standards] UPDATED: XEP-0325 (Internet of Things - Control)



 Hi all.



 As Peter mentions in LinkedIn thread


 https://www.linkedin.com/groupItem?view=item=5862110582659891202type=membergid=49429



 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?



 Happy Easter.



 -Teemu



 2014-04-07 23:53 GMT+03:00 XMPP Extensions Editor edi...@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

 





Re: [Standards] UPDATED: XEP-0325 (Internet of Things - Control)

2014-04-23 Thread Peter Waher
Hello Teemu

Yes, the original plan was only to include sensor data. But that is easily 
mended, so the XEP could show both how to publish sensor data (based on 
XEP-0323), and how to publish control commands (based on XEP-0325). Would that 
be sufficient, or do you see more use cases you would like to include as well?

Best regards,
Peter Waher


From: Teemu Väisänen [mailto:uol...@gmail.com]
Sent: den 23 april 2014 05:33
To: XMPP Standards
Subject: Re: [Standards] UPDATED: XEP-0325 (Internet of Things - Control)

Hi Peter.

That description looks like the information goes from sensors to pubsub nodes 
and from there to subscribers. We have been using mostly SOX protoxep for that 
purpose.. I meant controlling, configuring, etc. sensors with pubsub. Should 
there be two different XEPs are will that one handle both directions?
-Teemu

2014-04-21 17:55 GMT+03:00 Peter Waher 
peter.wa...@clayster.commailto:peter.wa...@clayster.com:

Hello Teemu



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:


xep--IoT-PubSub

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.



Best regards,

Peter Waher





-Original Message-
From: Teemu Väisänen [mailto:uol...@gmail.commailto:uol...@gmail.com]
Sent: den 20 april 2014 14:34
To: XMPP Standards
Subject: Re: [Standards] UPDATED: XEP-0325 (Internet of Things - Control)



Hi all.



As Peter mentions in LinkedIn thread

https://www.linkedin.com/groupItem?view=item=5862110582659891202type=membergid=49429



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?



Happy Easter.



-Teemu



2014-04-07 23:53 GMT+03:00 XMPP Extensions Editor 
edi...@xmpp.orgmailto:edi...@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