12:58:22 RRSAgent has joined #wot-td 12:58:26 logging to https://www.w3.org/2025/06/05-wot-td-irc 12:58:34 meeting: WoT-WG - TD-TF - Slot 2 12:58:39 rrsagent, make log public 12:58:43 rrsagent, draft minutes 12:58:44 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 12:59:22 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#June_4-5%2C_2025 12:59:29 present+ Kaz_Ashimura 13:00:36 chair: Ege, Koster 13:00:36 present+ Ege_Korkan 13:01:21 present+ Kunihiko_Toumura 13:02:04 present+ Mahda_Noura 13:03:06 present+ Michael_Koster, Tomoaki_Mizushima 13:03:12 rrsagent, draft minutes 13:03:13 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:03:25 EgeKorkan has joined #wot-td 13:03:37 mahda has joined #wot-td 13:03:48 present+ Mahda_Noura 13:04:35 present+ Cristiano_Aguzzi 13:05:13 cris has joined #wot-td 13:07:14 scribenick: EgeKorkan 13:07:43 topic: Minutes Review 13:07:56 ek: I will go over the minutes 13:08:39 q? 13:08:46 ek: any remarks? 13:08:50 ek: minutes are approved 13:09:07 topic: Toolchain Updates 13:09:20 dape has joined #wot-td 13:09:27 i|will|-> https://www.w3.org/2025/05/22-wot-td-minutes.html May-22| 13:09:30 rrsagent, draft minutes 13:09:31 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:09:50 present- Tomoaki_Mizushima 13:09:53 rrsagent, draft minutes 13:09:54 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:10:07 mn: got around to work on the toolchain again 13:10:42 ... the schemas are now updated and look better with respect to the spec 13:11:12 present+ Tomoaki_Mizushima 13:11:22 present+ Daniel_Peintner 13:11:24 rrsagent, draft minutes 13:11:25 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:11:31 ... I have restructured the security schemes as well 13:12:05 ... I am using annotations to pass variables to post processing 13:12:08 i|got around|-> https://github.com/w3c/wot-thing-description-toolchain-tmp/blob/main/resources/schemas/wot_security.yaml wot-seurity.yaml| 13:12:09 rrsagent, draft minutes 13:12:11 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:13:06 ek: so we can use it to pass variables to post processing 13:13:14 mn: yes 13:13:43 ek: were you doing this in post processing in a hard coded way? 13:13:53 mn: I wasn't doing this 13:14:23 ... I raised it as an issue for linkml but it didn't get fixed 13:15:36 ek: inheritance is on line 58 right? 13:16:02 mn: yes. it wasnt working working before but i think they fixed issues in the tool 13:16:10 https://github.com/w3c/wot-thing-description-toolchain-tmp/blob/main/resources/schemas/wot_security.yaml 13:16:47 rrsagent, draft minutes 13:16:48 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:17:22 ... I have added a benchmark tool to get a score for the generation of json schema 13:17:52 -> https://github.com/w3c/wot-thing-description-toolchain-tmp/blob/main/tests/src/validate_td_instances.py validate_td_instances.py 13:18:51 ek: i think it would be good to have generated results on the repo as well 13:19:27 ... we decided against it but it would be good to have it 13:21:21 ... can you show locally 13:21:27 mn: yes it would be helpful 13:21:54 q+ 13:22:14 ... (shows the local generated) 13:23:48 s/local generated/generated results on her local PC) 13:23:52 rrsagent, draft minutes 13:23:53 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:24:12 mn: we can see the generation of the "null" type. I have reported it to linkml 13:24:25 ... it also adds add type string when you dont specify a string 13:25:17 s/))/)/ 13:25:20 rrsagent, draft minutes 13:25:22 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:26:12 ... I also don't have a JSON Schema post processing. I though I had before 13:27:12 ... now the top level is correct 13:28:06 ek: the optional "null" was always there? 13:28:08 mn: yes 13:28:15 q? 13:29:18 kaz: it would be good to have the generated files on github 13:29:28 ... and explaining the folder structure 13:30:08 ... like at the top of the readme something like "Folder Structure" 13:30:11 rrsagent, draft minutes 13:30:12 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:30:18 q? 13:30:18 ack k 13:31:14 mn: also it is good to mention that the uri format has issues 13:31:32 q+ 13:31:42 ek: any remarks? 13:33:19 ca: regarding the output generation, we can put them as artefacts 13:34:08 ... like a release 13:34:13 s/artefacts/artifacts/ 13:36:15 ek: I think it is a rule that editor's draft must be a index.html 13:36:21 ... is it the case Kaz? 13:36:39 kaz: it is done like that and it would be best for the reader to get a link to the repository's name 13:36:55 ... but there is detailed requirement about this 13:37:09 q- 13:37:39 s/but there is detailed requirement about this/though there is no explicit requirement about that/ 13:37:43 rrsagent, draft minutes 13:37:44 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:39:51 s/must be a index.html must be the index.html file on the main branch./ 13:39:55 ek: we can change the github pages build to use a release 13:41:20 -> https://github.com/w3c/wot-thing-description-toolchain-tmp/issues/43 13:41:31 ... other remarks? 13:41:38 s/it is done like that/the link for an Editor's Draft from a spec is usually specified by the URL of the Editor's Draft repository/ 13:41:41 topic: Charter Deadline 13:42:46 s/ and it would be best for the reader to get a link to the repository's name/. I think it would be easier for the reader to use the repository's URL as usual to access the Editor's Draft./ 13:42:57 -> https://www.w3.org/2023/10/wot-wg-2023.html 13:43:00 scribe+ 13:43:06 s/html/html WoT WG Charter/ 13:43:10 ek: the charter is finishing in 4 months and we have summer holidays 13:43:16 s/scribe+// 13:43:35 s/the charter is finishing/the WoT WG Charter is expiring/ 13:43:41 rrsagent, draft minutes 13:43:43 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:44:03 ek: I don't think we can have a TD REC in that time 13:44:19 q+ 13:45:23 ek: I will summarize the basic process nex 13:45:34 ... we can get extension but have a REC ready in the end of it 13:45:45 ... or get rechartered for 2 years 13:45:56 kaz: W3C process is getting stricter 13:46:14 ... 6 months extension is only possible 13:46:49 ... by when can we publish a TD 2.0 REC? 13:47:06 ... if 6 months is possible, we can get an extension 13:47:31 q+ 13:47:58 s/6 months extension is only possible/6-month extension is possible but for a longer extension, we need the rechartering procedure./ 13:47:58 q- 13:47:58 ca: We definitely cannot publish in 6 months 13:48:10 ... we have all the work to be done in 3 major topics 13:48:23 ... data mapping, manageable affordances, simplified forms 13:48:29 ... we definitely need more work 13:48:30 s/by when can we publish a TD 2.0 REC?/so I'm asking by when we can publish the TD spec as a REC./ 13:48:51 ... with administrative work done, we can focus on the specwork 13:48:58 ... maybe 1 year is a good time 13:49:04 s/can get an extension/can get an extension, but if not, we need to go through the rechartering process./ 13:49:07 rrsagent, draft minutes 13:49:08 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:49:14 ... but it is difficult to tell 13:49:18 q+ 13:49:22 ack c 13:50:01 kaz: given we did not publish a working draft, we need more than 6 months for a REC 13:50:03 mjk has joined #wot-td 13:50:10 ... so I propose rechartering 13:50:44 ... we should think of summer and christmas periods 13:50:59 ... even with 6 monhts extension, we don't get 6 months 13:51:19 ek: if we don't do extension, we should think of the schedule 13:51:21 q- 13:52:17 ek: Does anybody think that we can have a REC with a 6 months extension? 13:53:26 ek: I agree with Cristiano 13:53:41 q+ 13:54:04 ack k 13:54:04 ek: I think that the preliminary consensus is that we don't think that a 6 months extension is enough 13:54:22 kaz: let's make our TF resolution 13:54:38 s/resolution/resolution, and bring it to the main call next week./ 13:54:47 i/let's/scribenick: kaz/ 13:54:51 scribenick: EgeKorkan 13:54:57 rrsagent, draft minutes 13:54:58 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 13:55:04 proposal: The TD TF thinks that a 6 months extension is not enough. Thus, a rechartering is required to publish the next REC of the TD specification 13:55:24 resolution: The TD TF thinks that a 6 months extension is not enough. Thus, a rechartering is required to publish the next REC of the TD specification 13:55:29 q+ 13:55:36 q+ 13:55:54 q+ 13:56:57 ca: what are the implications? will the work we declared in the current charter carry over or will it be scratched? 13:57:04 ek: I think it is treated as a new charter 13:58:00 dp: The resolution is from the TD right? There are other deliverables in the charter. So are they carried over? We need broader consensus 13:58:15 ack dape 13:58:19 mk: we want to adjust other stuff as well 13:58:22 ack c 13:58:37 kaz: the whole wot wg needs to think of the rechartering or extension 13:58:57 ... we need to generate an updated new charter. it can be based on the current charter 13:59:30 ek: nothing mandates that the current deliverables are carried over right? 13:59:32 kaz: yes 13:59:35 q- 13:59:51 s/over right/over. right/ 13:59:58 s/yes/right/ 14:00:02 ek: AOB? 14:00:10 ek: adjourned 14:00:14 rrsagent, draft minutes 14:00:15 I have made the request to generate https://www.w3.org/2025/06/05-wot-td-minutes.html kaz 14:59:34 zkis has joined #wot-td 16:11:14 Zakim has left #wot-td