Meeting minutes
Minutes review
<kaz> July-9
Ben: Minor change due to my absence. Anyone have any comments on the current minutes?
Minutes Approved
Schedule
Ben: Target is to publish the note by end of July.
… Lots of PR's but it is still feasible
… Need a review of the process for publishing. Do we need to create a new folder to the Publications folder in the repo and copy the document there.
Kaz: Copy the static HTML version there. And then I can do the publication procedure.
Ben: Any questions on Schedule?
Ben: 8 PR's to review.
… Need to discuss having a call next week
Pull Request review
PR 426
<kaz> PR 426 - Re-work HTTP Webhook Profile - closes #423
Ben: open for 3 weeks and ready for review. This is a significant change.
Ben: Comments from Luca, we defined a new payload wrapper, and moved things to the data payload.
<EgeKorkan> +1 based on the explanation :)
<jthomas> +1 here since the only comment left is the one for a more standard def on Webhooks
Ben: Merging the PR based on notes here
PR 427
<kaz> PR 427 - Re-work Links section - closes #255
Ben: Last time we just were waiting on more time for review. Any comments or more time to review?
… Any objections to merge?
… PR 427 merged
PR 428
<kaz> PR 428 - Replace Accessibility Constraints with Accessibility Considerations section - closes #320
Ben: There was some constraints in accessibility saying there must have a title and description. This was moved to a consideration section not requirements.
… Any objections on merging?
PR 429
<kaz> PR 429 - Remove Default Language section - closes #373
Ben: This is a discussion on the default language section. This is a requirement of the language array and to remove it to fall back on the TD level. If Language negotiation has happened then it should appear otherwise the key is not required.
… Call to merge the PR, any objections?
PR 430
<kaz> PR 430 - Soften privacy and security assertions - closes #422
Ben: Had a discussion in 422 on the privacy considerations. We softened the consideration to move from Must to Should. Requiring all the privacy considerations would be overwhelming.
… Any objections to merging today?
PR 431
<kaz> PR 431 - Profiling mechanism clarifications - closes #385, closes #403, closes #404
Ben: Is an attempt to close three issues, these are about what a profile can and cannot do. This cannot be fixed in 1.0. We want to clarify. This changes some levels of requirements to Should. The profile should not redefine the defaults from the binding template.
… Next is a profile can extend the TD, but anything exposed in the TD should stay the same to someone that does not implement the Profile.
… Final issue is just because a thing conforms to a profile the consumer should not assume that it does in fact confirm.
PR 431 needs a final review from Ted
PR 433
<kaz> PR 433 - Duplicate conflicting assertion - closes #367
Ben: This is from SK, updates the assertions to the security section. We need to discuss EK, comment on the combo security scheme.
Ben: one use case is an auth bearer token. If you place it in the URL and Cookie, you need to use a Combo since each defines a different IN. They are the same type but different parameters.
Josh: With the combo, you need to define why the combo is an option. No Auth and any other option would be a good Combo. But defining two Bearer types with a different IN property would be a good example of how to use Combo.
Ben: we might merge this out to two PR's one for assertions, which is fixed, and one for the Combo scheme.
PR 435
<kaz> PR 435 - Fix broken link to Profile requirements - closes #434
Ben: There was a link that needed moved from Github to w3c. Issue in the comment was that the final destionation of the line might move again until published.
Assign 1.0 issues needing a PR
<kaz> Issue 360 - Clarify the behavior when a response does not have body
<kaz> Issue 432 - Should clarify our plan for WoT Profile 1.0 within the Introduction section
Ben: can take Issue 432, and am wondering if somebody can take Issue 360...
… will continue the discussion next week (we can use the Plugfest slot for Profile discussion next Wednesday)
[adjourned]