[Scripting] minutes - 2 August 2021

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

also as text below.

Thanks a lot for taking the minutes, Cristiano!

Kazuyuki

---
   [1]W3C

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

                           WoT Scripting API

02 August 2021

   [2]IRC log.

      [2] https://www.w3.org/2021/08/02-wot-script-irc

Attendees

   Present
          Cristiano_Aguzzi, Daniel_Peintner, Kaz_Ashimura,
          Tomoaki_Mizushima

   Regrets
          Zoltan

   Chair
          Daniel

   Scribe
          cris, kaz

Contents

    1. [3]minutes
    2. [4]Quick Updates
         1. [5]vacation plans
    3. [6]PRs
    4. [7]issues
         1. [8]Issue 310
         2. [9]TypeScript - Type DataSchemaValue circularly
            references itself #301
         3. [10]Issue 107
         4. [11]issue 117
         5. [12]Issue 193
         6. [13]Issue 200
         7. [14]issue 212

Meeting minutes

  minutes

   Daniel: minutes are ok

   <kaz> [15]July-26

     [15] https://www.w3.org/2021/07/26-wot-script-minutes.html

   Daniel: ok minutes approved

  Quick Updates

    vacation plans

   Daniel: no updates
   … it might be diffcult to join on 16th

   Cristiano: yeah also from my side

   Daniel: zoltan will be able to join on the 9th

  PRs

   <dape> [16]https://github.com/w3c/wot-scripting-api/pull/329

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

   Daniel: we have still a pending PR from Cristiano: 329 PR 329 -
   feat: move thing-description types to a dedicated package
   … we are waiting for feedback from Zoltan

   Cristiano: no pressure from my side

  issues

   Daniel: we are small group and there are not so many updates
   … not sure what to do

   Cristiano: we could just do small clean up

    Issue 310

   <kaz> [17]Issue 310 - Handling pagination

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

   Daniel: issue 310 is about discovery right?

   Cristiano: not only it talks about pagination in discovery but
   it can be used as a built in functionality

    TypeScript - Type DataSchemaValue circularly references itself #301

   <dape> [18]Issue 301 - TypeScript - Type DataSchemaValue
   circularly references itself

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

   Cristiano: I think it was solved

   Daniel: I would close it

    Issue 107

   <kaz> [19]Issue 107 - Very high frequency updates

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

   Daniel: what happens when a thing fires many events in a short
   time?

   Cristiano: is it more protocol specific?

   Daniel: we could state the maximum updates in the TD and follow
   the regulation

   Daniel: I think we should add the propose closing label here,
   and just wait for feedback

   Kaz: we should have clear detailed use case, especially for
   complicated features like this
   … if we don't get any we could defer it

    issue 117

   <kaz> [20]Issue 117 - Extract normative assertions for testing

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

   Daniel: this issue is about assertions in the document
   … since scripting in not on the rec check
   … do we need this normative assertions?
   … or even a test plan?

   Kaz: we don't have to work on testing, since Scripting API is
   not a group Note at the moment.
   … maybe we could define the test plan if we have extra time

   Cristiano: might be really difficult to define a testing suite

   Daniel: I agree we could do behavioral testing (i.e. unit test
   suites)

   Cristiano: it might be a future improvement

   Daniel: there was I company who could develop those tests
   … but it never took off
   … dape close in favor 190

    Issue 193

   <kaz> [21]Issue 193 - Should writeProperty() return a value?

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

   Daniel: my take is to allow both use cases
   … if the td allows it we should allow to return the data
   … it is more flexible

   Daniel: it should not be required

   Cristiano: the api will be more complex, my opinion is that we
   should well document this behavior

   Daniel: yes understand, but as you said there are already
   concrete implementations that does so

   Cristiano: we have to keep in mind that this feature might only
   work for a specific protocol
   … so when checking the return value developers should somehow
   know the protocol used

   Cristiano: do we have a concrete TD of a Philips HUE device

   Kaz: we can think about this specific device implementation,
   but the discussion should be moved to profile calls or work
   with them

   Cristiano: should we move this issue somewhere else then?

   Kaz: yeah or at least link

   Daniel: we have an open issue about it in the thing description
   repository

   Kaz: we could ask this in the main call then

   Daniel: ok!

    Issue 200

   <kaz> [22]Issue 200 - Error Handling

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

   Daniel: (adds comments)

   <kaz> [23]Daniel's comments

     [23] https://github.com/w3c/wot-scripting-api/issues/200#issuecomment-890965694

    issue 212

   <kaz> [24]Issue 212 - Partial TD validation for input of
   produce() method

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

   Cristiano: I propose to close it and open small issues for left
   open topics

   Daniel: I agree
   … we are out of time
   … let's close the meeting now

   <kaz> [adjourned]


    Minutes manually created (not a transcript), formatted by
    [25]scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).

     [25] https://w3c.github.io/scribe2/scribedoc.html

Received on Monday, 20 September 2021 08:39:42 UTC