Difference between revisions of "Peter Waher Application 2013"

From XMPP WIKI
Jump to navigation Jump to search
(Created page with "== Introduction == My name is Peter Waher, and I'm a cofounder of Clayster. Clayster provides a platform for Internet-of-Things-based services hosted on everything from plug ...")
 
Line 35: Line 35:
 
* [http://xmpp.org/extensions/inbox/dynamic-forms.html XEP-xxxx: Data Forms - Dynamic Forms]
 
* [http://xmpp.org/extensions/inbox/dynamic-forms.html XEP-xxxx: Data Forms - Dynamic Forms]
 
* [http://xmpp.org/extensions/inbox/eventlogging.html XEP-xxxx: Event Logging over XMPP]
 
* [http://xmpp.org/extensions/inbox/eventlogging.html XEP-xxxx: Event Logging over XMPP]
 +
 +
The following presentation provides information about both the XEPs above, and future planned XEPs relating to the Internet of Things:
 +
 +
* [http://prezi.com/esosntqhewhs/iot-xmpp/ IoT & XMPP]
  
 
== Purpose for re-applying ==
 
== Purpose for re-applying ==

Revision as of 15:16, 6 December 2013

Introduction

My name is Peter Waher, and I'm a cofounder of Clayster. Clayster provides a platform for Internet-of-Things-based services hosted on everything from plug computers to the cloud, and incorporates apart from Internet-of-Things functionality also Semantic Web technology. My interest in XMPP stems from the fact that we're using it for IoT/M2M communications and peer-to-peer(-like) communications in IP-TV applications.

Some links contining information about what we do:

Contact

XMPP Activity

I've spent the last year rallying support for the use of XMPP within IoT and writing XEPs that lay the foundation for interoperable IoT applications using XMPP.

List of XEPs that I've helped write:

There are also two awaiting approval:

The following presentation provides information about both the XEPs above, and future planned XEPs relating to the Internet of Things:

Purpose for re-applying

The main purpose for reapplying for membership is to be able to propose XMPP extensions. Our main interest is to expand xmpp to be used mainly within the following two areas:

  • Sensor networks. This includes among others:
    • Sensor detection, integrated with existing XMPP standards
    • Sensor meta data, capabilities
    • Starting sensor readouts, and asynchronous metering data reporting.
    • Sensor configuratons (i.e. controlling devices for home automation)
    • Interoperability between sensor and meter manufacturers, by providing an accepted open framework for sensor communications.
  • 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.