12:54:57 RRSAgent has joined #wot-pf 12:55:01 logging to https://www.w3.org/2023/05/03-wot-pf-irc 12:55:03 McCool has joined #wot-pf 12:56:00 meeting: WoT Testing/Plugfest 12:57:23 present+ Kaz_Ashimura, Michael_McCool 13:02:17 present+ Ege_Korkan 13:03:10 present+ Tomoaki_Mizushima 13:03:51 agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_03.05.2023 13:03:58 topic: Minutes 13:04:06 deferred 13:06:15 topic: New inputs 13:06:47 subtopic: PR 563 13:07:00 -> https://github.com/w3c/wot-testing/pull/563 PR 563 - Update Intel Web Speak with JSON Pointers for sec body 13:07:21 mm: (adds comments) 13:07:27 -> https://github.com/w3c/wot-testing/pull/563#issuecomment-1533001354 McCool's comments 13:08:31 mm: would like to resolve the four prioritized features 13:08:39 [[ 13:08:40 (1) sec-body-name-json-pointer - Intel 13:08:40 (1) sec-body-name-json-pointer-creatable - Intel 13:08:40 (1) sec-body-name-json-pointer-array - Intel 13:08:40 (1) sec-body-name-json-pointer-type - Intel 13:08:41 ]] 13:09:03 i/would like/topic: Organization/ 13:09:11 https://github.com/w3c/wot-testing/pull/563 13:09:14 Ege has joined #wot-pf 13:09:28 s/topic: Organization// 13:09:51 cris_ has joined #wot-pf 13:10:04 present+ Cristiano_Aguzzi 13:10:22 mm: (skims the changes for PR 563) 13:10:42 -> https://github.com/w3c/wot-testing/pull/563/files Files changed 13:10:54 mm: looked into the API Keys, etc. 13:12:29 ... (refers to the RFC 6901 (JSON Pointer) spec) 13:12:38 -> https://www.rfc-editor.org/rfc/rfc6901 RFC 6901: JSON Pointer 13:12:47 mm: think I'm correct 13:12:59 ... Ege, do you agree? 13:13:01 ek: yeah 13:13:09 ... I misunderstood something 13:13:28 mm: fixed example would be helpful 13:13:39 ... actual payload has two items in my case 13:14:03 ... helpful to have some description 13:15:13 ... wondering what the expected array usage is like 13:15:25 q+ 13:15:35 ... a bit confusing 13:15:58 ek: actual intention of two strings or one string? 13:16:13 mm: I mean two elements 13:16:42 ... need to define what the spec means 13:16:57 ... anyway it's confusing 13:17:05 ... Ege to fix the Playground 13:17:17 ... and then I need to re-run the test tool 13:18:10 kaz: please give clarification 13:18:33 ... so the problem here is a bug within the Playground tool? 13:18:47 ... no impact with the spec or the examples? 13:19:01 mm: it's a bug of Playground tool 13:19:12 ... no impact with the spec at all 13:19:33 kaz: any impact for the test results? 13:20:09 mm: Ege's results are wrong 13:20:23 kaz: meaning all the results processed by Playground? 13:20:26 mm: right 13:21:02 kaz: need to regenerate all the results for TD, Architecture and Discovery? 13:21:12 mm: for TD 13:21:43 ... regarding this PR itself, OK to merge it? 13:22:03 kaz: this PR itself is not for Playground but Intel's new test results 13:22:05 mm: right 13:22:17 (merged) 13:22:32 s/(merged)// 13:22:37 https://github.com/w3c/wot-testing/pull/559 13:23:09 ... would wait for the fix for Playground, though 13:23:35 s|https://github.com/w3c/wot-testing/pull/559|| 13:23:37 https://github.com/thingweb/thingweb-playground/pull/469 13:24:11 i|469|kaz: In that case, let's fix the bug first right away, then move ahead for another PR.| 13:25:11 q+ 13:25:17 ack k 13:27:01 kaz: would suggest we once fix the Playground, then check the result for one PR, then try the next PR 13:28:14 mm: however, running the test result generation would take long, so would like to merge PR 563 and PR 564 at once 13:28:27 kaz: that's not ideal, but for today, I can live with that 13:28:43 (PR 563 merged) 13:29:00 subtopic: PR 564 13:29:19 -> https://github.com/w3c/wot-testing/pull/564 PR 564 - Update wot experimental TD for apikey in body #564 13:29:19 13:29:24 (also merged) 13:30:00 kaz: just to make sure, Playground has been also fixed on another repository. right? 13:30:03 mm: yes 13:30:29 ... (then regenerate the test results) 13:31:38 ... just to make sure, any other PRs updating TDs? 13:31:47 ... found PR 562 13:31:57 subtopic: PR 562 13:32:11 -> https://github.com/w3c/wot-testing/pull/562 PR 562 - Updated TDs from latest master branch of WebThings Gateway 13:33:46 mm: seems to be using wrong suffix 13:34:03 ... would merge this PR once the data is fixed 13:35:31 ... also the batchValidation script has not been updated 13:35:39 ... I'll check that 13:36:28 (regenerating the result for TD without merging PR 562) 13:36:51 mm: it takes 10 mins or so to get the results 13:36:53 https://github.com/w3c/wot-testing/pull/559 13:37:18 s|https://github.com/w3c/wot-testing/pull/559|| 13:37:27 ... meanwhile, let's work on the other PRs 13:37:32 subtopic: PR 559 13:37:49 -> https://github.com/w3c/wot-testing/pull/559 PR 559 - Updated WoT Profile implementation report for WebThings Gateway 13:38:01 mm: some problems with Consumers 13:38:43 ek: we had discussion within the CG 13:39:23 ... it could be a Consumer from my personal viewpoint 13:39:25 q? 13:39:26 +1 for it to be considered as consumer 13:39:28 ack e 13:39:42 mm: Profile is not a critical path 13:40:08 sebastian has joined #wot-pf 13:40:11 q+ 13:40:19 present+ Sebastian_Kaebisch 13:41:18 kaz: we used to use the term, "Servient", which includes both Consumer and Thing 13:41:32 ... so a Gateway could be considered as a Consumer 13:41:35 ck k 13:42:14 mm: (adds comments) 13:42:20 -> https://github.com/w3c/wot-testing/pull/559#issuecomment-1533051982 first comment 13:42:31 [[ 13:42:32 For the TD deliverable, we do not have many at-risk assertions left so it's not critical to push the definition of "Consumer". Profiles will be dealt with in the next charter so it is also no critical. So I think we can merge these TDs for now without the Consumer assertions. 13:42:33 ]] 13:42:59 s/first/McCool's/ 13:43:01 (merged) 13:43:06 subtopic: PR 560 13:43:28 -> https://github.com/w3c/wot-testing/pull/560 PR 560 - Fix Size2 result for RIOT implementation 13:43:36 (merged) 13:43:41 subtopic: PR 561 13:43:59 -> https://github.com/w3c/wot-testing/pull/561 PR 561 - WoT Profile implementation report for Krellian Cloud 13:44:17 mm: wondering about the comments 13:44:22 ... but ok to merge it 13:44:25 (merged) 13:44:44 subtopic: PR 562 13:45:22 -> https://github.com/w3c/wot-testing/pull/562 PR 562 - Updated TDs from latest master branch of WebThings Gateway 13:45:38 s/subtopic: PR 562/subtopic: PR 562 (revisited)/ 13:45:46 mm: need to wait until the data is fixed 13:45:58 topic: Regenerated results 13:46:13 s/results/results for TD/ 13:46:32 q+ 13:46:51 ack k 13:47:02 kaz: have we got the updated HTML? 13:47:24 mm: still need to push the results to the wot-testing repo 13:47:34 ... (pushing the results) 13:47:42 rrsagent, make log public 13:47:46 rrsagent, draft minutes 13:47:47 I have made the request to generate https://www.w3.org/2023/05/03-wot-pf-minutes.html kaz 13:49:57 uploaded 13:50:11 s/uploaded// 13:50:26 ... (creates a new PR for wot-testing repo) 13:50:48 -> https://github.com/w3c/wot-testing/pull/565 PR 565 - New Testing Results for TD 13:51:03 mm: wondering about deletion around line 404 13:51:43 -> https://github.com/w3c/wot-testing/pull/565/files Files changes - oracle-wt.csv line 404 13:51:59 ek: think moved to automatic 13:52:08 (PR 565 merged) 13:53:44 mm: need to update the Implementation on wot-thing-description repo too 13:54:25 -> https://w3c.github.io/wot-thing-description/testing/report11.html Implementation report for TD 1.1 to be updated 13:57:44 mm: (sees the atrisk.csv at wot-thing-description/testing) 13:58:35 -> https://github.com/w3c/wot-thing-description/blob/main/testing/atrisk.csv wot-thing-description/testing/atrisk.csv 13:59:11 mm: all the four high-priority features for TD are addressed now 13:59:27 q+ 13:59:57 topic: Next steps 14:00:04 kaz: we're getting out of time 14:00:07 ... how to proceed? 14:00:19 mm: still need to update the results 14:00:46 ... also will update the test result page 14:00:57 q+ 14:01:01 -> https://github.com/w3c/wot-testing/tree/main/events/2023.03.Online Testfest results page 14:01:31 kaz: how to deal with them by when? 14:02:17 mm: we've extended the deadline as May 17 14:02:58 kaz: do you mean you want to continue to work on the data update by May 17 14:03:08 ... and see the updated results for all the 3 specs on May 17? 14:03:32 mm: would like to work on the data until at least May 10 14:03:40 ... and see the final results on May 17 14:05:01 kaz: do you mean the goal for that purpose should be all the features at risk listed on the results page above? 14:05:10 mm: yeah, at least all the priory features 14:05:22 kaz: could you make an intermediate report around May 10 14:06:00 s/10/10?/ 14:06:13 ... then think about how to proceed at that time 14:07:01 ... then if needed, we can continue to work on the remaining features by May 17 14:07:09 ... then see the final results on May 17 14:07:11 [adjourned] 14:07:16 rrsagent, make log public 14:07:21 rrsagent, draft minutes 14:07:22 I have made the request to generate https://www.w3.org/2023/05/03-wot-pf-minutes.html kaz 16:25:46 Zakim has left #wot-pf