W3C home > Mailing lists > Public > public-wot-ig@w3.org > March 2017

AW: [TF-LD] Draft charter for Linked Data and Semantic Processing Task Force

From: Anicic, Darko <darko.anicic@siemens.com>
Date: Wed, 1 Mar 2017 15:26:55 +0000
To: Dave Raggett <dsr@w3.org>
CC: "Kis, Zoltan" <zoltan.kis@intel.com>, public WoT IG <public-wot-ig@w3.org>
Message-ID: <506E83C73FFE64489FEDD50EC57ACFC8209DA26F@DENBGAT9EK3MSX.ww902.siemens.net>

Von: Dave Raggett [mailto:dsr@w3.org]
Gesendet: Montag, 27. Februar 2017 20:04
An: Anicic, Darko (CT RDA NEC WOS-DE)
Cc: Kis, Zoltan; public WoT IG
Betreff: Re: [TF-LD] Draft charter for Linked Data and Semantic Processing Task Force

Thanks for the examples, they are most helpful. It sounds like the description of modular behaviours rather than that of the information model for the objects used to expose things to applications.

Procedural scripts are easy for computers to execute, but hard for them to understand and manipulate. Do you envisage machine interpretable recipes, or perhaps consider them for human use only as part of best design practices?

Yes, I envisage machine interpretable recipes. Therefore we need both a recipe model and information model (to annotate ingredients of a recipe).

How would you formalise the recipes?
One possibility to formalize a recipe is to formalize its ingredients and interactions between them.

I can imagine a role for event-condition-action rules, and worked with those in the EU project “Serenoa” which focused on model-based context aware user interfaces.

One should be able to realize event-condition-action rules with recipes. But recipes should not be limited only to ECA rules. We should be able to implement any application template with recipes.

I envisaged a scenario where a service designer (a human) sits at a workstation and comes up with an application that can perform a service like controlling the home environment, adapting to what devices are available in each home. This requires the device descriptions to declare what semantic modules (oneM2M sense) they support. The interfaces exposed by different air conditioners, for example, might differ, but the application would know how to adapt to each, without needing to know in advance the details of each device.

This is more tractable than what you describe as it just requires a way to describe the semantic modules that devices may support and does not require a standard for describing event-condition-action rules or other ways to describe behaviours.

Your example is also interesting. An example with ECA rules was picked by chance. Recipe is based on ingredients and interactions between them. Ingredients should be TD templates or perhaps abstract TDs (suggested by Kajimoto-san). These are similar to semantic modules you mentioned. We don’t need a standard to describe certain type of rules or behaviours. Instead we need just a format to specify a recipe with a semantic model behind.

Best regards,

Best regards,

On 27 Feb 2017, at 17:19, Anicic, Darko <darko.anicic@siemens.com<mailto:darko.anicic@siemens.com>> wrote:

Hi Zoltan,

an example recipe would be: if the temperature gets over threshold, turn the air-condition on. Such a recipe would have 2 ingredients: temperature threshold exceeded (expressed as a TD Event or Property) and air-condition turnOn (e.g., as a TD Action) and interaction between them. In addition it may specify constraints (e.g., on location etc.)  and non-functional-properties that may be important for the discovery.

Recipe can be accompanied/implemented with a script. It is a semantic specification of an application template, and can, for example, be used to discover a script or to find out Things on which the script can be implemented (hosted). Further, a recipe and its script implementation can be easily modified and shared.


Von: Kis, Zoltan [mailto:zoltan.kis@intel.com]
Gesendet: Montag, 27. Februar 2017 17:58
An: Anicic, Darko (CT RDA NEC WOS-DE)
Cc: Dave Raggett; public WoT IG
Betreff: Re: [TF-LD] Draft charter for Linked Data and Semantic Processing Task Force


Could you give an example for a recipe?
Would/could a recipe actually *contain* a script (event handlers, action definitions, request hooks etc)?

On Mon, Feb 27, 2017 at 6:49 PM, Anicic, Darko <darko.anicic@siemens.com<mailto:darko.anicic@siemens.com>> wrote:
Hi Dave,

In addition to the proposed charter I would like to propose one more topic related to a semantic specification of reusable application templates. These templates would enable a quick implementation of new WoT applications, and could be easily shared and extended. They are like recipes for WoT applications.

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.


-----Ursprüngliche Nachricht-----
Von: Dave Raggett [mailto:dsr@w3.org<mailto:dsr@w3.org>]
Gesendet: Mittwoch, 25. Januar 2017 09:45
An: public WoT IG
Betreff: [TF-LD] Draft charter for Linked Data and Semantic Processing Task Force

Please find a draft charter for the proposed Linked Data and Semantic Processing Task Force for discussion in today's Interest Group call.


Note: this is a temporary location as I am expecting that Matthias will have a preferred location for task force charters.

Dave Raggett <dsr@w3.org<mailto:dsr@w3.org>> http://www.w3.org/People/Raggett W3C lead for the Web of things

Dave Raggett <dsr@w3.org<mailto:dsr@w3.org>> http://www.w3.org/People/Raggett

W3C lead for the Web of things

Received on Wednesday, 1 March 2017 15:27:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:10 UTC