The HyperCat specification allows Internet of Things clients to discover what data an IoT server has available. It is built on the same Web standards that are now common for that interface, i.e. HTTPS, REST/HATEOAS, JSON. Have a look at http://www.hypercat.io/ and http://wiki.1248.io/doku.php?id=hypercat.
The Haystack project wants to standardize semantic modeling in the building area.
Finally, The IoT Information Model Repository project (IoTIMR) wants to push standardization of so called information models. An information model is an abstraction of a device. This means it abstracts the status, the properties and the functionalities of such a device.
Look at https://projects.eclipse.org/proposals/iot-information-model-repository
However,these 3 initiatives are standardization silos.
I strongly suggest a collaboration between the hypercat project and the Haystack project.
david menga Fri 26 Sep 2014
Hello Haystack community,
The HyperCat specification allows Internet of Things clients to discover what data an IoT server has available. It is built on the same Web standards that are now common for that interface, i.e. HTTPS, REST/HATEOAS, JSON. Have a look at http://www.hypercat.io/ and http://wiki.1248.io/doku.php?id=hypercat.
The Haystack project wants to standardize semantic modeling in the building area.
Finally, The IoT Information Model Repository project (IoTIMR) wants to push standardization of so called information models. An information model is an abstraction of a device. This means it abstracts the status, the properties and the functionalities of such a device.
Look at https://projects.eclipse.org/proposals/iot-information-model-repository
However,these 3 initiatives are standardization silos.
I strongly suggest a collaboration between the hypercat project and the Haystack project.
You can contact me to know more : [email protected] or [email protected]
Best regards
David