03:56:22 kaz has joined #wot-td 06:43:32 EgeKorkan has joined #wot-td 07:44:28 EgeKorkan has joined #wot-td 08:00:35 EgeKorkan has joined #wot-td 12:02:36 kaz has joined #wot-td 12:12:16 kaz has joined #wot-td 12:41:24 kaz has joined #wot-td 12:52:07 ktoumura has joined #wot-td 12:55:37 Zakim has joined #wot-td 12:55:51 rrsagent, bye 12:55:51 I see no action items 12:55:57 RRSAgent has joined #wot-td 12:55:57 logging to https://www.w3.org/2024/10/24-wot-td-irc 12:56:06 meeting: WoT-WG - TD-TF - Slot 2 12:56:13 present+ Kaz_Ashimura 12:56:28 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#October_23-24%2C_2024 12:58:45 present+ Michael_Koster 12:59:32 present+ Michael_McCool 12:59:44 mjk has joined #wot-td 13:04:38 present+ Kunihiko_Toumura 13:07:31 McCool has joined #wot-td 13:08:14 luca_barbato has joined #wot-td 13:08:21 IEEE SWEBOK: https://ieeecs-media.computer.org/media/education/swebok/swebok-v4.pdf - definition of "requirements" 13:08:26 present+ Luca_Barbato 13:08:38 i/IEEE/topic: Logistics/ 13:08:43 update to requirements presentation including a template: https://github.com/w3c/wot/blob/main/PRESENTATIONS/2024-09-tpac/2024-09-26-WoT-TPAC-Requirements-McCool.pptx 13:08:48 present+ Tomoaki_Mizushima 13:08:50 q+ 13:09:16 q- 13:09:16 Mizushima has joined #wot-td 13:11:06 scribenick: Luca_Barbato 13:11:18 scribenick: luca_barbato 13:11:46 topic: Agenda Review 13:12:00 mk: Today we want to focus on the Use Cases 13:12:10 i|Today|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#October_23-24%2C_2024 agenda for today| 13:12:25 rrsagent, make log public 13:12:30 rrsagent, draft minutes 13:12:31 I have made the request to generate https://www.w3.org/2024/10/24-wot-td-minutes.html kaz 13:12:38 topic: Meeting Minutes 13:12:46 regrets+ Ege 13:12:47 mk: We already reviewed them yesterday 13:12:57 topic: Use Cases 13:13:20 mk: First we'll have mm present 13:13:51 mm: I had a presentation at TPAC, I extended the presentation and uploaded it 13:14:09 -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2024-09-tpac/2024-09-26-WoT-TPAC-Requirements-McCool.pdf McCool's slides 13:14:40 s/uploaded/will upload/ 13:15:02 s/slides/slides for TPAC (to be updated)/ 13:15:40 i|Today|-> https://ieeecs-media.computer.org/media/education/swebok/swebok-v4.pdf IEEE SWEBOK (definition of "requirements") 13:15:49 rrsagent, draft minutes 13:15:51 I have made the request to generate https://www.w3.org/2024/10/24-wot-td-minutes.html kaz 13:16:08 mm: I added added the terminology from the IEEE 13:16:19 s/added added/added/ 13:17:02 present+ Daniel_Peintner 13:18:30 ... 13:21:20 q? 13:22:15 13:24:15 q+ 13:24:40 s/Template/Requirements Template/ 13:24:54 q- 13:25:05 q+ 13:25:12 q+ 13:25:13 mm: Comments 13:25:41 kaz: This is an initial proposal, do we want to do brainstorming on it? 13:26:07 mm: Yes, I'd try to collect the outcome in a PR or an Issue 13:27:05 13:27:54 q+ 13:28:29 q- 13:28:52 mm: We do not have enough people to make a decision, so I'm just preparing the PR 13:29:25 q+ 13:30:38 kaz: It is a bit odd editing wot-usecase from a wot-thing-description call 13:30:51 mm: I'm writing the PR as co-chair of the group 13:32:03 https://github.com/w3c/wot-usecases/pull/305 13:32:44 mm: The TD TF can create a db of user stories and link back to the use-cases 13:33:15 s|https://github.com/w3c/wot-usecases/pull/305|-> https://github.com/w3c/wot-usecases/pull/305 wot-usecases PR 305 - Create userstory-requirement.md (as an initial proposal)| 13:33:20 rrsagent, draft minutes 13:33:52 I have made the request to generate https://www.w3.org/2024/10/24-wot-td-minutes.html kaz 13:36:43 it is up to the TD TF to decide how to organize work items (e.g. PRs/issues/lists in an MD files/assertions) - end state should be an assertion, however (e.g. a feature in the TD specification) for "capabilities". For Use cases, if one does not exist, it should be created (keep it abstract; don't need a ton of implementation details in use case, 13:36:43 it should just state the purpose) and/or a category should be suggested (can be just in the user story, give a definition or link to at least one use case in the "details" section). 13:37:09 mm: I can put the above statements in a slide as well 13:37:23 mk: It starts to look like a workflow now 13:37:30 q+ 13:37:49 s/it should just state the purpose) and/or a category should be suggested (can be just in the user story, give a definition or link to at least one use case in the "details" section).// 13:38:02 s/in use case,/in use case, it should just state the purpose) and/or a category should be suggested (can be just in the user story, give a definition or link to at least one use case in the "details" section)./ 13:38:06 rrsagent, draft minutes 13:38:08 I have made the request to generate https://www.w3.org/2024/10/24-wot-td-minutes.html kaz 13:38:33 ack m 13:38:35 q? 13:38:44 q- 13:39:18 mk: It seems to me that the user-stories aren't fully created as use-cases 13:39:29 present+ Jan_Romann 13:40:14 mk: We have two templates: Requirements and Use Case 13:43:44 lu: Use Case and Requirements are input from outside, Categories is just an internal detail to sort them out 13:48:04 JKRhb has joined #wot-td 13:48:27 q? 13:48:48 rrsagent, please draft the minutes 13:48:49 I have made the request to generate https://www.w3.org/2024/10/24-wot-td-minutes.html JKRhb 13:49:45 lu: Both Use Case and User Stories, no matter who submits them would be good to have the same way to ingest (e.g. Forms) and they should have the same IPR rules since they end up in our repos one way or another 13:50:20 kaz: We can focus on the IPR later, better focus on the rest first 13:50:27 ack k 13:51:24 q? 13:52:03 s/We can focus on the IPR later/It seems to me that we're handling two levels of issues at once, (1) terminology of "requirements", "feature requests", etc., and (2) how to describe them based on additional templates. Given we have only 10 more mins, I'd suggest we focus on the first issue today/ 13:52:26 s/today/today, and talk about the templates and IPR issues later./ 13:52:38 s/, better focus on the rest first// 13:52:44 rrsagent, draft minutes 13:52:45 I have made the request to generate https://www.w3.org/2024/10/24-wot-td-minutes.html kaz 13:53:04 q? 13:53:06 q+ 13:53:53 q- 13:54:53 kaz: Do we have consensus on the following items? 13:56:43 s/on the following items/on the basic direction, e.g., need for clarifying terminology, workflow and templates/ 13:57:55 https://github.com/w3c/wot/blob/main/PRESENTATIONS/2024-10-24-WoT-Requirements-McCool.pdf 13:58:25 proposal: TD TF agrees on the need for clarifying the terminology (like "requirements" and "feature requests"), workflow and templates to describe them. 13:59:44 proposal: TD TF agrees on the need for clarifying the terminology (like "requirements"), workflow and templates to describe them. 14:00:52 [ we're out of time and continue the discussion next week. ] 14:01:06 [adjourned] 14:01:11 rrsagent, draft minutes 14:01:12 I have made the request to generate https://www.w3.org/2024/10/24-wot-td-minutes.html kaz 14:36:33 kaz has joined #wot-td 16:00:49 Zakim has left #wot-td