Difference between revisions of "Peter Waher for Council 2013"

Jump to navigation Jump to search
Line 1: Line 1:
== Introduction ==
== Introduction ==


My name is Peter Waher, and I work for Clayster where I manage the development of a platform for services hosted in the cloud, Semantic Web, the grid or/and sensor networks/IoT. I've worked since 1994 within the field of device communication, starting with utility meter reading, but later including control, automation, services, IoT, IP-TV, etc. (Prior to 94 I worked with video games development.) I've worked with a very large set of protocols over serial or parallel buses, M2M networks, radio networks, power line-based networks, and IP-based networks. I've worked both with large sets of proprietary protocols as well as standardized protocols (both standardized by standardization bodies and de facto standards having evolved into "standards" within their corresponding areas). I've also worked within all aspects of system design and development, from firmware development in resource constrained devices (using assembler) to design of large AMR and IoT systems. Through this work I've had the possibility to learn the advantages and mistakes made in different architectures and solutions in different areas.
My name is Peter Waher, and I'm a co-founder of Clayster where I manage the development of a platform for grid or/and sensor networks/IoT services hosted in the cloud, including Semantic Web and related "web 3.0" technologies. It is used by the largest telecom operator in the north of Europe as a Multi-Screen application platform embedding it into their IP-TV network.
 
I've worked since 1994 within the field of device communication, starting with utility meter reading, but later including control, automation, services, IoT, IP-TV, etc. (Prior to 94 I worked with video games development.) I've worked with a very large set of protocols over serial or parallel buses, M2M networks, radio networks, power line-based networks, and IP-based networks. I've worked both with large sets of proprietary protocols as well as standardized protocols (both standardized by standardization bodies and de facto standards having evolved into "standards" within their corresponding areas). I've also worked within all aspects of system design and development, from firmware development in resource constrained devices (using assembler) to design of large AMR and IoT systems. Through this work I've had the possibility to learn the advantages and mistakes made in different architectures and solutions in different areas.


As things gets closer to the Internet, I firmly believe XMPP is the best candidate available (among all presented to date) for use as an official "IoT protocol", if extended correctly. It is this conviction that makes me want to work as closely as I can with the XSF in order to participate in this extension into the world of IoT, using XMPP technology. I want to bring the experience achieved in my previous work to make sure XSF implements good, proven and interoperable practices where possible and avoids pitfalls and errors committed previously by others.
As things gets closer to the Internet, I firmly believe XMPP is the best candidate available (among all presented to date) for use as an official "IoT protocol", if extended correctly. It is this conviction that makes me want to work as closely as I can with the XSF in order to participate in this extension into the world of IoT, using XMPP technology. I want to bring the experience achieved in my previous work to make sure XSF implements good, proven and interoperable practices where possible and avoids pitfalls and errors committed previously by others.
15

edits

Navigation menu