W3C

– DRAFT –
WoT Testfest/Plugfest - Day 1

14 March 2022

Attendees

Present
Ben_Francis, Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Fady_Salama, Kaz_Ashimura, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Philipp_Blum, Sebastian_Kaebisch, Tomoaki_Mizushima
Regrets
-
Chair
Fady, McCool
Scribe
cris, Fady__, kaz

Meeting minutes

Testfest

Fady: welcome everyone

PRs

<kaz> PRs

McCool: we merged a bunch of PRs
… TMs and TDs has been added
… ditto TMs and TDs are faling validation

Ege: they should be fine, idk why they don't work

McCool: ok, we'll check them later
… merging PR 226

TD area for March Testfest

<kaz> 2022.03.Online/TD

McCool: we are grouping TDs by implementations
… is anybody else doing any implementation description?
… intel directory is not the best example
… I'll update it later
… good example is node-wot directory

<kaz> (McCool goes through the sub-directories of Ditto, Intel, Oracle, editdor, hitachi-esp-idf, hitahchi-node-red, node-wot)

McCool: Hitachi has an online instance working together with discovery implementation

Toumura: VPN is also available
... editdor folder has nothing live

Sebastian: correct they were all generated using ediTDor

McCool: it seems there are some duplicated TDs/TMs

Sebastian: good point I have to check

McCool: ok we might treat tools differently

McCool: there is a sintax error inside manual.csv file in the root folder
… we need to fix this after
… some assertions need to be fixed as well
… probably the active.csv template needs to be updated with additional information like links or a boolean saying if it is inside the VPN

Lagally: why don't we use the default assumption that if the active file is not avaible everything in the folder is online

McCool: I think is better if anyone states the status in the active.csv file
… any other updates for the tool descriptions?

Fady: not yet

McCool: about manual cvs a solution might be to delete the comment column

Ege: but people need it to understand the assertion

McCool: well people can just check the documentation this is not meant to be a reference

Ege: I would prefer to keeping it
… I was wondering also were this file coming from

Ege: it is from playground

McCool: we also have an interoperability problem between the scripts that generate the reports
… the csv that my tool don't create the comment column
… but Toumura's script does

Toumura: my tool is uploaded

<ktoumura> my extraction tool

McCool: I pinpoint the right output file for my assertion extractor, it still doesn't contain the text
… although for tools is not critical to know the the assertion text

McCool: published the template.csv generated with my tool
… be careful about iana-security-* assertions
… I'll update them cause they are not really useful, they are almost just recommandations rather than assertions
… discovery call today is confirmed and there we are going to organize testing
… in architecture we have a directory for implementation descriptions
… are we ready for profiles? do we have assertions etc.?

Lagally: I think we can prepare for that
… so that we are ready when everything is in place

Ege: for the implementers what they need to do?

McCool: we have description for it but it might need improvements
… I can add a link to the CSV

Daniel: we talked a lot about csv fixes, is active.csv ready?

McCool: yeah

<kaz> [Testfest adjourned]

Continue Testfest Organization

wot-architecture organization

McCool: organizing template for wot-architecture

Lagally: maybe it would be better to add the assertion text

McCool: We could but that file wasn't meant for that
… implemetation report has the descriptions
… not all are understandable or self-contained

Ege: We will not be able to validate architecture using assertion tester

McCool: Sorry, that will not happen. HTML is work in progress
… will not do anything now until I talk with architecture-team because of conflicts

Plugfest

McCool: Are there any Plugfest projects?

Lagally: depends on what is available
… Ben do you have something?

Ben: I will not be able to attend all Plugfest calls due to personal commitments but we have a snapshot of a discovery implementation
… we have some open issues with TD
… on the Profiles side we implemented all properties and events interactions

McCool: It may be better to have another directory for Plugfest

Lagally: No need to complicate the process

Ege: Ben, if you change file endings and update @context your files will pass validation

Ben: Not sure if a snapshot is more useful or if I manually edit them would be of more use

Ege: manually edited files would be good to have examples for specific assertions

Ben: If I have more time I could setup a life instance
… it would be public

McCool: We can check off the parts that does pass the validation. Especially oauth2

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).