12:54:09 <RRSAgent> RRSAgent has joined #wot-td
12:54:13 <RRSAgent> logging to https://www.w3.org/2024/03/14-wot-td-irc
12:54:23 <kaz> meeting: WoT-WG - TD-TF - Slot 2
12:54:29 <kaz> rrsagent, make log public
12:54:35 <kaz> rrsagent, draft minutes
12:54:36 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
12:59:10 <kaz> present+ Kaz_Ashimura, Luca_Barbato
12:59:55 <mjk> mjk has joined #wot-td
13:00:06 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#March_13_and_14%2C_2024
13:00:52 <kaz> present+ Michael_Koster
13:02:14 <Tomo> Tomo has joined #wot-td
13:02:34 <ktoumura> ktoumura has joined #wot-td
13:02:50 <kaz> present+ Kunihiko_Toumura
13:04:03 <kaz> present+ Ege_Korkan
13:04:07 <kaz> chair: Ege, Koster
13:05:20 <dape> dape has joined #wot-td
13:05:53 <Ege> Ege has joined #wot-td
13:06:03 <luca_barbato> luca_barbato has joined #wot-td
13:06:05 <kaz> present+ Tomoaki_Miushima
13:06:14 <kaz> s/Miushima/Mizushima/
13:06:20 <kaz> rrsagent, draft minutes
13:06:21 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
13:07:00 <kaz> present+ Daniel_Peintner
13:07:08 <luca_barbato> scribenick: luca_barbato
13:07:44 <kaz> present+ Michael_McCool
13:08:02 <luca_barbato> topic: CoAP
13:08:23 <luca_barbato> s/topic: CoAP/topic: Minutes
13:08:43 <luca_barbato> ege: Anybody has remarks on them?
13:09:05 <luca_barbato> ege: if none we shall approve the minutes
13:09:07 <kaz> i|Any|-> https://www.w3.org/2024/03/07-wot-td-minutes.html Mar-7 minutes|
13:09:08 <luca_barbato> <none>
13:09:16 <luca_barbato> topic: CoAP
13:09:37 <kaz> i/CoAP/approved/
13:09:43 <Ege> https://github.com/w3c/wot-binding-templates/pull/352
13:09:48 <McCool> McCool has joined #wot-td
13:10:18 <kaz> s|https://github.com/w3c/wot-binding-templates/pull/352|-> https://github.com/w3c/wot-binding-templates/pull/352 PR 352 - Min Polling Interval in CoAP|
13:10:20 <luca_barbato> ege: The patch was worked on asyncronously
13:10:59 <luca_barbato> ege: It showcases we are lacking tooling-wise, we could had the patch completed sooner
13:11:06 <luca_barbato> topic: Registry
13:11:27 <Ege> https://github.com/w3c/wot/pull/1183
13:11:58 <kaz> s|https://github.com/w3c/wot/pull/1183|-> https://github.com/w3c/wot/pull/1183 wot PR 1183 - Registry Requirements Revision|
13:12:22 <luca_barbato> ege: We worked on the document before and we can continue today, but I would like to make sure we agree on the last pending points
13:12:41 <Ege> A binding should be identifiable by the elements in a form such as href, contentType, or other terms.      We need to clarify whether the URI scheme and the media type MUST be registered in IANA first.         Provisional registration could reduce the overhead. Any new conflicting ones would bring up a discussion but it can still result in "our" provisional getting demoted.         Pros: more stable. Cons: More overhead and work  A binding that uses a [CUT]
13:12:58 <kaz> i/A binding/[[/
13:12:59 <kaz> ]]
13:13:17 <kaz> q+
13:14:06 <luca_barbato> kaz: You can mention explicitly the patch being discussed
13:14:27 <luca_barbato> ege: Yes, the patch is in the wot repository since the work can be shared with other TF
13:14:33 <kaz> -> https://github.com/w3c/wot/blob/c000f621ac356036cab3077c3f99b41a04220f7e/registry-analysis/Readme.md rendered version MD from PR
13:14:35 <Ege> https://github.com/w3c/wot/blob/egekorkan-patch-10/registry-analysis/Readme.md
13:14:50 <kaz> s|-> https://github.com/w3c/wot/blob/c000f621ac356036cab3077c3f99b41a04220f7e/registry-analysis/Readme.md rendered version MD from PR||
13:15:29 <kaz> s|https://github.com/w3c/wot/blob/egekorkan-patch-10/registry-analysis/Readme.md|-> https://github.com/w3c/wot/blob/egekorkan-patch-10/registry-analysis/Readme.md rendered text of "Registry Mechanism Analysis" on PR 1183|
13:15:36 <kaz> rrsagent, make log public
13:15:40 <kaz> rrsagent, draft minutes
13:15:42 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
13:17:58 <kaz> q?
13:18:05 <kaz> ack k
13:18:07 <kaz> q+ McCool
13:18:34 <kaz> q+
13:18:52 <kaz> ack m
13:18:52 <McCool> ack m
13:18:58 <luca_barbato> ege: we have some todo items before those points, but I'd first tackle the last 3 points
13:19:35 <kaz> [[
13:19:36 <kaz> TODO: Clarify what happens when two ecosystems like OCF and LwM2M both use CoAP binding. The initial thinking is to register them as separate entries but clarify what they use from CoAP binding. A layered registry can be thought of as language tags with en extending to en-us and en-uk where the tags and entries are different but the association to en is expressed in the id.
13:19:37 <kaz> ]]
13:19:38 <mjk> q?
13:19:59 <luca_barbato> mm: Regarding OCF and its relationship with CoAP, it extends CoAP in specific ways
13:20:29 <McCool> q+
13:20:37 <luca_barbato> kaz: We already started discussing possible extension mechanisms
13:21:13 <luca_barbato> ... do we want to start the detailed discussion now or complete the the global document and then fine tune?
13:21:15 <McCool> ack k
13:21:45 <luca_barbato> ege: I'd rather have the big picture look complete and then work on the details later
13:21:55 <luca_barbato> q+
13:22:14 <McCool> ack m
13:22:41 <luca_barbato> mm: An additional question is what to do for protocols using lower level protocols, do they fit a binding or a profile definition?
13:23:05 <kaz> kaz: @@@
13:23:55 <luca_barbato> lu: I'd complete the 3 points first and then use the remaining time for the binding-profile relationship
13:24:16 <kaz> s/@@@/for today, we record our questions as "TODO" and merge this PR itself, then think about how to soleve "TODO"s next. We can identify all the "TODO"s by specifying numbers like "TODO-1" and "TODO-2"./
13:24:24 <luca_barbato> ege: We need a way to identify a binding in the TD
13:24:27 <kaz> i/kaz:/scribenick: kaz/
13:24:35 <kaz> i/I'd/scribenick: luca_barbato/
13:24:38 <kaz> rrsagent, draft minutes
13:24:40 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
13:24:47 <kaz> q?
13:24:47 <kaz> ack l
13:24:52 <luca_barbato> ege: we can use some key-terms such as href, contentType
13:25:38 <luca_barbato> ege: It overlaps with the requirement of not having duplicate bindings
13:25:38 <luca_barbato> q+
13:28:44 <mjk> q+
13:28:52 <luca_barbato> ack l
13:29:18 <kaz> q+
13:29:20 <JKRhb> JKRhb has joined #wot-td
13:29:29 <kaz> ack k
13:30:19 <luca_barbato> lu: for the bindings we have some terms for the protocol bindings (href and subprotocol) and they may be enough, but for payload bindings contentType is not, since we may want to describe a serialization that in the end is still contentType json
13:30:58 <luca_barbato> .. we should probably use a single term `protocol` to avoid the confusion between the href schema and the subprotocol term and add a term for payload as well in TD 2.0
13:31:14 <JKRhb> rrsagent, draft minutes
13:31:16 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html JKRhb
13:31:27 <kaz> ack m
13:31:49 <luca_barbato> mjk: I want to add regarding content format: OCF is another example
13:31:52 <kaz> q+ McCool
13:32:12 <kaz> present+ Jan_Romann
13:32:23 <kaz> ack m
13:32:24 <McCool> q+
13:33:16 <McCool> ack m
13:33:19 <kaz> q+
13:33:25 <luca_barbato> mm: We can distinguish the protocol using the url/scheme
13:33:46 <luca_barbato> lu: We cannot, e.g. http is ambiguous
13:36:29 <Ege> https://github.com/w3c/wot-binding-templates/issues/281
13:36:37 <luca_barbato> kaz: We should use binding template as the title and technical term and think about protocol, formats as features related to the general mechanism
13:37:03 <kaz> s/binding template/"Binding Template"/
13:37:19 <kaz> s/formats as/formats and ecosystems as/
13:37:30 <mjk> q?
13:37:34 <kaz> ack k
13:38:10 <kaz> rrsagent, draft minutes
13:38:11 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
13:38:51 <luca_barbato> ege: Let's agree to constrain the bindings on terms contained by Form or Connection
13:40:27 <luca_barbato> ege: Next point: A protocol binding submission MUST provide a mapping between its operations and the WoT operations
13:40:43 <luca_barbato> q+
13:43:09 <kaz> q+
13:43:33 <Ege> ack l
13:43:37 <luca_barbato> lu: I think we can point to HTTP and MQTT as examples on explicit and implicit mapping
13:44:36 <kaz> ack k
13:46:03 <luca_barbato> kaz: I was wondering what we want to mean with WoT operations
13:46:54 <luca_barbato> lu: Me and Ege were thinking about just the `op` term, you are thinking about the overall operation concept
13:48:03 <luca_barbato> q+
13:50:53 <luca_barbato> ege: Then next point is about formats, their serialization and DataSchema.
13:51:18 <luca_barbato> ... We should make sure that a binding expressing a serialization format provides a DataSchema mapping
13:51:55 <luca_barbato> lu: This feels an expansion on the first of the 3 points, we need to add a vocabulary term to avoid clashes on the contentType
13:52:34 <luca_barbato> ege: With this we are at the end of the list and I would commit it
13:53:22 <luca_barbato> ege: Or given the time constraint we can go over the whole document the next time
13:53:53 <McCool> (ntd, ttyl).
13:53:53 <kaz> q?
13:53:57 <kaz> ack l
13:54:32 <luca_barbato> ege: We can also look at the ttwg boilerplate template
13:54:53 <kaz> q+
13:54:57 <kaz> rrsagent, draft minutes
13:54:59 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
13:55:05 <luca_barbato> topic: Binding Templates
13:57:15 <kaz> i/We can also/subtopic: Registries Breakkout/
13:57:16 <kaz> rrsagent, draft minutes
13:57:17 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
13:57:44 <kaz> kaz has joined #wot-td
13:58:12 <luca_barbato> kaz: I started an initial discussion with plh about that
13:58:23 <kaz> s/topic: Binding Templates//
13:58:51 <JKRhb> rrsagent, draft minutes
13:58:52 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html JKRhb
13:59:07 <kaz> i|We can|-> https://www.w3.org/2024/03/12-registries-minutes.html Registries Breakout minutes|
14:00:03 <kaz> s/We can also/We had discussion on existing registries within W3C like the TTWG's registry. We can/
14:00:10 <kaz> rrsagent, draft minutes
14:00:12 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
14:00:18 <Ege> https://github.com/w3c/wot-thing-description/issues/1987
14:00:41 <luca_barbato> ege: We should also discuss about the binding template section in the TD
14:00:56 <kaz> i/Registry Requirements R/subtopic: Registry Analysis and Requirements/
14:00:58 <kaz> rrsagent, draft minutes
14:00:59 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
14:01:34 <kaz> [adjourned]
14:01:36 <kaz> rrsagent, draft minutes
14:01:37 <RRSAgent> I have made the request to generate https://www.w3.org/2024/03/14-wot-td-minutes.html kaz
14:17:13 <JKRhb> JKRhb has joined #wot-td
15:59:19 <Zakim> Zakim has left #wot-td