Difference between revisions of "Peter Waher for Council 2013"

Jump to navigation Jump to search
no edit summary
(Created page with "== Introduction == My name is Peter Waher, and I work for Clayster. Clayster provides a platform for services hosted in the cloud, Semantic Web, the grid or/and sensor networks....")
 
Line 1: Line 1:
== Introduction ==
== Introduction ==


My name is Peter Waher, and I work for Clayster. Clayster provides a platform for services hosted in the cloud, Semantic Web, the grid or/and sensor networks. 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.)
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, powerline-based networks, and IP-based networks.
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 standadization bodies and de facto standards having evolved into "standards" within their corresponding areas). 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.
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.
 
== Contact ==
 
* Mail address: [mailto:peter.waher@clayster.com peter.waher@clayster.com]
* JID: peter.waher@gmail.com, peter.waher@jabber.org
* Twitter: [http://twitter.com/#!/PeterWaher PeterWaher]
* LinkedIn: [http://linkedin.com/in/peterwaher]


== XMPP Activity ==
== XMPP Activity ==
Line 37: Line 30:
** Thing meta data, capabilities
** Thing meta data, capabilities
** Starting sensor readouts, and asynchronous metering data reporting.
** Starting sensor readouts, and asynchronous metering data reporting.
** Thing configuratons (i.e. controlling devices for home automation, for example)
** Thing configuration (i.e. controlling devices for home automation, for example)
** Interoperability between manufacturers, by providing an accepted open framework for communications.
** Interoperability between manufacturers, by providing an accepted open framework for communications.
** Provisioning in sensor/IoT networks (i.e. controlling who can access what)
** Provisioning in sensor/IoT networks (i.e. controlling who can access what)
Line 46: Line 39:
** Transporting semantic information (RDF/XML, Turtle, SPARQL Results/XML, etc.) over XMPP
** Transporting semantic information (RDF/XML, Turtle, SPARQL Results/XML, etc.) over XMPP
* Decentralized Social Networking.
* Decentralized Social Networking.
== Contact ==
* Mail address: [mailto:peter.waher@clayster.com peter.waher@clayster.com]
* JID: peter.waher@gmail.com, peter.waher@jabber.org
* Twitter: [http://twitter.com/#!/PeterWaher PeterWaher]
* LinkedIn: [http://linkedin.com/in/peterwaher]
8

edits

Navigation menu