Difference between revisions of "Tech pages/IoT Interoperability"

From XMPP WIKI
Jump to navigation Jump to search
Line 1: Line 1:
= Layout=
  [[Tech pages/IoT_systems|Main]] Main page
  [[Tech pages/IoT_XepsExplained|IoT_XepsExplained]] Description of xeps and their interaction
  [[Tech pages/IoT_Examples|IoT_Examples]] Mashup some examples from different industries, help finding new ones
  [[Tech pages/IoT_Support|IoT_Support]] Here we describe who support this and related work that can help you.
  [[Tech pages/IoT_Interoperability|IoT_Interoperability]] How we will keep everything truly interoperable
  [[Tech pages/IoT_XMPP_Process|IoT_XMPP_Process]] How is the process of the xep's and interoperability interfaces managed
  [[Tech pages/IoT_ConstrainedDevices|IoT_ConstrainedDevices]] Going in to the world of restricted devices we need special care.
== Overview ==
== Overview ==
Creating interoperabilty is a crucial thing in the area of Internet of Things. Interoperability is needed on several layers and can either be forced in to specifications and required through certification processes.
Creating interoperabilty is a crucial thing in the area of Internet of Things. Interoperability is needed on several layers and can either be forced in to specifications and required through certification processes.

Revision as of 14:29, 17 April 2013

Layout

 Main Main page
 IoT_XepsExplained Description of xeps and their interaction
 IoT_Examples Mashup some examples from different industries, help finding new ones
 IoT_Support Here we describe who support this and related work that can help you.
 IoT_Interoperability How we will keep everything truly interoperable
 IoT_XMPP_Process How is the process of the xep's and interoperability interfaces managed
 IoT_ConstrainedDevices Going in to the world of restricted devices we need special care.

Overview

Creating interoperabilty is a crucial thing in the area of Internet of Things. Interoperability is needed on several layers and can either be forced in to specifications and required through certification processes.

ZigBee alliance is for example having a certification procedure

When working with open initiatives the only way for this to work is that it is free to join and doesn't cost a fortune to be compliant. And most importantly it is open specifications that is easy to find.

One obstacle is that the specifications must

Interoperability XSF working group

In all networks that combines information from different systems over business and technology borders the crucial thing is to get interoperability. And there is no other way to do this than creating specifications that adds the "common good practices" to make things speak the same language. The interoperability spec will be a moving target with constant elaboration to enable true interoperability between systems

We are therefore planning for a special working group in the XSF organisation that votes a

Interface specification Process

Automatic test bed

Other examples

  • Lonworks and the lonmark organisation
  • The Zigbee smart energy 2.0 and ZigBee IP