14:03:28 RRSAgent has joined #wot-td 14:03:33 logging to https://www.w3.org/2025/08/27-wot-td-irc 14:03:36 meeting: WoT-WG - TD-TF - Slot 1 14:04:04 present+ Kaz_Ashimura, Cristiano_Aguzzi, Ege_Korkan, Jan_Romann, Kunihiko_Toumura, Tomoaki_Mizushima 14:04:23 cris has joined #wot-td 14:04:26 Mizushima has joined #wot-td 14:04:41 dape has joined #wot-td 14:04:46 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#August_27%2C_28_2025 14:04:51 rrsagent, make log public 14:04:55 rrsagent, draft minutes 14:04:56 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:05:52 topic: agenda 14:06:35 ege: tomorrow we'll have Document freeze resolution 14:06:43 present+ Daniel_Peintner 14:06:46 topic: Minutes review 14:07:05 i|tomorrow|[[| 14:07:09 i|tomorrow|Wednesday: Schedule, Arch Spec, TD Optional Content Type, Registry Terminology 14:07:09 Thursday: HTTP Binding, Binding Templates Retirement, Document Freeze TF Resolution| 14:07:19 i|tomorrow|]]| 14:07:23 rrsagent, draft minutes 14:07:24 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:07:41 -> https://www.w3.org/2025/08/20-wot-td-minutes.html Aug-20 14:07:47 chair: Ege 14:07:50 jan: I noticed one thing, there are some "@" characters left 14:08:04 q+ 14:08:08 ... other than that it looks fine 14:08:18 kaz: ok I'll remove them 14:08:39 q- 14:08:50 ege: minutes approved 14:09:08 topic: Schedule 14:09:22 s/them/them, and done/ 14:09:37 rrsagent, draft minutes 14:09:38 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:09:57 ege: August 28 we'll have TD document freeze 14:10:08 i|Aug|-> https://github.com/w3c/wot/blob/main/planning/wg-schedule.md WG Schedule 14:10:10 rrsagent, draft minutes 14:10:11 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:10:18 ... small typos fixes can still happen 14:10:22 ... same date for bindings registry 14:10:48 ... for the binding templates we need to find the correct wording for "document retirement" 14:10:59 ... after tomorrow no big changes there too. 14:11:07 topic: Issues 14:11:16 kaz has joined #wot-td 14:11:22 ege: we have to issues to track current work 14:11:23 rrsagent, draft minutes 14:11:24 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:11:30 subtopic: Issue 2112 14:11:55 ege: no updates so far 14:12:09 -> https://github.com/w3c/wot-thing-description/issues/2112 TD Issue 2112 - TD 2.0 FPWD Goals 14:12:14 ... but I think we can land profiles vs binding topic by tomorrow 14:12:17 s|-> https://github.com/w3c/wot-thing-description/issues/2112 TD Issue 2112 - TD 2.0 FPWD Goals|| 14:12:25 i|no up|-> https://github.com/w3c/wot-thing-description/issues/2112 TD Issue 2112 - TD 2.0 FPWD Goals| 14:12:31 q+ 14:12:32 subtopic: issue 12 14:12:57 -> https://github.com/w3c/wot-bindings-registry/issues/12 Registry Issue 12 - First Draft Registry Plan| 14:12:59 ege: I'm finalizing the registry description 14:13:03 s/Plan|/Plan/ 14:13:04 ack dape 14:13:05 rrsagent, draft minutes 14:13:06 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:13:12 dape: intro section is not there yet 14:14:20 ek: (adds an action item to Issue 12 about that) 14:14:31 i|adds|scribenick: ek| 14:14:36 scribenick: cris 14:14:40 rrsagent, draft minutes 14:14:42 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:14:48 ege: next week we will invite some people from WoT CG to get feedback about initial connection 14:15:06 topic: Architecture specification assetions 14:15:11 i|tomorrow|scribenick: cris| 14:15:12 rrsagent, draft minutes 14:15:13 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:15:30 s/Thursday: HTTP Binding, Binding Templates Retirement, Document Freeze TF Resolution|// 14:15:39 i|]]|Thursday: HTTP Binding, Binding Templates Retirement, Document Freeze TF Resolution| 14:15:41 rrsagent, draft minutes 14:15:42 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:15:49 ege: we now have a list of assertions coming from Architecture spec 14:15:53 ... we have to categorize them and find which ones can impact TD 14:16:03 s/issue 12/Issue 12/ 14:16:35 i|we now|-> https://github.com/w3c/wot-thing-description/pull/2124 TD PR 2124 - Add list of assertions in Architecture document| 14:16:50 ... in PR 2124 you can find a list of possible categories 14:17:51 present+ Michael_Koster 14:17:55 chair+ Koster 14:17:58 rrsagent, draft minutes 14:17:59 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:18:17 mjk3 has joined #wot-td 14:19:22 ege: now we have to put the categories below 14:19:24 q+ 14:20:18 cris: how are we going to work for distributing the workload about categorization? 14:20:46 ege: we can take a set of assertions and create a PR with the proposals 14:21:35 cris: ok but how to put the category should we just add an A at the end of the sentence? 14:21:52 q+ 14:22:27 ack cris 14:23:05 jan: assertion 1 is a good example of a non-testable assertions 14:23:58 ... maybe add a new category for discarding those non-testable assetions 14:25:44 ege: ok if this is fine I comment with the format of how to declare a category for an assertion 14:25:53 ... is it ok to merge it ? 14:25:58 rrsagent, draft minutes 14:25:59 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:26:44 ... I propose to close issue 2120 and create new one for the categorization 14:29:41 -> https://github.com/w3c/wot-thing-description/issues/2120 TD Issue 2120 - Moving normative text from Architecture Specification about the TD features 14:30:04 rrsagent, draft minutes 14:30:05 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:30:58 ege: created issue 2126 14:31:13 topic: Optional content type 14:31:16 https://github.com/w3c/wot-thing-description/pull/2081 14:32:14 i|Optional|-> https://github.com/w3c/wot-thing-description/issues/2126 TD Issue 2126 - Categorizing Architecture Assertions| 14:32:45 s|https://github.com/w3c/wot-thing-description/pull/2081|-> https://github.com/w3c/wot-thing-description/pull/2081 TD PR 2081 - Make contentType optional in ExpectedResponse and AdditionalExpectedResponse classes| 14:32:45 ege: we have good amount of approvals 14:32:47 rrsagent, draft minutes 14:32:48 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:32:56 ca: I'm still not completely satisfied about how we deal the absece of payloads (inputs or outputs), I hope that in the next revision we can find something cleaner 14:33:04 ca: so as a reminder 14:33:22 ege: I update the assertions.csv file 14:33:35 ege: is it ok to merge this PR ? 14:33:40 q+ 14:33:49 jan: thank you everyone 14:33:58 ... ok for merging 14:34:01 ege: merged 14:34:23 jan: since this is coming from Discovery spec, I wondering if we can fix it 14:34:41 ... is the Discovery document will be updated soon? 14:34:59 ege: it depends, but definitely in the next charter. 14:35:06 ... currently we need more people working there 14:35:24 ... good news is that Discovery update is in the charter draft 14:36:51 topic: Profile explaination 14:38:09 ege: we have a good amount of approvals in this PR 14:38:20 ... very simple add informative text about profiles 14:38:30 ... ok merging 14:39:06 topic: PR 2125 automating assertion list 14:40:16 ege: this pr synchronize the assertions csv file 14:40:23 ... everytime we render 14:41:04 ... any objections ? 14:41:26 ... merged 14:42:56 topic: Binding registry 14:43:02 subtopic: PR 24 14:43:25 dape: the terminology should be now correct 14:43:43 ... but there still 4 warnings 14:43:57 ... but they are from intro section which will be removed 14:44:00 ege: ok 14:44:51 q+ 14:44:54 q- 14:45:27 q+ 14:46:18 q+ 14:47:08 cris: I think we should make it clear either with words or special characters 14:47:14 dape: we can use "concrete" 14:48:01 rrsagent, draft minutes 14:48:02 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:48:31 i|I'm still not|scribenick: EgeKorkan| 14:48:35 jan: additionally sometimes we can just remove WoT X and have a simpler definition 14:48:55 i|I update the|scribenick: cris| 14:48:58 rrsagent, draft minutes 14:48:59 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:50:10 i|the terminology should|-> https://github.com/w3c/wot-bindings-registry/pull/24 Registry PR 24 - Make use of some terminology terms| 14:50:43 i|this pr syn|-> https://github.com/w3c/wot-thing-description/pull/2125 TD PR 2125 - Automating assertion list generation| 14:50:45 rrsagent, draft minutes 14:50:47 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:51:09 ege: it seems that removing the X works quite well 14:51:13 cris: yes 14:52:00 i|we have a good|-> https://github.com/w3c/wot-thing-description/pull/2122 TD PR 2122 - Profile explanation| 14:52:01 rrsagent, draft minutes 14:52:02 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:52:19 ege: we can fix it in this PR 14:52:44 ege: do you prefer "concrete" or "specific" or removing WoT X ? 14:53:00 cris: +1 for removing and see if it fits well also in other parts of the document 14:53:27 i|topic: Architecture|topic: Thing Description| 14:53:39 s/topic: Architecture/subtopic: Architecture/ 14:53:51 s/topic: Optional/subtopic: Optional/ 14:54:02 s/topic: Profile/subtopic: Profile/ 14:54:23 s/topic: PR 2125 automating/subtopic: Automating/ 14:54:25 rrsagent, draft minutes 14:54:27 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:55:44 q? 14:55:55 q- 14:55:58 ack c 14:55:59 ack dape 14:56:19 q+ 14:58:09 rrsagent, draft minutes 14:58:10 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 14:58:38 q? 14:58:40 ack c 14:58:55 q+ 14:59:06 cris: I agree removing WoT in every definition of a term 14:59:22 dape: I think it is fine to note down in this PR the future direction 14:59:46 ... but it is better to implement that in a follow up PR 14:59:48 ege: ok 15:00:13 ack dape 15:00:28 q+ 15:01:37 kaz: ok for option 4. About the title, we can use also Web of Things (WoT) Binding Registry 15:01:49 ... it seems even more natural 15:02:12 ege: ok not related to this PR, but the change we'll have a couple of impacts 15:02:16 kaz: yes, before publication we can 15:04:16 proposal: Change the name of the repository to wot-binding-registry and the name of the document to "WoT Binding Registry" 15:04:26 +1 15:04:31 +1 15:04:31 q? 15:04:35 ack k 15:04:58 resolution: We agree to change the name of the repository to wot-binding-registry and the name of the document to "WoT Binding Registry" 15:05:18 rrsagent, please draft the minutes 15:05:20 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html jkrhb 15:06:14 q- 15:06:17 ege: AOB? 15:06:29 [adjourned] 15:06:33 rrsagent, draft minutes 15:06:34 I have made the request to generate https://www.w3.org/2025/08/27-wot-td-minutes.html kaz 17:29:24 Zakim has left #wot-td