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

_______________________________________________
IOT mailing list
IOT@xmpp.org
http://mail.jabber.org/mailman/listinfo/iot