12:01:11 RRSAgent has joined #wot-profile 12:01:11 logging to https://www.w3.org/2022/01/19-wot-profile-irc 12:01:16 meeting: WoT Profile 12:01:33 present+ Kaz_Ashimura, Ben_Francis, Ege_Korkan, Michael_McCool 12:02:04 benfrancis has joined #wot-profile 12:02:21 present+ Michael_Lagally 12:03:29 McCool has joined #wot-profile 12:04:01 mlagally__ has joined #wot-profile 12:04:11 Ege has joined #wot-profile 12:05:12 rrsagent, make log public 12:05:16 rrsagent, draft minutes 12:05:16 I have made the request to generate https://www.w3.org/2022/01/19-wot-profile-minutes.html kaz 12:06:05 present+ Tomoaki_Mizushima 12:06:56 topic: Logistics 12:07:12 IRC channel for the WoT Profile call will be "#wot-profile" 12:08:28 Kaz sent out the WebEx information to the group lists 12:10:06 the Architecture wiki will have the information on the Profile call as well 12:10:21 i/Logistics/scribenick: kaz/ 12:10:28 present+ Ryuichi_Matsukura 12:10:55 topic: Agenda 12:11:00 ryuichi has joined #wot-profile 12:11:04 minutes review 12:11:16 publication timeline 12:11:26 (including wide review) 12:11:34 Mizushima has joined #wot-profile 12:12:06 mm: we can talk about the wide review procedure during the main call later 12:12:22 Profile topics 12:12:33 ml: requirements 12:12:42 ... to avoid any misunderstandings 12:12:56 ... then out of the box interoperability 12:13:02 ... deployment scenarios 12:13:20 ... implementability and test plan 12:13:23 ... validation 12:13:38 ... anything to be added? 12:13:40 (none) 12:14:08 https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review 12:14:24 mm: the above is the guide for the wide reviews 12:14:55 ... the question is if we need to bump the feature freeze date 12:15:07 ml: let's start with the minutes review 12:15:10 mm: ok 12:15:14 topic: Minutes 12:15:40 -> https://www.w3.org/2022/01/13-wot-arch-minutes.html Jan-13 12:15:58 ml: (goes through the minutes from the Architecture call on Jan 13) 12:17:12 cris has joined #wot-profile 12:18:38 ml: better to have "WoT Architecture" as the section title for the section 4 12:19:02 approved 12:19:10 s/ap/fixed and ap/ 12:20:13 https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Deliverable_and_F2F_Meeting_Plan - regarding timeline and schedule 12:22:04 ml: note the REQUIREMENTS/profile-requirements.md has been renamed to REQUIREENTS/profile-requirements-13.1.md 12:22:18 topic: Publication timeline 12:22:36 s|https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Deliverable_and_F2F_Meeting_Plan - regarding timeline and schedule|| 12:22:46 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Deliverable_and_F2F_Meeting_Plan - regarding timeline and schedule 12:23:17 s/- regarding timeline and schedule/timeline and schedule on the main wiki/ 12:23:21 rrsagent, draft minutes 12:23:21 I have made the request to generate https://www.w3.org/2022/01/19-wot-profile-minutes.html kaz 12:23:35 mm: (explains the current proposed plan) 12:23:56 ... just discussed during the Chairs call this morning 12:24:15 ... we've missed some of the deadlines 12:24:36 ... should be marked as "tentative" 12:25:08 ... regarding feature freese 12:25:12 s/freese/freeze/ 12:25:18 ... everything is bumped 12:26:05 ... Kaz proposed we concentrate the document consistency check first, and possibly bump the test fest depending on the feature freeze timing 12:26:23 ml: what do you mean by "feature freeze"? 12:26:28 mm: nothing to be changed 12:26:47 ... we can start the process for the wide review in parallel 12:27:11 ml: we do wide reviews and then fix the features 12:27:53 ... 31 Jan is not the final freeze. right? 12:27:56 mm: right 12:28:26 ... one remaining topic for TD is webhooks 12:28:38 q+ 12:29:18 kaz: let's concentrate on the WoT Profile spec for this call 12:29:26 ... we can talk about TD later during the TD call 12:29:29 mm: that's true 12:30:49 ml: we can start wide review for WoT Profile 12:31:13 ... (put "XX" as the expected date for the placeholder) 12:31:34 s/XX/XX January/ 12:33:24 ... note we have many blocker issues for Profile 12:34:16 ... it is not realistic for Profile to have the Testfest even in mid-March 12:34:23 s/it is/so it's/ 12:35:01 ... we should deliver our spec as high quality as possible 12:36:07 mm: to be clear, TD 1.1 is not major version up but version up 12:37:02 ... many of the expected features defined by the Use Cases document to be implemented by the major updated version 12:37:25 ... looking at the WoT Profile by itself, what would be the reasonable schedule? 12:37:33 s/looking/on the other hand, looking/ 12:38:08 ml: we're holding discussion on our expectations 12:39:40 ... let's have more discussion during the main call too 12:39:46 mm: ok 12:40:08 ... wanted to identify the dates for Profile 12:40:09 q+ 12:41:43 kaz: if we can't tell concrete dates today, maybe we could think about how and when we identify the dates 12:42:01 ... for example, continue the discussion on requirements, and in 2 weeks we can tell the dates 12:42:24 ml: would like to continue the discussion on our requirements 12:42:30 ack k 12:42:38 topic: Requirements 12:43:14 -> https://github.com/w3c/wot-usecases/blob/main/REQUIREMENTS/profile-requirements-13.1.md Requirements on GitHub 12:44:18 mm: regarding "Ambiguities", need to narrow the choices 12:45:16 q? 12:45:32 ml: how to fix? 12:45:38 mm: select single choice 12:45:40 q+ 12:45:59 ml: ok to remove "*" now? 12:46:02 mm: yes 12:47:16 kaz: btw, we should mention the requirements with "*" need clarifications/improvements 12:47:49 ml: (adds description for that) 12:48:30 bf: the term "ambiguities" is ambiguous 12:50:21 ... the use of PUT or POST is clear 12:51:16 ... but what "choice of properties vs actions" means? 12:51:36 ... "observe protocols" also 12:52:21 ml: choice of actions/properties should be done in the TD 12:52:48 bf: with the clarification, you can remove my "*" (request for clarification) 12:53:01 zakim, who is on the call? 12:53:01 Present: Kaz_Ashimura, Ben_Francis, Ege_Korkan, Michael_McCool, Michael_Lagally, Tomoaki_Mizushima, Ryuichi_Matsukura 12:53:12 present+ Cristiano_Aguzzi 12:53:21 ml: what about Cristiano? 12:53:30 q+ 12:53:34 ca: ack k 12:53:44 s/ca: ack k// 12:53:54 ca: let's see the issue 12:55:18 -> https://github.com/w3c/wot-profile/issues/156 wot-profile issue 156 - Profile requirements 12:55:29 ca: you can remove my "*" from the requirements 12:56:12 ek: important to define what is complex 12:56:30 ml: which requirement are you talking about? 12:56:35 ek: "complexity" 12:57:27 i/what about C/subtopic: Limit and reduce complexity/ 12:58:00 +1 12:58:05 q+ 12:58:09 ack e 12:59:02 ek: need to determine what we exactly mean 12:59:12 s/ek: need to determine what we exactly mean// 12:59:19 i/+1/ek: need to determine what we exactly mean/ 12:59:27 ca: the point is fine 12:59:35 +1 to cris 12:59:59 subtopic: Ambiguities - revisited 13:00:06 ml: can you support it now? 13:00:16 ca: ok 13:00:18 ek: ok 13:01:16 ml: now, I'm saving the updated requirements as "19.1" 13:01:22 https://github.com/w3c/wot-usecases/blob/main/REQUIREMENTS/profile-requirements-19.1.md 13:01:25 [adjourned] 13:01:29 rrsagent, draft minutes 13:01:29 I have made the request to generate https://www.w3.org/2022/01/19-wot-profile-minutes.html kaz 13:01:33 s/now/tx. now/ 13:11:25 Ege has joined #wot-profile 14:30:13 Mizushima has left #wot-profile 15:01:59 Zakim has left #wot-profile