12:03:56 RRSAgent has joined #wot-profile 12:03:56 logging to https://www.w3.org/2022/01/26-wot-profile-irc 12:03:58 meeting: WoT Profile 12:04:09 present+ Kaz_Ashimura, Ben_Francis, Michael_Lagally 12:04:10 benfrancis has joined #wot-profile 12:05:17 Mizushima has joined #wot-profile 12:07:04 scribenick: McCool 12:07:18 present+ Ryuichi_Matsukura, Sebastian_Kaebisch, Tomoaki_Mizushima 12:07:55 ryuichi has joined #wot-profile 12:08:05 rrsagent, make log public 12:08:09 rrsagent, draft minutes 12:08:09 I have made the request to generate https://www.w3.org/2022/01/26-wot-profile-minutes.html kaz 12:08:31 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Profile_-_Jan_26th.2C_2022 12:10:03 chair: Lagally 12:10:19 present+ Michael_McCool 12:10:23 rrsagent, draft minutes 12:10:23 I have made the request to generate https://www.w3.org/2022/01/26-wot-profile-minutes.html kaz 12:11:20 McCool has joined #wot-profile 12:11:24 ml: want to talk about roadmap and timeline [08:07] ... and then continue the requirements discussion [08:07] ... incl definition of out-of-the-box interoperability [08:09] ... would like to use issue tracker to resolve requirements point by point rather than opening general discussion [08:10] mm: would like also give a status update on self-description - plan to resolve 12:11:52 topic: minutes 12:12:05 ml: approval of minutes of previous call 12:12:47 mm: changed the irc, so under wot-profile now 12:13:39 i/topic: minutes/topic: Agenda/ 12:13:39 i/topic: minutes/ml: want to talk about roadmap and timeline/ 12:13:39 i/topic: minutes/... and then continue the requirements discussion/ 12:13:39 i/topic: minutes/... incl definition of out-of-the-box interoperability/ 12:13:40 i/topic: minutes/... would like to use issue tracker to resolve requirements point by point rather than opening general discussion/ 12:13:42 i/topic: minutes/mm: would like also give a status update on self-description - plan to resolve/ 12:14:16 s/ml: want to talk about roadmap and timeline [08:07] ... and then continue the requirements discussion [08:07] ... incl definition of out-of-the-box interoperability [08:09] ... would like to use issue tracker to resolve requirements point by point rather than opening general discussion [08:10] mm: would like also give a status update on self-description - plan to resolve// 12:15:37 ml: typo fix; timeline and schedule; link to requirements on github (clean up of *'s) 12:15:57 ml: can we approve the minutes? 12:16:08 ml: hearing no objections... approved 12:16:12 topic: roadmap 12:17:15 ml: pull out into powerpoint to edit... 12:17:33 [[ 12:17:34 1. clarify requirements 12:17:34 2. profile scope, identify gaps 12:17:34 3. contributions to resolve normative gaps 12:17:34 4. contributions to resolve informative gaps 12:17:34 5. publication of second working draft 12:17:36 6. plugfest/testfest 12:17:38 7. incorporate review feedback from 2nd WD review 12:17:40 8. publication of candidate recommendation 12:17:42 ]] 12:17:56 q+ 12:19:48 ack m 12:19:53 rrsagent, draft minutes 12:19:53 I have made the request to generate https://www.w3.org/2022/01/26-wot-profile-minutes.html kaz 12:20:17 present+ Cristiano_Aguzzi 12:20:41 cris_ has joined #wot-profile 12:20:43 i/topic: Agenda/scribenick: kaz/ 12:20:47 rrsagent, draft minutes 12:20:47 I have made the request to generate https://www.w3.org/2022/01/26-wot-profile-minutes.html kaz 12:21:28 i/approval of mi/scribenick: McCool/ 12:21:28 rrsagent, draft minutes 12:21:28 I have made the request to generate https://www.w3.org/2022/01/26-wot-profile-minutes.html kaz 12:22:40 mm: the schedule really can't be extended further; also, I suggest we make the requirements as narrow as possible 12:23:05 ... KISS principle; the simpler the spec is, the easier it will be to get it done (and through wide review....) 12:24:25 ml: edits points on roadmap to add suggest durations 12:26:35 mm: proposed schedule puts finalization of normative gaps around time of first plugfest 12:26:48 ... so we could at least do some preliminary testing in that plugfest 12:27:34 ml: so end of March we should have a sync point 12:27:45 ... then clean up some informative gaps 12:28:00 ... and a second working draft around mid-May 12:31:34 mm: note second test fest should focus on testing and generating an implementation report, which implies we need stable implementations a few weeks prior 12:32:14 q+ 12:32:47 mm: need to keep things narrow to hit this 12:33:04 bf: given our current velocity is less than one pr per call 12:33:23 ... so we would need to have 23 calls to empty the current prs 12:33:39 ml: well, some of these are obsolete and will go away 12:33:45 q? 12:33:47 ack b 12:33:49 ... we are doing a second loop 12:33:53 rrsagent, draft minutes 12:33:53 I have made the request to generate https://www.w3.org/2022/01/26-wot-profile-minutes.html kaz 12:34:32 ml: but I hear you, you feel this is not realistic 12:34:51 bf: only realistic if we review and close PRs out of meetings 12:34:55 q+ 12:35:06 q+ 12:36:03 mm: suggest compromise where we use labels to identify easy cases, i.e. things that are obsolete, things that are not contentious (editorial) 12:36:14 ack m 12:36:44 kaz: should be recall deadline of charter period itself 12:37:03 ... and consider how long things should take; can go bottom up 12:37:41 ... for example, if need to finalize normalize features, and only have 1mo, then we need to shorten requirements 12:38:57 mm: note that for first plugfest I was only talking about initial testing, not full testing, which will not be feasible 12:39:20 topic: requirements 12:39:36 ml: had a presentation Dec 16 12:39:41 https://github.com/w3c/wot-profile/issues/156 https://github.com/w3c/wot-profile/blob/main/contributions/2021-12-16-WoT-Profiles-discussion%2Brequirements%2BOOTBI.pdf 12:40:29 ml: see also issue #156 12:40:35 ... profile requirements 12:42:13 mm: still think o-of-the-box-interop is primary requirement, the rest are supporting 12:42:20 ml: let's defer that discussion 12:43:10 s|https://github.com/w3c/wot-profile/issues/156|-> https://github.com/w3c/wot-profile/issues/156 wot-usecases PR 156 - Insert digital-twin-use-case.md and use-case-opc-ua-binding.md into index.html| 12:44:01 ml: disagreement about some requirements, e.g. human readability 12:44:09 mm: I also disagree that this should be a requirement 12:44:22 ml: let's then create an issue to capture input on that offline 12:45:13 sb: also a minus... have discussed this in the past 12:45:52 ml: now developer guidance 12:46:09 bf: comments on the issue, cristiano and I both said we supported it 12:47:36 q+ 12:47:51 q- 12:48:01 ack b 12:48:28 mm: for "multiple profiles", is a bit confused; one TD supports more than one? 12:48:50 bf: no, "composable" profiles is next point 12:49:37 mm: my main concern with both multiple and composable are future extensions; for now we should focus on just one 12:50:18 sb: current mechanism for TD already allows for selection from a set of profiles 12:50:34 q+ 12:50:42 mm: so is a requirement, but already satisfied 12:52:07 mm: also composable only makes sense if there are multiple profiles 12:52:44 bf: left some feedback on reasons for whether or not we should have multiple profiles 12:53:02 ... but this is about the *mechanism* to support more than one, and I agree we should have that 12:53:18 s/whether or not/when/ 12:54:01 ml: regarding composable profiles: let's create an issue to discuss 12:54:33 q+ 12:54:33 ml: next, verifiable TDs 12:55:00 ack b 12:55:02 q+ 12:55:21 bf: regarding filing issues to discuss, let's make sure we clean up old issues on these 12:56:18 ack 12:56:24 ack c 12:56:27 cr: support validatible requirement 12:56:47 ml: yes, on identification; is moot if we can't identify them 12:57:06 ... 4m left, will commit on a branch and make a PR for discussion 12:57:47 mm: would be nice to link issues from requirement docs so it is easy to find 12:57:59 ml: ... 12:58:23 q+ 12:58:38 mm: let's not merge just yet but keep as a PR so we can capture comments 12:58:57 ok: PR #179 12:59:10 ml: PR #179, leaving open 12:59:16 ack k 12:59:59 ml: also, there is a label, "requirement clarification" for requirements discussions 13:00:09 ... and please, let's close on this as soon as possible 13:00:50 (after the discussion, Kaz asks about how to proceed, and Lagally explains his plan based on the "Roadmap") 13:01:13 ml: planning horizon at this point just first three points on plan 13:01:20 [adjourned] 13:01:25 rrsagent, draft minutes 13:01:25 I have made the request to generate https://www.w3.org/2022/01/26-wot-profile-minutes.html kaz 13:29:05 Mizushima has left #wot-profile 13:29:44 Ege has joined #wot-profile 15:02:36 Zakim has left #wot-profile