W3C

– DRAFT –
WoT Testfest - Day 1

12 December 2022

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Fady_Salama, Kaz_Ashimura, Kunihiko_Toumura, Michael_Lagally, Michael_McCool, Ryuichi_Matsukura, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
Fady, kaz

Meeting minutes

Minutes Review

30 November 2022 Minutes

<kaz> Nov-30

McCool: published

07 December 2022 Minutes

<kaz> Dec-7

McCool: published

Logistics

McCool: We will review the instructions and CSV

Publication schedule

McCool: Moratorium is from Dec 23 - Jan 2 and the Deadline for publication request is Dec 21

Kaz: Publication Moratorium means no publication by the Webmaster, while the automatic publication for WDs is available. Also note that the Transition Requests for Architecture, TD and Discovery have been approved, and I'll work with the Webmaster for CR publication (though there is a note on Discovery)

CR Transition Request for Architecture

CR Transition Request for TD

CR Transition Request for Discovery

Logistics - revisited

Review Instructions

McCool: I will walk through the instructions
… Please make sure you are using the correct values in your CSVs
… for each spec we have particular things you have to do
… one special case is Profiles
… in Profiles and Architecture you put contributions directly in Results folder. Please do not to that with other specs

PR 494

<kaz> PR 494 - Manualcsv changelog for each implementation

Ege: I realized that we didn't impose a naming for manual CSVs. I made a PR to fix that

McCool: OK
… For TD or Profiles?

Ege: Just for TD

PR 493

<kaz> PR 493 - Update README.md: Adding Profile validation as goal of the testfest

Lagally: I created a PR that fixes broken links to Profile repo

McCool: *merges PR*

McCool: In Architecture, the CSV file format has changed
… but old CSV format should not be a problem
… you can use a tool provided by Ege to see changes

Ege: Yes, I tried the tool with TD and we can discuss specifics when looking at the PR

McCool: manual.csv in Architecture and Discovery and TD do not have the index

PRs

McCool: I will go through them from old to new

PR 409

<kaz> PR 409 - Change procedure to include Consumers

McCool: closed

PR 484

<kaz> PR 482 - Update processed results

<kaz> PR 484 - Manual CSVs for TUM implementations

McCool: I see that you updated some things so I will rerun my tools later to merge PR 482

McCool: *merged*

PR 485

<kaz> PR 485 - Remove commas from node-wot manual.csv

Ege: You can ignore this. I was trying to remove commas from all CSV files
… The problem happens when you use Excel to edit the CSV, you remove quotes around strings that have commas

McCool: I will update the README to warn about this issue

Kaz: Removing commas may solve the issue but maybe it would be better to use double quotes to show what is the value for the field.

McCool: I agree with kaz

Daniel: My PR does not have quotes. I will have to take a look

PR 487

<kaz> PR 487 - Add text direction guess pass to playground

<kaz> merged

PR 488

<kaz> PR 488 - Adding missing passes for multilanguage

McCool: this should solve an assertion, will merge and run the tool

<kaz> metged

McCool: This will probably not give us a complete pass but is a step

PR 490

<kaz> PR 490 - Update results for 3 (at-risk) security-related assertions in Discovery

McCool: merged

PR 492

<kaz> PR 492 - Add fujitsu test results

Ege: Can we change the name of manual.csv to the name of implementation name?

McCool: It should not be problem for my tooling

Ege: It would be easier for the tooling. We should either stick to all manual or all implentation names

Lagally: I also see that a profile tag being used so please use it as a contribution for profile spec

McCool: merged

PR 494

Ege: I changed the script for running batchValidation to make them use implentation.csv and went through all implementation and generated a changelog for them

McCool: I see that this is very nice information and I would merge it

Kaz: I don't think that we need to generate changelog everyday and see the changelog for this Testfest. Also, I don't think that we need to change every manual.csv to implementation.csv

McCool: I think that it is good for flagging stale assertions

Kaz: Then we need to tell people that we are still preparing for the testfest and ask for contributions starting from tomorrow

Lagally: I disapprove that we change something in input data from implementors and I don't think that we should use the time for looking at changes for just running tools that are not necessary in nature

McCool: So I ask Ege to revert the name changes to manual.csv files and and we are not going to merge the PR yet

Kaz: so we don't need to change the CSV file's name from manual.csv to implementation-name.csv, but we should still clarify what we want Matsukura-san to do

McCool: Matsukura-san, can you update the batch validation file quickly?

Matsukura: ok

PR 496

<kaz> PR 496 - Improve CSV contribution instructions

McCool: I am ok with merging this as long as keep in mind that this if meant for future submissions

McCool: *merged*

Kaz: if needed, we should explain the mechanism (and what we want people to do) around PR 494 within the README

<kaz> README for 2022.12.Online

McCool: the README has been updated, and the approach around PR 494 to be applied to the future Testfest

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).