<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>That sounds like a great project. The ARM9 should provide plenty of power to deal with the XMPP side of things.</div><div><br></div><div>With regards to formats, I've no idea what sort of data you are interested in but I've previously stumbled across: <a href="http://xmpp.org/extensions/xep-0127.html">http://xmpp.org/extensions/xep-0127.html</a> which might be useful to you.</div><div><br></div><div>I'm sure someone else on here can offer more advice though on formats.</div><div><br></div><br><div><div>On 7 Mar 2011, at 13:49, karel pavlata wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi..<br>In our first approach I'm counting on ARM9 based embedded system with<br>linux running on top of it and probably Java as programming<br>environment (there will be also implemented ReST access to the<br>network). I designed HW platform which is agnostic to the particular<br>WSN and gateway would pose as abstraction, so it's exactly ass You<br>said. Later I would like to re-implement the idea (if turns to be<br>usable) to some more lightweight device. I was thinking of XMPP to<br>pose as tool for gateways to distribute events and to exchange<br>configuration among them.<br><br>karel<br><br>2011/3/7 Theo Cushion <<a href="mailto:theo@jivatechnology.com">theo@jivatechnology.com</a>>:<br><blockquote type="cite">Hi Karel,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I've thrown around the idea of using XMPP as a system for distributing sensor data before. The pubsub mechanism provides a lot of really nice features that would make it great for clients.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I think your biggest hurdle is going to be the resource constrained embedded device. What platform are you going to be using? Is battery power an issue? The big problem is that you need a full network stack, and then enough processing power to crunch the XML. Is it possible that the XMPP gateway is a bit more powerful with access to say a ZigBee network on one side and the XMPP system on the other?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Just some thoughts.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Good luck!<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Theo<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 7 Mar 2011, at 13:32, karel pavlata wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Hello,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I'm a student working on 'smart' gateway for wireless sensor networks<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(WSN) with an idea of XMPP as a messaging/event distribution system.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">It would be probably build around XEP-0060: Publish-Subscribe and/or<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">XEP-0163: Personal Eventing Protocol with clients registering on<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">particular events (e.g. motion detection, new temperature measurement,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">etc.) which would be gathered in a tree of collection and leaf nodes.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Multiple resources (gateways) of single user (representing particular<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">WSN) would coexist and publish events and in this way client would<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">receive events from whole network independently of which gateway<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">generated it. If You have any comments regarding feasibility or like<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the idea and would like to suggest it for GSoC and pose as a mentor<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">please let me know. If the idea is viable it could be another nice<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">usage of XMPP and possible candidate for XEP(?). It would be mainly<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">machine-to-machine communication with gateways being resource<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">constrained embedded devices.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">regards<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Karel Pavlata<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">JDev mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev">http://mail.jabber.org/mailman/listinfo/jdev</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">JDev mailing list<br></blockquote><blockquote type="cite">Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev">http://mail.jabber.org/mailman/listinfo/jdev</a><br></blockquote><blockquote type="cite">Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote>_______________________________________________<br>JDev mailing list<br>Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev">http://mail.jabber.org/mailman/listinfo/jdev</a><br>Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a><br>_______________________________________________<br></div></blockquote></div><br></body></html>