10:03:31 RRSAgent has joined #wot-script 10:03:35 logging to https://www.w3.org/2025/02/19-wot-script-irc 10:03:37 meeting: WoT Scripting API 10:03:56 present+ Kaz_Ashimura, Cristiano_Aguzzi, Daniel_Peintner, Zoltan_Kis 10:05:52 scribe: dape 10:06:04 TOPIC: Previous minutes 10:06:23 -> 05 Feb -> https://www.w3.org/2025/02/05-wot-script-minutes.html 10:06:30 Mizushima has joined #wot-script 10:07:17 present+ Tomoaki_Mizushima 10:08:17 CA: Minutes look good -> approved 10:10:37 TOPIC: Calendar 10:10:49 DP: 2 points 10:11:37 ... it shows we didn't send update 10:11:58 ... wonder whether everyone has it in calendar?# 10:12:08 s/ calendar?#/ calendar? 10:12:22 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#February_19%2C_2025 10:12:53 q+ 10:13:12 CA: I think we did a minor update and didn't want to bother everyone 10:13:25 -> https://www.w3.org/events/meetings/d32e2081-22e7-4fb8-aa6c-308992284a0a/20250219T050000/ WoT Scripting API calendar 10:13:26 ZK: Had issues with W3C calendar entry 10:13:41 Kaz: Outlook has difficulties sometimes 10:14:34 ... ICS download is possible also 10:15:12 CA: used public link in Google Calendar and imported it in Outlook 10:15:31 ... shall we send notification to remove warning? 10:15:33 ZK: Yes 10:15:46 CA: Done! 10:16:07 rrsagent, make log public 10:16:13 rrsagent, draft minutes 10:16:14 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 10:16:33 chair: Cristiano 10:16:43 DP: 2nd point: Used to say the current slot is intermediary ... 10:16:52 CA: Correct, problematic for US 10:16:52 i/it shows/subtopic: Calendar invite/ 10:17:04 ... would keep the slot as is 10:17:12 i|2nd|subtopic: Marketing page| 10:17:56 i|2nd point|-> https://www.w3.org/WoT/activities/meetings/ WoT Marketing page - Web Conference Meetings 10:18:15 ZK: Slot is okay for me, but sometimes I might have issues 10:18:22 TOPIC: PRs 10:18:30 SUBTOPIC: Extend invokeAction 10:18:39 ... https://github.com/w3c/wot-scripting-api/pull/561 10:18:53 DP: No news from my side 10:20:26 s|... https://github.com/w3c/wot-scripting-api/pull/561|-> https://github.com/w3c/wot-scripting-api/pull/561 PR 561 - Extended return type of invokeAction() 10:20:30 rrsagent, draft minutes 10:20:32 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 10:20:38 ... once I have time to work I will summarize the decision 10:21:17 TOPIC: Issues 10:21:30 SUBTOPIC: Use-case WoT in the Browser 10:21:36 ... https://github.com/w3c/wot-scripting-api/issues/566 10:21:47 CA: Issue coming from McCool 10:21:57 ... going over use-cases issues 10:22:06 ... we can validate use-case 10:22:20 ... report back with real feature request 10:22:32 ... it is about WoT in the browser 10:23:10 ZK: websocket is a possibility 10:23:35 s|... https://github.com/w3c/wot-scripting-api/issues/566|-> https://github.com/w3c/wot-scripting-api/issues/566 Issue 566 - [Use-case] WoT in the Browser| 10:23:36 rrsagent, draft minutes 10:23:37 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 10:23:50 CA: Ben in web-thing-protocol is a relevant CG 10:24:00 ZK: feedback from browser people 10:24:20 ... native dependencies in the browser... will not happen 10:24:36 q+ 10:24:52 CA: MQTT, CoAP, WebSocket and HTTP can be supported 10:25:13 Kaz: We need to think about use-case 10:25:31 ... we need to clarify what "WoT in browser" means 10:25:44 q+ 10:25:44 ... browser vendors supporting WoT ? 10:26:03 CA: It would be nice 10:26:04 q+ 10:26:16 ... I don't think it will happen 10:26:26 ... used as library is fine 10:26:50 ... requirements on browser ? 10:26:56 q- 10:27:24 ZK: Interest w.r.t. dependency 10:27:39 ... problem with external dependencies 10:27:52 ... not acceptable for browser vendors 10:28:04 ... we have to go with existing APIs in browser 10:28:42 CA: limited to HTTP, CoAP, MQTT, WebWocket ... 10:29:16 ZK: WoT is a web application 10:29:48 ... we cannot have Scripting API though 10:30:10 DP: We can 10:30:33 ZK: But just not as native.. just as JS library 10:31:15 q+ 10:31:21 ack z 10:31:22 ack d 10:31:44 DP: I think we can live with JS library 10:31:46 ack dape 10:32:08 CA: Correct, native support wasn't needed in the past 10:32:24 Kaz: Polyfill library 10:32:24 q- 10:32:29 CA: Yes 10:33:03 10:33:03 s/Polyfill library/If we're OK with starting with a Polifill library for WoT. That would make sense./ 10:33:28 rrsagent, draft minutes 10:33:29 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 10:33:35 q? 10:35:42 DP: Need to report it back to Use-Case taskforce 10:36:25 CA: Okay, user story is valid but no need on browser side 10:38:19 q? 10:39:20 q+ 10:39:20 q+ 10:39:58 ack da 10:41:22 DP: New workflow in TD/Use-case requires use-case to foster new features 10:41:41 CA: Work already done ... but can be described 10:42:22 Kaz: working group is main stakeholder, but work can be delegated to task force 10:42:43 ... if Scripting TF is okay with polyfill we can propose that 10:43:02 q+ 10:43:07 q- 10:43:08 ... can talk about it in main call 10:43:22 s/with polyfill/with starting with polyfill/ 10:43:25 rrsagent, draft minutes 10:43:26 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 10:43:35 MS: topic important 10:43:42 ... W3C is browser 10:44:12 ... we should submit this issue to use-case taskforce 10:44:28 ... need to clarify what is needed 10:44:40 q+ 10:44:52 ... not sure where the topic should be discussed 10:45:04 CA: Correct, touches many task forces 10:45:16 q- 10:45:30 Kaz: I am suggesting to bring this proposal to main call 10:45:40 ... we can discuss how to deal with it 10:45:44 q+ 10:45:48 q- 10:45:48 ack kaz 10:45:51 ... procedure/process can be discussed 10:46:16 ZK: Technical input to main call today 10:46:22 s/I am /That's why I'm/ 10:46:31 CA: Yes, our feedback is important 10:46:32 s/to bring/we bring/ 10:46:45 s/deal with it/deal with it as well/ 10:46:50 rrsagent, draft minutes 10:46:52 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 10:47:12 s/to main call/to the main call/ 10:47:59 CA: Good that we have a direction now (issue is rather old) 10:48:47 rrsagent, draft minutes 10:48:48 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 10:48:54 present- Zoltan_Kis 10:48:54 SUBTOPIC: Review Observe handler in the algorithms 10:48:59 ... https://github.com/w3c/wot-scripting-api/issues/455 10:49:12 CA: need to look into it again 10:49:29 [adjourned] 10:49:31 s|... https://github.com/w3c/wot-scripting-api/issues/455|-> https://github.com/w3c/wot-scripting-api/issues/455 Issue 455 - Review Observe handler in the algorithms| 10:49:37 rrsagent, draft minutes 10:49:38 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 10:49:49 present+ Zoltan_Kis 10:49:50 rrsagent, draft minutes 10:49:52 I have made the request to generate https://www.w3.org/2025/02/19-wot-script-minutes.html kaz 12:06:36 zkis has joined #wot-script 12:22:15 JKRhb has joined #wot-script 13:01:35 mahda has joined #wot-script 13:27:32 Zakim has left #wot-script 15:02:50 mahda has joined #wot-script 17:07:46 JKRhb has joined #wot-script 17:24:22 JKRhb has joined #wot-script 17:45:05 JKRhb has joined #wot-script 18:02:41 JKRhb has joined #wot-script 19:20:56 JKRhb has joined #wot-script 20:54:28 JKRhb has joined #wot-script 22:56:16 JKRhb has joined #wot-script 23:55:40 JKRhb has joined #wot-script