11:59:18 RRSAgent has joined #wot-script 11:59:18 logging to https://www.w3.org/2022/01/17-wot-script-irc 12:02:02 meeting: WoT Scripting API 12:02:06 chair: Daniel 12:02:34 present+ Kaz_Ashimura, Cristiano_Aguzzi, Zoltan_Kis 12:02:46 dape has joined #wot-script 12:04:34 present+ Daniel_Peintner 12:04:53 scribenick: zkis 12:05:11 Topic: previous minutes 12:05:48 -> https://www.w3.org/2022/01/10-wot-script-minutes.html 12:05:58 Mizushima has joined #wot-script 12:06:03 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#17_January_2022 12:08:10 DP: in the end no need to shift the call time 12:08:48 DP: no objections, the minutes can be published 12:09:19 Topic: quick updates 12:09:24 Publication in Q1 12:10:13 Topic: Issues 12:11:54 subtopic: Issue 365 12:12:05 -> https://github.com/w3c/wot-scripting-api/issues/365 12:12:07 -> https://github.com/w3c/wot-scripting-api/issues/365 Issue 365 - Recent ReSpec Warnings - Found definition for "XYZ", but nothing links to it. 12:12:14 cris has joined #wot-script 12:12:20 q+ 12:13:07 ZK: business as usual, as ReSpec is evolving with new checks, we should periodically update the spec 12:14:16 q+ 12:14:24 ack cr 12:15:05 CA: it's a sanity check which is fine. In other case the references don't use correct syntax which is why they seem to be unreferred terms. We need to fix those. 12:15:26 DP: could try to do that 12:17:35 KA: we need to look for the reason for errors in our index.html, and if it's the case, we might want to raise issues against ReSpec 12:18:04 DP: some errors relate to the spec being on the REC track, not a Note 12:18:31 KA: we can change in the header 12:19:04 Subtopic: multiple properties 12:20:12 -> https://github.com/w3c/wot-scripting-api/issues/219 12:20:55 s|219|219 Issue 219 - Discussion about read- write-/multipleproperties| 12:21:05 CA: didn't we reach solution last time? 12:21:19 ... we took an action point last time 12:22:00 CA: the TD spec should be more specific on these 12:22:07 ZK: yes, including the error cases 12:22:31 DP: we opened issues on the TD spec on these, but no progress so far 12:22:50 present+ Tomoaki_Mizushima 12:22:50 JKRhb has joined #wot-script 12:23:00 zakim, who is on the call? 12:23:00 Present: Kaz_Ashimura, Cristiano_Aguzzi, Zoltan_Kis, Daniel_Peintner, Tomoaki_Mizushima 12:23:21 present+ Jan_Romann 12:23:47 DP: will ping the TD TF to expand on these 12:25:41 ZK: on the write/read multiple we know what to expect, but write/read multiple vs all is not specified well 12:26:13 Subtopic: callback based discovery 12:26:25 -> https://github.com/w3c/wot-scripting-api/issues/364 12:27:02 s|364|364 Issue 364 - Using a callback-based approach for Discovery?| 12:27:49 Jan: summarizes the issue 12:30:17 q+ 12:30:24 ack k 12:31:58 CA: we could do a pro/con summary on the suggestion 12:32:08 ... similar to what we do on events 12:32:16 q? 12:32:33 ack JKRhb 12:32:39 ZK: let's try to rewrite the algorithms based on this proposal and see how it works 12:34:03 CA: about the next() method, it is controlled by the application, the alternative would let the runtime handle it 12:35:02 q+ 12:36:10 q- 12:38:15 CA: looks like the version with next() can be optimized better 12:38:37 ... the app can stop when it finds what it wants 12:39:33 ZK: not all that much different from typical code with listeners either 12:41:05 ZK: let's analyze this more and weight the pros and cons 12:42:38 Jan: the question was in implementing the specified algorithm, to block until a TD is available 12:44:17 ZK: indeed the implementation difficulty is a valid reason to reconsider the API design, if the app can do the same things with the new design 12:45:42 DP: a naive thinking is that we get the ThingDiscovery, we could re-formulate the behavior, i.e. not wait on next() if nothing is available. 12:46:29 ZK: then it's easier to go with the listener model 12:48:05 ... if the apps don't need that extra control, we can go with the simpler listener model 12:49:12 CA: we use TD directory, that API is not finished yet, so we don't know about strong use cases yet for app side control 12:49:28 Jan: we could introduce more control with the listener model? 12:50:21 DP: let's continue in the issue 12:50:31 Subtopic: conformance 12:50:43 q+ 12:50:44 DP: waiting for feedback from Philip 12:50:48 ack kaz 12:51:07 KA: no answer yet, but will ping on IRC 12:51:42 Subtopic: thing models 12:52:23 -> https://github.com/w3c/wot-scripting-api/issues/361 12:52:33 DP: CA should update 12:53:28 SUBTOPIC: Finding correct unsubscribe form 12:53:28 Subtopic: find correct unsubscribe 12:53:48 -> https://github.com/w3c/wot-scripting-api/issues/351 12:55:49 Subtopic: multiple subscriptions 12:55:55 -> https://github.com/w3c/wot-scripting-api/issues/346 12:56:13 CA: we have a PR on this 12:56:35 DP: we can close it then 12:57:53 DP: adjourned 12:58:16 rrsagent, make log public 12:58:21 rrsagent, draft minutes 12:58:21 I have made the request to generate https://www.w3.org/2022/01/17-wot-script-minutes.html kaz 14:58:53 Mizushima has left #wot-script 15:30:33 Zakim has left #wot-script