14:08:25 RRSAgent has joined #wot-td 14:08:29 logging to https://www.w3.org/2025/10/22-wot-td-irc 14:08:30 Zakim has joined #wot-td 14:08:34 chair: Ege_Korkan, Michael_Koster 14:08:38 Meeting: WoT Thing Description 14:08:41 rrsagent, draft minutes 14:08:42 I have made the request to generate https://www.w3.org/2025/10/22-wot-td-minutes.html Ege 14:08:44 rrsagent, make log public 14:08:59 present+ Ege_Korkan, Michael_Koster, Cristiano_Aguzzi, Daniel_Peintner, Tomoaki_Mizushima, Kunihiko_Toumura, Mahda_Noura 14:10:00 scribenick: Ege 14:11:04 scribenick: cris 14:11:26 https://github.com/w3c/wot/issues/1243 14:12:30 luca_barbato has joined #wot-td 14:12:40 scribenick: luca_barbato 14:13:17 topic: Minutes review 14:13:27 https://www.w3.org/2025/10/15-wot-td-minutes.html 14:13:38 ege: Please point out only what you disagree with, typos will be addressed later 14:13:57 q? 14:14:09 14:14:14 ege: Approved 14:14:24 rrsagent, draft minutes 14:14:26 I have made the request to generate https://www.w3.org/2025/10/22-wot-td-minutes.html dape 14:15:17 topic: Binding Templates 14:15:26 subtopic: PRs 14:15:46 ege: We have few PR approved by non-editors, so we should review them now as well 14:16:16 https://github.com/w3c/wot-binding-templates/pull/450 14:16:25 ege: Any remarks? 14:16:29 14:16:33 ege: Merged 14:17:35 https://github.com/w3c/wot-binding-templates/pull/446 14:17:37 good to go +1 14:18:14 q? 14:18:20 ege: Any remarks? 14:18:22 14:18:25 ege: Merged 14:18:45 topic: URI vs IRI 14:20:18 q+ 14:22:14 lb: to sum it up, we reached consensus that we can use URIs. Whoever needs IRI-like strings, they encode 14:22:22 ek: correct 14:23:32 ege: We'd have a theoretical breaking change 14:25:17 q+ 14:25:28 ack l 14:25:44 b: to sum it up, we reached consensus that we can use URIs. Whoever needs IRI-like strings, they encode 14:25:53 s/b:/lb:/ 14:25:55 q+ 14:25:59 ege: correct 14:26:23 lb: We can also consider it a profile problem, but for 2.0 we can just break and have a clean reference to URI 14:27:36 dape: we have `base` and `href` using different types? 14:28:11 ege: They are both anyURI, the text description is referencing URI, IRI and the URI RFC 14:28:30 dape: We use href in two places, we should make sure we update all the places 14:28:35 ack dape 14:30:44 cris: Is joining IRIs having the same rules as URI ? 14:30:47 lu: yes 14:32:46 https://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/ 14:38:13 lu: We can break the xml tradition and have strict URI, since we have consensus for it, or we can go the profile way 14:38:53 ege: Profiles would have quite a bit of trouble to restrict that 14:39:08 lu: We can stay with URI and avoid troubles 14:39:16 q+ 14:39:22 ack c 14:39:49 mahda: Ontologies use IRI, are we fine with restrict? what about jsonschema? 14:39:52 q+ 14:41:53 lu: in any case IRI and URL parser would deal with %encoded uri 14:45:18 mahda7 has joined #wot-td 14:45:25 present+ Mahda_Noura 14:45:28 dape: We should allow non-ascii string 14:45:53 lu: then we do not have consensus? 14:48:49 q+ 14:50:38 ack l 14:53:13 q+ 14:55:16 ack dape 14:58:25 rrsagent, draft minutes 14:58:26 I have made the request to generate https://www.w3.org/2025/10/22-wot-td-minutes.html dape 14:59:26 q+ 14:59:48 scribenick: Ege 15:01:35 mn: the Consumers will reject the uri scheme if they don't support it. Like a browser cannot use mailto: and will open email client 15:09:01 rrsagent, draft minutes 15:09:03 I have made the request to generate https://www.w3.org/2025/10/22-wot-td-minutes.html dape 17:11:08 Zakim has left #wot-td 18:59:49 Ege has joined #wot-td 19:17:26 Ege has joined #wot-td 19:35:26 Ege has joined #wot-td 19:45:38 Ege has joined #wot-td 20:02:51 Ege has joined #wot-td 20:36:48 Ege has joined #wot-td 20:46:21 Ege has joined #wot-td 21:05:02 Ege has joined #wot-td 21:22:12 Ege has joined #wot-td 21:40:40 Ege has joined #wot-td 21:47:28 egekorkan has joined #wot-td 23:25:56 Ege has joined #wot-td 23:43:11 Ege has joined #wot-td 23:58:46 Ege has joined #wot-td