11:59:39 RRSAgent has joined #wot-pf 11:59:39 logging to https://www.w3.org/2022/03/18-wot-pf-irc 12:02:53 meeting: WoT Testfest/Plugfest - Day 5 12:03:07 present+ Kaz_Ashimura, Michael_McCool, Sebastian_Kaebisch 12:03:44 ryuichi has joined #wot-pf 12:04:02 ktoumura has joined #wot-pf 12:04:22 present+ Kunihiko_Toumura 12:06:27 Fady has joined #wot-pf 12:06:30 present+ Daniel_Peintner, Tomoaki_Mizushima 12:07:23 present+ Ege_Korkan 12:07:30 zakim, who is on the call? 12:07:30 Present: Kaz_Ashimura, Michael_McCool, Sebastian_Kaebisch, Kunihiko_Toumura, Daniel_Peintner, Tomoaki_Mizushima, Ege_Korkan 12:07:41 present+ Michael_Lagally 12:07:57 mlagally_ has joined #wot-pf 12:08:19 present+ Fady_Salama 12:08:59 chair: McCool, Fady 12:09:03 topic: minutes 12:09:05 scribenick: sebastian 12:09:11 https://www.w3.org/2022/03/17-wot-pf-minutes.html 12:09:13 scribenick: sebastiankaebisch 12:09:28 scribenick: sebastian 12:09:35 s/https/-> https/ 12:09:42 s/html/html Mar-17/ 12:09:47 any objection 12:09:48 no 12:10:47 topic: Policy for backward compatibility check 12:11:03 dape has joined #wot-pf 12:11:10 pproposal: we will use previous TD 1.0 submissions for TD1.1 (compatibility) testing if the only change needed is to add the context URL to the TD 1.1 version, in addition to the TD 1.0 context URL.. 12:12:07 we need to add TD 1.0 namespace at the first place 12:12:57 proposal: we will use previous TD 1.0 submissions for TD1.1 (compatibility) testing if the only change needed is to add the context URL to the TD 1.1 version, in addition to the TD 1.0 context URL. 12:12:58 q+ 12:13:44 Kaz: I'm ok with changing the namespace. For ECHONET is also ok. 12:15:21 s/also ok./also ok. So I'd suggest we check their TDs with both 1.0 context and 1.1 context for backward compatibility check./ 12:15:34 mm: yeah 12:15:51 MM: import all TDs from 1.0 TestFest, add v1.1 namespace 12:16:38 would also be possible to keep them separate in the implementation, under a "compatibility testing" column 12:16:49 s/implementation/implementation report/ 12:16:59 any objection to the resolution? 12:17:08 no 12:17:11 resolution: we will use previous TD 1.0 submissions for TD1.1 (compatibility) testing if the only change needed is to add the context URL to the TD 1.1 version, in addition to the TD 1.0 context URL. 12:17:19 topic: PRs 12:17:23 topic: check the PRs 12:17:51 https://github.com/w3c/wot-testing/pulls 12:18:15 MM: lets start with the PR that passed the test 12:18:20 https://github.com/w3c/wot-testing/pull/270 12:18:33 cris has joined #wot-pf 12:18:36 s/topic: PRs/ 12:18:54 s/topic: check the PRs/topic: Testfest/ 12:19:07 i/passed the/subtopic: PRs/ 12:19:13 s/https://github.com/w3c/wot-testing/pull/270/subtopic: #270 12:19:18 https://github.com/w3c/wot-testing/pull/270 12:19:27 rrsagent, make log public 12:19:33 rrsagent, draft minutes 12:19:33 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 12:19:54 MM: going to merge 12:20:03 subtopic: #271 12:20:14 https://github.com/w3c/wot-testing/pull/271 12:20:57 MM: TDs already aligned the namespace for the v1.0 and v1.1 case 12:21:14 MM: going to merge 12:21:24 rrsagent, draft minutes 12:21:24 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 12:21:38 subtopic: #272 12:21:53 https://github.com/w3c/wot-testing/pull/272 12:21:55 present+ Cristiano_Aguzzi 12:22:17 i/yeah/scribenick: kaz/ 12:22:27 i/import all/scribenick: sebastian/ 12:22:55 s/topic: PRs/topic: PR 271/ 12:23:05 s|/github.com/w3c/wot-testing/pull/270/subtopic: #270//github.com/w3c/wot-testing/pull/270|| 12:23:07 ML: its about pumps that are online 12:23:16 s/topic: #271/topic: PR 271/ 12:23:27 ... it also have event implementation in there 12:23:58 q+ 12:24:10 ack k 12:24:16 q+ 12:24:19 rrsagent, draft minutes 12:24:19 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 12:24:43 ML: should be compatible to v1.0 and v1.1 12:24:56 Ege has joined #wot-pf 12:25:47 just see there is dataResponse which is available in v1.1 12:25:53 q? 12:25:58 ack s 12:26:09 q+ Ege 12:26:11 ack e 12:27:36 ege: I don't see any problem here. Validator just follows the TD 1.1 spec 12:28:38 MM: lets merge it . Maybe is a test case for the validator 12:28:42 any objection? 12:28:43 no 12:29:09 topic: PR 274 12:29:26 https://github.com/w3c/wot-testing/pull/274 12:30:57 Ege: there are some problems with the version field 12:32:36 topic: PR 273 12:32:43 https://github.com/w3c/wot-testing/pull/273 12:32:57 present+ Ryuichi_Matsukura 12:33:08 Ege: strange that the validator complaints about the context. It seems be correct 12:34:12 s/273/276/ 12:34:13 s/273/276/ 12:34:19 topic: PR 276 12:34:25 https://github.com/w3c/wot-testing/pull/276 12:34:36 topic: Impl Report Drafts 12:34:48 q+ 12:34:52 Ege: test looks good. no fails in there so far 12:36:23 rrsagent, draft minutes 12:36:23 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 12:36:52 s/lets start/@@@PR270/ 12:37:54 i/strange that/@@@PR273/ 12:38:45 q+ 12:38:50 https://www.w3.org/2022/03/18-wot-pf-minutes.html 12:39:04 s/@@@PR270/let's start/ 12:39:11 i/let's start/@@@PR270/ 12:39:15 rrsagent, draft minutes 12:39:15 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 12:40:44 my proposal: if you see the following "data['@context'][0] should be equal to one of the allowed values, data['@context'] should be string, data['@context'] should be equal to one of the allowed values, data['@context'] should match exactly one schema in oneOf" please merge 12:41:09 MM: Ege will go over all PRs that have problems and try to solve the issue. 12:42:25 https://www.w3.org/2022/03/18-wot-pf-minutes.html 12:42:52 ML: I'm wondering if it is ok when we manipulate the TD of the submitter without asking before. 12:43:32 s/try to solve the problem/try to solve the problem (if it is a validator problem), or make a review (if it is an input data problem)/ 12:43:58 s/all PRs/PRs 273, 274, 275/ 12:44:03 Kaz: the proposal is about a specific PR and not for all PRs 12:44:17 q+ to if there is a context error, do we miss other errors? 12:44:27 i/the proposal/topic: expected proposal 12:44:40 @@@ Ege's proposal also moved to here 12:45:37 ack dape 12:45:37 dape, you wanted to if there is a context error, do we miss other errors? 12:45:50 ack k 12:45:55 topic: status implemantion report 12:46:50 12:47:03 ack e 12:47:07 MM: we have good results from discovery 12:47:26 @@@ Kaz will add manual edits to add clarification later 12:48:13 12:49:54 MM: the validation tool for discovery is live testing 12:51:47 if understand correctly so far there are many non implemented features listed, however, this is not correct since the validation tool does not work correct 12:52:24 MM: yes, we will check what is the issue here 12:53:45 q? 12:54:33 ML: is there a base line from the TD validation tool which we can reuse? 12:55:54 12:56:37 the legal values for test results are "pass", "fail", "not-impl", and "null". Other values, like "passed" will be ignored (treated as null) 12:57:48 this template is for the architecture test report 12:58:54 MM: please take a copy of the template file and modify your result 12:59:02 13:01:07 https://github.com/w3c/wot-testing/pull/279 13:01:40 q+ 13:02:14 sorry, I need to go 13:02:25 rrsagent, draft minutes 13:02:25 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 13:02:39 Kaz please can you take over 13:03:51 subtopic: PR 277 13:04:03 -> https://github.com/w3c/wot-testing/pull/277 Profile validation results 18.3. 13:04:21 mm: (goes through the changes 13:04:28 s/changes/changes)/ 13:04:56 ml: (adds clarification) 13:05:33 ... used the official JSON Schema for validation 13:05:54 mm: merge this? 13:06:07 ... useful to look at the results 13:06:10 (merged) 13:06:24 s/used the official JSON Schema for validation/used the official JSON Schema for validation with a couple of additional constraints/ 13:06:27 subtopic: PR 278 13:06:38 -> https://github.com/w3c/wot-testing/pull/278 PR 278 - Fix validation errors 13:06:45 ek: tested in my fork 13:06:49 mm: good to have it 13:06:56 ... can you re-validate everything? 13:07:14 ... will merge this PR itself 13:07:34 ek: if there is any problem, will be shown as failed 13:07:35 mm: ok 13:07:38 (merged) 13:08:22 subtopic: PR 274 13:08:36 -> https://github.com/w3c/wot-testing/pull/274 PR 274 - Fujitsu TDs 13:08:45 (problem fixed, and merged) 13:08:59 [Testfest part adjourned; 7min break] 13:09:02 rrsagent, draft minutes 13:09:02 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 13:10:14 s/topic: status implemantion report/subtopic: Implementation report/ 13:10:44 s/topic: expected proposal/subtopic: Expected proposal for PRs in general/ 13:11:09 s/topic: Impl Report Drafts/subtopic: Implementation report drafts/ 13:11:33 s/topic: PR 276/subtopic: @@@escape/ 13:11:49 s|https://github.com/w3c/wot-testing/pull/276|@@@URL escape| 13:12:02 s|topic: PR 276|topic: PR 273| 13:12:17 s|https://github.com/w3c/wot-testing/pull/276|https://github.com/w3c/wot-testing/pull/273| 13:12:37 s|subtopic: @@@escape|subtopic: PR 273| 13:13:06 s|@@@URL escape|https://github.com/w3c/wot-testing/pull/276| 13:13:16 s/topic: PR 274/subtopic: PR 274/ 13:13:22 rrsagent, draft minutes 13:13:22 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 13:14:36 s|https://github.com/w3c/wot-testing/pull/273|https://github.com/w3c/wot-testing/pull/276| 13:14:42 rrsagent, draft minutes 13:14:42 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 13:15:37 i/Implementation report drafts/PR 276/ 13:15:38 rrsagent, draft minutes 13:15:38 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 13:15:54 i/Profile validation/scribenick: kaz 13:15:56 rrsagent, draft minutes 13:15:56 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 13:15:57 ktoumura has joined #wot-pf 13:17:25 scribenick: cris 13:17:46 topic: agenda 13:18:13 mc: I want talk about vlan, is there something else you want to discuss? 13:18:17 s/topic: agenda/subtopic: agenda for the Plugfest part/ 13:18:29 ml: do you have any feedback regarding Oracle devices? 13:18:36 ... we can even discuss this offline 13:19:03 mc: there are no issue added, this means no additional projects 13:19:05 topic: vlna 13:19:18 s/vlna/vlan 13:19:27 mc: has anybody tried vlan? 13:19:30 ml: not me 13:19:37 s/topic: vlan/subtopic: VLAN for Plugfest/ 13:19:50 i/agenda for/topic: Plugfest/ 13:19:58 rrsagent, draft minutes 13:19:58 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 13:20:07 mc: I can't set the dhcp client 13:20:17 ... try to debug it but with no success 13:20:40 ... maybe is something about this pf2020 id 13:21:00 toumura: not sure 13:21:18 i|can't set the|-> https://github.com/w3c/wot-testing/blob/main/tools/vpn/vpn_softetherclient.md Setup instruction for SoftEther VPN client 13:21:22 rrsagent, draft minutes 13:21:22 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 13:21:56 mc: is there another place were I struggled the bridge 13:22:07 ... I needed to know the server ip address 13:22:09 but I can't find it 13:22:25 ... plus some steps are actually only needed for windows 13:22:43 ... i fix also a couple of things 13:23:29 ... some instructions for the AP would be useful 13:23:53 ... just the name of the tool would be sufficient 13:24:22 ... I haven't tried to do the no-bridge version 13:25:52 cris_ has joined #wot-pf 13:26:17 q+ 13:26:25 ack ml 13:27:05 mc: I want also to test mdns stuff 13:27:33 ... I hope that we can keep things up for a month or so 13:28:00 kaz: I suggest to file issues regarding this problems 13:28:11 mc: well, it is more a tool problem that test fest 13:28:34 ... even if we can add an issue about VLAN set up process 13:28:47 kaz: maybe we can use the last few minutes to wrap up 13:28:49 s/this problems/this kind of problems/ 13:28:55 ... and derive some results 13:29:07 subtopic: profile testing 13:29:47 ml: as you know we are working on the profile specification 13:29:47 ... I want to experiment more with what we have right now. 13:30:05 q+ 13:30:10 mc: you could document the process that you took to evaluate TDs 13:30:37 ... in the Profiles directory 13:31:19 13:32:14 s|maybe we can use the last few minutes to wrap up|I mean not only this specific problem with VPN setting but all the problems from this whole week in general. Given today is the last day of our Testfest/Plugfest this time, probably we should use the last 10-15 minutes to wrap up all the problems and think about how to resolve those problems. Probably we need another follow-up meeting to deal with them.| 13:32:57 ack k 13:33:15 ml: dittos TDs have wrong time format, I filed a issue about it 13:34:08 ... I have a WIP profile json schema 13:34:25 q? 13:34:34 mc: so you don't have all the profile constraints in there? 13:34:36 ml: not yet 13:34:53 i|as you know we|-> https://github.com/w3c/wot-testing/tree/main/events/2022.03.Online/tools/Oracle/TD-Profile-Validation/Ditto/TDs Oracle Profile results| 13:35:54 ege: I would recommend to not copy and paste the TD schema manually. It will probably updated 13:35:56 s/will/will be/ 13:36:13 ... instead I would create another schema 13:36:21 q? 13:36:21 ... with just restrictions about the profile 13:36:26 +1 13:36:27 ack e 13:36:36 q? 13:37:07 q+ 13:37:10 ml: thanks, I agree 13:37:40 q+ 13:37:53 ... I hoping the experts of JSONSchema validation would help Profile taskforce to define the proper schema 13:39:31 cris has joined #wot-pf 13:39:54 ml: I agree 13:40:06 ... we can do a double pass 13:40:19 ... TD schema first than profile later 13:41:07 kaz: this discussion implies that we'll need a versioned schema (with date) similar to w3c publication process 13:41:14 mc: I have a date version already 13:41:29 s/we'll/we might be going to/ 13:41:41 s/versioned schema/dated version of schema/ 13:41:51 s/ (with date)// 13:41:52 ... tecnically is the process that calls two schemas. You don't need an include 13:42:20 q+ 13:42:24 ack k 13:42:48 ml: but the TD scheme include nice defintions 13:42:55 ... that we can ri-use 13:43:12 q? 13:43:16 ack m 13:44:24 s/ri-use/re-use/ 13:44:28 ack c 13:44:55 cris: the problem is pretty similar to what we are dealing with in the protocol binding templates 13:45:06 s/with in/within/ 13:45:10 ... we are expirimenting with validatio with additional schemas 13:45:25 s/validatio /validation / 13:45:31 q+ 13:45:54 wip schema for modbus template https://github.com/w3c/wot-binding-templates/blob/main/bindings/protocols/modbus/modbus.schema.json 13:46:37 ege: is there any thing that implements the new actions 13:46:56 ml: yeah blue pump has the new model 13:48:21 ege: the validation schema is not an implementation report, it is only validation 13:48:40 ml: in the next pf calls we will probably talk about validation 13:49:04 mc: I want to continue this discussion in a more generic way 13:49:10 topic: wrap up 13:49:29 mc: It would be nice to have a profile testing issue 13:49:44 ... I'm also creating a plug fest TODO issue 13:49:55 ... with a list of things that we couldn't test 13:50:31 ... ege can you get some behavioral testing ? 13:50:46 ege: I'm overbooked with other testing tasks 13:51:10 ml: behavioral testing can be done manually 13:52:17 mc: some assertions might be done automatically 13:53:16 q+ 13:53:56 ack k 13:53:58 ack m 13:54:06 kaz: I would suggest to split the todos in TestFest and PlugFest 13:54:19 s/to split/we split/ 13:54:34 s/todos in/todos into/ 13:58:13 q+ 13:58:16 ... any other thing to do as follow up? 13:58:45 kaz: we should clarify expectations of collaborators 13:58:55 s/ kaz:/kaz:/ 13:59:03 ack k 13:59:21 ml: could we continue on Wednesday ? 13:59:24 mc: good idea 13:59:40 mc: adjourned 14:00:15 rrsagent, draft minutes 14:00:15 I have made the request to generate https://www.w3.org/2022/03/18-wot-pf-minutes.html kaz 18:09:49 Zakim has left #wot-pf