14:03:58 RRSAgent has joined #wot-td 14:04:02 logging to https://www.w3.org/2023/03/29-wot-td-irc 14:04:04 meeting: WoT-WG - TD-TF 14:04:14 rrsagent, make log public 14:04:19 rrsagent, draaft minutes 14:04:19 I'm logging. I don't understand 'draaft minutes', kaz. Try /msg RRSAgent help 14:04:21 luca_barbato has joined #wot-td 14:05:36 JKRhb has joined #wot-td 14:05:42 https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf 14:07:47 kaz are you joining? 14:12:54 https://meet.google.com/xpp-hddp-vid 14:14:41 scribenick: JKRhb 14:14:55 topic: Minutes Review 14:15:32 ek: We did a lot of PRs 14:15:54 ... we had the whole thing about TF lead, which did not do its entirety 14:16:14 ... then we looked at the charter, changed one work item, looked at the slides for the dev meeting 14:16:27 ... in the Binding Templates section, we looked at the figures and terms 14:17:20 q+ 14:19:14 ack k 14:20:31 ... influenced by different types of bindings, looked at the CoAP binding and cooperation with SDOs 14:20:31 i|We did a|-> https://www.w3.org/2023/03/22-wot-td-minutes.html Mar-22| 14:21:00 ... then we discussed PRs regarding TD consumption, we will have follow-ups today 14:21:23 ... discussed simple PRs for the TD repo, improving formatting/table numbers 14:21:51 ... minutes look good, there are only some discrepancies regarding the names 14:22:10 ... also a bit weird that some chat messages are in the minutes, should be deleted 14:23:22 kaz: I will include my comment regarding the TF lead in the minutes 14:23:38 ek: Afterward, minutes are approved 14:23:48 topic: TF Lead 14:24:09 ek: What we've agree on last time was that I am taking over the TF lead 14:24:20 ... since Sebastian is occupied for the last couple of months 14:24:38 q+ 14:24:39 fine by me 14:24:46 ... so I would propose that I take over the lead until the end of April, then we make a formal discussion 14:25:29 kaz: I think, Sebastian should have asked beforehand, but I am personally okay with you taking over his role as a temporary TF lead until the end of April, I assume? 14:25:38 ek: I would say end of April to be sure 14:26:26 kaz: Then I will propose that we make the resolution that you will take over the TF lead over the course of April, just to clarify the procedure, if the others are fine with that 14:26:32 mk: I am okay with that 14:26:47 ek: I'll prepare a resolution 14:26:57 kaz: You can then report it back to the main call 14:26:57 PROPOSED RESOLUTION: Ege Korkan will be interim TF Lead for TD+Binding call until end of April 14:27:02 mjk has joined #wot-td 14:27:09 present+ Kaz_Ashimura, Ege_Korkan, Cristiano_Aguzzi, Jan_Romann, Luca_Barbato, Michael_Koster, Tomoaki_Mizushima 14:27:20 ek: Does it look okay, Kaz? 14:27:23 kaz: Yes 14:27:39 RESOLUTION: Ege Korkan will be interim TF Lead for TD+Binding call until end of April 14:27:42 ek: Any objections to the proposed resolution? 14:27:50 jr: I am okay with it as well 14:28:33 ek: April 26 is the last call, on May 3 there is going to be a decision 14:28:57 rrsagent, draft minutes 14:28:58 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 14:29:05 kaz: Fine, as I mentioned having two TF leads from the same company is not ideal by the way 14:29:05 topic: PRs 14:29:09 subtopic: PR 266 14:29:14 rrsagent, make log public 14:29:28 ek: I have been working on a reorganization of the introduction and section 4 14:29:39 chair: Ege 14:29:44 ... there is a big diff since content has been moved around 14:30:03 s|https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf|| 14:30:12 s|kaz are you joining?|| 14:30:15 ... (shows the diff in the rendered document) 14:30:32 ... some content has been moved around, as you can see 14:30:34 s|https://meet.google.com/xpp-hddp-vid|| 14:30:42 ... I also applied some fixes to the introduction 14:30:51 ... I added three introduction paragraphs 14:31:01 ... this is very close to the Architecture 14:31:19 ... (shows the respective section 7 in the Architecture document) 14:31:29 q+ 14:31:40 ... I think this makes it a bit nicer, the rest is what we have talked about last time 14:31:44 https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/pull/266.html 14:32:25 ... I am showing the local version since the rendered web version does not render pictures correctly 14:32:29 https://deploy-preview-266--wot-binding-templates.netlify.app/ 14:32:46 ... however, the netlify version shows them 14:33:00 s|https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/pull/266.html|| 14:33:04 ... (pastes a link to the netlify version into the IRC) 14:33:10 ... what does everybody think? 14:33:12 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#March_29.2C_2023 14:33:35 s|https://deploy-preview-266--wot-binding-templates.netlify.app/|| 14:33:44 ... another thing I did changing the platform bindings to the same structure as the protocol bindings 14:33:45 i|pastes|-> https://deploy-preview-266--wot-binding-templates.netlify.app/ preview| 14:33:54 s/I did/ I did was/ 14:34:09 q+ 14:34:26 ack k 14:34:31 kaz: This is a good starting point for further discussions, thank you 14:34:38 No objections, merged 14:34:42 rrsagent, make log public 14:34:46 rrsagent, draft minutes 14:34:47 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 14:34:54 subtopic: PR 269 14:35:01 ek: This is another PR that is changing content around 14:35:15 ... previously, the ontology files were into a separate folder 14:35:26 ... this PR moves them to the respective protocol binding folders 14:35:34 ... this makes them a bit easier to manage 14:36:03 mk: This is what we'll expect a registry to work like, this is the right direction for that 14:36:12 q+ 14:36:26 ek: (adds a comment) 14:36:42 ... another positive aspect is that protocol bindings will become self-contained 14:37:29 ca: I am not against this change, however, if we take this approach we might be able to further simplify the structure as we did with CoAP 14:37:31 q? 14:37:49 i|his is another PR|-> https://github.com/w3c/wot-binding-templates/pull/269 PR 269 - Move ontologies into individual protocol binding folders 14:38:28 q+ 14:38:43 ack cri 14:38:52 ... at the moment, this will only be relevant for Modbus, in the case of MQTT we did a whole description. We might need to add an explainer for this decision 14:39:22 kaz: Maybe this is an easier direction for specification generators, however, we should think about how to export the ontologies to the public later 14:39:40 ... so that later, developers from all over the world can refer to these ontologies 14:39:45 q+ 14:39:59 ack k 14:40:04 ... if we want to expose them via w3c.org, we need to think about how to that 14:40:18 s/MQTT we did/MQTT we did not/ 14:40:50 s/w3c.org/w3.org/ 14:41:15 ek: I would imagine that the public ontologies would not necessarily be exposed under w3.org 14:41:33 q? 14:41:38 ... however, the content negotiation needs to be considered 14:41:52 rrsagent, draft minutes 14:41:53 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 14:43:04 mk: We are setting a bigger set of requirements for these documents 14:43:13 ackmjk 14:43:15 i|I have been working on|-> https://github.com/w3c/wot-binding-templates/pull/266 PR 266 - Reorganize intro and section 4| 14:43:32 s/ackmjk/ack mjk 14:43:33 s/ackmjk// 14:43:35 ack mjk 14:43:39 merged 14:43:44 ek: (completes his comment) 14:43:48 rrsagent, draft minutes 14:43:50 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 14:43:56 ... merges the PR 14:44:01 subtopic: PR 270 14:44:12 ek: This is an editorial change, I would simply merge this 14:44:17 s|s/ackmjk//|| 14:44:23 ... any objections to merging this? 14:44:27 Merged 14:44:34 subtopic: PR 273 14:44:50 i|This is an|-> https://github.com/w3c/wot-binding-templates/pull/270 PR 270 - remove duplicate "Figure"| 14:44:51 ek: Another simple PR 14:45:13 ... Daniel simply corrected the links, that were pointing to github.io previously 14:45:20 i|Another|-> https://github.com/w3c/wot-binding-templates/pull/273 PR 273 - Remove GitHub io links for specs like Arch and TD| 14:45:27 q+ 14:45:39 kaz: Just to make sure, is that for the main body text? 14:45:46 ek: It's to the index.html 14:46:08 kaz: Technically, all specifications should be linked via the reference link, right? 14:46:10 ek: Yes 14:46:16 s/It's/Yes, it's/ 14:46:22 ... (merges the PR) 14:46:30 subtopic: PR 277 14:46:47 ek: This introduces the new ReSpec table numbering feature 14:46:56 i|This|-> https://github.com/w3c/wot-binding-templates/pull/277 PR 277 - Add table numbering and captions| 14:46:58 rrsagent, draft minutes 14:47:00 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 14:47:08 ... the PR basically adds this to the document 14:47:08 q? 14:47:08 ack k 14:47:10 ... merging 14:47:11 Merged 14:47:23 subtopic: PR 268 14:47:39 ek: Last week we talked about this topic, the consumption of TDs with bindings 14:48:05 ... this PR adjusts the document that consumers don't need to use JSON Schema but can also validate programmatically 14:48:05 i|Last|-> https://github.com/w3c/wot-binding-templates/pull/268 PR 268 - Add TD Consumption step| 14:48:11 rrsagent, draft minutes 14:48:13 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 14:48:25 https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/pull/268.html#using-a-td-with-a-protocol-binding-template-subspecification 14:49:07 ... also included definition links, but the validation is the main change 14:49:21 q? 14:49:25 ... Luca, I think you had a comment regarding JSON Schema, are you fine with this version? 14:49:27 -> https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/268/c314cbd...f656e04.html#using-a-td-with-a-protocol-binding-template-subspecification diff - 4.1.3 Using a TD with a Protocol Binding Template Subspecification 14:49:29 q+ 14:49:34 lb: Looks good 14:50:08 kaz: Just a minor question: Is it fine as a general policy to use "TD" in a section title? 14:50:20 I would expand the name 14:50:51 ek: Good point, I will write it out 14:51:32 kaz: Another point, as raised by Ben: the title uses "Binding Template", should be discussed 14:52:03 ek: Needs to be discussed when the people are present, for now I kept it consistent 14:52:40 ek: (Adds a comment to the issue) 14:52:47 ... (merges the PR) 14:52:49 Merged 14:52:50 s/discussed/discussed. For the moment, it's fine to say "Protocol Binding Template" at section 4.1.3 within section 4.1, though./ 14:53:13 subtopic: PR 232 14:53:16 s/consistent/consistent with the current terminology./ 14:53:47 s/PR 232/Issue 232/ 14:53:58 -> https://github.com/w3c/wot-binding-templates/issues/232 Issue 232 - Next WD Path 14:54:05 q+ 14:54:06 rrsagent, draft minutes 14:54:07 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 14:54:13 ack k 14:54:23 ek: After we are now done with a lot of restructuring, we can now discuss how to proceed 14:55:12 mk: I think we decided that we need people to implement this, I think we have something that is almost ready for publishing 14:55:23 ... I think it is important to make some progress 14:55:34 ack mjk 14:56:09 ek: This is just related to the core document, there are ongoing discussions with the binding document 14:56:25 mk: This is the guidance we need when refactoring the other documents also 14:56:51 ek: Then I would say we make a resolution for the main call, then we can start the two week review process 14:57:17 ... applied some last fixes to PR 266, afterward we can proceed in this regard 14:57:35 ... (resolves merge conflicts) 14:58:27 q+ 14:59:28 s/No objections, merged/No objections, to be merged, bu need to resolve the conflicts./ 14:59:32 ack k 14:59:39 rrsagent, draft minutes 14:59:41 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 14:59:48 ... (now finally merges PR 266) 15:00:31 PROPOSAL: TF agrees to start the WD review process of the binding templates document 15:00:31 ... any objections or comments on the proposal? 15:01:02 -> https://github.com/w3c/wot-binding-templates/pull/266 PR 266 - Reorganize intro and section 4 has been merged after resolving the conflicts 15:01:02 ... If not, then we can make it into a resolution 15:01:02 PROPOSAL: TF agrees to start the WD review process of the binding templates document of two weeks 15:01:11 ... I will add "of two weeks" at the end 15:01:17 s|-> https://github.com/w3c/wot-binding-templates/pull/266 PR 266 - Reorganize intro and section 4 has been merged after resolving the conflicts|| 15:01:26 PROPOSAL: TF agrees to start the 2 week Working Draft review process of the binding templates document 15:01:34 ... or rather "two week WD review process" 15:01:38 i|now finally|-> https://github.com/w3c/wot-binding-templates/pull/266 PR 266 - Reorganize intro and section 4 has been merged after resolving the conflicts| 15:01:38 ... any objections? 15:01:41 rrsagent, draft minutes 15:01:42 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 15:01:48 RESOLUTION: TF agrees to start the 2 week Working Draft review process of the binding templates document 15:01:50 There are no obejctions, resolution has been adopted 15:02:04 s/obejections/objections/ 15:02:23 s/Working Draft// 15:02:30 kaz: This is a Working Group Note, not a Working Draft, though 15:02:31 rrsagent, draft minutes 15:02:33 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 15:02:55 s/though/though (Kaz removed "Working Draft" from the resolution)/ 15:02:57 rrsagent, draft minutes 15:02:59 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 15:03:06 The resolution text is adjusted 15:03:28 [adjourned] 15:03:32 rrsagent, draft minutes 15:03:33 I have made the request to generate https://www.w3.org/2023/03/29-wot-td-minutes.html kaz 15:08:19 luca_barbato has left #wot-td 15:21:01 JKRhb has joined #wot-td 15:24:23 dape has joined #wot-td 15:24:32 q+ 15:31:20 q- 15:31:28 dape has left #wot-td 16:21:22 Mizushima_ has left #wot-td 17:44:51 Zakim has left #wot-td