11:57:18 <RRSAgent> RRSAgent has joined #wot-profile
11:57:18 <RRSAgent> logging to https://www.w3.org/2022/02/09-wot-profile-irc
11:57:24 <kaz> meeting: WoT Profile
11:57:46 <kaz> present+ Kaz_Ashimura
11:59:56 <mlagally> mlagally has joined #wot-profile
12:01:51 <Ege> Ege has joined #wot-profile
12:02:05 <kaz> present+ Ege_Korkan, Michael_Lagally
12:05:37 <kaz> present+ Tomoaki_Mizushima
12:06:58 <kaz> present+ Michael_McCool, Ryuichi_Matsukura
12:07:02 <Mizushima> Mizushima has joined #wot-profile
12:08:14 <ryuichi> ryuichi has joined #wot-profile
12:10:20 <kaz> present+ Sebastian_Kaebisch
12:10:59 <benfrancis> Apologies but I won't be able to join today due to a conflict.
12:11:22 <sebastian> topic: Discovery
12:11:24 <benfrancis> Cris also sent his apologies.
12:12:21 <sebastian> MM: I'm working on a proposal how the discovery should run for consumer
12:12:28 <kaz> regrets+ Ben, Cristiano
12:12:44 <sebastian> https://github.com/w3c/wot-discovery/issues/272
12:13:02 <sebastian> ML: Looks quite complicated
12:13:16 <kaz> s/Apologies but I won't be able to join today due to a conflict//
12:13:29 <kaz> s/Cris also sent his apologies.//
12:13:31 <sebastian> MM: I will simplify the version and ask you for feedback
12:13:46 <sebastian> <MM needs to go>
12:14:26 <kaz> s/https/-> https/
12:14:29 <sebastian> ML: we will revisit next week
12:14:41 <sebastian> Topic: Minutes check
12:14:45 <kaz> s/272/272 wot-discovery issue 272 - Consumer Process for Discovery/
12:15:12 <sebastian> https://www.w3.org/2022/02/02-wot-profile-minutes.html
12:15:38 <sebastian> any objections?
12:15:40 <sebastian> no
12:15:50 <kaz> s/http/-> http/
12:16:01 <kaz> s/html/html Feb-2/
12:16:03 <sebastian> Topic: Profile Requirements
12:16:22 <sebastian> ML: we worked on this in the last calls
12:16:36 <sebastian> ... I compiled them to a MD file
12:18:03 <mlagally> https://github.com/w3c/wot-usecases/blob/main/REQUIREMENTS/profile-requirements.md
12:18:15 <kaz> s/https/-> https/
12:18:29 <kaz> s/s.md/s.md Profile Requirements/
12:19:11 <sebastian> ML: I also created issues with all requirements
12:19:13 <sebastian> https://github.com/w3c/wot-profile/issues?q=is%3Aissue+is%3Aopen+label%3Arequirement
12:20:37 <sebastian> ... there is also the names of supporters provided
12:20:50 <Ege> q+
12:21:15 <kaz> ack e
12:21:30 <sebastian> ... we should priories the issues based on the number of supporters
12:22:42 <sebastian> Ege: we cannot validate core profile yet.
12:22:55 <sebastian> https://github.com/w3c/wot-profile/issues/170
12:23:08 <kaz> q+
12:23:42 <kaz> s/https/-> https/
12:24:00 <kaz> s/170/170 wot-profile issue 170 - Validatible TDs/
12:24:47 <sebastian> ... since behaviour cannot be validated in the TD
12:24:51 <kaz> ack k
12:25:08 <kaz> rrsagent, make log public
12:25:12 <kaz> rrsagent, draft minutes
12:25:12 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/09-wot-profile-minutes.html kaz
12:25:50 <kaz> chair: Lagally
12:26:36 <sebastian> ML: A TD follow the Profile it should guaranteed that is really working. Should be true when I buy a IoT device that promise to follow the profile.
12:26:39 <sebastian> q+
12:27:05 <kaz> i/we cannot validate/subtopic: Issue 170/
12:27:51 <kaz> kaz: @@@
12:28:15 <sebastian> ack s
12:29:48 <kaz> s/@@@/It depend on what we mean by "validation". Our expectation on "validation" should be clearly defined, and I think we could do that based on what we've been doing for our Testing (=assertion check vs manual test)./
12:30:08 <kaz> rrsagent, draft minutes
12:30:08 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/09-wot-profile-minutes.html kaz
12:30:30 <sebastian> ML: we should minimize the implementation effort for adopters.
12:31:30 <sebastian> ... I will priories this issue with prio 1
12:31:56 <kaz> s/priories/prioritize/
12:32:15 <sebastian> Subtopic: Multiple profiles (mechanism)
12:32:25 <sebastian> https://github.com/w3c/wot-profile/issues/169
12:32:46 <sebastian> important should be prio 1
12:32:49 <kaz> s/https/-> https/
12:33:06 <kaz> s/169/169 wot-profile issue 169 - Multiple profiles (mechanism)/
12:34:55 <kaz> q+
12:36:14 <kaz> sk: the current Charter says we'll have one profile, doesn't it?
12:38:01 <kaz> ml: the goal is to define the HTTP-based profile.
12:38:45 <sebastian> thanks kaz
12:44:10 <sebastian> sk: if there another profile defined (e.g., Constrained Profile, OPC UA PRofile), the profile should be independent of existing profiles
12:44:57 <kaz> kaz: I'm a bit confused. What do you mean by saying "Multiple profiles mechanism is a requirement for WoT Profile"? Maybe support for multiple protocol?/
12:45:07 <kaz> s|?/|?|
12:49:59 <kaz> (some more discussion about our expectation for having multiple profiles)
12:51:48 <sebastian> Subtopic: Finite set of features and capabilities to implement by the consumer
12:51:55 <sebastian> https://github.com/w3c/wot-profile/issues/172
12:52:01 <sebastian> prio 1
12:52:25 <sebastian> Subtopic: Developer guidance
12:52:29 <sebastian> https://github.com/w3c/wot-profile/issues/173
12:52:31 <sebastian> Prio 1
12:53:54 <sebastian> Subtopic: Limit and reduce complexity
12:54:04 <sebastian> https://github.com/w3c/wot-profile/issues/167
12:54:06 <sebastian> Prio 1
12:55:24 <sebastian> Kaz I need to go in 1min
12:55:27 <sebastian> can you take over?
12:56:01 <kaz> i/some more/kaz: please note that the current WG Charter itself doesn't say we're limited to only one Profile. It's rather our own decision based on the progress so far. So we can clarify our expectation for having multiple Profiles first, and then think about what we can do next./
12:56:20 <kaz> i/I'm a bit/scribenick: kaz/
12:56:24 <mlagally> proposal: Select all P1 requirements in scope of the Profile 1.0 spec. These are identified by https://github.com/w3c/wot-profile/issues?q=is%3Aissue+is%3Aopen+label%3AP1
12:56:37 <kaz> i/Finite set of features/scribenick: sebastian/
12:56:39 <sebastian> thanks
12:57:10 <mlagally> proposal: Select all P1 requirements in scope of the Profile 1.0 spec. They must be satisfied by the Profile 1.0 specification.. These are identified by https://github.com/w3c/wot-profile/issues?q=is%3Aissue+is%3Aopen+label%3AP1
12:57:28 <kaz> q+
12:57:39 <mlagally> proposal: Select all P1 requirements in scope of the Profile 1.0 spec. They must be satisfied by the Profile 1.0 specification. These are identified by https://github.com/w3c/wot-profile/issues?q=is%3Aissue+is%3Aopen+label%3AP1
12:58:00 <kaz> kaz: you've added the "P1" label based on the number of the supporters. right?
12:58:03 <kaz> ml: yes
12:58:36 <mlagally> resolution: Select all P1 requirements in scope of the Profile 1.0 spec. They must be satisfied by the Profile 1.0 specification. These are identified by https://github.com/w3c/wot-profile/issues?q=is%3Aissue+is%3Aopen+label%3AP1
12:58:57 <kaz> [adjourned]
12:59:02 <kaz> rrsagent, make log public
12:59:06 <kaz> rrsagent, draft minutes
12:59:06 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/09-wot-profile-minutes.html kaz
13:58:13 <Mizushima> Mizushima has left #wot-profile
15:15:36 <Zakim> Zakim has left #wot-profile