[wot-ig/wg] minutes - 3 April 2019

available at:
  https://www.w3.org/2019/04/03-wot-minutes.html

also as text below.

Thanks a lot for taking notes, Sebastian!

Kazuyuki

---

   [1]W3C

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

                               - DRAFT -

                               WoT-IG/WG

03 Apr 2019

   [2]Agenda

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

Attendees

   Present
          Daniel_Peintner, Ege_Korkan, Kaz_Ashimura,
          Kunihiko_Toumura, Michael_Koster, Michael_Lagally,
          Sebastian_Kaebisch, Taki_Kamiya, Toru_Kawaguchi

   Regrets
          McCool, Matthias

   Chair
          Kaz

   Scribe
          kaz, sebastian

Contents

     * [3]Topics
         1. [4]Agenda
         2. [5]Wot workshop
         3. [6]Wide reviews for TD and Architecture including TAG
            review
         4. [7]TF report - Binding Templates
         5. [8]OneDM updates from Koster
         6. [9]AOB?
         7. [10]Some more discussion on workshop?
     * [11]Summary of Action Items
     * [12]Summary of Resolutions
     __________________________________________________________

   <kaz> Chair: kaz

   <kaz> scribenick: kaz

Agenda

   <scribe> Agenda:
   [13]https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda

     [13] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda

   Kaz: koster, update on one data model?

   Koster: can do that

Wot workshop

   Sebastian: want to start discussion about demo on the openday
   ... we'll organize a place for demo
   ... would like to know who is bringing your demos
   ... to see the requirement
   ... will set up a separate wiki page to collect information
   ... short explanation about your demo, etc.
   ... cross-domain scenario?
   ... our spec draft works well
   ... we should be able to set up a cross-domain demo
   ... maybe GitHub readme or W3C wiki

   Lagally: we used to have a plugfest call after the main call
   ... we might want to think about integration scenario
   ... need enough time/preparation
   ... we can replicate what we've been doing for our plugfest
   ... requirements for services, structure of TDs
   ... let's reuse the plugfest/testfest setting

   Sebastian: make sense
   ... we have 4 weeks for preparation

   Lagally: we should start soon
   ... e.g., next week

   Sebastian: a bit worried to have too many calls

   Kaz: we can start to collect interested people
   ... and then copy plugfest resources from the plugfest/testfest
   directories

   Lagally: good point
   ... we need time for dry-run as well

   Sebastian: please note that setting can be done on Friday, June
   1st

   Kaz: suggest you put all the logistics information on the
   readme page
   ... we can have some more discussion separately, e.g., after
   this call during the testfest slot, if people are ok

   Lagally: we can do so
   ... one more question
   ... CfP is online
   ... EasyChair is available
   ... so would encourage people to submit something
   ... good to know who is planning to submit a paper/statement

   Kaz: is everybody interested?

   Ege: yes

   Sebastian: some of German companies are planning including
   Siemens

   Lagally: Oracle as well

   Kunihiko: would like to prepare some presentation but maybe a
   bit difficult with the current deadline

   Kaz: maybe you can submit an updated paper later

   Koster: will be presenting my work

   Taki: will work with Matsukura-san for that

   Tomoaki: will submit a paper too

   Toru: will prepare something

   Zoltan: haven't discuss it yet, but would like to

   Lagally: good news :)

Wide reviews for TD and Architecture including TAG review

   <scribe> scribenick: sebastian

   Kaz: we need clearification about TD serializiation
   ... we should explain the simple and full form of TD
   ... ivan suggested to use json-ld + profile mediatype

   <inserted> scribenick: kaz

   Sebastian: comment on media type
   ... one TD format and TD own media type
   ... should have one only serialization
   ... introduction section misses clear description, so would
   like to work on the clarification

   Kaz: as I mentioned before, there is a specific guideline to
   register mediatypes for W3C specs

   <kaz> [14]media type registration procedure

     [14] https://www.w3.org/2002/06/registering-mediatype2014

   Kaz: regarding the media type for TD, will talk with Ralph from
   the W3C Team as well
   ... regarding wide reviews for TD in general, will talk with
   the team contacts for TAG, JSON-LD, i18n and a12y, and ask them
   for reviews
   ... regarding architecture, we don't need review by JSON-LD.
   right?

   Lagally: right

   Sebastian: discussion on how to deal with "@context"
   ... we should think about some description about it rather than
   using "simple TD" vs "full TD"
   ... some of the developers don't want to use semantic
   information like "@context"
   ... missing that kind of semantic information should be
   acceptable
   ... would like to talk about that point during the TD call on
   Friday, April 5

   Lagally: btw, it might make sense if we ask JSON-LD people to
   review the architecture spec as well

   Kaz: we can try to ask them if we want :)

   Lagally: more reviews of the specifications would be helpful

   Kaz: I can mention the Architecture draft as well when I ask
   the JSON-LD WG for review

   Lagally: there is a link to the architecture spec from TD.
   right?

   Sebastian: yes

   Lagally: and link from the TD explainer too?

   [15]Architecture explainer

     [15] https://github.com/w3c/wot-architecture/blob/master/proposals/WoT
