08:59:40 RRSAgent has joined #wot-script 08:59:45 logging to https://www.w3.org/2025/05/14-wot-script-irc 08:59:46 meeting: WoT Scripting API 09:02:13 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#May_14%2C_2025 09:02:13 cris has joined #wot-script 09:03:18 present+ Kaz_Ashimura, Cristiano_Aguzzi 09:03:23 chair: Cristiano 09:05:58 present+ Tomoaki_Mizushima 09:08:16 dape has joined #wot-script 09:08:54 present+ Daniel_Peintner 09:09:11 scribe: dape 09:09:32 TOPIC: Previous minutes 09:09:45 -> https://www.w3.org/2025/03/05-wot-script-minutes.html Mar-5 09:10:04 CA: Found minor typo 09:10:04 q+ 09:11:05 Kaz: fixing 09:11:13 ack k 09:11:14 CA: I think we can approve the minutes 09:11:18 ... minutes are approved 09:11:26 TOPIC: PRs 09:11:39 SUBTOPIC: PR 561 09:11:44 -> https://github.com/w3c/wot-scripting-api/pull/561 09:11:58 CA: I think the interface looks good 09:12:10 ... and can start changing the prose 09:12:45 ... new shape 09:13:01 s/fixing/fixed/ 09:13:01 ... ActionInteractionOutput 09:13:09 ... 2 new functions 09:13:19 ... cancel and query 09:13:39 s|https://github.com/w3c/wot-scripting-api/pull/561|https://github.com/w3c/wot-scripting-api/pull/561 PR 561 - Extended return type of invokeAction()| 09:13:43 rrsagent, make log public 09:13:49 rrsagent, draft minutes 09:13:50 I have made the request to generate https://www.w3.org/2025/05/14-wot-script-minutes.html kaz 09:13:57 ... we cannot do everything right now.. need to wait for TD to improrve 09:14:11 ... async vs sync actions 09:14:20 CA: What should we do if not async 09:14:39 scribenick: cris 09:14:52 dape: we can have two options: throw or no-op 09:14:55 DP: 2 options 09:15:03 ... throwing or no-op 09:15:17 ... I tend to throw 09:15:32 CA: cancel is easy.. void function 09:16:14 ... query more difficult.. need to decide what to return 09:17:29 ... opened issue on TD side... issue 2068 09:18:30 -> https://github.com/w3c/wot-thing-description/issues/2068 related TD Issue 2068 - Specify the result of queryaction operation 09:19:40 DP: wonder the pros and cons? 09:20:05 CA: No async term in TD possible 09:22:49 DP: sync could return the previously reported value and cancel a no-op 09:22:56 CA: requires buffering 09:23:12 ... plus it could be a different value for query 09:25:54 rrsagent, draft minutes 09:25:55 I have made the request to generate https://www.w3.org/2025/05/14-wot-script-minutes.html kaz 09:26:21 q+ 09:26:33 09:27:10 DP: Could also check whether in the Web space there are such cases already... 09:28:01 zkis has joined #wot-script 09:28:15 present+ Zoltan_Kis 09:28:15 Kaz: Technically, we can summarize our questions in more details 09:28:24 ... and ask TAG for feedback 09:28:38 CA: Makes sense, thanks! 09:29:09 i/2 options/scribenick: dape/ 09:29:12 rrsagent, draft minutes 09:29:13 I have made the request to generate https://www.w3.org/2025/05/14-wot-script-minutes.html kaz 09:29:22 ack k 09:30:07 ZK: Up to the underlying platform... 09:30:16 ... we should avoid giving no details 09:30:25 ... we should be transparent 09:31:28 ... failing is the better approach 09:32:14 CA: Corner cases in TD not specifying terms 09:32:36 ZK: I can get errors in Promise if there are problems anyway 09:33:08 DP: Can try to integrate the discussions.. 09:33:18 TOPIC: Issues 09:33:53 SUBTOPIC: Issue 571 - Sync schemas is now outdated 09:33:57 -> https://github.com/w3c/wot-scripting-api/issues/571 09:34:31 CA: At the moment sync is not working anymore 09:34:40 Mizushima has joined #wot-script 09:35:17 ... moreover GitHub stops action after some time 09:35:30 s|https://github.com/w3c/wot-scripting-api/issues/571|https://github.com/w3c/wot-scripting-api/issues/571 Issue 571 - Sync schemas is now outdated| 09:35:32 ... I will update the action 09:35:59 .... plan to just update the reference, https://github.com/w3c/wot-resources 09:36:07 q+ 09:36:43 Kaz: I am okay with the resolution 09:36:57 ... should use a specific label 09:37:09 ... like "GitHub" or so 09:38:58 s/"GitHub"/"Logistics", "GitHub problem"/ 09:39:00 s/"GitHub"/"logistics" 09:39:50 q+ 09:39:54 q- 09:40:49 DP: wot-resources is the final TD .. while we used the "live" version of the JSON schema 09:40:52 CA: Correct 09:41:03 ... should try to use the final version 09:41:17 ... and align it as much as we can 09:41:36 ... in the TD 2.0 work we might need to update the resources 09:41:52 q? 09:41:54 ack dape 09:42:49 SUBTOPIC: Issue 570 - Looking into Deno 09:42:53 -> https://github.com/w3c/wot-scripting-api/issues/570 09:43:01 CA: Reminder from main call 09:43:24 ... what do we want to do? 09:44:15 s|https://github.com/w3c/wot-scripting-api/issues/570|https://github.com/w3c/wot-scripting-api/issues/570 Issue 570 - Looking into Deno| 09:44:19 rrsagent, draft minutes 09:44:21 I have made the request to generate https://www.w3.org/2025/05/14-wot-script-minutes.html kaz 09:44:27 DP: Recalling Luca mentioning it was not working at that time 09:44:29 CA: Yes, tried together with Luca 09:45:00 ... we should give it a try with node-wot 09:45:23 ... closing the issue in Scripting? 09:47:11 ... BTW we have Bun as runtime also 09:49:16 SUBTOPIC: Issue 569 - Subscription stop misses InteractionInput 09:49:19 -> https://github.com/w3c/wot-scripting-api/issues/569 09:49:57 CA: TD misses the payload information 09:50:07 s|https://github.com/w3c/wot-scripting-api/issues/569|https://github.com/w3c/wot-scripting-api/issues/569 Issue 569 - Subscription stop misses InteractionInput ?| 09:50:45 CA: Do we need optional InteractionInput ? 09:51:38 DP: second optional parameter? 09:51:51 CA: Yes, but the pattern is used often enough 09:52:13 rrsagent, draft minutes 09:52:14 I have made the request to generate https://www.w3.org/2025/05/14-wot-script-minutes.html kaz 09:53:11 DP: issue with existing parameter... creates issue with backwards compatibility .. if we put it as first parameter 09:53:22 CA: Yes... 09:55:05 ... or break compatibility since we are still in the explorative version 09:56:33 CA: let's wait for feedback from others 09:56:57 SUBTOPIC: Issue 539 - ObserveProperty with uri vars 09:57:01 -> https://github.com/w3c/wot-scripting-api/issues/539 09:57:13 CA: This is a plain bug 09:57:48 ... same event with parameter 09:58:27 ... instead of 1 listener per event we should have 1 listener per event&uriParameter 09:58:50 ZK: Should be an option 09:59:27 ... why the constraint to have at most one listener at all 09:59:57 q+ 10:00:39 CA: Good point 10:01:04 ... map to allow multiple subscriptions? 10:01:41 ZK: Instead of single slot we would (should?) have a list or map 10:03:44 s|https://github.com/w3c/wot-scripting-api/issues/539|https://github.com/w3c/wot-scripting-api/issues/539 Issue 539 - ObserveProperty with uri vars| 10:03:46 rrsagent, draft minutes 10:03:48 I have made the request to generate https://www.w3.org/2025/05/14-wot-script-minutes.html kaz 10:03:54 q+ 10:06:02 ack d 10:06:04 ack k 10:06:13 DP: should do an analysis why we made this decision at that time 10:06:23 CA: Need to look into more closely 10:06:30 [adjourned] 10:06:34 rrsagent, draft minutes 10:06:35 I have made the request to generate https://www.w3.org/2025/05/14-wot-script-minutes.html kaz 12:29:08 Zakim has left #wot-script