Difference between revisions of "Tech pages/IoT Interoperability"
|Line 1:||Line 1:|
= Layout =
== Overview ==
== Overview ==
Latest revision as of 17:48, 1 November 2013
Links to important documents relating to Internet of Things and XMPP:
- Main: Main page.
- XEPs Explained: Description of xeps and their interaction. If you are new to XMPP & Internet of Things, you should read this.
- 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 Security: This is one of the strongest benefit of using XMPP.
- IoT XMPP Process: How is the process of the xep's and interoperability interfaces managed.
- IoT Constrained Devices: Going in to the world of restricted devices we need special care.
- IoT Local Environment: When dealing with home automation or a local network we need serverless or a local server configuration.
- IoT Http over XMPP: This extension extends the web to include devices in XMPP networks.
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.
Some examples of interoperability
The problem is that to finance these organizations they must take a member fee and the certification processes is very costly for companies. This also implies that they need to be more or less closed (you have t
This initiative in the XSF must be free and open but yet create a defined way to
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
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.
We are therefore planning for a special working group in the XSF organisation that votes on the changes in the interface specifications.
This will involve a separate mailing list
Interface specification Process
Automatic test bed
To be interoperable and to verify functions testing is crucial therefore we intend to setup an interoperable testbed with a interoperable bot that you can connect to and run an interoperable test.
In all technical protocols there are interoperability efforts unfortunately they often are to close to the physical protocol they are working with
- ZigBee alliance Defining all layers of the OSI stack for wireless sensor networks and adding "profiles" for smart energy
- Upnp Forum
- dlna working group Specifications for printers, Tv sets to be interoperable
- LonMark an initiative to standardize equipment connected to the lonworks communication system
- The Zigbee smart energy 3.0 and ZigBee IP this is one of the closest to actually leave the physical layer