[Scripting] minutes - 8 March 2021

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

also as text below.

Thanks  lot for taking the minutes, Zoltan!

Kazuyuki

---
   [1]W3C

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

                           WoT Scripting API

08 March 2021

   [2]Agenda. [3]IRC log.

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

Attendees

   Present
          Daniel_Peintner, Kaz_Ashimura Cristiano_Aguzzi,
          Tomoaki_Mizushima, Zoltan_Kis

   Regrets
          -

   Chair
          Daniel

   Scribe
          kaz, zkis

Contents

    1. [4]prev minutes
    2. [5]vF2F
    3. [6]GitHub branch renaming
    4. [7]Any other quick updates?
    5. [8]Issue 304
    6. [9]Issue 303
    7. [10]Issue 302
    8. [11]Issue 299
    9. [12]Issue 300
   10. [13]Next calls

Meeting minutes

  prev minutes

   <dape> [14]March-1

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

   Daniel: (goes through the minutes)

   Daniel: look good
   … any objections?

   (none)

   approved

  vF2F

   [15]vF2F agenda for Scripting API

     [15] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_March_2021#Scripting_.281h.29

   Daniel: (goes through the proposed agenda)

   [16]draft slides on scripting api

     [16] https://docs.google.com/presentation/d/1wlpO_l16XtuDPO-8DsSG6g-MjQI-dSESWqlgnt839-k/edit?usp=sharing_eip&ts=6033b061

   Daniel: (also shows the draft slides)

   Zoltan: we presented interaction input/output during TPAC

   Daniel: need to look at previous slide set about that

   Zoltan: would include several examples
   … Cristiano should talk about validation
   … exposedThing requires detailed discussion

   Daniel: some of the discussion points have been resolved
   … need to check
   … note our slot is 1 hour on March 25
   … we need to split our work into the people working on the
   specific topic
   … also note that there will be conflict with the F2F call next
   week

   Daniel: vF2F will be held on March 15, 17, 18, 22, 24 and 25

   [17]vF2F schedule

     [17] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_March_2021#Time_table_2

   Daniel: maybe no official call but possibly additional call by
   the Editors

   Cristiano: ok

   Zoltan: ok

  GitHub branch renaming

   Daniel: "master" branch has been renamed to "main"

   Kaz: some minor trouble with accessing the github.io page
   … but it's now available

   Zoltan: can with the "main" branch

   Daniel: if you have a pop-up saying you need to try 3 commands,
   please do so
   … if you don't, should be ok

  Any other quick updates?

   Kaz: there are discussions on memory size by the Profile TF
   … also pagination of big Thing Description discussion by the
   Discovery TF
   … so I was wondering about your interest in those points

   Daniel: not sure how to handle streaming or memory size

   Zoltan: for constraint device use cases, maybe we need to think
   about CBOR

   <zkis> zk: encapsulated by implementations

   <zkis> zk: Since fetching TDs is separate from the API, it is
   out of scope

   <zkis> ca: direct discovery might be involved

   Zoltan: exactly, but it is possible to encapsulate even then

   Kaz: I'm asking them to clarify some concrete use cases about
   those proposals, so we can revisit those proposals when the
   concrete use case descriptions are generated

   Daniel: there was some discussion about binary data

   <dape> [18]https://github.com/w3c/wot-thing-description/blob/
   main/test-bed/reports/binary-comparison-2018-04-13.csv

     [18] https://github.com/w3c/wot-thing-description/blob/main/test-bed/reports/binary-comparison-2018-04-13.csv

   Daniel: this is a broader discussion than our scope, I think

   Zoltan: also thinks we need to define a use case
   … note that these days the capability of "small devices" is
   getting improved
   … so wondering about embedded devices in the market
   … thought OCF had done a lot of work on limited devices

   Daniel: ok
   … so as the conclusion, we may be interested but need concrete
   use cases :)

  Issue 304

   <dape> [19]Produce ExposedThing from a ThingModel instance,

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

   Cristiano: need a stable definition for "Thing Model"

   Zoltan: let's discuss the proposal later

  Issue 303

   <dape> [20]Separate ExposedThing API,

     [20] https://github.com/w3c/wot-scripting-api/issues/303

   Daniel: security section as well

   Zoltan: let's keep it dormant for now

  Issue 302

   <dape> [21]ActionHandler returning InteractionInput always,

     [21] https://github.com/w3c/wot-scripting-api/issues/302

   <kaz> i/dp: (adds a label "next iteration" to Issue 304 and
   Issue 303)/302/

   Zoltan: we can close this issue

   Cristiano: I'm OK if Daniel is OK

   Daniel: ok

   (closed)

  Issue 299

   <dape> [22]Chose a particular security schema for an
   ExposedThing,

     [22] https://github.com/w3c/wot-scripting-api/issues/299

   Daniel: should add some label to this issue?

   Cristiano: ok with adding "next iteration"

   Daniel: (adds "next iteration" label)

  Issue 300

   <dape> [23]Should title be mandatory in ExposedThingInit?,

     [23] https://github.com/w3c/wot-scripting-api/issues/300

   Cristiano: could you please click the link there?

   [24]old issue 212 - Partial TD validation for input of
   produce() method

     [24] https://github.com/w3c/wot-scripting-api/issues/212

   Daniel: (clicks the link above to get issue 212)

   Zoltan: may to take it into account

   Daniel: this issue 212 is about what should be refused

   (since Ege's point was validation)

   Zoltan: we ourselves need to define exposedThing for that
   purpose here
   … since it's not defined by Thing Description itself

   Daniel: you implementation needs to add the title

   Zoltan: that is regarding the low-level API

   Cristiano: this is not the same behavior as the one we use for
   form and href

   Zoltan: we should add a clarification to the Scripting API spec

   Cristiano: that's true but we may get a paradox on how to
   handle the TD fragment

   Zoltan: have not provided the title
   … that was a failure

   Daniel: we had discussion on the default
   … having a default wouldn't be useful here
   … currently, in node-wot the default kicks twice

   Zoltan: but that depends on implementations
   … title can be changed by the users
   … while the id might be an automatically generated value
   … you could use an internally generated id as well

   Daniel: we need to get adjourned now

  Next calls

   <cris> this issue about title is proving harder than I thought
   :D

   Kaz: my understanding was no official calls on March 15 or 22
   … but possibly casual chats by the Editors on the slides, etc.

   Daniel: right

   [adjourned]


    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 10:54:50 UTC