12:08:08 RRSAgent has joined #wot-arch 12:08:08 logging to https://www.w3.org/2022/05/24-wot-arch-irc 12:08:36 meeting: WoT Architecture 12:08:51 present+ Kaz_Ashimura, Michael_Lagally, Tomoaki_Mizushima 12:11:12 Ege has joined #wot-arch 12:11:43 McCool_ has joined #wot-arch 12:11:45 mlagally has joined #wot-arch 12:12:35 I will join in the second 30 minutes 12:12:45 ktoumura has joined #wot-arch 12:13:50 s/I will join in the second 30 minutes// 12:14:07 present+ Michael_McCool, Kunihiko_Toumura 12:15:03 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_May_24th.2C_2022 12:15:13 topic: agenda 12:15:22 ml: (goes through the agenda) 12:15:26 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_May_24th.2C_2022 agenda for today 12:15:44 topic: minutes 12:15:52 https://www.w3.org/2022/05/19-wot-arch-minutes.html 12:15:59 -> https://www.w3.org/2022/05/19-wot-arch-minutes.html May-19 12:16:01 approved 12:16:27 topic: contributions 12:16:50 subtopic: PR 771 12:17:00 -> https://github.com/w3c/wot-architecture/pull/771 PR 771 - Add introduction text for section 6 and 7 12:17:27 mm: missing "and" between two points? 12:17:44 ml: using "in" to identify the sections 12:17:45 mm: ok 12:18:08 ml: (goes through the "Files changed") 12:18:20 mm: we've been using "usage pattern"? 12:18:27 s/usage/use case/ 12:18:42 ml: ok 12:18:54 mm: what about the images? 12:19:00 ml: changed the images and the titles 12:19:01 mm: ok 12:19:06 merged 12:19:26 mm: related issues should be also closed 12:20:13 -> https://github.com/w3c/wot-architecture/issues/628 Issue 628 - Introduction does not mention section 6 (also closed) 12:20:23 subtopic: PR 769 12:20:47 -> https://github.com/w3c/wot-architecture/pull/769 PR 769 - Internationalization Questionnaire Answers 12:21:02 mm: we should proceed with the i18n review 12:21:06 ml: ok 12:21:12 ... let's merge this PR itself 12:21:14 merged 12:21:37 mm: need another issue for the i18n review 12:22:19 ml: (shows a related issue 620) 12:22:33 -> https://github.com/w3c/wot-architecture/issues/620 Issue 620 - internationalisation requirements| 12:22:38 mm: it's a requirement 12:23:11 ... could reuse it as one of the i18n requirements 12:24:12 ... a subsection called "Requirements" to be added to section "8. Abstract WoT System Architecture" 12:25:08 ... or "7. System Integration" 12:25:20 ... which describes user interface 12:25:36 ml: (adds comments about that to Issue 620) 12:26:09 ... 12:26:09 ...Arch call on May 24th. 12:26:09 Add to the end of section "System integration" 12:26:21 s/Add to/... Add to/ 12:26:27 s/...Arch/... Arch 12:26:45 -> https://github.com/w3c/wot-architecture/issues/620#issuecomment-1135854172 Lagally's comments 12:27:06 subtopic: PR 768 12:27:21 -> https://github.com/w3c/wot-architecture/pull/768 PR 768 - Remove arch-id-correlation assertion 12:27:33 ml: (goes through the "Files changed") 12:27:39 rrsagent, make log public 12:27:43 rrsagent, draft minutes 12:27:43 I have made the request to generate https://www.w3.org/2022/05/24-wot-arch-minutes.html kaz 12:28:02 merged 12:28:37 ml: (checks related Issues) 12:28:53 -> https://github.com/w3c/wot-architecture/issues/625 Issue 625 - Assertion review 12:29:25 -> https://github.com/w3c/wot-architecture/issues/646 Issue 646 - [Index] Section structure, assertions, and issues 12:29:54 subtopic: PR 767 12:30:33 -> https://github.com/w3c/wot-architecture/pull/767 PR 767 - Remove operation type related assertions 12:30:41 merged 12:31:31 mm: missin gperiod thre 12:31:40 ml: (fixed it quickly) 12:31:47 s/missin /missing / 12:32:00 subtopic: PR 737 12:32:10 -> https://github.com/w3c/wot-architecture/pull/737 PR 737 - Align binding related information 12:32:28 mm: need to fix conflicts 12:32:44 ml: Ege has created an updated PR 767 12:32:51 mm: can lose PR 737 then 12:32:52 closed 12:33:31 -> https://github.com/w3c/wot-architecture/pull/767 related PR 767 - Remove operation type related assertions 12:34:08 topic: Issues 12:34:45 subtopic: Issue 606 12:34:57 -> https://github.com/w3c/wot-architecture/issues/606 Issue 606 - Move Table for ops to TD spec 12:35:06 present+ Ege_Korkan 12:35:34 mm: it's an optional thing and nice-to-have 12:35:44 rrsagent, make log public 12:38:03 ml: (goes through the section "8.6.2 Forms") 12:38:18 -> https://w3c.github.io/wot-architecture/#sec-hypermedia-forms 8.6.2 Forms 12:38:33 closed 12:39:07 subtopic: Issue 670 12:39:23 -> https://github.com/w3c/wot-architecture/issues/670 Issue 670 - Cross link Section 5 and Section 6 with corresponding use cases 12:39:48 closed 12:39:57 subtopic: Issue 642 12:40:25 -> https://github.com/w3c/wot-architecture/issues/642 Issue 642 - Identify normative RFC2119 assertions that affect the TD specification 12:40:34 ml: can we close this? 12:41:18 (no objections) 12:41:20 closed 12:41:59 subtopic: Issue 635 12:42:11 -> https://github.com/w3c/wot-architecture/issues/635 Issue 635 - arch-id-correlation : An identifier in the WoT Thing Description MUST allow for the correlation of multiple TDs representing the same original Thing or ultimately unique physical entity. 12:42:34 ml: (summarizes what happened) 12:43:00 mm: Farshid's point is about a bit different topc 12:43:05 s/topc/topic/ 12:43:26 ... we should be careful about what "unique" means here 12:44:04 ml: let's close this 12:44:07 closed 12:44:33 subtopic: Issue 630 12:44:46 -> https://github.com/w3c/wot-architecture/issues/630 Issue 630 - Why are Chapter 8 and 9 separated 12:45:04 ml: got suggestions but no concrete contributions yet 12:45:27 ... would like to close this 12:45:56 ek: not clear who to work on this 12:46:14 ml: we need concrete PR as a contribution to move ahead 12:46:57 ek: the procedure is not really clear to me 12:47:48 q+ 12:48:21 ack k 12:49:03 kaz: I think section 8 describes the basic concept and section 9 describes the building blocks as concrete specs 12:49:21 ... so there is enough difference there 12:50:30 ml: we need concrete contributions to move ahead 12:50:38 ek: don't have time for that purpose 12:50:40 ack k 12:50:43 q+ 12:50:52 ... but not really sure about the procedure 12:51:44 ml: would encourage people who raise concern to consider contributions as well 12:52:19 q? 12:53:43 kaz: some of the WGs except contributions for the spec text, tests and implementations 12:54:10 ... that might be too much for WoT, but we should clarify our expectation a bit clearer 12:54:25 mm: yeah, would be good to document our policy 12:54:28 ack k 12:55:11 Issue 630 itself is closed 12:55:21 subtopic: Issue 629 12:55:50 -> https://github.com/w3c/wot-architecture/issues/629 Issue 629 - Splitting the architecture document 12:55:56 ml: (goes through the issue) 12:56:20 ml: a lot of background information within the Architecture spec 12:56:31 ... do we have right information? 12:56:32 q+ 12:56:56 ... maybe we could defer this issue to ver. 2.0 12:57:02 ek: ok, agree 12:57:13 ... but not happy to close this issue 12:58:34 q+ 12:58:36 ack e 12:59:11 mm: we should clarify which parts are normative and which are informative clearly 13:00:09 ek: if it's difficult to fix the specification from now, I'm OK to defer this issue 13:00:50 mm: defer the restructuring as a whole 13:00:57 ... and create another issue if needed 13:03:33 kaz: I'm OK with deferring this issue itself to ver. 2.0 13:03:56 ... but please remember that what is more important is the text of the spec itself 13:04:34 ... if any of the sections are identified as "informative" but include "normative" feature definitions, that should be fixed 13:04:57 ml: don't think we have that kind of problems any more 13:05:05 kaz: that's good :) 13:05:08 [adjourned] 13:05:20 rrsagent, make log public 13:05:21 rrsagent, draft minutes 13:05:21 I have made the request to generate https://www.w3.org/2022/05/24-wot-arch-minutes.html kaz 15:04:27 Zakim has left #wot-arch