12:03:23 RRSAgent has joined #wot-script 12:03:23 logging to https://www.w3.org/2022/03/07-wot-script-irc 12:03:57 dape has joined #wot-script 12:04:43 zkis has joined #wot-script 12:08:54 meeting: WoT Scripting API 12:08:58 chair: Daniel 12:09:09 present+ Kaz_Ashimura, Daniel_Peintner, Zoltan_Kis 12:09:19 regrets+ Cristiano 12:09:22 topic: Minutes 12:09:36 -> https://www.w3.org/2022/02/28-wot-script-minutes.html Feb-28 12:09:39 approved 12:10:02 topic: Cancellation? 12:10:22 dp: basically, next week will be the PlugFest 12:10:35 ... however, our slot is not overlapped 12:10:39 ... shall we have a call? 12:10:43 (some discussion) 12:11:00 dp: let's cancel the Scripting call next Monday, on March 14 12:11:17 present+ Tomoaki_Mizushima 12:11:41 topic: Issues 12:11:43 Mizusima has joined #wot-script 12:11:51 subtopic: Issue 335 12:12:24 -> https://github.com/w3c/wot-scripting-api/issues/335 Issue 335 - New op values (queryaction and cancelaction) 12:12:33 dp: we need resolution for this 12:13:19 zk: related to "sync" vs "async" 12:13:23 q+ 12:16:17 -> https://github.com/w3c/wot-thing-description/issues/890 related wot-thing-description Issue 890 - [vocabulary] Consider adding keyword to describe synchronous actions 12:16:20 ack k 12:17:14 kaz: we need to clarify the minimum set of cancellable session and the minimum set of expected synchronous/asynchronous actions based on concrete use cases 12:17:56 ... so I suggested before for the TD discussion and also would still suggest we defer this feature to the next version 12:19:06 -> https://w3c.github.io/wot-scripting-api/#the-consumedthing-interface 8. . The ConsumedThing interface 12:19:30 dp: (shoes section "8. The ConsumedThing interface" of Scripting API) 12:19:41 s/8. /8/ 12:19:57 s/8The/8. The/ 12:20:14 s/8. ./8./ 12:20:45 [[ 12:20:46 Promise invokeAction(DOMString actionName, 12:20:46 optional InteractionInput params = null, 12:20:46 optional InteractionOptions options = null); 12:20:47 ]] 12:22:28 JKRhb has joined #wot-script 12:22:59 zk: we can have this kind of pattern for Scripting API itself without any conflicts 12:23:12 present+ Jan_Romann 12:24:10 dp: the question is the possibility of another possible action to be defined other than some simple actions 12:24:46 ... only specifying the name of action might not be sufficient 12:25:57 ... we can't tell whether the target action is a single one or a set of multiple ones 12:26:48 q+ 12:29:16 kaz: for example, ECHONET defines history and grouping 12:29:55 ... if we think about sync/async and cancellation of actions, probably we should consider those capabilities as well 12:31:01 ... ECHONET doesn't ask us, WoT WG, to extend TD with those capabilities at the moment 12:31:04 q+ 12:31:20 ... but there is a possibility they will give us some more use cases for that direction 12:31:21 ack k 12:31:55 ... anyway, we (Scripting TF) should collaboratively work with the TD TF for further extensions 12:32:02 ... based on concrete use cases 12:32:10 ... but that should be done for the next version 12:32:16 ack j 12:32:53 jr: maybe this approach of querying actions for cancellation would be related to subscription of events 12:35:24 dp: what if I invoked the same action twice and would cancel only one of them? 12:35:26 q+ 12:36:10 zk: we have to have a notation to distinguish it 12:38:08 ... technically, we can add an ID to distinguish it for the API 12:40:33 kaz: again, this topics is a bigger issue to be handled by a TF, e.g., the Scripting TF or the TD TF 12:41:11 ... if we really want to think about this direction, we should once clarify a dedicated use case description which requires this direction 12:41:41 ... and then think about how to deal with the requirements based on the use case for Architecture, TD, Scripting API, etc. 12:43:31 ... because we need to define an ID to identify an action from others, manage the history of actions, a session to be rolled back at once, etc. 12:43:36 zk: right 12:43:46 subtopic: Issue 354 12:44:09 -> https://github.com/w3c/wot-scripting-api/issues/354 Issue 354 12:44:22 s/Issue 354/Issue 354 - Conformance section necessity/ 12:44:42 dp: need discussion during the Editors call 12:45:09 topic: Next call 12:45:40 dp: as confirmed at the beginning, there will no Scripting call next Monday, March 14, due to the PlugFest 12:46:09 ... we'll have the next Scripting Call on March 21 12:46:17 [adjourned] 12:46:23 rrsagent, make log public 12:46:28 rrsagent, draft minutes 12:46:28 I have made the request to generate https://www.w3.org/2022/03/07-wot-script-minutes.html kaz 14:21:48 Mizusima has left #wot-script 14:45:28 zkis has joined #wot-script 15:00:04 Zakim has left #wot-script 15:03:40 JKRhb has joined #wot-script 16:18:28 zkis has joined #wot-script 16:23:59 zkis_ has joined #wot-script