- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 30 Nov 2021 16:54:26 +0900
- To: public-wot-wg@w3.org
available at: https://www.w3.org/2021/11/22-wot-script-minutes.html also as text below. Thanks a lot for taking the minutes, Daniel! Kazuyuki --- [1]W3C [1] https://www.w3.org/ WoT Scripting API 22 November 2021 [2]IRC log. [2] https://www.w3.org/2021/11/22-wot-script-irc Attendees Present Cristiano_Aguzzi, Daniel_Peintner, Kaz_Ashimura, Tomoaki_Mizushima, Zoltan_Kis Regrets - Chair Daniel Scribe dape Contents 1. [3]Previous minutes 2. [4]Issues 1. [5]Next charter topics 2. [6]Reference terminology section of the architecture specification 3. [7]Description for labels 4. [8]Finding correct unsubscribe form 5. [9]Clarify multiple requests for subscription/observation 6. [10]subscribeEvent and observerProperty misaligned signature 7. [11]New op values (queryaction and cancelaction) Meeting minutes Previous minutes [12]-> Nov-15 [12] https://www.w3.org/2021/11/15-wot-script-minutes.html -> Minutes approved Issues Next charter topics [13]https://github.com/w3c/wot-scripting-api/issues/352 [13] https://github.com/w3c/wot-scripting-api/issues/352 Daniel: created basic list … Ege added "complex actions" … that makes sense to me also Cristiano: Looks good so far Daniel: Details don't need to be fully specified Kaz: Right … more important to look at *new* TD work Reference terminology section of the architecture specification [14]https://github.com/w3c/wot-scripting-api/issues/342 [14] https://github.com/w3c/wot-scripting-api/issues/342 Daniel: M. Lagally advised us to look at terms … 2nd topic was about where to put terminology section Daniel: should move terminology to Chapter 4 Cristiano: +1 … should also look at terms Daniel: Agree, suggest having 2 PRs Cristiano: Makes sense Kaz: Since Scripting API is a Note, we do not need the conformance section Daniel: Correct, but i guess it still makes sense .. we also have conventions Cristiano: wonder whether we can link most of the terms … e.g, URL terms Kaz: points to Conformance section. Should revisit it. Daniel: Will create a dedicated issue about it <Mizushima> +1 Description for labels [15]https://github.com/w3c/wot-scripting-api/issues/336 [15] https://github.com/w3c/wot-scripting-api/issues/336 Daniel: Other label Zoltan: Meant we create "other" label Daniel: not the plan Cristiano: +1 for adding the descriptions Finding correct unsubscribe form [16]https://github.com/w3c/wot-scripting-api/issues/351 [16] https://github.com/w3c/wot-scripting-api/issues/351 Daniel: Issue links TD issue Cristiano: TD resolution is to be post-poned … Ege was saying it is not 1st priority … algorithm in Scripting spec seems fine Clarify multiple requests for subscription/observation [17]https://github.com/w3c/wot-scripting-api/issues/346 [17] https://github.com/w3c/wot-scripting-api/issues/346 Daniel: multiple subscription Cristiano: Not sure what runtime should do … one subscribe … multiple subscribers … what to do in case of cancellation of 1 subscriber Daniel: Decision of complexity Zoltan: Would vote for 1 subscription … another subscription would overwrite it Cristiano: I am OK with that Zoltan: Wonder what should happen in case of a *new* subscription … throwing error ? Cristiano: Not throwing hides mistakes Daniel: +1 Zoltan: +1 subscribeEvent and observerProperty misaligned signature [18]https://github.com/w3c/wot-scripting-api/issues/343 [18] https://github.com/w3c/wot-scripting-api/issues/343 Daniel: difference of TS definitions and the spec Cristiano: Will work on PR w.r.t. return type New op values (queryaction and cancelaction) [19]https://github.com/w3c/wot-scripting-api/issues/335 [19] https://github.com/w3c/wot-scripting-api/issues/335 Zoltan: Is TD integrating it? Cristiano: Yes, it has been merged Zoltan: discuss this next time... <kaz> [adjourned] Minutes manually created (not a transcript), formatted by [20]scribe.perl version 159 (Fri Nov 5 17:37:14 2021 UTC). [20] https://w3c.github.io/scribe2/scribedoc.html
Received on Tuesday, 30 November 2021 07:54:31 UTC