[IOT] Thoughts on XEP-0347 IoT - discovery

Cramer, E.R. (Eelco) Eelco.Cramer at tno.nl
Tue Oct 14 15:28:44 UTC 2014


Hi,

I'm currently investigating options to implement something similar as the IoT registry that is described in XEP-0347 but I have some different requirements that I would like to share as they might help to improve this XEP.

I would like to allowing more complex searches in the registry. For example I would like to be able to do spatial searches:

- give me 10 temperature sensors closest to a given location.
- give me all light-switches in a range of hundred meters around a given location.

Following the current XEP I cannot ask such queries directly but should fire multiple queries and do all calculation in the client.

Also I would like to do union searches so I do not have to calculate intersections myself:

- give me all light-switches or light-dimmers closest to a given location.

As these type of queries are more complex and not all registry servers might have implemented such a feature I would like to add the possibility to discover registry capabilities. This kind of discovery can be done using entity capability (XEP-0115).

Also the current description XEP-0347 allows only meta-data that consist of numbers and strings but I would like to be able to have more options (including location). Maybe we can reuse the stuff that is in XEP-0004 data-forms (https://xmpp.org/extensions/xep-0004.html#protocol-fieldtypes) and add XEP-0350 (data forms geolocation element).

This would allow more semantical reasoning on the meta-data of a thing (like the example queries above).

What do you think?

Best regards,
Eelco

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.jabber.org/pipermail/iot/attachments/20141014/1d467c7f/attachment.sig>
-------------- next part --------------
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.


More information about the IOT mailing list