Meeting minutes
Tooling issue
Two new assertions: tm-versioning-2 and tm-tmOptional-resolver
ege: I implemented two assertions and they were all red, but it should not
mc: I updated the implementation reports but I didn't update the tool
wot-thing-description PR 1715
<kaz> wot-thing-description PR 1715 - Add model and prohibit instance in tm schema
ege: I opened a PR to not diverge from the tool
mc: ok, but the tool does not need this PR to work correctly
ege: correct
mc: I feel uncomfortable merging because it goes in the TD repo
… but it is not critical and we can wait
… let's wait for Sebastian
problems with quotation
ml: question about problem on [["]] (quotation), I created a PR with some quotes
… we can look it later
… should I fix it? or should I wait for tool updates?
mc: let's wait for Ege
PRs
mc: I already merge a bunch to update the implementation report
PR 422
<kaz> PR 422 - additional operations on async actions
mc: I merged but I suspected to see updates in the assertions covered but they aren't
ege: it should be recognized
PR 423
<kaz> PR 423 - WoT Profile implementation report for WebThings Gateway
mc: profile implementation, the first result of manual.csv of profiles
… we have some inputs
ml: still working on the other manual.csv
PR 424
<kaz> PR 424 - Minor report updates for architecture/discovery
mc: contribution from Toumura-san for Arch and Discovery
… I updated the implementation reports of both
PR 426
<kaz> PR 426 - sync template for architecture
mc: Ege fixed some old assertions
ege: quite weird
… I hope that the reference that I used is updated
PR 429
<kaz> PR 429 - Update manual.csv
mc: it updates an old manual csv from the last TestFest
PR 428
<kaz> PR 428 - October 6 testfest updates
mc: did a bunch of re-organizations
… renamed directories to be consistent
… in general I didn't add new stuff but I clarified some titles
… not yet finished
… should I merge it right now and we can do updates later?
cris: +1 for merging right now
mc: feel free to make PR to improve descriptions and titles
PR 425
<kaz> PR 425 - 2022.09.plug+testfest profile validation 1
mc: big PR
… but it contains duplicated files because we said that TDs can be used both in Profile testing and TD testing
ml: in the candidates folder you can see Original and Processed. The original you can see TDs from past testfest
… Processed is the result of running processTD.sh
… which adds profile identifiers
… it is a starting point
… it adds a lot of input material to be used a dataset for validation
ml: there are many duplicates
mc: we can just look where we have gaps
ml: basically this is just a preparation
mc: I'm incline to merge this PR even if duplicates TDs
ege: it is weird that my submission it is use for Profile test
… I actually asked to do this thing an year ago
… it is late to use this approach
… you can do it offline
… and provide the result
… the motiviations are not clear
ml: why are you concerned? about the ownership of TDs used in the testing?
ege: I've never claimed to support Profiles
cris: why do we copy all the previous TDs in the original?
ml: I'm not concerned about the number of files in a git repository
mc: regarding Ege's point we can ask people if they let other to use their TDs
ml: ok, what is the process?
mc: we can do reverse permission
… ask people if they have any objections
… but how do we ask to people that are not inside the group anymore
… btw you can use Intel's TDs
kaz: actually to avoid this kind of discussions I suggest we clarify how to test Profile spec.
mc: profiles have a set of assertions that differ from TDs
… profiles covers a set of best practices that are not covered in the TD
… that is true for arch there are a lot of assertions that are duplicated
kaz: I agree, and that's why I've been suggesting we clarify which assertions from the Architecture spec and the Profiles spec to be covered by which test results, i.e., some by the results under Architecture and Profiles directly and some by referencing the TD results.
toumura: my implementation does not comply with Profile
… it uses different status codes
… it may cause some problems for testing
ml: people get the wrong impression that in the processed folder there are already profile complaints TDs
… it is a process
… they are not yet compliant indeed
… we can close this whole thing and I will come back with the schema
ege: most of TDs that are there are not Profile compliant
… unless they are doing bare minimum stuff
… before doing schema we should first check if they are profile compliant
mc: we can always use null
… and say that we are not sure
mc: PR closed without merging
implementation reports
Architecture report
<kaz> wot-architecture PR 849 - Oct 2022 Testfest Updates to Implementation Report
<kaz> rendered draft Implementation for Architecture
mc: re-run things
… some issues are now solved
… got new results
… we have 13 at risk items
… not bad
… a lot of these assertions may be turned to informative
… I am worried about DTLS assertions
… the other ones are not so critical
… any other comments?
ml: we already discussed
mc: there are couple of PII related assertions that should be already satisfied by TDD implementations
… we are making progress
Thing Description report
<kaz> wot-thing-description PR 1706 - Oct 2022 Testfest Updates to Implementation Report
<kaz> rendered version of the Implementation Report for TD
mc: we still have two not implemented assertions in security
… another one is about processor
… playground is all null, is that ok?
ege: maybe the test case is implented wrong for URI variables in sec scheme
mc: we should have more cancelaction and queryaction
ege: found bug
… fixing
mc: query all actions is not included in any implementation
mc: I have to re-run the tool
… we can look at the results tomorrow
<kaz> kaz: question about the Playground. Is Playground an actual implementation for Architecture and Thing Description?
<kaz> mm: let's revisit that tomorrow
<kaz> [adjourned]