14:01:10 RRSAgent has joined #wot-td 14:01:14 logging to https://www.w3.org/2024/11/07-wot-td-irc 14:01:20 meeting: WoT-WG - TD-TF - Slot 2 14:01:27 EgeKorkan has joined #wot-td 14:01:47 present+ Kaz_Ashimura, Ege_Korkan, Mahda_Noura, Kunihiko_Toumura 14:02:21 present+ Michael_Koster 14:03:43 rrsagent, make log public 14:03:46 rrsagent, draft minutes 14:03:47 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html kaz 14:03:54 present+ Michael_McCool 14:04:06 chair: Ege 14:04:09 McCool has joined #wot-td 14:04:33 EgeKorkan has joined #wot-td 14:05:07 luca_barbato has joined #wot-td 14:05:15 Y 14:05:17 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#November_6-7%2C_2024 14:05:45 rrsagent, draft minutes 14:05:46 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html kaz 14:05:52 present+ Tomoaki_Mizushima 14:05:53 rrsagent, draft minutes 14:05:54 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html kaz 14:06:09 s/Y// 14:06:11 rrsagent, draft minutes 14:06:12 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html kaz 14:06:25 scribenick: EgeKorkan 14:06:49 topic: Minutes 14:06:55 -> https://www.w3.org/2024/10/31-wot-td-minutes.html Oct-31 14:07:30 present+ Luca_Barbato 14:08:06 ek: anything to change? 14:08:14 ... minutes are approved 14:08:46 mjk has joined #wot-td 14:09:13 topic: use case discussion 14:09:37 https://github.com/w3c/wot-thing-description/pull/2053#issuecomment-2459671352 14:10:24 ege: the submitter writes the user story 14:10:34 i|the sub|scribenick: mjk| 14:11:29 ... we decided to keep who, what, and why as separate line items in the form 14:12:34 i|the submitter|-> https://github.com/w3c/wot-thing-description/pull/2053/files changes 14:12:37 ... We probably have enough use cases to justify the planned work 14:12:40 rrsagent, draft minutes 14:12:41 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html kaz 14:14:36 ... we can link features to use cases and stories 14:14:57 i|2459|-> https://github.com/w3c/wot-thing-description/pull/2053 PR 2053 - User Stories in Work Item Descriptions| 14:15:07 mm: we could use a table to associate features with use cases 14:15:33 ... we could maintain links in one direction and use tables for the reverse direction 14:15:40 s|https://github.com/w3c/wot-thing-description/pull/2053#issuecomment-2459671352|-> https://github.com/w3c/wot-thing-description/pull/2053#issuecomment-2459671352 Discussion by McCool and Ege| 14:15:44 rrsagent, draft minutes 14:15:45 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html kaz 14:16:10 ege: we need to also capture who is involved, sometimes called "stakeholders" 14:16:20 q+ 14:16:35 ... 4 categories of stakeholder 14:17:17 ... submitter, spec writer, implementer, and impacted 14:18:18 mm: there are other stakeholders like device installer 14:19:22 ... these categories are new definitions for roles 14:20:30 ... we need to consolidate the definitions in the UCR document 14:21:30 ... the different documents we publish have their own stakeholder definitions 14:21:48 q? 14:21:50 q+ 14:21:50 ack m 14:22:18 q+ 14:22:50 kaz: do we want to get new use cases from the stakeholders? Who are the priority stakeholders? 14:23:16 ... industry liaison is a priority 14:23:57 mm: we can sort by category for priority as a separate step from identifying stakeholders 14:24:13 kaz: we don't need a lot of details 14:24:31 q? 14:24:33 ack k 14:24:34 ack m 14:25:02 ege: we need this for the work items we have 14:25:05 q+ 14:25:44 mm: we need to identify negative vs. positive impacts 14:27:53 q? 14:27:53 ack m 14:27:54 ege: can we requite the user stories in who, what, why format? 14:28:03 mm: it seems clear enough 14:28:26 mm: each are a line item 14:28:37 +1 14:28:46 proposal: User Stories should be written as a set of 3 items, the total being a single sentence if items were put together 14:28:48 ... written as if it is part of a sentence 14:28:54 q? 14:28:59 q+ 14:29:32 mm: going to create a draft PR with examples 14:29:34 +1 14:30:59 ... this is mostly process documentation rather than spec content 14:31:19 q+ 14:31:30 ack m 14:31:33 ack m 14:32:54 mahda: it seems easier to write a user story than who, what, why and may not be equivalent 14:33:32 mm: the intention is not to have different meanings 14:34:01 ege: don't understand the issue 14:34:35 mm: would rather write sentences than separate expressions 14:34:44 s/mm/mahda 14:35:07 mm: you can write the sentence and then pull out the expressions 14:35:47 resolution: User Stories should be written as a set of 3 items, the total being a single sentence if items were put together 14:35:59 ege: no objections to the proposal 14:36:45 ege: does anyone object to the stakeholder definitions? 14:37:00 proposal: We should identify process stakeholder for each user story submission. See PR 2053 for the concrete definitions 14:37:23 resolution: We should identify process stakeholder for each user story submission. See PR 2053 for the concrete definitions 14:37:35 ... no objections, approved 14:38:23 [ submitter, spec writer, implementation volunteer, impacted people ] 14:38:45 subtopic: Example review 14:39:21 ege: (walks through the connection example) 14:40:19 q+ 14:41:12 q- 14:41:55 q+ 14:42:15 ege: there should be links from the form to the defined use cases 14:42:25 mm: there can be more than one use case 14:42:25 JKRhb has joined #wot-td 14:43:01 ... we should re-use the categories we have and avoid creating new ones 14:43:27 s/connection/Reusable Connection 14:43:48 q? 14:43:53 ack m 14:45:30 rrsagent, draft minutes 14:45:32 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html kaz 14:45:58 present+ Jan_Romann 14:46:05 ege: we may not always get a comprehensive writeup with a submission 14:46:07 q? 14:46:41 ege: the example contains everything that might be needed in a submission 14:48:02 ... are there any comments on the PR? 14:48:33 s/PR/PR #2053 14:48:44 rrsagent, draft minutes 14:48:46 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html JKRhb 14:49:14 ... any opinions? 14:49:43 OK, we will merge the PR 14:49:59 s/OK/ege: OK 14:50:01 q+ 14:50:07 ... what is the next step? 14:50:42 mm: we need to decide locations for the documents and linking, and the table we discussed earlier 14:51:28 ... will create a PR and send the link 14:51:31 q? 14:52:02 kaz: let's merge this PR and handle the UCR note separately 14:52:46 mm: I'll create a PR and we can review in the Use Case context 14:53:11 kaz: we need to clarify what will be done in the TD call and what is in the scope of the UC TF 14:53:29 mm: the specific user stories are TD TF scope 14:54:26 ege: we would create tracking for the TD issues 14:55:13 mm: yes, you can track them and submit from the TD TF 14:55:51 ... we generally won't accept input from outside the WoT group 14:57:07 kaz: we need to think about document structure 14:57:26 mm: there is a PR to add new sections and categories 14:57:51 mm: the scope is use case categories and requirements 14:58:26 kaz: we don't need to include the current document in the new document, but can link to it 14:58:59 s/link to it/link to it. the detailed discussion should be organized during the UC call./ 14:59:00 q 14:59:00 ege: we are almost at the hour, we can continue the discussion in the UC TF 14:59:03 ack k 14:59:03 q? 14:59:10 ... any other business? 14:59:21 ... adjourned 14:59:35 rrsagent, draft minutes 14:59:36 I have made the request to generate https://www.w3.org/2024/11/07-wot-td-minutes.html kaz