13:58:35 RRSAgent has joined #wot-td 13:58:39 logging to https://www.w3.org/2024/09/04-wot-td-irc 13:58:42 meeting: WoT-WG - TD-TF - Slot 1 13:59:13 chair: Koster 13:59:15 mjk has joined #wot-td 13:59:18 rerets+ Ege 13:59:43 present+ Kaz_Ashimura, Luca_Barba, Michael_Koster, Michael_McCool 14:00:55 Tomo has joined #wot-td 14:02:35 present+ Kunihiko_Toumura 14:02:36 present+ Tomoaki_Mizushima 14:05:18 scribenick; kaz 14:05:49 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#September_4%2C_2024 14:05:53 topic: Agenda 14:05:59 mjk: (goes through the agenda) 14:06:06 ... concentrate on two topic 14:06:15 ... TPAC and Use Cases 14:07:02 q+ 14:07:28 q- 14:07:32 topic: Minutes 14:07:43 -> https://www.w3.org/2024/08/07-wot-td-minutes.html Aug-7 14:07:55 mjk: minutes from the Wednesday meeting 14:08:06 ... (quick scan) 14:08:16 present+ Daniel_Peintner 14:08:27 rrsagent, make log public 14:08:33 rrsagent, draft minutes 14:08:34 I have made the request to generate https://www.w3.org/2024/09/04-wot-td-minutes.html kaz 14:10:36 approved 14:10:44 -> https://www.w3.org/2024/08/08-wot-td-minutes.html Aug-8 14:12:00 approved 14:12:16 topic: Use Case process 14:12:37 mm: basically, we had the use cases call this morning 14:12:53 ... Ege's proposed simpler template was approved 14:13:08 ... Daniel mentioned some feedback to be applied 14:13:21 dape has joined #wot-td 14:13:22 ... we should give a week to Daniel to propose updates 14:13:30 q+ 14:13:35 ... next thing is organizing requirements 14:13:36 q? 14:13:57 -> https://github.com/w3c/wot-usecases/blob/main/.github/ISSUE_TEMPLATE/use-case-template.yml new use case template 14:14:13 dape: it's Jan and myself who tried the simpler use case template 14:14:22 mm: ok 14:14:33 q+ 14:14:36 ack d 14:15:01 ... why don't you and Jan create a PR? 14:15:04 https://github.com/w3c/wot-thing-description/issues/2039#issuecomment-2275330078 14:15:27 dape: my commen in an issue as above 14:15:40 q? 14:16:41 mm: maybe you should create an Issue for UC also 14:17:42 -> https://github.com/w3c/wot-thing-description/issues/2039#issuecomment-2275330078 wot-thing-description Issue 2039 - Using the New Use Case Template and Gathering Experience 14:17:45 q+ 14:18:08 kaz: in that case, what to be done? 14:18:56 ... will the UC TF look into the TD issue 2039 directly? 14:18:58 mm: yes 14:19:33 ... then look into backlogs from TD repo for use cases and requirements 14:19:55 ... may or may not include the YAML template 14:20:24 ... maybe the features could be dealt with by multiple use cases 14:21:17 ... would say if we have some requirements process, create use cases and let the UC TF know 14:21:35 ... please point us to the issue 14:22:12 ... regarding requirements, don't think we need to handle functional requirements vs technical requirements at the moment 14:22:25 ... requirements could be very simple 14:22:42 ... need to start to think about requirements 14:22:49 ... could start with one-liner 14:22:59 ... given users need certain function 14:23:19 ... if you have a different idea, that's fine and please create an issue 14:23:26 s/issue/issue about your idea/ 14:23:39 ... next week, let's walk through the draft 14:23:43 mjk: ok 14:23:44 q? 14:23:48 ack k 14:24:03 mm: any requirements written down by the TD TF? 14:24:11 q+ 14:24:25 ... would capture use story 14:24:51 q- 14:24:59 kaz: no concrete discussion about that yet 14:25:16 ... just wanted to start use case extraction based on the existing TD issues 14:25:48 ... so let's think about our basic process first 14:26:03 mm: Yeah 14:26:44 McCool has joined #wot-td 14:26:48 https://github.com/w3c/wot-usecases/labels/Requirement%20Extraction 14:27:04 ... there is one label saying "Requirement Extraction" 14:27:16 ... on the wot-usecases repo 14:27:24 s/repo/repo as above/ 14:27:49 https://github.com/w3c/wot-usecases/issues/301 for requirements process feedback 14:29:34 kaz: and the details about the UC/Req process to be done during the UC call next week. right? 14:29:37 mm: right 14:29:52 ... will generate some draft for that purpose 14:30:02 ... discussion during TPAC also 14:30:17 ... need to justify all the features 14:30:36 mjk: makes sense 14:30:53 ... any comments/questions? 14:30:55 (none) 14:31:02 topic: TPAC planning 14:31:29 mjk: talked earlier during the main call about the TD slot at TPAC 14:31:53 ... regular WoT track and breakouts 14:32:04 subtopic: Breakouts 14:33:18 -> https://github.com/w3c/tpac2024-breakouts/issues/23 tpac2024-breakouts issue 23 - One Year Update: Using LinkML in Web of Things Specifications 14:33:30 mjk: a session about LinkML usage 14:33:39 ... do we need to refine this further? 14:33:44 ... ok for now? 14:33:55 q? 14:33:56 q+ 14:34:22 q- 14:35:06 kaz: maybe we should double check Ege/Mahda about if they want to mention not only LinkML but also the other part of the WoT toolchain in general 14:35:16 mjk: might have impact to the title 14:35:18 kaz: right 14:35:28 ... so should be confirmed 14:36:08 mjk: Ian Jacobs is handling the breakouts 14:36:12 kaz: right 14:36:19 mjk: any other comments? 14:36:21 (none) 14:36:47 -> https://github.com/w3c/tpac2024-breakouts/issues/24 tpac2024-breakouts issue 24 - Registries for W3C Specifications 14:36:55 mjk: this is about registry 14:37:46 kaz: IRC channel name might be too long :) 14:38:54 ... another session about "Registry" uses #webcomponents 14:39:18 ... so maybe we could simply use "#registries" might be ok 14:39:24 mjk: ok 14:39:42 ... (gives a comment on the GitHub issue) 14:40:13 ... what about conflicts 14:42:11 kaz: will mention we'd avoid conflicts with WoT-related proposals within my Issue on Smart Cities 14:42:21 mjk: maybe we might want to suggest "WoT Track" 14:42:26 kaz: yeah 14:42:49 ... can mention that too 14:43:33 ... don't think we need to update all the issues one by one 14:44:46 mjk: anything more for today? 14:45:14 kaz: maybe we could skim the topics for the TD slot during TPAC. right? 14:45:19 mjk: right 14:45:31 subtopic: TPAC TD agenda items 14:46:27 kaz: maybe the agenda topics there on the TD agenda wiki might be the candidates 14:46:30 mjk: ok 14:46:46 ... note we just have one hour for TD during TPAC 14:47:06 ... we need to think about our priority for TPAC meeting 14:48:14 s/candidates/candidates, i.e., Toolchain, Reusable connection, Project/Backlog, Registry, Binding vs Profile, Resource management 14:48:41 mjk: (looks at the Backlog section of the agenda wiki) 14:49:03 i/mjk/mm: use case extraction also/ 14:49:20 ... "7. Reviews of the individual bindings to extract use cases" 14:49:55 mm: note that we'll have OPC liaison separately 14:50:05 ... who's doing what 14:50:27 ... 1. give updates to the group 14:50:31 ... 2. TD discussion 14:50:33 ... separately 14:51:49 -> https://www.w3.org/WoT/IG/wiki/Wiki_for_F2F_2024_planning#Liaisons TPAC WoT wiki - Day 2 - Liaisons section 14:51:59 q+ 14:52:34 q- 14:53:01 mjk: HTTP3 connection might be of interest 14:54:42 kaz: at least we should add "HTTP3" or "QUIC" to the list of missing protocols 14:55:36 ... given the relationship with the liaison topics, it might be better to put the TD session right after the Liaisons session at TPAC? 14:55:45 mm: makes sense 14:55:59 -> https://www.w3.org/WoT/IG/wiki/Wiki_for_F2F_2024_planning#Thing_Descriptions_and_Binding TD session at TPAC 14:56:35 mm: btw, it would take 5mins or so for meeting organization at the beginning of the meeting each day 14:56:43 mjk: will add that change 14:57:00 ... any more discussion about TPAC for today? 14:57:16 (none) 14:57:28 topic: AOB 14:57:34 q+ 14:57:45 mjk: no meeting tomorrow or Thursday next week 14:57:49 ack d 14:58:02 dape: who to update the W3C Calendar? 14:58:07 kaz: will do 14:58:12 [adjourned] 14:58:17 rrsagent, draft minutes 14:58:18 I have made the request to generate https://www.w3.org/2024/09/04-wot-td-minutes.html kaz 17:07:21 Zakim has left #wot-td