[TD-TF] minutes - 28 February 2020

available at:
  https://www.w3.org/2020/02/28-wot-td-minutes.html

also as text below.

Thanks a lot for taking the minutes, Taki!

Kazuyuki

---
   [1]W3C

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

                               - DRAFT -

                             WoT-WG - TD-TF

28 Feb 2020

   [2]Agenda

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

Attendees

   Present
          Kaz_Ashimura, Taki_Kamiya, Tomoaki_Mizushima,
          Ege_Korkan, Daniel_Peintner

   Regrets
          Sebastian

   Chair
          Taki

   Scribe
          TK

Contents

     * [3]Topics
         1. [4]Ac review for Proposed Recommendation Review
         2. [5]Last week's telecon minutes
         3. [6]Online F2F
         4. [7]PR #880
         5. [8]Issue #851
         6. [9]#848
         7. [10]#842
     * [11]Summary of Action Items
     * [12]Summary of Resolutions
     __________________________________________________________

   <kaz> scribenick: taki

Ac review for Proposed Recommendation Review

   Kaz: Ac review for Proposed Recommendation of WoT Thing
   Description has ended.
   ... 17 supports and 2 abstains.
   ... 17 is a good number, I think.
   ... Thank you for you all and your AC reps!

Last week's telecon minutes

   <kaz> [13]Feb-21 minutes

     [13] https://www.w3.org/2020/02/21-wot-td-minutes.html

   Minutes approved.

   <kaz> (note: the date of the minutes was wrong, so Kaz has just
   fixed the date to 21)

Online F2F

   [14]Online F2F wiki

     [14] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_16-19_March_2020,_Online

   Time slot for TD discussion: 6am PST / 9am EST / 2pm CET / 3pm
   EET / 10pm JST; 2h

   Taki: We can discuss agenda items again next week.

PR #880

   <kaz> [15]PR 880

     [15] https://github.com/w3c/wot-thing-description/pull/880

   Ege: Subprotocol fix in JSON-Schema's fix in index.html is
   included in this PR.

   Daniel: We can kick off rendering process automatically.
   ... It is something we can look into.
   ... I had to switch to Linux after I edited on Windows.

   Kaz: Who and when?

   Daniel: I can create an issue.

   Kaz: Please create an issue with lower priority.

   Taki: section 6.4 still contains experimental number 65100.

   <kaz> [16]Changes

     [16] https://github.com/w3c/wot-thing-description/pull/880/files

   Taki: My PR #881 removes experimental numner 65100
   ... I suggest we merge #881 first then #880 after that.

   PR #880 and #881 were merged...

   <kaz> [17]PR 881

     [17] https://github.com/w3c/wot-thing-description/pull/881

   <kaz> [18]PR 880

     [18] https://github.com/w3c/wot-thing-description/pull/880

Issue #851

   <kaz> [19]Issue 851

     [19] https://github.com/w3c/wot-thing-description/issues/851

   Ege: We can update the report for the next version.
   ... Implementation report linked from static TD spec should
   also be static.
   ... Implementation report should be specific to a specific TD
   version.

   Daniel: We could create a new URI.

   Kaz: McCool was interested in adding various features in next
   version. There should be a drastic changes. We can create a
   separate sub-folder (or even a separate GitHub repo) for new
   implementation report with new URI.

   Ege: Implementation report was created by WG.

   Kaz: We can improve implementation report any time.
   ... McCool and Ege can be editors of this document, and people
   contributed to testing can be described in acknowledgement.

   <kaz> [20]fyi, verifiable credentials data model implementation
   report

     [20] https://w3c.github.io/vc-test-suite/implementations/

   Taki: Ege, can you create an issue to fix this point?

   Ege: OK

   Kaz: We can use "contributor" word in addition to authors and
   editors in implementation report.

   Issue #851 was closed.

#848

   <kaz> [21]Issue 848

     [21] https://github.com/w3c/wot-thing-description/issues/848

   Ege: We can close this issue.
   ... In some protocol we can describe this, but for MQTT, we
   cannot do this.
   ... A sort of specification bug.
   ... How do we do this in node wot?

   Daniel: you send a list of names.

   Ege: it is not a good practice. It can be URI variables.

   Daniel: list of names in node wot.

   Ege: problem is when you map into protocol.
   ... consumer has to provide array for read operation.
   ... payload should not be used in HTML get

   Daniel: It is shortcut of reading many property.

   Ege: This operation needs input.

   Daniel: read all - read all properties.
   ... multiple properties is similar.

   Ege: How array is passed?

   Daniel: It still iterates through all property.

   Ege: TD spec says array should be sent.

   Daniel: This feature was added later in Node wot.
   ... not sure how it should be mapped to protocol.

   Taki: Let's keep this issue open for now.

#842

   <kaz> [22]Issue 842

     [22] https://github.com/w3c/wot-thing-description/issues/842

   Kaz: I suggest to keep this issue open till we publish the
   Recommendation.

   Daniel: The working branch still appears to present the issue.
   We need to fix index.template.html.

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [23]scribe.perl version 1.154 ([24]CVS log)
    $Date: 2020/03/04 10:00:33 $

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

Received on Wednesday, 1 April 2020 08:58:51 UTC