W3C home > Mailing lists > Public > public-wot-wg@w3.org > February 2020

[Scripting] minutes - 17 February 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Tue, 25 Feb 2020 08:54:48 +0900
Message-ID: <877e0bh77b.wl-ashimura@w3.org>
To: public-wot-wg@w3.org
available at:
  https://www.w3.org/2020/02/17-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

17 Feb 2020

Attendees

   Present
          Kaz_Ashimura, Daniel_Peintner, Tomoaki_Mizushima,
          Zoltan_Kis

   Regrets
          Ege_Korkan

   Chair
          Zoltan

   Scribe
          kaz, zkis

Contents

     * [2]Topics
         1. [3]Previous minutes
         2. [4]https://github.com/w3c/wot-scripting-api/issues/202
         3. [5]Error mapping
         4. [6]https://github.com/w3c/wot-scripting-api/issues/201
         5. [7]https://github.com/w3c/wot-scripting-api/issues/193
     * [8]Summary of Action Items
     * [9]Summary of Resolutions
     __________________________________________________________

   <inserted> scribenick: kaz

Previous minutes

   [10]Feb-10 minutes

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

   Kaz: Zoltan is OK with the above minutes
   ... any problems/comments form the others?

   Daniel: np

   Mizushima: np

   Kaz: I'm also OK, so let's approve the minutes

   (previous minutes approved)

   (Zoltan joins)

   <inserted> scribenick: zkis

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

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

   Zoltan: We have some ReSpec issues. Maybe we should update the
   source, following the best practices in
   [12]https://github.com/w3c/web-nfc

     [12] https://github.com/w3c/web-nfc

   Daniel: we should work on defining InteractionOptions

   Zoltan: Currently at
   [13]https://w3c.github.io/wot-scripting-api/#idl-def-interactio
   noptions
   ... We need to remove the markdown line from the doc header in
   the spec. Then it renders fine.

     [13] https://w3c.github.io/wot-scripting-api/#idl-def-interactionoptions

   <dape>
   [14]https://www.w3.org/TR/wot-scripting-api/#idl-def-interactio
   noptions

     [14] https://www.w3.org/TR/wot-scripting-api/#idl-def-interactionoptions

   Daniel: the simplest is to extend with another optional field
   that provides an index to the preferred binding

   Zoltan: should it be a single value or an Array?
   ... what is the policy, just a hint or if that index doesn't
   work then should it fail?

   Daniel: the easiest would be to fail, since the script could
   choose another one, or remove the index hint

   Zoltan: formIndex as name?

   Daniel: sounds fine

   Zoltan: so we agreed how to extend, in the name and what does
   it mean

   Daniel: what about it being optional?

   Zoltan: InteractionOptions is a dictionary all are optional at
   the moment

   Daniel: ok, it should not be required

Error mapping

   <zkis> [15]https://github.com/w3c/wot-scripting-api/issues/200

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

   Daniel: will prepare a proposal with Ege in the issue

   Zoltan: about writeProperty return values we have already
   agreed. Zoltan takes the task to create PR.

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

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

   Daniel: this is a breaking change in the API
   ... problem with scripts already running

   Zoltan: what I planned to do at the moment was to return "any"
   from reads, but explain in more detail how to deal with Forms,
   content types and DataSchema

   Daniel: in node-wot the "any" gets interpreted according to the
   media type.

   Zoltan: the thing is that there are already solutions in the
   Web Platform and would be nice to use them here as well
   ... maybe we can create a new issue about it

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

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

   Zoltan: having issue doing smart things instead of the scripts

   Daniel: it should be the same as reading the property

   Zoltan: when do we provide the value?

   Daniel: we raised that in the TD spec

   Zoltan: indeed we could handle it saying it's the same as a
   read done with the same bindings
   ... but there are issues
   ... not all devices will behave in the same way

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [18]scribe.perl version 1.154 ([19]CVS log)
    $Date: 2020/02/18 13:35:51 $

     [18] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [19] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 24 February 2020 23:54:55 UTC

This archive was generated by hypermail 2.4.0 : Monday, 24 February 2020 23:54:56 UTC