10:59:18 RRSAgent has joined #wot-profile 10:59:18 logging to https://www.w3.org/2022/11/02-wot-profile-irc 10:59:22 meeting: WoT Profile 11:01:17 McCool_ has joined #wot-profile 11:01:19 mlagally has joined #wot-profile 11:01:25 Mizushima has joined #wot-profile 11:01:33 present+ Kaz_Ashimura, Michael_McCool, Michael_Lagally 11:03:29 present+ Sebastian_Kaebisch 11:03:46 present+ Tomoaki_Mizushima 11:03:56 present+ Ege_Korkan 11:04:08 Ege has joined #wot-profile 11:06:12 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_.28combined_Profile_.2B_Architecture.29_Nov_2nd.2C_2022 11:06:41 q+ 11:06:47 ktoumura has joined #wot-profile 11:06:57 present+ Kunihiok_Toumura 11:08:42 sebastian has joined #wot-profile 11:09:24 topic: minutes 11:09:34 i|minutes|MM: we should add time limits to the issues. We can do it at the end| 11:09:45 -> https://www.w3.org/2022/10/26-wot-profile-minutes.html 11:09:52 i/we should/topic: agenda/ 11:10:06 s/html/html Oct-26/ 11:10:12 ML: objections? 11:10:14 ack k 11:10:15 MM: no 11:10:29 present- Kunihiok_Toumura 11:10:35 present+ Kunihiko_Toumura 11:10:39 -> https://www.w3.org/2022/10/27-wot-arch-minutes.html 11:10:44 present+ Ryuichi_Matsukura 11:10:59 ML: in this call we made a resolution 11:11:11 11:11:17 Webasto 11:11:19 i/html/html Oct-27/ 11:12:06 ryuichi has joined #wot-profile 11:12:08 ML: I want to add the company name of the planed guest 11:12:29 s/planed guest/planned guest/ 11:12:33 q+ 11:12:45 11:14:05 MM: 8. December is too late we should do the request some weeks earlier 11:14:38 s/ML: I want to add the company name of the planed guest// 11:14:41 Kaz: There is no need to mention the comany for now. We can do it when the guest is showing up 11:14:51 s/comany/company 11:15:07 s/Kaz: There is no need to mention the comany for now. We can do it when the guest is showing up// 11:15:19 ok 11:15:23 s/ok// 11:16:59 ML: requests that the minutes should mention that PR #862 has no group consensus 11:17:53 ... instead of "ok" there should be "I object" 11:19:39 ML: any objections? 11:20:26 no 11:20:40 topic: Publication Schedule 11:21:20 MM: targing 8. December is to dangerous, we should do the CR tranistion request earlier 11:22:44 s/targing/targeting 11:23:25 ML: I agree 11:23:28 s/to dan/too dan/ 11:23:36 topic: Issues to close 11:23:59 11:24:13 i|targ|-> https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md schedule| 11:24:21 -> https://github.com/w3c/wot-architecture/issues?q=is%3Aissue+is%3Aopen+label%3Aclose 11:24:30 -> https://github.com/w3c/wot-architecture/issues?q=is%3Aissue+is%3Aopen+label%3A%22close+next+week%22 11:25:10 q+ 11:25:14 q+ 11:25:55 11:26:02 -> https://github.com/w3c/wot-architecture/issues?q=is%3Aissue+is%3Aopen+label%3A%22by+CR+transition%22 11:27:30 q+ 11:27:33 ML: we should evaluate the use cases. The task is to complete the assessment for architecture. 11:27:37 ktoumura has joined #wot-profile 11:27:52 ... it is a shame that we have no ansear for geo location 11:28:04 s/ansear/answear 11:28:46 Kaz: We should clearifiy what is a must for the CR and what can be defered to the next version 11:28:46 ack k 11:29:27 ack e 11:29:53 ML: Profile would ansewear the geo location topic, there is already a placeholder 11:30:33 s/ansewear/answer/ 11:32:03 Ege: We already fullfill the current charter. Use cases should be used to identify topics for new charter. 11:32:25 s/meeting: WoT Profile/meeting: WoT Architecture + WoT Profile/ 11:32:29 ... TD already supports geo locations. There are examples. 11:32:31 rrsagent, make log public 11:32:39 rrsagent, draft minutes 11:32:39 I have made the request to generate https://www.w3.org/2022/11/02-wot-profile-minutes.html kaz 11:32:39 q? 11:32:49 q+ 11:33:48 ack s 11:34:25 ack mc 11:34:55 SK: we should conentrate on the PRs and we should not do use case dicussion 11:35:29 s/dicussion/discussion 11:38:08 (we need to move on; there is no way we have time to add a good spec for geolocation at this point, so we need to simply have a clear resolution to defer it (and other requirements) to the next version) 11:38:21 +1 11:38:36 q+ 11:39:09 Kaz: There should be issues provided that address use case topic. E.g., there should be geolocation issue in the TD repo that address this topic. 11:39:25 s/topic/topics 11:40:34 ack k 11:40:40 ack m 11:40:57 topic: PR 11:41:09 11:41:19 -> https://github.com/w3c/wot-architecture/pulls 11:42:06 subtopic: PR 858 11:42:14 -> https://github.com/w3c/wot-architecture/pull/858 11:42:15 s/this topic./this topic. If some of the requirements are not covered by any of the specs yet, we should identify those features "to be deferred"./ 11:42:35 PR about prep for CR, finalize IR and document at-risk items 11:42:58 11:43:06 s/858/858 PR 858 - Prep for CR, finalize IR and document at-risk items/ 11:44:22 MM: There is a new text about the exit CR 11:44:53 ML: looks good 11:45:17 -> https://cdn.statically.io/gh/w3c/wot-architecture/a1aecbf83fcd5a20e8e06c226edf454f90ecf729/publication/ver11/3-cr/Overview.html Rendered draft of ver11/3-cr/Overview.html 11:46:12 MM: also fixed some typos and respec errors 11:46:18 +1 11:46:22 ML: I'm ok to merge, any objections? 11:46:25 no 11:47:15 subtopic: PR 862 and PR 871 11:47:27 -> https://github.com/w3c/wot-architecture/pull/862 11:47:52 -> https://github.com/w3c/wot-architecture/pull/871 11:48:01 s/862/862 PR 862 - Option 1: Switch Profile to non-normative section/ 11:48:19 s/871/871 PR 871 - Option 2: Define whole Chapter 7 non-normative/ 11:48:48 q+ 11:49:03 MM: there is no assertation in Chapter 7 there is no need to define the whole chapter 7 normative 11:49:31 ML: another alternative we can mark the Profile section as "at-risk" 11:50:03 q+ 11:50:15 ack k 11:51:18 Kaz: I'm ok with Option 2, however, we need to clearify our policy for the transition 11:52:14 MM: I think option 2 is the most easy solution here, it has no asserations. 11:52:17 s/clearify/clarify/ 11:52:18 Ege: Im ok with it 11:52:32 ML: any objections? 11:52:47 ... then lets merge this 11:52:50 s/for the transition/for testing and explain the policy for the CR Transition./ 11:53:49 ML: Problem solved, I will also close Option 1 11:53:50 q+ 11:54:07 subtopic: PR 855 11:54:21 -> https://github.com/w3c/wot-architecture/pull/862 11:55:38 q+ 11:55:51 11:56:15 s/862/855 PR 855 - Clarify interaction affordance binding mechanisms/ 11:56:21 Ege: It breaks the TD design. 11:57:04 i|It b|-> https://pr-preview.s3.amazonaws.com/w3c/wot-architecture/855/efb4cf6...9a0169e.html#hypermedia-driven 6.7.1 Hypermedia-driven 11:57:11 q+ 11:57:27 ... personally, I would no support this 11:57:38 s/no/not 11:59:37 ack mc 11:59:53 q+ 12:00:05 ack e 12:00:25 proposal: Accept the current editor's draft as the CR candidate. Some editorial changes to incorporate the changes from PR #871. 12:00:45 proposal: Accept the current editor's draft as the CR candidate including some editorial changes to incorporate the changes from PR #871. 12:02:37 +1 12:02:40 ML: any objections? 12:02:42 +1 12:02:48 +1 12:02:57 same changes to the ED: https://w3c.github.io/wot-architecture/#sec-building-blocks to be applied to the the CR draf 12:03:02 s/draf/draft/ 12:03:55 resolution: Accept the current editor's draft as the candidate for CR transition. 12:04:07 adjourn 12:04:56 s|CR draft|CR draft at: https://github.com/w3c/wot-architecture/blob/main/publication/ver11/3-cr/| 12:05:01 rrsagent, draft minutes 12:05:01 I have made the request to generate https://www.w3.org/2022/11/02-wot-profile-minutes.html kaz 12:07:15 chair: Lagally 12:07:16 rrsagent, draft minutes 12:07:16 I have made the request to generate https://www.w3.org/2022/11/02-wot-profile-minutes.html kaz 13:13:24 Ege_ has joined #wot-profile 13:14:45 Mizushima has left #wot-profile 13:17:36 Ege has joined #wot-profile 14:00:41 Zakim has left #wot-profile