[Scripting] minutes - 20 July 2020

available at:
  https://www.w3.org/2020/07/20-wot-minutes.html

also as text below.

Thanks a lot for taking te minutes, Zoltan!

Kazuuki

---
   [1]W3C

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

                               - DRAFT -

                             WoT Scripting

20 Jul 2020

Attendees

   Present
          Kaz_Ashimura, Zoltan_Kis, Cristiano_Aguzzi,
          Tomoaki_Mizushima, Daniel_Peintner

   Regrets

   Chair
          Zoltan

   Scribe
          zkis

Contents

     * [2]Topics
         1. [3]Next publication
         2. [4]Previous call
         3. [5]Issue 222
         4. [6]Issue 219
         5. [7]Issue 215
         6. [8]OAuth 2.0
     * [9]Summary of Action Items
     * [10]Summary of Resolutions
     __________________________________________________________

   <scribe> scribe: zkis

Next publication

   Zoltan: propose to make a Note from the current version and
   then if we change the Discovery API, we can make another Note

   Daniel: does the Discovery TF has deadlines?

   Kaz: we can talk about that in the Discovery call today

Previous call

   <kaz> [11]June 15

     [11] https://www.w3.org/2020/06/15-wot-minutes.html

   [12]https://github.com/w3c/wot-scripting-api/pulls?q=is%3Apr+is
   %3Aclosed

     [12] https://github.com/w3c/wot-scripting-api/pulls?q=is:pr+is:closed

   Minutes approved

Issues 222

   <dape> [13]Issue 222 - Possible alternative design of
   Discovering API

     [13] https://github.com/w3c/wot-scripting-api/issues/222

   Cristiano: presents the proposal

   Zoltan: explains his own comment in the issue

   Cristiano: completely agree, need to converge on a stable set
   of discovery methods

   Daniel: we should keep the API similar across the 3 patterns
   (consume, produce, discover)
   ... for instance if we look at DataSchema abstract class +
   subclasses, we could use something similar eventually

   <kaz> [14]9.3 The ThingFilter dictionary

     [14] https://w3c.github.io/wot-scripting-api/#the-thingfilter-dictionary

   Daniel: we could have an abstract ThingFilter and then
   different instances

   Zoltan: that makes sense

   Cristiano: I see the point, but it's not trivial to use a
   common ThingFilter across all methods etc
   ... are you proposing different methods or not?

   Daniel: I can add a comment to the issue

   Cristiano: if we have one method with different subclasses of
   ThingFilter, then we implement different strategies with
   different classes
   ... it's better to use functions
   ... but we need more experimenting and more inputs
   ... looks there is consensus there will be 2-phase discovery,
   and this should also reflect in the API design

   Zoltan: 2-phase is a newer development, we will follow the
   discussion

   Daniel: not opposed to the proposal, but seen the similarity
   with DataSchema
   ... one open point: we usually in plugfests we didn't use
   discovery, grabbed the TD URL from somewhere, so we should
   implement discovery in node-wot
   ... we did have some early implementation, but the number of
   options for URL complicates things

   Zoltan: we could use some kind of capability querying API for
   discovery

Issue 219

   [15]Issue 219

     [15] https://github.com/w3c/wot-scripting-api/issues/219

   Zoltan: any resolution on that in the TD call?

   Daniel: no resolution yet, looks like an optimization

   <kaz> [16]wot-thing-description issue 848

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

   Daniel: we could mark it deprecated and not support in
   Scripting

   Cristiano: I remember the same, people were more supportive of
   reading all properties

   Kaz: I also asked everyone to have more use cases for this
   (during the TD call)

   Zoltan: we should be able to deprecate things, so what about
   putting version number in WoT object?

   Cristiano: sounds fine

   Daniel: node-wot is not fully compliant with TD spec on
   handling readmultiple

   <kaz> [17]7.6 The readMultipleProperties() method

     [17] https://w3c.github.io/wot-scripting-api/#the-readmultipleproperties-method

   Daniel: we should perhaps drop it

   Zoltan: right, we can add it back later
   ... will make an issue about this
   ... should we publish before we remove?
   ... let's think about that until the next call

Issue 215

   [18]Issue 215

     [18] https://github.com/w3c/wot-scripting-api/issues/215

   Cristiano: needs more discussion

   Daniel: BTW, does WebIDL support modules?

   Cristiano: yes, modules should represent namespaces

OAuth 2.0

   [19]Issue 214

     [19] https://github.com/w3c/wot-scripting-api/issues/214

   Cristiano: we reached a consensus about the flow support
   ... propose to discuss this next time
   ... including the lifecycle of the script itself (e.g. waiting
   for user input)

   Zoltan: it should be abstracted by the UA behind async
   operations

   Cristiano: currently we cannot trigger a flow

   Zoltan: we used to have a start() call for that, but we removed
   it

   Daniel: in node-wot we have basic support for that

   <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 ([21]CVS log)
    $Date: 2020/07/22 13:00:49 $

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

Received on Tuesday, 28 July 2020 06:20:13 UTC