11:01:44 <RRSAgent> RRSAgent has joined #wot-profile
11:01:44 <RRSAgent> logging to https://www.w3.org/2022/07/20-wot-profile-irc
11:01:50 <kaz> meeting: WoT Profile
11:01:52 <Mizushima> Mizushima has joined #wot-profile
11:02:17 <kaz> present+ Kaz_Ashimura, Michael_Lagally
11:02:22 <kaz> chair: Lagally
11:06:17 <kaz> scribenick: Ege
11:06:43 <kaz> present+ Ben_Francis, Ege_Korkan, Michael_McCool, Tomoaki_Mizushima
11:07:24 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_July_20th.2C_2022
11:07:59 <Ege> topic: Minutes Review
11:09:04 <Ege> ek: the initials can be replaced
11:09:11 <Ege> kaz: Done, please refresh
11:09:18 <Ege> ml: then we can publish
11:09:19 <kaz> i|the initi|-> https://www.w3.org/2022/07/13-wot-profile-minutes.html July-13|
11:09:20 <Ege> topic: schedule
11:09:49 <Ege> ml: looking at the profiles, we should feature freeze today
11:10:06 <kaz> i|looking|-> https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md wg-2021-extension-plan.md|
11:11:03 <Ege> ... CR after testfest
11:11:05 <benfrancis> q+
11:12:00 <Ege> bf: I think we need to extend this, spec is not ready
11:12:51 <kaz> q+
11:12:57 <kaz> ack b
11:13:14 <Ege> mm: start with thinking how much we can push it
11:14:06 <Ege> brb
11:14:41 <kaz> kaz: two possible options here
11:14:54 <kaz> ... 1. publishing a smaller stable spec this period or
11:15:15 <kaz> ... 2. publishing a full stable spec next Charter period
11:15:30 <kaz> ... the second option requires us to include it into the new Charter
11:15:37 <kaz> s/brb/scribenick: kaz/
11:16:27 <kaz> (some more discussion)
11:16:47 <kaz> mm: could focus on some specific protocols, etc.
11:17:01 <kaz> ... we need to think about what to be done during this period
11:17:14 <kaz> ml: we have to put all the remaining issues on the table
11:17:24 <kaz> ... and think about which to be deferred
11:17:29 <kaz> mm: right
11:17:59 <kaz> ml: let's try to distinguish issues
11:18:34 <kaz> topic: Call logistics
11:18:45 <kaz> mm: proposal of merging the Architecture call and the Profile call
11:18:54 <kaz> q+
11:19:12 <Ege> ml: I would propose merging the arch and profile calls
11:19:24 <kaz> i/would/scribenick: Ege/
11:19:30 <kaz> s/mm:/ml:/
11:19:41 <benfrancis> q+
11:19:44 <kaz> ack k
11:20:13 <kaz> kaz: you mean just for one hour, either this slot or Thursday?
11:20:17 <kaz> ml: I'm flexible
11:20:36 <kaz> i/you mean/scribenick: kaz/
11:20:50 <Ege> bf: I can work only one day per week
11:21:06 <kaz> i/can work/scribenick: Ege/
11:21:16 <Ege> ml: another possibility would be to start 1h earlier
11:21:53 <Ege> ml: we reuse the existing slot and move discussion slot to wednesdays that concern ben
11:21:58 <Ege> q+
11:22:13 <kaz> ack b
11:23:18 <kaz> q+
11:23:20 <kaz> ack e
11:23:24 <Ege> ek: thursday slot is annoying for me
11:24:20 <Ege> ml: what about starting an hour later on thursday
11:24:24 <mlagally> proposal: 2 hour slot on Thursday 11am UTC-1pm UTC,
11:25:12 <Mizushima> q+
11:25:32 <Ege> mm: we can wait for the CR transition of arch
11:26:01 <Ege> kaz: I cannot attend the second hour
11:26:27 <kaz> ack k
11:27:33 <kaz> i/can wait/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./
11:27:33 <Mizushima> ack Mi
11:27:48 <Ege> mm: we can start earlier today and move chairs call as well
11:27:57 <kaz> s/of arch/of arch. btw, Kaz, are you available at the proposed time above?/
11:27:58 <Ege> ml: let's do a doodle call
11:28:00 <Ege> topic: Issues
11:28:12 <kaz> s/cannot attend/cannot make/
11:28:35 <kaz> i/given the/scribenick: kaz/
11:28:43 <kaz> i/we can wait/scribenick: Ege/
11:29:10 <Ege> bf: I was surprised to see this text
11:30:10 <Ege> ml: let's see the text
11:30:24 <Ege> mm: we can say that dont do 3xx unless it is for security
11:31:59 <kaz> s/dont/don't/
11:32:11 <Ege> ml: is the behavior on 3xx well defined?
11:32:18 <kaz> i/I was/subtopic: Issue 246/
11:32:35 <kaz> i|I was|-> https://github.com/w3c/wot-profile/issues/246 Issue 246 - Refine assertions around 3xx redirect responses|
11:33:43 <Ege> ml: for now, it seems safer to remove this assertion
11:35:40 <Ege> bf: these codes already have a meaning by the HTTP spec
11:36:12 <kaz> q+
11:36:47 <McCool> McCool has joined #wot-profile
11:36:54 <benfrancis> List of 3xx responses https://developer.mozilla.org/en-US/docs/Web/HTTP/Status#redirection_messages
11:38:27 <Ege> subtopic: Issue 93
11:38:49 <Ege> subtopic: PR 93
11:38:59 <Ege> ml: this is a tracker like PR, it will never be merged
11:40:25 <kaz> s/subtopic: Issue 93//
11:40:43 <kaz> i|this is a|-> https://github.com/w3c/wot-profile/pull/93 PR 93 - WIP: reworking data model section|
11:40:58 <Ege> subtopic: PR 119
11:41:02 <kaz> q?
11:41:03 <kaz> ack k
11:41:17 <kaz> -> https://github.com/w3c/wot-profile/pull/119 PR 119 - Add timestamps to event protocol binding - closes #100
11:41:32 <Ege> bf: this is simple and follows the recommendation of the SSE
11:42:04 <Ege> q+
11:43:55 <Ege> ek: I think that it is not good that two event profiles have different payload requirements
11:44:55 <kaz> ack e
11:45:43 <Ege> ml: that is another discussion, we can do talk about this later
11:46:17 <Ege> bf: ege's point is that PR 235 needs to be revisited
11:47:19 <benfrancis> Cloud Events issue: https://github.com/w3c/wot-profile/issues/126
11:47:48 <benfrancis> Suggest revisiting https://github.com/w3c/wot-profile/pull/235
11:48:05 <kaz> q?
11:48:47 <kaz> subtopic: PR 235
11:48:57 <kaz> -> https://github.com/w3c/wot-profile/pull/235 PR 235 - CloudEvents as message payload format for WebHooks
11:49:38 <Ege> ml: we can add this to the agenda
11:50:01 <Ege> q+
11:51:08 <kaz> ack e
11:52:17 <kaz> q+
11:53:29 <benfrancis> q+
11:53:42 <Ege> ek: I think cloudevents in wot as a greenfield proposal is fundamentally wrong
11:53:58 <Ege> ml: we should not open this discussion now, do it next meeting
11:54:21 <Ege> kaz: we can open a new issue about this
11:55:02 <kaz> s/we can/given we only have 5 more minutes, I'd suggest we/
11:55:04 <Ege> bf: I agree with Ege's points
11:55:23 <kaz> s/about this/about this and deal with the issue next week./
11:55:29 <Ege> ml: I will put this issue 126 in the next agenda
11:55:54 <kaz> rrsagent, make log public
11:55:57 <kaz> rrsagent, draft minutes
11:55:57 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/20-wot-profile-minutes.html kaz
11:56:45 <kaz> i/subtopic: PR 93/topic: PRs/
11:56:47 <kaz> rrsagent, draft minutes
11:56:47 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/20-wot-profile-minutes.html kaz
11:57:00 <Ege> subtopic: PR 121
11:57:26 <benfrancis> q+
11:57:33 <kaz> ack k
11:58:39 <kaz> i|PR 121|-> https://github.com/w3c/wot-profile/issues/126 Issue 126 - Dependency on Cloud Events|
11:59:04 <Ege> bf: My main proposal is that a TD should have a HTTP URL
11:59:18 <kaz> i|My main|-> https://github.com/w3c/wot-profile/pull/121 PR 121 - Add Discovery section to HTTP Baseline Profile - closes #112|
12:00:49 <kaz> rrsagent, draft minutes
12:00:49 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/20-wot-profile-minutes.html kaz
12:01:02 <kaz> q?
12:01:04 <kaz> ack b
12:01:32 <Ege> ml: aob?
12:01:32 <kaz> q?
12:01:52 <kaz> (none)
12:01:54 <kaz> [adjourned]
12:01:58 <kaz> rrsagent, draft minutes
12:01:58 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/20-wot-profile-minutes.html kaz
13:09:22 <Mizushima> Mizushima has left #wot-profile
14:02:27 <Zakim> Zakim has left #wot-profile