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