[wot-discovery] minutes - 29 March 2021

availabl at:
  https://www.w3.org/2021/03/29-wot-discovery-minutes.html

also as text below.

Thanks a lot for taking the miutes, Cristiano and Christian!

Kazuyuki

---
   [1]W3C

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

                             WoT Discovery

29 March 2021

   [2]IRC log.

      [2] https://www.w3.org/2021/03/29-wot-discovery-irc

Attendees

   Present
          Andrea_Cimmino, Ben_Francis, Christian_Glomb, Christine
          Perey, Cristiano_Aguzzi, Farshid_Tavakolizadeh,
          Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool,
          Soumya_Kanti_Datta, Tomoaki_Mizushima

   Regrets
          -

   Chair
          McCool

   Scribe
          cris, glomb, kaz

Contents

    1. [3]F2F minutes
    2. [4]Issue 145
    3. [5]Editorial PRs
    4. [6]Issue 147
    5. [7]Issue 133
    6. [8]Summary of resolutions

Meeting minutes

  F2F minutes

   [9]vF2F day 1

      [9] https://www.w3.org/2021/03/15-wot-minutes.html

   [10]vF2F day 2

     [10] https://www.w3.org/2021/03/17-wot-minutes.html

   [11]vF2F day 3

     [11] https://www.w3.org/2021/03/18-wot-minutes.html

   [12]vF2F day 4

     [12] https://www.w3.org/2021/03/22-wot-minutes.html

   [13]vF2F day 5

     [13] https://www.w3.org/2021/03/24-wot-minutes.html

   [14]vF2F day 6

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

   Kaz: will send a reminder to the IEC guys and ask them for
   slides

   McCool: "will give feedback for T2TRG"
   … don't see any issues, can accept?

   (no objection)

   day 1 minutes accepted and to be marked as "reviewed"

   Kaz: note day 2 is the Discovery day

   McCool: don't see major problems; any problems?

   (none)

   McCool: mark as "reviewed"
   … official acceptance during the main call later

  Issue 145

   <glomb> [15]https://github.com/w3c/wot-discovery/pull/145 PR
   145: Listing with chunked transfer

     [15] https://github.com/w3c/wot-discovery/pull/145

   PR not issue

   Farshid presents

   Three proposal: pagination / headers / chunking

   Chunking: Streaming instead of pagination

   <kaz> [16]Preview: 6.2.2.1.5 Listing

     [16] https://pr-preview.s3.amazonaws.com/farshidtz/wot-discovery/pull/145.html#exploration-directory-api-registration-listing

   mm issue:JSON-LD needs context, Farshid: not necessary

   HTTP 1.1 chunked transfer encoding

   Widely supported

   HTTP/2 -> http frames

   Where is it applied?

   McCool: browser support it, variable chunk size

   McCool: almost invisible

   clients have to request content-lenght

   Question: how big is the entire message?

   McCool: Content-length optional

   Farshid: expensive to calculate, can be optimized

   McCool: client can do head

   Farshid: some concerns that it is not enough, does not prevent
   pagination

   Christian: want to have both options

   <kaz> [17]Linked Data Platform Paging 1.0: 4.2 Simple paging
   flow using redirects

     [17] https://www.w3.org/TR/ldp-paging/#ldpp-ex-paging-303

   Both mandatory: both optional?

   Farshid: Query API should provide pagination

   McCool: Server should optimize

   McCool: extra work to realize

   Chunking for large TDs

   Payload body: array of TDs

   Christian: want possibility to add extra info

   McCool: clean up draft, chunking as basic functionality

   McCool: leave pagination for the moment and ask for review

   Farshid: not compatible

   Chunking w/ current draft

   Farshid: Header based approach can be added to chunking

   <kaz> [18]PR 130 Preview: 6.2.2.1.5 Listing

     [18] https://pr-preview.s3.amazonaws.com/farshidtz/wot-discovery/pull/130.html#exploration-directory-api-registration-listing

   <kaz> proposal: merge PR 145; add a new PR based on PR 130

   [19]https://github.com/w3c/wot-discovery/pull/145 should be
   merged. [20]https://github.com/w3c/wot-discovery/pull/130.

     [19] https://github.com/w3c/wot-discovery/pull/145
     [20] https://github.com/w3c/wot-discovery/pull/130.

   130 will be closed

   Cristiano: +1 for merging this PR
   ... Then cleanup
   ... What about extra info in the body?
   ... Issue Mix of JSON + JSON-LD
   ... Chunking also applies for submitting TDs
   ... Large TDs vs. large sets of TDs.

   McCool: Pagination info in body or header: to be discussed.
   Farshid will fix 130: then discussion <kaz> (some more
   discussion)

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

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

   Resolution: Will merge this PR145 and add a new PR to add
   pagination based on the header-based proposal in PR130 with
   necessary features (e.g. nextLink, etag headers).

   130 cancelled, then new PR.

   Plus one more PR for having extra info in body

  Editorial PRs

   <kaz> [22]PR 136: Validation error example

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

   McCool: Editorial PRs should be merged

   <kaz> [23]PR 137: Update jsonpath draft URL and date

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

   <kaz> [24]PR 138: Improve directory intro

     [24] https://github.com/w3c/wot-discovery/pull/138

  Issue 147

   [25]Issue 147: Add reference to Discovery paper by Arne
   Broering, Soumya Kanti Datta, and Christian Bonnet

     [25] https://github.com/w3c/wot-discovery/issues/147

   Fundamental work should be acknowledged

   McCool: Some more work to be cited?

   <kaz> [5min break]

   <kaz> (Christian and Soumya leaves)

   <kaz> (Ben joins)

  Issue 133

   <kaz> [26]Issue 133 - Refactoring TDD Thing Description

     [26] https://github.com/w3c/wot-discovery/issues/133

   Farshid: please speak about the refactored td

   Ben: single things properties, combining listing and filtering
   … spitting in three events
   … anyother changes?

   Farshid: td -> is now things. More readable

   <kaz> i/please peak/topic: Issue 133/

   Farshid: is it ok to call them things
   … ?

   McCool: I agree with the changes
   … it is a reasonable change, although it is less readable
   … is a registration an action?

   Farshid: yep

   McCool: another issue property names in url is not consistent
   … should we create a convention for urls?
   … it is a whole other discussion
   … urls can change but not the affordance names

   Farshid: it is a another issue... it means that the URL can be
   changed in the spec?

   McCool: maybe a TM can help

   Farshid: should we call things or tds?

   McCool: vote for td
   … @type : "Thing" is a legacy definition
   … I am ok eitherway
   … just stick with things
   … is sparql a property
   … is weird

   Cristiano: did we solve the problem of choosing which form to
   use?

   Farshid: sparql is special

   Ben: we cannot add sparql as query filter
   … property vs action is an open question

   Andrea: why sparql is not a property?

   Ben: we cannot describe it correctly as a form of things

   McCool: jsonpath would be much more common
   … sparql is even optional

   Ben: sparql is separate because jsonpath and xpath is more a
   fragment than a proper high level query lang
   … also we have still to decide what is really normative

   McCool: I would say that once we have a thingmodel we'll use it

   (usually TMs does not have fixed urls)

   McCool: closing the meeting, let's keep discuss on the issue

   <kaz> [adjourned]

Summary of resolutions

    1. [27]Will merge this PR145 and add a new PR to add
       pagination based on the header-based proposal in PR130 with
       necessary features (e.g. nextLink, etag headers).


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

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

Received on Monday, 26 April 2021 12:00:25 UTC