Architecture Explainer.md

   [16]TD explainer

     [16] https://github.com/w3c/wot-thing-description/blob/master/explainer/Explainer.md

   Kaz: confirms that TD explainer has a link to the Architecture

TF report - Binding Templates

   Koster: planning to update the binding templates document

   Kaz: good to publish an updated Note :)

OneDM updates from Koster

   <inserted> scribenick: sebastian

   Koster: oneDM is a broad liaison between multiple SDOs,
   corporations, and invited experts
   ... driving toward common IoT data model that all can use
   ... supports patterns
   ... abstract definitions with seperate protocol binding
   ... separate data types
   ... compatible with TD meta model with properties, actions, and
   events
   ... decide on JSON representation
   ... support multiple namespaces
   ... + ODM namespaces for agreed common definitions
   ... Process: 1. create presentation, 2. Prototypes, 3. ?
   ... status: working on meta-model + representation format
   ... next f2f in May
   ... there are weekly meetings (Wed 7am PDT)
   ... Michael_K has a proposal for OneDM based on TD
   ... shows many samples

   Lagally: can you provide the slide?

   Koster: is on github

   Mihcael_L: there is an example of extensions

   Kaz: the oneDM people want to use JSON based format. How they
   want to use the namespaces?

   Koster: using scoping for it
   ... google call it pathing
   ... linking is very important

   <kaz> scribenick: kaz

   Sebastian: so many feature points mentioned here
   ... similar to the TD and binding templates
   ... are they aware of our WoT work?
   ... would like to have discussion with them

   Koster: mainly OCF and Zigbee guys
   ... I mentioned schema.org, etc.
   ... Matthias also mentioned WoT work
   ... definition language looks more like schema
   ... if we could put TD between the high-level definition and
   the low-level definition, would be great

   Kaz: think it would make sense to invite them to our main call
   and the workshop in June

   Sebastian: good point

   Lagally: in this discussion, any functional gap we should
   consider?
   ... require extensions or don't work with our mechanism?

   Koster: if they can agree to use JSON-LD, that would be good
   ... template thing might make sense
   ... would think about the template
   ... might become an object

AOB?

   (none)

Some more discussion on workshop?

   Sebastian: not available today

   Kaz: let's have some more discussion after the TD call on
   Friday, April 5

   Lagally: ok
   ... Sebastian, please put the information on demo logistics
   together

   Kaz: Sebastian, you can copy the items/sections from the
   previous plugfest/testfest pages
   ... and we can fill the fields based on the discussions with
   the group participants

   Sebastian: let's discuss the details on Friday

   Toru: when will the PC call start?

   Kaz: April 15th
   ... because there will be the AC meeting next week
   ... Sebastian will send a message about that to the PC list

   Sebastian: McCool will make a lightning talk at the AC meeting
   ... and he is expected to mention the workshop as well

   Kaz: will check with him

   Lagally: can everybody bring your demo to the workshop, e.g.,
   the ones you showed in Lyon during TPAC?

   Kaz: would be a good starting point
   ... let's check that point as well on Friday
   ... everybody, please check within your company to see if your
   demos will be available in June in Munich
   ... any other questions?

   (none)

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [17]scribe.perl version 1.154 ([18]CVS log)
    $Date: 2019/04/07 12:54:17 $

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

Received on Sunday, 7 April 2019 13:02:43 UTC