13:56:33 <RRSAgent> RRSAgent has joined #wot-td
13:56:38 <RRSAgent> logging to https://www.w3.org/2025/06/18-wot-td-irc
13:56:40 <kaz> meeting: WoT-WG - TD-TF - Slot 1
13:58:28 <kaz> present+ Kaz_Ashimura
13:58:35 <kaz> chair: Ege, Koster
13:58:56 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#June_18-19%2C_2025
14:00:22 <kaz> present+ Ege_Korkan
14:00:24 <mjk> mjk has joined #wot-td
14:00:59 <kaz> present+ Michael_Koster
14:02:07 <kaz> present+ Kunihiko_Toumura
14:02:12 <kaz> rrsagent, make log public
14:02:17 <kaz> rrsagent, draft minutes
14:02:18 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:03:17 <dape> dape has joined #wot-td
14:03:31 <kaz> present+ Cristiano_Aguzzi, Daniel_Peintner
14:03:33 <kaz> rrsagent, draft minutes
14:03:34 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:04:59 <kaz> regrets+ Mahda
14:05:05 <kaz> scribenick: kaz
14:05:20 <Mizushima> Mizushima has joined #wot-td
14:05:25 <kaz> topic: Agenda
14:05:39 <kaz> -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#June_18-19%2C_2025 Agenda for today
14:05:44 <kaz> ek: (goes through the agenda)
14:06:09 <kaz> topic: Minutes
14:06:20 <kaz> -> https://www.w3.org/2025/06/04-wot-td-minutes.html June-4
14:06:33 <kaz> present+ Tomoaki_Mizushima
14:06:39 <kaz> rrsagent, draft minutes
14:06:40 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:06:48 <kaz> approved
14:08:19 <mjk> q?
14:08:49 <kaz> q+
14:09:04 <luca_barbato> luca_barbato has joined #wot-td
14:10:20 <kaz> present+ Luca_Barbato
14:10:27 <kaz> rrsagent, draft minutes
14:10:28 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:10:51 <kaz> s/approved/approved (after fixing a typo)/
14:10:55 <kaz> rrsagent, draft minutes
14:10:56 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:11:02 <luca_barbato> scribenick: luca_barbato
14:11:34 <kaz> -> https://www.w3.org/2025/06/05-wot-td-minutes.html June-5
14:12:27 <kaz> scribenick: luca_barbato
14:12:47 <luca_barbato> ege: Any more remarks?
14:13:14 <kaz> none; approved
14:13:19 <kaz> topic: Quick schedule
14:13:24 <luca_barbato> ege: Who can join tomorrow?
14:13:34 <luca_barbato> ege: Tomorrow is a public holiday in Germany
14:13:40 <kaz> q+
14:13:51 <luca_barbato> <non Germans>: we can join
14:14:03 <kaz> q-
14:14:20 <luca_barbato> kaz: To be sure, since Ege is on holiday mjk will take over the lead?
14:14:25 <luca_barbato> mjk: yes
14:14:48 <luca_barbato> subtopic: Publication Schedule
14:15:06 <kaz> rrsagent, draft minutes
14:15:08 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:15:29 <kaz> s/subtopic:/topic:/
14:15:32 <kaz> rrsagent, draft minutes
14:15:34 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:15:40 <kaz> q+
14:16:12 <kaz> -> https://github.com/w3c/wot/blob/main/planning/wg-schedule.md wg-schedule.md
14:17:15 <luca_barbato> kaz: we discussed in main call the publication schedule
14:17:30 <luca_barbato> kaz: the main topic for the WG is TD and Binding
14:17:49 <luca_barbato> kaz: The initial proposal is to publish a first draft in September
14:18:17 <kaz> s/in Sep/by the end of Sep/
14:18:17 <luca_barbato> kaz: We need to update the schedule by the next TD meeting
14:19:03 <luca_barbato> ege: Basically our TF needs to fill most of the schedule
14:20:11 <luca_barbato> ege: we do not needs to fill everything during the first working draft
14:20:51 <kaz> s/the schedule by the next TD meeting/the wg-schedule.md for TD and Binding./
14:21:09 <kaz> s/We need to/We as the TD-TF need to/
14:21:12 <luca_barbato> ege: does anybody have other opinions?
14:21:15 <kaz> q/
14:21:16 <kaz> q-
14:21:20 <cris> cris has joined #wot-td
14:21:25 <kaz> s|q/||
14:22:09 <luca_barbato> ege: Is everybody fine in calling it TD 2.0 ?
14:22:14 <cris> q+
14:22:21 <luca_barbato> ege: do we have any objections or proposal?
14:22:51 <luca_barbato> cris: Do we have some implications regarding the name?
14:23:02 <luca_barbato> q+
14:23:20 <luca_barbato> ege: It would impact the urls
14:23:59 <kaz> q+
14:24:26 <luca_barbato> cris: if we use `next` we'd just have a deprecation notice for the final name?
14:24:39 <EgeKorkan> scribenick: EgeKorkan
14:24:53 <EgeKorkan> lb: I would keep on using versioning
14:25:10 <EgeKorkan> ... consensus is that the next version will be incompatible so 2.0 makes sense
14:25:31 <EgeKorkan> ... we already have the concept of draft, candidate rec, and rec
14:25:43 <EgeKorkan> ... I wouldn't spend much time, just go with 2.0
14:25:48 <kaz> ack cr
14:25:51 <EgeKorkan> ack l
14:25:52 <kaz> ack lu
14:26:23 <luca_barbato> kaz: I agree with lu, we basically already agreed on it during this charter period
14:26:45 <kaz> -> https://www.w3.org/2023/10/wot-wg-2023.html the Current WoT WG Charter
14:27:06 <kaz> i/I agree/scribenick: luca_barbato/
14:27:12 <luca_barbato> ege: I also thing TD 2.0 will be incompatible
14:27:26 <dape> q+
14:27:30 <kaz> ack k
14:28:11 <luca_barbato> dape: I do not mind 2.0, but I see CSS went with just CSS 3
14:28:14 <kaz> s/period/period. Note that the current Charter just says "Thing Description (Update)"./
14:28:15 <kaz> q+
14:28:36 <luca_barbato> q+
14:28:54 <EgeKorkan> ack d
14:28:55 <dape> ack dape
14:28:55 <luca_barbato> ege: Do we have opinions?
14:29:17 <luca_barbato> kaz: Keep in mind that CSS 3 means "level 3" and not version
14:30:02 <luca_barbato> dape: I see other specifications doing with single number
14:30:11 <luca_barbato> kaz: We already used 1.1
14:30:38 <luca_barbato> kaz: from my point of view anything is fine but it must not be 1.2
14:30:57 <EgeKorkan> q?
14:31:03 <EgeKorkan> ack k
14:31:03 <kaz> q-
14:31:42 <EgeKorkan> lb: I would stay consistent. We already have 11. Unless we have 10 major versions, we shouldn't have a problem
14:31:51 <kaz> -> https://www.w3.org/TR/wcag-3.0/ WCAG uses 3.0 for version 3 :)
14:32:39 <kaz> q?
14:32:45 <kaz> q+
14:33:08 <luca_barbato> kaz: Each working group has their own policy
14:33:33 <luca_barbato> kaz: we can keep 11, 20 as we like
14:33:47 <luca_barbato> ege: I'd go 2.0 since is more descriptive
14:35:04 <kaz> q?
14:35:06 <kaz> ack lu
14:35:07 <kaz> ack k
14:35:29 <kaz> kaz: note that we need to talk with PLH before FPWD publication about the URL
14:35:43 <kaz> s/note/scribenick: kaz/
14:35:49 <kaz> scribenick: luca_barbato
14:36:02 <kaz> rrsagent, draft minutes
14:36:03 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:36:14 <EgeKorkan> proposal: The TD TF agrees on working for FPWDs for TD (Update) and Binding Registry documents.
14:36:37 <kaz> i|I would stay con|scribenick: EgeKorkan|
14:36:38 <kaz> rrsagent, draft minutes
14:36:39 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:36:57 <EgeKorkan> proposal: The TD TF agrees on working for FPWDs for TD (Update) and Binding Registry documents within this charter period.
14:36:59 <kaz> i|Each working|scribenick: luca_barbato|
14:37:01 <kaz> rrsagent, draft minutes
14:37:02 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:37:08 <EgeKorkan> q?
14:37:15 <mjk> q?
14:37:15 <kaz> q+
14:37:24 <luca_barbato> ege: any objections?
14:38:01 <kaz> q-
14:39:41 <EgeKorkan> The TD TF agrees on working for First Public Working Draft for the TD (Update) document and the First Public Draft Registry for the Binding Registry document within this charter period.
14:40:07 <EgeKorkan> proposal: The TD TF agrees on working for First Public Working Draft for the TD (Update) document and the First Public Draft Registry for the Binding Registry document within this charter period.
14:40:20 <luca_barbato> ege: Any objections?
14:40:45 <EgeKorkan> resolution: The TD TF agrees on working for First Public Working Draft for the TD (Update) document and the First Public Draft Registry for the Binding Registry document within this charter period.
14:41:00 <EgeKorkan> proposal: The TD TF agrees on calling the update to the TD specification "Web of Things (WoT) Thing Description 2.0" with the shortname wot-thing-description-2.0
14:41:09 <luca_barbato> ege: Any remarks on the second one?
14:41:14 <EgeKorkan> q?
14:41:24 <EgeKorkan> resolution: The TD TF agrees on calling the update to the TD specification "Web of Things (WoT) Thing Description 2.0" with the shortname wot-thing-description-2.0
14:41:48 <kaz> q+
14:42:47 <kaz> -> https://www.w3.org/standards/history/webcodecs-video-frame-metadata-registry/ history of registry docs
14:42:48 <kaz> q-
14:44:07 <cris> q+
14:45:12 <luca_barbato> cris: Before listing the features, I guess we can list the new features and explain why we are going to 2.0
14:45:17 <luca_barbato> q+
14:45:52 <kaz> ack c
14:45:59 <EgeKorkan> lb: all of this would be great material for mastodon or long form blog posts
14:46:08 <EgeKorkan> ... we can blog more about such upcoming features
14:46:09 <kaz> i|all|scribenick: EgeKorkan|
14:46:17 <kaz> rrsagent, draft minutes
14:46:18 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:46:44 <EgeKorkan> ... on the other hand, we should try to pick just one feature and get implementation feedback on it. In a coordinated manner
14:47:46 <kaz> s/scribenick: kaz/note/
14:47:59 <kaz> i|we need to talk with PLH|scribenick: kaz|
14:48:08 <kaz> rrsagent, draft minutes
14:48:09 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:48:26 <EgeKorkan> ... so in a month get some results and say that multiple implementations work in an interoperable way
14:48:49 <EgeKorkan> ... it would be outreach too. 70% outreach, 30% spec work
14:48:56 <EgeKorkan> ... so we would not need to wait for a plugfest
14:49:16 <EgeKorkan> ... we should see if the implementations work
14:49:50 <luca_barbato> ege: it would be a good strategy in general and it was the original plugfest format
14:50:06 <luca_barbato> ege: with 4 plugfest per year
14:50:12 <kaz> i|it would be|scribenick: luca_barbato|
14:50:14 <kaz> rrsagent, draft minutes
14:50:15 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:50:33 <EgeKorkan> q?
14:50:34 <luca_barbato> ege: since we are more distributed it would be good to try as you suggest
14:50:56 <kaz> s/4 plugfest/4 plugfests/
14:52:34 <luca_barbato> cris: and all this work is blocked on the toolchain work
14:52:57 <kaz> rrsagent, draft minutes
14:52:58 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
14:53:14 <mjk> q?
14:53:21 <cris> q+
14:53:49 <luca_barbato> q+
14:53:54 <EgeKorkan> ack l
14:53:59 <EgeKorkan> q+ luca_barbato
14:54:14 <luca_barbato> cris: we could have a normative section to tell how to model a queue of actions
14:55:07 <luca_barbato> cris: queues for actions aren't that common though
15:00:09 <kaz> q?
15:00:14 <kaz> ack c
15:00:32 <kaz> q+
15:02:18 <luca_barbato> ege: Do we need to put more or that's already too much?
15:02:29 <luca_barbato> cris: it is good to have a list
15:02:32 <luca_barbato> q+
15:02:59 <kaz> ack lu
15:05:51 <kaz> ack k
15:06:01 <kaz> scribe+
15:06:35 <kaz> kaz: please think about which feature would take how long discussion. we should avoid working too complicated features.
15:06:46 <kaz> rrsagent, draft minutes
15:06:47 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz
15:07:10 <kaz> [adjourned]
15:07:12 <kaz> rrsagent, draft minutes
15:07:13 <RRSAgent> I have made the request to generate https://www.w3.org/2025/06/18-wot-td-minutes.html kaz