[wot-discovery] minutes - 8 March 2020

available at:
  https://www.w3.org/2021/03/08-wot-discovery-minutes.html

also as text below.

Thanks a lot for taking the minutes, Farshid!

Kazuyuki

---
   [1]W3C

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

                             WoT Discovery

08 March 2021

   [2]Agenda. [3]IRC log.

      [2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#8_March_2021
      [3] https://www.w3.org/2021/03/08-wot-discovery-irc

Attendees

   Present
          Andrea_Cimmino, Christian_Glomb, Cristiano_Aguzzi,
          Farshid_Tavakolizadeh, Kaz_Ashimura, Kunihiko_Toumura,
          Michael_McCool, Tomoaki_Mizushima

   Regrets
          -

   Chair
          McCool

   Scribe
          FarshidT

Contents

    1. [4]minutes
    2. [5]discussions points
    3. [6]plugfest outcome
    4. [7]cancellations
    5. [8]F2F slides
    6. [9]JSONPath
    7. [10]PR Updated ontology source code, diagrams, and spec
       text
    8. [11]PR updates to geolocation proposal
    9. [12]PR Specify additional responses
   10. [13]Summary of issues

Meeting minutes

  minutes

   <kaz> [14]March-1

     [14] https://www.w3.org/2021/03/01-wot-discovery-minutes.html

   no objections. Publishing minutes.

  discussions points

   Kaz: some discussion related to pagination in the scripting API
   today

   Cristiano: streaming of TDs instead of paginating

   McCool: incremental loading of TDs, need to match the
   underlying networking protocol

   Kaz: small devices may need to extract TD fragments/elements
   one by one, but the Scripting TF wanted to know about the
   detailed use case scenario before thinking about the details.
   that was today's discussion.

   McCool: scripting API can use JSONPath to select parts of the
   TD

   McCool: maybe JSONPath should be added as an optional feature
   for self-describing devices

   McCool: There is PR to distinguish fragment from element

   Farshid: if self-describing device cannot perform the
   filtering, it should reject to avoid surprise on the client
   side (unexpected model, size)

   Cristiano: the filtering could be on a dedicated endpoint,
   similar to the TDD

   Issue: [15]https://github.com/w3c/wot-discovery/issues/132

     [15] https://github.com/w3c/wot-discovery/issues/132

  plugfest outcome

   <kaz> [16]wot-testing issue 122 - Create Outcomes Presentation
   for 2021.03 Plugfest

     [16] https://github.com/w3c/wot-testing/issues/122

   <kaz> mm: wonders if the next plugfest is in October during
   TPAC

   <kaz> kaz: if we don't schedule any additional meetings, yes

   <kaz> ... probably we need to hold testfests to check the
   implementation status, though

   Farshid: need to focus on closing critical issues, before
   implementing more

   <cris> +1

   McCool: we could remove less important features

   McCool: pagination could be removed.

   Andrea: adding pagination to ontology is not appropriate. We
   can try to remove them pagination from ontology and move the
   headers

   Andrea: commented on [17]https://github.com/w3c/wot-discovery/
   issues/54#issuecomment-792660587

     [17] https://github.com/w3c/wot-discovery/issues/54#issuecomment-792660587

   <McCool> [18]https://www.w3.org/TR/ldp-paging/

     [18] https://www.w3.org/TR/ldp-paging/

   McCool: Linked Data Platform Paging is a note, not a standard

   Cristiano: this means we need to rely on the protocol for
   pagination

   Cristiano: other protocols may have their own pagination
   mechanism

   Andrea: this is an http solution, we don't need to worry about
   other hypothetical protocols

   McCool: need to also check if we can paginate within a TD

   McCool: we have to make a decision on this, latest by March
   29th

   Farshid: the header-based proposal was similar. Since we need
   to rely on HTTP headers and spec and return a plain array,
   there is not much to decide.

   Christian: can we support several mechanisms? Not just one?

   Cristiano: shouldn't other endpoints also support pagination?

   McCool: pagination annotation in TD may be useful

  cancellations

   McCool: no calls in the next two weeks, due to conflicts with
   F2F

   McCool: we need to continue working on the issues and create
   PRs in the meantime

   <McCool> [19]https://github.com/w3c/wot/tree/main/
   PRESENTATIONS/2021-03-online-f2f

     [19] https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-03-online-f2f

  F2F slides

   upload to [20]https://github.com/w3c/wot/tree/main/
   PRESENTATIONS/2021-03-online-f2f

     [20] https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-03-online-f2f

   McCool: discovery meeting is on Mar 17th (next Wednesday)

  JSONPath

   McCool: need to change the reference in the draft

   <McCool> update JSONpath ref to point at
   draft-ietf-jsonpath-jsonpath/

  PR Updated ontology source code, diagrams, and spec text

   [21]https://github.com/w3c/wot-discovery/pull/127

     [21] https://github.com/w3c/wot-discovery/pull/127

   Andrea: Removed the id from RegistrationInfo, because if there
   is an id there, it would be the RegistrationInfo's ID, not the
   TD

   McCool: the context URL need to change in future to use the
   w3.org domain

   Kaz: the current URL is fine for the editor's draft, but what
   concrete URL do we want to use for the "update"?

   no objections to merging

  PR updates to geolocation proposal

   [22]https://github.com/w3c/wot-discovery/pull/128

     [22] https://github.com/w3c/wot-discovery/pull/128

  PR Specify additional responses

   [23]https://github.com/w3c/wot-discovery/pull/131

     [23] https://github.com/w3c/wot-discovery/pull/131

   merged

   <kaz> [adjourned]

Summary of issues

    1. [24]https://github.com/w3c/wot-discovery/issues/132


    Minutes manually created (not a transcript), formatted by
    [25]scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).

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

Received on Monday, 26 April 2021 11:54:30 UTC