WoT TestFest

08 May 2019



Kaz_Ashimura, Michael_McCool, Ege_Korkan, Kunihiko_Toumura, Taki_Kamiya, Tomoaki_Mizushima, Toru_Kawaguchi


<scribe> scribe: ege

at risk updates

McCool: concern that we are overmarking at risk items
... what is really at risk
... if the section is at risk, not marking the table
... what we don't have tests for and what is not implemented should be marked
... assertion is not a feature
... feature is like a set of assertions

Ege: like event as feature and subscription description as assertion?

McCool: give a name to a set of assertions
... label multiple assertions together
... new directory for the tds targeting the worksho
... but that are meant for testing
... to generate the report in the end for PR

<McCool> https://github.com/w3c/wot/tree/master/testing/tests/2019-05

McCool: so make your PRs to this directory
... now schedule
... same time as workshop

Ege: no, workshop is 3-5 june
... implementation report, some things are broken
... iri is a problem too, we might need to do it manually
... spent last week discussing on the text direction
... the language tags will be tricky
... built in format?
... I need to check

McCool: let's do the schedule
... (fills in the IG wiki with schedule)
... (finishes the schedule)

Kaz: a preliminary report is ok for CR transition
... we need a report fulfilled with two implementations for each feature for PR transition
... we can remove features marked as "at risk" when we transition to PR if we can't get implementations; and then move forward to REC

McCool: we can more flexible with features
... discussing our definitions
... (explains the schedule)
... we need to figure out oauth implementations

Ege: presenting schedule in main call

McCool: yes

<kaz> [adjourned]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2019/05/09 17:36:25 $