10:00:28 RRSAgent has joined #wot-arch 10:00:28 logging to https://www.w3.org/2022/11/03-wot-arch-irc 10:01:26 meeting: WoT Architecture + Profile 10:01:44 present+ Kaz_Ashimura, Ege_Korkan, Michael_Lagally, Michael_McCool 10:01:52 chair: Lagally 10:03:31 Mizushima has joined #wot-arch 10:04:53 mlagally has joined #wot-arch 10:05:00 sebastian has joined #wot-arch 10:05:55 zakim, who is on the call? 10:05:55 Present: Kaz_Ashimura, Ege_Korkan, Michael_Lagally, Michael_McCool 10:05:59 topic: Minutes 10:06:26 ml: call notes from yesterday (covering arch topics) and last week 10:06:43 ml: minutes from 27 Oct 2022 10:07:23 kaz: already reviewed, so do not have to do it again 10:07:47 ml: ok, let's look at Nov 2 minutes 10:08:00 -> https://www.w3.org/2022/11/02-wot-profile-minutes.html Nov-2 10:08:15 present+ Sebastian_Kaebisch, Tomoaki_Mizushima 10:09:33 ml: no objections? ... 10:09:35 Ege has joined #wot-arch 10:09:38 ... let's publish 10:09:53 topic: Contributions 10:10:16 subtopic: PR 872 and related issue 10:11:05 ryuichi has joined #wot-arch 10:11:05 -> https://github.com/w3c/wot-architecture/pull/872 PR 872 - Update CR and Norm/Inf for section 7 10:12:30 -> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/872/1c7ba10...mmccool:415982c.html#sec-building-blocks diff 10:13:17 q+ 10:14:57 kaz: clarification question 10:15:03 q+ 10:15:21 q+ 10:15:45 ... this PR 872 makes (1) most of the section 7 non-normative and (2) 7.4 WoT Discovery and 7.5 WoT Binding Templates normative 10:15:53 ... is that correct? 10:15:53 ack k 10:15:55 mm: right 10:16:07 kaz: 7.4 may be OK 10:16:18 ... but 7.5 is about WoT Binding Templates 10:16:33 ... does that section really include normative assertions? 10:16:37 mm: yes 10:16:47 ... not one but many assertions included there 10:18:36 q? 10:18:37 q+ 10:18:42 ack s 10:18:53 present+ Ryuichi_Matsukura 10:20:05 q+ 10:20:44 ack e 10:24:38 sk: think we should make the section "7.5 WoT Binding Templates" non-normative 10:24:40 ek: +1 10:24:42 kaz: +1 10:24:51 +1 10:26:10 mm: I'm OK with that direction 10:26:46 ... note that the section "7.4 WoT Discovery" could be also non-normative since we can remove the assertions within that section 10:27:34 q+ 10:27:38 ... the necessary assertions for WoT Discovery are defined by the "WoT Discovery" specification already 10:27:40 ack k 10:27:42 ack m 10:28:01 sk: would agree with McCool 10:28:39 q+ 10:29:17 ... making the whole section "7 WoT Building Blocks" would make the situation easier 10:29:20 q+ 10:29:37 ... and give readers less confusions 10:29:40 ack s 10:31:43 ack k 10:32:10 kaz: I'm OK with making "7.4 WoT Discovery" as well non-normative 10:32:11 q+ 10:32:40 ... and making the whole section "7 WoT Building Blocks" also non-normative 10:33:33 ... another question might be whether we want to say "WoT Runtime MUST support WoT Thing Description.", etc., at the beginning of the section "7 WoT Building Blocks" 10:33:41 q? 10:33:46 ack m 10:33:46 mm: need to see the section 7 carefully 10:35:05 ... also wondering if it's OK if I update section 7.5 WoT Binding Templates 10:35:10 ek: that's fine 10:35:57 mm: I'll work on a new Pullrequest then 10:36:14 s/I'll/I can/ 10:36:58 proposal: McCool creates a single PR that makes all RFC2119 assertions in chapter 7 (7.4 and 7.5) informative text. Arch TF approves the PR via email within 24 hours. WG is requested to approve CR transition by email until Wednesday noon next week. 10:37:22 ek: please remember you need to update the test results for the Implementation Report 10:37:27 mm: will handle that too 10:38:51 proposal: McCool creates a single PR that makes all RFC2119 assertions in chapter 7 (7.4 and 7.5) informative text. Arch TF approves the PR via email within 24 hours, i.e. if there's no objection the PR will be merged. Likewise the WoT WG is requested to approve CR transition by email until Wednesday noon next week. 10:39:03 rrsagent, make log public 10:39:07 rrsagent, draft minutes 10:39:07 I have made the request to generate https://www.w3.org/2022/11/03-wot-arch-minutes.html kaz 10:39:19 +1 10:39:22 resolution: McCool creates a single PR that makes all RFC2119 assertions in chapter 7 (7.4 and 7.5) informative text. Arch TF approves the PR via email within 24 hours, i.e. if there's no objection the PR will be merged. Likewise the WoT WG is requested to approve CR transition by email until Wednesday noon next week. 10:40:02 topic: profile 10:40:04 i/call notes fro yesterday/scribenick: McCool/ 10:40:06 rrsagent, draft minutes 10:40:06 I have made the request to generate https://www.w3.org/2022/11/03-wot-arch-minutes.html kaz 10:40:07 https://github.com/w3c/wot-profile/pulls 10:40:22 scribenick: McCool 10:40:29 ml: would like to switch over now and look at pending pull requests, several of which have already been approved 10:40:46 subtopic: PR 293 10:40:53 i/Update CR and/scribenick: kaz/ 10:40:53 rrsagent, draft minutes 10:40:53 I have made the request to generate https://www.w3.org/2022/11/03-wot-arch-minutes.html kaz 10:41:08 ml: previously security was only allowed at top level, this removes that, and allows them on forms 10:41:26 ... this allows more sensitive affordances to have additional security 10:41:36 ... any objections? 10:41:39 ... none, merged 10:41:53 i|previously|-> https://github.com/w3c/wot-profile/pull/293 PR 293 - Allow security metadata on Forms - closes #292/ 10:41:54 rrsagent, draft minutes 10:41:54 I have made the request to generate https://www.w3.org/2022/11/03-wot-arch-minutes.html kaz 10:42:00 subtopic: PR 294 10:42:11 ml: this makes security bootstrapping mandatory 10:42:42 i|this makes|-> https://github.com/w3c/wot-profile/pull/294 PR 294 - Make security bootstrapping mandatory - closes #250/ 10:43:17 -> https://pr-preview.s3.amazonaws.com/w3c/wot-profile/294/5912319...benfrancis:6afbeb0.html#common-constraints-security diff - 6.3 Security 10:43:54 mm: I am ok with these, but note that this only applies to discovery 10:44:11 ... if we want security bootstrapping everywhere, we have to allow the "auto" security scheme 10:44:37 ... I suggest we create an issue for the auto security scheme, otherwise I am ok with this PR 10:44:52 q+ 10:45:05 ml: creates issue #313 for auto scheme, assigns mmccool 10:46:14 ege: was there not another Pr revising the list of security schemes? 10:48:00 ml: looks like a merge conflict, PR still has the old list of security schemes 10:48:07 ... let's try to fix 10:48:43 ... no, it looks like the conflict was with the other PR that removed restriction to top level 10:48:49 ... (fixes) 10:49:11 ... (checks diff) 10:50:12 ... old security schemes still in diff, but let's merge and see if it still needs fixing after 10:50:28 mm: I will remove them when I do my PR if necessary. 10:50:58 q+ 10:51:30 subtopic: PR 297 10:51:57 q- 10:52:00 ml: this is moving content out into a requirements document 10:52:11 ... but it also makes a lot of other changes 10:52:15 rrsagent, draft minutes 10:52:15 I have made the request to generate https://www.w3.org/2022/11/03-wot-arch-minutes.html kaz 10:52:27 seb: however, I do think over all it is a big improvement 10:52:58 ... it makes the exposition much more straightforward 10:53:26 i|this is moving|-> https://github.com/w3c/wot-profile/pull/297 PR 297 - Revised Abstract and Introduction - fixes #115 and fixes #190/ 10:53:51 s|190/|190| 10:53:53 rrsagent, draft minutes 10:53:53 I have made the request to generate https://www.w3.org/2022/11/03-wot-arch-minutes.html kaz 10:54:32 ... I think that very detailed explanations, motivations, etc. can go into an explainer 10:54:45 ml: (makes notes on PR) 10:55:03 q? 10:55:05 ack s 10:55:24 ml: we don't have an explainer yet... 10:55:32 mm: but will need one soon 10:55:54 q+ 10:55:57 ml: (see notes on PR) 10:56:36 seb: a simple example at the very beginning would also be helpful, and it more interesting than 5-6 pages of justification; I can support and provide an example 10:57:38 ml: suggest that we split into multiple PRs, one for requirements, one for explainer, one for improved intro 10:58:14 ... will ask ben to restructure 10:58:34 ... please do say that sebastian was quite in favor of the change, we just want to organize it better 10:59:06 kaz: agree that smaller topic-by-topic PR is better 10:59:28 ... one more point - might want to have a requirements document and consolidated explainer 10:59:52 ... for all of WoT, not just profiles 11:00:02 mm: please bring that up when we do the next charter 11:00:48 subtopic: PR 311 11:01:00 ml: adds summary of assertions 11:01:14 mm: ok with merging, but yes, I do plan to update the IR shortly 11:01:23 i|adds|-> https://github.com/w3c/wot-profile/pull/311 PR 311 - Oct Testfest - summary table| 11:01:24 ml: merges this Pr 11:01:55 [adjourned] 11:01:59 rrsagent, draft minutes 11:01:59 I have made the request to generate https://www.w3.org/2022/11/03-wot-arch-minutes.html kaz 13:00:51 Zakim has left #wot-arch 14:02:14 zkis has joined #wot-arch 15:11:53 zkis_ has joined #wot-arch 15:57:54 zkis has joined #wot-arch 17:28:54 zkis has joined #wot-arch 18:16:52 zkis has joined #wot-arch 19:23:16 zkis has joined #wot-arch 21:11:35 zkis has joined #wot-arch