10:05:29 RRSAgent has joined #wot-arch 10:05:29 logging to https://www.w3.org/2022/09/01-wot-arch-irc 10:05:31 meeting: WoT Architecture 10:05:53 present+ Kaz_Ashimura, Michael_Lagally, Kunihiko_Toumura, Michael_McCool 10:07:37 ktoumura has joined #wot-arch 10:07:43 mlagally_ has joined #wot-arch 10:09:27 McCool has joined #wot-arch 10:09:46 topic: minutes 10:10:01 ml: review minutes of 4 aug 10:10:15 i|review|-> https://www.w3.org/2022/08/04-wot-arch-minutes.html Aug-4| 10:10:27 regrets+ Sebastian, Ege, Mizushima 10:12:33 mm: wonder if using tag-needs-resolution label is a good idea, hard to remove, but ok 10:14:15 ml: can we publish the minutes? Any objections? 10:17:54 topic: Publication 10:18:01 subtopic: PR 823 10:18:15 -> https://github.com/w3c/wot-architecture/pull/823 PR 823 - WIP: Add change log from FPWD 1.1 to 2-WD 10:18:39 ml: some minor issues, but I think we should just merge it 10:18:56 q+ 10:19:19 mm: ok 10:19:26 ack k 10:19:32 kaz: now that we have the change log, shall I publish the updated draft? 10:19:38 ml: yes, let's 10:20:08 topic: tag-needs-resolution issues 10:20:27 subtopic: issue 818 10:20:33 ml: should arch be a note 10:21:08 ml: mozilla previously asked this, now raising 10:21:40 i|should arch|-> https://github.com/w3c/wot-architecture/issues/818 Issue 818 - Consider whether this makes more sense as a Note [TAG feedback] | 10:21:46 s/a note/a note?/ 10:22:25 mm: bottom line is we need a place for global assertions, like security 10:23:15 q+ 10:26:54 ack k 10:26:58 ack k 10:27:18 mm: but charter does not set security as a normative document 10:32:32 mm: related to other issues that are "extra"; if we remove unessential assertions, then restructuring later will be easier 10:32:53 kaz: agree 10:34:30 mm: before we can change from normative to informative, need to identify essential assertions first 10:35:10 q? 10:35:16 ml: issue 816 10:35:54 mm: regarding redundant assertions, I think we fixed the one they called out already 10:36:03 ... but there may be others 10:40:18 mm: suggest updating comment to say that we are open to discussing this further 10:40:34 kaz: also suggest we reach out to TAG and request a meeting 10:45:56 q? 10:45:59 q+ 10:48:10 ack k 10:48:25 subtopic: issue 814 10:48:39 ml: compatibility story - added some comments 10:48:53 mm: need to explain what protocols work, gateways, etc. 10:49:15 s/ml: issue 816/subtopic: issue 816/ 10:49:35 i|regarding redundant|-> https://github.com/w3c/wot-architecture/issues/816 Issue 816 - Review for redundant normative statements [TAG feedback]| 10:50:12 i|compatibility|-> https://github.com/w3c/wot-architecture/issues/814 Issue 814 - Compatibility in the ecosystem [TAG feedback]| 10:51:43 subtopic: issue 811 10:52:40 mm: add comment that we plan to update the Guidelines document this fall, but because it is informative essential assertions need to be in a normative document. We can update the reference so it is informative 10:55:44 subtopic: issue 809 10:55:58 ml: informative/normative refs again, should be relatively easy to fix 11:01:53 i|add comment|-> https://github.com/w3c/wot-architecture/issues/811 Issue 811 - Improve security section to address TAG feedback| 11:02:33 i|informative/n|-> https://github.com/w3c/wot-architecture/issues/809 Issue 809 - Fix normative references / convert to informative, where applicable| 11:02:46 topic: implementation report 11:03:06 mm: updated, but more work to do 11:03:17 topic: WIP security assertion issue 11:03:22 ml: issue 823 11:03:43 mm: issue mentions what we have to deal with, but I still need to implement a PR 11:04:32 s/823/824/ 11:05:10 s|issue mentions|-> https://github.com/w3c/wot-architecture/issues/824 Issue 824 - WIP: Adjust policy-like security and privacy assertions| 11:05:12 [adjourned] 11:05:17 rrsagent, make log public 11:05:22 rrsagent, draft minutes 11:05:22 I have made the request to generate https://www.w3.org/2022/09/01-wot-arch-minutes.html kaz 13:15:35 Zakim has left #wot-arch 15:04:24 kaz has joined #wot-arch