W3C

– DRAFT –
WoT Testfest - Day 4

09 June 2022

Attendees

Present
Daniel_Peintner, David_Ezell, Ege_Korkan, Elodie_Thieblin, Fady_Salama, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Sebastian_Kaebisch, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
Ege, kaz

Meeting minutes

Latest online version of the TD Implementation Report

TD Implementation Report: Automated Validation Results

McCool: I forgot that we need to add extra assertions
… Ege made a PR and fixed the issue

Ege: I am amazed that you did it manually, we should automate it

<kaz> (McCool shows report11.html on his PC)

McCool: So I have removed them from supressed.csv for the testing phase

McCool: now our report is looking better

Sebastian: we should implement the lower hanging fruits

McCool: yes so that we can see the actually difficult things

McCool: if you have targeted an assertion in your PR, mention it

Kaz: starting with this draft implementation report is fine, but we should organize this call better. So would suggest we capture the existing issues first, starting with the issue of the procedure, missing tests, etc. And then discuss how to solve them next.

McCool: (goes through the draft report11.html)

zero data

Ege: regarding the results with 0 data, should be the problem with the test mechanism itself

td-security-oauth2-client-flow

McCool: need one more implementation

td-security-auth2-code-flow

McCool: need 2 implementations

allOf

anchor--Link

Kaz: 2 dashes within the title correct?

McCool: yes, that's table assertion

at-type--SecurityScheme

contentCoding--Form

McCool: similarly with contentProtection

default--DataSchema

DigestSecurityScheme

minLength--SringSchema

multipleOf--IntegerScehema

McCool: surprising...

BasicSecurityScheme

McCool: similar to DigestSecurityScheme
… should be easy

ComboSecuritycheme

McCool: I have a proxy and still need one more

op--Form

McCool: surprised
… pretty much used

Ege: there are child assertions

McCool: right

queryaction

McCool: should be easy

Ege: not merged yet
… maybe some problem there

McCool: ok, need to clean it up

pattern--StringSchema

Ege: new feature

McCool: ok

proxy--DigestSecurityScheme

McCool: qop (quality of protection)

sizes--Link

McCool: just icon

subprotocol--Form

McCool: any child assertion?

Ege: just did yesterday
… there is just an example but no actual child assertion

tm-extend

McCool: TM assertions
… related to modularity of TM

placeholder

McCool: need some text

tmRef1

tmRequired

McCool: got one from Siemens
… and need another from the other implementers

Sebastian: kind of surprised

<Ege> tm-extend is tracked here: https://github.com/thingweb/thingweb-playground/issues/266

Daniel: node-wot should be able to cover it

McCool: consuming TM is a bit different

TD Implementation Report: Manual validation results

privacy-auth...

McCool: these are easy
… need manual assertions

td-context-ns-td10-namespace(v10)

McCool: test cases?

Ege: will work on the test cases

td-default...

McCool: handled by Consumers
… don't have many Consumers
… but surprised if node-wot can't handle this

(specifically, td-default-idempotent and td-default-in-apikey)

Daniel: let me check again

Sebastian: these features were included in TD 1.0 already

McCool: might be included in Huawei's results

Kaz: as I mentioned the other day, we should clarify how to deal with old results for compatible features
… importing the old results should be fine, though

McCool: ok
… wondering what implementation(s) cover all the features in addition to node-wot

td-ns-multilanguage-content-negotiation

McCool: need 2 implementations

security-extension

td-text-at-direction

McCool: need to cover the example

Kaz: do we have actual text within the spec?
… or just examples?

McCool: these assertions have been extracted from the spec text
… this can be covered by any existing TD (by adding an entry for this)
… for example, if a Web browser can consume a TD, that's also fine

Kaz: ok

PRs

PR 330

PR 330 - Update input data

McCool: need to update this PR itself

PR 324

PR 324 - Discovery: Add results for siemens-logilab

Elodie: you can merge this PR
… and then I can look into the details

(merged)

PR 328

PR 328 - Discovery: Add missing registration info IDs, remove auto tested tdd-notification

McCool: let's merge this
… cleaning up CSV for Discovery

(merged)

PR 332

PR 332 - Add siemens-logilab TDD thing description

McCool: about TD

(merged)

PR 334

PR 334 - manuel assertation CSV file for ediTDor

(merged)

PR 335

PR 335 - Added manual assertions CSV for Eclipse Ditto

McCool: using different name
… let me go ahead and merge this

Kaz: and then you'll check the problem later?

McCool: yes

(merged)

PR 336

PR 336 - Update README.md - Improve Instructions

McCool: just updated the instructions

(merged)

PR 317

PR 317 - Add manual.csv files for dart_wot

McCool: need Jan

PR 330

PR 330 - Update input data

McCool: need to update it
… can merge this and create another PR

(merged)

TD PRs

PR 1524

PR 1524 - Add old context value

McCool: bug fix

(merged)

PR 1532

PR 1532 - Allow placeholder for required and enum in TMs

Fady: placeholder must be located much upper

McCool: we're out of time
… let's discuss this tomorrow

AOB

Kaz: we should clarify what to discuss tomorrow
… if our goal is finalizing the test platform for this Charter period, that's fine
… but we should clarify our expectations

McCool: think our goals should be clarifying the gaps this time
… can have follow-up discussion next week

Kaz: in that case, we should clarify the plan for next week as well
… but let's do that tomorrow

McCool: ok
… tomorrow, we'll focus on finalizing the gaps mainly

[adjourned]

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