W3C home > Mailing lists > Public > public-wot-wg@w3.org > September 2020

[wot-ig/wg] minutes - 26 August 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 07 Sep 2020 17:32:09 +0900
Message-ID: <87lfhmkmwm.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:

also as text below.

Thanks a lot for taking the minutes, Jennifer!



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

                               - DRAFT -


26 Aug 2020


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


          Kaz_Ashimura, Jennifer_Lin, Cristiano_Aguzzi,
          Kunihiko_Toumura, Michael_Lagally, Daniel_Peintner,
          Michael_McCool, Ege_Korkan, Tomoaki_Mizushima,
          Ryuichi_Matsukura, David_Ezell





     * [3]Topics
         1. [4]Prev minute
         2. [5]Upcoming events
         3. [6]Upcoming calls
         4. [7]Publication schedule
         5. [8]TF Reports
         6. [9]AOB
     * [10]Summary of Action Items
     * [11]Summary of Resolutions

   <kaz> scribenick: jennifer

Prev minute

   <inserted> [12]Aug-19

     [12] https://www.w3.org/2020/08/19-wot-minutes.html

   McCool: Going over past minutes on 8/19

   <kaz> ('TS' fixed as 'Typescript')

   McCool: publishing minutes

Upcoming events

   McCool: Upcoming events reminder: API Spec Conference (Ege

   Singapore Geospatial Week, TPAC 2020 Joint Meetings and Smart
   Cities Week

Upcoming calls

   McCool: PlugFest call today (organizational)
   ... TD call is canceled
   ... Architectural Call confirmed from mlgally
   ... Use case call next week
   ... Need to send an ITU-T Liaison email to join

Publication schedule

   McCool: Scripting call today: possible delay for WoT Scripting
   API by end of Sept 2020
   ... WoT Thing Description 1.1 is the highest priority
   ... Then updating WoT Architecture
   ... Intended to do a 2nd version of Architecture after the

   Lagally: Planning to have the first skeleton of Architecture by

   McCool: Use case document, when first draft?

   Lagally: October time frame
   ... WoT Use Cases Note is an IG Note

   Daniel: Prefer to postpone publication so there's a better
   aligned implementation
   ... Should be done by end by Sept

   McCool: TPAC
   ... ToDo: Work on TPAC WoT IG/WG Agenda items
   ... not sure we can get all the joint meetings on one day (Oct

   <inserted> [13]Joint meeting candidates

     [13] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_October_2020#Collaborations

   McCool: Collaborations, people should have meetings on the
   initial stage of collaborations
   ... Waiting for responses from other groups
   ... Doubt we'll have all these collaboration meetings on the
   ... if you see other group sessions you want to organize, feel
   ... We should create issues on issue trackers for each working

   <McCool> Use label like "WoT Joint Meeting"

   <McCool> and create another issue under "wot" and link them to
   each other

   McCool: (To Kaz) When Sebastian gets back we should put our
   heads together to optimize our procedure for tagged items

   Lagally: We should proceed with the explainers we have and add
   deltas, a combined explainer document would require additional
   coordination etc.

   McCool: yeah, let's start with a delta
   ... Put creation of explainers on to the agendas
   ... Plan to review the explainers on the TPAC session
   ... Look at TPAC agenda
   ... Proposed Topics per task force
   ... Architecture, Scripting, Security, Discovery, Plugfest
   ... Thing Description
   ... Collaboration Report: ITU-T, One DataModel, WISHI/IETF,
   Joint Meetings
   ... Tutorials
   ... Web Page Design
   ... Ideally there would be a linked issue tracker for all the
   above issues

   Kaz: what about Use cases and Requirements?

   McCool: Good point. BTW, regarding Requirements, which would be
   better having a document for Use Cases and Requirements? or
   Requirements as part of the Architecture?

   Lagally: Table for discussion tomorrow

   McCool: Each task force to fill in, ideally with links to
   issues and time estimates and proposed speaker

TF Reports

   McCool: TF Reports

   <kaz> [Scripting]

   Daniel: had discussion with a guest form TUM. still need to
   improve the API design. also need implementations. removing
   write all, but we have read all/read multiple

   <inserted> [Security]

   McCool: Proposal for Security we're ready to merge soon
   ... appropriate to make all the fields in OAuth2 mandatory?
   ... Do we make things like authentication server optional?
   ... And if we do, are they authoritative?

   <inserted> [Discovery]

   McCool: Slowly making progress on the spec for Discovery
   ... Still working on Discovery API spec -- in flight
   ... Discovery semantic API is under heavy construction
   ... json path vs xpath
   ... leaning towards xpath

   Daniel: plan to standardize json path

   McCool: Concern is the timing if it can get done in time
   ... for now we'll just use xpath and SPARQL

   <inserted> [Marketing]

   McCool: Marketing - captured various responses to the animator
   ... Homework to do to collect TDs
   ... Daniel agreed to do a TD and node-wot temperature script

   Daniel: I've contacted Christian Glomb about the slides, but
   the content was actually provided by Sebastian. On the other
   hand, Cristiano is helping me generate node-wot scripts.

   McCool: Change from winemaker to vegetable grower
   ... We should get our act together on tutorials


     [14] https://github.com/w3c/wot-marketing/tree/master/tutorials

   <inserted> [PoC]

   McCool: PoC: Hijacked PoC and talked about the Smart Cities
   ... Not just WoT, everything related to Smart Cities
   ... [PlugFest/Test]/Testing: met last week
   ... Need to do more work today to define scenarios

   <inserted> [TD]

   McCool: Thing Description -- no call
   ... Will be call next week

   <inserted> [Use Cases]

   McCool: No calls
   ... for Use Cases

   <inserted> [Architecture]

   McCool: Architecture -- no calls - there will be a call


   Kaz: regarding the 3-min video on WoT asked by Ralph, it seems
   his intention is our own explaining the summary on what WoT is
   like rather than the explainer animation video. We can use
   WebEx or Zoom to record a session for that purpose.

   <inserted> [main call adjourned, take an 8-minute break before
   the PlugFest call]

Summary of Action Items

Summary of Resolutions

   [End of minutes]

    Minutes manually created (not a transcript), formatted by
    David Booth's [15]scribe.perl version ([16]CVS log)
    $Date: 2020/08/31 07:02:03 $

     [15] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [16] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 7 September 2020 08:32:14 UTC

This archive was generated by hypermail 2.4.0 : Monday, 7 September 2020 08:32:14 UTC