Meeting minutes
Minutes review
<kaz> July-23
Ben: Any comments on the minutes from July 9th?
… Minutes approved
Agenda review
Ben: PRs to review and approve today
… any other items for the agenda today?
PRs
PR #431
<kaz> PR 431 - Profiling mechanism clarifications - closes #385, closes #403, closes #404
Ben: Any questions or comments?
… any objections to merging PR #431?
… merged
PR #433
<kaz> PR 433 - Duplicate conflicting assertion - closes #367
Ben: fixes assertions
… One item is limiting the security to a single security scheme
… any comments?
… there can be multiple schemes available but there must be a "oneOf" selection
Ege: this is OK
Ben: any other comments?
… any objections to merging #433 today?
(merged)
PR #435
<kaz> PR 435 - Fix broken link to Profile requirements - closes #434
Ben: changes a URL to github pages
… there is an issue with github links potentially changing
… we could keep the github pages URL or remove the use case reference entirely or create a W3C reference (which would also not be guaranteed stable)
Kaz: OK with keeping the github URL
Ben: any other opinions?
… any objections to merging #435
(merged)
PR #436
<kaz> PR 436 - Clarify behaviour when an HTTP request or response does not have a body - closes #360
Ben: handling of empty response body, response code and content-type
… clarifies that a JSON null is not an empty body
… any questions?
… any objections to merging PR #436
(merged)
PR #437
<kaz> PR 437 - Clean up markup
Ben: this is just cleanup of the markup
… making things consistent
… no normative changes
… does anyone need more time to review this?
Kaz: it would be nicer to have smaller PRs but this is OK
… anyone object tp merging today?
… will rebase to resolve conflicts and merge
PR #438
<kaz> PR 438 - Change document to Group Note and explain status of document - closes #432
Ben: Changes the document to note track
… need to try to avoid discouraging people from using the spec but make it clear this document isn't a REC
<kaz> Status section (diff)
<kaz> Status section (preview)
Ege: The respec HTML content can be changed without changing the URL of the document
<EgeKorkan> https://
Ben: OK we won't merge this PR as is but still need to get agreement on the text
Luca: it should be mentioned that there is already software implemented and working
Kaz: OK with the direction and the text is not a big concern
… technically, we could publish this as a WD instead but we've given up to bring WoT Profile 1.0 spec to the REC stage during this Charter period
PR #439
<kaz> PR 439 - Add a list of changes made since the 2023 Working Draft
Ben: changelog
… Is this an appropriate level of detail?
Kaz: yes
Ben: do people want more time to review this PR before we merge it?
Kaz: would like to talk with Philippe before submitting the transition request to verify the procedure
Ben: any objections to merging PR #439 today?
(merged)
Discuss 1.0 issues
Issue #347
<kaz> Issue 347 - Clarify OAuth schemes - consider requiring Bearer tokens only
Ben: Oauth bearer scheme is not good for interoperability because of the out of band token allocation
… since there is no concrete resolution, we should keep the current list of schemes
Ben: suggest closing this PR or deferring to after 1.0
… any other opinions?
David: agree that Oauth is a heavy lift, this is OK as is but maybe there needs to be an eventual solution
… Oauth is basically the only option
Ben: does anyone object to removing the Profiles 1.0 requirement for this?
… no objections
Issue #313
<kaz> Issue 313 - Include the "auto" security scheme to the list of supported schemes
<kaz> related PR 314 - WIP: Allow auto security scheme for other permitted security schemes
Ben: does anyone object to removing the Profiles 1.0 dependency (remove the 1.0 label from the issue)?
Kaz: OK
Ben: will remove the 1.0 label
Publication process
Ben: What are the next steps?
<kaz> 6.3.13.1. Abandoning an Unfinished Recommendation
Kaz: as put above, the latest W3C Process (section 6.3.13.1) says that we should publish a draft, which we have given up to bring to REC, as a "Discontinued Draft" instead of a "Note", so we need to talk with Philippe about the publication status as a Note. So I'll talk with him on Monday.
Ben: How do we create the PR to move the HTML to the publication folder?
Kaz: I can do that
Ben: do we need a resolution in the main call?
Kaz: yes, first a TF resolution then a group resolution
Ben: any other comments?
… OK, ready to wrap this up
… adjourned