14:01:24 <RRSAgent> RRSAgent has joined #wot-td
14:01:28 <RRSAgent> logging to https://www.w3.org/2024/03/07-wot-td-irc
14:01:36 <kaz> meeting: WoT-WG - TD-TF - Slot 2
14:01:41 <Ege> I am coming in a minute, sorry
14:01:45 <ktoumura> ktoumura has joined #wot-td
14:01:48 <kaz> present+ Kaz_Ashimura, Jan_Romann, Kunihiko_Toumura
14:02:01 <kaz> s/I am coming in a minute, sorry//
14:02:06 <kaz> rrsagent, make log public
14:02:10 <kaz> rrsagent, draft minutes
14:02:11 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/07-wot-td-minutes.html kaz
14:02:18 <Tomo> Tomo has joined #wot-td
14:03:46 <Ege> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf
14:05:50 <mahda-noura> mahda-noura has joined #wot-td
14:06:30 <kaz> present+ Ege_Korkan, Mahda_Noura, Tomoaki_Mizushima
14:06:36 <kaz> rrsagent, draft minutes
14:06:38 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/07-wot-td-minutes.html kaz
14:07:24 <mahda-noura> present+ Mahda_Noura
14:07:27 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#March_06_and_07%2C_2024
14:08:44 <kaz> topic: Minutes
14:08:53 <kaz> -> https://www.w3.org/2024/02/29-wot-td-minutes.html Feb-29
14:09:00 <kaz> ek: looks good
14:09:07 <kaz> ... (goes through the minutes)
14:09:26 <JKRhb> q+
14:09:33 <kaz> ack j
14:09:44 <kaz> jr: one IRC command remaining
14:11:10 <cris_> cris_ has joined #wot-td
14:11:50 <kaz> kaz: fixed
14:11:59 <kaz> approved
14:12:26 <Ege> https://www.w3.org/2024/03/breakouts-day-2024/
14:12:35 <kaz> i|https|topic: Breakouts|
14:13:06 <Ege> https://www.w3.org/events/meetings/fb7b6d9f-fc2f-456f-9fff-3a516f3ec7ab/
14:13:10 <Ege> https://www.w3.org/events/meetings/7c1b6bcd-9ee1-4570-ba4d-9ccad717e78f/
14:13:46 <kaz> i|fb|Schemata session at 13 UTC|
14:13:47 <Ege> q?
14:13:51 <kaz> s/13/14/
14:14:06 <kaz> i|7c|Registries session at 13 UTC|
14:14:11 <kaz> q+
14:15:06 <kaz> kaz: if you want to invite non-Members to the sessions, please let us know
14:15:17 <kaz> ack k
14:15:52 <kaz> present+ Cristiano_Aguzzi
14:16:05 <kaz> topic: Binding
14:17:13 <kaz> subtopic: Registry
14:17:39 <kaz> -> https://github.com/w3c/wot/blob/main/registry-analysis/Readme.md registry-analysis/Readme.md
14:19:27 <kaz> present+ Michael_Koster
14:19:39 <kaz> ek: (goes through the document)
14:19:47 <kaz> ... some requirements here
14:20:11 <kaz> ... we'll have some more discussion during the breakout session next Tuesday
14:21:05 <mjk> mjk has joined #wot-td
14:21:11 <mjk> q?
14:21:16 <kaz> q+
14:22:01 <kaz> kaz: thanks for your hard work
14:22:28 <kaz> ... as the next step, we should clarify what to be required for what purpose a bit more
14:22:46 <kaz> ... data format, content, procedure, who to submit what, etc.
14:23:13 <kaz> ack k
14:23:47 <kaz> ek: (adds some more points)
14:24:12 <kaz> ... todo: ask existing registry managers about opinions
14:24:59 <kaz> q+
14:27:51 <kaz> ack k
14:28:27 <kaz> kaz: the descriptions here under "Requirements" are good starting point for further discussion
14:29:06 <kaz> ... but it seems to me they're rater our expectations for a possible WoT Registry
14:29:13 <Ege> q?
14:29:20 <kaz> ... so I'd suggest we change the title to "Expectations"
14:29:37 <kaz> ... and clarify actual "Requirements for the possible WoT Registry" based on them
14:29:41 <kaz> ek: ok
14:29:59 <kaz> ... (changes the section title from "Requirements" to "Expectations")
14:30:09 <kaz> q+
14:31:06 <kaz> ack k
14:31:27 <kaz> rrsagent, draft minutes
14:31:28 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/07-wot-td-minutes.html kaz
14:31:53 <kaz> q+
14:32:36 <JKRhb> q+
14:35:31 <kaz> ack k
14:35:46 <kaz> kaz: what do you mean by "registry lives within TD spec"?
14:36:13 <kaz> ek: thinking about a possible option of having a registry section within the TD spec
14:37:19 <kaz> ... because we've agreed on including the main Binding Template section into the TD spec
14:37:49 <kaz> kaz: we still need to consider the relationship between the Binding Template section of the TD spec and the registry
14:38:32 <kaz> jr: from versioning viewpoint, having a registry separately would be better to manage multiple versions of TDs
14:38:47 <kaz> ek: good point
14:38:50 <kaz> q?
14:38:52 <kaz> ack jk
14:39:16 <kaz> kaz: yeah, so we need to think about the how to manage the registry
14:39:38 <kaz> ... and the relationship between the Binding Templates section of TD and the Registry itself
14:39:45 <kaz> ek: ok
14:39:50 <kaz> ... will update the description here
14:40:08 <kaz> q+
14:40:52 <kaz> kaz: what do you mean by  "association of a binding to the TD spec"?
14:41:00 <kaz> ... is that a possible registry entry?
14:41:01 <kaz> ek: yes
14:42:12 <mjk> q?
14:43:13 <kaz> ack k
14:44:21 <kaz> kaz: technically, the registry is a deliverable of the WoT WG
14:44:34 <kaz> ... so the WoT WG as a whole should be the registry manager instead of the TD TF
14:44:45 <kaz> ... and we can assign somebody as the main contact person
14:44:48 <kaz> ek: ok
14:45:28 <kaz> kaz: regarding the possible future mechanism after the WoT WG Charter is expired, we should add a "TODO" question for that
14:45:29 <kaz> ek: ok
14:45:46 <kaz> q+
14:46:14 <kaz> ack k
14:46:23 <kaz> kaz: regarding the next bullet point
14:47:17 <kaz> ... would be better to say "It SHOULD b possible to register, update, or remove a registry entry for associating a binding to a specific TD spec"
14:47:18 <kaz> ek: ok
14:48:11 <kaz> q+
14:48:38 <kaz> ack k
14:48:49 <kaz> kaz: regarding the next bullet point
14:49:05 <kaz> ... There SHOULD be no two bindings for the same protocol
14:49:20 <kaz> ... would be better to say "There SHOULD NOT be two bindings for the same protocol"
14:49:29 <kaz> ... Koster, what do you think?
14:49:41 <kaz> mjk: ok
14:50:08 <kaz> ek: (adds descriptions to "Reasons")
14:50:41 <kaz> q?
14:50:57 <kaz> q+
14:51:09 <kaz> mjk: we may replace old one by a new one
14:51:54 <kaz> ... for example, several ecosystems have their definitions for CoAP
14:52:18 <kaz> ek: two points
14:53:21 <kaz> mjk: we could say this is a binding for CoAP
14:53:29 <kaz> ... and another for OPC
14:53:38 <kaz> ... also could think about layered binding
14:53:59 <kaz> ... ecosystem binding in addition to protocol binding
14:54:54 <kaz> ... the question is which would be better to have them as two separate entries, or one based another entry?
14:55:18 <kaz> q?
14:57:38 <kaz> ack k
14:57:48 <kaz> kaz: important question
14:57:59 <kaz> ... reminded me of the language tag from IANA
14:58:43 <kaz> ... like en_US, we can think about CoAP_OPC as the ID but the registry entries themselves should be separate with each other for the variations, I think
14:58:54 <kaz> ek: good point
14:59:09 <kaz> mjk: yeah, like the registry for natural languages
14:59:45 <Ege> q?
14:59:46 <kaz> ... for example, there are OCF version of CoAP and OMA version of CoAP
15:00:02 <kaz> ek: ok
15:00:15 <kaz> ... there are still 3 more bullet points
15:00:22 <kaz> ... but we're out of time, so let's continue the discussion next time
15:00:26 <kaz> q+
15:00:35 <kaz> ack k
15:00:49 <kaz> kaz: this is very important discussion
15:00:58 <kaz> ... thank you very much for your contribution
15:01:06 <kaz> ek: thank YOU too
15:01:23 <kaz> ... (saves the changes based on today's discussion)
15:01:29 <kaz> [adjourned]
15:01:44 <kaz> rrsagent, draft minutes
15:01:46 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/07-wot-td-minutes.html kaz
15:02:21 <kaz> s/en_US/en_US and en_GB/
15:02:37 <kaz> s/, I think//
15:02:41 <kaz> rrsagent, draft minutes
15:02:43 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/07-wot-td-minutes.html kaz
16:09:03 <JKRhb> JKRhb has joined #wot-td
16:19:25 <JKRhb> JKRhb has joined #wot-td
16:46:14 <JKRhb> JKRhb has joined #wot-td
17:01:20 <Zakim> Zakim has left #wot-td
17:17:51 <kaz> kaz has joined #wot-td
17:21:34 <JKRhb> JKRhb has joined #wot-td
17:42:54 <JKRhb> JKRhb has joined #wot-td
18:14:27 <JKRhb> JKRhb has joined #wot-td
19:17:14 <kaz> kaz has joined #wot-td
19:34:15 <JKRhb> JKRhb has joined #wot-td
19:44:37 <JKRhb> JKRhb has joined #wot-td
20:00:11 <JKRhb> JKRhb has joined #wot-td
21:00:11 <JKRhb> JKRhb has joined #wot-td
21:17:01 <JKRhb> JKRhb has joined #wot-td
21:27:24 <JKRhb> JKRhb has joined #wot-td
21:53:28 <JKRhb> JKRhb has joined #wot-td
22:11:03 <JKRhb> JKRhb has joined #wot-td
22:22:05 <JKRhb> JKRhb has joined #wot-td