12:06:59 RRSAgent has joined #wot-script 12:07:03 logging to https://www.w3.org/2024/01/22-wot-script-irc 12:07:07 topic: Minutes 12:07:08 https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#January_22.2C_2024 12:07:11 scribe: zkis 12:07:23 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#January_22.2C_2024 12:07:29 chair: Cristiano 12:07:45 present+ Kaz_Ashimura, Cristiano_Aguzzi, Zoltan_Kis, Tomoaki_Mizushima 12:08:33 Topic: previous minutes 12:08:49 https://www.w3.org/2024/01/15-wot-script-minutes.html 12:09:01 s/https/-> https/ 12:09:07 s/html/html Jan-15/ 12:09:18 s/topic: Minutes// 12:10:13 CA: no complaints, minutes approved. 12:10:30 Topic: scheduling the calls 12:10:47 CA: we have discussed cancellations for public holidays in 2024 12:11:23 i|we have|-> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations_and_Schedule_Updates Cancellations on the WoT main wiki| 12:11:29 rrsagent, make log public 12:11:33 rrsagent, draft minutes 12:11:34 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:11:41 CA: Feb 12 is holiday 12:12:07 CA: we will cancel the call on Feb 12 12:12:57 CA: we discussed possible biweekly schedule 12:13:16 meeting: WoT Scripting API 12:13:26 ... once we finish reviewing the current issues, we can (experimentally) move to biweekly calls 12:14:14 Topic: PRs 12:14:30 CA: no updates here, still needs work, will skip for now. 12:14:36 Topic: issues 12:15:02 CA: we can tag with "next-iteration" some of the issues 12:15:51 subtopic: Issue 529 12:15:53 -> https://github.com/w3c/wot-scripting-api/issues/529 Issue 529 12:15:56 dape has joined #wot-script 12:15:57 Subtopic: issue 529 12:16:14 s/Issue 529/Issue 529 - Clean-up Scripting API wiki page/ 12:16:29 s|Subtopic: issue 529|| 12:16:35 present+ Daniel_Peintner 12:16:41 rrsagent, draft minutes 12:16:42 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:16:48 CA: summarizing the development so far: archiving old stuff, follow other task forces best practices 12:17:20 CA: Daniel asked if should we remove Stash section, I agree 12:17:28 DP: yes, it's old and outdated 12:18:28 q+ 12:19:04 ack k 12:19:07 KA: removing Stash is OK, but the Scripting TF should also align project management with the other TFs 12:19:57 CA: removed, closing the issue. 12:20:09 Subtopic: issue 488 12:21:16 https://github.com/w3c/wot-scripting-api/issues/488 12:21:51 s/https/-> https/ 12:21:58 s/488/488 Issue 488 - Use a different tag for unstable npm packages/ 12:21:59 CA: we should switch to date based tags 12:22:19 CA: after publishing 1.1.0 12:22:30 https://www.npmjs.com/package/wot-thing-description-types 12:23:40 q+ 12:24:08 DP: only for TD and Thing Models 12:24:15 ThindModel on NMP, https://www.npmjs.com/package/wot-thing-model-types 12:24:24 ack kaz 12:24:29 s/ThindModel/ThingModel 12:24:58 q+ 12:25:07 KA: Ege is working on similar things for the TD and MMc for discovery, so we should join those calls and discuss 12:25:11 ... also in the main call 12:26:32 DP: agree we should follow what TD TF is using, but the Scripting API had somewhat different tradition 12:26:33 Scripting API on NPM, https://www.npmjs.com/package/wot-typescript-definitions 12:27:16 DP: all breaking changes bump the version 12:27:36 q? 12:27:40 ack dape 12:27:42 ack dape 12:28:08 q+ 12:28:43 DP: not sure about the "pre-" prefix, needs discussion 12:28:46 ack dape 12:28:47 ack dape 12:30:09 Suptopic: issue 224 12:30:36 https://github.com/w3c/wot-scripting-api/issues/224 12:31:02 s/https/-> https/ 12:31:11 s/224/224 Issue 224 - Scripting API versioning/ 12:31:14 q+ 12:32:26 KA: if all topics have been discussed here, we can close this 12:32:42 CA: yes, the strict points have been addressed by using tags 12:33:04 KA: but I agree we could keep the issue to track similar version management related issues 12:33:37 present+ Jan_Romann 12:34:01 Topic: issue 528 12:34:10 https://github.com/w3c/wot-scripting-api/issues/528 12:34:25 s|https://github.com/w3c/wot-scripting-api/issues/528|-> https://github.com/w3c/wot-scripting-api/issues/528 Issue 528 - Add support for URI variables to exploreDirectory method| 12:34:27 JR: no updates on this for now, needs more work 12:34:36 rrsagent, draft minutes 12:34:38 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:35:16 Topic: issue 352 12:35:17 https://github.com/w3c/wot-scripting-api/issues/352 12:35:31 CA: about possible ideas for the next charter 12:35:53 ... but if those topics all have issues, we can close this 12:35:55 s/https/-> https/ 12:36:04 s/352/352 Issue 352 - Next charter topics/ 12:36:07 rrsagent, draft minutes 12:36:08 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:36:14 CA: created issues for the missing ones 12:36:15 ... so we can close this one 12:36:18 +1 12:37:03 DP: agree 12:37:43 Topic: issue 396 12:37:55 https://github.com/w3c/wot-scripting-api/issues/396 12:38:13 JKRhb has joined #wot-script 12:38:19 s/https/-> https/ 12:38:30 s/396/396 Issue 396 - The future of the conformance class WoT Discovery/ 12:38:38 DP: things changed since the issue was filed, fine with closing it 12:38:53 q+ 12:39:04 ack k 12:39:05 q+ 12:39:45 JR: it was a discussion if conformance classes are needed at all, but consensus was reached and it can be closed now 12:40:04 ... the general direction is clear now 12:40:39 q? 12:40:43 ack JK 12:40:46 ack kaz 12:41:06 q+ 12:41:35 KA: based on the title, we can handle this as a future issue, if Daniel decides to keep it 12:42:21 ... so label it accordingly 12:42:44 Subtopic: issue 313 12:42:49 https://github.com/w3c/wot-scripting-api/issues/313 12:43:04 s/https/-> https/ 12:43:13 s/313/313 Issue 313 - ThingDescription TaskForce related issues/ 12:44:10 ZK: it's basically a label, not an issue 12:44:23 CA: we can close it 12:44:30 q+ 12:44:50 DP: this was just meant as a management issue 12:44:57 ack dape 12:46:11 CA: so does it make sense to keep it? 12:46:26 ... closing. 12:46:43 Topic: issue 204 12:47:23 https://github.com/w3c/wot-scripting-api/issues/204 12:47:24 CA: there is a newer issue about this 12:47:36 https://github.com/w3c/wot-scripting-api/issues/527 12:47:59 CA: so we can supercede the old issue with the new one 12:48:00 s/https/-> https/ 12:48:10 s/204/204 Issue 204 - Extend API with semantic capabilities/ 12:48:24 rrsagent, draft minutes 12:48:25 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:48:32 Subtopic: issue 226 12:48:32 https://github.com/w3c/wot-scripting-api/issues/226 12:49:02 CA: this comes from old WoT issue 50 12:49:10 s|https://github.com/w3c/wot-scripting-api/issues/204|-> https://github.com/w3c/wot-scripting-api/issues/204| 12:49:11 rrsagent, draft minutes 12:49:13 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:49:25 CA: we have a discussion in another issue 222 12:49:42 CA: so we supercede this issue with the new one 12:49:54 ... and close this one. 12:49:57 s/527/527 Issue 527 - Semantic ConsumedThing part of Scripting API/ 12:50:23 s|https://github.com/w3c/wot-scripting-api/issues/226|-> https://github.com/w3c/wot-scripting-api/issues/226 Issue 226 - ThingFilter server attribute - Issue 50 from w3c/wot| 12:50:55 i|so we|-> https://github.com/w3c/wot-scripting-api/issues/222 Issue 222 - Possible alternative design of Discovering API| 12:50:58 Subtopic: issue 206 12:51:12 CA: already reviewed by Jan 12:51:24 https://github.com/w3c/wot-scripting-api/issues/206 12:51:39 CA: is there any things still to be done here? 12:52:05 s|https://github.com/w3c/wot-scripting-api/issues/206|| 12:52:12 CA: Zoltan should review it and close it eventually. 12:52:25 i|already review|-> https://github.com/w3c/wot-scripting-api/issues/206 Issue 206 - Clarify Discovery API scope| 12:52:30 rrsagent, draft minutes 12:52:31 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:52:45 https://github.com/w3c/wot-scripting-api/labels/for%20next%20iteration 12:52:53 Subtopic: issues for next iteration 12:52:58 https://github.com/w3c/wot-scripting-api/labels/for%20next%20iteration 12:53:07 CA: please review 12:53:22 s|https://github.com/w3c/wot-scripting-api/labels/for%20next%20iteration|-> https://github.com/w3c/wot-scripting-api/labels/for%20next%20iteration Issues for the next iteration| 12:53:36 rrsagent, draft minutes 12:53:37 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:53:43 CA: assigned the priority-high label to those which affect implementations 12:53:53 ... some still wait on the TD task force 12:54:44 ... added the label use-case if use cases can be extracted 12:55:07 ... after reviewing we can draft a plan on how to handle them 12:55:14 ... will contact Ege about TD related issues 12:55:33 ... so please review these issues 12:56:57 CA: with that we can close the call for now 12:57:09 CA: AOB? 12:57:18 JR: call next week? 12:57:24 CA: yes 12:58:15 adjourned 12:58:19 rrsagent, draft minutes 12:58:21 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 12:58:37 i/AOB/topic: AOB/ 12:58:39 rrsagent, draft minutes 12:58:40 I have made the request to generate https://www.w3.org/2024/01/22-wot-script-minutes.html kaz 14:07:30 zkis_ has joined #wot-script 14:59:57 Zakim has left #wot-script