12:48:25 RRSAgent has joined #wot-uc 12:48:29 logging to https://www.w3.org/2023/10/19-wot-uc-irc 12:56:45 McCool has joined #wot-uc 12:58:28 meeting: WoT Use Cases 13:01:49 Mizushima has joined #wot-uc 13:03:34 https://www.w3.org/pubrules/?url=https%3A%2F%2Fw3c.github.io%2Fwot-discovery%2Fpublication%2F6-rec%2FOverview.html&profile=REC-Echidna&validation=simple-validation&informativeOnly=false&echidnaReady=true&patentPolicy=pp2020 13:06:25 chair: McCool 13:06:28 Ege has joined #wot-uc 13:06:55 https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#October_19th.2C_2023 13:06:57 JKRhb has joined #wot-uc 13:07:31 present+ Kaz_Ashimura, Michael_McCool, Ege_Korkan, Jan_Romann, Kunihiko_Toumura,Michael_Koster, Tomoaki_Mizushima 13:07:51 ktoumura has joined #wot-uc 13:09:33 s/https/agenda: https/ 13:09:37 topic: Minutes 13:09:46 -> https://www.w3.org/2023/04/18-wot-uc-minutes.html Apr-18 13:09:49 approved 13:10:32 i/app/scribenick: kaz/ 13:10:36 scribenick: Ege 13:10:42 topic: Agenda 13:11:18 mm: I have put myself as temporary use cases TF lead 13:11:19 luca_barbato has joined #wot-uc 13:11:41 s/topic: Agenda/topic: TF Lead/ 13:12:13 mm: I will also cleanup the wiki 13:12:39 i|I have|-> https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#People People section of the WoT Use Cases wiki| 13:12:47 rrsagent, make log public 13:12:52 rrsagent, draft minutes 13:12:53 I have made the request to generate https://www.w3.org/2023/10/19-wot-uc-minutes.html kaz 13:13:01 topic: Today's Topics 13:13:43 subtopic: Process 13:14:07 mm: we need to figure out how to link all use cases and requirements to each other 13:15:17 ... we need to categorize them as well. For security they are obvious to me but for discovery I am not sure 13:15:53 ... I have a list already 13:15:56 q+ 13:16:40 q+ 13:16:58 ek: is this list for the previous rec? 13:16:59 mm: yes 13:17:21 present+ Luca_Barbato 13:17:31 ek: also, did you use the existing use cases for this? 13:17:52 mm: no but we should find the relevant use cases 13:18:47 s/no but/no, but/ 13:19:05 q+ 13:19:10 ack e 13:21:03 mm: we have a section commented out 13:21:28 kaz: we should use this call and following ones for agreeing on the process and how to organize the current document 13:21:55 mm: Using Discovery as an example to agree on the process would work nicely 13:22:14 ack k 13:22:41 mm: I will copyover the requirements now 13:23:13 mm: each requirement should have an identifier 13:23:47 q+ 13:24:35 i/I will/kaz: yeah, we could use the existing resources (both those in the Use Cases Note and those in the Discovery.md) to discuss the process :) 13:24:46 i/kaz:/scribenick: kaz/ 13:24:51 ack e 13:24:58 i/I will/scribenick: Ege/ 13:24:59 ek: you can have ids in lists no? 13:25:03 rrsagent, draft minutes 13:25:04 I have made the request to generate https://www.w3.org/2023/10/19-wot-uc-minutes.html kaz 13:25:10 mm: Yeah and we can have some short names 13:25:20 s|https://www.w3.org/pubrules/?url=https%3A%2F%2Fw3c.github.io%2Fwot-discovery%2Fpublication%2F6-rec%2FOverview.html&profile=REC-Echidna&validation=simple-validation&informativeOnly=false&echidnaReady=true&patentPolicy=pp2020|| 13:25:21 rrsagent, draft minutes 13:25:23 I have made the request to generate https://www.w3.org/2023/10/19-wot-uc-minutes.html kaz 13:27:14 s/ids/IDs/ 13:27:42 s/lists no/lists, can't you/ 13:28:01 s/Yeah and/Yeah,/ 13:28:04 rrsagent, draft minutes 13:28:05 I have made the request to generate https://www.w3.org/2023/10/19-wot-uc-minutes.html kaz 13:29:33 ek: so this requirement is too broad, ideally we should not have such requirements 13:29:44 mm: yes this is a broad one but we can look at the process 13:29:58 ek: yes I agree with the linking and similar part 13:31:47 mm: I can create this requirement, i.e. the template to use, then we can do the same for the others 13:33:42 rrsagent, draft minutes 13:33:44 I have made the request to generate https://www.w3.org/2023/10/19-wot-uc-minutes.html kaz 13:34:06 ek: Actually, discovery has the requirements document so it is a bit an unusual case. I am not sure if TD has one 13:34:11 mm: that is not good 13:34:24 q+ 13:35:50 ack k 13:36:22 kaz: to generate an improved version of the Use Cases Note, we need to clarify @@@ 13:36:34 mm: I get confused with different types of requirements 13:37:08 ... what is a functional or technical requirement? 13:37:57 s|@@@|what kind of granularity of the description is needed for the categories and each use case/requirement.| 13:38:14 i|to genera|scribenick: kaz| 13:38:23 i|get confu|scribenick: Ege| 13:38:40 q+ 13:38:56 q+ 13:39:12 mm: I will go over the use cases and give ids 13:39:18 ... and concrete names 13:40:03 s/ids/IDs/ 13:40:04 kaz: that is what I have been mentioning for a while. 13:40:05 ack k 13:40:12 mm: categories make it difficult 13:40:36 s/that is/agree :) That is exactly/ 13:40:58 s/ for a while// 13:41:05 rrsagent, draft minutes 13:41:06 I have made the request to generate https://www.w3.org/2023/10/19-wot-uc-minutes.html kaz 13:41:19 ... I will put uc before the requirement 13:43:48 ek: it would be good to have numbers in the id so that we can have future use cases with similar names 13:43:54 mm: but not visible in the title right? 13:44:03 ek: yes. Just to future proof 13:45:23 s/ id / ID / 13:45:40 q+ 13:45:48 mm: The id should be consistent with the title 13:45:56 ack e 13:46:15 kaz: clarifying the notation for id is nice. 13:46:29 ... if two use cases are similar, they can be categorized 13:46:32 ... or even merged 13:47:34 mm: categories are not good 13:48:01 kaz: we can maybe merge use cases that are similar, like a typical use case 13:48:13 mm: I do not want to change the submitted use cases, since they are submitted people 13:49:07 kaz: maybe old and new use cases need to exist 13:49:44 q+ 13:49:55 mm: use cases should be concrete, there should be users 13:50:27 ack k 13:51:57 s/maybe old and new use cases need to exist/In that case, maybe we need to have two bigger sections, one for the new use cases and another for the old use cases./ 13:53:13 ek: I have one "radical" idea which is to create a new document and transfer each use case that is fit to our new template one by one 13:53:36 mm: that is indeed a lot of work and it should happen in one go 13:54:08 s/we can maybe merge use cases that are similar, like a typical use case/If we want to avoid using categories, maybe we need to merge all the similar use cases as a typical use case with several variations./ 13:54:16 ack k 13:54:26 rrsagent, draft minutes 13:54:27 I have made the request to generate https://www.w3.org/2023/10/19-wot-uc-minutes.html kaz 13:54:34 ack e 13:56:58 -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2023-09-tpac/2023-09-14-WoT-TPAC-UseCases-McCool.pdf McCool's slides on Use Case work 13:57:09 q+ 13:57:20 ek: I think we should have a gate/check before moving to a work item 13:57:39 mm: there can be also open requirements that are not being worked on 13:57:56 ek: yes like 3 states, done, open or worked on as part of a work item 13:59:28 kaz: what are the next steps? 13:59:41 mm: we can further discuss in the next discovery call 13:59:56 ... and have a PR to merge by next use cases call 14:00:19 s/can further discuss in/can have further discussion during/ 14:00:30 rrsagent, draft minutes 14:00:31 I have made the request to generate https://www.w3.org/2023/10/19-wot-uc-minutes.html kaz 16:05:06 Zakim has left #wot-uc