14:04:22 RRSAgent has joined #wot-td 14:04:26 logging to https://www.w3.org/2024/04/03-wot-td-irc 14:04:26 luca_barbato has joined #wot-td 14:04:31 meeting: WoT-WG - TD-TF Slot 1 14:04:50 present+ Kaz_Ashimura, Ege_Korkan, Luca_Barbato 14:05:04 present+ Mahda_Noura 14:05:12 chair: Ege, Koster 14:05:56 cris1 has joined #wot-td 14:07:28 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#April_3_and_4%2C_2024 14:08:51 ktoumura has joined #wot-td 14:09:51 present+ Mahda_Noura 14:10:32 present+ Kunihiko_Toumura 14:12:29 present+ Cristiano_Aguzzi, Michael_Koster 14:12:45 topic: agenda 14:12:59 ege: now we added a quick schedule point 14:13:16 ... to describe the overall plan for the next calls 14:13:30 topic: previous minutes 14:13:39 ege: we already reviewed it 14:14:02 ... do you have any objections? 14:14:12 ... minutes approved 14:14:23 i|now we|-> https://www.w3.org/2024/03/27-wot-td-minutes.html Mar-27| 14:14:39 topic: PRs 14:14:45 present+ Tomoaki_Mizushima 14:14:50 rrsagent, make log public 14:14:51 ege: we already merge a couple of easy PRs 14:14:54 rrsagent, draft minutes 14:14:56 I have made the request to generate https://www.w3.org/2024/04/03-wot-td-minutes.html kaz 14:15:17 ... the readme was updated with the correct links to the REC and main branch 14:15:27 ... I also explained why we are using prettier 14:16:18 i|the read|-> https://github.com/w3c/wot-thing-description/pull/1970 PR 1970 - Prettier Formatter Version alignment and GH Action| 14:16:28 ... any remarks on PR 1992 ? 14:16:45 q? 14:16:50 q+ 14:17:23 q+ 14:17:48 luca: tiny remark we can restrict the actions so that they apply only if something relevant changes 14:17:54 ... we can look at it later 14:18:11 ege: we have already a filter for it 14:18:18 i|the readme|-> https://github.com/w3c/wot-thing-description/pull/1992 PR 1992 - Small Readme Improvements| 14:18:26 luca: but that is the ignore for priettier 14:18:41 ... you can limit also the action activation 14:18:56 ege: right, created a issue 14:19:11 ack lu 14:19:59 mjk has joined #wot-td 14:20:05 kaz: about previous changes we might improve the text about branch 14:20:08 Tomo has joined #wot-td 14:20:17 ege: good point, updating right away 14:20:25 kaz: you might add also a link for the implementation report 14:20:30 ege: right 14:21:28 subtopic: PR #1993 14:21:38 ege: there is a respec error shown 14:21:49 ... it was my fault 14:22:08 ... it is really small change I updated an id 14:22:20 ... but there are some formatting changes too 14:22:28 ... I'm merging it 14:22:53 subtopic: Tool chain 14:23:01 i|there is|-> https://github.com/w3c/wot-thing-description/pull/1993 PR 1993 - Fix respec error on section id| 14:23:20 ege: we talked about two PRs last week 14:23:29 ... the first is 1989 14:23:51 ... I removed the requirements.md file 14:24:07 ... the content is under README.md in the toolchain folder 14:24:29 ... the rendered document contains the highlevel diagram 14:25:17 ... current source of truth consists of many document the goal of this work to transition to something leaner 14:25:25 https://github.com/w3c/wot-thing-description/blob/17f2973faa1a54397c7b1b4f1f659288c275d073/toolchain/README.md 14:25:28 ... then in the document there is a section about requirements 14:25:35 ... nothing changed there 14:25:52 ... we still need to think about the requirements of the Input resources 14:25:59 ... any questions? 14:26:01 q? 14:26:32 kaz: I think we should save the requirements.md file 14:26:54 ... I mean recorded in the minutes 14:27:00 q- 14:27:12 present+ Daniel_Peintner 14:27:22 https://github.com/w3c/wot-thing-description/blob/main/toolchain/requirements.md is being deleted and the content merged into the toolchain readme 14:29:03 ege: about the toolchain analysis file I updated the table with new entries and explanations about the each feature. 14:29:19 q? 14:29:21 ... we can work later on to add other points 14:29:24 q+ 14:29:34 ack 14:29:37 ack k 14:29:41 https://github.com/w3c/wot-thing-description/blob/ege-toolchain-highlevel/toolchain/tool-analysis.md 14:31:33 ege: there are some conflicts 14:31:38 ... I'll merge the PR later 14:31:57 ... probably something about enconding or line ending 14:32:40 q+ 14:32:42 ege: once we finalize the project management up and running we can tackle the issues regarding the toolchain. 14:32:47 ... any other points? 14:32:56 kaz: we are getting closer to the final goal 14:33:13 ... what to do next? 14:33:36 ege: the next small thing to do is filling the table in the tool-analysis.md 14:33:52 and at the same time we can start experimenting and publish the results 14:34:07 ... madha already has something preliminary 14:34:14 s/and/...and/ 14:35:38 ... from our first study it seems that linkML it is a good candidate 14:35:41 ... we can try it 14:35:48 ... and get a first feeling 14:36:16 q? 14:36:21 q- 14:36:30 q+ 14:36:34 rrsagent, draft minutes 14:36:36 I have made the request to generate https://www.w3.org/2024/04/03-wot-td-minutes.html kaz 14:36:43 cris: it is a good start 14:36:55 ... but the question is who is starting 14:37:08 q? 14:37:35 luca: if you have oneOf you can support Type/Type[] 14:38:09 ... the question is weather we like the output 14:38:17 mahda: true good point 14:38:31 ... it is supported also with post processing 14:38:43 luca: I looked at treeML and TreeLDR 14:38:59 s/treeML/linkML/ 14:39:13 ... LinkML seems better matained 14:39:31 ... however TreeLDR is maintained by someone closer to W3C 14:39:48 ... both tools have APIs for generations 14:40:02 ... it means that we can extend both libraries 14:40:03 present+ Jan_Romann 14:40:06 rrsagent, draft minutes 14:40:07 I have made the request to generate https://www.w3.org/2024/04/03-wot-td-minutes.html kaz 14:43:01 ege: we can start with LinkML 14:43:14 ... and presents the results within two weeks or so 14:43:23 q+ 14:43:29 ack l 14:43:29 ack l 14:44:00 kaz: which is the relationship between our toolchain and respec? 14:44:06 q+ 14:44:18 ... it would be better to combine somehow the toolchain with respec 14:44:35 ege: we will keep respec for sure 14:44:45 ack k 14:44:49 ... we haven't looked at bkeshed 14:45:01 s/bkeshed/bikeshed/ 14:45:19 ... let's keep track of this in a issue 14:45:45 luca: bikeshed makes easier to write specifications, it is something we can use but we need a single point of truth 14:46:21 ... we can have linkML files to be a SpT and then we can later configure the result with Bikeshed 14:47:13 s|which is the relationship between our toolchain and respec?|Maybe this is kind of overkill at the moment, but I've started to wonder about the relationship between our toolchain and ReSpec/Bikeshed.| 14:47:37 luca: I'd like to have bikeshed in the toolchain because it can digest MD files. 14:47:48 s/it would be better/Technically, it would be even nicer/ 14:47:51 ... however, it can not be the only tool 14:48:11 s/keep respec/keep using ReSpec/ 14:48:32 rrsagent, draft minutes 14:48:34 I have made the request to generate https://www.w3.org/2024/04/03-wot-td-minutes.html kaz 14:50:25 topic: Refectoring 14:50:50 ege: in particular it is about refactoring the binding mechanism 14:50:57 ... moving it to the TD spec 14:50:59 ... we have an issue 14:51:33 ... in particular we plan to move chapter 4 14:51:38 ... there are some overlaps 14:51:44 ... we need a simple plan 14:51:52 ... only the core document will be moved 14:52:06 ... there might be other working group documents that will be impacted 14:52:19 ... from an intial look we pinpointed some overlaps 14:52:31 i|in part|-> https://github.com/w3c/wot-thing-description/issues/1987 PR 1987 - Moving Binding Mechanism Text to TD| 14:52:50 ... we can start by copy&past into the TD spec between chaper 7 and 8 14:53:21 ... after this initial PR we can re-arrange the content to fit better 14:53:31 ... another way is to move bit by bit 14:53:34 q+ 14:53:45 ack l 14:53:49 ack l 14:55:53 ack c 14:56:15 q+ 14:57:36 cris: I like the plan A, but maybe we can put the binding section before 7 14:57:47 ege: yeah it might work 14:57:54 kaz: I agree with plan A too 14:58:05 ... we can later improve it in the TD calls 14:58:15 q+ 14:58:19 ack k 14:58:22 ... any favorite place for the new section? 14:58:54 luca: I don't have it really, which ever is faster. 14:59:01 ... just move the text 14:59:19 ... we can re-order that later 14:59:22 +1 15:00:06 ege: we can even re-evaluate the current ordering of the sections in the future 15:01:08 ... any other points? 15:01:26 [adjourned] 15:01:31 rrsagent, draft minutes 15:01:33 I have made the request to generate https://www.w3.org/2024/04/03-wot-td-minutes.html kaz 17:07:57 Zakim has left #wot-td