[TF-LD] Comments on the Linked Data Task Force Charter

[danicic]

In addition to the topics from the proposed charter I would like to propose one more: Recipes.

Recipe

Recipe is a semantic specification of a reusable application template. It enables a quick implementation of new WoT applications, and it can be easily shared and extended.

Recipe specifies ingredients and interactions between them. Ingredients are Thing Description Interaction Patterns (events, properties and actions), and interactions are semantic links between them. Constraints and Non Function Properties are specified in Recipes too. Recipe can be published and discovered by using Linked Data principles. Further on, one can use semantic discovery to find out Things that match ingredients of a Recipe. A Recipe should be implementable in a straightforward manner with the WoT Scripting API.

[draggett]

I see recipes as a general term that covers two levels of modularisation. IoT standards suites often specify devices as a composition of separately specified interface definitions, e.g. OCF defines devices in terms of sets of resources, whilst oneM2M defines devices in terms of modules. This is syntactic modularization. Real or virtual devices can also be defined at a semantic level in terms of a composition of semantic models that the device implements. Both kinds of modularization are valuable.

We therefore need to work on the means to specify reusable syntactic and semantic modules for WoT applications. A recipe is then a description for combining modules.

At the syntactic level, we can specify a relationship between a device and the modules it is based upon via an imports predicate that imports the triples from the graph it links to. We can use the rdf:type predicate to indicate that a thing, or property, etc. is an instance of class. The link to the class can be dereferenced to obtain the semantic constraints on instances of that class. Linked Data shapes could be used for validation of the constraints. We could also exploit OWL ontologies, but need to be careful to keep the approach simple for non experts to grasp.

I think we're able to close this issue, but if not please explain why.

[egekorkan]

I am guessing that this has resulted in the following publication:
https://www.researchgate.net/publication/319276546_Recipes_for_IoT_Applications

Closing