AW: Call to discuss interop demo with OCF

Dear Dave

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.

Great! Will it be a WebEx call? I would like to participate.

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.

OCF uses CoAP as primary protocol for thing-to-thing communication. And so far, IoTivity only supports CoAP.

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.

Indeed, prototyping a gateway or proxy servient for OCF sounds like a great exercise to better understand how to complement other platforms and, furthermore, provides an awesome demo to encourage IoT consortia in generel to join.

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.

I would be interested in this work (not sure if I have enough time before the next F2F). Unfortunately, your talk or the slides did not contain any concrete information about your approach for TD or type system. As already mentioned during one of the breakouts, it would be great to see your proposals in the form of TD samples or API descriptions. Could you maybe compile something in the style of the Current Practices document? It definitely does not have to be that verbose, but I would love to see concrete examples of how your solutions look like. I guess, this could also improve the discussion for the working documents and future breakouts.

Best regards
Matthias