11:01:18 RRSAgent has joined #wot-pf 11:01:18 logging to https://www.w3.org/2022/06/08-wot-pf-irc 11:01:53 meeting: WoT Testfest - Day 3 11:04:20 McCool_ has joined #wot-pf 11:04:49 Fady has joined #wot-pf 11:05:09 present+ Kaz_Ashimura, Michael_McCool, Fady_Salama Meiyu_Hao Sebastian_Kaebisch, Tomoaki_Mizushima 11:05:14 present+ Ege_Korkan 11:05:42 zakim, who is on the call? 11:05:42 Present: Kaz_Ashimura, Michael_McCool, Fady_Salama, Meiyu_Hao, Sebastian_Kaebisch, Tomoaki_Mizushima, Ege_Korkan 11:05:57 ktoumura has joined #wot-pf 11:06:06 present+ Kunihiko_Toumura 11:06:21 Ege has joined #wot-pf 11:06:23 https://github.com/w3c/wot-thing-description/pull/1525 11:08:59 topic: PR 1525 11:10:22 scribenick: Fady 11:10:46 ElodieThieblin has joined #wot-pf 11:10:58 s/topic: PR 1525// 11:11:17 i|pull/1525|topic: TD PR 1525| 11:11:25 s/https/-> https/ 11:11:27 Ege: I added default assertion extraction in my PR in the wot-thing-desxription repo 11:12:00 s|pull/1525|pull/1525 wot-thing-description PR 1525 - Testing Cleanup and Assertion Extractor| 11:12:15 mm: My tool doesn't do that, I need to check 11:13:13 Mizushima has joined #wot-pf 11:13:22 Ege: I also updated the depends.csv 11:14:10 mm: We need to merge this and make sure we generate the manual.csv 11:14:24 q+ 11:15:05 Ege: The weird thing is that we it should have produced false gaps 11:15:27 mm: Then it would be good to do a sanity check 11:15:49 ack 11:15:56 s/ack// 11:15:56 Kaz: We need to clarify the procedure of the testing 11:15:57 ack k 11:16:30 s/testing/testing, and document it somewhere. probably on the wot-testing repository pointing each spec repo./ 11:17:12 mm: I see that we should merge. Sebastian, do you agree? 11:17:28 Sebastian: Yes we should merge 11:17:48 present+ Elodie_Thieblin 11:18:04 mm: merged 11:19:41 Ege: I think we need to document all the things that need to be pushed for testing 11:20:15 mm: Sure. Also I wanted to check the manual.csv, Ege and Fady, did you update it? 11:20:30 Fady: I pushed the new manual.csv 11:20:55 mm: PRs are better so we can see the diffs 11:20:57 q+ 11:21:35 topic: wot-testing PRs 11:22:26 ack k 11:23:32 subtopic: PR 324 - Discovery: Add results for siemens-logilab 11:24:00 mm: We will not merge this yet 11:24:09 -> https://github.com/w3c/wot-testing/pull/324 PR 324 - Discovery: Add results for siemens-logilab 11:24:28 subtopic: PR 326 11:24:30 subtopic: PR 326 - fixes ediTDor TMs 11:24:52 s/subtopic: PR 326 - fixes ediTDor TMs// 11:25:08 -> https://github.com/w3c/wot-testing/pull/326 PR 326 - fixes ediTDor TMs 11:25:37 Sebastian: This PR fixes the TMs and makes sure the assertion tester can test them correctly 11:25:46 mm: merged 11:26:20 topic: Current gaps 11:26:59 mm: bearer-format is not implemented by anyone, but can be marked as risk 11:27:25 ... security-flow as well 11:27:57 ... ComboSecurityScheme is also not implmented anywhere 11:28:49 ... ContentEncoding is currently also at risk 11:30:14 ... we can easily have examples exclusiveMinimum etc. 11:31:06 ... unobserveProperty is also missing 11:32:08 ... synchronous ActionAffordance is not implemented yet 11:33:29 ... Then we have manual assertions, mostly about security 11:33:38 gaps are documented here: https://github.com/w3c/wot-testing/issues/327 11:33:38 topic: Issues 11:34:13 mm: We are missing implementation descriptions 11:34:43 Issue 325 - Missing Implementation Descriptions 11:35:24 i|bearer|-> https://github.com/mmccool/wot-thing-description/blob/june-2022-impl-report/testing/report.html current implementation report for wot-thing-description 11:38:40 Issue 321 - Missing manual.csv contributions 11:39:13 mm: New manual.csv are generally neeeded for all implementations 11:39:15 q+ 11:40:49 kaz: We should clarify the expectations for the implementers 11:41:28 ... Github issues is not the best way to do things 11:44:05 mm: Can you update the instructions, Ege? 11:44:12 Ege: Doing it right now 11:44:38 mm: We will discuss these in the main call afterwards 11:44:38 https://github.com/w3c/wot-testing/issues/329 11:44:44 s/Github issues is not the best way to do things/using a GitHub issue to get data is a possible option, but we should clarify the whole procedure to get which data how and when, and then ask all the implementers to provide which data. Maybe creating a GitHub issue before that mentioning we are missing this data and that would not be very polite./ 11:45:12 mm: meeting adjourned 11:45:29 rrsagent, make log public 11:45:33 rrsagent, draft minutes 11:45:33 I have made the request to generate https://www.w3.org/2022/06/08-wot-pf-minutes.html kaz 11:47:31 chair: McCool 11:47:48 rrsagent, draft minutes 11:47:48 I have made the request to generate https://www.w3.org/2022/06/08-wot-pf-minutes.html kaz 11:59:05 @mccool I have stupidly deleted the readme I was writing, I am going to rewrite now... 11:59:10 hopefully will take less time 12:01:39 Mizushima has left #wot-pf 13:19:59 McCool_ has joined #wot-pf 13:30:08 https://github.com/thingweb/thingweb-playground/issues/258 14:02:32 Zakim has left #wot-pf