09:57:07 RRSAgent has joined #wot-script 09:57:12 logging to https://www.w3.org/2025/03/05-wot-script-irc 09:58:28 meeting: WoT Scripting API 09:58:33 present+ Kaz_Ashimura 09:58:41 rrsagent, make log public 09:58:46 rrsagent, draft minutes 09:58:47 I have made the request to generate https://www.w3.org/2025/03/05-wot-script-minutes.html kaz 10:03:33 present+ Cristiano_Aguzzi, Tomoaki_Mizushima 10:03:53 Mizushima has joined #wot-script 10:04:57 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#March_05%2C_2025 10:05:16 present+ Daniel_Peintner 10:05:47 dape has joined #wot-script 10:05:59 q+ 10:06:56 q- 10:07:25 chair: Cristiano 10:07:59 scribenick: kaz 10:08:22 topic: Minutes 10:08:22 -> https://www.w3.org/2025/02/19-wot-script-minutes.html Feb-19 10:08:45 ca: (goes through the minutes) 10:09:12 approved 10:09:33 topic: Calendar 10:09:42 kaz: (mentions DST changes) 10:09:47 topic: PRs 10:10:12 subtopic: PR 561 10:10:25 cris has joined #wot-script 10:10:29 -> https://github.com/w3c/wot-scripting-api/pull/561 PR 561 - Extended return type of invokeAction() 10:10:39 dp: (gives summary) 10:11:43 ... addition around ActionInteractionOutput 10:12:07 ... InteractionOptions for query is optional 10:12:15 ... also for cancel 10:13:05 ... (shows inex.d.ts) 10:13:47 ... the change here is minimum 10:14:29 ... (also revisit his comments last week) 10:14:30 q? 10:14:39 -> https://github.com/w3c/wot-scripting-api/pull/561#issuecomment-2681596255 Daniel's comments last week 10:14:51 ... inline with the comments above 10:14:58 ca: mixed feeling here... 10:15:05 ... what is the use case? 10:15:23 ... wondering why we get errors 10:15:31 dp: good point 10:15:39 JKRhb has joined #wot-script 10:15:42 ... if I query something, that can fail 10:15:55 ca: we can remove it then? 10:16:06 dp: ok 10:16:19 ca: let's see others' comments too 10:16:22 present+ Jan_Romann 10:16:27 rrsagent, daft minutes 10:16:27 I'm logging. I don't understand 'daft minutes', kaz. Try /msg RRSAgent help 10:16:44 s/rrsagent, daft minutes/ 10:16:48 rrsagent, draft minutes 10:16:49 I have made the request to generate https://www.w3.org/2025/03/05-wot-script-minutes.html kaz 10:17:47 ... having InteractionOptions optional itself is fine, but what about input? 10:17:59 dp: there is InteractionInput as well 10:18:13 ... originally started with InteractionInput 10:18:23 ... and was wondering if we need both 10:18:40 ca: that surprises me too... 10:18:44 rrsagent, draft minutes 10:18:45 I have made the request to generate https://www.w3.org/2025/03/05-wot-script-minutes.html kaz 10:19:01 ... we should be consistent 10:19:26 ... why do we want to have query, etc.? 10:19:36 ... (goes through the Editor's Draft) 10:20:12 -> https://w3c.github.io/wot-scripting-api/#the-interactionoptions-dictionary WoT Scripting API Editor's Draft - 8.12 The InteractionOptions dictionary 10:20:16 rrsagent, draft minutes 10:20:18 I have made the request to generate https://www.w3.org/2025/03/05-wot-script-minutes.html kaz 10:20:28 dp: not sure if we really need both 10:21:09 ... two possibilities here... 10:21:37 ... was not really sure which way would be better 10:22:20 ca: anyway, the API should be consistent with the other APIs 10:22:23 q+ 10:22:31 ack jk 10:22:40 jr: also wondering about that 10:23:08 ... this InteractionOptions for query() 10:23:22 ... we can indicate which form to be used 10:23:26 ca: you're right 10:23:34 ... but something is missing by the TD spec 10:24:06 dp: on one hand, we have formIndex 10:24:26 ... at the moment, we don't need the status 10:24:51 ... both query() and cancel() are optional 10:25:00 jr: ok 10:25:42 ca: can afford with the same algorithm 10:26:14 ... we don't know about the actual protocol, so wondering about the cancel() 10:26:25 s/the ca/ca/ 10:26:31 dp: maybe to be aligned 10:26:55 s/aligned/aligned with stop() from Subscription/ 10:27:20 ... here, InteractionOptions for stop() is also optional 10:27:41 ca: we have to review the method carefully 10:27:53 ... can you check it for the TD spec as well? 10:28:01 dp: let me see... 10:28:54 -> https://w3c.github.io/wot-thing-description/ Web of Things (WoT) Thing Description - Next (Editor's Draft) 10:29:10 ca: open issue there 10:29:23 dp: issue with the data model to me 10:29:34 ca: let's double check the issue with the TD TF 10:30:15 -> https://w3c.github.io/wot-thing-description/#table-vocabulary-terms-in-eventaffordance-level TD spec (Editor's Draft) - Table 7: Vocabulary Terms in EventAffordance Level 10:31:02 ca: this could be an issue for TD as well 10:31:33 dp: the name is also being reused, e.g., for stop() 10:31:45 ca: right 10:31:52 q+ 10:31:53 q? 10:31:56 q+ 10:32:20 ... this is a bug or missing feature of the Scripting API spec 10:32:41 jr: wondering about the interface 10:33:01 ... data can't be defined for the properties 10:33:10 ca: right 10:33:22 dp: maybe we could split it 10:33:34 ca: possibly could use sub interface? 10:33:56 jr: wondering if we should use the same mechanism for both 10:34:15 ca: it's rather an issue of the TD spec, I think 10:34:23 ack j 10:34:44 kaz: what should be the next step then? 10:34:51 ... should we bring this to the TD TF? 10:35:05 ca: yeah, would create an issue for TD 10:35:08 ack k 10:35:21 kaz: ok. tx! 10:35:44 dp: will update the PR based on the feedback today 10:36:00 ca: and then I'll create an issue for TD 10:36:06 rrsagent, draft minutes 10:36:08 I have made the request to generate https://www.w3.org/2025/03/05-wot-script-minutes.html kaz 10:36:49 topic: Issues 10:37:08 subtopic: Issue 566 10:37:10 https://github.com/w3c/wot-scripting-api/issues/566 10:37:27 s|https://github.com/w3c/wot-scripting-api/issues/566|-> https://github.com/w3c/wot-scripting-api/issues/566 Issue 566 - [Use-case] WoT in the Browser| 10:37:52 q? 10:38:01 ca: we should support WoT in the browser in general 10:38:59 q+ 10:39:05 q+ 10:39:40 dape: we all agreed based served as an external library (at the beginning) 10:40:12 ... if browser vendors are interested themselves in native implementation, that would be great, though 10:40:21 ca: right 10:40:26 ack dape 10:40:43 ... also would be nice for us to capture problems with the Scripting API beforehand 10:41:45 kaz: agree 10:41:55 ... we should clarify what to be done as the WoT WG as a whole 10:41:57 q- 10:44:43 ca: (adds some more comments to the issue) 10:45:30 ... we're aligned with Ben's comments 10:46:05 ... the question is not just about the WoT Scripting API but the whole WoT including TD and Discovery 10:46:38 -> https://github.com/w3c/wot-scripting-api/issues/566#issuecomment-2700545661 Cristiano's comments 10:47:40 subtopic: Issue 567 10:48:04 -> https://github.com/w3c/wot-scripting-api/issues/567 Issue 567 - [TD] Consequence of contentType being optional 10:48:22 rrsagent, draft minutes 10:48:23 I have made the request to generate https://www.w3.org/2025/03/05-wot-script-minutes.html kaz 10:48:45 ca: we need to handle this for TD 2.0. right? 10:49:23 ... after clarifying what to be done for TD 1.1 10:49:54 ... let's wait for TD updates 10:50:36 dp: maybe we need to add some statement about our stance 10:50:56 ca: (adds some comments about that to issue 567) 10:51:24 dp: the PR Jan created is only about response at the moment 10:51:46 q+ 10:52:20 -> https://github.com/w3c/wot-thing-description/pull/2081 TD PR 2081 - Make contentType optional in ExpectedResponse and AdditionalExpectedResponse classes 10:52:40 jr: there is no schema 10:53:22 s/schema/schema for Discovery/ 10:53:42 rrsagent, draft minutes 10:53:44 I have made the request to generate https://www.w3.org/2025/03/05-wot-script-minutes.html kaz 10:53:50 [adjourned] 10:53:50 rrsagent, draft minutes 10:53:51 I have made the request to generate https://www.w3.org/2025/03/05-wot-script-minutes.html kaz 11:23:26 JKRhb has joined #wot-script 11:55:17 JKRhb has joined #wot-script 12:08:16 JKRhb has joined #wot-script 12:08:40 JKRhb_ has joined #wot-script 12:57:42 JKRhb has joined #wot-script 13:05:00 Zakim has left #wot-script 13:06:29 mahda has joined #wot-script 13:59:57 JKRhb has joined #wot-script 15:04:53 JKRhb has joined #wot-script 15:05:17 mahda has joined #wot-script 15:05:36 JKRhb has joined #wot-script 16:49:57 JKRhb has joined #wot-script 17:21:41 JKRhb has joined #wot-script 17:53:02 JKRhb has joined #wot-script 18:09:24 JKRhb has joined #wot-script 18:24:51 JKRhb has joined #wot-script 18:51:33 JKRhb has joined #wot-script 19:07:54 JKRhb has joined #wot-script 19:23:19 JKRhb has joined #wot-script 19:52:33 JKRhb has joined #wot-script 20:08:55 JKRhb has joined #wot-script 20:24:22 JKRhb has joined #wot-script 20:53:35 JKRhb has joined #wot-script 21:09:57 JKRhb has joined #wot-script 21:25:23 JKRhb has joined #wot-script 21:54:35 JKRhb has joined #wot-script 22:10:56 JKRhb has joined #wot-script 22:26:23 JKRhb has joined #wot-script 22:55:35 JKRhb has joined #wot-script 23:11:57 JKRhb has joined #wot-script 23:27:29 JKRhb has joined #wot-script 23:55:13 JKRhb has joined #wot-script