IRC log of wot-td on 2024-05-23

Timestamps are in UTC.

13:03:01 [RRSAgent]
RRSAgent has joined #wot-td
13:03:05 [RRSAgent]
logging to https://www.w3.org/2024/05/23-wot-td-irc
13:03:19 [kaz]
meeting: WoT-WG - TD-TF - Slot 2
13:03:49 [kaz]
present+ Kaz_Ashimura, Michael_Koster, Daiel_Peintner, Ege_Korkan, Kunihiko_Toumura, Mahda_Noura
13:03:53 [kaz]
chair: Koster
13:05:10 [Ege]
scribenick: Ege
13:08:47 [Ege]
topic: TD Errata
13:09:50 [kaz]
q+
13:10:21 [kaz]
ack k
13:11:01 [kaz]
-> https://github.com/w3c/wot-thing-description/pull/2023 PR 2023 - Fixes to Errata Documents
13:11:12 [kaz]
scribe+
13:11:15 [kaz]
ek: slightly updated the PR 2023
13:11:24 [kaz]
... (goes through the updated PR 2023)
13:11:41 [kaz]
-> https://github.com/w3c/wot-thing-description/pull/2023/files Files changed
13:12:01 [Ege]
ek: I have removed scripts, added how to main the document section
13:12:27 [kaz]
i/have/scribenick: Ege/
13:12:30 [Ege]
mk: this can be automated later
13:12:37 [kaz]
rrsagent, make log public
13:12:42 [kaz]
rrsagent, draft minutes
13:12:43 [RRSAgent]
I have made the request to generate https://www.w3.org/2024/05/23-wot-td-minutes.html kaz
13:13:13 [Ege]
ek: we can look at this one and the arch and discovery in the next main call
13:14:28 [Ege]
mk: do we need resolution?
13:14:35 [Ege]
kaz: we can do so and bring to main call
13:15:25 [Ege]
proposal: agree to update the errata document for TD 1.0 and 1.1 by merging PR at https://github.com/w3c/wot-thing-description/pull/2023
13:16:26 [Ege]
RESOLUTION: agree to update the errata document for TD 1.0 and 1.1 by merging PR at https://github.com/w3c/wot-thing-description/pull/2023
13:16:35 [kaz]
rrsagent, draft minutes
13:16:36 [RRSAgent]
I have made the request to generate https://www.w3.org/2024/05/23-wot-td-minutes.html kaz
13:17:10 [kaz]
agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#May_22_and_23_2024
13:17:58 [kaz]
topic: Binding Templates
13:18:01 [kaz]
subtopic: Registry
13:18:10 [Ege]
ek: we have a draft PR for the requirements
13:18:34 [kaz]
i|we|-> https://github.com/w3c/wot/blob/main/registry-analysis/Readme.md Registry mechanism Analysis
13:18:55 [kaz]
q+
13:19:22 [kaz]
-> https://github.com/w3c/wot/pull/1183 wot PR 1183 - Registry Requirements Revision
13:19:23 [kaz]
q-
13:19:56 [Ege]
mk: we can render to view this new section
13:20:16 [kaz]
-> https://github.com/w3c/wot/blob/9f34a033bc14357750f0f21c6ab15e46c922d6b6/registry-analysis/Readme.md Rendered Readme.md
13:22:06 [Ege]
ek: we have the point with TODO, then we have points with not enough text
13:24:39 [Ege]
mk: we have todo on where the registry should live
13:24:47 [mjk]
q?
13:25:21 [Ege]
ek: if it is a section, it is mechanically more difficult to update
13:26:26 [Ege]
mk: any questions?
13:27:28 [kaz]
q+
13:27:28 [Ege]
ek: not having it in the td spec means maintaining a document close to the TD spec
13:28:39 [kaz]
ack k
13:29:08 [Ege]
kaz: we can keep working on this document
13:29:32 [Ege]
mk: I tend towards having a separate document
13:29:55 [kaz]
q+
13:32:53 [kaz]
q-
13:32:54 [kaz]
q+
13:33:25 [kaz]
-> https://www.w3.org/2023/Process-20231103/ W3C Process Document
13:33:56 [luca_barbato]
luca_barbato has joined #wot-td
13:34:26 [Ege]
ek: are we allowed to have a registry track document since it is not mentioned in the charter?
13:35:07 [kaz]
[[
13:35:08 [kaz]
A registry report or registry section is purely documentational, is not subject to the W3C Patent Policy, and must not contain any requirements on implementations. For the purposes of the Patent Policy [PATENT-POLICY], any registry section in a Recommendation track document is not a normative portion of that specification.
13:35:09 [kaz]
]]
13:35:13 [Ege]
Registries can be published either as a stand-alone technical report on the Registry Track called a registry report, or incorporated as part of a Recommendation as a registry section.
13:38:14 [Ege]
kaz: registries are documentational and are not subject to patent policy
13:38:23 [Ege]
mk: so the main question is whether we can have a separate document
13:38:31 [Ege]
q?
13:38:39 [kaz]
-
13:38:41 [kaz]
q-
13:39:06 [mjk1]
mjk1 has joined #wot-td
13:39:23 [luca_barbato]
q+
13:39:27 [Ege]
ek: Does anyone object to having a separate document for registry if W3C process allows it?
13:40:48 [kaz]
rrsagent, draft minutes
13:40:49 [RRSAgent]
I have made the request to generate https://www.w3.org/2024/05/23-wot-td-minutes.html kaz
13:40:57 [Ege]
lb: IPR is a bit confusing here?
13:41:26 [kaz]
s/Daiel/Daniel/
13:41:41 [kaz]
present+ Luca_Barbato
13:41:55 [kaz]
q+
13:42:35 [luca_barbato]
q+
13:42:37 [kaz]
ack lu
13:42:41 [kaz]
ack k
13:42:42 [Ege]
lb: whether a binding is in rec section table or a separate document, the policy doesnt matter
13:42:43 [kaz]
q+ luca
13:47:48 [mjk1]
q:
13:47:50 [mjk1]
q?
13:47:55 [luca_barbato]
q-
13:48:02 [mjk1]
q?
13:48:07 [mjk1]
ack lu
13:49:29 [Ege]
mk: we should definitely have a layered registry
13:49:56 [Ege]
... coap is used differently in ocf and lwm2m, ocf uses post and lwm2m uses a put to writeproperty
13:50:31 [kaz]
q+
13:50:43 [Ege]
mk: bindings should be identifiable
13:51:10 [kaz]
ack k
13:53:50 [luca_barbato]
q+
13:54:52 [Ege]
ek: an ocf or lwm2m binding would be difficult to identify just from form elements
13:55:01 [Ege]
... also has other requirements
13:55:59 [Ege]
mk: A profile can be useful in that case
13:56:15 [Ege]
q?
13:56:40 [Ege]
... but we need to define the profile first
13:57:33 [Ege]
lb: (didn't understand the first point, please extend)
13:57:59 [Ege]
lb: we need to understand how to compose bindings
13:59:06 [Ege]
... also I would deprecate subprotocol and have a term called protocol and thus make everything explicit
13:59:24 [Ege]
... subprotocol is a "papercut" I have found
14:00:31 [Ege]
lb: I would love to talk about degraded consumption
14:01:09 [mjk1]
q?
14:01:14 [kaz]
ack lu
14:03:30 [kaz]
[adjourned]
14:03:36 [kaz]
rrsagent, draft minutes
14:03:37 [RRSAgent]
I have made the request to generate https://www.w3.org/2024/05/23-wot-td-minutes.html kaz