14:01:04 RRSAgent has joined #wot-td 14:01:08 logging to https://www.w3.org/2025/01/16-wot-td-irc 14:01:17 meeting: WoT-WG - TD-TF - Slot 2 14:01:41 rrsagent, make log public 14:01:45 rrsagent, draft minutes 14:01:46 I have made the request to generate https://www.w3.org/2025/01/16-wot-td-minutes.html kaz 14:02:26 dape has joined #wot-td 14:03:29 Mizushima has joined #wot-td 14:03:37 cris has joined #wot-td 14:03:40 present+ Kaz_Ashimura, Ege_Korkan, Daniel_Peintner, Cristiano_Aguzzi, Kunihiko_Toumura, Michael_Koster, Tomoaki_Mizushima 14:03:47 chair: Ege, Koster 14:03:51 rrsagent, draft minutes 14:03:53 I have made the request to generate https://www.w3.org/2025/01/16-wot-td-minutes.html kaz 14:04:21 Ege has joined #wot-td 14:05:03 EgeKorkan has joined #wot-td 14:05:17 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#January_15-16%2C_2024 14:07:20 scribenick: kaz 14:08:04 topic: Minutes 14:08:11 -> https://www.w3.org/2025/01/09-wot-td-minutes.html Jan-9 14:08:19 ek: (goes through the minutes) 14:08:49 ... any comments? 14:08:50 (none) 14:09:11 approved 14:09:32 present+ Luca_Barbato, Michael_McCool 14:09:39 rrsagent, draft minutes 14:09:40 I have made the request to generate https://www.w3.org/2025/01/16-wot-td-minutes.html kaz 14:09:50 luca_barbato has joined #wot-td 14:09:50 McCool has joined #wot-td 14:10:03 topic: Agenda 14:10:15 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#January_15-16%2C_2024 Agenda for today 14:10:44 ek: would like to talk about the Issue around the Binding registry 14:10:49 topic: Binding 14:11:00 subtopic: Registry inclusiveness 14:11:38 -> https://github.com/w3c/wot-binding-templates/issues/393 Issue 393 - Registry Inclusiveness 14:11:43 q+ 14:11:51 ek: should follow the W3C rule, look/feel? 14:11:54 q+ 14:11:59 ca: we can be flexible here 14:12:38 ... would be OK to use a different style 14:12:39 q+ 14:13:04 ack c 14:13:18 mm: we should recommend the same order 14:13:23 ... of the sections 14:13:45 ... e.g., Introduction 14:14:22 q? 14:14:45 ... should be defined 14:14:49 mjk has joined #wot-td 14:15:02 lb: anything within the registry should follow the W3C rules 14:15:22 ... regarding the look&feel, also should be the same 14:15:24 q+ 14:15:34 ack l 14:15:53 -> https://www.w3.org/TR/?filter-tr-name=&status%5B%5D=dry&status%5B%5D=cry&status%5B%5D=ry W3C (Draft) Registries 14:16:22 lb: less burden if we have the same style 14:16:45 ... should be machine readable and parsable 14:18:18 kaz: not really sure what we're talking about 14:18:30 ... the Registry Track has its specific style and structure already 14:18:40 ek: it's about the entry 14:19:49 q+ 14:19:51 ack k 14:19:53 q+ 14:20:02 ek: (shows the requirements.md) 14:20:13 -> https://github.com/w3c/wot-binding-templates/blob/main/registry-requirements.md registry-requirements.md 14:20:37 q+ 14:21:00 mm: that's still "nice to have" 14:21:24 ack m 14:21:48 q+ 14:21:53 [[ 14:21:54 The WoT binding CAN be just one section of the document. In that case, the "Link to the binding document" in the registry entry MUST point to the specific location. PDF or similar document types CAN be submitted if the "Link to the binding document" in the registry entry contains a text pointing to the section. However, HTML and Webpages SHOULD be favoured. 14:21:54 ]] 14:23:13 lb: would like to think about something similar to the IANA registry 14:23:28 mm: it's rather similar situation of MPEG here 14:23:36 ... everyone still implements the format 14:23:58 ... some of the entries are not free 14:24:23 q? 14:24:27 ack m 14:25:26 q+ 14:25:43 (I would like to propose a compromise...) 14:30:22 ack k 14:31:05 kaz: think the question here "Should the binding document be required to follow W3C copyright rules, and should the document follow the exact template and look and feel?" should be clarified a bit 14:31:38 ... e.g., what kind of binding definition document (our own ones or externally defined ones) 14:31:54 ... and then the copyright, style, and so on can be discussed 14:32:33 ek: question 1.1: should the linked binding document have the W3C copyright? 14:32:57 ... question 1.2: should th elinked binding document have the same "look and feel" of the W3C documents? 14:33:29 i/ek:/ek: (tries to split the question into two pieces)/ 14:33:38 q? 14:33:41 ack lu 14:34:24 lb: binding registry document should follow the W3C style 14:34:39 ... if we provide some kind of template 14:34:52 ek: we don't really provide templates for the Binding definition 14:35:02 mm: would suggest some compromise 14:35:04 ack m 14:35:15 ... may be a published ontology 14:35:25 ... organized by the other SDOs 14:35:39 ... need to think about more than just a link 14:36:02 q+ 14:36:33 ek: seems we're restarting the big part of the discussion... 14:37:22 ... thought the registry document itself would just include links 14:37:57 q? 14:37:57 q+ 14:39:44 ack k 14:40:02 kaz: think we're all thinking about something like the IANA registry 14:40:27 ... so the registry document itself only manages the list of the entries with links to the actual definition documents 14:40:35 q+ 14:40:40 ... and the definition documents might be generated by external SDOS 14:40:51 ... so we can't control the copyright or style of them 14:40:55 ek: right 14:41:06 q? 14:41:12 mm: agree 14:41:14 ack m 14:41:14 ack m 14:42:19 lb: guess we can have the situation with only the index rather than the links 14:42:51 ... all we need is showing a link for the binding definition 14:43:00 ... let's go for this direction 14:43:23 ... we have a correction of bindings 14:43:35 q+ 14:43:58 ... if we want to keep the full registry, then there is a potential burden 14:44:09 ack lu 14:44:52 ... if the custodian hosts, the implementation is easier 14:45:20 ... if not, it's easier to write the documents but more difficult to implement 14:45:28 mm: agree with that point 14:45:54 ... would try to make WoT relevant 14:46:04 lb: don't see what would be problematic 14:46:28 ... let me explain a bit 14:47:06 ... if there is a proprietary protocol, you still might want to use it 14:48:08 q+ 14:48:28 mm: it's huge amount of legal work... 14:48:36 ack m 14:49:04 q+ 14:49:51 kaz: btw, the answer for the question should say "We cannot do it for all the bindings for legal reasons." 14:50:16 EgeKorkan has joined #wot-td 14:50:19 ... for free kind of protocols or our own defined protocols, we can generate binding documents ourselves 14:50:27 mm: yeah, there are gray areas 14:50:31 ack k 14:50:32 ack m 14:51:00 ek: can understand it would be easier for implementers if we could define all the binding documents 14:51:21 ... but defining everything in the W3C manner is difficult 14:51:30 (btw... the RTP registry has been closed... https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-payload-registry/) 14:52:16 ek: so could we make a consensus here? 14:52:32 lb: if the consensus is just keeping the index, that's fine 14:53:11 ... but we can set a rule for those who are out of our target 14:53:54 ... also we have a need a way to reach the linked documents which actually define the bindings 14:54:05 ... so we need a way to verify them 14:54:15 q? 14:54:17 q+ 14:54:33 ek: (adds some points) 14:54:35 (could just add a rule that the link should be stable and if it can't be resolved the entry will be removed from the registry, and also that the document should be a specific stable version - not updated in-place) 14:55:11 ... if the document is detected to change and not fulfill the requirements, it can be removed. 14:56:02 ... would make a decision now 14:56:17 ... the custodian does not host the binding documents 14:56:27 ca: does not have to? 14:56:31 ek: right 14:56:51 kaz: that's inline what I mentioned 5 mins ago 14:57:07 ek: then 2nd point 14:57:56 zkis has joined #wot-td 14:57:57 ... as the custodian does not host it, it cannot enforce the W3C copyright. 14:58:03 q? 14:58:05 ack k 14:58:13 kaz: we should make resolution for those points 14:58:27 .... and for that purpose "it" here should be clarified again 14:58:31 mm: yeah 14:59:12 ... also we should define what the minimum requirements would be 14:59:22 proposal: Custodian does not have to host the binding documents and associated files. Custodian hosts the summary document. The summary document's content will be decided later 14:59:48 q+ 15:00:27 ack k 15:00:33 resolution: Custodian does not have to host the binding documents and associated files. Custodian hosts the summary document. The summary document's content will be decided later 15:01:38 proposal: As the custodian does not host the binding document, it cannot enforce the W3C copyright. Thus, the linked binding document does not have to follow W3C copyright. 15:02:50 draft resolution: As the custodian does not host the binding document, it cannot enforce the W3C copyright. Thus, the linked binding document does not have to follow W3C copyright. 15:03:58 i/draft/kaz: 2nd point should be a "draft resolution" now and to be confirmed with McCool 15:04:00 [adjourned] 15:04:03 rrsagent, draft minutes 15:04:05 I have made the request to generate https://www.w3.org/2025/01/16-wot-td-minutes.html kaz 15:35:21 EgeKorkan has joined #wot-td 16:07:33 EgeKorkan has joined #wot-td 16:20:45 EgeKorkan has joined #wot-td 16:36:37 EgeKorkan has joined #wot-td 16:52:28 EgeKorkan has joined #wot-td 17:00:30 Zakim has left #wot-td 17:08:20 EgeKorkan has joined #wot-td 17:24:13 EgeKorkan has joined #wot-td 17:39:52 EgeKorkan has joined #wot-td 17:55:43 EgeKorkan has joined #wot-td 18:11:33 EgeKorkan has joined #wot-td 18:27:28 EgeKorkan has joined #wot-td 18:38:03 EgeKorkan has joined #wot-td 18:53:52 EgeKorkan has joined #wot-td 19:09:19 EgeKorkan has joined #wot-td 19:25:03 EgeKorkan has joined #wot-td 19:39:03 EgeKorkan has joined #wot-td 19:44:00 EgeKorkan has joined #wot-td