13:05:15 RRSAgent has joined #wot 13:05:19 logging to https://www.w3.org/2023/03/08-wot-irc 13:05:32 meeting: WoT-IG/WG 13:05:40 chair: McCool 13:05:42 luca_barbato has joined #wot 13:05:44 regrets: Sebastian 13:05:58 matsuda has joined #wot 13:06:03 mlagally_ has joined #wot 13:06:31 present+ Kaz_Ashimura, Michael_McCool, Deniel_Peintner, Kunihiko_Toumura, Luca_Barbto, Michael_Kostr, Michael_Lagally, Tetsushi_Matsuda 13:06:59 present+ Ryuichi_Matsukura 13:07:16 scribenick: dape 13:07:41 TOPIC: Quick updates 13:07:48 MMC: Next Use Cases call on March 14 13:07:52 agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#8_March_2023 13:07:59 TOPIC: Planning 13:08:01 i/Quick u/topic: Minutes review/ 13:08:06 SUBTOPIC: Testing 13:08:07 i/Quick u/(skipped today)/ 13:08:18 --> doodle poll -> https://doodle.com/meeting/participate/id/dGRmPm0b 13:08:43 s/March 14/March 14. will continue the discussion on the policy for use case collection as well./ 13:08:46 MMC: need input o doodle poll 13:09:12 ... Testfest doodle during the week of March 20 -> https://doodle.com/meeting/participate/id/b6WOR77d 13:09:20 SUBTOPIC: Binding Meetup 13:09:21 s/doodle poll/doodle poll for Dev Meeting/ 13:09:29 rrsagent, make log public 13:09:33 rrsagent, draft minutes 13:09:34 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:09:41 TM: JP Meetup by WoT-JP CG 13:09:42 ... held on Feb 27 with ECHONET 13:09:49 ... two more meetings planned with IPA DADC and NHK 13:10:01 ... afterwards we will report back 13:10:25 rrsagent, draft minutes 13:10:26 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:11:03 TOPIC: Publications progress check 13:11:03 MMC: schedule needs revision 13:11:03 ... need to do PR 13:11:03 Mizushima has joined #wot 13:11:03 Ege has joined #wot 13:11:03 ... we missed proposed deadlines 13:11:07 mjk has joined #wot 13:11:15 s|--> doodle poll -> https://doodle.com/meeting/participate/id/dGRmPm0b|-> https://doodle.com/meeting/participate/id/dGRmPm0b doodle poll for Dev Meeting| 13:11:27 https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda_Session_5.2C_Day_1_-_Mar_8 13:11:39 s/need input o doodle poll for Dev Meeting/need input to the doodle poll for Testfest as well./ 13:11:42 rrsagent, draft minutes 13:11:44 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:11:55 present+ Ege_Korkan 13:12:06 i/Session_5/topic: WG Charter/ 13:12:10 TOPIC: Charter discussions 13:12:25 MMC: We have 10 PRs 13:12:27 present+ Ege_Korkan 13:12:52 s/TOPIC: Charter discussions// 13:12:54 SUBTOPIC: #75 13:12:56 https://github.com/w3c/wot/pull/75 : W3C Presentation API Section 13:13:10 present+ Micahel_Koster 13:13:16 MMC: Adds proposed chairs 13:13:16 present- Michael_Kostr 13:13:27 q+ 13:13:45 ack k 13:13:45 Kaz: we can wait for more potential candidates 13:13:55 ... what is the deadline 13:14:04 s/deadline/deadline?/ 13:14:21 MMC: More candidates can be added later 13:14:35 present- Luca_Barbto 13:14:40 present+ Luca_Barbato 13:14:42 SUBTOPIC: #76 13:14:44 https://github.com/w3c/wot/pull/76 : Added a few bullets about WebRTC in landscape doc 13:15:03 MMC: removes process note 13:15:08 ... simply formatting 13:15:17 ... no objections -> merging 13:15:38 SUBTOPIC: #79 13:15:40 https://github.com/w3c/wot/pull/79 : Tech landscape update by Takuki Kamiya 13:15:46 s|https://github.com/w3c/wot/pull/75 : W3C Presentation API Section|-> https://github.com/w3c/wot-charter-drafts/pull/75 PR 75 - Propose Chairs| 13:15:57 MMC: about versioning 13:16:17 ... changed names of deliverables to be generic 13:16:28 s|https://github.com/w3c/wot/pull/79 : Tech landscape update by Takuki Kamiya|-> https://github.com/w3c/wot-charter-drafts/pull/79 PR 79 - Use Generic Spec Names| 13:16:41 rrsagent, draft minutes 13:16:42 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:17:30 MMC: no objections -> merging 13:17:56 s|https://github.com/w3c/wot/pull/76 : Added a few bullets about WebRTC in landscape doc|-> https://github.com/w3c/wot-charter-drafts/pull/76 PR 76 - Comment out note from template| 13:18:20 SUBTOPIC: WoT Charters PR #81 13:18:22 https://github.com/w3c/wot/pull/81 : Introducing abstract TDs for late bindings. 13:18:35 MMC: removes on boarding from charter 13:18:43 ... we might still do it 13:18:49 https://github.com/w3c/wot/pull/81 : Introducing abstract TDs for late bindings. 13:19:01 ... just removed commitment 13:19:15 s|https://github.com/w3c/wot/pull/81 : Introducing abstract TDs for late bindings.|| 13:19:44 s|https://github.com/w3c/wot/pull/81 : Introducing abstract TDs for late bindings.|-> https://github.com/w3c/wot-charter-drafts/pull/81 PR 81 - Remove onboarding from scope summary| 13:19:53 q+ 13:19:57 MMC: Got approvals and no objections -> merging 13:20:16 SUBTOPIC: PR #83 13:20:17 rrsagent, draft minutes 13:20:18 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:20:24 https://github.com/w3c/wot/pull/83 : WoT architecture document 13:20:24 DP: typo fix 13:20:38 MMC: straight forward -> merging 13:20:52 SUBTOPIC: PR 82 13:20:56 s|https://github.com/w3c/wot/pull/83 : WoT architecture document|-> https://github.com/w3c/wot-charter-drafts/pull/83 PR 83 - typo fix| 13:21:01 rrsagent, draft minutes 13:21:02 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:21:14 https://github.com/w3c/wot-charter-drafts/issues/16 13:21:19 MMC: related issue 16 13:21:36 ... whether Architecture should be normative 13:21:57 q+ 13:22:00 ack k 13:22:17 q+ 13:22:21 i|issues/16|-> https://github.com/w3c/wot-charter-drafts/pull/82 PR 82 - adding architecture deliverable| 13:22:33 MMC: Personal opinion. Normative security in Arch.. need to go somewhere 13:22:46 s/should be normative/should be normative or not/ 13:22:50 rrsagent, draft minutes 13:22:52 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:23:03 ... made some fixes like typos and renaming 13:23:28 q? 13:23:34 s|https://github.com/w3c/wot-charter-drafts/issues/16|-> https://github.com/w3c/wot-charter-drafts/issues/16 related issue 16 - Architecture Restructuring| 13:23:37 ack ml 13:23:39 rrsagent, draft minutes 13:23:41 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:23:55 ML: 13:24:30 ... current charter is following same tasks 13:24:47 ... it is continuing the work 13:25:08 i|looking at|-> https://pr-preview.s3.amazonaws.com/w3c/wot-charter-drafts/pull/82.html Preview| 13:25:09 ... we just got TAG review saying it should be non-normative 13:25:40 EK: TAG review was from this charter 13:25:52 present+ Tomoaki_Mizushima 13:25:52 ... person raised good reasons 13:26:05 q+ 13:26:20 ... Mozilla objection was long time ago 13:26:34 ... Assertions in Arch cause issue 13:26:42 ... it is about implementation 13:26:54 q+ 13:26:58 ack e 13:27:06 ... normative parts could be moved to specific documents 13:27:13 q? 13:27:16 q+ 13:27:21 ... no sense in having 20 assertions for Security in Arch document 13:27:54 Kaz: We should think about normative parts of Arch document 13:28:06 ... a dedicated discussion might be useful 13:28:34 MMC: We seem to have no consensus 13:29:09 Kaz: That's why I would like to define what part should be normative 13:29:29 MMC: I see, talking about sections 13:29:31 q? 13:29:31 ack k 13:30:22 ML: We have normative sections about Consumer etc 13:30:28 ... this is the status quo 13:30:41 ... we might want to restructure it 13:30:50 ... question is who is doing the work 13:31:20 ... proposing is simple 13:31:20 s/We should think about normative parts of Arch document/Before diving into the possible conclusion, i.e., normative spec or not, we should think about which parts/sections from the WoT Architecture spec should be normative first./ 13:31:34 rrsagent, make log public 13:31:38 rrsagent, draft minutes 13:31:39 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:31:45 MMC: I think internal restructuring is needed 13:32:05 ... I would like to focus on Arch ... if someone else tales over discovery etc 13:32:32 s/tales/takes 13:33:05 ... chapter "Application domains" is non normative etc 13:33:17 ... chapter 6 Architecture is normative 13:33:20 s/a dedicated discussion might be useful/If we can get a consensus during this call, that's great. However, if not, having a dedicated call would make sense./ 13:33:23 rrsagent, draft minutes 13:33:25 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:33:31 ... what are relevant assertions 13:33:31 q? 13:33:31 ack ml 13:33:32 ack mc 13:33:33 ... assertions need to be testable 13:33:43 q+ 13:33:55 ... there are not that many assertions 13:34:07 ... Q: Can those be handled somewhere else 13:34:14 a/Mozilla objection/Mozilla objection for the Charter review/ 13:34:15 rrsagent, draft minutes 13:34:16 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:34:22 ... chapter 7 building blocks is non normative 13:34:34 ... chapter 8 and 9 is non normative 13:34:45 ... Chapter 10 Security is normative 13:35:47 ... Section 6 and 10 are the only normative sections 13:36:08 ML: Architecture discussion ... for tomorrow 13:36:10 s|That's why I would like to define what part should be normative|That's why I mentioned a possible additional call. In any case, we need to clarify which parts/sections from the WoT Architecture spec should be normative first./ 13:36:21 s|first./|first.| 13:36:23 rrsagent, draft minutes 13:36:24 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:36:40 s/Consumer etc/Consumer, etc./ 13:36:43 MMC: it boils down to. Is Arch the best place for normative sections 13:37:17 ... for 10 Security, it has to go in another document.. I think 13:37:19 s/Mozilla objection/Mozilla objection for the Charter review/ 13:37:27 q? 13:37:33 s|a/Mozilla objection/Mozilla objection for the Charter review/|| 13:37:35 rrsagent, draft minutes 13:37:36 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 13:37:52 EK: Commit to move assertions in another document 13:38:11 ... Question: are people reading Arch spec? 13:38:32 ... I think management reads Arch document 13:38:51 q+ 13:38:57 q+ 13:39:06 ... implementors do not read Arch spec 13:39:20 ack e 13:39:21 ... it is a burden to test Arch spec 13:39:46 Kaz: Agree with McCool looking into dedicated sections 13:39:47 q+ 13:40:01 qq+ 13:40:14 ... it is a different question whether developers read this document 13:40:22 ack e 13:40:22 Ege, you wanted to react to Ege 13:40:29 ... I think people do read Arch document 13:40:33 ack k 13:40:46 EK: I was referring to the assertions 13:40:55 MMC: Purpose of assertion? 13:40:59 ... thing you can test 13:41:00 ack e 13:41:08 q+ 13:41:11 ... or requirements 13:41:12 ack mc 13:42:04 for the minutes, I am not saying that people do not read the architecture specification. Just that during the implementation stage, people do not refer to the assertions in there 13:42:22 MMC: I don't think we can agree soon 13:42:44 ... suggest to look at the assertion and move them if best 13:43:03 q? 13:43:07 ... by keeping Arch document being normative 13:43:11 that is fine kaz, we can discuss other time 13:43:24 ML: I like that 13:43:51 q+ 13:44:10 ML: I also agree with Ege... some sections are for project managers no developers 13:44:24 ack ml 13:44:37 q+ 13:45:06 ML: Agree with the approach to go with normative Arch and discuss it the next weeks while Charter review 13:45:52 Kaz: test reports needed for W3C process based on assertions 13:46:17 ... checking the content and sections is very important 13:46:35 MMC: We are not saying Arch is not important 13:46:43 ... the question is about assertions 13:46:51 ... Ege thinks it causes testing burden 13:46:57 q+ 13:47:02 ack k 13:47:02 ack m 13:47:02 ... it is a practical question 13:47:15 ack m 13:47:19 q+ 13:47:45 Kaz: testing does not only meaning automatic test 13:47:52 ... but also manual tests 13:48:00 ... we need humans in the loop 13:48:07 MMC: True 13:48:28 q? 13:48:34 Kaz: question is what is required and what is optional 13:48:57 EK: The problems with the assertion is real 13:49:01 q? 13:49:06 q+ 13:49:11 ... some assertions are very generiv 13:49:41 EK: argument to keep Arch normative because it was normative does not make sense 13:49:55 ... we got strong opinion from TAG 13:50:17 ... I do not agree with Arch being normative 13:50:29 q? 13:50:32 s/generiv/generic/ 13:50:34 ack Ege 13:50:35 ack e 13:50:55 ML: Concern by Ege or by Siemens? 13:51:06 EK: Also from Sebastian... 13:51:11 ... from Ben Francis 13:51:21 ML: I would like to see a "Siemens" opinion 13:51:29 s/The problems with/I agree with Kaz on it's not only about automatic testing, but the problems with/ 13:51:37 EK: Will do 13:51:38 ack ml 13:52:01 ML: What is the counter proposal? 13:52:14 MMC: List Arch under other deliverable .. 13:52:24 ML: Please provide a PR 13:53:43 13:54:00 MMC: move Arch to informative deliverables 13:54:15 ... plan to relocate other assertions 13:54:24 i|move|-> https://github.com/w3c/wot-charter-drafts/pull/82 PR 82 - adding architecture deliverable| 13:54:30 q? 13:54:36 ML: I don't see a reason for doing that 13:54:43 ... we don't have consensus 13:55:03 ... need feedback from other members 13:55:26 MMC: doing it next week would put as back 2 weeks behind schedule for AC review 13:55:32 q? 13:55:42 ... consensus is more important 13:56:24 Kaz: As team contact: I suggest to look into content of Arch document 13:56:46 ... personally I think we could merge Arch and Profile 13:56:55 ... kind of bigger discussion 13:57:05 ... should happen before making conclusion 13:57:23 MMC: I strongly object merging Arch and Profile 13:57:51 q+ 13:57:52 ... but we do need introductory document 13:57:56 ack kaz 13:58:27 MMC: let's spend time tomorrow discussing feasibility 13:58:33 s/kind of bigger discussion/That's just my personal opinion about a possibility./ 13:58:39 Please see https://github.com/w3c/wot-charter-drafts/pull/85 for an informative deliverable 13:58:42 ML: Small note 13:58:53 ... should we have proposal a) and b) 13:59:16 ... a) merging this PR and b) being Arch non-normative 13:59:30 ... but let's discuss this tomorrow 13:59:43 s/should happen before making conclusion/However, bigger discussion about how to deal with the content of the Architecture spec should happen before making the conclusion about whether Architecture spec should be normative or not./ 14:00:00 MMC: If there are other ideas please bring them up 14:00:10 q? 14:00:11 EK: I created alternative PR 14:00:14 ack ml 14:00:15 ack m 14:00:46 MMC: No testing call today 14:00:55 s/merging Arch and Profile/merging Arch and Profile, because those two documents define completely different viewpoints./ 14:01:00 [adjourned] 14:01:25 rrsagent, draft minutes 14:01:27 I have made the request to generate https://www.w3.org/2023/03/08-wot-minutes.html kaz 15:03:14 Ege has joined #wot 16:20:20 Zakim has left #wot