15:03:08 <RRSAgent> RRSAgent has joined #wot-td
15:03:12 <RRSAgent> logging to https://www.w3.org/2023/02/22-wot-td-irc
15:03:13 <Ege> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#February_22.2C_2023
15:03:58 <dape> dape has joined #wot-td
15:04:19 <mjk> mjk has joined #wot-td
15:04:37 <kaz> q+
15:04:48 <kaz> meeting: WoT-WG - TD-TF
15:05:40 <JKRhb> JKRhb has joined #wot-td
15:06:27 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#February_22.2C_2023
15:07:46 <kaz> present+ Kaz_Ashimura, Ege_Korkan, Cristiano_Aguzzi, Daniel_Peintner, Jan_Romann, Luca_Barbato, Michael_Koster, Michael_McCool
15:09:09 <kaz> ack k
15:11:25 <mjk_> mjk_ has joined #wot-td
15:11:49 <kaz> q+
15:12:23 <kaz> topic: Minutes
15:12:42 <Ege> https://github.com/w3c/wot-charter-drafts/files/10745556/WoT_Binding_2.0.pdf
15:14:34 <kaz> -> https://www.w3.org/2023/02/15-wot-td-minutes.html Feb-15
15:14:40 <mjk_> topic: test related issues
15:14:57 <kaz> i|test|(link to the slides above added)|
15:15:01 <mjk_> #1758
15:15:04 <kaz> i|test|minutes approved|
15:15:56 <kaz> s/#1758/subtopic: PR 1758/
15:16:03 <mjk_> mm: "at risk" won't make it into the final PR anyway
15:16:08 <Ege> https://github.com/w3c/wot-thing-description/pull/1758
15:16:18 <Ege> q?
15:16:20 <Ege> ack k
15:16:31 <kaz> s/http/-> http/
15:16:37 <mjk_> PR 1758 merged
15:17:01 <kaz> s/1758/1758 PR 1758 - Updating at risk assertions in the main body/
15:17:13 <kaz> rrsagent, make log public
15:17:17 <kaz> rrsagent, draft minutes
15:17:19 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
15:17:45 <kaz> q+
15:18:48 <mjk_> kaz: we have already published a list of at risk features
15:19:04 <mjk_> mm: this will be marked as an update
15:19:49 <mjk_> kaz: we can't put that information in the editors draft
15:20:09 <mjk_> mm: we could remove it from the main draft
15:20:21 <mjk_> kaz: it's just a memorandum for us
15:21:55 <mjk_> ... we need to publish a new CR to update this informaton
15:21:55 <kaz> ack k
15:21:55 <mjk_> mm: we should delete the at-risk feature list from the draft
15:21:59 <Ege> https://github.com/w3c/wot-thing-description/issues/1773
15:22:05 <mjk_> ege: created an issue for this
15:22:47 <mjk_> ege: implementers please look at this as a source of at-risk items
15:23:38 <mjk_> topic: big scope discussion for new charter
15:23:40 <cris_> q+
15:23:58 <kaz> rrsagent, draft minutes
15:23:59 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
15:24:05 <mjk_> mm: recommend against a major redesign, suggest incremental improvement
15:24:05 <mjk_> ... for example, streaming
15:24:19 <kaz> chair: Ege
15:24:24 <mjk_> mm: are there issues for all the work items?
15:24:24 <kaz> regrets+ Sebastian
15:24:48 <mjk_> mm: for the charter we don't need a detailed list of work items
15:25:19 <Ege> q?
15:25:20 <mjk_> ... we want to fix the major problems with small improvements
15:25:26 <kaz> i/"at risk" won't/scribenick: mjk_/
15:25:29 <kaz> rrsagent, draft minutes
15:25:31 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
15:25:52 <luca_barbato> q+
15:25:56 <kaz> q+
15:25:58 <mjk_> cris: I agree, there are some issues with forms and operations need work
15:26:15 <mjk_> ... maybe some things will need a lot of redesign
15:26:36 <mjk_> ... we shouldn't limit ourselves artificially
15:26:47 <kaz> ack c
15:26:47 <mjk_> ... may want breaking changes
15:27:10 <mjk_> luca: agree, we may need to remove some items
15:27:42 <kaz> ack l
15:27:46 <mjk_> ... we should first remove what isn't working and then discuss what can be added
15:28:13 <mjk_> cris: for the charter we don't need to be specific
15:28:27 <kaz> i/Feb-15/scribenick: kaz/
15:29:11 <mjk_> kaz: the title of an issue should be "high level scope discussion" for this discussion
15:30:01 <McCool_> q?
15:30:01 <McCool_> q+
15:30:04 <mjk_> ... think about use cases to further extend industry deployment
15:30:13 <kaz> ack k
15:30:30 <mjk_> mm: there should be a use case for each feature
15:30:38 <kaz> s/an issue/this issue/
15:30:39 <Mizushima> +1 kaz
15:30:46 <mjk_> ... user stories also
15:30:53 <kaz> s/discussion"/description"/
15:31:08 <cris_> +1
15:31:10 <mjk_> q?
15:31:14 <McCool_> ack m
15:31:19 <kaz> s/think about/then regarding the content of this issue, we should think about/
15:31:32 <kaz> rrsagent, draft minutes
15:31:34 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
15:31:41 <cris_> q+
15:32:08 <mjk_> q+
15:32:34 <mjk_> ege: some things are not use case motivated
15:32:56 <kaz> ack cr
15:33:13 <mjk_> cris: we can't always rely on use cases
15:33:20 <kaz> q+
15:34:44 <kaz> mjk: we have use cases but still have bugs
15:34:54 <kaz> ... need general use cases on how to use TD
15:35:32 <kaz> ack m
15:35:35 <mjk_> ege: this is the question; are there large issues
15:35:54 <mjk_> mjk: agree, there are bugs in addition to use cases
15:36:51 <mjk_> kaz: sometimes the use cases are difficult to write down
15:37:16 <McCool_> q+
15:37:52 <mjk_> ... for example, TD without forms still needs a use case to inform how to implement it
15:37:56 <kaz> ack k
15:38:27 <cris_> q+
15:38:36 <mjk_> mm: we can use the form "as a", "I would like to", "in order to achieve"
15:38:37 <kaz> s/write down/write down. However, we still need use case description with user-side story for the required features./
15:39:08 <mjk_> ege: we need to differentiate between new features and improvements
15:39:36 <kaz> q+
15:39:39 <kaz> ack mc
15:39:48 <cris_> +1 for user stories
15:40:06 <kaz> ack cr
15:40:31 <JKRhb> rrsagent, draft minutes
15:40:32 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html JKRhb
15:40:56 <mjk_> cris: high level scope requires some more imagination, but we still need user stories
15:41:21 <mjk_> ... agree that we need to create issues for these user stories and use cases
15:41:44 <mjk_> q?
15:42:05 <mjk_> ege: agree that there should be a document with some template
15:42:56 <mjk_> kaz: there are even user stories driving bug fixes
15:44:57 <Ege> ack k
15:45:06 <mjk_> mk: agree, user perspective is part of both bug fixes and new features
15:45:25 <mjk_> sub-topic: naming discussion
15:46:16 <mjk_> ege: what do we call the different mechanisms involved in a binding?
15:47:13 <mjk_> ... tried to map out different concepts
15:47:37 <kaz> q+
15:48:09 <mjk_> ... core binding template document, protocol and payload bindings, profile documents, TD instances, and TM models
15:49:07 <mjk_> kaz: we need Ben's input to this discussion
15:49:48 <Ege> https://github.com/w3c/wot-charter-drafts/issues/14
15:49:51 <mjk_> ege: wil invite Ben Francis and schedule a time slot in the meeting
15:50:08 <mjk_> ... int he meantime, please review and comment on this issue
15:50:16 <mjk_> s/int he/in the
15:50:42 <mjk_> topic: publication schedule
15:51:14 <mjk_> ... how many weeks are needed for review?
15:51:19 <mjk_> kaz: 2 weeks
15:51:46 <kaz> s/for review/for the review by the WoT WG/
15:51:53 <mjk_> s/... how/ege: how
15:53:08 <mjk_> ege: update to schedule
15:54:18 <mjk_> ... add 2 week review period for binding templates after 5 weeks
15:54:54 <mjk_> topic: technical discussions
15:55:02 <kaz> rrsagent, draft minutes
15:55:03 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
15:55:19 <mjk_> sub-topic: json schemas for bindings
15:55:30 <mjk_> PR #237
15:55:45 <kaz> s/big scope discussion/High-level description/
15:56:02 <luca_barbato> q+
15:56:28 <dape> q+
15:56:33 <mjk_> ege: remove URI from the binding since it's in the context
15:56:34 <kaz> q-
15:57:00 <cris_> q+
15:57:04 <mjk_> luca: how will JSON schema validate this case?
15:57:22 <mjk_> ege: it uses a string pattern
15:57:35 <kaz> rrsagent, draft minutes
15:57:36 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
15:57:42 <cris_> qq+
15:57:57 <mjk_> luca: do we reject use of non-htv namespace?
15:58:11 <kaz> s|PR #237|-> https://github.com/w3c/wot-binding-templates/pull/237 PR 237 - Add JSON Schema for HTTP|
15:58:24 <mjk_> cris: these is a limitation of JSON schema and variable keys
15:58:30 <kaz> q+
15:58:34 <kaz> ack cri
15:58:44 <kaz> ack luca
15:58:48 <kaz> ack c
15:58:48 <Zakim> cris_, you wanted to react to kaz
15:59:03 <mjk_> luca: another option is to add a JSON-LD validation step
15:59:04 <kaz> rrsagent, draft minutes
15:59:05 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
15:59:27 <mjk_> q?
16:00:27 <mjk_> luca: would like to provide a way to prevent conforming instances from breaking things
16:01:16 <Ege> q?
16:01:18 <mjk_> ege: the consensus was that we should direct implementations to use the official namespace
16:02:04 <mjk_> dape: there could be a check on the external context
16:02:20 <mjk_> q?
16:02:31 <dape> ack dape
16:03:18 <mjk_> kaz: in 237 and 239 we have bigger question than binding templates, that also impacts TD itself
16:03:58 <mjk_> ege: agree, for example the geolocation issue is similar
16:04:49 <mjk_> kaz: maybe we could put the binding core back into the main TD document
16:05:03 <luca_barbato> q+
16:05:08 <cris_> q+
16:05:23 <kaz> ack k
16:06:14 <mjk_> luca: moving the description to the TD document makes sense and could be normative
16:06:32 <mjk_> ... if the registry is structured properly
16:07:04 <mjk_> cris: agree, it's a potential direction
16:07:09 <JKRhb> react to
16:07:17 <Ege> q?
16:07:21 <Ege> ack l
16:07:22 <Ege> ack c
16:07:28 <JKRhb> s/react to//
16:07:57 <mjk_> ege: will create an issue for discussion
16:07:57 <cris_> ack c
16:08:07 <cris_> cris: is not a bad idea to merge protocol binding templates into td
16:08:20 <mjk_> ... there is no technical reason to have a separate document, just size
16:08:22 <JKRhb> rrsagent, draft minutes
16:08:24 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html JKRhb
16:08:31 <mjk_> q?
16:08:54 <cris_> ... but I am not sure if we can technically merge it a recomandation into another charter wise
16:09:08 <cris_> mk: +1 only downside is the readability
16:09:26 <mjk_> mjk: +1, no technical reason except size
16:09:39 <kaz> rrsagent, draft minutes
16:09:40 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:10:02 <mjk_> luca: we could refactor into TM as a separate document to reduce the TD size
16:10:03 <cris_> luca: if the problem is the length of the main document, we can refactor it by moving TM out
16:10:08 <kaz> q+
16:10:09 <mjk_> q?
16:10:43 <mjk_> q+
16:10:47 <kaz> ack k
16:11:02 <kaz> i/is not a bad idea/scribenick: cris_/
16:11:04 <kaz> rrsagent, draft minutes
16:11:05 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:11:15 <cris_> mk: I think protocol binding can also be a sort of mapping between TM and TDs
16:11:20 <cris_> ege: intresting
16:12:04 <cris_> mk: we haven't yet document how to map abstract data structures into a payload structure
16:12:14 <cris_> ege: we still need work there
16:12:26 <mjk_> mjk: the payload binding may need TM references
16:12:26 <cris_> ... but protocols should be easy
16:12:43 <cris_> subtopic: PR 250
16:12:54 <cris_> ege: just mirroring TD spec
16:13:20 <dape> q+
16:13:23 <cris_> ... any objections?
16:13:29 <Ege> ack m
16:13:49 <cris_> dape: how you link the TD doc? are you point to the editor draft?
16:13:59 <cris_> ege: yes, you are right I need to update it
16:15:24 <cris_> ... ok now merging
16:15:40 <cris_> ... also merging PR 237
16:16:07 <cris_> subtopic: PR 241
16:16:10 <kaz> rrsagent, draft minutes
16:16:11 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:16:17 <cris_> ege: Jan worked on coap ontology and the render script
16:17:04 <cris_> ... changing the render script
16:17:18 <kaz> i|just mirror|-> https://github.com/w3c/wot-binding-templates/pull/250 PR 250 - Mention that the HTTP binding mirrors the TD spec HTTP Binding|
16:17:30 <cris_> ... I'd prefer to merge it cause is a dependency of other PRs
16:17:48 <cris_> jan: improves readability
16:18:14 <cris_> cris: +1
16:18:53 <kaz> rrsagent, draft minutes
16:18:54 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:19:00 <cris_> subtopic: PR 246
16:19:18 <kaz> i|Jan worked|-> https://github.com/w3c/wot-binding-templates/pull/241 PR 241 - Refactor render script|
16:19:42 <cris_> ege: this a good update, but we need to wait for klaus review
16:20:00 <kaz> i|this a|-> https://github.com/w3c/wot-binding-templates/pull/246 PR 246 - Generate CoAP vocabulary from RDF|
16:20:03 <cris_> jan: it is a starting point
16:20:08 <kaz> s/this a/this is a/
16:20:09 <cris_> ... we can regenerate the document
16:20:11 <kaz> rrsagent, draft minutes
16:20:12 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:20:45 <cris_> ... ontology still needs improvements and discussion about its future direction
16:21:08 <cris_> ege: the index.html does not really contain substantial changes
16:21:20 <cris_> ... it is more about tooling update
16:21:42 <cris_> ... I also asked to add Jan as editor
16:21:58 <cris_> +1
16:22:41 <cris_> ... if klaus approves the PR we can merge it without group meeting
16:22:55 <cris_> ... any other opinions?
16:23:03 <cris_> ... ok thank you Jan
16:23:15 <cris_> subtopic: PR 249
16:23:22 <cris_> ege: I've just created it
16:23:53 <cris_> ... it addresses an old temporary section about subprotocols
16:24:08 <cris_> ... we need to discuss if we need it
16:24:17 <cris_> ... the definition is a little bit fuzzy
16:24:23 <mjk_> q?
16:24:25 <cris_> ... but I didn't update it a simply move it
16:25:54 <cris_> ... I also added one sentence, explaning that can be explained in the binding document.
16:26:04 <mjk_> q?
16:26:13 <cris_> ... i.e. longpolling should be explained in the http binding
16:26:33 <Ege> ack d
16:26:33 <cris_> q+
16:26:37 <mjk_> ack d
16:26:45 <dape> ack dape
16:27:03 <mjk_> q+
16:27:20 <cris_> cris: I would create an issue to keep track of this new requirement for binding templates documents
16:27:41 <cris_> ege: yes
16:27:59 <cris_> ... coap is probably already mention it
16:28:30 <cris_> ack c
16:29:15 <cris_> mk: are we calling coap observe a subprotocol?
16:29:17 <cris_> ege: yes
16:29:33 <dape> dape has joined #wot-td
16:29:34 <cris_> mk: the meaning of subprotocol is ambiguous
16:29:38 <luca_barbato> q+
16:30:09 <cris_> ... for websockets it defines application protocols
16:30:17 <kaz> q+
16:30:21 <cris_> ... we should bound what a subprotocol can or cannot specify
16:30:23 <cris_> q+
16:30:23 <kaz> ack m
16:30:44 <cris_> ege: for websockets is kind of straightforward
16:31:04 <cris_> ... but for other protocols it gets weird because they have their semantics
16:31:23 <cris_> mk: exactly, http has less degrees of freedom
16:31:44 <cris_> ... which should figured out if the subprotocol meaning can be bounded
16:32:04 <cris_> ege: websocket is like tpc in that sense
16:32:12 <cris_> luca: I would remove subprotocol
16:32:33 <cris_> ... the form operation is not reach enough
16:32:46 <kaz> rrsagent, draft minutes
16:32:48 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:33:02 <mjk_> q?
16:33:06 <cris_> ... I would remove it and jus relay on the protocol binding
16:33:35 <kaz> s/ jus / just /
16:33:55 <kaz> s/relay on/rely on/
16:33:57 <kaz> ack luca
16:34:03 <cris_> luca: if it is just not just a tag
16:34:15 <mjk_> q+
16:34:16 <cris_> ... you need more vocabulary terms
16:36:14 <kaz> ack m
16:36:57 <luca_barbato> q+
16:37:26 <kaz> ack k
16:37:59 <cris__> cris__ has joined #wot-td
16:38:00 <kaz> kaz: OK with once removing the subprotocol feature
16:38:20 <mjk_> kaz: we could remove sub-protocol but need to describe the websocket use in different platforms
16:38:30 <kaz> s/kaz: OK with once removing the subprotocol feature//
16:38:37 <kaz> i/we could/scribenick: mjk_/
16:38:50 <kaz> rrsagent, draft minutes
16:38:52 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:38:58 <mjk_> cris: we should see if we can extend the form description to provide these descriptions
16:39:17 <mjk_> ... there is also a transport protocol question like MQTT over websockets
16:39:30 <mjk_> ... we need a way to describe these also
16:39:52 <mjk_> ege: this applies to RPC protocols in general
16:39:53 <Ege> q?
16:39:56 <Ege> ack c
16:40:22 <cris__> ack l
16:40:49 <cris__> ege: back to PR
16:40:54 <cris__> ... should we merge it?
16:40:57 <cris__> ... I would like so
16:41:03 <mjk_> ege: back to PR #249
16:41:13 <cris__> ... any objections?
16:41:16 <mjk_> ... any objection to merging?
16:41:20 <cris__> ege: go
16:41:20 <mjk_> ... merged
16:41:40 <cris__> subtopic: PR 251
16:41:48 <mjk_> scribenick: cris
16:41:51 <cris__> ege: getting rid of the appendixes
16:42:05 <mjk_> scribenick: cris__
16:42:39 <cris__> ege: we had a long section for binding properties
16:42:57 <cris__> ... but it explained good concepts
16:43:03 <cris__> ... in a easy format
16:43:21 <cris__> ... I kept thoes ideas
16:43:22 <cris__> ... and moved in the right section
16:43:55 <cris__> ... cris should review the PR because it has examples with the modbus
16:44:02 <cris__> q+
16:44:17 <cris__> ... it explains how binding  should really work
16:44:24 <cris__> ... I won't merge it today
16:44:27 <Ege> q?
16:45:23 <kaz> rrsagent, draft minutes
16:45:25 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:45:57 <kaz> i|getting rid|-> https://github.com/w3c/wot-binding-templates/pull/251 PR 251 - Temporary Section Reorg - Part 5: Interaction Patterns|
16:45:58 <mjk_> q?
16:45:59 <kaz> rrsagent, draft minutes
16:46:00 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:46:17 <cris__> cris: the examples are pretty concrete and they introduce a dependecy with the binding docs
16:46:32 <kaz> q+
16:46:35 <kaz> ack cr
16:46:47 <cris__> ... should we use a more abstract syntax? i.e. foo protocol binding
16:46:47 <cris__> ege: I see your point, but then is too abstract
16:46:54 <cris__> cris: yes indeed
16:47:16 <cris__> kaz: I would like to see a diagram to explain the concepts better
16:47:31 <Mizushima> +1 kaz
16:47:48 <cris__> ege: it should go to the introduction
16:48:20 <cris__> ... I can tackle it in the PR
16:48:20 <Ege> q?
16:48:22 <Ege> ack k
16:48:23 <cris__> ... any other ^
16:48:29 <cris__> s/
16:48:37 <cris__> s/^/?/
16:48:48 <cris__> ege: mkj can yuo have a look at it?
16:48:55 <cris__> mk: ok
16:49:17 <cris__> ege: there is still a lot to discuss but we need to move to TD
16:49:23 <cris__> Topic: Thing description
16:49:26 <Ege> https://github.com/w3c/wot-thing-description/pulls?q=is%3Apr+is%3Aopen+label%3AEditorial
16:49:38 <kaz> rrsagent, draft minutes
16:49:39 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:49:46 <cris__> ege: I create a PR and then cristiano took over
16:50:08 <cris__> ... the overall idea is to introduce captions
16:50:16 <cris__> ... to make it easer to refer the tables
16:50:32 <cris__> ... it create numbers
16:50:44 <cris__> ... so that we can refer to table
16:50:45 <cris__> ... there is no way to refer to the tables
16:51:03 <kaz> s/mkj/Koster, /
16:51:08 <kaz> s/can yuo/can you/
16:51:28 <cris__> ... you can't click the table
16:52:04 <cris__> q+
16:52:04 <dape> q+
16:52:04 <cris__> ... I think we can still merge it
16:52:33 <kaz> i|I create|subtopic: PR 1772|
16:52:50 <kaz> i|I create|-> https://github.com/w3c/wot-thing-description/pull/1772 PR 1772 - Add table numbers and captions using new respec option v.2|
16:53:02 <kaz> q+
16:53:06 <kaz> ack c
16:53:46 <cris__> cris: there is a workaround
16:53:52 <cris__> ege: it is good enough
16:54:08 <cris__> cris: about respec, I checked the code it easy to fix
16:54:33 <cris__> dape: remember that figures are not clickable either.
16:54:39 <kaz> ack d
16:54:39 <cris__> ege: true
16:54:55 <cris__> cris: +1
16:55:13 <Ege> q?
16:55:16 <cris__> ege: I would not stop the PR
16:55:37 <kaz> rrsagent, draft minutes
16:55:38 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
16:56:15 <cris__> dape: if we can fix it in the respec we can wait
16:56:30 <cris__> cris: it depends how much they are fast to approve PRs and ship it
16:56:43 <cris__> ege: I would merge the PR anyway
16:57:08 <cris__> kaz: examples have clickable links, we can take them as examples
16:57:50 <cris__> ... even though making resources clickable is good, but it is not worth too much work
16:57:53 <cris__> ege: yeah
16:58:05 <cris__> cris: yes, I agree
16:58:17 <cris__> ege: I looked around and tables are not used that much
16:58:39 <kaz> s/as examples/as examples. Also we can look into the other existing specifications by the other WGs./
17:00:30 <dape> q+
17:00:30 <kaz> q-
17:00:30 <cris__> ... I'd merge it and if there is an update we would have a follow up pr
17:01:01 <cris__> dape: I'm not objecting, but currently some table has the caption but others don't
17:01:12 <kaz> s/even though making resources clickable is good, but it is not worth too much work/However, please note that this is rather a "nice-to-have" kind of addition. So if it takes too long to see how to do that, we can simply live with the current status./
17:01:42 <kaz> rrsagent, draft minutes
17:01:43 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
17:02:09 <kaz> present+ Tomoaki_Mizushima
17:02:10 <cris__> ege: ok let's wait for the next week
17:02:30 <cris__> ege: ok than we are done
17:02:34 <cris__> ... any AoB ?
17:03:04 <cris__> [adjourned]
17:03:09 <kaz> rrsagent, draft minutes
17:03:10 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/22-wot-td-minutes.html kaz
18:09:52 <kaz> kaz has joined #wot-td