13:48:24 <RRSAgent> RRSAgent has joined #wot-td
13:48:24 <RRSAgent> logging to https://www.w3.org/2022/10/19-wot-td-irc
13:54:07 <Mizushima> Mizushima has joined #wot-td
14:01:57 <kaz-brb> meeting: WoT-WG - TD-TF
14:03:09 <dape> dape has joined #wot-td
14:03:38 <Ege> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf
14:06:03 <mjk> mjk has joined #wot-td
14:06:15 <kaz-brb> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#October_19.2C_2022
14:06:32 <cris_> cris_ has joined #wot-td
14:06:48 <kaz-brb> present+ Kaz_Ashimura, Ege_Korkan, Daniel_Peintner, Erich_Barnstedt, Klaus_Hartke, Michael_Koster, Sebastian_Kaebisch
14:06:58 <kaz> chair: Ege/Sebastian
14:07:13 <sebastian_> sebastian_ has joined #wot-td
14:07:25 <kaz> scribenick: sebastian_
14:08:09 <sebastian_> topic: minutes
14:08:35 <sebastian_> -> https://www.w3.org/2022/10/12-wot-td-minutes.html
14:09:02 <kaz> s/html/html Oct-12/
14:09:12 <Ege> https://github.com/w3c/wot-binding-templates/issues/191
14:09:17 <JKRhb> JKRhb has joined #wot-td
14:10:51 <kaz> present+ Matthias_Kovatsch
14:11:34 <kaz> rrsagent, make log public
14:11:39 <kaz> rrsagent, draft minutes
14:11:39 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:11:39 <cris_> present+ Cristiano_Aguzzi
14:12:38 <kaz> present+ Jan_Romann
14:12:40 <sebastian_> Ege: any objections? anything to change?
14:12:58 <sebastian_> no
14:13:05 <sebastian_> minutes are approved
14:13:40 <kaz> rrsagent, draft minutes
14:13:40 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:14:41 <sebastian_> topic: Binding PRs
14:14:51 <kaz> subtopic: PR 188
14:15:04 <kaz> -> https://github.com/w3c/wot-binding-templates/pull/188 PR 188 - Define CoAP Content Negotiation
14:15:35 <kaz> q?
14:15:38 <sebastian_> s/subtopic: PR 188/subtopic: PR 188 + PR193
14:15:47 <kaz> q+ klaus
14:15:50 <kaz> ack k
14:16:19 <sebastian_> -> https://github.com/w3c/wot-binding-templates/pull/193 PR 193 - Alternative proprosal for handling CoAP Content-Formats
14:16:50 <Mizushima> present+ Tomoaki_Mizushima
14:17:22 <kaz> rrsagent, draft minutes
14:17:22 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:18:48 <kaz> -> https://w3c.github.io/wot-thing-description/#form WoT Thing Description 1.1 ED - 5.3.4.2 Form
14:19:06 <cris_> q+
14:19:42 <sebastian_> <Klaus explains the technical details of the PRs>
14:19:52 <kaz> s/subtopic: PR 188/subtopic: PR 188 and PR 193/
14:22:14 <kaz> q+
14:22:17 <kaz> ack c
14:23:03 <sebastian_> Klaus: I open a PR in binding PR and not in node-wot
14:23:25 <JKRhb> q+
14:23:40 <sebastian_> ... HTTP binding does not check contentType
14:23:45 <cris_> ack c
14:23:46 <Ege> q+
14:24:25 <sebastian_> Kaz: You remove the contentType and make the field empty?
14:25:14 <sebastian_> Klaus: TD spec says it is manditory but I do not want to provide default value.
14:25:43 <mkovatsc> mkovatsc has joined #wot-td
14:26:06 <mkovatsc> q+
14:26:07 <Ege> https://github.com/w3c/wot-thing-description/pull/1564
14:26:31 <kaz> s/field empty?/field empty, but do you expect the default value of "application/json" to be applied?/
14:26:33 <kaz> ack k
14:26:33 <sebastian_> Jan: Agree with Klaus that there is some fundemental problem.
14:26:49 <cris_> q+
14:27:02 <sebastian_> ... contentType can be protocol specefic
14:27:03 <McCool_> McCool_ has joined #wot-td
14:27:34 <sebastian_> Matthias: I check the history of the binding repo
14:28:22 <kaz> i/1564/kaz: in that case, we need to clarify the behavior, e.g., contentType with an empty string would mean VOID or might be better to explicitly specify [[ "contentType": "VOID" ]]. So need more clarification here./
14:28:46 <kaz> rrsagent, draft minutes
14:28:46 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:29:29 <kaz> i/in that case/scribenick: kaz/
14:29:33 <sebastian_> ... content type should be ideally a metric if you read it
14:29:39 <kaz> i/Agree/scribenick: sebastian_/
14:29:42 <kaz> rrsagent, draft minutes
14:29:42 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:30:10 <mkovatsc> See https://github.com/eclipse/thingweb.node-wot/blob/fd2adf5a2b8eb08cc25f745590e589ea6b3e36e1/packages/binding-http/src/http-client.ts#L387 for original contentType handling before breaking it.
14:30:21 <kaz> q+
14:30:27 <kaz> ack jk
14:30:30 <kaz> ack ege
14:30:32 <kaz> ack mk
14:30:42 <sebastian_> ... ideal would be to use IANA media types , they are globally defined and teh shall be protocol indenpendent
14:30:45 <sebastian_> q+
14:31:14 <kaz> s/teh shall be protocol indenpendent/they should be protocol-independent/
14:32:00 <kaz> present+ Michael_McCool
14:32:35 <sebastian_> Kaz: we can rules such as if input type is used there should be a contentType used
14:33:10 <sebastian_> <Ege shows the contentType usage in the TD1.1 spec>
14:33:28 <kaz> s/Kaz:/Ege:/
14:33:42 <kaz> rrsagent, draft minutes
14:33:42 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:34:02 <mkovatsc> q-
14:34:14 <sebastian_> Klaus: we should check this table and dicuss this again next week
14:34:29 <Ege> q?
14:34:48 <Ege> ack k
14:35:29 <kaz> kaz: clarification question, when you@@@
14:35:52 <mkovatsc> q+
14:36:42 <kaz> s/you@@@/you said "This is a bug.", what did you mean the bug was from? The TD 1.1 spec, the Binding Templates Note, or node-wot?/
14:37:04 <kaz> Ege: a bug of node-wot
14:37:14 <kaz> kaz: as Klaus also kind of agree@@
14:37:47 <cris_> ack c
14:38:25 <sebastian_> Cris: we had also a proposal
14:38:35 <kaz> s/agree@@/agree, probably the description on the default value within the TD 1.1 spec and possibly the Binding Templates Note should be modified about what would happen in which case, e.g., having no contentType line at all, having a contentType field with an empty value./
14:38:53 <kaz> rrsagent, draft minutes
14:38:53 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:39:31 <kaz> i/clarification/scribenick: kaz/
14:39:36 <sebastian_> subtopic: PR 183 + 176
14:39:43 <kaz> i/we had also a/scribenick: sebastian_/
14:40:03 <sebastian_> -> https://github.com/w3c/wot-binding-templates/issues/176
14:40:10 <kaz> s/PR 188 and PR 193 + PR193/PR 188 + 193/
14:40:13 <kaz> rrsagent, draft minutes
14:40:13 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:40:17 <sebastian_> -> https://github.com/w3c/wot-binding-templates/pull/183
14:40:59 <kaz> s/+ 176/+ Issue 176/
14:41:27 <sebastian_> Ege: question is about if the href. Should href be used to put all address information in there
14:41:33 <kaz> s/176/176 Issue 176 - [Modbus] URI design for modbus+tcp URI schemes/
14:41:59 <kaz> s/183/183 PR 183 - feat(modbus): move addres and quantity to URL components/
14:42:02 <kaz> rrsagent, draft minutes
14:42:02 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
14:42:11 <Ege> q?
14:42:19 <Ege> ack s
14:42:21 <Ege> ack m
14:42:55 <sebastian_> Matthias: href follows web approach and I do not understand why not relying on this
14:43:21 <mjk> q?
14:44:03 <sebastian_> <Ege present its comment https://github.com/w3c/wot-binding-templates/pull/183#issuecomment-1277200021>
14:44:48 <sebastian_> q+
14:45:31 <kaz> s/its c/his c/
14:46:59 <mjk> q+
14:48:12 <cris_> q+
14:48:24 <sebastian_> ack s
14:48:26 <Ege> ack s
14:49:15 <kaz> q+
14:49:20 <kaz> ack mjk
14:49:50 <sebastian_> there are pros and cons. Readability and simple validation is important
14:50:08 <mkovatsc> q+
14:50:19 <mjk> ack m
14:50:29 <sebastian_> ... WS is also not solved nicely. href is used localy without any value
14:50:30 <mjk> oops, sorry matthias
14:50:38 <mjk> I was trying to ack myself
14:50:47 <kaz> q+ mkovatsc
14:50:50 <kaz> ack c
14:51:15 <kaz> s/oops, sorry matthias//
14:52:02 <sebastian_> Cris: we can define URL more verbose with readable variables (e.g. quantity etc)
14:52:09 <kaz> ack k
14:52:15 <cris_> I did use modbus different times
14:52:20 <sebastian_> Kaz: who has implemented Mobus binding so far?
14:52:38 <sebastian_> s/Mobus/Modbus
14:53:12 <sebastian_> ... we need more experiences from the developer
14:53:25 <kaz> s/so far?/so far? I think we can collect some more "Current Practices" like IPA guys (=Takenaka guys)/
14:53:55 <cris_> q+
14:53:56 <sebastian_> Matthias: we have devices and implementation, however, different business units used in different way
14:54:29 <kaz> i/we have/mm: I've been working on Modbus implementations for my smart home system./
14:54:39 <kaz> q?
14:54:41 <kaz> ack mk
14:54:49 <kaz> q+
14:54:56 <sebastian_> Matthias: address information in a single string has benefits such as simple copy it
14:55:04 <sebastian_> q+
14:55:08 <cris_> ack cris_
14:55:27 <sebastian_> ack s
14:56:01 <sebastian_> Ege: should any protocol put in the href?
14:56:48 <Ege> q?
14:57:56 <mkovatsc> q+
14:57:57 <kaz> ack k
14:59:04 <sebastian_> Kaz: we should collect best practices
14:59:14 <mkovatsc> q-
14:59:22 <mkovatsc> have to leave for another meeting.
14:59:27 <kaz> s/practices/practices as the starting point./
14:59:47 <sebastian_> subtopic: PR 190
15:00:07 <sebastian_> -> https://github.com/w3c/wot-binding-templates/pull/190
15:00:27 <sebastian_> Ege: HTTP has no abstract, Modbus has
15:00:35 <kaz> s/190/190 PR 190 - Align protocol binding abstracts/
15:00:56 <sebastian_> ... there should be always a part with the same abstract text
15:01:07 <kaz> q+
15:02:34 <sebastian_> Kaz: Im ok with this PR. We should have a concentrate note about the relation of the binding documents and ontologies
15:02:36 <kaz> ack k
15:04:16 <sebastian_> Ege: I will merge it later. Need to fix the URL problem
15:05:16 <Ege> scribenick: Ege
15:05:29 <Ege> topic: TD
15:05:29 <kaz> s/We should have a concentrate note about the relation of the binding documents and ontologies/Please remember I still think it would be better to have a consolidated Binding Templates document describing the Binding mechanism and separate ontologies to refer to protocol-specific vocabularies. If we really want to go for this multiple sub-documents approach, we need to survey the existing vocabulary documents like the HTTP vocabulary and the MQTT
15:05:34 <kaz> vocabulary, and clarify the relationship between our generating vocabulary sub-documents and those existing documents./
15:05:41 <Ege> subtopic: Dependency Check on the Binding Document
15:05:53 <kaz> s|vocabulary, and clarify the relationship between our generating vocabulary sub-documents and those existing documents./||
15:06:00 <Ege> sk: Michael Lagally has asked us to check if we have a dependency
15:06:17 <kaz> s|and the MQTT|and the MQTT vocabulary, and clarify the relationship between our generating vocabulary sub-documents and those existing documents.|
15:06:18 <Ege> ... so we should do this
15:06:26 <kaz> rrsagent, draft minutes
15:06:26 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
15:06:27 <Ege> ... I checked before the meeting
15:06:52 <Ege> ... I have checked the references first (ones used like [foo bar])
15:06:57 <kaz> s/Im ok/I'm OK/
15:07:16 <kaz> s/this PR/merging this PR itself/
15:07:18 <kaz> rrsagent, draft minutes
15:07:18 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
15:07:18 <Ege> ... we are referring to the last version published in January 2020 and only that
15:07:44 <kaz> s/Please remember/However, please remember/
15:07:46 <kaz> rrsagent, draft minutes
15:07:46 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
15:08:18 <kaz> q+
15:08:19 <Ege> sk: I have also checked with the 1.0 version and we are only referring to it to say "you can look there to have more information"
15:10:02 <Ege> ka: that may not answer Michael Lagally's question, we should check the assertions
15:10:57 <Ege> sk: that is why I do this pattern search and I do not find the [WOT-BINDING-TEMPLATES] in an assertion anywhere
15:11:28 <dape> q+
15:11:34 <kaz> ack k
15:12:02 <Ege> sk: the results are pointing informatively to the binding templates for readers to find more information
15:12:52 <Ege> sk: Also we are doing the same in the 1.0 version
15:13:59 <Ege> q+
15:14:38 <Ege> ka: if you look for protocol binding, you find results
15:16:23 <Ege> sk: but these are not references to the document
15:17:05 <Ege> https://w3c.github.io/wot-architecture/#dfn-wot-protocol-binding
15:18:56 <Ege> ek: the term protocol binding actually means having forms and href inside etc. It does not mean the binding templates specification
15:19:20 <kaz> s/find results/find results on "protocol binding" which might be referring to the content of the Binding Templates Note./
15:19:24 <Ege> sk: we have put the http protocol binding in the TD spec since it was the most demanded one
15:23:16 <Ege> ek: I think that we do not have a dependency since the mechanism is defined in the TD spec
15:23:26 <Ege> ka: I think we should look into the assertions
15:24:21 <Ege> ka: we can do it offline
15:24:57 <Ege> sk: I can comment on Michael Lagally's issue
15:25:09 <Ege> ka: we can split the assertions into group and the load can be shared
15:25:27 <Ege> sk: what do you mean by categorizing
15:26:09 <Ege> ka: like the first X lines are reviewed by you, another by me and another volunteer like Ege
15:26:11 <sebastian_> https://github.com/w3c/wot-thing-description/issues/1722
15:26:20 <Ege> sk: I will make a proposal on how to split it
15:27:05 <Ege> ek: I can help
15:27:08 <Ege> ca: I can also help
15:27:17 <Ege> sk: I will make a plan and ping you in the issue
15:27:49 <Ege> sk: then we can do the work and that should satisfy the requirements of the issue 1772
15:27:55 <Ege> s/1772/1722
15:29:51 <kaz> subtopic: Editors list updates
15:30:08 <Ege> sk: we can look at the commits
15:30:56 <cris_> q+
15:31:02 <Ege> ack e
15:31:05 <Ege> ack d
15:31:08 <cris_> ack c
15:31:14 <cris_> I'm ok :)
15:31:23 <dape> ack dape
15:31:31 <McCool_> q?
15:32:00 <Ege> sk: what does everyone think?
15:32:06 <kaz> i|we can look|-> https://github.com/w3c/wot-thing-description/pull/1718 PR 1718 - Update editors list and acknowledgements|
15:32:50 <kaz> q+
15:33:47 <Ege> ek: Is it ok to have Matthias as Huawei
15:33:49 <Ege> sk: not sure
15:35:01 <Ege> ka: there is no policy from W3C, the WG can define a policy. You can ask Matthias
15:35:36 <Ege> mm: we had a similar issue with Farshid, you can duplicate it
15:35:59 <Ege> sk: I think we can merge it and then talk with Matthias about what he thinks or wants
15:37:13 <kaz> s/there is no policy from W3C, the WG can define a policy. You can ask Matthias/Each WG can define its own policy about this kind of detail. I'd suggest you ask Matthias about his preference first. Technically, we can put his name with the previous affiliation under the "Former Editors" section and put his name with the current affiliation under the "Editors" section./
15:37:40 <kaz> s/"Editors" section./"Editors" section. What is important here is rather when he made his major contributions./
15:38:14 <Ege> subtopic: Implementation Report
15:40:17 <Ege> sk: we are looking pretty good
15:40:24 <Ege> mm: it is acceptable to go to CR right now
15:41:11 <kaz> i|we are|-> https://github.com/w3c/wot-thing-description/pull/1725 PR 1725 - Oct 2022 impl report updates|
15:41:41 <kaz> i|we are|-> https://cdn.statically.io/gh/w3c/wot-thing-description/a6cdd9567442230c35f6f174b46b08734d5fe4ea/testing/report11.html rendered version of the TD Implementation Report+
15:41:42 <Ege> sk: how many assertions do we have?
15:41:46 <kaz> s/Report+/Report/
15:41:47 <Ege> mm: I see 455 in the template.csv
15:42:12 <kaz> i|we are|-> https://github.com/w3c/wot-thing-description/pull/1726 PR 1726 - Enumerate At-Risk Items|
15:43:07 <kaz> i|we are|-> https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/1726/57bf285...mmccool:30ea0c8.html#sotd Status of This Document section including the features at risk|
15:47:43 <kaz> q+
15:48:08 <Ege> mm: who to put as editors?
15:48:42 <Ege> mm: we can put me, me and Ege, me and Fady
15:48:57 <Ege> ... the conclusion is to put 3 of us
15:49:36 <Ege> mm: I will update contributions is to reflect the new implementation contributions
15:50:19 <Ege> proposal: the editors of the implementation report should be the organizers and the contributors are all who contribute with the implementation results
15:51:18 <Ege> proposal: the editors of the implementation report should be the organizers and the acknowledgements should list all the contributors who contributed with the implementation results
15:53:14 <sebastian_> +1
15:53:33 <kaz> ack k
15:53:55 <Ege> resolution: the editors of the implementation report should be the organizers and the acknowledgements should list all the contributors who contributed with the implementation results
15:55:54 <kaz> subtopic: PR 1711
15:56:19 <kaz> s/subtopic: PR 1711//
15:57:29 <Ege> proposal: the editors of the TD specification are decided by the consensus of the group and the acknowledgements should list all the contributors who contributed with git commits. There can be contributors who raise issues or participate in discussions and they can be added upon request in the acknowledgments
15:58:05 <kaz> i/proposal/kaz: it would be nicer if we could clarify our policy for the TD spec as well./
15:58:12 <kaz> rrsagent, draft minutes
15:58:13 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
15:58:21 <kaz> q+
15:58:56 <McCool_> q+
15:59:06 <kaz> ack k
16:00:01 <sebastian_> +1
16:00:05 <McCool_> ack m
16:00:12 <Ege> resolution: the editors of the TD specification are decided by the consensus of the group and the acknowledgements should list all the contributors who contributed with git commits. There can be contributors who raise issues or participate in discussions and they can be added upon request in the acknowledgments
16:00:38 <Ege> ka: we can then document this in the readme
16:00:52 <Ege> mm: please remind us in the main call next week to have a wg-wide resolution
16:00:58 <Ege> subtopic: PR 1711
16:01:01 <kaz> s/readme/readme after getting the whole WG resolution :)/
16:01:05 <Ege> dp: I have fixed the merge conflicts
16:01:14 <Ege> sk: any objections?
16:01:31 <kaz> i|any|-> https://github.com/w3c/wot-thing-description/pull/1711 PR 1711 - refactor: add // or /*...*/ to make example be highlighted correctly|
16:04:48 <kaz> q+
16:04:59 <Ege> ek: I have that contentType PR, I can do it by next week. It is just explanation
16:05:29 <kaz> subtopic: PR 1721
16:05:47 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1721 PR 1721 - remove ednotes
16:06:31 <kaz> sk: (shows Editors notes within the latest Editors Draft)
16:07:02 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/1721/5c1822e...0ef2081.html diff version
16:07:37 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/pull/1721.html preview version
16:08:53 <kaz> -> https://w3c.github.io/wot-thing-description/#validation-serialization-json current Editors Draft
16:09:16 <kaz> sk: (shows the Editors Note with a description of "No Tag Yet")
16:09:20 <kaz> q+
16:10:14 <kaz> kaz: can we really remove all the Editor's Notes?
16:10:41 <Ege> sk: they show that the spec is somewhat not ready right
16:10:52 <Ege> ka: if some are not resolved, we should keep them
16:11:31 <kaz> i/subtopic:/scribenick: kaz/
16:11:40 <kaz> i/they show/scribenick: Ege/
16:12:32 <kaz> s/keep them/keep them mentioning this is not fatal and we can continue discussion on this for the next version./
16:13:14 <Ege> ka: there are non-fatal editors notes in the other specs
16:16:24 <Ege> subtopic: PR 1727
16:16:39 <Ege> sk: it only updates the link to the arch document
16:17:48 <kaz> i|PR 1727|kaz: btw, we're already out of time, so I'd suggest we close the call and you update the publication schedule based on today's discussion./
16:18:07 <kaz> i|it only updates|-> https://github.com/w3c/wot-thing-description/pull/1727 PR 1727 - use proper Architecture 1.1 reference|
16:18:44 <kaz> rrsagent, draft minutes
16:18:44 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
16:18:50 <Ege> sk: any objections?
16:19:21 <kaz> q?
16:19:27 <kaz> ack k
16:19:30 <kaz> q+
16:19:45 <kaz> (merged)
16:20:11 <Ege> subtopic: PR to remove coap example
16:20:44 <Ege> sk: I have talked with Klaus Hartke and he said that the TD should not have these examples but point to the binding
16:20:54 <Ege> sk: coap is not ready yet
16:21:36 <Ege> sk: I suggested that other protocols can be used, for more look at binding templates
16:21:51 <Ege> s/subtopic: PR to remove coap example/PR 1728
16:22:19 <kaz> i|-> https://github.com/w3c/wot-thing-description/pull/1728 PR 1728 - Update 8.3 Protocol Bindings section|
16:23:45 <kaz> q+
16:24:57 <Ege> ka: we can remove the example and add a clear example in the binding templates
16:25:09 <kaz> ack k
16:25:35 <Ege> q?
16:26:34 <Ege> subtopic: PR 1729
16:26:35 <kaz> s/we can remove the example and add a clear example in the binding templates/Removing the informative example from the WoT Thing Description 1.1 specification is fine, but we should clarify our plan to add even nicer and clearer description and example within the Binding Templates Note instead./
16:27:12 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1729 PR 1729 - Update validation|
16:27:20 <kaz> s/validation|/validation/
16:27:53 <Ege> mm: I have further explained the validation
16:29:27 <Ege> mm: also the editors note is safe to remove
16:29:31 <Ege> sk: we can keep them
16:29:36 <kaz> q+
16:29:37 <Ege> mm: but the editors note does not make sense here
16:29:55 <Ege> sk: I can remove it now
16:31:23 <Ege> sk: we can merge it now
16:31:43 <Ege> ka: some of the non-fatal editors note can live in REC. We need to identify which is fatal which is not
16:31:56 <kaz> -> https://www.w3.org/TR/2022/REC-html-aria-20220927/ example of Editor's note within a REC
16:32:19 <kaz> s/REC. We/REC but we/
16:32:27 <kaz> s/fatal/fatal and /
16:34:51 <Ege> subtopic: PR 1676
16:35:12 <Ege> mm: We have discussed this in the security call, we can merge it
16:35:30 <kaz> i|We have|-> https://github.com/w3c/wot-thing-description/pull/1676 PR 1676 - Tweak "out-of-band" in td-security-no-secrets assertion|
16:35:57 <kaz> (merged)
16:36:02 <kaz> subtopic: PR 1677
16:36:15 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1677 PR 1677 - Define what it means to satisfy a security scheme
16:36:51 <Ege> mm: I will resolve the conflict and merge it
16:38:04 <kaz> [adjourned]
16:38:12 <Ege> topic: epilogue
16:38:17 <Ege> sk: thank you all for attending
16:38:21 <kaz> rrsagent, draft minutes
16:38:21 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
16:38:27 <Ege> sk: Adjourned
16:38:32 <kaz> s/[adjourned]//
16:38:34 <kaz> rrsagent, draft minutes
16:38:34 <RRSAgent> I have made the request to generate https://www.w3.org/2022/10/19-wot-td-minutes.html kaz
18:05:01 <JKRhb> JKRhb has joined #wot-td
18:59:23 <Zakim> Zakim has left #wot-td