12:58:24 RRSAgent has joined #wot-uc 12:58:28 logging to https://www.w3.org/2023/01/10-wot-uc-irc 12:58:44 meeting: WoT Use Cases 13:00:36 mlagally has joined #wot-uc 13:01:58 Mizushima has joined #wot-uc 13:05:34 chair: Lagally 13:05:47 present+ Michael_Lagally, Kaz_Ashimura, Tomoaki_Mizushima 13:11:14 agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#Jan_10th.2C_2023 13:14:54 scribenick: kaz 13:14:57 topic: Minutes 13:15:14 -> https://www.w3.org/2022/12/20-wot-uc-minutes.html Dec-20 13:17:35 approved 13:18:18 topic: Contributions 13:18:41 subtopic: PR 200 13:18:51 -> https://github.com/w3c/wot-usecases/pull/200 PR 200 - Add new use cases for smart agriculture-Milking 13:19:21 ml: MunHwan has updated the PR 13:20:45 merged 13:21:51 subtopic: PR 204 13:22:57 ->https://github.com/w3c/wot-usecases/pull/204 PR 204 - carry over profile requirements from profile spec 13:26:19 s/->h/-> h/ 13:26:22 merged 13:26:40 subtopic: PR 193 13:26:51 -> https://github.com/w3c/wot-usecases/pull/193 PR 193 - Add new requirement fields for the template 13:27:12 ml: this in an improvement for the Use Cases template 13:27:37 ... we have to add similar changes to the HTML doc as well 13:27:37 q+ 13:29:23 kaz: adding information on implied requirements would be useful 13:29:44 ... however, I'm not sure if it would be the best way to put that information directly into the Use Case template 13:30:13 ... because some use cases could be related to multiple requirements 13:30:29 ... and some requirements could be related to multiple use cases 13:30:45 ... we should avoid potential redundancy if possible 13:31:09 ml: (shows his slides on extracting requirements from the use cases) 13:32:09 kaz: yeah 13:32:31 ... I agree we need to define our procedure for extracting requirements clearer 13:32:51 ... e.g., what is needed for which use case for what purpose 13:33:19 ml: (refines the diagram of requirements extraction a bit) 13:33:55 ... this was not really included in today's agenda 13:34:05 ... but would be very important for the next Charter activity 13:37:12 q+ 13:37:32 ack 13:39:05 kaz: would personally call the "shortlist" "categorization of the basic need" 13:39:11 ml: ok 13:39:33 ... (put "categorization of the basic need based on the business priority and resources" 13:39:40 s/s"/s")/ 13:39:48 ack k 13:39:50 ack m 13:40:01 mizu: that discussion is important, and I agree 13:40:34 ... would point out that we should consider actual needs from non-Engineer stakeholders 13:40:53 ... because we've mainly asking engineers to provide use cases 13:41:01 ml: yes, that's very important 13:41:05 ... completely agree 13:41:47 ... that implies we need to ask people outside of the WoT WG as well to provide use cases 13:41:49 kaz: right 13:42:08 ml: any other comments? 13:42:15 (none) 13:43:29 topic: Use case coverage 13:43:41 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv coverage.csv 13:44:11 -> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage-gaps.md coverage-gaps.md 13:44:23 q+ 13:46:17 kaz: thinking about those technical topics is important, but most of them are "technical topics" than "use cases and their coverage" 13:46:51 ... so I'd suggest we clarify actual use cases for each technical topic quickly again to see the "coverage of our use cases" 13:47:00 ml: right 13:47:12 ... (shows the coverage.csv as well) 13:47:39 rrsagent, make log public 13:47:45 rrsagent, draft minutes 13:47:46 I have made the request to generate https://www.w3.org/2023/01/10-wot-uc-minutes.html kaz 13:50:38 kaz: for example, we can add "Important technical topics which are not covered yet" at the top of the coverage-gaps.md 13:51:09 ... and should put which use case or use cases are related to each technical topic 13:51:30 rrsagent, make log public 13:51:33 rrsagent, draft minutes 13:51:34 I have made the request to generate https://www.w3.org/2023/01/10-wot-uc-minutes.html kaz 13:52:40 ml: how to add clarifications to each technical topic? 13:52:57 kaz: we should start with a basic list of topics first 13:53:08 ... so should not add too much detail at the moment 13:54:54 ml: (quickly skim the list of topics) 13:55:14 q? 13:55:16 q- 13:55:19 q+ 13:56:26 kaz: probably it would be better to put several categories to this document as well 13:57:15 ... e.g., data including geolocation and time, wide review viewpoints including security, privacy, accessibility and internationalization 13:59:59 ml: yeah 14:00:13 ... we can try that kind of restructure during the next calls 14:01:21 topic: Next calls 14:01:52 ml: we won't have a use case call next Tuesday 14:02:10 kaz: in that case, we should clarify when to have the next call 14:02:24 ml: yeah, let's think about the schedule after the Charter discussion 14:02:29 [adjourned] 14:02:37 rrsagent, draft minutes 14:02:38 I have made the request to generate https://www.w3.org/2023/01/10-wot-uc-minutes.html kaz 16:10:11 Zakim has left #wot-uc