Hi, I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise? I'm particularly interested if there is some sort of a reference implementation of a "Thing Register". Best regards, Eelco Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. 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.
Hello Eelco We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.) We are also working on a reference Thing Registry and Provisioning Server at the moment. You can find it here: http://thingk.me/ API page: https://www.thingk.me/Provisioning/Api.xml At the bottom of the API page, you can also find some papers related to XMPP & IoT. There's also an Android app you can download, to interact and with the registry and claim ownership of devices and interact with them. Other platforms coming soon. Best regards, Peter Waher -----Original Message----- From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl] Sent: den 21 augusti 2014 11:23 To: XMPP in the Internet of Things Subject: [IOT] Reference implementation Hi, I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise? I'm particularly interested if there is some sort of a reference implementation of a "Thing Register". Best regards, Eelco ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14
On August 21, 2014 5:40:49 PM CEST, Peter Waher <Peter.Waher@clayster.com> wrote:
Hello Eelco
We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.)
First off, looking forward to this! Not to rain on your parade or diminish the huge amount of work you've put into this, but all of these specifications are currently Experimental. Are you addressing the possibility that any of them might incur (significant) changes after the release of your book? FWIW I am still planning to go through all of the IoT related specs with a fresh look. I know this is quite a task, but this should be done eventually, hopefully by a bunch of people. From what I remember when accepting (formally not-objecting to) these XEPs, they are quite lengthy. Also, you've reported some issues with reusing existing building blocks. I hope to give you more actionable feedback soonish. -- Cheers, ralphm
Hello Ralph Thanks for your concern, and look forward to your input.
Not to rain on your parade or diminish the huge amount of work you've put into this, but all of these specifications are currently Experimental. Are you addressing the possibility that any of them might incur (significant) changes after the release of your book?
Correct. Yes, this is addressed. It highlights the issue that some of the extensions might be sufficiently mature now, to start the work of moving them to Draft.
FWIW I am still planning to go through all of the IoT related specs with a fresh look. I know this is quite a task, but this should be done eventually, hopefully by a bunch of people. From what I remember when accepting (formally not-objecting to) these XEPs, they are quite lengthy.
Yes, they might be lengthy. But it's only because they have examples in them. Tried to mimic previous XEPs. They are still shorter than many other popular XEPs.
Also, you've reported some issues with reusing existing building blocks.
What existing building blocks would that be?
I hope to give you more actionable feedback soonish.
Excellent. Best regards, Peter Waher
Hi Peter, Thank you for your quick answer! I'm going to take a look at the stuff you sent me. Kind regards, Eelco On 21 aug. 2014, at 17:40, Peter Waher <Peter.Waher@clayster.com> wrote:
Hello Eelco
We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.)
We are also working on a reference Thing Registry and Provisioning Server at the moment. You can find it here: http://thingk.me/
API page: https://www.thingk.me/Provisioning/Api.xml
At the bottom of the API page, you can also find some papers related to XMPP & IoT. There's also an Android app you can download, to interact and with the registry and claim ownership of devices and interact with them. Other platforms coming soon.
Best regards, Peter Waher
-----Original Message----- From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl] Sent: den 21 augusti 2014 11:23 To: XMPP in the Internet of Things Subject: [IOT] Reference implementation
Hi,
I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise?
I'm particularly interested if there is some sort of a reference implementation of a "Thing Register".
Best regards, Eelco
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14 _______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. 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.
HI I have an open implementation of xep 323 and 325 in python published on github https://github.com/joachimlindborg/SleekXMPP/tree/xep_0323_325 It will take some major steps during the autumn and hopefully soon merge fully in the main release track. We do also have some java code based on smack if thats of interest but thats not fully published yet. *Regards* Joachim Lindborg CTO, systems architect Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270 2014-08-21 17:40 GMT+02:00 Peter Waher <Peter.Waher@clayster.com>:
Hello Eelco
We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.)
We are also working on a reference Thing Registry and Provisioning Server at the moment. You can find it here: http://thingk.me/
API page: https://www.thingk.me/Provisioning/Api.xml
At the bottom of the API page, you can also find some papers related to XMPP & IoT. There's also an Android app you can download, to interact and with the registry and claim ownership of devices and interact with them. Other platforms coming soon.
Best regards, Peter Waher
-----Original Message----- From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl] Sent: den 21 augusti 2014 11:23 To: XMPP in the Internet of Things Subject: [IOT] Reference implementation
Hi,
I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise?
I'm particularly interested if there is some sort of a reference implementation of a "Thing Register".
Best regards, Eelco
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14 _______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Hi Joachim, Thanks for the links. I will take a look at the implementation. If we go forward on this our client side currently depends on Java. In that case the smack-based code might come in handy. Are you planning to release that in the open source in the coming months? Best regards, Eelco On 22 aug. 2014, at 01:03, Joachim Lindborg <joachim.lindborg@sust.se> wrote:
HI I have an open implementation of xep 323 and 325 in python published on github https://github.com/joachimlindborg/SleekXMPP/tree/xep_0323_325 It will take some major steps during the autumn and hopefully soon merge fully in the main release track.
We do also have some java code based on smack if thats of interest but thats not fully published yet.
Regards Joachim Lindborg CTO, systems architect
Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270
2014-08-21 17:40 GMT+02:00 Peter Waher <Peter.Waher@clayster.com>: Hello Eelco
We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.)
We are also working on a reference Thing Registry and Provisioning Server at the moment. You can find it here: http://thingk.me/
API page: https://www.thingk.me/Provisioning/Api.xml
At the bottom of the API page, you can also find some papers related to XMPP & IoT. There's also an Android app you can download, to interact and with the registry and claim ownership of devices and interact with them. Other platforms coming soon.
Best regards, Peter Waher
-----Original Message----- From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl] Sent: den 21 augusti 2014 11:23 To: XMPP in the Internet of Things Subject: [IOT] Reference implementation
Hi,
I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise?
I'm particularly interested if there is some sort of a reference implementation of a "Thing Register".
Best regards, Eelco
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14 _______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. 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.
yes that is the plan. My project ends september, so should be available by then. But we could arrange for you to try it out beforehand would be good testing *Regards* Joachim Lindborg CTO, systems architect Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270 2014-08-26 12:05 GMT+02:00 Cramer, E.R. (Eelco) <Eelco.Cramer@tno.nl>:
Hi Joachim,
Thanks for the links. I will take a look at the implementation.
If we go forward on this our client side currently depends on Java. In that case the smack-based code might come in handy. Are you planning to release that in the open source in the coming months?
Best regards, Eelco
On 22 aug. 2014, at 01:03, Joachim Lindborg <joachim.lindborg@sust.se> wrote:
HI I have an open implementation of xep 323 and 325 in python published on github https://github.com/joachimlindborg/SleekXMPP/tree/xep_0323_325 It will take some major steps during the autumn and hopefully soon merge fully in the main release track.
We do also have some java code based on smack if thats of interest but thats not fully published yet.
*Regards* Joachim Lindborg CTO, systems architect
Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270
2014-08-21 17:40 GMT+02:00 Peter Waher <Peter.Waher@clayster.com>:
Hello Eelco
We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.)
We are also working on a reference Thing Registry and Provisioning Server at the moment. You can find it here: http://thingk.me/
API page: https://www.thingk.me/Provisioning/Api.xml
At the bottom of the API page, you can also find some papers related to XMPP & IoT. There's also an Android app you can download, to interact and with the registry and claim ownership of devices and interact with them. Other platforms coming soon.
Best regards, Peter Waher
-----Original Message----- From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl] Sent: den 21 augusti 2014 11:23 To: XMPP in the Internet of Things Subject: [IOT] Reference implementation
Hi,
I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise?
I'm particularly interested if there is some sort of a reference implementation of a "Thing Register".
Best regards, Eelco
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14 _______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
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.
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Thank you for the offer. I'll keep in touch! My project runs into 2015 so we would be able to contribute to the code base. Thanks, Eelco On 26 aug. 2014, at 12:11, Joachim Lindborg <joachim.lindborg@sust.se> wrote:
yes that is the plan. My project ends september, so should be available by then. But we could arrange for you to try it out beforehand would be good testing
Regards Joachim Lindborg CTO, systems architect
Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270
2014-08-26 12:05 GMT+02:00 Cramer, E.R. (Eelco) <Eelco.Cramer@tno.nl>: Hi Joachim,
Thanks for the links. I will take a look at the implementation.
If we go forward on this our client side currently depends on Java. In that case the smack-based code might come in handy. Are you planning to release that in the open source in the coming months?
Best regards, Eelco
On 22 aug. 2014, at 01:03, Joachim Lindborg <joachim.lindborg@sust.se> wrote:
HI I have an open implementation of xep 323 and 325 in python published on github https://github.com/joachimlindborg/SleekXMPP/tree/xep_0323_325 It will take some major steps during the autumn and hopefully soon merge fully in the main release track.
We do also have some java code based on smack if thats of interest but thats not fully published yet.
Regards Joachim Lindborg CTO, systems architect
Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270
2014-08-21 17:40 GMT+02:00 Peter Waher <Peter.Waher@clayster.com>: Hello Eelco
We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.)
We are also working on a reference Thing Registry and Provisioning Server at the moment. You can find it here: http://thingk.me/
API page: https://www.thingk.me/Provisioning/Api.xml
At the bottom of the API page, you can also find some papers related to XMPP & IoT. There's also an Android app you can download, to interact and with the registry and claim ownership of devices and interact with them. Other platforms coming soon.
Best regards, Peter Waher
-----Original Message----- From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl] Sent: den 21 augusti 2014 11:23 To: XMPP in the Internet of Things Subject: [IOT] Reference implementation
Hi,
I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise?
I'm particularly interested if there is some sort of a reference implementation of a "Thing Register".
Best regards, Eelco
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14 _______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
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.
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Wonderful to hear! *Regards* Joachim Lindborg CTO, systems architect Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270 2014-08-26 12:31 GMT+02:00 Cramer, E.R. (Eelco) <Eelco.Cramer@tno.nl>:
Thank you for the offer. I'll keep in touch!
My project runs into 2015 so we would be able to contribute to the code base.
Thanks, Eelco
On 26 aug. 2014, at 12:11, Joachim Lindborg <joachim.lindborg@sust.se> wrote:
yes that is the plan. My project ends september, so should be available by then. But we could arrange for you to try it out beforehand would be good testing
*Regards* Joachim Lindborg CTO, systems architect
Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270
2014-08-26 12:05 GMT+02:00 Cramer, E.R. (Eelco) <Eelco.Cramer@tno.nl>:
Hi Joachim,
Thanks for the links. I will take a look at the implementation.
If we go forward on this our client side currently depends on Java. In that case the smack-based code might come in handy. Are you planning to release that in the open source in the coming months?
Best regards, Eelco
On 22 aug. 2014, at 01:03, Joachim Lindborg <joachim.lindborg@sust.se> wrote:
HI I have an open implementation of xep 323 and 325 in python published on github https://github.com/joachimlindborg/SleekXMPP/tree/xep_0323_325 It will take some major steps during the autumn and hopefully soon merge fully in the main release track.
We do also have some java code based on smack if thats of interest but thats not fully published yet.
*Regards* Joachim Lindborg CTO, systems architect
Sustainable Innovation SUST.se <http://sust.se/> Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270
2014-08-21 17:40 GMT+02:00 Peter Waher <Peter.Waher@clayster.com>:
Hello Eelco
We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.)
We are also working on a reference Thing Registry and Provisioning Server at the moment. You can find it here: http://thingk.me/
API page: https://www.thingk.me/Provisioning/Api.xml
At the bottom of the API page, you can also find some papers related to XMPP & IoT. There's also an Android app you can download, to interact and with the registry and claim ownership of devices and interact with them. Other platforms coming soon.
Best regards, Peter Waher
-----Original Message----- From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl] Sent: den 21 augusti 2014 11:23 To: XMPP in the Internet of Things Subject: [IOT] Reference implementation
Hi,
I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise?
I'm particularly interested if there is some sort of a reference implementation of a "Thing Register".
Best regards, Eelco
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14 _______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
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.
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
_______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
Hi Joachim, We are currently planning to try out XEPs 323 and 325 and we want to implement these functions on an OSGi framework. You mentioned that you are working on an open source Java implementation of these XEPs. I’m wondering is this implementation already available? Thanks, Eelco On 26 Aug 2014, at 12:11, Joachim Lindborg <joachim.lindborg@sust.se<mailto:joachim.lindborg@sust.se>> wrote: yes that is the plan. My project ends september, so should be available by then. But we could arrange for you to try it out beforehand would be good testing Regards Joachim Lindborg CTO, systems architect Sustainable Innovation SUST.se<http://SUST.se> Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se<mailto:Joachim.lindborg@sust.se> linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270 2014-08-26 12:05 GMT+02:00 Cramer, E.R. (Eelco) <Eelco.Cramer@tno.nl<mailto:Eelco.Cramer@tno.nl>>: Hi Joachim, Thanks for the links. I will take a look at the implementation. If we go forward on this our client side currently depends on Java. In that case the smack-based code might come in handy. Are you planning to release that in the open source in the coming months? Best regards, Eelco On 22 aug. 2014, at 01:03, Joachim Lindborg <joachim.lindborg@sust.se<mailto:joachim.lindborg@sust.se>> wrote: HI I have an open implementation of xep 323 and 325 in python published on github https://github.com/joachimlindborg/SleekXMPP/tree/xep_0323_325 It will take some major steps during the autumn and hopefully soon merge fully in the main release track. We do also have some java code based on smack if thats of interest but thats not fully published yet. Regards Joachim Lindborg CTO, systems architect Sustainable Innovation SUST.se<http://sust.se/> Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg@sust.se<mailto:Joachim.lindborg@sust.se> linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270 2014-08-21 17:40 GMT+02:00 Peter Waher <Peter.Waher@clayster.com<mailto:Peter.Waher@clayster.com>>: Hello Eelco We are currently writing a book ("Learning Internet of Things") which will include source code for a sensor, actuator, camera, controller and a protocol bridge. This code includes support for XMPP, MQTT, CoAP, UPnP and HTTP. It is not yet public, but will be soon. This free code supports XEPs 0323, 0324, 0325 (not 0326), 0347 & 0348. (We also license our Clayster platform, which has a much more extensive support for extensions and protocols.) We are also working on a reference Thing Registry and Provisioning Server at the moment. You can find it here: http://thingk.me/ API page: https://www.thingk.me/Provisioning/Api.xml At the bottom of the API page, you can also find some papers related to XMPP & IoT. There's also an Android app you can download, to interact and with the registry and claim ownership of devices and interact with them. Other platforms coming soon. Best regards, Peter Waher -----Original Message----- From: Cramer, E.R. (Eelco) [mailto:Eelco.Cramer@tno.nl<mailto:Eelco.Cramer@tno.nl>] Sent: den 21 augusti 2014 11:23 To: XMPP in the Internet of Things Subject: [IOT] Reference implementation Hi, I was wondering if (parts) of the IoT XMPP specifications and / or components that are used within the specification are already implemented as open source or otherwise? I'm particularly interested if there is some sort of a reference implementation of a "Thing Register". Best regards, Eelco ----- No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com/> Version: 2014.0.4745 / Virus Database: 4007/8066 - Release Date: 08/19/14 _______________________________________________ IOT mailing list IOT@xmpp.org<mailto:IOT@xmpp.org> http://mail.jabber.org/mailman/listinfo/iot _______________________________________________ IOT mailing list IOT@xmpp.org<mailto:IOT@xmpp.org> http://mail.jabber.org/mailman/listinfo/iot Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. TNO aanvaardt geen aansprakelijkheid voor de inhoud van deze e-mail, de wijze waarop u deze gebruikt en voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. 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. _______________________________________________ IOT mailing list IOT@xmpp.org<mailto:IOT@xmpp.org> http://mail.jabber.org/mailman/listinfo/iot _______________________________________________ IOT mailing list IOT@xmpp.org<mailto:IOT@xmpp.org> http://mail.jabber.org/mailman/listinfo/iot
participants (4)
-
Cramer, E.R. (Eelco) -
Joachim Lindborg -
Peter Waher -
Ralph Meijer