W3C home > Mailing lists > Public > public-wot-wg@w3.org > July 2021

[TD-TF] minutes - 19 May 2021

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 12 Jul 2021 17:02:37 +0900
Message-ID: <87k0lw2c4i.wl-ashimura@w3.org>
To: public-wot-wg@w3.org
available at:

also as text below.

Thanks a lot for taking the minutes, Taki!



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

                             íV DRAFT íV
                             WoT-WG - TD-TF

19 May 2021

   [2]Agenda. [3]IRC log.

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

      [3] https://www.w3.org/2021/05/19-wot-td-irc


          Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan,
          Kaz_Ashimura, Klaus_Hartke, Michael_Koster,
          Michael_McCool, Taki_Kamiya, Tomoaki_Mizushima



          kaz, taki, TK


    1. [4]Minutes
    2. [5]Debriefing from the main call
    3. [6]PR# 1147
    4. [7]Issue 1044

Meeting minutes


   <kaz> [8]May-12

      [8] https://www.w3.org/2021/05/12-wot-td-minutes.html

   Taki: minutes were accepted from last week.

  Debriefing from the main call

   <kaz> [9]TD discussion during the main call

      [9] https://www.w3.org/2021/05/19-wot-minutes.html#t09

   McCool: abstract intro and change log were merged.

   McCool: made correction to abstract.

   McCool: changed wording mistake.

   McCool: basically ready waiting for sebastian's change to

  PR# 1147

   <kaz> [10]PR 1147 - PR including the comments

     [10] https://github.com/w3c/wot-thing-description/pull/1147

   Kaz: there are only two lines mentioning "features at-risk" but
   is that OK?

   McCool: At risk part needs to be taken care of before CR.

   Kaz: this is for an updated WD not CR, so should be OK

   Taki: PR# 1147 was merged.

   Kaz: my only question is relationship between this PR's update
   and the candidate draft

   [11]candidate draft for updated WD

     [11] https://github.com/w3c/wot-thing-description/tree/wd-update-candidate

   Kaz to check if the spec is clean on wd-update-candidate2

   Daniel: I still see broken links in the spec.

   Kaz: we can check in static version first, then fix broken

   <kaz> [12]Link checker

     [12] https://validator.w3.org/checklink

   Kaz: DP can fix links directly on the branch.

   Daniel: Should it be which branch?

   Kaz: ideally to both branches, but you can create yet another
   branch for publication like Taki did for "wd-update-candidate2"

   Daniel: I will ping others after fixing links.

   McCool: Fix rendered version, and merge the changes back in.

   Kaz: Please take a look at possible errors, and can discuss
   what to do else on Friday.

   Use case document clean up was already done by Kaz, but PR to
   be done for applying the changes back to the respec draft.

  Issue 1044

   <kaz> [13]Issue 1044 - Adding term to indicate a stream of data

     [13] https://github.com/w3c/wot-thing-description/issues/1044

   McCool: Chunked transfer is needed in directory use case.

   McCool: HTTP use case needs to be able to handle it.

   Ege: devices that generates big data can choose to output as a

   McCool: HTTP 1.1 and 2.0 have different mechanisms.

   McCool: images and videos are big, and videos are unlimited

   Koster: chunking can be used on HTTP, but chunking itself does
   not mean streaming.

   McCool: pagination and chunking are different.

   McCool: chunking does not mean structure.

   Cristiano: HTTP provides chunking. if protocol does not support
   chunking, then server still want to make chunks, so streaming
   can be useful.

   McCool: "streaming" is a hint.

   McCool: we can check contenttype can use any options for

   McCool: such as streaming=true

   Koster: it depends on protocols. HTTP has a way to do.

   McCool: HTTP2 uses different mechanism.

   McCool: we can capture this dicussion in the issue.

   McCool: we can also take a look at alternatives such as

   Koster: CoAP only has blocking.

   Koster: but it is not continuous.

   Cristiano: streaming can make TD handling complex.

   McCool: protocol binding can also cover this aspect.

   McCool: each protocol can define what streaming=true means.

   Ege: When I opened the issue, I heard some people need this. We
   can keep this issue open and try to solve it going forward.

   Kaz: we can clarify media use cases first (like video streaming
   using MEPG-DASH or HLS) but that would be a complex task. We
   can address this in 2.0.

   Cristiano: scripting support is just basic now. we can wait
   till 2.0.

   <kaz> [adjourned]

    Minutes manually created (not a transcript), formatted by
    [14]scribe.perl version 131 (Sat Apr 24 15:23:43 2021 UTC).

     [14] https://w3c.github.io/scribe2/scribedoc.html

Received on Monday, 12 July 2021 08:02:42 UTC

This archive was generated by hypermail 2.4.0 : Monday, 12 July 2021 08:02:44 UTC