13:05:21 RRSAgent has joined #wot-pf 13:05:25 logging to https://www.w3.org/2023/04/05-wot-pf-irc 13:11:31 ktoumura has joined #wot-pf 13:11:55 McCool has joined #wot-pf 13:14:02 cris__ has joined #wot-pf 13:14:08 topic: minutes review 13:14:42 mc: there is a confusing sentence, did the meeting happen or it did not? 13:14:58 ege: I don't know 13:15:07 ... not in the 28th for sure 13:15:53 mc: we are sharing the slide links everywhere 13:15:59 ... everybody can comment 13:16:12 ... there might be problems 13:16:20 ... they can't change the content 13:16:20 q+ 13:16:27 ... should we try to protect these? 13:16:46 ege: we can always close inappropriate comments 13:17:15 mc: yes we can even disable the comment feature, but the slide should be still accessible 13:17:32 ... at this point all the links are pubblic 13:17:55 Mizushima has joined #wot-pf 13:18:05 ... other than the first issue minutes look ok 13:18:13 s/look/looks/ 13:18:23 topic: dev meeting plan 13:19:21 q+ 13:19:49 s/topic: dev meeting plan// 13:20:20 kaz: as I reported there was a TD dev meeting 13:20:34 mc: did it happen on march 28th? 13:20:44 kaz: not sure the date I have to check 13:21:15 ... confirmed 28th of March 13:21:19 i|there is a con|-> https://www.w3.org/2023/03/29-wot-pf-minutes.html Mar-29| 13:23:11 i/as I/(Kaz joins)/ 13:23:18 topic: dev meeting plan 13:23:29 mc: we have two slide decks, architecture is good 13:23:45 i/we have to/subtopic: Architecture/ 13:24:02 ... there is an issue in the assertion comunication-platform 13:24:08 ... not sure it even make sense 13:25:12 ... also pre-shared keys should be changed to certificates 13:25:14 luca_barbato_ has joined #wot-pf 13:25:16 subtopic: discovery ù 13:25:24 s/ù// 13:25:57 i|subtopic|-> https://lists.w3.org/Archives/Member/member-wot-wg/2023Apr/0002.html Slides info (For Members)| 13:26:09 mc: I noticed that we are using an outdated URI for link-description-type 13:26:19 i|subtopic|-> https://lists.w3.org/Archives/Group/group-wot-ie/2023Apr/0001.html Slides info (For IEs)| 13:26:20 ... for the test we will consider correct both the old and the new one 13:26:25 rrsagent, make log public 13:26:30 rrsagent, draft minutes 13:26:31 I have made the request to generate https://www.w3.org/2023/04/05-wot-pf-minutes.html kaz 13:27:03 chair: McCool 13:27:18 mc: there is also a loop hole in tdd-http-alternate-language 13:27:30 present+ Kaz_Ashimura, Michael_McCool, Cristiano_Aguzzi, Ege_Korkan, Kunihiko_Toumura, Luca_Barbato, Tomoaki_Mizushima 13:27:41 ... people can satisfy the assertion even if they to do provide a TD with the right language 13:27:45 ... it needs to be updated 13:27:54 q+ 13:27:59 ... any other logistical things that we need to do ? 13:28:04 ege: what about the video? 13:28:10 mc: we didn't decide yet 13:28:23 i/there is a c/scribenick: cris__/ 13:28:49 ... the concern is record the meeting 13:28:51 q? 13:28:52 ack e 13:29:05 meeting: WoT-Testing/Profile 13:29:38 mc: we are settling for record a video blog in a separate setting 13:29:43 rrsagent, draft minutes 13:29:44 I have made the request to generate https://www.w3.org/2023/04/05-wot-pf-minutes.html kaz 13:29:56 ege: then where to be shared ? 13:30:05 mc: we need also to review it 13:30:14 ... so where you host it meanwhile ? 13:30:23 ege: we can use youtube 13:30:26 mc: or google drive 13:31:03 ege: regarding the timing, it might be too tight 13:31:07 mc: I know.. 13:31:19 ... we can mail the presentation too 13:31:24 ... without making the video 13:31:56 mc: what value the voice over adds? 13:32:02 ... maybe not that much 13:32:29 q? 13:34:51 kaz: thing about too much about the video does not worth it. We should focus on inviting people to the event 13:36:00 ... also we need to identify which features are important and prioritize accordingly. 13:36:07 mc: we will do this for discovery 13:36:33 ... my guess is that policy assertions might be sacrificed 13:36:44 ... other things might happen 13:36:58 s/thing about too much about the video does not worth it./Thinking about the video recording too much would not make sense./ 13:37:04 ... language is something that we need to provide to meet internationalization goals 13:37:10 s/focus on/rather focus on/ 13:37:18 q? 13:37:20 q+ 13:37:23 ack k 13:37:32 s/and prioritize/and prioritized/ 13:37:47 mc: I'll try to resolve some of the missing assertions 13:37:53 ... the list might get shorter 13:38:30 ege: a lot of these are best practices, I see this in all around our other spec documents. 13:38:45 ack e 13:38:46 q+ 13:38:46 ... I think we are shouting ourselves in the foot 13:39:01 ... we should consider where to move this best practices 13:39:16 mc: discovery is a web server 13:39:25 ... and it needs to be implemented in a secure fashion 13:39:39 ... we should discourage things that have security holes 13:40:12 ... lot of these assertions are need to create a secure service 13:40:44 ege: instructing people is good 13:40:53 ... but it is not a feature 13:41:02 mc: in architecture might be true 13:41:15 ... but in discovery a lot of them are really feature 13:41:32 ... there are some policies 13:41:59 q+ 13:42:27 mc: the point is that we have these assertions 13:42:32 q- 13:42:40 ... we have to figure it out how to test them 13:42:41 q+ 13:43:01 mc: discoverer behavior is important 13:43:06 kaz: I agree with Ege 13:43:28 ... but we need to discuss this important question another time 13:43:46 ... and now focus on charter discussion and closing the work of the current charter 13:44:07 ... during the arch call we might not get implementations for some of the assertions 13:44:20 ... therefore we should concentrate on important features 13:45:26 s/I agree with Ege/I agree with Ege, and that's why I also mentioned similar comments during the Architecture call yesterday./ 13:45:32 luca: if an assertion is important for interoperability it should stay, but if the assertion is about policies or nice to have features should be moved to another section 13:45:47 s/another time/another time for the next Charter period./ 13:45:54 s/but we need/However, we need/ 13:46:17 ... also is not good to have too many fuzzy assertions, because people might ignore them all together 13:46:36 s/now focus on charter/now should focus on discussion for the current Charter period/ 13:46:49 s/work of the/work for the/ 13:46:53 mc: another idea is to prioritize assertions that already have 1 implementation 13:47:01 topic: Testfest 13:47:21 mc: it is immediately after hannover fair 13:47:43 s/during the arch call we might not/Maybe we might not be going to/ 13:48:01 rrsagent, draft minutes 13:48:02 I have made the request to generate https://www.w3.org/2023/04/05-wot-pf-minutes.html kaz 13:48:36 q+ 13:48:36 mc: should we send a email to the group and confirm the dates 13:48:42 ack l 13:48:57 ack k 13:49:18 ... we will discuss it in the main call 13:53:33 q+ 13:53:44 mc: anything else? 13:53:55 ack k 13:54:01 kaz: the test task force should be clear about what to prepare for this event 13:54:13 mc: yes, we need to clean up readmes 13:54:22 subtopic: PR 13:54:28 s/what to prepare/what to be prepared/ 13:54:35 mc: we have a new PR 13:54:44 mc: merging 539 13:54:45 https://github.com/w3c/wot-testing/pull/539 13:54:59 +1 kaz 13:55:03 [adjourned] 13:55:40 s|https://github.com/w3c/wot-testing/pull/539|-> https://github.com/w3c/wot-testing/pull/539 PR 539 - Update saywot manual csv| 13:55:47 rrsagent, make log public 13:55:53 rrsagent, draft minutes 13:55:55 I have made the request to generate https://www.w3.org/2023/04/05-wot-pf-minutes.html kaz 14:09:33 luca_barbato_ has left #wot-pf 16:02:37 Zakim has left #wot-pf 16:13:29 s|WoT-Testing/Profile|WoT Testing/Plugfest| 16:13:31 rrsagent, draft minutes 16:13:32 I have made the request to generate https://www.w3.org/2023/04/05-wot-pf-minutes.html kaz