W3C

– DRAFT –
WoT Testfest - Day 3

27 July 2022

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, David_Ezell, Ege_Korkan, Fady_Salama, Kaz_Ashimura, Michel_McCool, Sebastian_Kaebisch, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
Fady, kaz

Meeting minutes

PRs

PR # 379

<kaz> PR 379 - update node-wot.csv for 2022-07

Daniel: It adds the manual.csv for node-wot implementation

McCool: A note, the csv is missing quotes

PR #381

<kaz> PR 381 - Add mqttExperimental implementation

McCool: adds mqtt experimental implementation
… looks fine

Implementation Report

McCool: it is taking a long time to run now
… I need to add Ege's implementation to batchValidation.sh

McCool: There are some TM at-risk items

Ege: Did you run the script on my new implementation?

McCool: I am doing it now... It's done

McCool: Seems to generate an error, Ege's file is not in the right directory, moving it there

McCool: *Running script on Ege's implementation only*

McCool: Seems to have solved a couple of missing at-risk items

Daniel: td-vocab-default--DataSchema is missing which I find strange
… we should have 2 implemenations: node-wot and Ege's mqtt implementation
… I just realized that the 2022.06.Online Testfest has newer node-wot Things than what is currently in the input_2022
… they should be copied over

McCool: I will copy them and rerun the script

Kaz: Did you copy all the implementations from previous plugfests into the input_2022?

McCool: Not exactly. I copied all the input data from them and generated all the results again. The question here is how to deal with multiple implementations based on one specific code base.

Kaz: At some point we categorized implementations based on the implementor and then we decided to switch to categorizing based on code-base

<dape> https://github.com/w3c/wot-testing/blob/b27e528c9989690f897e00fbc6a2354f785adfc2/events/2022.06.Online/TD/node-wot/TDs/siemens-dataSchemas.jsonld#L117

McCool: I may need to reorganize the results again, please remind me Kaz

Fady: I would like to have an overview of all the problems with tooling so I can keep track

McCool: Well you can create issues in playground and/or wot-testing repository
… Ege, can you write issues?

Ege: Yes
… I found the testing problems

Daniel: For tm-tmRef2, I realized that in old csvs, the assertion tag was tm-tmRef-2 and may , therefore, not be tracked by the tools

Fady: Exactly, tm-tmRef-2 and td-tmRef-2 are old assertions tags

McCool: I see, I found them in a saywot manual.csv and fixed that

Sebastian: editor manual.csv is not picked up

McCool: I found the issue in the script, will fix

Kaz: let's see the remaining problems based on that regenerated results tomorrow :)

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 147 (Thu Jun 24 22:21:39 2021 UTC).