Meeting minutes
Minutes Review
<kaz> July-13
Ege: the initials can be replaced
Kaz: Done, please refresh
Lagally: then we can publish
schedule
<kaz> wg-2021-extension-plan.md
Lagally: looking at the profiles, we should feature freeze today
… CR after testfest
Ben: I think we need to extend this, spec is not ready
McCool: start with thinking how much we can push it
Kaz: two possible options here
… 1. publishing a smaller stable spec this period or
… 2. publishing a full stable spec next Charter period
… the second option requires us to include it into the new Charter
(some more discussion)
McCool: could focus on some specific protocols, etc.
… we need to think about what to be done during this period
Lagally: we have to put all the remaining issues on the table
… and think about which to be deferred
McCool: right
Lagally: let's try to distinguish issues
Call logistics
Lagally: proposal of merging the Architecture call and the Profile call
Lagally: I would propose merging the arch and profile calls
Kaz: you mean just for one hour, either this slot or Thursday?
Lagally: I'm flexible
Ben: I can work only one day per week
Lagally: another possibility would be to start 1h earlier
Lagally: we reuse the existing slot and move discussion slot to wednesdays that concern ben
Ege: thursday slot is annoying for me
Lagally: what about starting an hour later on thursday
<mlagally> proposal: 2 hour slot on Thursday 11am UTC-1pm UTC,
Kaz: given the current two slots, one on Wednesday (the Profile call now) and another on Thursday (the Architecture call) are OK by all, I'd suggest we simply continue use those slots for a while until the Architecture spec is really finalized.
McCool: we can wait for the CR transition of arch. btw, Kaz, are you available at the proposed time above?
Kaz: I cannot make the second hour
McCool: we can start earlier today and move chairs call as well
Lagally: let's do a doodle poll
Issues
Issue 246
<kaz> Issue 246 - Refine assertions around 3xx redirect responses
Ben: I was surprised to see this text
Lagally: let's see the text
McCool: we can say that don't do 3xx unless it is for security
Lagally: is the behavior on 3xx well defined?
Lagally: for now, it seems safer to remove this assertion
Ben: these codes already have a meaning by the HTTP spec
<benfrancis> List of 3xx responses https://
PRs
PR 93
<kaz> PR 93 - WIP: reworking data model section
Lagally: this is a tracker like PR, it will never be merged
PR 119
<kaz> PR 119 - Add timestamps to event protocol binding - closes #100
Ben: this is simple and follows the recommendation of the SSE
Ege: I think that it is not good that two event profiles have different payload requirements
Lagally: that is another discussion, we can do talk about this later
Ben: ege's point is that PR 235 needs to be revisited
<benfrancis> Cloud Events issue: https://
<benfrancis> Suggest revisiting https://
PR 235
<kaz> PR 235 - CloudEvents as message payload format for WebHooks
Lagally: we can add this to the agenda
Ege: I think cloudevents in wot as a greenfield proposal is fundamentally wrong
Lagally: we should not open this discussion now, do it next meeting
Kaz: given we only have 5 more minutes, I'd suggest we open a new issue about this and deal with the issue next week.
Ben: I agree with Ege's points
Lagally: I will put this issue 126 in the next agenda
<kaz> Issue 126 - Dependency on Cloud Events
PR 121
<kaz> PR 121 - Add Discovery section to HTTP Baseline Profile - closes #112
Ben: My main proposal is that a TD should have a HTTP URL
Lagally: aob?
<kaz> (none)
<kaz> [adjourned]