Difference between revisions of "Peter Waher for Council 2013"

Jump to navigation Jump to search
no edit summary
Line 1: Line 1:
== Introduction ==
== Introduction ==


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. It uses XMPP to provide peer-to-peer funcionality to services and a communication platform for devices in a secure manner.
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. It uses XMPP to provide peer-to-peer functionality to services and a communication platform for devices in a secure manner.


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.
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.
Line 27: Line 27:
In many cases Internet of Things can use existing extensions, or enhance existing extension, primarily designed for use in chat/messaging clients by human users. This includes, but is not limited to, data forms, service discovery, MUC, PubSub, streaming in various forms, RPC, roster features, contact/user information, versioning, etc. My interest here is to include an IoT perspective to all new extensions made for XMPP to make XMPP easier and more natural to use for IoT and M2M applications.
In many cases Internet of Things can use existing extensions, or enhance existing extension, primarily designed for use in chat/messaging clients by human users. This includes, but is not limited to, data forms, service discovery, MUC, PubSub, streaming in various forms, RPC, roster features, contact/user information, versioning, etc. My interest here is to include an IoT perspective to all new extensions made for XMPP to make XMPP easier and more natural to use for IoT and M2M applications.


Thera are also several areas which need to be expanded for XMPP to be successfully implemented in the Internet of Things and related areas. Therefore, apart from my general interest in XMPP and their extensions, my aim is to provide added support by working on extending XMPP in the following areas:
There are also several areas which need to be expanded for XMPP to be successfully implemented in the Internet of Things and related areas. Therefore, apart from my general interest in XMPP and their extensions, my aim is to provide added support by working on extending XMPP in the following areas:


* Internet of Things. This includes among others:
* Internet of Things. This includes among others:
9

edits

Navigation menu