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

[TF-LD] minutes - 21 July 2017

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Sat, 22 Jul 2017 00:23:37 +0900
Message-ID: <CAJ8iq9Xe-+JiOxaN+4APdjYTKicNdD5BDN+3uC=j1WDaZA6Cug@mail.gmail.com>
To: Public Web of Things IG <public-wot-ig@w3.org>
available at:
  https://www.w3.org/2017/07/21-wot-minutes.html

also as text below.

Thanks for taking these minutes, Danh and Michael!

Kazuyuki

---

   [1]W3C

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

                               - DRAFT -

                             WoT IG - TF-LD

21 Jul 2017

   [2]Agenda

      [2] https://www.w3.org/WoT/IG/wiki/IG_Linked_Data_and_Semantic_Processing_WebConf#Agenda

   See also: [3]IRC log

      [3] http://www.w3.org/2017/07/21-wot-irc

Attendees

   Present
          Kaz_Ashimura, Danh_Le_Phuoc, Darko_Anicic,
          Michael_Koster

   Regrets
          Maria_Poveda, Achille_Zappa

   Chair
          Darko

   Scribe
          DanhLePhuoc, mjkoster, kaz

Contents

     * [4]Topics
         1. [5]f2f recap and discussion on discovery
     * [6]Summary of Action Items
     * [7]Summary of Resolutions
     __________________________________________________________

f2f recap and discussion on discovery

   <kaz> scribenick: DanhLePhuoc

   <kaz> [8]Dusseldorf f2f agenda

      [8] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_9-13_July_2017,_Düsseldorf,_Germany#Agenda

   <kaz> [9]Dusseldolf f2f minutes

      [9] https://www.w3.org/2017/07/09-13-wot-minutes.html

   we're currently have 3 tracks in LD task forces but only the
   outcomes of two tracks were presented at the F2F

   there are two streams of on vocabularies

   the first one is on advocating in bridging ontologies

   <DarkoAnicic> iot.schema.org :
   [10]http://www.w3.org/2017/07/wot-f2f/slides/iotschema-wotf2f.p
   df

     [10] http://www.w3.org/2017/07/wot-f2f/slides/iotschema-wotf2f.pdf

   and another one is leaning towards building by iot.schema.org
   leading by michael koster

   there're several separated efforts in annotating
   semantics/ontologies to TD

   but quite some of them have some difficulties in dealing with
   ontologies and SW technologies and lack of devices during F2F

   right now there's no use of TD repository because there's no
   user interface to query/discover the repository to find usable
   things

   <inserted> scribenick: mjkoster

   danh: provide a json interface for queries?
   ... basic vocabulary to discover things

   darko: doing semantic queries was the difficulty

   mkoster: maybe we need a template based discovery system where
   you fill out a TD type template to express what you need
   ... looks like part of a recipe

   darko: may be an approximate match using a recipe to compose a
   possible solution from different ingredients
   ... servients register TDs to the repository and can be
   discovered "bottom-up" but it doesnt work very well
   ... top-down may be a better solution
   ... using recipes
   ... servient to servient

   danh: who will create the recipes?

   darko: created by humans who want to create an application

   danh: will we put this into the best practices?

   darko: we should look at use cases for discovery and decide
   what the better pattern is
   ... top-down or bottom up... the current pattern is not working
   because it is difficult for users to form sparql queries

   danh: turn recipes into sparql queries or make simple js
   language

   darko: what kind of discovery API is needed?

   kaz: what is the target? local area? could use mDNS/bonjour on
   a local network
   ... do we need some new 21st century DNS for web of things?

   danh: we also need to think about discovery above the network
   layer

   kaz: is it the assumption that TD repository contains all of
   the addresses?

   danh: yes, everything will be in TD

   kaz: there may be some use for network discovery, finding a
   link

   <kaz>
   [11]https://www.w3.org/TR/2017/NOTE-mmi-mc-discovery-20170202/

     [11] https://www.w3.org/TR/2017/NOTE-mmi-mc-discovery-20170202/

   <inserted> scribenick: kaz

   kaz: think there are several states, e.g., IDLE, AVAILABLE, and
   we need to think about how to handle those states using
   management thing api or LD recipe
   ... from my viewpoint, "TD Recipe" is kind of high-level
   abstraction of Management Thing APIs.

   <inserted> scribenick: DanhLePhuoc

   DarkoAnicic: which task forces are managing the discovery
   requirements?

   TD TF is discussing a bit on that
   [12]https://w3c.github.io/wot/current-practices/wot-practices.h
   tml#td-discovery

     [12] https://w3c.github.io/wot/current-practices/wot-practices.html#td-discovery

   [13]https://github.com/thingweb/thingweb-repository/

     [13] https://github.com/thingweb/thingweb-repository/

   <inserted> scribenick: kaz

   kaz: Darko, are you planning to collaborate with TD guys and
   Management Thing guys?

   darko: yes, would like to generate some proposal and bring that
   to the main call, e.g., maybe the week after.

   [ adjourned ]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [14]scribe.perl version
    1.152 ([15]CVS log)
    $Date: 2017/07/21 15:15:32 $

     [14] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [15] http://dev.w3.org/cvsweb/2002/scribe/
Received on Friday, 21 July 2017 15:24:44 UTC

This archive was generated by hypermail 2.3.1 : Friday, 21 July 2017 15:24:45 UTC