Meeting minutes
Organization
<kaz> manual.csv
McCool: Fady and I updated the manual.csv files
<kaz> PR 312 - Intel Nodejs Implementation 2022.06 Inputs
McCool: I added an Intel implementation and noticed a lot of duplicates, which are fixed by PR 312
… which is already merged
McCool: I also updated the draft for the implementation report in the WoT TD repository
wot-thing-description PR 1522 - WIP: June 2022 Implementation Report
McCool: The updated implementation report is based on the old one and on the results from the last plugfest
… gives a good idea about some gaps
… most of which are not surprising, given that we added new features recently
… I thought most of them are manual assertions, some of which might be misclassified
… in general, gives a good impression of where the gaps are. Most gaps are in the area of security and privacy
… also default values
… language negotiation, URI variables
McCool: We need to fill these gaps as we go forward
McCool: assertions should now be in order, links in the implementation report should now point to the assertion in the document
… sometimes there are missing references, due to dynamic generation by ReSpec. We should probably regenerate the port with a static version
McCool: Noticed a bug in the Intel manual.csv file, "true" should actually be "pass"
… (fixes the file)
Instructions
McCool: there are also instructions for the terminology used in the event's README file
Jan: How's the plan for this week?
McCool: Plan for this meeting is to organize the input data
… README has instructions for contributing during the event
<kaz> 2022.06.Online/README.md
McCool: For the organization, you only need to add a manual.csv file for adding a new implementation
Contributions
McCool: I would like to merge PR #313 now, any objections to merging?
<kaz> PR 313 - Intel Proxy Implementation 2022.06 Inputs
There are no objections, PR is merged
McCool: Toumura-San, can you also update your implementations?
ts: I haven't updated my implementation/the manual.csv yet, will do today
… does it also apply to discovery?
McCool: Discovery is only a template so far
… good point, implementation report draft, template.csv, and manual.csv need to be updated
… did you implement a directory, Toumura-San?
ts: No, I only implemented mDNS discovery
McCool: Most implementations for discovery will probably be manual assertions anyway
… I actually implemented a simple directory, I haven't run the test tool yet, will do today
McCool: Do you have a directory consumer, Toumura-San?
ts: Yes, but it is not public yet
McCool: No problem, only need the test results
McCool: In the discovery call, we should generate a manual.csv, probably based on the Editor's version, due to changes in the specification with regard to TDs that are not hosted by the Thing itself
… today, we will hopefully add this kind of "service exploration" in the discovery call
Kaz: Given the discussion today, it is my impression that we should ask the implementers for their implementation reports
… we probably should send a reminder with instructions
McCool: Good idea, discovery hasn't been finished yet, will finish discovery later and then send a reminder for both TD and discovery
McCool: For targeting certain testing gaps, people should open issues, I'll add this to the README
… (updates the event's README.md file)
McCool: What we should do here is creating issues for the gaps to signal to others that we are working on a certain topic
… for example, I plan to work on some gaps in security and language negotiation
… I don't have an implementation report for discovery, but by tomorrow it will be updated
… the TD one is okay, discovery will be finished by the end of the day, after the discovery call resolved a few PRs
… let me make some notes about this in the Wiki
… (updates the Wiki page)
<kaz> wiki
[adjourned]