Peter Waher for Council 2013

From XMPP WIKI
Jump to: navigation, search

Contents

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 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 experience the advantages and mistakes made in different architectures and solutions in different areas.

As things get 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.

XMPP & XSF Activity

I spend a lot of time rallying support for the use of XMPP for the Internet of Things, in sensor networks and semantic web applications in Europe and South America. Through Clayster, this effort is extended to USA as well. I partake in standardization efforts (IEEE/ISO/IEC) defining how to use XMPP for IoT. I also partake in several research projects whose aim it is to establish methods to interchange sensor data using these technologies, as well as hold lectures explaining the benefits of the use of XMPP and Semantic Web technologies in sensor networks.

In this work, I've helped in the authoring of the following XEPs:

Purpose for applying

The main purpose for applying to the council is to be able to work closer with the XSF and help develop XMPP as a platform for the Internet of Things and related areas, as well as provide my experience within these areas to the council.

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.

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:
    • Thing detection, integrated with existing XMPP standards
    • Thing meta data, capabilities
    • Starting sensor readouts, and asynchronous metering data reporting.
    • Thing configuration (i.e. controlling devices for home automation, for example)
    • Interoperability between manufacturers, by providing an accepted open framework for communications.
    • Provisioning in sensor/IoT networks (i.e. controlling who can access what)
  • Semantic Web (web 3.0). This includes:
    • Semantic Service discovery, integrated with existing XMPP standards.
    • Publishing SPARQL endpoints over XMPP
    • Extending SPARQL queries over social/sensor networks.
    • Transporting semantic information (RDF/XML, Turtle, SPARQL Results/XML, etc.) over XMPP
  • Decentralized Social Networking.

Contact