15:00:13 <RRSAgent> RRSAgent has joined #wot-td
15:00:18 <RRSAgent> logging to https://www.w3.org/2023/02/01-wot-td-irc
15:01:15 <kaz> meeting: WoT-WG - TD-TF
15:01:34 <kaz> present+ Kaz_Ashimura, Ege_Korkan
15:02:43 <kaz> rrsagent, make log publc
15:02:50 <kaz> s/rrsagent, make log publc//
15:02:54 <kaz> rrsagent, make log public
15:03:00 <kaz> rrsagent, draft minutes
15:03:31 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:03:39 <MIzushima> MIzushima has joined #wot-td
15:03:39 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#February_01.2C_2023
15:03:47 <kaz> present+ Sebastian_Kaebisch
15:05:32 <dape> dape has joined #wot-td
15:06:03 <kaz> present+ Daniel_Peintner, Michael_Koster
15:06:16 <kaz> chair: Sebastian/Ege
15:06:25 <cris_> cris_ has joined #wot-td
15:07:54 <kaz> q+
15:09:56 <sebastian> sebastian has joined #wot-td
15:10:21 <kaz> topic: Calendars
15:11:49 <kaz> -> https://www.w3.org/groups/wg/wot/calendar wg/wot/calendar
15:11:51 <kaz> kaz: @@@
15:11:52 <dape> scribe: dape
15:13:20 <dape> TOPIC: Minutes
15:13:52 <kaz> s/@@@/as PLH mentioned within his message to the Chairs, we're encouraged to use the group Calendar to manage the WG calls. However, we need to confirm the calendar entries because it seems some of the entries are strange. Also we have similar information on the Wiki and the Marketing page as well. So should clarify how to deal with them too./
15:14:06 <kaz> rrsagent, make log public
15:14:10 <kaz> rrsagent, draft minutes
15:14:11 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:15:00 <kaz> i|kaz:|-> https://lists.w3.org/Archives/Member/chairs/2023JanMar/0044.html PLH's message (member-only)|
15:15:17 <kaz> -> https://www.w3.org/2023/01/25-wot-td-minutes.html Jan-25
15:15:24 <kaz> rrsagent, draft minutes
15:15:25 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:15:49 <kaz> i/as PLH/scribenick: kaz/
15:15:49 <kaz> rrsagent, draft minutes
15:15:50 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:16:43 <kaz> present+ Cristiano_Aguzzi, Tomoaki_Mizushima
15:16:49 <kaz> rrsagent, draft minutes
15:16:50 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:17:21 <Ege> sk: we need to remove details for the TD and Binding Templates charters
15:17:42 <Ege> ... they need to go to another document
15:18:57 <Ege> kaz: I will add some of my sentences to the binding minutes
15:19:00 <Ege> sk: any objections?
15:19:05 <Ege> sk: minutes are approved
15:19:56 <Ege> topic: TD Charter Items
15:20:21 <Ege> ek: I will do the detail removal once the PR is merged
15:22:20 <kaz> q+
15:23:19 <kaz> ack k
15:23:53 <Ege> ek: I will add some new items such as virtual things and what is also in my comment above
15:24:07 <kaz> q+
15:24:07 <Ege> sk: we can merge now and remove the details later on
15:24:12 <cris_> q+
15:24:15 <Ege> sk: any objections to merge this?
15:24:53 <kaz> ack k
15:24:53 <Ege> kaz: merging is fine, we should not remove but find where to put the details
15:25:04 <kaz> s/fine,/fine, but/
15:25:11 <JKRhb> JKRhb has joined #wot-td
15:25:24 <kaz> s/remove/through the details away.
15:25:49 <kaz> s/but find/So we should find/
15:25:55 <Ege> ca: how should we review this?
15:26:22 <Ege> sk: we will evaluate everything once they are here
15:26:37 <kaz> q?
15:26:41 <kaz> ack c
15:26:42 <kaz> q+
15:27:00 <Ege> sk: there will be a separate repo where the charter will live
15:27:35 <kaz> ack k
15:30:28 <Ege> sk: we have a similar PR for the binding templates
15:30:51 <Ege> sk: we can merge it like the TD PR. We need to summarize the work items and move details somewhere else
15:31:52 <Ege> sk: there are merge conflicts
15:32:01 <Ege> ek: I can resolve and merge it if there are no complaints
15:32:22 <kaz> i/we have/kaz: will create a separate repo for further discussion, and try to move the remaining PRs to that repo. To be honest, it would be easier to merge all the remaining PRs right away, and move the updated HTML to that separate repo, though :)/
15:32:26 <kaz> q?
15:32:26 <Ege> sk: I hear no complaints
15:32:57 <kaz> rrsagent, draft minutes
15:32:59 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:33:34 <kaz> i|I will do the detail|subtopic: PR 1063|
15:33:52 <kaz> i|I will do the detail|-> https://github.com/w3c/wot/pull/1063 wot PR 1063 - TD Work Items|
15:34:02 <Ege> topic: Thing Description
15:34:29 <kaz> i|we have a similar|subtopic: PR 1065|
15:34:39 <Ege> sk: you must have seen that the root url has td 1.1 version now
15:34:55 <kaz> i|we have a similar|-> https://github.com/w3c/wot/pull/1065 wot PR 1065 - WG Charter - Binding Templates|
15:34:59 <kaz> q+
15:35:18 <Ege> q+
15:35:22 <kaz> i|w need to|scribenick: Ege|
15:35:35 <Ege> sk: so you need to know the URL in advance
15:36:25 <dape> q+
15:36:29 <Ege> ... our bibliography also self links
15:36:51 <kaz> -> https://www.w3.org/2005/05/tr-versions version guide
15:37:56 <Ege> kaz: we have version management guide
15:38:08 <Ege> ... you can also see all the specifications
15:38:59 <Ege> ... we should understand that first, then agree on a policy and make sure to use dated urls
15:39:48 <kaz> s/all the specifications/all the specifications via the "History" link within the spec/
15:40:02 <kaz> s/management guide/management guide, and this is the proper behavior./
15:40:14 <kaz> s/we should/in addition, we should/
15:40:22 <kaz> s/in addition, //
15:42:30 <kaz> s/on a policy and/on a policy (and apply the policy all the WoT specs equally), and/
15:42:38 <Ege> ek: It is trivial to add a link, we can agree on a policy
15:42:40 <kaz> s/dated urls/dated URLs for reference purposes./
15:42:48 <kaz> q?
15:42:50 <kaz> ack k
15:42:51 <kaz> ack e
15:42:53 <kaz> ac d
15:42:58 <kaz> s/ac d//
15:43:00 <kaz> ack d
15:43:21 <kaz> rrsagent, draft minutes
15:43:22 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:43:35 <Ege> kaz: also 1.0 is an obsolete document once 1.1 rec is published
15:43:55 <kaz> q+
15:43:58 <Ege> ek: we can add (obsolete) in the text
15:44:15 <Ege> dp: I find it wrong that a CR version is replacing a REC
15:44:22 <kaz> s/we need to remove details/scribenick: Ege/
15:44:27 <kaz> q?
15:44:29 <Ege> ... once we reach 1.1 REC, this is fine but now it is wrong
15:44:29 <kaz> s/we need to remove details/scribenick: Ege/
15:44:32 <dape> ack dape
15:44:32 <kaz> rrsagent, draft minutes
15:44:33 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:45:41 <kaz> s/sk: scribenick: Ege/sk: we need to remove details/
15:45:49 <kaz> i/we need to remove details/scribenick: Ege/
15:45:49 <kaz> rrsagent, draft minutes
15:45:50 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:46:04 <Ege> dp: this is probably the same in arch document
15:47:17 <Ege> kaz: CR is also a stable document so from process point of view, it is fine to replace the REC 1.0 with CR 1.1
15:47:20 <sebastian> q?
15:47:24 <kaz> ack k
15:47:57 <kaz> s/CR is also a/Right. On the other hand, please remember that CR is already a/
15:48:14 <Ege> topic: TD PRs
15:48:50 <Ege> PR 1684
15:48:50 <Ege> https://github.com/w3c/wot-thing-description/pull/1684
15:49:41 <kaz> s/ so from process point of view, it is fine to replace the REC 1.0 with CR 1.1/. So it's reasonable to use the latest CR draft for the canonical URL instead of the old REC from the W3C Process viewpoint./
15:49:47 <Ege> sk: this PR fixes as much as possible until TD 2.0
15:50:18 <kaz> q?
15:50:18 <kaz> rrsagent, draft minutes
15:50:19 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:50:25 <Ege> ca: also this fixes some CI pipeline issues
15:50:34 <Ege> sk: you can see that it only affects the semantics
15:51:06 <kaz> i/you must have/subtopic: TD version management/
15:51:08 <Ege> sk: so we can merge it
15:51:20 <kaz> rrsagent, draft minutes
15:51:22 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:51:58 <kaz> s/topic: TD PRs/subtopic: PR 1684/
15:52:00 <kaz> rrsagent, draft minutes
15:52:01 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:52:56 <kaz> s/https/-> https/
15:53:10 <kaz> s/1684/1684 PR 1684 - Fix shacl, context and ontology/
15:53:13 <kaz> rrsagent, draft minutes
15:53:14 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:53:51 <kaz> rrsagent, draft minutes
15:54:22 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:54:28 <cris_> q+
15:54:44 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1712 PR 1712 - Add table numbers and captions using new respec option
15:54:47 <kaz> rrsagent, draft minutes
15:54:48 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:54:55 <cris_> ack c
15:54:55 <Ege> subtopic: PR 1712
15:54:59 <Ege> https://github.com/w3c/wot-thing-description/pull/1712
15:55:14 <Ege> ek: I get errors again, the captions are the same
15:55:17 <kaz> s/topic: TD Charter Items/topic: Charter Items/
15:55:36 <kaz> rrsagent, draft minutes
15:55:37 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:55:43 <Ege> ... cris can you have a look ?
15:55:43 <Ege> ca: yes I can
15:55:44 <Ege> sk: let's see next week
15:55:50 <Ege> subtopic: PR 1732
15:56:21 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1732 PR 1732 - Minor follow-up syntax alignments/fixes
15:56:27 <kaz> rrsagent, draft minutes
15:56:28 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
15:57:06 <Ege> sk: thank you daniel for the fixes
15:57:16 <Ege> subtopic: PR 1737
15:57:27 <Ege> https://github.com/w3c/wot-thing-description/pull/1737
15:58:22 <kaz> s/https/-> https/
15:58:49 <kaz> s/1737/1737 PR 1737 - Add explanation about observeproperty relationship/
15:59:35 <Ege> ek: This is just to add a statement that there is no guarantees
15:59:57 <Ege> sk: so a consumer does not necessarily get a notification of property changes
16:00:56 <Ege> sk: we can stop the TD part for now, Ege will do the binding templates now
16:01:06 <kaz> present+ Jan_Romann
16:01:27 <sebastian> bye
16:01:32 <cris_> bye!
16:01:37 <mjk> mjk has joined #wot-td
16:01:49 <cris_> topic: Protocol binding templates
16:02:03 <kaz> s/Protocol b/B/
16:02:11 <kaz> scribenick: cris_
16:02:20 <cris_> subtopic: Pull Requests
16:02:44 <cris_> s/subtopic:/topic:/
16:02:58 <cris_> subtopic: PR XXX
16:03:14 <cris_> ege: moving orphaned sections back into the main body
16:03:19 <kaz> rrsagent, draft minutes
16:03:20 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:03:56 <kaz> q+
16:03:56 <cris_> ege: today I tackled content-type section
16:04:00 <cris_> s/XXX/228/
16:04:34 <cris_> topic: japanese vendor view point
16:05:00 <cris_> kaz: it needs several improvements especially the core document.
16:05:15 <cris_> ... you wanted to know their availability to join this call
16:05:18 <cris_> ... I asked them
16:05:53 <cris_> ... 1. they are very interested in the discussion, but they are concerned about the current mechanism
16:06:02 <cris_> s/1.//
16:06:30 <cris_> ... 1. hosting a developer meeting up and evaluate together the current document
16:07:06 <cris_> 2. do a Japanese meetup, collect feedback and then report back
16:07:15 <kaz> s/vendor view point/vendor feedback/
16:07:23 <cris_> s/2./... 2./
16:07:32 <cris_> ege: good news
16:07:39 <cris_> ... we could start with the developer meetup
16:08:04 <cris_> ... after that we can start welcome them our calls
16:08:06 <cris_> ... would it work?
16:08:44 <cris_> kaz: Mizushima-san is already working on a Japanese meetup
16:08:56 <cris_> ... it will be held in February
16:09:18 <cris_> ... so I would recommend to first wait and get an initial feedback
16:09:34 <cris_> ... later we can organize a second global meetup
16:09:43 <cris_> mizushima: I don't have a date yet
16:09:47 <cris_> kaz: true
16:09:55 <cris_> ege: after the 15th ?
16:10:11 <cris_> ... so that we can have a deadline to get a better document
16:10:14 <cris_> kaz: not sure
16:10:21 <cris_> ege: ok then it's asap
16:10:31 <cris_> ... but that's a great news
16:10:32 <kaz> s/2. do a/... 2. do a/
16:10:38 <kaz> rrsagent, draft minutes
16:10:39 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:10:53 <cris_> topic: PR
16:11:01 <cris_> subtopic: PR 228
16:11:13 <kaz> s/topic: Pull Requests//
16:11:14 <cris_> ege: This PR fits well in the discussion about the improvements
16:11:20 <kaz> s/topic: PR//
16:11:42 <cris_> ege: improved the section structure
16:11:42 <kaz> rrsagent, draft minutes
16:11:43 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:12:31 <kaz> s/topic: japanese vendor feedback/subtopic: Japanese vendor's feedback/
16:12:34 <cris_> <ege shows changes about content-types>
16:13:06 <kaz> rrsagent, draft minutes
16:13:08 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:13:41 <kaz> subsubtopic: test
16:13:43 <kaz> rrsagent, draft minutes
16:13:45 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:14:25 <kaz> s/sub 228//
16:14:28 <dape> q+
16:14:31 <cris_> ege: any questions?
16:14:33 <kaz> ack k
16:14:43 <kaz> s/topic: PR/subtopic: PR 228/
16:14:46 <kaz> rrsagent, draft minutes
16:14:47 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:14:53 <kaz> ack d
16:14:59 <cris_> dape: quick note: last example have contentType in the wrong place
16:15:06 <cris_> ege: yeah, I can quickly fix it
16:15:07 <kaz> s/subsubtopic: test//
16:15:12 <kaz> rrsagent, draft minutes
16:15:13 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:15:19 <Ege> q?
16:15:22 <cris_> q+
16:16:22 <kaz> ack cr
16:16:51 <cris_> cris: maybe there are too many examples about different content types?
16:17:15 <dape> q+
16:17:15 <kaz> i|This PR fits|-> https://github.com/w3c/wot-binding-templates/pull/228 PR 228 - Temporary Section Reorg - Part 2: Payloads|
16:17:45 <cris_> ege: it is nice to have multiple examples
16:17:50 <mjk> q?
16:18:22 <dape> ack dape
16:18:33 <cris_> dape: I think I see the point, maybe it is enough to a list of different content-types without ripeting the form
16:18:39 <cris_> ege: I see, that make sense
16:18:53 <cris_> cris: agree
16:19:00 <cris_> ege: any other opinion ?
16:20:42 <cris_> ... I would still have single json example with a list of possible content-types
16:21:09 <cris_> subtopic: PR 224
16:21:24 <kaz> -> https://github.com/w3c/wot-binding-templates/pull/224 PR 224 - Add initial version of feedback survey
16:21:57 <cris_> ege: it would be helpful to gather feedback from devs
16:22:07 <cris_> ... would it relevant for the Japanese meetup?
16:22:09 <kaz> q+
16:22:27 <cris_> kaz: at the moment I am not sure
16:23:15 <cris_> ... in any case we should discuss what should be described by the core document a priori and then we can ask feedback.
16:23:42 <cris_> ... current draft includes important pieces but it is kind of a cheatsheet
16:23:57 <cris_> ... we need more explanatory text
16:24:34 <cris_> ... the survey would be too tough for external people
16:24:51 <cris_> ... even if the survey per se is a good idea.
16:25:28 <kaz> q-
16:26:23 <kaz> ... so we should think about this kind of questions as part of the possible Developer Meetup for Binding Templates
16:26:34 <kaz> i/so we/scribenick: kaz/
16:26:40 <kaz> scribenick: cris_
16:26:44 <kaz> rrsagent, draft minutes
16:26:45 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:27:08 <cris_> ege: can we do both ? events + survey?
16:27:49 <cris_> kaz: we can ask participants of the online meetup to provide further feedback in a survey
16:28:37 <cris_> ege: about the PR are you ok for merginng?
16:28:52 <cris_> ... ok, then I'll merge it but without sending it
16:29:16 <kaz> s/of the/in the/
16:29:40 <kaz> rrsagent, draft minutes
16:29:41 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:29:47 <cris_> topic: Issues
16:29:54 <cris_> subtopic: issue 227
16:30:04 <cris_> ege: we need a json schema for each protocol binding
16:30:14 <cris_> ... Jan are you going to work with CoAP?
16:30:24 <cris_> jan: yes, I will
16:30:45 <cris_> subtopic: Issue 230
16:31:03 <cris_> ege: is somebody free to create a jsonschema for mqtt?
16:31:06 <cris_> cris: I can
16:31:21 <cris_> subtopic: Issue YYY
16:31:37 <cris_> ege: tricky because is coming from an external vocabulary
16:31:41 <kaz> s/topic: Issues//
16:32:15 <cris_> q+
16:32:15 <dape> q+
16:32:21 <kaz> i|we need a json|-> https://github.com/w3c/wot-binding-templates/issues/227 Issue 227 - JSON Schema for CoAP Vocabulary|
16:32:28 <mjk> q?
16:32:51 <kaz> i|is somebody|-> https://github.com/w3c/wot-binding-templates/issues/230 Issue 230 - JSON Schema for MQTT Vocabulary|
16:33:17 <kaz> rrsagent, draft minutes
16:33:18 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
16:33:31 <cris_> ege: how should we treat RDF data, in the json schema?
16:33:53 <cris_> cris: you mean how to use keyword that are not in the RDF ontology?
16:34:04 <kaz> q+
16:34:15 <cris_> ege: no, more about if we should use all the keywords or just the ones useful for us
16:34:27 <cris_> dape: reduce it to a sanity check
16:34:40 <cris_> ... do not list all the precise values for HTTP
16:35:43 <Ege> ack c
16:35:44 <Ege> ack d
16:35:45 <dape> ack dape
16:36:07 <cris_> kaz: we can talk with some semantic web experts
16:36:14 <cris_> ... from the other w3c groups
16:36:21 <cris_> ege: we can, but about what?
16:36:32 <cris_> kaz: if they know more about this kind of vocabulary
16:36:46 <cris_> ege: we can do it
16:37:20 <cris_> kaz: we should refer to external vocabulary as much as possible
16:37:34 <cris_> ... that's why I'm suggesting to ask
16:38:05 <cris_> ege: it is not vocabulary related by it is more about the json schema related to the thing description
16:38:29 <cris_> kaz: json schema is used for validating the vocabulary in this context ?
16:38:43 <cris_> ege: not really, it is more about validating our data
16:41:23 <cris_> kaz: would we want to refer to specific ontology terms?
16:41:45 <cris_> ... if jsonschema is complicated, semantic experts can help us
16:42:05 <cris_> ege: they would probably recommend SHACL validation
16:42:10 <cris_> ... it would be too much
16:42:25 <cris_> ... we need a simpler mechanism with json schema
16:45:09 <cris_> kaz: what do you mean by validation ?
16:45:43 <cris_> ege: coming from thing description
16:48:25 <cris_> kaz: should explain how a TD that contains protocol binding keywords should be validated
16:48:35 <cris_> ege: ok, any other points?
16:52:19 <cris_> kaz: are we  asking external developers to write protocol specific binding validation them self?
16:52:32 <cris_> ege: correct, but it is kind of tough
16:52:48 <cris_> s/but it is kind of tough//
16:53:03 <cris_> kaz: but it is a good amount of work
16:53:11 <cris_> ege: but we can collaborate
16:53:20 <cris_> kaz: still it is a bit too much
16:56:02 <cris_> ... the core document should focus more on the mechanism of the bindings
16:56:13 <cris_> ege: schema is helpful
16:56:48 <cris_> kaz: the reason I'm concerned it is also testability
16:57:15 <cris_> ... how are we going to test also this additional requirement?
16:57:23 <cris_> ... manually or automatically
16:59:00 <cris_> ege: maybe this discussion should be held another time
16:59:07 <cris_> kaz: I have another point of view
16:59:24 <cris_> ... we should actually discuss it right now,
17:00:06 <cris_> ... going forward on this direction would not be right
17:00:30 <cris_> ege: I don't understand why we should not doing it on this charter
17:00:52 <cris_> kaz: why do we need add new description to the main body?
17:01:01 <cris_> ... we should finalize the document
17:01:47 <cris_> ege: this is to improve the readability of the core document
17:02:09 <kaz> rrsagent, draft minutes
17:02:10 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
17:03:04 <kaz> s/YYY/229/
17:03:31 <kaz> i|tricky|-> https://github.com/w3c/wot-binding-templates/issues/229 Issue 229 - JSON Schema for HTTP Binding Terms|
17:03:35 <kaz> [adjourned]
17:03:39 <kaz> rrsagent, draft minute
17:03:39 <RRSAgent> I'm logging. I don't understand 'draft minute', kaz.  Try /msg RRSAgent help
17:03:48 <kaz> rrsagent, draft minutes
17:03:49 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/01-wot-td-minutes.html kaz
17:56:33 <JKRhb> JKRhb has joined #wot-td
20:28:56 <Zakim> Zakim has left #wot-td