Meeting minutes
Agenda
<kaz> agenda for today
McCool: anything to add?
PRs
PR 417
McCool: there is a pr but it is still failing
<kaz> PR 417 - adding TD with async action
<kaz> Validation errors
McCool: the errors are difficult to understand
Ege: it seems that the json is invalid
McCool: we can merge it once that is fixed
PR 409
<kaz> PR 409 - Change procedure to include Consumers
McCool: I have thought about this, I think that we do not have time
Lagally: how was behavior testing done in TD?
McCool: we are over our deadline
McCool: we can add this to our new charter
Ege: my question is about how to handle the Consumer implementations
… how to manage actions, etc.
… we've not had discussion on how to test WoT Profile
… so wondering how to tackle this point
McCool: we do not do testing for security
… so that should be cleaned up
Ege: I think that profile spec should not be tested like we test the TD. Profile has specific assertions on the consumer behavior
Lagally: I understand the concerns. How should we do it though? A concrete proposal would be appreciated
kaz: I'd like to suggest again that we should clarify our policy on how to test Profile and Architecture first to avoid this kind of discussion repeatedly everyday
<sebastian> +1
McCool: do we agree that we should clarify testing of profiles
Ege: I can say that we have never tested profiles in a plugfest. There were some TDs submitted but I do not remember people using these TDs and experimenting with them
… I agree with kaz that we should clarify that
… and this PR was my proposal on how to test profiles
McCool: We can add another column to indicate whether an implementation is a producer or consumer
Lagally: that sounds good
Lagally: I think we can have 2 producer and 2 consumer implementations and do pairwise and cross pairwise testing
Lagally: that should satisfy the requirements
McCool: that sounds good, also for TD spec this makes sense
<mlagally> I agree that we also should apply the same methodology to TD testing
<kaz> McCool's comments for PR 409
Ege: the implementation descriptions do not say something about whether they are profile implementations (producer or consumer)
McCool: yes, we were not clear about that terminology
McCool: we should test profiles in a matrix but that might complicated with multiple profiles
kaz: I agree
Ege: did you merge the ditto PR?
McCool: yes, so that I can prepare for this meeting
PR 420
<kaz> wot-architecture PR 849 - Oct 2022 Testfest Updates to Implementation Report
<kaz> Draft Implementation Report
<kaz> PR 420 - Reorganize Files
McCool: I have reorganized the files via PR 420 Reorganize Files
… I had to change the ids of some TDs
TD Implementation Report
<kaz> wot-thing-description PR 1706 - Oct 2022 Testfest Updates to Implementation Report
<kaz> Draft Implementation Report
McCool: some tm optional features are fixed
Ege: for the tm versioning, I have created a PR to fix it in the TD spec. I will propagate the changes to the playground once merged
<kaz> merged https://
McCool: there are two assertions that seem to be broken
McCool: ege can you fix all the "all red" assertions
McCool: we have some assertion that have a single implementation
McCool: we need someone to put name in the basic security
McCool: you can see how to do it at intel nodejs implementation
<kaz> Intel's node.js implementation
Daniel: I can look into our examples and add it
McCool: we can leave the uri scheme to the PR transition, I can do it
McCool: we need client flow for oauth2
McCool: we also need the device flow but that is an odd one
… I do not care if we lose it
<kaz> PR 849 - Oct 2022 Testfest Updates to Implementation Report
<kaz> Draft Implementation Report
McCool: we are missing half of the implementations
McCool: I think we can spend half of the call tomorrow to go over the red ones
<kaz> node-wot TDs
Ege: I think that we need more and different submissions from people if we are going to test individual things instead of codebases
Daniel: we need to clarify the perspective before answering the questions
… also suppliying manual.csv for each thing would be too complicated
<kaz> Architecture Results of node-wot.csv
Lagally: I have fixed the problems in the PRs before, so they can be merged
McCool: I will merge PR 417 and 421
<kaz> PR 417 - adding TD with async action
<kaz> PR 421 - Schema Fixes to WoTWebThing+problemDetails.td.jsonld
McCool: I will update the reports accordingly
<kaz> [adjourned]