Meeting minutes
minutes
<kaz> Dec-1
Lagally: review minutes from 1 Dec 2022 (Arch call)
McCool: I was not there, but am noting the conversation about oauth; we need to look at the client flow, not the code flow; see comments on issues
Lagally: any changes needed to minutes?
… no objections, approved
McCool: see PR 331
<kaz> wot-profile PR 331 - narrowing down oauth required flows
Lagally: let's revisit
Testfest prep
Lagally: on implementation status, was looking at xrefs
… all vs min; min excludes 1.0 results
… long story short, merged by accident
Lagally: want to understand where we have gaps
McCool: so these are TD results, and want to avoid things that are not widely supported
McCool: need to differentiate corner cases (that may not even be good ideas) from things that are important but with few impls for other reasons
… e.g client flow
McCool: client flow is important for factory automation, but historically we only had code
Lagally: only impl seems to be from TinyIoT
McCool: would like to request client flow; also, note that oauth uses bearer tokens so adding that would not be a big implementation burden
<kaz> wot-profile PR 331 - narrowing down oauth required flows
McCool: in PR 331, seems we have a consensus to add client; also, in issue #41, mentioned that node-wot only does CLIENT flow, but this is not reflected in the result CSV files; we should investigate
… it may be the result files are in error
Lagally: (edits PR 331 to add client flow)
Lagally: in other subtopics, want to discuss what a simple consumer looks like
Lagally: for example, a simple consumer that reads a TD and invokes all actions
… for example, some are synchronous, some are asynch
McCool: personally suggest we have a number of small consumers for test purposes
Lagally: would be helpful just to have a code template
McCool: thinking just JSONparse and request in a node.js script
Contributions
Lagally: would like to merge everything today that we can and get to a draft
PR 331
<kaz> wot-profile PR 331 - narrowing down oauth required flows
Lagally: let's merge the updated PR 331 (code and client) flows.
Lagally: (merged)
PR 314
<kaz> wot-profile PR 314 - Allow auto security scheme for other permitted security schemes
Lagally: PR #314 - auto scheme, but only if results in another supported scheme
McCool: suggest we merge this, but raise additional issues for the other discussion points
Lagally: given ben's comments, will wait until next week
… mm, can you create issues for the related points?
McCool: ok
Lagally: then if no objections, will merge next week (even if no meeting)
PR 315
<kaz> wot-profile PR 315 - Improve link assertions
Lagally: PR 315 - improve link assertions
… change text to say "best effort"
… comment in a note, but it's not an editors' note, so would be in the final text
Lagally: propose merging
McCool: ok with me
Lagally: (merges)
PR 318
<kaz> wot-profile PR 318 - Converting from ednote to note
Lagally: convert ednote to note
… this is about readmultiple; don't want to remove from text, also remove the word "currently"
Lagally: does not really change language, ben agrees; suggest merging
McCool: concur
Lagally: (merges)
PR 321
Lagally: remove mention of plugfest experience in intro
<kaz> wot-profile PR 321 - Removing mention of plugfest experience
McCool: is old text
… agree to delete
Lagally: (merges)
PR 325
<kaz> wot-profile PR 325 - Webhook subscription mechanism
Lagally: webhook subscription mechanisms
… some fixes as discussed last week, listed in PR, eg. no payload in DELETE
… span->div change reverted
… need another pass though to completely resolve the "normative text in examples" problem; could add an ednote as temporary patch
Lagally: these changes are all in the webhook section, right?
McCool: I would vote to merge even if not perfect; can be baseline for further improvements
Lagally: is additional work coming for this section
Lagally: (merges)
PR 332
<kaz> wot-profile PR 332 - Testing CSV cleanup
McCool: just updates the impl report using the new tooling, also copied template.csv to manual.csv in prep for testfest
Lagally: (merges)
other PRs
McCool: have said I will refactor 297; will also look at 334
<kaz> wot-profile PR 297 - Revised Abstract and Introduction - fixes #115 and fixes #190
<kaz> wot-profile PR 334 - WIP: Provide example in the new introduction section
Publication
Lagally: already have a FPWD, should we publish an update?
<kaz> WoT Profile FPWD
McCool: support a WD update, will fix respec error as part of statics
<mlagally> proposal: use the current version of the editors draft including small editorial changes as the next working draft and publish it.
<mlagally> proposal: use the current version of the editors draft after fixing respec errors as the next working draft and publish it.
RESOLUTION: use the current version of the editors draft after fixing respec errors as the next working draft and publish it.
McCool: I will take care of generating the static version and will ask kaz to publish when it is ready
<kaz> [adjourned]