Hi Joachim, We have over the last few years developed a very rich set of XMPP protocols fro working with Iot devices… From TV's to air conditioners to thermostats to battery devices to lighting.. to…. I saw the XEP's you mention as they were being developed, and unfortunately we were too far ahead in our own definitions and implementations at the time they were being formulated. When I last looked at them they were insufficient for the use cases our customers wanted and we sadly did not have the bandwidth to help make them 'fit'. Which I do regret.
We already had a couple of major brands adopting our protocol, and the consequence of changing and working with you guys to make changes at that time were high impact. Now doubly so :-( As is often the case, "executing code always wins". I am hoping next year to be able to more fully contribute to the open standards in this area and also to have a road map for our protocol to adopt the standards where appropriate. As we work on the Eventlogging XEP implementation we will be sure to provide any issues or feedback as we find it. Mat On Tue, Dec 24, 2013 at 5:34 PM, Joachim Lindborg <[email protected]>wrote: > Here is the latest https://github.com/joachimlindborg/XMPP-IoT > > > http://htmlpreview.github.io/?https://github.com/joachimlindborg/XMPP-IoT/blob/master/eventlogging.html > > why not add the the two extensions for read and write of IoT devices to. > So your whole system is compliant? > http://xmpp.org/extensions/xep-0323.html > http://xmpp.org/extensions/xep-0325.html > > Just send a note will be happy helping you out > > > > *Regards* > Joachim Lindborg > CTO, systems architect > > Sustainable Innovation AB > Adress: Box 55998 102 16 Stockholm > Besöksadress: Storgatan 31 (Malmgården) > Email: [email protected], www.sust.se > linkedin: http://www.linkedin.com/in/joachimlindborg > Tel +46 706-442270 > > > 2013/12/24 mat henshall <[email protected]> > >> All - where is the latest draft of the event logging XEP? >> >> We are going prototype it into our IOT framework and build a little event >> logging client to receive and store… >> >> Mat >> >> >> On Wed, Nov 13, 2013 at 2:58 PM, Peter Waher <[email protected]>wrote: >> >>> Hello Ludovic >>> >>> Excellent. Thanks for taking the time to read the document so carefully. >>> It's hard to see those details. >>> >>> I've attached a new version of the document where this has been >>> corrected. >>> >>> Best regards, >>> Peter Waher >>> >>> -----Original Message----- >>> From: Ludovic BOCQUET [mailto:[email protected]] >>> Sent: den 13 november 2013 19:34 >>> To: [email protected] >>> Subject: Re: [Standards] Updated: Event logging over XMPP >>> >>> Comments after: >>> Le 13/11/2013 19:09, Peter Waher a écrit : >>> > <message from='[email protected]/device' to=' >>> [email protected]' type='normal' xml:lang='en'> >>> > <log xmlns='urn:xmpp:eventlog' timestamp='2013-11-10T15:52:23Z'> >>> > <message>Something happened.</message> >>> > </log> >>> > <log xmlns='urn:xmpp:eventlog' >>> timestamp='2013-11-10T15:54:23Z''> >>> must be: >>> >>> <log xmlns='urn:xmpp:eventlog' timestamp='2013-11-10T15:54:23Z'> >>> >>> > <message>Something else happened.</message> >>> > </log> >>> > </message> >>> >>> For be beautiful, all http://www.xmpp.org links must be http://xmpp.org. >>> Example <http://www.xmpp.org/extensions/ipr-policy.shtml> >>> >>> Regards, >>> >>> BOCQUET Ludovic >>> >>> >> >> >> -- >> >> Mat Henshall >> Founder and CEO, Square Connect, Inc. >> San Jose, CA >> www.squareconnect.com >> cell: 650.814.7585 >> > > -- Mat Henshall Founder and CEO, Square Connect, Inc. San Jose, CA www.squareconnect.com cell: 650.814.7585
