11:06:48 <RRSAgent> RRSAgent has joined #wot-script
11:06:52 <RRSAgent> logging to https://www.w3.org/2024/03/18-wot-script-irc
11:07:15 <kaz> meeting: WoT Scripting API
11:07:36 <kaz> present+ Kaz_Ashimura, Cristiano_Aguzzi, Jan_Romann, Tomoaki_Mizushima
11:08:19 <kaz> scribenick: kaz
11:08:33 <zkis> zkis has joined #wot-script
11:08:38 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#March_18%2C_2024
11:08:41 <kaz> topic: Minutes
11:08:50 <kaz> -> https://www.w3.org/2024/03/04-wot-script-minutes.html Mar-4
11:09:47 <kaz> present+ Zoltan_Kis
11:10:44 <JKRhb> JKRhb has joined #wot-script
11:11:20 <kaz> jr: I had a problem with Firefox for HTML diff last week
11:11:22 <kaz> kaz: fixed
11:11:28 <kaz> rrsagent, make log public
11:11:33 <kaz> rrsagent, draft minutes
11:11:35 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/18-wot-script-minutes.html kaz
11:11:46 <kaz> minutes approved
11:11:59 <kaz> topic: Logistics
11:12:33 <kaz> ca: reminder that (1) Scripting API call is now bi-weekly and (2) US Daylight Saving has started
11:13:28 <kaz> ... we can cancel the call on Apr-1
11:13:56 <kaz> ... then April 8 also due to the AC meeting
11:15:05 <kaz> kaz: btw, we should be clear about the "bi-weekly policy" as the basis :)
11:15:55 <kaz> ... no call on Apr-1 or 8. right?
11:16:02 <kaz> ca: right
11:16:53 <kaz> resolution: Scripting API TF will not have the TF call Apr 1 or 8
11:17:05 <kaz> topic: PRs
11:17:18 <kaz> subtopic: PR 545
11:17:21 <cris_> https://github.com/w3c/wot-scripting-api/pull/545
11:17:36 <JKRhb> q+
11:17:42 <kaz> s|https://github.com/w3c/wot-scripting-api/pull/545|-> https://github.com/w3c/wot-scripting-api/pull/545 PR 545 - feat: expand exploreDirectory algorithm
11:17:48 <kaz> jr: no real update so far
11:18:02 <kaz> ... just want to push one commit
11:18:10 <kaz> ... started to define some kind of dictionary
11:18:32 <kaz> ... minor change so far
11:18:39 <kaz> ... should have some more discussion
11:19:12 <kaz> ca: tx
11:19:28 <kaz> ... think the direction is good, and would see the final resolution
11:19:41 <kaz> ... let's have more discussion
11:19:52 <kaz> ... any opinions from Zoltan?
11:19:57 <kaz> zk: not really
11:20:10 <kaz> ... still a bit vague
11:20:29 <kaz> ... general thought is already described but need to think about how to implement it
11:20:42 <kaz> ... should be aligned with the Discovery work
11:20:52 <kaz> .. would ask the Discovery TF for review also
11:21:15 <kaz> q+
11:21:17 <kaz> ack jk
11:21:31 <kaz> ... after Jan makes clarification
11:21:56 <kaz> ack k
11:22:10 <kaz> kaz: this is related to the "inter-TF collaboration" discussion
11:22:32 <kaz> ... you can mention your need about the review during the main call also
11:22:58 <kaz> ca: any conclusion about the "inter-TF collaboration" discussion?
11:23:02 <kaz> kaz: still ongoing
11:23:12 <kaz> ... so you can mention your need during the main call
11:24:18 <kaz> ... maybe we might want to think about the mechanism for the Wide Review for sepcs on GitHub
11:24:21 <kaz> zk: right
11:24:35 <kaz> kaz: but let's have discussion during the main call first
11:24:40 <kaz> topic: Issues
11:24:55 <kaz> ca: no new issues this week
11:25:16 <kaz> ... but have many remaining issues
11:25:21 <kaz> -> https://github.com/w3c/wot-scripting-api/issues remaining issues
11:25:39 <kaz> ca: need to think about how to have discussion with related TFs
11:25:56 <kaz> q+
11:26:14 <kaz> ack k
11:26:28 <kaz> kaz: this is also related to the "inter-TF collaboration" discussion
11:26:43 <kaz> ... but some of the issues are already identified as "bug"s
11:26:53 <kaz> ... so we can work on those issues first
11:26:57 <kaz> ca: that's true
11:27:31 <kaz> ... also maybe it might be a good timing to think about how to deal with use cases too
11:27:50 <kaz> q+
11:28:05 <zkis> present- Zoltan_Kis
11:29:04 <kaz> kaz: we should join the UC discussion for that purpose
11:29:18 <kaz> ... they're working on the updated procedure and the improved template
11:29:40 <kaz> ... but at some point, Mizushima-san can make some debriefing at the main call also
11:29:45 <kaz> ack k
11:29:48 <kaz> ca: good point
11:30:26 <kaz> ... we might want to start with error handling
11:30:37 <Mizushima> q+
11:30:41 <kaz> qq+
11:31:00 <kaz> kaz: there are several issues about error handling. right?
11:31:03 <kaz> ca: yes
11:31:05 <kaz> ack k
11:31:05 <Zakim> kaz, you wanted to react to kaz
11:31:29 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/200 Issue 200 - Error Handling
11:32:00 <kaz> mizu: it's important to clarify what Scripting spec describes
11:32:20 <kaz> ... use cases are useful to understand that too
11:32:36 <kaz> ... so would suggest we (=Scripting TF guys) join the UC discussion also
11:33:20 <kaz> ... note that not many people are really aware of the Scripting API discussion as a whole
11:34:03 <kaz> ... clarifying concrete use cases would be helpful for people to understand what is expected for Scripting APIs
11:34:07 <kaz> ca: agree
11:34:28 <kaz> ... Jan, can you join the UC call?
11:34:41 <kaz> jr: have some conflict at the moment
11:34:49 <kaz> ca: would try to join the calls more
11:34:52 <kaz> q+
11:34:55 <kaz> ack mi
11:36:08 <kaz> ack k
11:36:35 <kaz> kaz: yeah, Scripting API itself is clear enough but how to improve/update it is a bit vague
11:37:00 <kaz> ... so providing concrete use cases about our expectation would be helpful for people (including myself) to understand the points
11:37:03 <kaz> ca: right
11:37:20 <kaz> ack k
11:37:24 <kaz> q+
11:37:48 <kaz> rrsagent, draft minutes
11:37:50 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/18-wot-script-minutes.html kaz
11:38:06 <kaz> ... regarding "error handling"
11:38:18 <kaz> ... let's describe possible errors first
11:40:33 <kaz> kaz: that can be a good starting point
11:41:07 <kaz> ... but at some point, we need to think about the interface between the "WoT World" and the "External IoT World" as well
11:43:03 <kaz> ... what would be the impact to TD and Scripting API caused by the errors from the outside of WoT
11:43:36 <kaz> ... and also what would cause potential errors of the external world based on the errors of TD and Scripting API
11:43:40 <kaz> ca: right
11:43:51 <kaz> topic: Versioning
11:44:06 <kaz> ca: we're still waiting for the conclusion from the main group
11:44:20 <kaz> ... based on the work on TD and Discovery
11:44:42 <kaz> chair: Cristiano
11:45:24 <kaz> kaz: the discussion by TD TF and Discovery TF is still ongoing
11:45:47 <kaz> ... but the TD TF should be able to bring their initial proposal back to the main group next week
11:46:01 <kaz> present+Zoltan_Kis
11:47:42 <kaz> jr: there was an issue around Discovery
11:47:55 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/535 Issue 535 - Dedicated methods for DNS-SD, CoRE Link-Format discovery, and other approaches?
11:48:40 <kaz> ca: what about adding a label of "high-priority" to the issue?
11:48:52 <kaz> jr: maybe "middle-priority"?
11:49:12 <kaz> ca: let's discuss this issue next time anyway
11:50:21 <kaz> q+
11:50:32 <kaz> i/there was/topic: AOB/
11:52:18 <kaz> ack k
11:52:20 <kaz> rrsagent, draft minutes
11:52:21 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/18-wot-script-minutes.html kaz
11:52:44 <kaz> [adjourned]
11:52:46 <kaz> rrsagent, draft minutes
11:52:47 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/18-wot-script-minutes.html kaz
14:27:53 <Zakim> Zakim has left #wot-script