11:01:30 <RRSAgent> RRSAgent has joined #wot-script
11:01:34 <RRSAgent> logging to https://www.w3.org/2024/05/13-wot-script-irc
11:01:42 <kaz> meeting: WoT Scripting API
11:02:01 <zkis> zkis has joined #wot-script
11:02:13 <kaz> present+ Kaz_Ashimura, Zoltan_Kis, Cristiano_Aguzzi
11:05:33 <zkis> scribenick: zkis
11:06:03 <Tomo> Tomo has joined #wot-script
11:06:20 <JKRhb> JKRhb has joined #wot-script
11:07:19 <zkis> Topic: approving last minutes
11:07:27 <cris> https://www.w3.org/2024/03/18-wot-script-minutes.html
11:07:33 <zkis> Approved
11:08:21 <zkis> Agenda:
11:08:25 <JKRhb> q+
11:08:29 <cris> https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#May_13%2C_2024
11:08:41 <zkis> CA: we should reflect the biweekly meetings in the calendar
11:08:45 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#May_13%2C_2024
11:08:56 <kaz> s/Agenda://
11:09:08 <zkis> JR: maybe we can cancel the ones we skip
11:09:23 <kaz> present+ Jan_Romann, Tomoaki_Mizushima, Daniel_Peintner
11:09:37 <kaz> q+
11:09:41 <kaz> ack jk
11:09:42 <JKRhb> ack J
11:09:44 <dape> dape has joined #wot-script
11:10:17 <zkis> ZK: if the meeting falls on a holiday, do we skip (i.e. 4 weeks without meeting)?
11:10:20 <zkis> CA: yes
11:10:42 <dape> q+
11:11:16 <kaz> ack k
11:11:17 <zkis> KA: we can change the calendar entry to biweekly
11:12:04 <zkis> ... I can give the permission for that
11:12:34 <zkis> DP: it has pros and cons; currently we have the freedom to align better with public holidays
11:12:53 <kaz> q+
11:14:11 <zkis> KA: if all is fine with specifying biweekly calls, technically we can do it; but if we do it manually, we need to send email notifications every time
11:14:38 <zkis> q+
11:15:07 <kaz> ack d
11:15:09 <kaz> ack k
11:15:31 <dape> dape has joined #wot-script
11:17:21 <zkis> ZK: in some groups the biweekly meetings are announced by email a week earlier with the agenda - that has been a good practice
11:17:59 <zkis> CA: yes, but are you fine with changing to biweekly meetings?
11:18:18 <zkis> ZK: yes, but IMHO it would be a good practice to announce the meetings by email
11:18:23 <zkis> CA: OK
11:18:58 <zkis> CA has changed the calendar - will send notifications
11:19:27 <zkis> Topic: PRs
11:19:39 <zkis> Subtopic: PR 550
11:19:42 <cris> https://github.com/w3c/wot-scripting-api/pull/550
11:20:07 <zkis> CA: this comes from the Marketing TF
11:20:36 <dape> rendered version at https://github.com/w3c/wot-scripting-api/blob/319786f8ed8e6a81e306cd331e6da69170f237f0/README.md
11:20:47 <zkis> ... a general alignment template for task forces
11:20:48 <dape> q+
11:21:13 <zkis> ack d
11:21:15 <zkis> ack z
11:24:28 <kaz> rrsagent, make log public
11:24:33 <kaz> rrsagent, draft minutes
11:24:34 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/13-wot-script-minutes.html kaz
11:25:14 <kaz> s|https://github.com/w3c/wot-scripting-api/pull/550|-> https://github.com/w3c/wot-scripting-api/pull/550 PR 550 - refactor: align with latest marketing template|
11:25:17 <zkis> CA: merging the PR
11:25:26 <kaz> q+
11:26:02 <zkis> KA: the proposed readme is not just for Marketing but all the WoT task forces activities
11:26:07 <zkis> ack k
11:26:30 <kaz> ack k
11:26:32 <zkis> KA: so the PR title was not entirely correct, but the content was OK
11:27:12 <zkis> Subtopic: PR 549
11:27:17 <cris> https://github.com/w3c/wot-scripting-api/pull/549
11:28:02 <zkis> DP: the reason was that Eclipse repo hierarchy was changed
11:28:38 <zkis> ... also http changed to https
11:28:55 <cris> q?
11:28:55 <zkis> CA: ok, we can safely merge
11:29:02 <zkis> PR merged
11:29:16 <dape1> dape1 has joined #wot-script
11:29:35 <zkis> Subtopic: PR 545
11:29:47 <zkis> JR: no updates on this yet, it still needs work
11:29:51 <zkis> Topic: issues
11:30:17 <zkis> Subtopic: issue 548
11:30:24 <cris> https://github.com/w3c/wot-scripting-api/issues/548
11:30:51 <zkis> CA: this comes from Luca
11:31:03 <zkis> ... it brought up something we need to implement, and even spec
11:31:03 <dape1> q+
11:31:25 <zkis> ... the spec doesn't mention how to handle this case
11:32:02 <kaz> i|no updates|-> https://github.com/w3c/wot-scripting-api/pull/545 PR 545 - feat: expand exploreDirectory algorithm|
11:32:12 <zkis> CA: things become tricky when additional responses refer to their own schema
11:32:32 <kaz> s|https://github.com/w3c/wot-scripting-api/issues/548|-> https://github.com/w3c/wot-scripting-api/issues/548 Issue 548 - Support for additionalResponses|
11:32:37 <kaz> rrsagent, draft minutes
11:32:39 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/13-wot-script-minutes.html kaz
11:32:45 <zkis> CA: currently this is categorized as spec improvement
11:33:04 <zkis> q+
11:33:58 <zkis> DP: the opening comment we need to correct
11:34:07 <zkis> CA: good cath
11:34:11 <dape1> ack dape1
11:34:12 <zkis> s/cath/catch
11:35:01 <JKRhb> q+
11:35:03 <dape1> q+
11:35:07 <zkis> ZK: we can make a note, give a scripting example, eventually we can make an algorithm
11:35:12 <zkis> ack d
11:35:14 <zkis> ack z
11:36:02 <zkis> DP: when additional responses are more than just success/errors, then how to handle that?
11:36:20 <zkis> CA: the schema of the output property should reflect also the schema of the additional responses
11:36:27 <zkis> ... but we don't say anything about it now
11:36:40 <zkis> ... somehow the runtime needs to figure it out
11:37:00 <zkis> DP: so it's a bit of a grey area
11:37:08 <zkis> q?
11:38:16 <zkis> JR: not sure how well can we generalize this, as it's HTTP specific...
11:38:31 <zkis> ... a general algorithm should also handle other protocols
11:38:40 <zkis> ... maybe in the bindings
11:38:49 <zkis> CA: right, this is coming from HTTP
11:39:13 <zkis> ack J
11:39:38 <zkis> CA: CoAP might be OK, but MQTT might be different
11:39:41 <zkis> q+
11:39:58 <zkis> CA: what is important is the mapping, including error mapping
11:41:42 <zkis> ZK: this shows the importance of scripting APIs, since it can model all these protocols with the same API
11:42:07 <zkis> ... we need to give explicit examples for how to handle these situations
11:42:28 <zkis> ... the best is to solve it in the bindings / TD spec.
11:42:37 <zkis> Subtopic: issue 535
11:43:00 <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:43:07 <kaz> rrsagent, draft minutes
11:43:08 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/13-wot-script-minutes.html kaz
11:43:14 <zkis> ack z
11:43:21 <kaz> chair: Cristiano
11:43:22 <kaz> rrsagent, draft minutes
11:43:24 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/13-wot-script-minutes.html kaz
11:43:45 <cris> https://github.com/w3c/wot-scripting-api/issues/535
11:44:36 <kaz> i|we should reflect the biweekly meetings in the calendar|topic: Next calls|
11:44:38 <kaz> rrsagent, draft minutes
11:44:39 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/13-wot-script-minutes.html kaz
11:44:47 <zkis> JR: it's about if the Discovery TF introduction methods can be modeled explicitly
11:44:58 <zkis> ... or are we fine with generic API
11:45:08 <kaz> s|https://github.com/w3c/wot-scripting-api/issues/535||
11:45:10 <kaz> rrsagent, draft minutes
11:45:12 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/13-wot-script-minutes.html kaz
11:45:23 <zkis> ...or whether these should be added by libraries
11:45:53 <zkis> ... not sure how to move on
11:46:42 <zkis> CA: IMHO it's quite hard to unify all introduction methods in one method
11:47:13 <JKRhb> q+
11:47:43 <zkis> q+
11:48:22 <zkis> JR: maybe we could just request a TD and explore that
11:48:38 <zkis> ... was not sure how the "magic" discovery would work
11:48:57 <zkis> ack JKRhb
11:51:20 <zkis> ack Zakim
11:51:24 <zkis> ack zkis
11:52:04 <kaz> rrsagent, draft minutes
11:52:05 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/13-wot-script-minutes.html kaz
11:55:44 <JKRhb> q+
11:57:14 <zkis> q?
11:58:22 <zkis> ZK: it all depends how much functionality do we want to expose in the app side from the implementation side
11:58:42 <zkis> CA: most people seem to have some kind of directory which they explore
11:58:48 <zkis> JR:
11:58:52 <zkis> ack JKRhb
11:59:20 <zkis> JR: maybe having the general way of discovery is nice, but was wondering is how to best configure this
11:59:41 <zkis> ZK: we used to have some but they can change
12:00:33 <zkis> JR: I gave an example in the issue
12:00:48 <zkis> ZK: right, those have been supported in the past, we can extend the filters
12:00:59 <zkis> JR: right, we can experiment more on this
12:01:32 <zkis> CA: we could label features as experimental and gather more dev feedback
12:02:02 <zkis> CA: maybe even during a plugfest
12:02:13 <zkis> CA: time is up, AOB?
12:02:22 <zkis> Meeting adjourned.
12:02:43 <kaz> rrsagent, draft minutes
12:02:44 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/13-wot-script-minutes.html kaz
14:30:59 <Zakim> Zakim has left #wot-script