Hi Dave,

IoTivity currently supports only CoAP. The HTTP mapping defined in OCF is not yet implemented.

I think there is some experimental work ongoing towards a mapping over MQTT. IoTivity supports the use of CoAP over BT(LE), which is not specified in OCF yet.

If you have issues to get IoTivity started I can help you, if you don't mind i join the call with Ravi. The web site documentation needs to be updated. The wiki has a more up-to-date state of documentation. Please have a look on  wiki.iotivity.org

Best Regards,

 

Dr.techn. Markus Jung

IoT, IoTivity, OIC | IoT Lab

Software R&D Center | Samsung Electronics Co., Ltd

Mobile +82 10 3304 8502

markus.jung at samsung.com

------- Original Message -------

Sender : Dave Raggett<dsr@w3.org>

Date : Apr 21, 2016 02:12 (GMT+09:00)

Title : Call to discuss interop demo with OCF

 

I am planning a call with Ravi Subramaniam at 9am PST on Friday 29th April.  (5pm UK, 6pm across Western Europe).   The aim is to produce a demo for how to integrate OCF into the Web of Things.  He pointed me at the following sites:

    http://www.oneiota.org/   and   https://www.iotivity.org/documentation

From this, I see that IoTivity supports CoAP and HTTP as protocols, and the website describes how to discover resources, how to query the resource state, how to update the resource state, and  how to observe the resource state.

I imagine creating an open source gateway that exposes selected  IoTivity resources as “things”. For this we would need metadata for describing the data and interaction models exposed to applications, for the choice of communications patterns, and for the information needed for interoperating with the platforms and protocols, including security settings.

The One IoTa site provides a suite of RAML and JSON based descriptions of resources that we would start from. I am curious about how OCF have approach MQTT and Bluetooth and look forward to asking Ravi about that.

I am working on a C++ based gateway, and this would be a great way to ensure that the design is modularised appropriately when it comes to adding support for new platforms.  We would also need some instances of devices that implement the OCF specifications, and this is what I am hoping Intel will be able to provide.

Of course it would be good to collaborate with other members of the Web of Things Interest Group, e.g. on the initial work on Thing Descriptions, and if appropriate on coding the gateway itself.

Note that I have slightly different idea of the type system and representation of Thing Descriptions than given in the current draft of the current practices document. See my implementation report slides from the Montreal face to face. In particular, this should make it easier to support nested properties, late binding of things as properties and so forth.

If anyone else would like to participate in this work and next week’s call with Ravi please let me know.

   Dave Raggett <dsr@w3.org>