[TF-LD] minutes - 23 February 2018

available at:
  https://www.w3.org/2018/02/23-wot-minutes.html

also as text below.

Thanks a lot for taking these minutes, Michael Koster!

Kazuyuki

---

   [1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

                             WoT IG - TF-LD

23 Feb 2018

Attendees

   Present
          Darko_Anicic, Kaz_Ashimura, Aparna_Thuluva,
          Danh_Le_Phuoc, Darko_Anicic, Michael_Koster, Taki_Kamiya

   Regrets

   Chair
          Darko

   Scribe
          mjkoster, kaz

Contents

     * [2]Topics
         1. [3]WebEx coordinate
         2. [4]Semantic integration for the plugfest
         3. [5]Thing Description Template Generation -Aparna
         4. [6]Next meeting
     * [7]Summary of Action Items
     * [8]Summary of Resolutions
     __________________________________________________________

WebEx coordinate

   scribenick: kaz

   kaz: wondering about the webex setting because there are two
   WebEx reservations for the LD call now and it's confusing
   ... can remove the old bi-weekly reservation
   ... and will update the LD wiki with the new webex coordinate

Semantic integration for the plugfest

   <kaz> scribenick: mjkoster

   darko: 2 points on semantic integration
   ... Aparna and darko have been working on shape constraints
   ... Victor has made some updates to iotschema.org
   ... points from previous calls on integration of other
   ontologies ssn, sosa for example FoI

   <inserted> scribenick: kaz

   koster: how we could extend the semantic integration?
   ... device installation, etc.
   ... basically annotate capability
   ... related to features of interest
   ... illumination of rooms
   ... enhancing semantic integration on discovery
   ... how to do it?
   ... we can put in triples
   ... how to add features of interest?
   ... brightness of light
   ... changing illumination level of room

   darko: extend iotschema.org and create TD template
   ... concrete template for devices
   ... can be achieved for devices we present
   ... what to be prepared for the upcoming plugfest?

Thing Description Template Generation - Aparna

   <kaz> -> slides tbd

   <kaz> scribenick: kaz

   aparna: (goes through her slides)
   ... [Thing Description Modeling Overview]
   ... [iot.schema.org Capability]
   ... interaction pattern in detail here
   ... interaction's data
   ... [SHACL Shapes for Level Capability]
   ... Thing Capability Constraints
   ... CurrentLevelShape
   ... LevelDataShape
   ... distinguish things which have same capability
   ... [W3C WoT Thing Description]
   ... [Modeling of Automation System Things]
   ... implementation available on GitHub
   ... SHACL and Shapes
   ... [Work Plan]
   ... online version of TD generator
   ... iot.schema.org capabilities
   ... shape constraints for iot.schema.org capabilities

   darko: the idea is trying to provide online mechanism
   ... specify capability
   ... local code you can run yourself

   <inserted> scribenick: mjkoster

   darko: please try to use the tool
   ... the tool will generate a TD which contains the semantic
   annotation
   ... the TD is generated top-down from the semantic definitions

   kaz: do you plan to make it available to the plugfest
   participants?

   darko: yes, that is the plan
   ... we can enable everyone to create TDs using the tool

   kaz: is it related to recipes?

   darko: recipes are one level above, for orchestration of a few
   things
   ... in this tool, you choose a capability from a list and the
   TD is generated using the selected capabilities

   kaz: so a TD authoring tool?

   darko: yes

   danh: do you have an example of TD using this annotation vs.
   one which doesn't
   ... how can other abstract features be included?

   darko: iotschema has 3 categories of annotation: capability,
   interaction, and data
   ... in order to generate a complete TD, we are working on
   mapping from shapes languages to json schema
   ... tracking changes that are still in progress in the schema
   language part of TD

   danh: some example that can be reused with cut-and-paste
   ... also to demonstrate the value of the current annotation
   plus future ideas like FoI
   ... for example discovery could use feature and target entity
   subtype
   ... if we could annotate TDs and use in discovery to validate
   the use case
   ... use case of a client that does some reasoning

   darko: there are some simple use cases around semantic
   equivalence that could be possible
   ... like device substitution

   aparna: example of air conditioner TD generated from a template
   ... has annotations for the 3 semantic categories.. capability,
   interaction, and data

   darko: if no more questions, Victor can present

   victor: updating the ontology
   ... fixing the broken stuff in iotschema.org

   <DarkoAnicic> Schema page on iotschema.org created:
   [9]http://schema.org/docs/schemas.html

      [9] http://schema.org/docs/schemas.html

   victor: added a hierarchy, so now it is possible to navigate
   the classes
   ... is there a shape constraint for capabilities?

   darko: it's not clear if there is just one shape for all
   instances of e.g. air conditioner
   ... for example there may need to be an interaction with either
   a property shape or an action shape, depending on the instance
   ... any questions with respect to Victors update

   danh: is there a reason to have e.g. temperature at the top
   level rather than something generic like sensing with a
   semantic hierarchy
   ... for testing
   ... how do we add meaning?

   darko: the capability pattern has simple level structure

   <inserted> scribenick: kaz

   koster: definition level and controlling level
   ... some open issues there

   <DanhLePhuoc> [10]https://sweet.jpl.nasa.gov/

     [10] https://sweet.jpl.nasa.gov/

   <inserted> scribenick: mjkoster

   danh: want to connect the capability to real world meaning in
   terms of observation
   ... for example, illuminance
   ... humans don't need such a rigorous definition but we do for
   machine understanding
   ... next step is how to come up with a showcase semantic
   integration based on what we have

   <DarkoAnicic> Material for Semantic Integration:
   [11]https://github.com/w3c/wot/tree/master/plugfest/2018-prague
   /semantic%20integration

     [11] https://github.com/w3c/wot/tree/master/plugfest/2018-prague/semantic
integration

   danh: to illustrate the nice features also to give an
   implementation guide

   darko: we have defined some scenarios as a place to start, or
   we can add new scenarios
   ... these scenarios are based on the devices we expect to see
   at the Plugfest
   ... please look at these and make suggestions
   ... scenarios, capabilities, TDs, and recipes are the focus
   areas

   danh: what are the working assumptions, do we just bring things
   and TDs to describe them

   darko: TDs people bring are registered in a thing directory
   ... clients discover things it wants to orchestrate or interact
   with

   danh: do you assume REST API?

   darko: there is a W3C WoT REST API reference implementation in
   the open source project node-wot

   [12]https://github.com/thingweb/node-wot

     [12] https://github.com/thingweb/node-wot

   danh: location, type of sensor, Feature of Interest?

   darko: please look at the materials and contribute

Next meeting

   darko: next week Darko will not be available, so we can meet
   again in 2 weeks unless we have someone to organize next week
   ... please send email if we do
   ... thank you, meeting adjourned

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [13]scribe.perl version
    1.152 ([14]CVS log)
    $Date: 2018/02/23 16:56:18 $

     [13] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [14] http://dev.w3.org/cvsweb/2002/scribe/

Received on Friday, 23 February 2018 17:00:41 UTC