11:01:54 RRSAgent has joined #wot-script 11:01:58 logging to https://www.w3.org/2023/09/18-wot-script-irc 11:02:01 meeting: WoT Scripting API 11:02:21 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#September_18.2C_2023 11:02:32 present+ Cristiano_Aguzzi 11:03:53 JKRhb has joined #wot-script 11:05:16 q+ 11:05:25 q- 11:05:35 scribenick: JKRhb 11:05:37 topic: Minutes 11:05:40 topic: Minutes Review 11:05:56 -> https://www.w3.org/2023/09/04-wot-script-minutes.html Sep-4 11:06:02 ca: Minutes look fine to me, if there are no objections I would publish them 11:06:12 No objections, minutes are approved 11:06:19 topic: Publication Check 11:07:01 ca: I noticed a minor issue, there is a problem with the WebIDL verification 11:07:04 q+ 11:07:23 ... you mentioned, kaz, that you will talk to the Webmaster, this is something we need to keep in mind 11:07:43 kaz: This is an issue with the namespaces, right? 11:08:08 ca: Related to partial namespaces, maybe you have already fixed that. Let us know if we can help us 11:08:25 ... issue is an old one, did not make any changes yet 11:08:59 chair: Cristiano 11:09:02 Issue: https://github.com/w3c/wot-scripting-api/issues/480 11:09:05 ... from the issue, I understood that you would make manual changes to the document before publication 11:09:15 First comment: https://github.com/w3c/wot-scripting-api/pull/477#issuecomment-1554299220 11:09:18 present+ Kaz_Ashimura, Cristiano_Aguzzi, Jan_Romann, Zoltan_Kis 11:09:22 rrsagent, make log public 11:09:26 rrsagent, draft minutes 11:09:28 I have made the request to generate https://www.w3.org/2023/09/18-wot-script-minutes.html kaz 11:09:35 "resolution": https://github.com/w3c/wot-scripting-api/pull/477#issuecomment-1557044099 11:09:47 topic: TPAC 11:10:05 ca: I wanted to talk about TPAC, sadly Daniel is not here 11:10:16 s/"resolution"/Group's proposed solution/ 11:10:24 ... what I can say is that we had a nice conversation with the Web Agents group 11:10:26 regrets+ Daniel 11:10:36 q? 11:10:37 ... and I think we can find some synergies 11:10:38 ack k 11:10:46 q+ 11:10:58 ... even though they have their own APIs and technologies 11:11:21 ... sadly I could not attend the device interaction meeting due to conflicts 11:11:36 ... in general, we could not tackle any Scripting API topics in the other meetings 11:11:56 ... meetings were more focussed on high-level discussions 11:12:20 q+ 11:12:36 ... relevant for us might be the Architecture changes, assertions are moved elsewhere, Servient concept could be defined in our document 11:12:52 kaz: Please give information regarding the Web Agents CG also during the main call 11:13:32 ... as you mentioned, main topic was refactoring and use case discussions, that is what the working group should focus on, including Scripting API topics 11:14:14 ack q 11:14:14 ack k 11:14:24 ack z 11:14:59 zk: This is a TPAC + previous discussions feedback: I think we had a discussion with someone from Google that also dealt with creating a more consolidated API in WebIDL and JavaScript 11:15:29 s/ and JavaScript/rather than JavaScript/ 11:16:02 ... there are best practices we should adopt 11:16:34 present+ Tomoaki_Mizushima 11:17:14 rrsagent, make log public 11:17:15 rrsagent, draft minutes 11:17:16 I have made the request to generate https://www.w3.org/2023/09/18-wot-script-minutes.html kaz 11:18:06 s/topic: Minutes Review// 11:18:25 s/topic: Minutes/topic: Minutes Review/ 11:18:27 rrsagent, draft minutes 11:18:28 I have made the request to generate https://www.w3.org/2023/09/18-wot-script-minutes.html kaz 11:19:04 topic: Scripting API report 11:19:04 ca: We should prepare a recap and report to the others what has changed and what is new in the Scripting API 11:19:24 ... I would say that this won't happen in the next main call 11:19:42 zkis_ has joined #wot-script 11:19:49 ... as we haven't agreed on a slot this week, but maybe in the next week such a report could happen 11:20:02 q+ 11:20:16 ... should we simply ask we for a slot next week, Kaz? Or should we send an email and do it this week? 11:20:18 present- Zoltan Kis 11:20:34 kaz: I think this week's main call should be used for general reports from TPAC 11:20:47 ... probably, we should arrange the Scripting API update next week or later 11:21:18 ca: Then I would say that we can ask for a ten minute slot for next week 11:21:40 s/present- Zoltan kis/(Zoltan leaves)/ 11:21:42 rrsagent, draft minutes 11:21:43 I have made the request to generate https://www.w3.org/2023/09/18-wot-script-minutes.html kaz 11:21:50 kaz: You can also send an email to the team-wot mailinglist regarding a slot 11:21:51 ca: Will do that 11:22:32 ca: Our next focus should be to identify use cases 11:22:52 ... after reviewing the use cases, we can focus on bugs in the specification 11:23:25 topic: Issues 11:23:37 s/regarding a slot/to ask for a slot/ 11:23:38 ca: We have 65 open issues 11:24:13 dape has joined #wot-script 11:26:54 ... one thing that is currently missing is discovery 11:27:25 present+ Daniel_Peintner 11:27:33 ... we have open issues and PRs, what is missing is implementations 11:27:51 rrsagent, draft minutes 11:27:52 I have made the request to generate https://www.w3.org/2023/09/18-wot-script-minutes.html kaz 11:27:59 jr: Will try to pick up existing PRs in node-wot to continue discussion in the upcoming weeks 11:28:14 topic: TPAC (continued) 11:28:37 ca: Do you have anything report regarding Scripting API here, Daniel? 11:29:25 dp: Not really, but I joined the Web Agents joint meeting and some chinese vendor showed an interesting demo based on WebAssembly 11:29:58 ... not sure if we could adapt their approach 11:30:13 ... apparently they haven't open-sourced it yet 11:30:40 ... was a chinese university together with Huawei, if I remember correctly 11:30:50 ca: Wasm is an interesting approach 11:31:01 q+ 11:31:19 ... as it is an compiled language, which would improve the loading time in the browser 11:31:37 ... however, the API would stay the same, only the implementation would change 11:31:42 ... good to know, though 11:31:58 q+ 11:31:59 kaz: Liason should mainly discussed during the main call 11:32:37 ... even though Wasm could be an interesting improvement for node-wot or other implementations, it would not impact the Scripting API itself 11:32:50 ... so it should be discussed during the main call 11:33:23 ca: I think there is not that much to discuss here, but the Web Agents group is interesting in any case 11:34:04 q? 11:34:06 ack k 11:34:07 q+ 11:34:17 kaz: Even cooperation with other working groups such as the Web Payments API should be discussed during the main call so that others have the opportunity to notice it 11:34:56 ack dape 11:35:11 dp: It was relatively specific to the Scripting API, therefore I mentioned it here. Other WGs are more interesting for the whole group 11:35:31 kaz: I would suggest discussing liason topics in general during the main call 11:36:04 ... as the topics can be interesting for all task forces 11:36:35 ... my suggestion would be to make this report during the main call 11:37:25 ca: I think it could be interesting to make the connection to projects like Solid and then report that in the main call 11:37:40 kaz: Such a preliminary discussion is fine 11:38:46 ack k 11:39:19 dp: There was a discussion with Tim Berners-Lee with the result that Solid should be integrated with WoT 11:39:58 ca: We can close the meeting early today and will continue next week 11:40:02 [adjourned] 11:40:51 s/Such a preliminary discussion is fine/Such a preliminary discussion is fine. In that case, let's consider today's discussion during this Scripting API call a preliminary discussion to clarify what to be reported during the main call from the Scripting TF participants./ 11:40:57 rrsagent, draft minutes 11:40:58 I have made the request to generate https://www.w3.org/2023/09/18-wot-script-minutes.html kaz 12:58:00 kaz has joined #wot-script 13:01:43 mahda-noura has joined #wot-script 13:59:11 Zakim has left #wot-script