01:21:40 kaz has joined #wot-pf 05:32:07 kaz has joined #wot-pf 12:45:56 RRSAgent has joined #wot-pf 12:45:56 logging to https://www.w3.org/2021/06/08-wot-pf-irc 12:46:16 Meeting: WoT Testfest - Day 2 12:59:25 McCool has joined #wot-pf 12:59:43 FarshidT has joined #wot-pf 13:01:09 ktoumura_ has joined #wot-pf 13:01:17 chair: McCool 13:01:27 present+ Kaz_Ashimura, Michael_McCook, Kunihiko_Toumura 13:01:51 Mizushima has joined #wot-pf 13:02:19 dape has joined #wot-pf 13:02:42 Hi, I am in another call. I will join after 10-20 minutes to discuss the validation PR. 13:05:52 cris_ has joined #wot-pf 13:06:19 present+ Andrea_Cimmino, Cristiano_Aguzzi, Daniel_Peintner, Philipp_Blum 13:06:28 present+ Tomoaki_Mizushima 13:06:35 present- Michael_McCook 13:06:40 present+ Michael_McCool 13:06:43 topic: minutes 13:06:51 mc: they look good 13:07:03 i|they|-> https://www.w3.org/2021/06/07-wot-pf-minutes.html June-7| 13:07:17 i/they/scribenick: cris_/ 13:07:28 present+ Christian_Glomb 13:07:41 present+ Sebastian_Kaebisch 13:07:50 rrsagent, make log public 13:08:04 mc: any objections to publish the minutes? 13:08:17 rrsagent, draft minutes 13:08:17 I have made the request to generate https://www.w3.org/2021/06/08-wot-pf-minutes.html kaz 13:08:50 ... minor problem with how "action" is recorded 13:09:03 ... ok minutes approved 13:09:24 topic: Agenda updates 13:09:33 mc: we have two prs 13:09:48 mc adding two points in the agenda 13:09:54 ryuichi has joined #wot-pf 13:09:58 topic: PRs 13:10:11 subtopic: PR 131 13:10:15 mc: it adds a github action 13:10:42 daniel: I am pretty sure that the action will kick in only for new prs 13:11:36 cris: some actions can be run manually 13:11:39 ... not this one 13:11:43 mc: let's try 13:12:29 subtopic Pr 133 13:12:34 mc: merging 13:12:42 ... ege does the playground handle TMs? 13:12:47 ege: no 13:12:57 mc: is it easy to add? 13:13:18 ege: yeah it is possible, just annoying from a design prospective 13:13:25 mc: we are just interested to the script 13:13:30 ... is there a way to do it? 13:13:36 ege: yes 13:14:13 ... however it is not just a simple validation so it might get tricky later on 13:14:41 ... but we can add a script dedicated to TMs 13:15:08 mc: we can collaborate with farshid to add it 13:15:17 q+ 13:15:33 ege: I want to add this feature in a consistent way 13:15:44 ... but I can write a dedicated script outside the playground 13:15:57 ack dape 13:16:03 dape: yeah we can just use ajv with our new schema 13:16:59 mc: I let you guys to choose the optimal way to solve this issue 13:17:07 topic: TD Testing 13:17:36 mc: we only have intel and siemens TDs 13:17:47 i|it adds a github|-> https://github.com/w3c/wot-testing/pull/131 PR 131 - Add Github Action to validate new TDs| 13:17:51 ... who else has plan to submit TDs ? 13:17:53 ege: I am 13:18:12 mc: I am worried about not having a good amount of TDs 13:18:55 i|mc: merging|-> https://github.com/w3c/wot-testing/pull/133 PR 133 - feat: add Siemens TDs and TMs files| 13:19:10 ege: small warning: some early TDs submitted by Mathias were autogenerated and had weird security schemes. 13:19:27 mc: where are they located? 13:19:49 ege: maybe under testfests 13:20:18 mc: can you find them? 13:20:55 present+ Ryuichi_Matsukura 13:20:59 rrsagent, draft minutes 13:20:59 I have made the request to generate https://www.w3.org/2021/06/08-wot-pf-minutes.html kaz 13:21:37 cris: should I add also wot farm TDs? they are generated by node-wot 13:21:42 mc: good question 13:22:15 ege: yeah we discussed about grouping TDs by implementation not organization. But there were some resistance a while ago 13:23:11 mc: I'll add a column keep track of the implementation 13:23:38 farshid: why don't move this column first? 13:23:45 ege: +1 13:24:00 mc: we actually care about different implementation from different companies 13:24:11 s/subtopic Pr 133/subtopic: PR 133/ 13:24:13 rrsagent, draft minutes 13:24:13 I have made the request to generate https://www.w3.org/2021/06/08-wot-pf-minutes.html kaz 13:25:38 present+ Farshid_Tavakolizadeh 13:25:45 mc: custom code/implementation need unique name 13:26:06 mc: still think to collect more TDs as possible even from node-wot 13:26:19 ... so please if you have them just add it to the repository 13:26:28 rrsagent, draft minutes 13:26:28 I have made the request to generate https://www.w3.org/2021/06/08-wot-pf-minutes.html kaz 13:27:10 i|we only have intel|-> https://github.com/w3c/wot-testing/tree/main/events/2021.06.Online/TD/TDs TDs so far| 13:27:14 ege: some dubts about naming implementations, what if I use a tech in a slightly different way? 13:28:17 i|can you find|(McCool look into the active.csv file then)| 13:28:29 mc: if you do custom coding based on a technology use a different identifier, just be mindful (i.e. if two implemantations share a lot of code use one id) 13:28:54 i|can you find|-> https://github.com/w3c/wot-testing/blob/main/events/2021.06.Online/TD/TDs/active.csv active.csv (which lists expected TDs from the group)| 13:29:02 rrsagent, draft minutes 13:29:02 I have made the request to generate https://www.w3.org/2021/06/08-wot-pf-minutes.html kaz 13:29:38 mc: geolocation is even more special, it is not an implementation 13:30:53 farshid: sorry any concerns about the PRs? 13:31:12 mc: can you add manual trigger? 13:31:31 present+ Ege_Korkan 13:31:39 ... another stuff is to handle also TM 13:31:41 rrsagent, draft minutes 13:31:41 I have made the request to generate https://www.w3.org/2021/06/08-wot-pf-minutes.html kaz 13:33:21 seb: I have a question about DID testing 13:33:32 q+ 13:33:37 ... how they will look like? 13:33:50 s/they will/will they/ 13:34:16 farshid: I have set up a repo for testing 13:34:44 seb: what self describing is? 13:35:09 mc: just expose the thing 13:35:16 mc: then we have introduction 13:35:23 s/introductions/ 13:35:36 ... that include DNS-SD 13:36:29 farshid: add link smart 13:36:39 cris: and webthings.io 13:36:46 mc: then we have DID endpoints 13:36:55 ... and finally CoRE RD 13:37:37 ... need volontiers for DID 13:37:59 ... I can do one implementation 13:38:12 ... also CoRE RD 13:38:46 kaz: regarding DIDs github is also a method 13:39:16 ... also I have a question to farshid. Can you add one liner about what the action does 13:40:36 farshid: a manual action is easier to set up but it takes a lot of time 13:41:01 mc: it is not necessary to scan the entire repository 13:41:15 ... maybe we can trigger manually only in one repository 13:41:49 farshid: best way is to extract relevant parts and run it locally 13:42:01 mc:ok back to introductions 13:42:08 ... CoRE RD is important 13:42:21 s/what the action does/what the validation action does (on the testfest page)?/ 13:42:34 cris: I can 13:43:15 Philipp: I could, but I have more relevant work to do 13:43:47 mc: one implementation is fine and commiting doing it 13:44:05 ... by the end of the summer is good 13:44:38 seb: I can do it but I need a little bit guidance 13:44:58 s/page)?/page)? That would be part of the Testfest guideline, I think./ 13:46:09 cris: about DNS-SD should we have tests about discoverer side? 13:46:11 mc: yes 13:46:30 farshid: shouldn't we do the same for TDD 13:46:51 mc: not really, it is fine to test just the api 13:48:09 farshid: testing the discoverer is tricking we would mock everything 13:48:54 mc: we should test the entire process 13:49:27 toumura: we have also another discoverer 13:49:34 ... my node-red implementation 13:49:45 mc: anything else? 13:49:46 q+ 13:49:53 q- 13:50:09 mc: please send your TDs 13:50:31 ... it would be nice to have oauth tds 13:50:36 q+ 13:51:00 ... any known gap to be worried? 13:51:14 ... I would add oauth and body 13:51:33 ... maybe TMs, but siemens has a lot of them 13:51:39 ... we need a second implementation 13:51:58 daniel: maybe the one from Vorto 13:52:53 seb: I have to check, but we could ask Koster and Legally 13:53:22 s/Legally/Lagally/ 13:53:43 farshid: are you looking for implementation about oauth? or what else? 13:54:08 mc: we have to decide 13:54:21 farshid: linksmart has implementation 13:54:45 ... but it uses openID 13:55:25 mc: we don't have a security schem for openID but we can describe it using oauth 13:56:35 daniel: node-wot has some flows implemented 13:57:04 farshid: there is also Node-RED 13:57:43 mc: the second producer could be the second directory 13:58:06 andrea: not sure my directory will have oauth 13:59:29 mc: conolicalization it is cover by intel 13:59:40 ... maybe the second one could the the directory 13:59:48 s/conolicalization/canonicalization/ 14:00:02 ... signing still need to be finish but I am confident to close it soon 14:00:51 seb: is it xml signature? 14:01:13 mc: not actually it is inspired by it but it uses jws 14:01:56 daniel: node wot could have canonicalization 14:02:12 cris: +1 14:02:33 mc: I would write a script and node-wot could use it as inspiration 14:03:12 cris: node-wot has also the producer side 14:03:28 s/producer/oauth producer/ 14:03:41 daniel: farshid's farshid action is working 14:03:54 ... a bit tricky to understand why it failed but it is ok 14:04:25 -> https://github.com/w3c/wot-testing/pull/135 14:05:29 kaz: it would be better to consolidate the todo list on the GitHub side 14:05:41 mm: let's do that next time 14:59:36 ryuichi has joined #wot-pf 14:59:36 citrullin has joined #wot-pf 16:12:08 Zakim has left #wot-pf