14:01:07 RRSAgent has joined #wot-td 14:01:11 logging to https://www.w3.org/2025/04/09-wot-td-irc 14:01:18 meeting: WoT-WG - TD-TF - Slot 1 14:01:44 present+ Kaz_Ashimura, Michael_Koster, Ege_Korkan 14:01:44 chair: Ege, Koster 14:01:47 rrsagent, make log public 14:01:55 rrsagent, draft minutes 14:01:56 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 14:02:22 present+ Kunihiko_Toumura 14:03:18 sebastian has joined #wot-td 14:03:36 luca_barbato has joined #wot-td 14:04:49 present+ Cristiano_Aguzzi, Luca_Barbato, Sebastian_Kaebisch 14:05:08 rrsagent, draft minutes 14:05:10 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 14:05:20 cris has joined #wot-td 14:05:26 mjk has joined #wot-td 14:05:41 present+ Jan_Romann 14:05:53 topic: Agenda 14:05:56 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#April_9-10%2C_2025 14:06:05 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#April_9-10%2C_2025 Agenda for today 14:06:15 s/topic: Agenda/topic: minutes/ 14:06:27 ege: you should have seen the minutes 14:06:35 ... is there anything that needs to be changed? 14:06:50 ... minutes approved 14:06:55 topic: Agenda 14:07:00 Mizushima has joined #wot-td 14:07:13 ege: is there any updated on PR 2081 ? 14:07:19 jan: nothing yet 14:07:43 ege: next one is Binding registry, there are three PRs active 14:08:02 ege: we should choose the next Work Item, we need more input 14:08:19 ... next we have to work on the initial connection expansion algorith 14:08:43 seb: I joined to let know about the review phase of the OPC UA binding 14:08:59 ... the document is not that long, you should review a single chapter 14:09:16 ... I'm looking forward to hear you feedback 14:09:28 q+ 14:09:37 s/chapter/chapter 6/ 14:10:06 ege: we can do the discussion today 14:10:10 ack k 14:10:15 present+ Tomoaki_Mizushima 14:10:21 rrsagent, draft minutes 14:10:23 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 14:10:32 ege: is it ok to discuss OPC UA binding today? 14:10:43 ege: added 14:10:54 topic: OPC UA Binding 14:10:55 whttps://lists.w3.org/Archives/Member/member-wot-wg/2025Apr/0004.html 14:10:57 https://lists.w3.org/Archives/Member/member-wot-wg/2025Apr/0004.html 14:11:48 seb: it should only visible for working group memebers 14:11:49 s|whttps://lists.w3.org/Archives/Member/member-wot-wg/2025Apr/0004.html|| 14:11:59 ... please don't share it outside this group 14:12:10 ... it is fine to get feedback from github issues 14:12:11 s|https://lists.w3.org/Archives/Member/member-wot-wg/2025Apr/0004.html|-> https://lists.w3.org/Archives/Member/member-wot-wg/2025Apr/0004.html Sebastian's message about the OPC UA Binding Document| 14:12:33 ege: we are not going to follow the "official" review process of binding 14:12:39 https://github.com/w3c/wot-binding-templates/blob/main/registry-requirements.md 14:12:39 ... we can just do basic tests 14:13:09 ... for the future we should follow the process described in the link above. 14:13:13 q? 14:13:49 ege: The document as a initial introduction section 14:14:02 seb: it is something required by the OPC UA foundation 14:14:17 ... just a basic explaination of the context 14:14:31 ... if you go to chapter 6 you will find TD relevant information 14:14:46 ... 4 to 5 page maximum 14:15:02 ... previous part might be removed 14:15:06 q+ 14:15:23 s/previous part/previous parts/ 14:16:19 ege: the goal of the document is to describe an OPC-UA server 14:16:37 rrsagent, draft minutes 14:16:38 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 14:16:44 ... hrefs targets will be "nodes" a concept of OPC UA data model 14:17:14 kaz: technically sebastian should be in the opc-ua liason mailing list 14:17:31 ... second point we can use this first contribution as a blueprint for future bindings 14:17:44 ... and we can think about the procedure 14:18:24 q+ 14:18:27 q- 14:19:08 cris: where should be the feedback collected? 14:19:20 ege: wot binding templates repository issues 14:19:26 ... with label opc-ua 14:19:35 s/technically sebastian should be in the opc-ua liason mailing list/technically, Sebastian should forward this document to the W3C Liaison Team mailing list as well given there is an official liaison between OPC and W3C./ 14:20:37 s/use this first contribution as a blueprint for future bindings/use this document as an example application for our expected WoT Binding Registry./ 14:20:38 seb: the binding is pretty simple, mainly is all about the URL 14:21:05 s/about the procedure/about how to improve our proposed WoT Binding Registry procedure based on that discussion./ 14:21:09 rrsagent, draft minutes 14:21:11 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 14:21:17 ack c 14:21:24 ... and some additional optional keywords that might be used for further explain how to connect and interact with the server 14:21:41 ege: note that the URL main contain enconded characters 14:22:03 ... the document contain information about security defintions 14:22:10 ... we should include this information in our process 14:23:02 ege: the default prefix is uav 14:23:14 seb: as you know it is just an example prefix it can be changed 14:23:39 janro has joined #wot-td 14:25:31 seb: format is not perfect yet 14:25:38 ege: then a the bottom there are examples 14:26:09 ... I'm interested in the default mapping between op keywords and opc-ua configurations 14:26:46 seb: there is some information in the access level paragraph 14:27:03 ... but there is not really a default provided 14:27:16 ege: is there an equivalent of the HTTP GET method? 14:27:26 seb: good question, I don't really know 14:27:29 q? 14:27:37 ... they should have read and write command 14:27:46 ... you can use the issues to raise the question 14:27:58 q? 14:28:04 ege: there should not be so much flexibility 14:28:09 ... but it should be good to have it 14:29:28 ... checking the current todo list for the new process, we are aligned 14:29:38 ... but we are missing this mapping information 14:31:48 rrsagent, draft minutes 14:31:49 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html janro 14:31:55 ... probably we need also a JSON schema to validate the form parts of opc-ua TDs 14:32:04 ... anything else should be fine 14:32:11 ... there are small things to improve 14:32:18 ... but anybody here can help 14:32:35 q? 14:33:17 ege: you can experiment using off the shelf libraries 14:33:24 ... node-wot support it too 14:34:16 rrsagent, draft minutes 14:34:17 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 14:34:23 topic: Binding Registry 14:34:26 https://github.com/w3c/wot-binding-templates/pull/423 14:34:29 subtopic: PR 423 14:34:52 ege: we agreed about the version of a binding should look like 14:34:56 s|https://github.com/w3c/wot-binding-templates/pull/423|| 14:34:59 ... main thing we agreed is the uniqueness 14:35:11 sebastian has joined #wot-td 14:35:13 i|we agreed|-> https://github.com/w3c/wot-binding-templates/pull/423 Binding PR 423 - Registry versioning requirements| 14:35:19 ok, I have to leave for another meeting. Thanks and bye 14:36:31 ege: the document must contain a changelog 14:36:41 ... and all the previous versions listed as links 14:36:47 q? 14:36:51 q+ 14:40:10 cris: do we explain that version should define a concrete ordering scheme? 14:40:24 ... or is it implied by previous version links? 14:40:37 ege: do we version summary document too? 14:40:42 cris: yeah 14:40:44 ack c 14:40:47 rrsagent, draft minutes 14:40:48 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 14:41:58 cris: also they should explain ordering only if it is not already clear 14:42:01 ege: yes 14:42:23 q? 14:43:16 subtopic: PR 424 14:43:18 https://github.com/w3c/wot-binding-templates/pull/424 14:43:33 ege: we agreed before quite a while ago. 14:43:45 ... we only require json schema 14:43:50 s|https|-> https| 14:44:00 ... and really advice to place a json-ld context 14:44:06 s/424/424 Binding PR 424 - Machine readable documents requirements/ 14:44:08 rrsagent, draft minutes 14:44:10 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 14:46:43 q? 14:46:47 ... straightforward PR , any remarks? 14:47:58 subtopic: Future of registry requirements document 14:48:08 ege: it is in a very good state 14:48:16 ... we can turn it into an editor draft 14:48:19 https://github.com/w3c/wot-binding-templates/issues/421 14:48:29 ... we should get opionions about issue above 14:48:56 ... current TD editor draft contains everything about the binding mechanism 14:49:05 s|https://github.com/w3c/wot-binding-templates/issues/421|| 14:49:06 ... the binding is going to be just a registry doucment 14:49:18 s/doucment/document/ 14:49:24 i|it is in a very|-> https://github.com/w3c/wot-binding-templates/issues/421 Binding Issue 421 - Where should the registry live?| 14:49:47 ... currently we have two options 14:50:19 ... use current wot-binding-templates, delete everything and redirect back to TD 14:50:39 ... create a new document, keep the old one but create a new red banner 14:51:40 ... any proposals? opionions? 14:51:43 q+ 14:53:07 q+ 14:53:42 cris: ok for proposal 2 14:54:19 kaz: wot-binding-templates repository was focused on editing the group note 14:54:58 ... from my view point it is better to have a different repository to help people understand the differences with the new approach 14:55:03 q+ 14:55:05 ack c 14:55:06 ack k 14:55:19 luca: ok for proposal 2 14:56:01 ... I'm also ok to use the old repo to store current set of bindings (http, coap, etc.) 14:57:04 +1 14:57:08 mk: ok for 2 14:57:36 toumura: ok for 2 14:57:46 mizushima: 2 works 14:58:48 q+ 14:58:54 ack l 14:59:14 ack k 15:00:02 ege: ok then we have 100% consensus 15:00:05 proposal: Create a new repository called wot-binding-registry to manage the new registry and use the old repository for managing the individual bindings 15:00:14 +1 15:01:22 proposal: Create a new repository called wot-binding-templates-registry to manage the new registry and use the old repository for managing the individual bindings 15:01:39 q? 15:01:43 ok good for me now 15:01:47 resolution: Create a new repository called wot-binding-templates-registry to manage the new registry and use the old repository for managing the individual bindings 15:02:50 [adjourned] 15:02:57 rrsagent, draft minutes 15:02:59 I have made the request to generate https://www.w3.org/2025/04/09-wot-td-minutes.html kaz 16:30:51 kaz has joined #wot-td 17:27:01 Zakim has left #wot-td