[wot-discovery] minutes - 4 May 2020

available at:
  https://www.w3.org/2020/05/04-wot-discovery-minutes.html

also as text below.

Thanks a lot for taking the minutes, Farshid!

Kazuyuki

---
   [1]W3C

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

                               - DRAFT -

                             WoT Discovery

04 May 2020

   [2]Agenda

      [2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#4_May_2020

Attendees

   Present
          Kaz_Ashimura, Christian_Glomb, Andrea_Cimmino,
          Farshid_Tavakolizadeh, Kevin_Olotu, Michael_McCool,
          David_Ezell, Tomoaki_Mizushima

   Regrets

   Chair
          McCool

   Scribe
          FarshidT

Contents

     * [3]Topics
         1. [4]Reviewing the minutes
         2. [5]Going through the agenda
         3. [6]Query and filter operations
         4. [7]TTL Support
         5. [8]Multiple results in a query response
         6. [9]Closing
     * [10]Summary of Action Items
     * [11]Summary of Resolutions
     __________________________________________________________

   <kaz> scribenick: FarshidT

Reviewing the minutes

   <kaz> [12]Apr-27 minutes

     [12] https://www.w3.org/2020/04/27-wot-discovery-minutes.html

   no objections. Will publish the minutes.

Going through the agenda

   McCool: partial TDs
   ... multiple results in a query. Possibly related to
   [13]https://github.com/w3c/wot-discovery/issues/16
   ... compare and contrast query/filter approaches
   ... we should discuss each major topic in a github issue.

     [13] https://github.com/w3c/wot-discovery/issues/16

Query and filter operations

   Issue: [14]https://github.com/w3c/wot-discovery/issues/17

     [14] https://github.com/w3c/wot-discovery/issues/17

   McCool: (off-topic) creating an issue for partial/part of TD
   considerations.

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

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

TTL Support

   Issue: Query and filter operations

   McCool: is there a way for the consumers to know how long a
   thing has been alive
   ... adding additional use-case for when a device is
   ungracefully deinstalled or died.

   Issue: [16]https://github.com/w3c/wot-discovery/issues/18

     [16] https://github.com/w3c/wot-discovery/issues/18

   McCool: different ways of setting keepalive info, TTL time
   boundary, configurable TTL boundary. (more info in github issue
   comments)

   Farshid: use created/modified fields to know when TD was
   updated in directory

   McCool: need to look into the specs to know what those fields
   refer to. They probably refer to TD creating time on the
   device.
   ... add directory-specific info an out-of-band and include the
   TD inside

   Farshid: out-of-band info makes the submitted (TD) and queried
   (object with a TD) payloads inconsistent.

   McCool: keeping the TD intact and avoiding the modification
   makes it possible to check the integrity of TDs
   ... push (device checks in) vs poll (directory checks the thing
   status) to know the status of things

   Farshid: for polling, need a different implementation / access
   control for every protocol

   McCool: can use a proxy to poll the device status without
   accessing the device itself

   Kaz: have to establish trust between the device and proxy.
   maybe we ourselves don't have to think about the mechanisms but
   we should survey the existing mechanisms.

   <inserted> [17]McCool's updated comments for issue 18

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

Multiple results in a query response

   McCool: adding points in a comment to the issue
   [18]https://github.com/w3c/wot-discovery/issues/16

     [18] https://github.com/w3c/wot-discovery/issues/16

   Farshid: pagination of TDs in API response, TDs are an array
   inside an object with pagination info (page, total, perpage)

   McCool: what about a corner case, where an individual TD is
   very large

   Farshid: we did break TDs in pagination as part of previous
   implementations but it adds complications to the client. And
   different pages may end up with different models when dealing
   with partial TDs.

   McCool: notes added to issue 16:
   [19]https://github.com/w3c/wot-discovery/issues/16#issuecomment
   -623514384
   ... would like to have a resolution on pagination issue next
   Monday, 11th

     [19] https://github.com/w3c/wot-discovery/issues/16#issuecomment-623514384

Closing

   McCool: need to look at use cases to see if there discovery
   requirements to discuss the security issues

   <kaz> [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [20]scribe.perl version 1.154 ([21]CVS log)
    $Date: 2020/05/11 14:15:00 $

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

Received on Monday, 18 May 2020 05:52:35 UTC