11:02:52 RRSAgent has joined #wot-script 11:02:56 logging to https://www.w3.org/2024/06/10-wot-script-irc 11:03:12 Tomo has joined #wot-script 11:03:15 meeting: WoT Scripting API 11:03:50 present+ Kaz_Ashimura, Cristiano_Aguzzi 11:06:33 present+ Tomoaki_Mizushima 11:07:32 present+ Jan_Romann 11:09:12 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#June_10%2C_2024 11:09:40 dape has joined #wot-script 11:09:50 present+ Daniel_Peintner 11:09:57 chair: Cristiano 11:11:28 topic: Minutes 11:11:32 -> https://www.w3.org/2024/05/13-wot-script-minutes.html May-13 11:11:48 q? 11:11:50 q+ 11:12:17 JKRhb has joined #wot-script 11:12:23 scribe: dape 11:12:27 TOPIC: Previous minutes 11:12:50 CA: Checked them look good 11:12:53 ... minutes are approved 11:12:57 TOPIC: Update wiki info 11:13:06 s/TOPIC: Previous minutes// 11:13:10 rrsagent, make log public 11:13:15 rrsagent, draft minutes 11:13:17 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 11:13:30 WebEx coordinates are outdated 11:13:40 luca_barbato has joined #wot-script 11:13:45 s/WebEx /CA: WebEx 11:13:51 CA: We use Zoom now 11:14:01 ... should update the entry 11:14:20 DP: Do other group have the same issue? 11:14:22 rrsagent, draft minutes 11:14:24 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 11:14:31 s/other group/other groups 11:14:43 CA: TD is updated 11:15:22 ... let's use the same entry as on TD wiki 11:15:41 Tomo has joined #wot-script 11:15:56 s/entry/style/ 11:16:06 TOPIC: PRs 11:16:15 SUBTOPIC: Improve README 11:16:22 https://github.com/w3c/wot-scripting-api/pull/553 11:16:29 q+ 11:16:39 CA: I tried to improve readme 11:17:10 ack k 11:17:35 Kaz: Side-node we need to improve wiki further. Section "Mondays .." 11:17:52 ... time should be updated.. or remove whole section 11:18:47 i|Side|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#Mondays_at_7am_US_Eastern_%2F_1pm_Europe_%2F_9pm_Japan "Mondays at 7am"... 11:19:12 i/Side-note/topic: Scripting wiki issue - revisited/ 11:19:13 q+ 11:20:42 DP: Could just leave US Eastern time.. since all W3C entries are based on US Eastern 11:20:51 Kaz: Okay either way 11:20:58 ack d 11:21:22 s/either/with either/ 11:21:48 @@@ Kaz will move the above section later :) 11:22:01 CA: PR updates readme only 11:22:10 ... DP updated template 11:22:17 ... this is a follow-up 11:22:21 s|https://github.com/w3c/wot-scripting-api/pull/553|-> https://github.com/w3c/wot-scripting-api/pull/553 PR 553 Improve README| 11:22:34 rrsagent, draft minutes 11:22:35 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 11:22:41 CA: added a little explainer 11:23:07 present+ Luca_Barbato 11:23:30 CA: Jan proposed changes 11:23:36 ... okay with suggestion 11:23:59 JR: Apart from my suggestion it looks good 11:24:37 DP: Looks good now 11:25:00 CA: Okay,. let's merge PR 553 11:25:16 SUBTOPIC: use references from specref instead local bibliography 11:25:21 ... https://github.com/w3c/wot-scripting-api/pull/552 11:25:44 JR: Mostly editorial 11:25:53 ... we had manually defined references 11:26:13 ... replaced those provided by specref 11:26:24 s|... https://github.com/w3c/wot-scripting-api/pull/552|-> https://github.com/w3c/wot-scripting-api/pull/552 PR 552 - chore: use references from specref instead local bibliography| 11:26:32 ... PR points to latest REC version 11:26:41 i/SUBTOPIC/(merged)/ 11:26:44 rrsagent, draft minutes 11:26:45 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 11:26:52 ... binding to latest spec version 11:27:17 JR: Rendered diff shouldn't show changes 11:27:30 s/PR 553 Imp/PR 553 - Imp/ 11:27:32 rrsagent, draft minutes 11:27:33 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 11:28:08 CA: We point to REC version ... what about latest published version 11:28:29 JR: specref can also point to latest published version 11:29:01 CA: Until we don't use anything "new" we should point to REC version 11:29:06 DP: +1 11:29:14 q? 11:29:20 i|Rendered diff|-> https://pr-preview.s3.amazonaws.com/w3c/wot-scripting-api/552/23dc59e...JKRhb:877153c.html diff| 11:30:20 -> https://pr-preview.s3.amazonaws.com/w3c/wot-scripting-api/552/23dc59e...JKRhb:877153c.html#references E. References section from the diff 11:30:24 rrsagent, draft minutes 11:30:26 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 11:30:37 q? 11:30:38 CA: Once we use new features we need to keep that in mind 11:30:40 q? 11:30:57 q+ 11:31:09 CA: Okay, seems ready to be merged .. 11:31:35 Kaz: Do we want to make all the other spec editors follow this style? 11:32:03 ... maybe check with others in main call 11:32:49 ... we could send mail message to team-wot 11:32:58 CA: Will do... 11:33:08 ... merging PR 552 11:33:26 SUBTOPIC: Add clarifications for discover method 11:33:33 ... https://github.com/w3c/wot-scripting-api/pull/551 11:33:35 i/SUB/(merged)/ 11:33:52 JR: related to discover method 11:34:12 ... discover can handle introduction and exploration phase 11:34:18 s|... https://github.com/w3c/wot-scripting-api/pull/551|-> https://github.com/w3c/wot-scripting-api/pull/551 PR 551 - Add clarifications for discover method| 11:34:23 rrsagent, draft minutes 11:34:25 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 11:34:31 q? 11:34:31 ... I added URL parameter 11:34:31 ack k 11:34:54 JR: Maybe we need another interfaces 11:35:20 ... and as DP mentioned we need to reflect it in TS definition 11:35:33 CA: related with issue 535 11:36:09 ... question is what do we want to hide w.r.t. introduction phase 11:36:43 ... what about preferences 11:36:58 ... e.g., just things from a given thing directory 11:37:07 ... where do we set the bar 11:37:40 ... URL provided means we should go with this directory 11:37:55 CA: URL can be added to ThingFilter also 11:38:26 luca_barbato_ has joined #wot-script 11:38:27 i|related with|-> https://github.com/w3c/wot-scripting-api/issues/535 Issue 535 - Dedicated methods for DNS-SD, CoRE Link-Format discovery, and other approaches?| 11:39:02 present+ Zoltan_Kis 11:39:04 ... do we have use-case for using own URL 11:39:09 q+ 11:39:43 LB: 2 scenarios 11:40:12 ... all the discovery the app wants to support are provided by operating system 11:40:25 ... system takes care 11:41:10 ... on the other hand ... situation that application/developer wants to specify 11:42:01 ... bare discovery is fine (based on operating system) plus having interface with URL or so 11:43:19 ... e.g. just running query on a specific interface is apart 11:43:34 q+ 11:43:39 ack luca_barbato_ 11:44:48 q+ zkis 11:44:51 ZK: Bigger context 11:45:06 ... multiple devices using Bluetooth and other means 11:45:24 ... servient provisioned 11:45:46 ... we need to support developer choices 11:46:00 ... e.g. choose mDNS if available 11:46:06 ... we could use filters 11:46:12 ... no filter -> any means 11:46:35 ... with filter -> application/developer can choose 11:46:57 ZK: multistage discovery is yet another question 11:47:24 q? 11:47:27 q+ 11:47:28 ack zk 11:47:48 ack c 11:47:54 CA: I think we are aligned 11:48:22 ... we need some "magic" discovery ... without any configuration 11:48:44 ... we can try to be open to extension like Luca suggested 11:48:52 ... own discovery mechanism 11:49:03 ... how can we support that? 11:49:59 ... what if I want to use default .. but additionally tweak it a bit 11:50:26 ... how can I know which discovery mechanism is available 11:51:02 ... rename ThingFilter ... more like configuration 11:51:12 ZK: filter is not local only 11:51:20 q+ 11:51:36 CA: remote filter depends on options 11:52:12 ZK: filter is software construct 11:52:31 ... local filter and protocol filters should be in different method 11:53:30 ... API should be generic 11:53:54 ... suggest to collect use-cases 11:54:24 ... and check how we can solve them in Scripting API 11:54:37 q? 11:54:47 Kaz: Agree with Cristiano and Zoltan 11:55:03 ... specifically to thing discovery method 11:55:16 ... different methods and URLs 11:55:26 ... we need to get more use-cases 11:55:36 ack kaz 11:56:07 LB: first ground work ... what is the API and what are the boundaries 11:56:50 s/more use-cases/more use cases to see which case requires what kind of method/ 11:56:54 ... one part is actual discovery like mDNS 11:57:29 ... other part is interface that can be configured 11:57:55 ... "my" discovery process could be just querying a directory I know already 11:58:07 rrsagent, draft minutes 11:58:08 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 11:58:57 ... "my" filtering process could just be filtering things 11:59:21 q? 11:59:23 ack luca_barbato_ 12:00:07 CA: All ideas are relevant 12:00:29 ... also like recursion of TD directory 12:00:42 ... I think we need developer experience 12:00:56 ... Jan worked on dart_wot 12:01:23 CA: w.r.t. to PR .. text improvement is fine ... 12:01:36 ... however, changing method should be postponed 12:01:42 JR: Okay, will split the PR 12:01:57 DP: +1 12:02:00 +1 12:02:04 q+ 12:02:50 TOPIC: Next meetings 12:02:55 rrsagent, draft minutes 12:02:56 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 12:03:02 DP: will be on vacation till end of June 12:03:19 CA: Please ping me in one way or the other so that we know 12:03:41 [adjourned] 12:03:43 rrsagent, draft minutes 12:03:44 I have made the request to generate https://www.w3.org/2024/06/10-wot-script-minutes.html kaz 14:31:04 Zakim has left #wot-script