[Scripting] minutes - 15 November 2021

available at:
  https://www.w3.org/2021/11/15-wot-script-minutes.html

also as text below.

Thanks a lot for taking the minutes, Zoltan!

Kazuyuki

---
   [1]W3C

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

                           WoT Scripting API

15 November 2021

   [2]IRC log.

      [2] https://www.w3.org/2021/11/15-wot-script-irc

Attendees

   Present
          Cristiano_Aguzzi, Daniel_Peintner, Kaz_Ashimura,
          Tomoaki_Mizushima, Zoltan_Kis

   Regrets
          -

   Chair
          Daniel

   Scribe
          zkis

Contents

    1. [3]approving previous minutes
    2. [4]node-wot release
    3. [5]PR 350
    4. [6]ISSUES
         1. [7]Clarify multiple requests for
            subscription/observation
         2. [8]subscribeEvent and observerProperty misaligned
            signature
    5. [9]Summary of action items

Meeting minutes

  approving previous minutes

   <dape> [10]https://www.w3.org/2021/10/
   18-wot-script-minutes.html

     [10] https://www.w3.org/2021/10/18-wot-script-minutes.html

   no objections

   <dape> [11]https://www.w3.org/2021/10/
   25-wot-script-minutes.html

     [11] https://www.w3.org/2021/10/25-wot-script-minutes.html

   Daniel: note that we discussed what to do in the next charter,
   to be tracked in an issue

   ACTION: DP creates issue for tracking charter changes

   no objections

   Daniel: last week we had joint call with Security TF

   <kaz> [12]Nov-8 Security call minutes

     [12] https://www.w3.org/2021/11/08-wot-sec-minutes.html

   [13]https://github.com/w3c/wot-security-best-practices/issues/
   27

     [13] https://github.com/w3c/wot-security-best-practices/issues/27

   Zoltan: we discussed onboarding, provisioning, discovery,
   management APIs, etc. See issues in the minutes.

   Daniel: will list these for the new charter

  node-wot release

   Daniel: we are publishing a Note and then update node-wot
   … but at the moment no need for an updated Note

  PR 350

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

     [14] https://github.com/w3c/wot-scripting-api/pull/350

   Daniel: related to the link checker

   Daniel: the PR fixes the broken links and typos

   <dape> Broken fragments: [15]https://w3c.github.io/
   wot-thing-description/#securityscheme (line 3948) [16]https://
   w3c.github.io/wot-thing-description/#nosecurityscheme (line
   3948)

     [15] https://w3c.github.io/wot-thing-description/#securityscheme
     [16] https://w3c.github.io/wot-thing-description/#nosecurityscheme

   Daniel: some of the errors were false

   Kaz: we should generate a static html first, only then apply
   the validator
   … There might be some option for that purpose, but, need to
   consult the validator checker doc

   Daniel: suggest merging this PR and then do the rest separately

   Zoltan: fine with that

   Daniel: merged

  ISSUES

    Clarify multiple requests for subscription/observation

   <dape> [17]https://github.com/w3c/wot-scripting-api/issues/346

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

   Cristiano: when we subscribe, should also record how to
   unsubscribe

   Daniel: this as also discussed in the TD TF,

   Cristiano: but it's not yet in the spec, may come only in the
   next charter

   Cristiano: it's about choosing a Form for unsubscribe

   Cristiano: implemented a scorer algorithm for determining how
   to unsubscribe
   … but we should change the TD spec to link the unsubscribe Form

   Daniel: can we subscribe via HTTP and unsubscribe via CoAP?
   … how should it work?

   Cristiano: we don't have practical use cases for that, but I
   think we should have the same binding

   Zoltan: I agree, also for security reasons

   Daniel: there is no statement to prohibit this use case

   Cristiano: it's a validation problem

   Cristiano: the TD should be invalid if it didn't have
   unsubscribe Form

   Daniel: right now the matching algorithm could possibly use the
   Form from any binding

   Zoltan: IMHO we should create an issue to track this, and
   update the algorithms in Scripting, to be precise

   <dape> [18]https://github.com/w3c/wot-thing-description/issues/
   968

     [18] https://github.com/w3c/wot-thing-description/issues/968

   Daniel: this depends on the TD TF to solve.

   [19]https://w3c.github.io/
   wot-scripting-api/#finding-an-unsubscribe-form

     [19] https://w3c.github.io/wot-scripting-api/#finding-an-unsubscribe-form

    subscribeEvent and observerProperty misaligned signature

   <dape> [20]https://github.com/w3c/wot-scripting-api/issues/343

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

   Cristiano: we can track this problem in a dedicated issue

   <dape> [21]https://github.com/w3c/wot-scripting-api/issues/351

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

   Daniel: then we also have an issue about the multiple
   subscriptions

   <dape> [22]https://github.com/w3c/wot-scripting-api/issues/346

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

   Cristiano: currently if subscribed, the next call will fail

   Zoltan: that is good enough for now

   Daniel: time is up, continue next time

   <kaz> [adjourned]

Summary of action items

    1. [23]DP creates issue for tracking charter changes


    Minutes manually created (not a transcript), formatted by
    [24]scribe.perl version 159 (Fri Nov 5 17:37:14 2021 UTC).

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

Received on Tuesday, 30 November 2021 07:48:20 UTC