11:10:46 RRSAgent has joined #wot-script 11:10:46 logging to https://www.w3.org/2022/09/05-wot-script-irc 11:12:53 dp: we had a short meeting last time 11:12:54 TOPIC: Previous minutes 11:13:07 -> August-22 -> https://www.w3.org/2022/08/22-wot-script-minutes.html 11:13:32 dp: we talked about quick updates 11:13:38 ... the minutes looks good 11:13:47 ... we can remove empty sections 11:19:19 ... any objections? 11:19:23 ... ok minutes approved 11:19:28 topic: Quick updates 11:19:58 dp: it is pre-tpac week 11:20:13 ... it seems that every call will take place as usual 11:20:23 ... only main and testing calls are canceled 11:20:42 ... today I would like to discuss not the technical aspect but the agenda 11:20:54 ... I will ask mccool for a scripting slot 11:21:22 ... just notice that the next two meetings are cancelled 11:21:37 topic: TPAC Agenda 11:21:50 dp: I created threee different slots 11:22:01 ... one is the working mode for the next charter 11:22:09 ... different options: 11:22:37 ... stay in the Working Group and write an Informative Note 11:23:08 ... stay in WG but create a Formal Note (note track) . In this case we can have a conformance section 11:23:17 ... WG, REC track 11:23:39 ... and finally Community Group but there we don't have any W3C team support 11:24:04 ... in my understanding kaz can provide two slides with pro and cons about these four options 11:24:23 s/two/one or two/ 11:24:29 ... what do you think about this agenda point? 11:24:33 q+ 11:27:09 cris: I agree that we must discuss this with high priority. About the options my personal take would be to go with the 2nd option. is not that I don't like the others but I think they are harder to achive 11:27:25 dp: I agree 11:27:31 ack c 11:27:33 q| 11:27:33 q? 11:27:34 q+ 11:27:38 s/q|// 11:28:18 kaz: the options here are not really correct ( the terminology can be improved) 11:29:10 dp: Ok fixed 11:29:45 kaz: the problem is that people are not familiar with the latest status of the "process" document 11:30:08 ... I'd like to describe the essence of the document to everybody 11:30:13 dp: I totally agree 11:30:51 q+ 11:32:05 kaz: also the community groud produce a community group reoport and it is not endorsed by the W3C 11:33:43 ... notice that this information is reported by the status section in each document type 11:37:57 ... originally this presentation about the latest status of the process document was planned during the recharting presentation 11:38:13 dp: ok then we can try to schedule scripting discussion after it 11:40:25 kaz: we need to think also about potential push backs for the new charter 11:41:02 ... there is not just pro/cons but a rather complex mix of view points 11:42:46 ... anything else to add here? 11:42:49 q+ 11:42:55 ack k 11:42:57 ... should we collect pro/cons that we see? 11:43:22 mizushima: I would not add CG among the options 11:43:28 ... the direction of the group is not clear 11:43:54 ... there is no deliverables defined 11:44:17 dp: I agree I would not go to the CG 11:44:23 q+ 11:44:32 ack m 11:44:35 ... the point was raised by Zoltan to reach for a wider contributor pool 11:45:05 mizushima: CG is the last option 11:45:15 q? 11:45:32 ack c 11:45:39 cris: I agree 11:46:26 kaz: if we talk about these options we should also include people opinion 11:48:47 subtopic: Breaking changes 11:48:52 ack k 11:48:55 chair: Daniel 11:49:00 dp: we can discuss about Exposing process 11:49:11 ... also about discovery API 11:49:14 present+ Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi, Tomoaki_Mizushima 11:49:20 regrets+ Zoltan 11:49:24 rrsagent, make log public 11:49:32 rrsagent, draft minutes 11:49:32 I have made the request to generate https://www.w3.org/2022/09/05-wot-script-minutes.html kaz 11:49:36 ... do you have something that you want to present to the group 11:50:18 ... also actions support 11:51:16 s/dp: we had a short meeting last time// 11:51:29 i/we talked about quick/dp: we had a short meeting last time/ 11:51:30 rrsagent, draft minutes 11:51:30 I have made the request to generate https://www.w3.org/2022/09/05-wot-script-minutes.html kaz 11:52:07 meeting: WoT Scripting API 11:52:09 rrsagent, draft minutes 11:52:09 I have made the request to generate https://www.w3.org/2022/09/05-wot-script-minutes.html kaz 11:52:26 cris: I think we can discuss also additionalResponses and error codes 11:52:31 dp: I agree 11:52:42 s/threee/three/ 11:53:07 i/one is the/subtopic: Working mode for Scripting API/ 11:53:10 subtopic: Next charter 11:53:22 dp: mccool asked to report next charter topics 11:53:32 ... I collected some options 11:53:46 s/people opinion/people's preference, why they would like to go for which option/ 11:53:49 rrsagent, draft minutes 11:53:49 I have made the request to generate https://www.w3.org/2022/09/05-wot-script-minutes.html kaz 11:54:51 ... Discovery Alignment, TD profile support 11:55:01 ... also management API 11:55:31 ... finally, we can try to bring our API to project fugu 11:57:01 cris: about the last one we have a blocker: we need to define discovery api correctly 11:57:02 q+ 11:57:11 dp: any other topics to discuss? 11:57:40 kaz: during the Architecture call and testing call we discussed about how to test architecture specification 11:58:07 ... it seems that there are some assertions in the Architecture that are relevant to scripting implementations 11:58:35 ... it seems that we can have an implementation report also for scripting api 11:58:51 ... then how should we test a scripting API implementation? 11:59:48 ... also we should clarify the relationship between Architecture and Scripting. 12:00:39 s/and testing/and the Testing/ 12:00:54 s/ we disc/, we disc/ 12:01:06 s/discussed about/discussed/ 12:01:22 dp: anything else to discuss? 12:01:56 ... feel free to ping me if you want to add more topics 12:02:15 ... aob? 12:02:31 [adjourned] 12:02:38 rrsagent, draft minutes 12:02:38 I have made the request to generate https://www.w3.org/2022/09/05-wot-script-minutes.html kaz 12:03:02 join #wot-sec 12:03:48 rrsagent, bye 12:03:48 I see no action items