12:54:03 RRSAgent has joined #wot-td 12:54:08 logging to https://www.w3.org/2025/04/24-wot-td-irc 12:54:16 meeting: WoT-WG - TD-TF - Slot 2 12:54:21 rrsagent, make log public 12:54:25 rrsagent, draft minutes 12:54:26 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:00:28 present+ Kaz_Ashimura, Ege_Korkan 13:02:57 present+ Kunihiko_Toumura, Michael_Koster, Tomoaki_Mizushima 13:03:25 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#April_23-24%2C_2025 13:03:28 rrsagent, draft minutes 13:03:30 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:05:54 q+ 13:06:28 q- 13:09:19 scribenick: EgeKorkan 13:10:14 topic: Wrap up on Issue 143 13:10:18 https://github.com/w3c/wot-binding-templates/issues/143 13:10:35 ek: we talked about this and wrote all the concepts that we are targeting 13:11:04 https://github.com/w3c/wot-binding-templates/issues/143#issuecomment-2824603550 is the results of yesterday's discussions 13:11:26 s|https://github.com/w3c/wot-binding-templates/issues/143|-> https://github.com/w3c/wot-binding-templates/issues/143 Issue 143 - "Protocol Binding" vs. "Binding Template" 13:11:33 rrsagent, draft minutes 13:11:35 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:11:48 ... we don't need to agree on the name as we can change the repository name easily 13:12:15 mjk has joined #wot-td 13:12:26 ... we can decide on the concrete wording later on. 13:12:33 q? 13:12:51 ek: forgot to mention but we have no TD call for two weeks 13:13:21 topic: Moving Information to the New Repository 13:13:33 subtopic: requirements 13:13:35 https://github.com/w3c/wot-binding-templates-registry/pull/1 13:13:54 ek: we are basically copying the information from the binding templates here 13:14:11 q+ 13:15:13 q- 13:15:28 proposal: For discussion around the binding registry, we will use https://github.com/w3c/wot-binding-templates-registry repository 13:16:14 proposal: For discussion around the binding registry, we will use https://github.com/w3c/wot-binding-templates-registry repository. However, the name of the repository is subject to change based on the results of the discussions at https://github.com/w3c/wot-binding-templates/issues/143 13:16:51 resolution: For discussion around the binding registry, we will use https://github.com/w3c/wot-binding-templates-registry repository. However, the name of the repository is subject to change based on the results of the discussions at https://github.com/w3c/wot-binding-templates/issues/143 13:17:08 ek: then we have a resolution. but I will send an email 13:17:16 cris has joined #wot-td 13:17:26 ... also no objections to merging this PR? 13:17:39 chair: Ege, Koster 13:17:41 rrsagent, draft minutes 13:17:42 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:18:26 i|proposal:|@@@ the first proposal to be removed| 13:18:36 present+ Cristiano_Aguzzi 13:18:40 rrsagent, draft minutes 13:18:41 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:19:34 ek: any objections to moving the related issues as well? 13:19:43 ... basically all the issues with the tag at https://github.com/w3c/wot-binding-templates/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22registry%20mechanism%22 13:20:30 ... if someone goes to the old link, they should get redirected 13:21:58 q? 13:22:02 ... we don't have any leftover issues regarding the registry mechanism in the binding-templates repository 13:23:21 topic: Use Case Process 13:23:39 ... we aim to have documents of the form https://github.com/w3c/wot-thing-description/tree/main/proposals/initial-connection 13:24:03 ek: that way we know why a certain was needed 13:24:16 i|we aim|subtopic: Reusable Connection| 13:24:18 rrsagent, draft minutes 13:24:20 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:25:14 ek: we should not see this as a bureaucratic step but as a way to align before writing spec documents 13:26:11 ek: we can write what the user needs to fullfil, the needs of users in form of requirements 13:26:44 ek: in this example, we also have description about the concrete feature 13:26:54 q+ 13:28:00 ek: we have a document which can be used as a reference 13:29:05 kaz: we should note that this feature is not only useful for agriculture 13:29:46 ... also extending the use case with the requiremeent of usability would be nice 13:30:08 ek: we can link to more use cases for sure 13:30:31 ... however I think the use cases should stay generic a bit 13:31:12 kaz: TD TF should describe in which part of the use case this initial connection feature would be useful 13:31:49 ek: so you mean we should explain why there is a link between a user story and use case 13:32:48 q? 13:32:52 ack k 13:34:11 ek: I have opened an issue for this in the use case repo 13:34:17 https://github.com/w3c/wot-usecases/issues/358 13:34:44 ek: any questions on the goal we have? 13:35:20 s|https://github.com/w3c/wot-usecases/issues/358|-> https://github.com/w3c/wot-usecases/issues/358 UC Issue 358 - User Story relation to the Use Case| 13:35:24 rrsagent, draft minutes 13:35:25 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:37:20 ek: the first thing is to write a user story, which is simple to do 13:37:35 ... you should basically write one sentence and link to use case that has domain information 13:37:55 ek: I want to show an example 13:39:21 -> https://github.com/w3c/wot-usecases/issues/357 UC Issue 357 - Relevant Payload Selection in (JSON) Payloads 13:42:34 q+ 13:42:59 ek: (presents the content of the user story) 13:43:30 s/story/story within the UC Issue 357/ 13:44:07 ca: the use case is clear. there might be a way that people were using existing solutions. For example, you can undescribe the payload 13:44:32 ... I am wondering, I can propose a solution on this thread 13:46:04 q+ 13:46:25 ek: for existing feature in our specs, we should write here 13:46:44 ... in the final document, we should collect existing solutions from other specs. see https://github.com/w3c/wot-thing-description/blob/main/planning/work-items/analysis/analysis-data-mapping.md#existing-solutions 13:46:59 ... however, how to collect it in the beginning when the user story is submitted, I don't know 13:48:02 kaz: I agree with Cris. The whole process needs to be clear 13:48:15 ek: we should make a proposal 13:48:27 s/ek:/kaz: 13:50:18 ek: we know the first step, the last step but the path between is not clear 13:50:26 s/proposal/proposal to the next main call./ 13:50:29 rrsagent, draft minutes 13:50:30 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:51:03 ek: we need to also decide on prioritization 13:51:46 q? 13:51:49 ack c 13:54:44 ek: right now we have a mixed process. We have a charter and an idea of what we want to do 13:55:05 kaz: the process can be bidirectional. We can write requirements and use cases for the features we are building 13:55:39 ... we should discuss this in the main call 13:56:23 ack k 13:57:08 rrsagent, draft minutes 13:57:09 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 13:59:44 subtopic: Manageable Affordance 14:00:04 -> https://github.com/w3c/wot-thing-description/pull/2096 TD PR 2096 - Manageable Affordances Analysis 14:00:25 +1 14:00:34 q+ 14:00:35 ek: I am putting all information into one place first 14:01:07 kaz: so we work on the potential user scenario right? 14:01:09 ek: yes 14:01:18 ... we can merge it to have a place to work on this feature 14:01:54 ack k 14:02:10 ek: AOB? 14:02:10 ek: Adjourned 14:02:42 rrsagent, draft minutes 14:02:43 I have made the request to generate https://www.w3.org/2025/04/24-wot-td-minutes.html kaz 14:03:45 EgeKorka_ has joined #wot-td 14:58:56 zkis has joined #wot-td 16:29:24 Zakim has left #wot-td