12:02:01 RRSAgent has joined #wot-script 12:02:01 logging to https://www.w3.org/2021/12/06-wot-script-irc 12:02:07 meeting: WoT Scripting API 12:03:07 chair: Daniel 12:03:15 present+ Kaz_Ashimura, Daniel_Peintner 12:04:59 Mizushima has joined #wot-script 12:06:55 present+ Tomoaki_Mizushima 12:09:58 scribenick: kaz 12:10:02 topic: Minutes 12:10:13 -> https://www.w3.org/2021/11/29-wot-script-minutes.html Nov-29 12:10:40 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#6_December_2021 12:10:58 dp: let's discuss the topic on the Use Cases section later again 12:11:11 ... don't see any issues with the minutes themselves 12:11:35 (no objections; minutes approved) 12:13:35 cris has joined #wot-script 12:13:58 present+ Cristiano_Aguzzi 12:15:11 topic: Decision process 12:15:46 -> https://github.com/w3c/wot/pull/1005 wot PR 1005 - Asynchronous Review Process for Specification Changes 12:16:13 ca: maybe we can introduce some specific labels to clarify the importance of each issue/PR 12:16:16 q+ 12:16:41 dp: yeah, would make sense 12:19:13 kaz: if we REALLY want and need, we can go for this asynchronous decision making direction 12:19:33 ... however, as I mentioned last week already, we should be very careful about this issue 12:21:17 ... because our basic policy for this Charter period has been having discussion on GitHub, then during TF calls and during the main call in the end for important topics like publication decision 12:21:37 ... so we should clarify what kind of issues/PRs can be handled by which method 12:21:43 dp: right 12:22:17 ... we should continue to discuss how to deal with it 12:25:23 topic: Meeting cancellations 12:26:57 dp: McCool suggest we cancel all the WoT calls after Dec 19 except the main calls (and all meetings canceled after 26th) 12:27:14 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations Cancellation plan on the main wiki 12:27:20 dp: I'm OK with that plan 12:27:33 ca: I'm also OK 12:27:56 topic: PRs 12:28:01 subtopic: PR 353 12:28:31 -> https://github.com/w3c/wot-scripting-api/pull/353 PR 353 - refactor: move section "Terminology and conventions" right after "Conformance" 12:28:40 dp: moved the Terminology section 12:28:46 s/moved/moving/ 12:31:09 ... also removing references 12:31:26 ca: reference for ECMAScript has some issue 12:32:11 dp: can create another issue to address that point 12:33:09 ... note there is some ReSpec error about [[value]] 12:33:43 ... objection to merge this PR 353? 12:33:47 (no objections) 12:34:14 merged 12:34:41 subtopic: PR 356 12:34:53 -> https://github.com/w3c/wot-scripting-api/pull/356 Allow only one subscription per affordance 12:35:31 ca: will clean up the PR 12:36:10 dp: if you can fix the issue with ECMAScript, that's great 12:38:45 -> https://github.com/w3c/wot-scripting-api/issues/358 Issue 358 - FIX ECMASCRIPT references 12:39:02 topic: Issues 12:39:20 subtopic: Issue 342 12:39:47 -> https://github.com/w3c/wot-scripting-api/issues/342 Issue 342 - Reference terminology section of the architecture specification 12:39:55 dp: think this issue is already resolved 12:40:13 q+ 12:40:32 ca: what about the "Use cases" section? 12:41:04 dp: there is a comment from Mizushima-san for another issue about that point 12:42:06 ... (adds comments) 12:42:23 -> https://github.com/w3c/wot-scripting-api/issues/342#issuecomment-986740109 Daniel's comments 12:42:33 subtopic: Issue 355 12:42:49 -> https://github.com/w3c/wot-scripting-api/issues/355 Issue 355 - Rename Use Cases section ? 12:43:31 dp: Mizushima-san suggests we change the section title from "Use Cases" to "Features" 12:43:40 ca: features are about more products 12:43:42 q? 12:48:43 ack k 12:57:08 kaz: the most important thing here is all the WoT Editors/Contributors having the same understanding for the terminologies for WoT specs including "Use cases", "Functionalities" and "Features" so that we can use those terms consistently for all the WoT spec documents 12:59:18 dp: I'm OK with "Functionalities" 12:59:24 ca: I'm OK too 13:00:26 mizu: would still prefer "Features" 13:00:46 kaz: I'm OK with either way, "Functionalities" or "Features" 13:01:40 ... but "Use cases" is confusing to be used to show functionalities withing WoT spec documents 13:01:44 [adjourned] 13:01:48 rrsagent, make log public 13:01:57 rrsagent, draft minutes 13:01:57 I have made the request to generate https://www.w3.org/2021/12/06-wot-script-minutes.html kaz 15:28:19 Zakim has left #wot-script