[Scripting] minutes - 20 April 2020

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

also as text below.

Thanks a lot for taking the minutes, Zoltan!

Kazuyuki

---
   [1]W3C

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

                               - DRAFT -

                             WoT Scripting

20 Apr 2020

Attendees

   Present
          Kaz_Ashimura, Daniel_Peintner, Tomoaki_Mizushima,
          Zoltan_Kis

   Regrets

   Chair
          Zoltan

   Scribe
          zkis

Contents

     * [2]Topics
         1. [3]Review minutes
         2. [4]issue#210
         3. [5]issue#211,
            https://github.com/w3c/wot-scripting-api/issues/211
         4. [6]issue#212,
            https://github.com/w3c/wot-scripting-api/issues/212
         5. [7]PR#https://github.com/w3c/wot-scripting-api/pull/20
            9
     * [8]Summary of Action Items
     * [9]Summary of Resolutions
     __________________________________________________________

Review minutes

   Previous minutes:
   [10]https://www.w3.org/2020/04/06-wot-minutes.html

     [10] https://www.w3.org/2020/04/06-wot-minutes.html

   <scribe> scribe: zkis

   Daniel: about init dictionary, do we continue using that name?

   Zoltan: until it's changed in the Architecture call discussion,
   we use the name
   ... it is a common name, what we needs to be discussed is how
   does it relate to Thing Templates or Partial TDs

issue#210

   <kaz> [11]Issue 210

     [11] https://github.com/w3c/wot-scripting-api/issues/210

   Zoltan: wondering about the value of opening up hooks for event
   subscription and observe

   Daniel: it came from proxy implementations who want to know
   when an event has been dispatched and observation notification
   happened

   Zoltan: the proxy could subscribe explicitly to the original
   Thing
   ... so it uses ConsumedThing

   Daniel: but also exposes a new Thing as ExposedThing
   ... and needs to forward the subscriptions to the original
   Thing

   Zoltan: ok, so it _completely_ defines the behavior, not just
   customizes it
   ... so I can do the changes in this way.
   ... another question, could we include additional data
   (subscribe and cancelation data) into InteractionOptions?

   Daniel: makes sense
   ... wondering if we need at all the subscription data and
   cancellation data

   <kaz> [12]7. the ExpostedThing interface

     [12] https://w3c.github.io/wot-scripting-api/#the-exposedthing-interface

   <kaz> [13]6. The ConsumedTHing interface

     [13] https://w3c.github.io/wot-scripting-api/#the-consumedthing-interface

   Daniel: anyway it's good to include into InteractionOptions

issue#211, [14]https://github.com/w3c/wot-scripting-api/issues/211

     [14] https://github.com/w3c/wot-scripting-api/issues/211

   Daniel: explains the use case

   Zoltan: seems clear, will complete the changes

issue#212, [15]https://github.com/w3c/wot-scripting-api/issues/212

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

   Daniel: currently we don't really fully validate TDs in
   node-wot, just check context and expand the TD with default
   values.

   Zoltan: yes, we should just relax that in the spec

PR#[16]https://github.com/w3c/wot-scripting-api/pull/209

     [16] https://github.com/w3c/wot-scripting-api/pull/209

   Daniel: had the question whether should we use InteractionData
   as input as well

   Zoltan: implementations can do that, why to bother apps with
   that
   ... apps should just provide the language abstracted types, and
   implementations figure out the serialization based on protocol
   bindings

   Daniel: points out an incorrect example, needs to be fixed

   Zoltan: eventually we could return a parsed simple types or the
   complex InteractionData

   Daniel: need to think about this
   ... wondering would it be too complex if we require
   InteractionData also for input

   Zoltan: here is one example:
   [17]https://w3c.github.io/web-nfc/#example-6
   ... and [18]https://w3c.github.io/web-nfc/#example-13
   ... the problem is that in order to be able to handle the
   exceptions, we make all use cases difficult
   ... perhaps at this level it is fine to be a complex API and
   eventually have other simpler libraries on top

     [17] https://w3c.github.io/web-nfc/#example-6
     [18] https://w3c.github.io/web-nfc/#example-13

   Daniel: OK, let's reach out to others and ask

   Zoltan: any other topics?

   Daniel: checking the list of issues at
   [19]https://github.com/w3c/wot-scripting-api/issues

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

   Zoltan: feel free to comment on any issues

   [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/04/26 12:23:38 $

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

Received on Wednesday, 29 April 2020 07:50:08 UTC