14:02:04 RRSAgent has joined #wot-td 14:02:08 logging to https://www.w3.org/2025/02/06-wot-td-irc 14:02:13 meeting: WoT-WG - TD-TF - Slot 2 14:02:21 mahda has joined #wot-td 14:02:21 chair: Ege 14:02:41 present+ Mahda_Noura 14:03:16 EgeKorkan has joined #wot-td 14:03:16 Mizushima has joined #wot-td 14:03:19 present+ Kaz_Ashimura, Ege_Korkan, Michael_Koster, Klaus_Harte, Jan_Romann, Tomoaki_Mizushima 14:04:06 mjk has joined #wot-td 14:04:21 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#February_6%2C_2025 14:04:27 rrsagent, make log public 14:04:31 rrsagent, draft minutes 14:04:32 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:04:57 scribenick: EgeKorkan 14:05:03 present+ Kunihiko_Toumura 14:05:07 rrsagent, draft minutes 14:05:08 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:05:21 topic: Agenda 14:05:54 ek: two minutes review, then coap and binding registry 14:06:04 topic: Minutes Review 14:06:09 https://www.w3.org/2025/01/29-wot-td-minutes.html 14:07:01 q? 14:07:06 ek: Any comments? 14:07:21 ek: minutes of wednesday are approved 14:07:33 https://www.w3.org/2025/01/30-wot-td-minutes.html 14:07:53 i|01/29|subtopic: Jan 29| 14:08:04 i|01/30|subtopic: Jan 30| 14:08:06 rrsagent, draft minutes 14:08:08 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:08:26 ek: Any comments? 14:08:36 ek: minutes are approved 14:09:01 topic: Binding Templates 14:09:17 subtopic: merged prs 14:09:17 https://github.com/w3c/wot-binding-templates/pulls?q=is%3Apr+is%3Aclosed 14:09:38 cris has joined #wot-td 14:09:42 s/two minutes/two: minutes/ 14:09:55 q+ 14:09:59 s/merged prs/Merged PRs/ 14:10:27 ek: these are trivial PRs that have been merged 14:10:34 ca: I want to discuss about the PR 395 14:11:07 ... I am not sure why the editorconfig is changed 14:11:12 ... it can be kept to be safer? 14:11:33 kh: in an ideal case, all computers would use the same line ending 14:11:45 ... linux, windows and macos do it differently 14:12:04 ... you can deal with this in different ways, like forcing a specific line endings 14:12:23 ... we had issues in this repo as some editors do not support editorconfig 14:12:35 ... an alternative is to not force anything, just let people use what their OS does 14:12:54 rrsagent, draft minutes 14:12:56 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:13:02 ... gitattributes file will do the conversion for you 14:13:22 ... change to your OS in checkout, and in commit convert back 14:14:03 ca: I am familiar with this. Keeping end of line would be safer no? 14:14:10 i|I wan to discuss|subtopic: PR 395| 14:14:15 ... less bytes wasted 14:14:37 i|I wan to discuss|-> https://github.com/w3c/wot-binding-templates/pull/395 PR 395 - Fix line endings| 14:14:42 rrsagent, draft minutes 14:14:43 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:14:53 s/discuss about/discuss/ 14:14:58 rrsagent, draft minutes 14:14:59 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:15:42 kh: safer would be to let git handle it 14:15:43 q+ 14:16:20 JKRhb has joined #wot-td 14:16:29 s/linux, windows and macos/Linux, Windows and MacOS/ 14:16:32 rrsagent, draft minutes 14:16:33 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:16:39 ack c 14:16:48 ca: I cannot remember but there were issues not having 14:17:22 ek: let's see if we notice an issue 14:17:39 ca: the issue will be only locally 14:17:45 q? 14:17:48 ek: we can notice that as well 14:18:11 kh: only in makefiles this is an issue 14:18:28 ca: I remember that. Also sometimes in docker 14:18:36 ack c 14:19:05 kaz: I personally prefer linux but github mechanism is fine 14:19:17 ... it would be have been better to merge it in the call after the explanation 14:19:30 s/would be have/would have/ 14:19:52 ek: you are right. It is a fundamental change in the end 14:20:27 rrsagent, draft minutes 14:20:28 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:20:34 q? 14:20:45 ek: I could not find the right label as well, let's add something at least 14:20:51 ek: any further remarks? 14:20:59 s/prefer linux/prefer Linux style/ 14:21:04 s/but github/but GitHub/ 14:21:11 rrsagent, draft minutes 14:21:12 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:21:18 ek: any opinion on the other PRs? 14:21:56 q+ 14:22:06 topic: OPC UA URI Scheme 14:22:12 ek: do we know the decision? 14:22:53 ca: We almost settled the discussion last time. I could not join 14:23:02 ... we should check with daniel and sebastian about it 14:23:37 ek: I don't know the final decision's documentation though 14:23:45 ca: it should be the query parameter 14:23:49 q? 14:23:54 ack k 14:23:56 ack c 14:24:09 ca: there was also a small discussion on using nodeid or just id 14:24:54 topic: CoAP Confirmable Requests 14:25:20 jr: klaus made some changes to the PR and they are already approved 14:25:44 ... it is about a hint for the consumer to add an option called confirmable to the requests 14:26:02 ... it is called cov:confirmable, a boolean 14:26:30 i|klaus made|-> https://github.com/w3c/wot-binding-templates/pull/392 PR 392 - feat: introduce cov:confirmable vocabulary term| 14:26:33 rrsagent, draft minutes 14:26:34 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:26:46 ... if you don't use UDP, it is not applicable 14:27:05 ... there can be some further guidance for the TD designer on when to use these terms 14:27:15 ... it can be a follow up PR 14:27:36 ek: anything to add? 14:27:49 i|do we know|-> https://github.com/w3c/wot-thing-description/issues/2069 Issue 2069 - URL Scheme Decision 14:27:53 kh: everything looks good 14:28:06 q? 14:28:07 ... what triggered this change though? Is it fixing the issue? 14:28:18 jr: matthias kovatsch brought up the issue in the WoT Week 14:28:34 i|I want to discuss|subtopic: PR 395| 14:28:43 ... knx iot devices were not always turned on. 14:28:47 i|I want to discuss|-> https://github.com/w3c/wot-binding-templates/pull/395 PR 395 - Fix line endings| 14:28:49 rrsagent, draft minutes 14:28:50 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:29:18 ... however, we should probably work more on this. So that we can know when the device is reachable, i.e. understanding the sleep schedule 14:29:42 present+ Cristiano_Aguzzi 14:29:46 rrsagent, draft minutes 14:29:48 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:29:58 ... this way, at least the Consumer is not trying to send confirmable requests 14:30:09 kh: it would be good to continue the discussion 14:30:32 ... and learn more about the background 14:31:22 ... if you know that the device wakes up every 5 mins for 20 seconds. We can put that in the TD, which can apply to other protocols 14:31:47 ... then you need to know in which part of the schedule we are, synchronize and then send the requests precisely 14:32:18 jr: I wanted to check if there are existing solutions and algorithms 14:32:27 q+ 14:32:42 kh: Have you checked with Matthias? 14:32:55 jr: he was pinged in the issue but maybe I should send an email 14:33:07 mk: I concur with what klaus has said 14:33:38 ... there is a separation of concerns like Klaus said. Maybe there should be an interface for the Consumer to influence this schedule. Retries create network congestion 14:33:47 s/klaus has/Klaus has/ 14:33:48 ... it is more about the configuration of the server 14:33:58 ... it should be separated from the normal get/put operations 14:34:17 ... most systems won't want you to change it or the system cannot be changed 14:34:46 ack mjk 14:34:47 q+ 14:34:59 kh: this PR is about a specific use case. The TD creator knows it better that the request is confirmable 14:35:24 ... if it makes it better for the people, I don't oppose but we can explore this further 14:36:00 kaz: The direction is ok and fine but it would be nicer to have a more detailed explanation in the specification text 14:36:05 ... like when to use this feature 14:36:07 q+ 14:36:13 ... so I agree with Klaus on that 14:36:14 -> https://github.com/w3c/wot-binding-templates/issues/389 Issue - CoAP: Vocabulary for (non-)confirmable messages and retry patterns| 14:36:17 q- 14:36:24 jr: I will try to follow up on this PR 14:36:26 s/patterns|/patterns/ 14:36:29 rrsagent, draft minutes 14:36:31 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:36:48 ... as klaus said, it would be valuable to add this to other protocols too 14:37:01 s/Issue - Co/related Issue 389 - Co/ 14:37:03 rrsagent, draft minutes 14:37:04 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:37:18 s/klaus/Klaus/ 14:37:25 ek: can you create a user story in the use case repo? we can provide the background in that way and motivate the work 14:37:27 rrsagent, draft minutes 14:37:28 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:38:36 topic: Binding Registry 14:39:01 ek: I have worked on the PR 378 to make it mergable 14:39:09 https://github.com/w3c/wot-binding-templates/pull/378 14:39:33 s/https/-> https/ 14:39:49 s/378/378 PR 378 - Registry Requirements Update/ 14:39:52 rrsagent, draft minutes 14:39:53 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:40:02 ek: this is a messy PR because it was collecting opinions 14:40:36 s/topic: Binding Templates/topic: Binding Templates PRs/ 14:40:40 rrsagent, draft minutes 14:40:41 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:41:36 ... I have removed the opinions etc. into issues that are linked now 14:42:39 ... this way the PR is mergable and we can continue the discussions in the issues for the specific points 14:43:57 ek: Is it fine for everyone to merge it as is and continue the discussions step by step in the issues and address each issue separately? 14:43:58 q? 14:44:03 ack j 14:44:36 ek: any opinions? 14:46:32 ek: we are fine to merge 14:46:46 ... please comment on the specific issues and we can make PRs as well 14:48:17 rrsagent, draft minutes 14:48:18 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:48:47 q+ 14:48:51 ek: anyone want to bring up a topic for discussion? 14:49:52 i|we are fine|(no objections)| 14:49:55 rrsagent, draft minutes 14:49:56 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:51:10 topic: WoT TD Project Progress Check 14:51:16 -> https://github.com/orgs/w3c/projects/80 WoT TD Project 14:51:55 ek: We are getting more issues than we are handling, seen in the unsorted column of the GH project 14:52:06 ... anyone volunteering to take some of the issues here? 14:53:23 subtopic: Issue 2068 14:53:43 -> https://github.com/w3c/wot-thing-description/issues/2068 TD Issue 2068 - Specify the result of queryaction operation 14:53:51 ca: should once close it at the moment 14:54:03 ek: we can move it to "Parking" 14:54:06 ca: ok 14:54:21 i/should once/scribenick: kaz 14:54:26 rrsagent, draft minutes 14:54:28 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:54:58 subtopic: Issue 2066 14:55:09 ek: it is in PR https://github.com/w3c/wot-thing-description/pull/2070 14:55:49 i|it is|-> https://github.com/w3c/wot-thing-description/issues/2066 TD Issue 2066 - Typo: approache -> the … approach| 14:55:51 q+ 14:56:00 i|it is|ca: any PR?| 14:56:01 q- 14:56:20 jr: I have experienced that before. I should have opened an issue before 14:56:22 i|it is in PR|scribenick: EgeKorkan| 14:56:25 rrsagent, draft minutes 14:56:27 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 14:59:00 q+ 14:59:59 q+ 15:00:04 ack j 15:00:29 ek: will check with Daniel about PR 2070 15:01:03 mn: you can assign 2071 to me 15:01:17 i|you can|subtopic: PR 2070 15:01:22 ek: we will see each other next week. no cancellations 15:02:11 s/PR 2070/Issue 2071/ 15:02:46 i|assign 20|-> https://github.com/w3c/wot-thing-description/issues/2071 TD Issue 2071 - json-ld playground Error thing definition ontology/schema| 15:02:50 [adjourned] 15:02:54 rrsagent, draft minutes 15:02:55 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 15:03:43 i|will check|scribenick: kaz| 15:03:51 i|you can a|scribenick: EgeKorkan| 15:03:53 rrsagent, draft minutes 15:03:54 I have made the request to generate https://www.w3.org/2025/02/06-wot-td-minutes.html kaz 15:08:13 EgeKorkan has joined #wot-td 15:23:28 EgeKorkan has joined #wot-td 15:27:42 JKRhb has joined #wot-td 15:28:51 JKRhb_ has joined #wot-td 15:36:05 EgeKorkan has joined #wot-td 15:37:42 JKRhb has joined #wot-td 15:38:39 JKRhb has joined #wot-td 15:39:46 JKRhb_ has joined #wot-td 15:52:28 EgeKorkan has joined #wot-td 15:57:40 EgeKorkan has joined #wot-td 16:13:10 JKRhb has joined #wot-td 17:28:57 Zakim has left #wot-td 18:27:41 JKRhb has joined #wot-td 19:29:15 JKRhb has joined #wot-td 20:29:57 JKRhb has joined #wot-td 23:08:21 JKRhb has joined #wot-td 23:55:43 JKRhb has joined #wot-td