14:50:16 RRSAgent has joined #wot-arch 14:50:16 logging to https://www.w3.org/2021/11/04-wot-arch-irc 14:50:24 meeting: WoT Architecture 14:50:29 present+ Kaz_Ashimura 14:55:10 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Nov_4th.2C_2021 15:01:23 mlagally has joined #wot-arch 15:01:46 will be here after a short bio break 15:03:49 s/will be here after a short bio break// 15:04:43 present+ Kaz_Ashimura, Ege_Korkan, Michael_Lagally, Tomoaki_Mizushima 15:04:52 rrsagent, make log public 15:04:55 rrsagent, draft minutes 15:04:55 I have made the request to generate https://www.w3.org/2021/11/04-wot-arch-minutes.html kaz 15:05:05 benfrancis has joined #wot-arch 15:05:42 present+ Ben_Francis 15:07:14 scribenick: kaz 15:07:25 topic: Agenda 15:07:33 ml: 2 topics for today 15:07:41 ... next week agenda is also available 15:07:55 ... we don't a lot of time 15:08:05 present+ Ryuichi_Matsukura 15:08:29 ... (goes through the agenda) 15:09:14 q+ 15:09:25 ben: question about timeline 15:09:52 ml: consensus we won't make any normative changes after mid Nov 15:10:13 bf: ok 15:10:33 ... don't think WoT Profile is stable enough... 15:10:54 ml: in that case, we should clarify the main concerns 15:11:02 ... and bring them to the Editors call and the Chairs 15:11:58 -> https://github.com/w3c/wot/pull/1000 updated publication plan 15:12:32 ek: would like to talk about assertion review issue 15:12:54 ml: anything else? 15:12:55 (none) 15:12:58 topic: Minutes 15:13:26 -> https://www.w3.org/2021/09/23-wot-arch-minutes.html Sep-23 15:13:33 (approved) 15:14:13 https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-10-online-f2f 15:14:20 -> https://www.w3.org/2021/10/27-wot-minutes.html Oct-27 (vF2F day 4) 15:16:47 ml: (goes through the minutes) 15:17:38 ... anything needs to be changed? 15:17:55 ... can approve the Arch/Profile sections? 15:17:59 (no objections) 15:18:02 (approved) 15:18:12 present+ Michael_Koster 15:18:34 topic: Architecture 15:18:38 subtopic: PR 615 15:18:55 mjk has joined #wot-arch 15:19:18 -> https://github.com/w3c/wot-architecture/pull/615 Address Binding Templates related issues #615 15:19:29 ek: for alignment with the Binding Templates doc 15:20:54 ... the text on security should be put under section 8 15:21:39 ... don't want the Arch spec to have the security detail for Binding 15:22:14 ml: where should it be described then? 15:22:35 ek: think should be included in the Binding Templates doc 15:23:06 ... not the Binding Templates section of the Architecture spec 15:23:32 ... note that the Binding Templates document is about not only Protocol Binding but Binding in general 15:24:16 Ege has joined #wot-arch 15:24:30 ml: would be fine to move the description itself 15:24:39 ... but would like to check with McCool 15:24:40 q+ 15:27:26 ack k 15:27:35 kaz: think this PR is too big 15:27:58 ... would be better to split this into 3-4 smaller PRs for easier review 15:28:19 ml: smaller PRs are better 15:28:35 ... but can still review this PR 615 15:29:02 ... we need some more time for review and need to conclude next week, though 15:29:12 s/smaller/agree smaller/ 15:29:52 kaz: ok 15:31:12 ml: once we get McCool's feedback for the security part, I'll be OK 15:31:30 subtopic: PR 631 15:31:49 -> https://github.com/w3c/wot-architecture/pull/631 precedence rule for terminology #631 15:31:58 ml: terminology 15:32:23 -> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/631/6531e45...e615cef.html#terminology diff 15:32:39 q? 15:32:41 q+ 15:32:59 [[ 15:33:00 In case of a conflict of a definition with terminology used in another WoT document, the definition of the WoT Architecture takes precedence. 15:33:00 ]] 15:33:15 ack k 15:33:18 kaz: fine 15:33:39 ... but we need to check the inconsistency among specs 15:33:58 bf: don't think adding this note would be really good 15:34:07 ... should check the inconsistency among specs 15:34:27 ml: we'll definitely check the inconsistency 15:35:05 (with the condition, we'll merge the PR) 15:35:07 (merged) 15:35:28 subtopic: PR 624 15:35:42 -> https://github.com/w3c/wot-architecture/pull/624 preparing implementation report #624 15:36:32 ml: implementation report preparation 15:36:42 q+ 15:40:26 kaz: is this a different tool to extract assertions from McCool's one? 15:41:42 ml: copied the tool for Discovery 15:41:54 kaz: so the same one? 15:42:47 ... probably the same tool 15:43:15 ... but should ask McCool for clarification about where to put the resulted CSV and the format of the CSV file 15:43:30 ... we can merge this PR itself and then check with McCool later, though 15:43:48 ml: would merge this PR itself 15:43:52 (merged) 15:44:41 subtopic: Issue 625 15:44:52 -> https://github.com/w3c/wot-architecture/issues/625 Assertion review #625 15:45:32 ek: some of the assertions are not really correct 15:47:17 ... mis-alignment with TD 15:47:59 ml: a couple of normative portions included here 15:48:19 q+ 15:48:23 q- 15:48:25 q+ 15:49:33 ml: need more time to look into this issue 15:50:31 ... would suggest we handle this offline 15:50:37 ack b 15:50:45 bf: a couple of points 15:51:22 ... Mozilla made a Formal Objection to make the Architecture document a normative spec 15:51:43 ... all the normative portions should be defined by the other specs like TD 15:52:27 ... these normative assertions would cause confusion 15:52:29 q? 15:52:35 ek: agree 15:52:45 ... still mis-alignment with the other specs 15:52:58 ml: ok 15:53:07 ... anyway I need more time for review 15:54:48 kaz: agree consistency among specs is very important 15:55:13 ... that's why I'm asking all the Editors to check the consistency among specs 15:55:21 ... and see which description to be included in which spec 15:55:44 ... some of the assertions here might to to another spec 15:56:03 ... @@@ 15:56:07 ek: agree 15:56:33 ml: would like to ping the related Editors here (McCool, Sebastian, Ryuichi, Ege and Lagally) 15:56:54 ... and have discussion during the Editors call next week as well 15:57:36 s/@@@/also again, I'd suggest we split this issue 625 into several smaller issues about Architecture and TD, Architecture and Discovery, Architecture and Binding Tempaltes, etc./ 15:58:22 ml: also another issue on the timeline for Profile 15:58:29 ... would think about that as well 15:58:56 i/also/topic: Profile 16:00:21 ... (creates Issue 110) 16:00:45 -> https://github.com/w3c/wot-profile/issues/110 Blocker for publication #110 16:01:02 bf: was concerned about the updated timeline 16:01:20 q? 16:01:26 q- 16:01:27 q+ 16:02:39 -> https://github.com/w3c/wot/pull/1000 updated timeline 16:05:06 kaz: we need to clarify what we want and what we can do during this Charter period 16:05:16 ... and then think about how to deal with them 16:05:43 ... and then think about how/when to publish the spec document for this Charter period 16:06:58 rrsagent, make log public 16:07:02 rrsagent, draft minutes 16:07:02 I have made the request to generate https://www.w3.org/2021/11/04-wot-arch-minutes.html kaz 16:07:36 ml: would like to send an email about this problem 16:07:43 topic: AOB 16:08:09 mizushima: wondering about the results of the doodle on the possible next slot 16:08:31 -> https://doodle.com/poll/q58mh9pp4bpccayd doodle poll 16:08:38 kaz: no good slot in the end... 16:09:11 ek: will be more flexible 16:09:28 bf: any chance to make the meeting one hour? 16:10:07 ... or splitting the call into two separate calls, one for Architecture and another for Profile 16:10:15 ml: let me think 16:10:55 kaz: what about the next call? 16:11:00 ... on Nov. 11 right? 16:11:04 ml: yes 16:11:13 kaz: one hour or two hours? 16:11:24 ml: next call on Nov 11 will be two hours 16:11:47 ... may need to shorten the call to one hour on Nov. 18, though. 16:12:13 [adjourned] 16:12:20 rrsagent, draft minutes 16:12:20 I have made the request to generate https://www.w3.org/2021/11/04-wot-arch-minutes.html kaz 18:04:06 Zakim has left #wot-arch