12:02:32 RRSAgent has joined #wot 12:02:36 logging to https://www.w3.org/2025/07/16-wot-irc 12:02:57 meeting: WoT-WG/IG 12:03:22 present+ Kaz_Ashimura, Michael_Koster, Michael_McCool, Kunihiko_Toumura, Sebastian_Kaebisch 12:03:24 chair: Koster 12:03:49 agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#16_July_2025 12:04:33 present+ Tomoaki_Mizushima 12:04:35 Mizushima has joined #wot 12:04:50 rrsagent, make log public 12:04:55 rrsagent, draft minutes 12:04:56 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 12:05:30 present+ Ege_Korkan 12:06:29 present+ Tetsushi_Matsuda 12:06:46 matsuda has joined #wot 12:06:59 rrsagent, draft minutes 12:07:01 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 12:07:22 EgeKorkan has joined #wot 12:07:43 scribenick: EgeKorkan 12:08:58 q+ 12:09:00 topic: new people 12:09:03 q- 12:09:14 mk: no new people at the moment 12:09:17 topic: Minutes 12:09:20 s/new people/Guests, New Members and IEs/ 12:09:34 -> https://www.w3.org/2025/07/09-wot-minutes.html July-9 12:10:07 mk: let's skim over the minutes 12:10:40 dape has joined #wot 12:10:42 mk: any remarks? 12:11:38 mk: minutes are approved 12:12:16 topic: TPAC2025 Planning 12:12:33 q? 12:12:39 q+ 12:13:05 mk: we need to plan the TPAC and Plugfest 12:13:12 q- 12:13:24 q+ 12:14:11 present+ Daniel_Peintner 12:14:38 kaz: please provide your availability for plugfest and tpac 12:14:43 mk: yes please everyone 12:14:53 sk: I have also invited OPCUA Binding WG in OPCF 12:14:55 q+ 12:15:03 s/OPCUA/OPC UA/ 12:15:07 sk: some can participate. possibly remote 12:15:16 mm: I would like to invite NGSI-LD as well 12:16:27 q? 12:16:29 ack s 12:16:30 ack k 12:16:36 kaz: They need to pay in all cases, so keep it in mind 12:16:42 ... very short participation might be ok 12:17:53 q+ 12:18:12 s/They need to pay in all cases, so keep it in mind/Basically, all the participants need to pay, so we need to clarify who to participate how/ 12:18:41 s/very short participation might be ok/if their participation is only one-hour or so, maybe we can negotiate, though/ 12:18:53 rrsagent, draft minutes 12:18:54 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 12:19:24 q+ 12:19:47 ack s 12:19:49 ack k 12:20:40 topic: Holiday and Unavailabilities 12:21:01 mk: kaz is not available on july 31. I will cancel the td call 12:22:32 mm: I will update the schedule for use cases 12:22:38 topic: New Charter 12:22:57 i/I will/topic: Publication schedule/ 12:23:43 -> https://www.w3.org/2023/10/wot-wg-2023.html WoT WG Charter 12:24:16 mk: we need to agree on what to do with the marketing and people who did not join the wg 12:24:23 q+ 12:24:24 -> https://www.w3.org/2024/04/wot-ig-2024.html WoT IG Charter 12:24:25 q+ 12:24:37 q+ 12:24:55 q+ 12:25:01 q- 12:26:43 ek: what would happen with the marketing resources on GitHub? 12:26:59 q+ 12:27:22 ... technically, we can remove the WoT IG, but don't want to lose any existing resources 12:27:48 mk: the biggest issue I imagine is some of the IG participants can't join the WG officially 12:27:56 ... but we can invite them to the WG calls if needed 12:28:07 i/what would/scribenick: kaz/ 12:28:20 q? 12:28:24 ... we can simplify our activities, I think 12:28:27 ack e 12:28:37 sk: Ege's concern is valid, I think 12:29:03 sk: valid points regarding infrastructure. Is it possible to continue the space? 12:29:13 i/valid/scribenick: EgeKorkan/ 12:29:24 sk: in my understanding, we can define our own rules for such kind of task forces like marketing and plugfest 12:31:04 sk: we can say that the CG acts like the old IG. Kaz can comment on that. We can have a closer collab with the CG 12:31:07 -> https://www.w3.org/2024/04/wot-ig-2024.html#scope WoT IG's scope 12:31:45 kaz: probably we need long discussion about this mechanism. We should clarify what we want to work on as a whole ig and wg together 12:32:56 q? 12:32:58 ack s 12:33:00 ack k 12:33:09 ... then we can discuss which group can do which work 12:33:20 mm: I propose merging the work of IG into the WG space 12:34:08 dezell has joined #wot 12:34:17 present+ David_Ezell 12:34:21 q? 12:34:28 ... and then decide how to split the work where 12:34:29 ack m 12:34:33 ... to not leave anything hanging 12:34:37 rrsagent, draft minutes 12:34:38 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 12:34:44 mk: IG charter has time left 12:35:11 q+ 12:36:11 mk: There will be time in the IG charter which overlaps with WG 12:36:13 q+ 12:36:21 kaz: I will talk with PLH about the process 12:37:25 s/process/concrete process/ 12:37:46 mk: should we make a resolution 12:37:50 ack k 12:37:57 kaz: we can agree on the general direction 12:38:11 q+ 12:38:29 ack dape 12:38:55 dp: what about moving the IG topics to the CG? 12:39:00 ack k 12:39:02 q? 12:39:36 q+ 12:39:51 q+ 12:40:27 kaz: both directions can work potentially 12:40:34 ack k 12:40:35 mm: a draft charter can be done 12:40:42 kaz: I can help the chairs for this one 12:41:32 q+ 12:41:49 Proposal: We would like to proceed with merging the WoT Interest Group work into the WoT Working Group. NExt steps are to coordinate with W3M asnd create a plan for merging the activities 12:41:54 EgeKorka_ has joined #wot 12:42:10 scribenick: EgeKorka_ 12:42:18 sk: I am fine with this direction 12:42:18 ack s 12:42:20 ack k 12:42:49 s/NExt/Next/ 12:42:53 s/asnd/and/ 12:42:56 Resolution: We would like to proceed with merging the WoT Interest Group work into the WoT Working Group. Next steps are to coordinate with W3M and create a plan for merging the activities 12:43:13 EgeKork__ has joined #wot 12:43:54 mk: ok we have a resolution for the basic direction 12:43:55 rrsagent, draft minutes 12:43:57 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 12:44:22 i|ok we|scribenick: EgeKork__| 12:44:24 rrsagent, draft minutes 12:44:25 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 12:44:33 topic: Use Case Discussion 12:44:49 mm: I need 1 more hour of work on it. Then it will be in a state ready for the note 12:45:00 mm: the question is about the process 12:45:13 q+ 12:46:49 mm: Current document has too much stuff for someone to find the interesting stuff 12:47:12 ... the intention was always to move the interesting parts to the TFs and for this document to act as a public facing summary 12:48:01 q? 12:48:17 ... also there are some use cases and stories that do not fit one TF 12:48:25 kaz: I agree that we need to think about the process 12:49:11 scribenick: EgeKork__ 12:50:18 EgeKorkan has joined #wot 12:50:36 q? 12:51:40 kaz: which version of the template should be used should be clarified. Also it should be detached from specwork 12:51:50 mm: there are no different versions 12:52:20 kaz: can you clarify what to use? 12:53:11 mm: I will show 12:53:25 s/use?/use? Also we should handle (1) the template on GitHub for spec work and (2) the UCR document as a Note separately./ 12:53:28 rrsagent, draft minutes 12:53:29 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 12:53:58 i|which version of|scribenick: EgeKorkan| 12:53:59 rrsagent, draft minutes 12:54:00 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 12:54:57 EgeKorka_ has joined #wot 12:55:38 mm: (shows the github issues and the templates) 12:55:49 q+ 12:55:53 mm: (shows how it looks like in the document) 12:56:45 EgeKork__ has joined #wot 12:57:59 q? 12:58:42 mm: here are the definitions we use. different people have different definitions attached to these words 12:59:14 -> https://github.com/w3c/wot-usecases/blob/main/README.md wot-usecases/README.md 12:59:29 ... I think we have enough use caes, which are more generic stuff. User stories drive the features as they are written from the point of view of a developer asking for a feature 13:00:17 s/use caes/use cases/ 13:01:23 ack k 13:01:30 rrsagent, draft minutes 13:01:31 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 13:01:43 q+ 13:02:40 q+ 13:05:12 kaz: It would be good to use the same terms 13:05:16 q- 13:05:33 rrsagent, draft minutes 13:05:34 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 13:06:01 i|shows the github|scribenick: EgeKorka_| 13:06:02 rrsagent, draft minutes 13:06:03 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 13:06:23 i|here are the defi|scribenick: EgeKork__| 13:06:25 q? 13:06:26 rrsagent, draft minutes 13:06:27 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 13:07:47 mk: adjourning unless there are no other comments 13:07:55 mk: no call in the next hour 13:08:53 i|shows the github issues|-> https://github.com/w3c/wot-usecases/issues/new/choose wot-usecases repo's Issue templates| 13:09:47 i|shows how it looks|-> https://w3c.github.io/wot-usecases/ WoT Use Cases and Requirements Editor's Draft| 13:11:22 i|I think we have enough|kaz: tx for your description. now we're getting information about the templates, and we should think about the process a bit clear. there is some initial proposed process on README.md above, but we still need to clarify the actual process. 13:11:25 rrsagent, draft minutes 13:11:26 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 13:11:52 i|tx for|scribenick: kaz| 13:12:08 i|I think we have enough|scribenick: EgeKork__| 13:12:10 rrsagent, draft minutes 13:12:11 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 13:14:16 s/It would be good to use the same terms/as you know, the TD TF has started to define concrete process for UCR definition on the TF side, so we as the whole group should clarify which parts to be handled by the UC TF and which other parts to be handled by the TD TF. 13:14:17 rrsagent, draft minutes 13:14:19 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 13:14:28 [adjourned] 13:14:29 rrsagent, draft minutes 13:14:30 I have made the request to generate https://www.w3.org/2025/07/16-wot-minutes.html kaz 13:20:17 kaz has joined #wot 15:09:27 TallTed has joined #wot 15:36:13 Zakim has left #wot 16:00:42 bigbluehat has joined #wot