Hello
During the work in other standards groups, there has been some interest in
the discovery model presented in XEP-0347. This has lead to the desire to
update the IoT-discovery encoding described in the XEP somewhat and
formalize it into a URI scheme. I've therefore prepared an application to
IANA for a provisional URI scheme. The idea is to send it by the end of next
week. So, if you have time, and an interest, you're welcome to return any
comments, suggestions or questions to me by then, so I have a chance to
update the application before mailing it. The idea is to update XEP-0347
after the approval of such a provisional URI scheme.
Best regards,
Peter Waher
Hi guys,
We’ve decided to open source our implementation of XEP-0347 IoT Discovery. We’ve named it Ekster and you can find the code on github: https://github.com/TNO-IoT/ekster <https://github.com/TNO-IoT/ekster>
Until now there was no open source implementation of the IoT discovery XEP for developers to play with (expect for the hosted service of Clayster) and Ekster enables developers with an intrest in XMPP IoT to run a registry on their own development environment.
The current state of Ekster is that it suitable for development. We haven’t used it in production ourselves. Ekster is written in coffeescript and runs on NodeJS. Currently it can run as an external component to a XMPP server but it should not be to hard to change it to run as a XMPP client. The documentation is still to be improved with message flow examples and it would be nice to create some kind of demo site to see the code in action.
Ekster uses mongod as its database but it is possible to add custom backend providers to enable other storage. When we started the implementation we’ve experimented with octoblu as a backend and the code for the octublu backend is still there.
The code is accompanied by 2 other github projects that I use for integration tests.
I welcome all of your suggestions! Feedback is greatly appreciated.
Kind regards,
Eelco
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.
