10:58:57 RRSAgent has joined #wot-script 10:58:57 logging to https://www.w3.org/2022/10/10-wot-script-irc 10:59:15 zkis has joined #wot-script 11:00:44 meeting: WoT Scripting API 11:01:16 present+ Kaz_Ashimura, Jan_Romann, Zoltan_Kis 11:01:24 dape has joined #wot-script 11:03:40 present+ Daniel_Peintner 11:04:32 present+ Cristiano_Aguzzi 11:04:36 cris_ has joined #wot-script 11:06:43 JKRhb has joined #wot-script 11:07:34 scribe: zkis 11:07:55 Mizushima has joined #wot-script 11:08:01 Agenda: 11:08:16 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#October_10.2C_2022 11:08:26 Previous minutes 11:08:39 s/Agenda:/topic: Agenda/ 11:08:44 -> September-26 -> https://www.w3.org/2022/09/26-wot-script-minutes.html 11:08:51 s/Previous/topic: Previous/ 11:09:00 present+ Tomoaki_Mizushima 11:09:21 zakim, who is on the call? 11:09:21 Present: Kaz_Ashimura, Jan_Romann, Zoltan_Kis, Daniel_Peintner, Cristiano_Aguzzi, Tomoaki_Mizushima 11:10:19 No objections, minutes approved. 11:10:54 rrsagent, make log public 11:11:03 Topic: quick updates 11:11:20 DP: we discussed changing the document so that the Note could also include normative statements 11:11:38 q+ 11:11:41 DP: wondering if there are any pushback from W3C 11:11:46 ack kaz 11:12:29 KA: the process doc defines just Rec track. Note track doc may include normative statements. 11:13:02 ... anyway, we needed to clarify the status of Scripting in the new WG charter 11:14:08 KA: not yet discussed with Philip 11:14:50 ... he will ask on the WoT WG decision, so we did need the group resolution on that 11:15:01 DP: yes, we have that 11:15:54 KA: we should prepare for comments from other W3C members 11:15:54 a/Philip/Philippe/ 11:16:59 KA: I am not sure why we want a normative Note, since that would require AC review, comments, etc. Should we try to make the Scripting to make normative Rec track doc again? 11:18:01 DP: we need the normative statements, but we don't need to go to Rec 11:18:25 ... we are still in the exploratory phase, the API is not stable 11:18:40 ... maybe in the future, but not sure about that yet 11:18:41 q? 11:20:18 ZK: does it mean we can only use MUST, SHALL, etc with AC reviews? 11:20:35 KA: no, I just meant a normative deliverable for Scripting 11:22:18 q+ 11:22:21 ZK: we can stick to the group decision already made 11:22:50 DP: so far it has been accepted that we use normative statements 11:22:54 ack cris 11:23:07 CA: I also think we should stick with the group decision 11:23:30 ... if all goes well, we might end up in the Rec track, but for now we can stay in the current state 11:24:19 Subtopic: Wot Profile test fest 11:24:42 DP: if anyone was present, any takeaways for Scripting? 11:24:50 q+ 11:24:59 ack cris 11:25:18 CA: I joined nearly all calls 11:25:26 q+ 11:25:28 ... the general feeling is that Profile is not mature enough yet 11:25:39 ... but they will try to finish it in the next months 11:25:51 ... there was some implementation attempt, not yet finished 11:25:56 ... some tests as well 11:26:06 CA: no dependencies for Scripting 11:26:20 ... we might look into action operations which we don't support 11:26:27 ... maybe we should look into that 11:26:33 ack kaz 11:26:51 KA: look into the minutes of the test fest 11:26:59 (link) 11:27:46 q? 11:27:59 KA: some takeaways for TD, Michael McCool will summarize the findings in this week's calls (discovery, profile, architecture, ...) 11:28:25 DP: thank you for the summaries 11:28:53 DP: CA's point (query action) is something we should do in the next charter 11:29:21 ... the TD needs to improve wrt the OP values and align with Profiles 11:29:35 ... so cancel/query actions are underspecified 11:29:49 ... after that is solved, we can update the Scripting API 11:30:00 ... but it will likely go into the next charter period 11:30:19 ... since it also needs a plugfest where we can test those ideas 11:30:36 rrsagent, make log public 11:30:40 rrsagent, draft minutes 11:30:40 I have made the request to generate https://www.w3.org/2022/10/10-wot-script-minutes.html kaz 11:30:49 Topic: pull requests 11:31:05 Subtopic: PR432 11:31:20 -> https://github.com/w3c/wot-scripting-api/pull/432 11:31:49 DP: fixes a typo 11:32:38 ... we discussed to use "empty" without emphasis 11:33:06 +1 11:33:07 DP: can we merge? 11:33:32 s|432|432 PR 432 - refactor: fix/remove emphasised empty #432| 11:33:37 Subtopic: PR431 11:33:39 -> https://github.com/w3c/wot-scripting-api/pull/431 11:34:12 DP: fixes a typo 11:34:20 Merged. 11:34:39 Subtopic: PR434 11:34:42 -> https://github.com/w3c/wot-scripting-api/pull/434 11:35:19 Jan: last time we discussed to move out some changes to a new PR 11:35:39 Jan: this could clear the way for accepting the other PR 11:36:08 DP: are these dependent? 11:36:21 Jan: no, they are independent and should be discussed separately, hence the new PR 11:36:51 q+ 11:37:20 Jan: so PR 405 could be taken further 11:37:35 s|434|434 PR 434 - feat: adjust ThingFilter interface| 11:38:00 -> https://github.com/w3c/wot-scripting-api/pull/405 PR 405 - feat!: add new Discovery Web IDL definitions| 11:38:16 q? 11:39:49 CA: there are some mistakes, like if the filters are now mandatory 11:40:31 CA: I agree we move the async iterator forward and discuss the rest later 11:41:07 ... maybe we should move that line out as well (which removes optional from the filter arg) 11:41:24 ... apart from that we can merge the async iterator change 11:41:34 Jan: OK, the PR is updated 11:42:32 DP: nice - in rest, the PR has been reviewed, so we could merge that 11:44:43 PR 405 merged 11:44:52 q? 11:44:55 ack cris 11:45:19 CA: we can handle the rest in the new PR 11:46:02 Topic: Issues 11:46:12 Subtopic: issue 433 11:46:14 -> https://github.com/w3c/wot-scripting-api/issues/433 11:46:35 DP: it's about what to publish in the current charter 11:47:03 s|433|433 Issue 433 - New publication within current charter?| 11:47:18 q+ 11:47:29 DP: I think we should make a release 11:47:34 ack zkis 11:47:35 q+ 11:48:23 ack cris 11:48:36 zkis: the async iterator is enough reason to publish 11:48:52 DP: yes, but we should not update the OP values 11:49:25 CA: I agree with this. We should also finalize the Discovery chapter to align with the Discovery TF. 11:49:34 ... also, update node-wot 11:49:47 ... after that we can publish 11:50:38 Jan: regarding discovery implementation in node-wot is going well, should be able to finish in next months 11:51:34 q+ 11:51:38 ... also experimented with bootstrapping, security 11:51:44 ack cris 11:51:58 CA: what about test results 11:52:08 Jan: there were some, but need to update them 11:52:20 CA: MMc asked to finalize them 11:52:44 ... security bootstrapping is not specified well 11:54:05 DP: thank you 11:54:19 Subtopic: issue 430 11:54:24 -> https://github.com/w3c/wot-scripting-api/issues/430 11:54:34 DP: we need to rely on dependencies on Bindings spec 11:54:38 ... which is not ready yet 11:55:01 q+ 11:55:09 s|430|430 Issue 430 - Define exact steps/algorithms instead generic references to "Protocol Bindings" spec| 11:55:49 q+ 11:56:11 ack z 11:56:23 zkis: we need to define those algorithms, eventually temporarily in Scripting, then move them to Bindings 11:56:45 ack kaz 11:57:01 KA: we should clarify which portions are to be included in the Bindings spec 11:58:39 ... my suggestion is to discuss with TD spec guys 11:58:43 ... at least in this chapter 11:59:19 ZK: in that case we can keep it in Scripting until the Bindings spec is ready to take them 11:59:50 DP: makes sense 12:00:10 DP: it's also fine to leave it open and wait until properly defined 12:01:02 ZK: should we cover it for HTTP, eventually CoAP? 12:01:18 DP: need to adjourn 12:01:20 call adjourned 12:01:28 rrsagent, draft minutes 12:01:28 I have made the request to generate https://www.w3.org/2022/10/10-wot-script-minutes.html kaz 12:01:50 chair: Daniel 12:01:51 rrsagent, draft minutes 12:01:51 I have made the request to generate https://www.w3.org/2022/10/10-wot-script-minutes.html kaz 12:44:34 Mizushima has left #wot-script 13:07:40 zkis has joined #wot-script 14:23:50 Zakim has left #wot-script