12:02:48 RRSAgent has joined #wot-script 12:02:52 logging to https://www.w3.org/2024/01/15-wot-script-irc 12:02:58 meeting: WoT Scripting API 12:05:25 present+ Kaz_Ashimura, Cristiano_Aguzzi, Jan_Romann, Tomoaki_Mizushima 12:07:00 JKRhb has joined #wot-script 12:07:28 cris__ has joined #wot-script 12:08:05 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#January_15.2C_2024 12:08:31 zkis has joined #wot-script 12:08:41 present+ Zoltan_Kis 12:08:48 topic: Logistics 12:09:14 kaz: maybe you should split the agenda wiki content into several pieces based on the year like the main wiki 12:09:17 ca: agree 12:09:19 topic: Minutes 12:09:35 -> https://www.w3.org/2023/12/11-wot-script-minutes.html Dec-11 12:09:59 approved 12:10:10 topic: PRs 12:10:14 subtopic: PR 524 12:10:34 -> https://github.com/w3c/wot-scripting-api/pull/524 PR 524 - Update text and examples regarding the fetching of TDs 12:10:46 ca: Jan, could you explain? 12:10:52 jr: mostly cleaning up 12:10:59 chair: Cristiano 12:11:29 ... we had discussion around "fetch" 12:12:12 ... explain the rationale at an appendix 12:12:20 ca: let's see the changes 12:13:04 -> https://pr-preview.s3.amazonaws.com/w3c/wot-scripting-api/524/6482a8c...JKRhb:329213a.html diff rendering 12:13:32 jr: wording change 12:13:52 i/wording/kaz: "fetching" converted to "requesting" 12:14:07 ca: (shows Appendiex A.2) 12:14:37 -> https://pr-preview.s3.amazonaws.com/w3c/wot-scripting-api/524/6482a8c...JKRhb:329213a.html#requesting-and-validating-a-td A.2 Requesting and validating a TD 12:14:49 q+ 12:15:22 ack k 12:16:27 kaz: As I mentioned the other day, we should have an Editor's Note describing why we added these changes around section 5.1 (on "Fetching" => "Requesting") 12:16:56 ca: let's merge this PR 524 itself, and then create an issue 12:18:02 dape has joined #wot-script 12:18:29 kaz: that's fine 12:19:10 -> https://github.com/w3c/wot-scripting-api/issues/530 Issue 530 - Improve section 5 12:19:16 subtopic: PR 489 12:19:42 -> https://github.com/w3c/wot-scripting-api/pull/489 PR 489 - Better types for Scripting API 12:19:58 ca: would like to skip this because need some more updates 12:20:05 topic: Issues 12:20:28 subtopic: Issue 529 12:20:42 -> https://github.com/w3c/wot-scripting-api/issues/529 Issue 529 - Clean-up Scripting API wiki page 12:20:56 ca: proposal from Daniel 12:21:22 ... Kaz also mentioned similar ideas at the beginning of this call 12:21:42 dp: like the Marketing wiki 12:22:17 ... the Scripting wiki should have the information only about this year 12:22:33 q+ 12:23:28 q+ 12:23:36 ack dape 12:23:38 ack k 12:24:05 kaz: would suggest we simply one page for one year and put old content to that yearly page 12:24:19 dp: just copy over the old content 12:24:27 ... can do that later offline 12:25:09 resolution: Scripting TF also will put older content to yearly subpages like 2023, 2022, 2021, ... 12:25:43 ca: after Daniel has done that, let's close Issue 529 12:26:01 subtopic: Issue 528 12:26:17 -> https://github.com/w3c/wot-scripting-api/issues/528 Issue 528 - Add support for URI variables to exploreDirectory method 12:26:44 ca: use case description to be written 12:26:57 q+ 12:27:08 ... we can work on the use case description 12:27:14 q? 12:27:16 q+ 12:28:00 jr: wanted to ask if the "Use Case" to be included in the Use Cases document on the wot-usecases repo 12:28:15 q+ 12:29:19 ack j 12:29:21 ack k 12:30:00 kaz: think we as the whole group should start with some Use Case description within the Use Cases document 12:30:14 ... the extract requirements from the use cases 12:30:39 ca: we can make contribution but maybe lower priority 12:31:25 kaz: that kind of policy should be discussed during the use cases call and partly the main call too 12:31:37 dp: agree we should start with the use case description 12:32:18 ... but probably we need to think about use cases handled by the use cases document and another use cases handled by spec TFs 12:32:26 q? 12:32:30 ack d 12:32:53 ca: yeah 12:33:03 ... but don't want to talk about the procedure now 12:33:03 q+ 12:33:43 ... we can propose our ideas to the Use Cases TF 12:33:45 kaz: right 12:33:57 ... so we need to clarify the procedure as the whole WG/IG 12:34:06 ack k 12:35:24 jr: (describes the proposal a bit more) 12:35:46 ... exposed to the user 12:35:59 ... maybe some access limitation would make sense 12:36:37 zk: URI Variables should be optional 12:37:30 ... URI Variables are standardized by HTTPS. right? 12:37:50 ... we should provide some standardized range of the variables too 12:37:55 ca: good point 12:38:07 zakim, who is here? 12:38:07 Present: Kaz_Ashimura, Cristiano_Aguzzi, Jan_Romann, Tomoaki_Mizushima, Zoltan_Kis 12:38:09 On IRC I see dape, zkis, cris__, JKRhb, RRSAgent, Zakim, Mizushima, kaz 12:38:17 present+ Daniel_Peintner 12:38:32 ... want to add a label to this issue 12:39:16 q+ 12:39:21 ... (adds "use case" label) 12:39:57 jr: would like to work on some use case description then 12:40:10 ca: yeah 12:40:28 ... but that depends on the Use Cases TF's activity 12:40:38 q+ 12:40:40 ack j 12:42:47 kaz: the Use Cases TF will restart the day after tomorrow on Wednesday 12:43:06 subtopic: Select important issues 12:43:25 -> https://github.com/w3c/wot-scripting-api/issues remaining issues 12:43:44 ca: would like to skim all the remaining issues again 12:44:09 q+ 12:44:38 ack k 12:46:00 kaz: we should clarify some criteria like a need for actual system implementations and deployment 12:46:22 ... from that viewpoint, issue 200 would be "important" 12:46:25 ca: yeah 12:47:20 kaz: we should record that criteria first before diving into concrete issues 12:47:24 +1 12:47:27 ... resolution on the minutes would be fine 12:50:29 proposal: Scripting TF would like make Issues important ones when they have need for actual system implementation 12:50:57 resolution: Scripting TF would like make Issues important ones when they have need for actual system implementation 12:51:06 rrsagent, make log public 12:51:08 rrsagent, draft minutes 12:51:09 I have made the request to generate https://www.w3.org/2024/01/15-wot-script-minutes.html kaz 12:51:19 subtopic: Issue 200 12:51:34 -> https://github.com/w3c/wot-scripting-api/issues/200 Issue 200 - Error Handling 12:52:12 ca: from the viewpoint of the need for implementations, this is important 12:52:15 kaz: agree 12:52:29 ca: would add a label for "use case" 12:52:51 ... and "priority: high" 12:53:11 subtopic: Issue 352 12:53:27 -> https://github.com/w3c/wot-scripting-api/issues/352 Issue 352 - Next charter topics 12:55:06 ca: would propose to close this issue because this was a generic need and we're already getting new concrete issues 12:55:07 dp: ok 12:56:13 ca: will close this when we've confirmed it's redundant and obsolete 12:56:20 subtopic: Issue 193 12:56:44 -> https://github.com/w3c/wot-scripting-api/issues/193 Issue 193 - Should writeProperty() return a value 12:56:52 ca: a long-standing issue 12:57:28 ... discussion during the TD call in 2021 12:57:56 ... need use case and add "use case" label 12:58:30 q+ 12:59:07 ack k 12:59:50 kaz: what about the next steps? 13:00:06 ca: visiting issues with "for next iteration" label first 13:00:17 ... and then the other remaining issues 13:00:20 kaz: ok 13:00:24 [adjourned] 13:00:29 rrsagent, draft minutes 13:00:30 I have made the request to generate https://www.w3.org/2024/01/15-wot-script-minutes.html kaz 14:01:08 mahda-noura has joined #wot-script 15:07:25 Zakim has left #wot-script