12:00:22 RRSAgent has joined #wot-script 12:00:22 logging to https://www.w3.org/2022/11/07-wot-script-irc 12:00:29 meeting: WoT Scripting API 12:00:51 present+ Kaz_Ashimura 12:02:50 present+ Zoltan_Kis, Daniel_Peintner 12:05:02 Mizushima has joined #wot-script 12:06:06 JKRhb has joined #wot-script 12:06:19 present+ Tomoaki_Mizushima, Jan_Romann 12:08:22 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#November_7.2C_2022 12:08:48 scribe: zkis 12:09:00 Topic: previous minutes 12:09:05 -> https://www.w3.org/2022/10/17-wot-script-minutes.html Oct-17 12:10:06 DP: we missed 2 calls, will continue where we left off 12:10:36 Minutes approved. 12:10:55 Topic: publication schedule 12:11:08 DP: the current charter ends Jan 2023 12:11:34 q+ 12:12:22 ack z 12:12:59 ZK: I suggest to finish the discussion on the discovery API changes and get it reviewed and published 12:13:23 q+ 12:13:25 DP: since the review time requirements, we should ask for review latest by Jan 9 12:13:37 DP: will be on vacation the week before 12:13:45 ack kaz 12:14:03 KA: we should think about charter and publication separately 12:14:33 ... focus on what the Scripting TF can do 12:15:16 DP: so final draft should be ready by end of year 12:15:47 q+ 12:16:17 ack kaz 12:16:27 cris__ has joined #wot-script 12:16:37 ZK: we have 5-6 meetings, should be enough for this objective 12:17:12 KA: Scripting being a Note, the date is less of a concern than the content of the proposed changes 12:17:15 present+ Cristiano_Aguzzi 12:17:18 ack k 12:17:28 DP: we agree that discovery should be the content 12:17:33 +1 12:17:51 DP: we should agree on an interface that we can also implement 12:18:17 ... next, the new op values 12:18:30 ... we have some PRs in work 12:19:37 Topic: PRs 12:19:45 Subtopic: PR 438 12:19:52 -> https://github.com/w3c/wot-scripting-api/pull/438 12:20:03 DP: fix ReSpec errors 12:22:16 Jan: this just removed the internal slot 12:22:48 ZK: we need a larger change that consistently updates the algorithms for using async iterators 12:22:54 DP: the change looks enough for me 12:24:27 ZK: I suggest we leave the PR open and maybe other changes will be needed as well 12:24:35 Jan: okay with that 12:24:43 Subtopic: PR 434 12:24:46 -> https://github.com/w3c/wot-scripting-api/pull/434 12:25:38 q+ 12:25:46 Jan: will continue with that next week 12:26:04 DP: we need multiple alternative PRs 12:26:15 CA: indeed, planning to do that ASAP 12:27:26 ZK: we can also work in issues and first agree on the web idl 12:28:29 -> Issue 364 -> https://github.com/w3c/wot-scripting-api/issues/364 12:31:44 CA: if we choose to have factory, we don't have to use the same interface for every start method 12:31:52 ZK: yes 12:38:19 CA: I suggest having separate functions in a namespace 12:38:27 DP: I agree 12:40:03 s|-> https://github.com/w3c/wot-scripting-api/pull/438|-> https://github.com/w3c/wot-scripting-api/pull/438 PR 438 - fix: remove mentioning of internal discovery results| 12:40:40 s|-> https://github.com/w3c/wot-scripting-api/pull/434|-> https://github.com/w3c/wot-scripting-api/pull/434 PR 434 - feat: adjust ThingFilter and ThingDiscovery interfaces| 12:41:28 Jan: also leaning towards Cristiano's approach 12:41:50 s|-> Issue 364 -> https://github.com/w3c/wot-scripting-api/issues/364|-> https://github.com/w3c/wot-scripting-api/issues/364 Issue 364 - Using a callback-based approach for Discovery?| 12:42:03 ZK: please make an alternative proposal, handling the generic discovery use case and also the async iterators fro multiple results 12:42:29 Jan: in implementation I found that merging the functions in one interface also has benefits 12:45:29 ZK: we should follow the rule of constituency: developers first, then implementation, then theoretical considerations 12:46:28 DP: we have 2 styles, we should choose the one simpler for developer 12:47:46 q+ 12:48:51 ZK: we might want to expose the initialization need for discovery 12:49:01 CA: not sure if it's a real requirement 12:49:37 ... we can split the init methods to the specific ones needed by the discovery method 12:50:03 ZK: I agree with with that 12:50:14 q+ 12:50:20 ack c 12:51:15 ZK: a bit concerned in exposing a lot of functions in the root namespace 12:51:22 CA: yes, we can think about that 12:51:24 ack kaz 12:51:26 ack c 12:51:26 q+ 12:51:47 KA: we might want to survey the existing discovery APIs 12:52:17 ZK: we did that, but indeed we could do it again 12:52:43 DP: only direct discovery reports a single or no results, all the rest a lits 12:52:47 s/lits/list 12:53:28 s/APIs/APIs like Chrome Cast API, mdns-js and node-mdns. at least it would be better to have some kind of compatibility with them or some kind of binding./ 12:54:27 CA: those are not pure functions, e.g. local does different things than multicast 12:55:39 CA: I met a problem as a developer with the too generic object approach - would have preferred separate functions 12:55:58 ... the discovery spec is also designed for separate use cases 12:56:01 ack dape 12:56:31 DP: to not have root level function spread, but we could put them into an object 13:00:44 ZK: let Jan and Cristiano comment on issue 364 13:01:02 ... and let's continue the discussion in the issue, rather than in PRs 13:01:14 CA: yes - and also need to think about the algorithms 13:01:30 DP: time is up, let's continue on github 13:01:31 rrsagent, make log public 13:01:38 rrsagent, draft minutes 13:01:38 I have made the request to generate https://www.w3.org/2022/11/07-wot-script-minutes.html kaz 13:02:06 Jan: I already opened a PR for node-wot, will update that with Cristiano's proposal and then we have an implementation viewpoint as well 13:02:11 DP: adjourned 13:02:48 rrsagent, draft minutes 13:02:48 I have made the request to generate https://www.w3.org/2022/11/07-wot-script-minutes.html zkis