09:59:29 RRSAgent has joined #wot-arch 09:59:29 logging to https://www.w3.org/2022/04/07-wot-arch-irc 10:01:26 meeting: WoT Architecture 10:01:33 mlagally has joined #wot-arch 10:02:14 present+ Kaz_Ashimura, Michael_Lagally 10:03:17 np 10:04:16 ktoumura has joined #wot-arch 10:07:44 Mizushima has joined #wot-arch 10:09:54 zakim, who is on the call? 10:09:54 Present: Kaz_Ashimura, Michael_Lagally 10:10:16 present+ Kunihiko_Toumura 10:10:18 present+ Kunihiko_Toumura, Michael_McCool 10:10:35 present+ Tomoaki_Mizushima 10:10:45 McCool has joined #wot-arch 10:11:09 topic: minutes 10:11:11 scribenick: McCool 10:11:16 ml: no objs, approved 10:11:28 i|no o|-> https://www.w3.org/2022/03/31-wot-arch-minutes.html Mar-31| 10:11:35 present+ Ryuichi_Matsukura 10:11:45 topic: schedule 10:11:57 ml: let's just review where we are 10:15:22 ... norm freeze may 6th 10:16:24 ... feb 4 was normative sections 10:16:42 mm: one thing to mention is if S&P become normative, technically adds new assertions 10:16:57 ... but this would be consistent with other specs 10:17:33 ... I would expect the security TF to get through that in the next two weeks 10:18:49 ktoumura has joined #wot-arch 10:21:28 -> https://w3c.github.io/wot-architecture/#sec-security-considerations 10. Security Considerations 10:21:38 ml: what does it mean if they violate one of the S&P assertions? 10:23:38 mm: see also 726, which is review 10:24:49 -> https://github.com/w3c/wot-architecture/issues/726 Issue 726 - Review and Update Security and Privacy Considerations 10:26:10 ml: let's do a PR that just makes it normative, and then ask for review 10:27:27 ... also delete the ednote about refactoring, already done 10:29:46 mm: also we need to add discovery, of course 10:30:14 topic: spec structure 10:31:39 ml: for the May 6 deadline, need to see if there are any other places where there would be assertions 10:32:01 q+ 10:32:06 ... is label called "normative sections", but these are reorg 10:33:05 ack k 10:33:48 ... see also issue 646 10:34:21 -> https://github.com/w3c/wot-architecture/issues/646 Issue 646 - [Index] Section structure, assertions, and issues 10:34:44 mm: also want to check S&P are in the right place 10:35:23 ml: is issue 646 still open? 10:35:35 ... can we close this, or is it still open? 10:35:52 kt: if structure is settled, we can close this issue 10:36:04 ml: ok, I think we are settled, let's close 10:36:40 ml: spec alignment 10:36:47 ... binding template, ege has looked into 10:37:14 ... mccool still has some open issues on discovery 10:37:52 i|spec alignment|-> https://github.com/w3c/wot-architecture/issues?q=is%3Aissue+is%3Aopen+label%3A%22spec+alignment%22 spec alignment issues 10:38:01 rrsagent, make log public 10:38:06 rrsagent, draft minutes 10:38:06 I have made the request to generate https://www.w3.org/2022/04/07-wot-arch-minutes.html kaz 10:38:40 https://github.com/w3c/wot-architecture/pull/731 10:38:44 ml: see PR 731, addressing issue 616 10:39:06 ... also did some cleanup to get rid of an informative note 10:39:26 i/alignment issues/topic: Spec alignment/ 10:39:37 i/731/subtopic: PR 731/ 10:39:44 s/https/-> https/ 10:40:08 ... just an outdated reference to use case process 10:40:24 ml: propose merging and closing related issue 10:40:39 mm: ok 10:40:41 ml: done 10:40:50 s/731/731 PR 731 - fixing issue 616/ 10:41:08 ml: next is issue 674, aligning terminology 10:41:32 ... is still a problem with a few things, like "virtual thing", which is used inconsistently 10:41:48 i/issue 674/subtopic: Issue 674/ 10:42:30 mm: real issue is normative docs, things like use case doc we can clean up later 10:42:48 ... but if discovery and arch are inconsistent, that is a problem for our schedule 10:43:19 i|issue 674|-> https://github.com/w3c/wot-architecture/issues/674 Issue 674 - Review use cases document / align terminology / identify gaps| 10:44:08 ml: propose closeing 674, then work on other issues that are aiming to make each normative doc consistent with architecture 10:44:18 s/closeing/closing. 10:45:41 mm: regarding discovery, one issue I am aware of is use of "producer", etc. 10:45:59 topic: testing 10:46:16 https://github.com/w3c/wot-architecture/issues/729 10:46:31 ml: created small issues, e.g. update readme 10:47:25 -> https://cdn.statically.io/gh/w3c/wot-architecture/aeae0b90e29a01aae6500e63785c3b6c0f86eab5/testing/inputs/templates/report.html rendered version of the draft implementation report for WoT Architecture 1.1 10:50:53 mm: some other minor things in the report to fix, will do another bugfix pass soon; impl sections, automated testing, etc 10:51:10 ... also ignore the staticly links, they are out of date now 10:51:45 ... need to delete some extra files that are not needed anymore, eg. test specs 10:51:51 topic: contributions 10:52:06 ml: pr 730, fixes a respec error; merging 10:52:51 i/pr 730/subtopic: PR 730/ 10:53:09 i|pr 730|-> https://github.com/w3c/wot-architecture/pull/730 PR 730 - fix respec error on producer| 10:55:30 ml: also producer is not referenced, but can be linked from S&P 10:55:42 mm: I can fix that then when I make my PR for that section 10:56:08 ml: PR 728, some review comments 10:56:32 i/PR 728/subtopic: 728/ 10:56:42 ... is a comment about "industrial controllers", but that is beyond telemetry 10:56:53 i|PR 728|-> https://github.com/w3c/wot-architecture/pull/728 PR 728 - Draft telemetry section| 10:57:14 ... ege also commented that term "bearer" should be changed to "communication channels" 10:59:25 mm: small typo noted (wont't), but ok with merging 10:59:34 q+ 10:59:51 ack k 10:59:58 ml: ok, will merge 11:00:03 ml: aob? 11:01:25 none 11:01:26 [adjourned] 11:01:30 rrsagent, draft minutes 11:01:30 I have made the request to generate https://www.w3.org/2022/04/07-wot-arch-minutes.html kaz 11:02:14 ktoumura has left #wot-arch 13:31:11 Zakim has left #wot-arch