14:11:24 RRSAgent has joined #wot-td 14:11:28 logging to https://www.w3.org/2025/10/15-wot-td-irc 14:11:28 Mahda has joined #wot-td 14:11:31 Zakim has joined #wot-td 14:11:37 present+ Mahda_Noura 14:11:44 chair: Ege_Korkan 14:11:48 Meeting: WoT Thing Description 14:11:54 rrsagent, draft minutes 14:11:55 I have made the request to generate https://www.w3.org/2025/10/15-wot-td-minutes.html dape 14:11:59 rrsagent, make log public 14:12:03 present+ Tomoaki_Mizushima 14:12:17 present+ Daniel_Peintner 14:12:23 present+ Ege_Korkan 14:12:30 rrsagent, draft minutes 14:12:32 I have made the request to generate https://www.w3.org/2025/10/15-wot-td-minutes.html dape 14:12:43 present+ Kunihiko_Toumura 14:12:55 present+ Klaus_Hartke 14:13:24 present+ Klaus_Hartke 14:13:26 scribe: dape 14:14:00 rrsagent, draft minutes 14:14:01 I have made the request to generate https://www.w3.org/2025/10/15-wot-td-minutes.html dape 14:16:25 present+ Luca_Barbato 14:17:47 TOPIC: Minutes 14:18:03 -> https://www.w3.org/2025/10/08-wot-td-minutes.html 14:18:45 EK: Minutes from Wednesday are approved 14:19:02 TOPIC: Quick Schedule 14:19:19 SUBTOPIC: URI vs IRI 14:19:27 https://github.com/w3c/wot-thing-description/issues/2156 14:20:12 EK: Issue come out of an OPC-UA discussion 14:20:23 https://github.com/eclipse-thingweb/node-wot/tree/master/packages/binding-opcua#getting-started 14:21:06 ... the URI schema for OPC-UA contains s= meaning a string 14:21:21 ... protocol allows any string which is UTF8 encoded 14:21:38 ... technically possible 14:22:13 ... can contain German Umlaut or Japanese characters 14:22:24 ... we noticed discrepancy 14:22:36 ... we reference RFC3986 14:22:45 ... anyURI is IRI 14:23:02 ... both are in normative tables and we have some conflict 14:23:33 KH: in href we say IRU and not URI 14:23:37 EK: Correct 14:24:01 ... I think W3C review asked us to use IRI 14:24:19 ... but correct, there is a discrepancy 14:24:28 luca_barbato has joined #wot-td 14:24:33 q+ 14:24:39 ... IRI parsing not common in code basis 14:25:18 ... I found https://www.w3.org/International/wiki/IRIStatus 14:25:45 EK: We can restrict it per protocol to URIs 14:26:19 LB: Would it be enough to point IRI RFC 14:26:39 .... saying non ASCII characters are allowed 14:26:49 ... most parsing libraries do work with unicode 14:27:06 ... main problem is weird escaping 14:27:21 ... DNS had problems with IRI 14:28:35 ... we could restrict strings to UTF8 14:29:03 EK: IRI handling in specific parts only? 14:29:28 LB: yes, but sounds more profile worthy 14:29:53 ... we should review the RFCs 14:30:07 ... and pick the one that fits our target 14:30:38 ... TD should give freedom 14:30:45 ... profile can restrict 14:31:04 q? 14:31:06 ack l 14:31:25 KH: We want address resources on the Web 14:31:32 ... we should use Web standards 14:31:44 ... we can choose URL, IRI etc 14:31:51 ... no matter of taste 14:32:02 ... it is about protocol 14:32:18 ... protocol driver (HTTP, CoAP) needs to know 14:32:35 ... so far URI standard is used 14:32:58 egekorkan has joined #wot-td 14:33:16 ... value in href field (or base field) use URI 14:33:26 Related specifications: https://url.spec.whatwg.org https://www.rfc-editor.org/rfc/rfc3987 14:33:38 ... w.r.t. to OPC-UA I need to see the ABNF grammar 14:34:13 EK: Document is open to members 14:34:20 ... not sure if it contains ABNF 14:34:31 KH: There should be something 14:35:00 ... saying URI or IRI 14:35:34 ... you cannot say URI standard and put unicode characters in query string 14:36:06 q+ 14:36:28 LB: We can make it extra flexible 14:36:42 ... field is UTF8 string and offload it to protocol 14:36:50 KH: This cannot work 14:37:00 ... because of base 14:37:38 EK: True 14:38:10 ... unless we indicate in a different way the protocol 14:38:26 KH: We could get rid of base and href ... 14:38:40 ... and come upo with a combined string per protocol 14:38:51 ... but it creates major problems 14:39:17 MN: hypermedia concept claim does no longer make sense also 14:39:37 LB: Easiest thing is to pick the right definittion of href 14:40:17 ... additional field for anything we cannot support 14:40:30 KH: I would go with URI 14:40:57 ... no huge problem, I think we need a pragmatic solution 14:41:14 ... for base is correct 14:41:29 ... for href it should be used URI also (currently not the case) 14:41:56 LB: Uniform to URI 14:42:09 KH: Yes, it should be always been URI 14:43:45 ... there are options to support unicode in URI 14:43:59 ... we need to better understand the OPC-UA requirements 14:44:06 q+ 14:44:11 ack dape 14:44:28 ack luca_barbato 14:44:30 q+ 14:44:44 EK: IRI to URI is in RFC? 14:45:07 KH: Yes, there is a conversion algorithm 14:45:56 ... UTF8 bytes to percentage encoding 14:48:21 DP: the OPCUA binding requires percentage encoding 14:48:29 EK: Not sure 14:49:07 KH: We need to check we (or OPCUA) violate the standard 14:49:47 EK: Let's look at the OPC spec 14:50:05 KH: Next week Wed I cannot join, I can join Thursday 14:50:08 EK: Thanks! 14:50:37 https://github.com/w3c/wot-thing-description/pull/2154 14:50:49 TOPIC: Common definitions 14:51:03 https://github.com/w3c/wot-thing-description/pull/2154 14:51:37 EK: I started the exercise to extend the examples 14:51:42 https://github.com/w3c/wot-thing-description/blob/ege-common-definitions-examples/proposals/common-definitions/tooling/tds.js 14:52:21 EK: examples at line 454 14:52:41 ... recommendedTDs 14:53:21 ... e.g., change from default contentType JSON to cbor etc 14:53:41 ... or Modbus with all parameters 14:53:53 ... multi IP addresses 14:54:09 ... local vs public security 14:54:47 rrsagent, draft minutes 14:54:48 I have made the request to generate https://www.w3.org/2025/10/15-wot-td-minutes.html dape 14:55:19 EK: Do you see more useful examples? 14:55:28 ... to test this new method 14:55:40 ... will show it tomorrow in more details 14:55:57 ... please provide feedback in PR 14:56:23 ... in PR I summarized also some of my findings 14:56:57 TOPIC: Bindings 14:56:59 github.com/w3c/wot-binding-templates/pull/446 14:57:11 https://github.com/w3c/wot-binding-templates/pull/446 14:57:19 rrsagent, draft minutes 14:57:20 I have made the request to generate https://www.w3.org/2025/10/15-wot-td-minutes.html dape 14:57:42 EK: realized some mistakes 14:57:53 ... no proper rendering for Modbus 14:58:18 ... the same stupid error appeared more often 14:58:36 ... I also updated the authors 14:59:03 ... same change everywhere expect Modbus with more changes 14:59:21 q? 14:59:27 ... I will wait a bit for feedback 14:59:32 ack dape 15:00:02 KH: Wonder why S has been removed in general 15:00:25 EK: We started off with S and changed later on 15:00:48 ... due to W3C feedback 15:00:52 KH: I see 15:01:17 EK: IANA uses plural and W3C seems to use singular 15:02:06 s/EK: IANA/KH: IANA 15:02:14 rrsagent, draft minutes 15:02:15 I have made the request to generate https://www.w3.org/2025/10/15-wot-td-minutes.html dape 15:02:45 [adjourned] 15:02:46 rrsagent, draft minutes 15:02:48 I have made the request to generate https://www.w3.org/2025/10/15-wot-td-minutes.html dape 15:26:20 Ege has joined #wot-td 17:15:48 Zakim has left #wot-td 18:11:42 Ege has joined #wot-td 18:28:56 Ege has joined #wot-td 18:45:24 Ege has joined #wot-td 20:01:46 Ege has joined #wot-td 20:29:09 Ege has joined #wot-td 21:01:35 Ege has joined #wot-td 21:13:57 Ege has joined #wot-td 21:16:50 Ege has joined #wot-td 21:34:48 Ege has joined #wot-td 22:22:38 Ege has joined #wot-td 22:43:40 Ege has joined #wot-td 22:59:48 Ege has joined #wot-td 23:33:40 Ege has joined #wot-td