11:01:39 RRSAgent has joined #wot-script 11:01:44 logging to https://www.w3.org/2023/10/02-wot-script-irc 11:01:44 cris_ has joined #wot-script 11:02:30 zkis has joined #wot-script 11:03:57 meeting: WoT Scripting API 11:04:01 Mizushima has joined #wot-script 11:05:05 present+ Kaz_Ashimura, Zoltan_Kis, Cristiano_Aguzzi 11:05:33 chair: Cristiano 11:05:34 scribe zkis 11:05:42 scribenick: zkis 11:05:52 agenda: https://www.w3.org/WoT/IG/wiki/index.php?title=WG_WoT_Scripting_API_WebConf&action=edit§ion=6 11:06:56 Topic: Topic: previous minutes 11:07:06 -> https://www.w3.org/2023/09/25-wot-script-minutes.html Sep-25 11:07:09 Accepted 11:07:16 Topic: publication process 11:07:21 q+ 11:07:27 CA: there were issues that Kaz fixed 11:07:31 ack kaz 11:07:42 -> https://github.com/w3c/wot-scripting-api/tree/main/releases/note2 wot-scripting-releases/note2 11:09:25 KA: instead of big changes, this time we replaced the conflicting id's using a postprocessing script that assigns unique id's 11:09:29 JKRhb has joined #wot-script 11:10:13 s|scripting-|scripting-api/| 11:10:20 CA: thank you, excellent. DP already signaled he's fine with publishing, I also support. 11:10:24 rrsagent, make log public 11:10:28 rrsagent, draft minutes 11:10:29 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 11:10:36 ack k 11:10:40 CA: we should check ReSpec to fix the original issue 11:11:01 CA: Resolution for publication has already been made. 11:11:06 present+ Jan_Romann, Tomoaki_Mizushima 11:11:12 rrsagent, draft minutes 11:11:14 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 11:11:20 Topic: reports 11:11:58 CA: there are changes coming in other task forces and only then we update Scripting API 11:12:27 Topic: PRs 11:13:19 Subtopic: PR 502 11:13:24 https://github.com/w3c/wot-scripting-api/pull/502 11:14:00 q+ 11:15:51 CA: let's try to fix ReSpec instead of discarding partial declarations 11:15:53 s/https/-> https/ 11:16:01 s/502/502 PR 502 - refactor: move WoT definitions up in a single place/ 11:16:04 rrsagent, draft minutes 11:16:05 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 11:16:12 ZK: we should re-evaluate the need of conformance classes, implementors should chime in 11:16:52 ZK: so far in the group there has been consensus that we need conformance classes, i.e. we don't have to implement all parts in a mandatory way 11:17:57 q? 11:17:57 i|we should|topic: Issue on conformance classes| 11:18:01 ack zkis 11:18:14 CA: creating a new issue about conformance classes 11:18:21 i|we should|-> https://github.com/w3c/wot-scripting-api/issues/506 Issue 506 - Re-evaluate the conformance classes| 11:18:23 https://github.com/w3c/wot-scripting-api/issues/506 11:19:12 CA: we should have an editors' meeting and discuss these outstanding issues 11:20:27 s|topic: Issue on conformance classes|| 11:20:43 s|-> https://github.com/w3c/wot-scripting-api/issues/506 Issue 506 - Re-evaluate the conformance classes|| 11:20:51 ZK: we should let Daniel close the PR, since it has been superseded by Kaz' PR for the publication problem, but it raises the problem of conformance classes, that can be discussed in the separate issue. 11:21:06 s|https://github.com/w3c/wot-scripting-api/issues/506|-> https://github.com/w3c/wot-scripting-api/issues/506 Issue 506 - Re-evaluate the conformance classes| 11:21:10 rrsagent, draft minutes 11:21:11 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 11:21:31 Topic: PR 489 11:21:41 CA: improves compiler checks 11:21:48 s/Topic:/Subtopic:/ 11:21:48 q+ 11:22:11 ... warns you if the TD you're using is not valid (e.g. a property missing) 11:22:20 i|improves|-> https://github.com/w3c/wot-scripting-api/pull/489 PR 489 - Better types for Scripting API| 11:22:45 ack Mizushima 11:23:21 ZK: readability is compromised, but we get the benefits said before, so no hard opinions 11:24:14 CA: right, and now the types are very strict 11:27:10 rrsagent, draft minutes 11:27:11 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 11:29:09 ZK: so this is a TS specific optimization for implementations, not really related to the spec in a normative sense, but it's more like a helper. 11:29:31 CA: we can leave this open for more comments. 11:29:43 CA: AOB? 11:30:23 Jan: question about TD getter, on ExposedThing 11:30:53 https://w3c.github.io/wot-scripting-api/#dom-exposedthing-getthingdescription 11:31:31 q+ 11:31:53 JR: nowadays JavaScript has built-in getters and setters, should we use those? 11:32:59 q+ 11:33:01 q+ 11:33:15 ZK: having a method allows doing postprocessing on internal slot data 11:33:25 CA: theoretically we can also use getter and setter 11:33:57 JR: right, we can facade with the method, maybe better from API point of view 11:35:36 ZK: the method provides a presentation layer too, and security filter eventually in the future 11:36:12 CA: in our case there are not many reasons for postprocessing 11:37:42 ... at least for consumed things - but for exposed things the method might be better 11:37:54 ... and for consistency, we could also have the same in consumed things 11:38:01 q? 11:38:05 ack j 11:38:06 rrsagent, draft minutes 11:38:07 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 11:38:16 ack zkis 11:38:24 CA: meeting adjourned 11:38:27 rrsagent, draft minutes 11:38:29 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 11:38:56 i|AOB|topic: AOB| 11:38:58 rrsagent, draft minutes 11:38:59 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 11:39:32 i|AOB?|-> https://github.com/w3c/wot-scripting-api/issues/507 Issue 507 - Should we refactor getThingDescription to a JS getter?| 11:39:34 rrsagent, draft minutes 11:39:35 I have made the request to generate https://www.w3.org/2023/10/02-wot-script-minutes.html kaz 13:01:30 mahda-noura has joined #wot-script 13:58:18 Zakim has left #wot-script