14:02:08 RRSAgent has joined #wot-td 14:02:08 logging to https://www.w3.org/2022/11/02-wot-td-irc 14:02:22 meeting: WoT-WG - TD-TF 14:02:52 present+ Kaz_Ashimura, Ege_Korkan, Michael_McCool, Sebastian_Kaebisch 14:03:42 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#November_2.2C_2022 14:05:47 cris_ has joined #wot-td 14:05:59 scribenick: cris_ 14:06:32 dape has joined #wot-td 14:06:43 topic: minutes review 14:07:13 ege: last week we discussed the binding templates topics 14:07:24 ... ontology links 14:08:04 ... then we discussed TD topics 14:08:07 ... CR transition 14:08:32 ... we decided to have another test fest in December 14:08:50 ... we look at some deferred PR and propose closing issues 14:09:20 ... no blockers and started the next step for CR transition 14:09:33 ... does anyone have any change requests? 14:09:49 ... hearing none; minutes are approved 14:10:00 topic: Agenda 14:10:09 ege: anyone wants to add something? 14:10:10 ... ok 14:10:30 topic: TD Binding Templates 14:10:43 subtopic: PR on content type 14:11:07 ege: I move the content of the pr to the appendix and in the text a put link a to it 14:11:25 ... got feedback from Klaus 14:11:34 ... headers need to be taken into account 14:11:40 ... now it is ready for review 14:12:14 q+ 14:12:15 ... I'll do examples later 14:12:31 daniel: I was wondering if it covers all cases 14:12:41 ege: I hope there isn't 14:12:47 ... do you have a case in mind? 14:13:12 ack dape 14:13:18 s/there isn't/it is covering all the cases 14:13:24 s/there isn't/it is covering all the cases/ 14:14:20 sebastian has joined #wot-td 14:14:23 q+ 14:14:30 i|last week|-> https://www.w3.org/2022/10/26-wot-td-minutes.html Oct-26| 14:14:40 sebastian: it is very helpful 14:14:51 q? 14:14:53 ack s 14:14:56 ... I like the fact it is in the appendix 14:15:08 cris: +1 14:15:24 rrsagent, make log public 14:15:30 ege: any other concerns or questions? 14:15:31 rrsagent, draft minutes 14:15:31 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 14:15:36 q+ 14:15:37 q+ 14:16:18 cris: so it is ready for merge? 14:16:20 ege: yes 14:16:34 s/it is/is it/ 14:16:37 ack c 14:16:58 q+ 14:17:00 ack k 14:17:05 kaz: these changes should be discussed with WoT developers 14:17:09 chair: Ege/Sebastian 14:17:18 ege: it is very important to get feedback from developers 14:17:42 present+ Cristiano_Aguzzi, Daniel_Peintner, Michael_Koster, Tomoaki_Mizushima 14:17:57 ... we are planning office hours in the WoT CG dedicated to get this kind of feedbacks 14:18:02 s/these changes/this kind of complicated description/ 14:18:11 sebastian: I agree with this aspect 14:18:25 q? 14:18:27 ack s 14:18:47 ... regarding the structure of Binding Templates, too 14:19:02 ege: we'll discuss it in a moment 14:20:19 rrsagent, draft minutes 14:20:19 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 14:20:25 ... there are some bits of this hints in the Scripting API 14:20:58 cris: +1 14:21:03 ege: ok merging PR 14:21:31 topic: Binding Templates 14:21:48 subtopic: new charter proposal 14:22:01 ege: I got already some initial feedback 14:22:08 ... I fixed a bunch of issues 14:22:19 i|I move the|-> https://github.com/w3c/wot-thing-description/pull/1564 wot-thing-description PR 1564 - explain contentType usage 14:22:26 rrsagent, draft minutes 14:22:26 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 14:22:28 ... but I waiting for Klaus to further investigate some comments 14:22:44 subtopic: PR 182 14:23:14 ege: I fixed merge conflicts and merged as discussed last time 14:23:18 i|I got already|-> https://github.com/w3c/wot/pull/1035 wot PR 1035 - Create new charter proposal for binding templates| 14:23:19 q+ 14:23:42 ack k 14:23:50 https://github.com/w3c/wot-binding-templates/pull/182 14:24:30 s/https/-> https/ 14:24:38 subtopic: PR modbus design 14:24:52 s/182/182 PR 182 - Ontology links/ 14:25:29 ege: cristiano provided fixes for the feedbacks that he got last time 14:25:40 https://github.com/w3c/wot-binding-templates/pull/183 14:25:53 s/https/-> https/ 14:26:10 ege: I looked for feedback inside siemens and they are ok with both URI proposals 14:26:22 s/183/183 PR 183 - feat(modbus): move addres and quantity to URL components/ 14:26:35 rrsagent, draft minutes 14:26:35 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 14:26:43 ... URI base design is the currently understood as best practice 14:27:04 ... if we merge this PR this means that we have to follow the same approach with the other bindings 14:28:30 cris: I agree that this PR has implications greater than the modbus binding 14:28:39 ege: I plan to put this rule in the core document 14:29:51 topic: Issues 14:29:56 https://github.com/w3c/wot-binding-templates/issues/196 14:30:14 subtopic: Issue 196 14:30:25 ege: it is about document structure 14:31:06 i|it is|-> https://github.com/w3c/wot-binding-templates/issues/196 Issue 196 - Adding binding template document structure figure| 14:31:16 q+ 14:31:37 q+ 14:31:43 ack s 14:31:55 sebastian: it is helpful to have this overview, but we need to collect feedback from the Japanese community group 14:32:22 ... is it really payload binding or serialization binding ? 14:32:31 ege: it is about serialization 14:32:50 ... maybe we can call it: payload serialization binding template 14:32:57 sebastian: ok 14:33:26 kaz: Is this a future proposal? 14:33:46 ... because it split the Binding Templates document even more 14:34:13 ege: it is not changing anything, it describe the current structure 14:34:22 s/describe/describes/ 14:34:43 kaz: it is more important to describe the external relationships with the existing documents 14:35:02 ... namely: Architecture, Discovery, Profiles, and Thing Description 14:35:08 ege: I see 14:35:43 McCool has joined #wot-td 14:35:50 ... we can extend the graph with that information 14:35:57 ... we have the "use" relation 14:36:26 s/existing document/existing specifications/ 14:36:56 q+ 14:37:34 kaz: the diagram might be useful for some of the people, but we can use text to describe the same relations. 14:38:01 ege: ok but I think figure can still be added 14:38:33 kaz: the diagram it is fine, but some developers might not sure what the relation "use" means 14:38:55 ... that is why text would help to clear that out 14:39:31 subtopic: Issue 187 14:39:31 https://github.com/w3c/wot-binding-templates/issues/187 14:40:24 s/it is fine/itself might be fine/ 14:40:35 s/not sure/not be sure/ 14:42:58 s/https/-> https/ 14:43:14 s/187/187 Issue 187 - [Modbus] Usage of "zeroBasedAddressing" Parameter/ 14:43:28 cris: I'm not sure about why we introduced that parameter, I have to recall the history 14:43:55 ... and then we can discuss how it relates to the new changes in the modbus pr 14:44:18 q+ 14:44:24 ack k 14:44:31 subtopic: YYY 14:44:38 https://github.com/w3c/wot-binding-templates/issues/139 14:44:52 s/YYY/Issue 139/ 14:44:57 q? 14:45:06 ege: the issue is about how we can describe xml payloads in TD 14:45:15 s/https/-> https/ 14:45:30 daniel: this conversion is coming from a spec that Taki and I worked on previously 14:45:36 https://www.w3.org/XML/EXI/docs/json/exi-for-json.html 14:45:37 ... it is not a real spec sadly 14:45:42 s/139/139 Issue 139 - XML template is more for green field devices/ 14:46:14 ... x-query did something similar 14:46:36 ... there were some downsides 14:47:16 q+ 14:47:45 ege: that should cover how to validate the payload with json schema, but not how to describe the payload with json schema 14:48:14 daniel: it is a lossy conversion 14:48:29 ... there are corner cases 14:48:56 ack d 14:49:34 ege: I think we can just state the corner cases and do a best effort approach 14:49:39 daniel: that's right 14:55:13 sebastian has joined #wot-td 14:56:31 ege: main question is who is motivated to bring up a proposal? 14:56:35 q+ 14:56:36 daniel: I can issue a proposal 14:56:38 ack c 14:57:35 cris: you can use the PR that I did as a template if you like 14:57:43 q+ 14:57:45 q? 14:58:03 kaz: I don't understand the need of the feature 14:58:11 ... the issue is one year old 14:58:36 ... we need to clarify the requirements 14:58:42 ack k 14:59:06 s/requirements/priority of the requirements/ 14:59:11 q+ 14:59:24 sebastian: sadly there was no time for working on this 14:59:25 ack s 14:59:39 ... we can take a specific example 14:59:50 q+ 15:00:45 ... there are a couple of ISO and other formats to look at 15:00:56 ... also ask feedback from people 15:01:23 ack k 15:01:29 kaz: yeah, keep in mind to importance to clarify the industry need for this feature 15:01:37 s/need of/need for/ 15:02:40 s/kaz: yeah, keep in mind to importance to clarify the industry need for this feature/please continue to clarify that kind of industry need for all the features. not only for this feature but all the features, I mean./ 15:03:09 sebastian: also OPC-UA use xml 15:03:20 ... among other formats 15:03:42 subtopic: Issue 93 15:04:02 https://github.com/w3c/wot-binding-templates/issues/93 15:04:06 ege: propose closing 15:04:14 ... any objections ? 15:04:23 s/https/-> https/ 15:04:35 s/93/93 Issue 93 - Create RDF representations of CoAP and MQTT vocabulary/ 15:04:40 ... closed 15:04:50 subtopic: Issue 194 15:05:02 https://github.com/w3c/wot-binding-templates/issues/194 15:05:20 s/https/-> https/ 15:05:33 ege: feedback from a dev, it request a better design of form operations 15:05:35 s/194/194 Issue 194 - Improve the htv:methodName, cov:method usage/ 15:06:01 q+ 15:06:40 cris: I would favor a better design of forms 15:06:45 ack c 15:07:47 sebastian: we avoided a fixed index position for inferencing features 15:08:40 ... we had this arithmetic approach in the beginning 15:08:44 ... but it was more complex 15:09:15 cris: I agree 15:09:57 topic: Thing Description 15:10:24 topic: Agenda 15:10:44 sebastian: plug fest, and closing issues 15:12:30 dape has joined #wot-td 15:12:36 TOPIC: TD 15:13:24 SUBTOPIC: Add CR exit criteria in sotd section 15:13:37 SK: Swick asked for exit criteria 15:13:45 ... has been added in the meanwhile 15:14:02 i/TOPIC: TD/scribenick: dape/ 15:14:25 i|Swick|-> https://github.com/w3c/transitions/issues/467 CR Transition Request for TD 1.1| 15:14:29 ... 15:14:47 SK: seems exit criteria is still missing in SOTD 15:14:59 rrsagent, make log public 15:15:02 MMC: I am double checking 15:15:03 rrsagent, draft minutes 15:15:03 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 15:15:29 SK: Ahh, only applied to publication folder and not main branch 15:16:11 s|TD Binding Templates|TD and Binding Templates| 15:16:14 https://github.com/w3c/wot-thing-description/pull/1736/files 15:16:34 s/https/-> https/ 15:17:00 q+ 15:17:07 s/files/files Files changed in PR 1736 - CR exit criteria/ 15:17:16 SK: at risk criterias with no more than 2 implementations will be converted to informative statement 15:17:26 present+ Michael_McCool 15:17:30 MMC: special clause 15:17:41 ... old vs new Ids 15:17:44 present+ Erich_Barnstedt 15:18:15 ... remaining at risk items can be checked against old publication 15:19:19 SK: will create PR to add this exit criteria statement also to main branch 15:19:33 MMC: makes sense 15:19:51 https://github.com/w3c/transitions/issues/467 15:20:08 SK: see transition request link above 15:20:58 SUBTOPIC: Missing Implementations 15:21:09 SK: Should look "at-risk" features 15:21:37 ... implementors might try to overcome such features 15:21:47 ... PlugFest planned in December also 15:22:17 ... please check your implementations 15:22:24 ... 1,5 months left 15:22:28 i|Should|-> https://w3c.github.io/wot-thing-description/#sotd features at risk listed on the SoTD section of the TD 1.1 draft| 15:22:42 q+ 15:22:46 ack s 15:22:46 SK: any news from PlugFest call 15:22:48 ack m 15:22:56 MMC: will create readme under events 15:23:07 ... please have a look at it and check the goals 15:23:19 https://github.com/w3c/wot-testing/tree/main/events/2022.12.Online 15:23:28 s/https/-> https/ 15:23:33 ... resolve at risk items is one goal 15:23:52 s/Online/Online README.md for the December Testfest/ 15:23:56 ... some assertions seems to miss updates ... to fill in certain blanks 15:25:15 ... we seem to have 2 conflicting CSV files 15:25:47 ... XXXX in a row indicate no input given 15:26:41 s/will create/have created a/ 15:27:07 ... we need 2 passes for each feature 15:27:10 -> https://github.com/w3c/wot-thing-description/blob/20a66ccef95be67e5848ed51a9656bed9f62e12a/testing/all-TD-implementations.csv Lagally's generated CSV to see which implementations cover which features 15:27:23 ... atrisk.csv lists all missing assertions 15:27:37 https://github.com/w3c/wot-thing-description/blob/Impl-Xref/testing/atrisk.csv 15:27:52 ... Kaz suggested to look for volunteers 15:28:40 Kaz: I suggest all to join next TestFest call 15:29:00 SK: I will be not available next week 15:29:10 s/call/call or at least sign up on the volunteers list ;) 15:29:14 MMC: I will be out-of-office for 2 weeks also 15:29:19 rrsagent, draft minutes 15:29:19 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 15:29:41 q? 15:29:42 ack k 15:29:43 EK: I can join the call and will try to push forward 15:30:01 SUBTOPIC: Check the status of open PRs 15:30:11 -> https://github.com/w3c/wot-thing-description/pulls 15:30:44 SK: PR 1684 15:30:52 -> https://github.com/w3c/wot-thing-description/pull/1684 15:31:10 SK: ethieblin provided feedback 15:31:27 CA: she is mentioning other issues also 15:31:38 ... I guess we can tackle these in other PRs 15:31:56 ... this PR is about strings 15:32:15 ... SHACL has plain strings and language strings 15:32:32 ... render script has bugs too 15:33:02 ... 2nd comment in PR, having 2 dataTypes 15:33:22 s/1684/1684 PR 1684 - Fix shacl, context and ontology/ 15:33:28 ... need to fix this everywhere 15:33:47 ... we can say that title is human readable 15:34:16 ... in this PR I forced everything to be a language string 15:34:31 ... I used default language to EN 15:34:42 ... ethieblin mentioned this cannot be changed 15:35:01 ... I need to find a solution.. default language can be set by user 15:35:40 ... will ask ethieblin for clarifications 15:35:44 ... other point 15:36:16 ... hasSecurityConfiguration changed @type to string 15:36:33 ... ethieblin makes the point it should remain @id 15:37:01 q+ 15:37:17 ... suggest to fix it later, in another PR 15:37:30 SK: what would be the solution? 15:37:41 CA: using @id is correct 15:38:08 MMC: I think it is a string, not an URI 15:38:37 ... we could have a conversion process 15:39:25 CA: Mhh, I think we have a problem here 15:39:43 ... security definitions are translated to URIs 15:39:59 MMC: string is supposed to be unique 15:40:07 ... can use pre-processor 15:40:36 CA: we need to retain the id in the RDF process 15:41:17 SK: Does this mean ethieblin is not correct? 15:41:42 CA: Yes and no... but there are misalignments 15:43:02 Kaz: PR 1684 is identified as editorial change 15:43:16 ... doesn't it impact implementations ? 15:43:39 ... is it a bug fix? 15:43:48 ... if so we should fix NOW 15:44:08 SK: This PR does not have impact on tables 15:44:20 Kaz: Please check tables ... I see changes 15:44:35 CA: I do not expect changes... but yes there are changes 15:44:54 -> https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/1684/6e2d51a...relu91:6e6df6e.html#thing diff 15:45:01 ... string to langString 15:45:15 SK: That's a problem.. we cannot change that now 15:45:34 s|-> https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/1684/6e2d51a...relu91:6e6df6e.html#thing diff|| 15:45:41 CA: I think we can leave it as it was... I will revert this change 15:45:44 i|I do not|-> https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/1684/6e2d51a...relu91:6e6df6e.html#thing diff| 15:45:49 rrsagent, draft minutes 15:45:49 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 15:46:08 SK: Yes, should show up as string again 15:46:24 CA: Okay, will do and it will be an editorial change again 15:47:37 CA: there was one more issue 15:47:51 ... hasRelationType used to be ObjectProperty 15:48:25 ... seems we just need strings.. not always URIs 15:49:34 SK: Suggest to stick to string to not introduce changes 15:49:43 ... version 1.0 used string also 15:50:02 CA: Okay, that leave it as it is 15:50:26 s/that leave/let's leave 15:51:07 ... will also check examples... ethieblin pointed at some examples 15:52:45 CA: BTW, added GitHub action scripts 15:52:52 ... like validation 15:52:57 ... I added some tests 15:53:20 ... people can provide more valid TDs 15:53:52 EK: Did you move TM models 15:53:54 CA: Yes 15:54:17 SK: Cool 15:54:47 ... GitHub actions does what exactly? 15:55:20 CA: It takes TDs and translates it and checks RDF 15:55:29 ... it also does SHACL validation 15:55:45 ... but it is very basic since we just have some simple examples 15:56:11 SK: Would be nice to test all TDs from PlugFests 15:56:22 CA: Yes, but it would be a big impact .. 15:56:44 https://github.com/thingweb/thingweb-playground/tree/master/packages/core/examples/tds/valid 15:56:48 EK: for TD 1.0 we have TDs that cover all features 15:57:05 ... not covering all features of 1.1 yet 15:57:33 q? 15:57:49 EK: We also have examples for TMs 15:58:30 CA: Can we create a script that merges all TDs into one BIG TD 15:58:39 ... and test this BIG TD ? 15:58:48 EK: security might cause issues 15:59:14 SK: PR looks good... some more changes needed ... recorded in comments 15:59:40 CA: I will work on it 16:00:06 SK: Suggest to check next week again.. or in 2 weeks 16:00:24 q? 16:00:26 ack k 16:00:37 ... other PRs are not urgent and we should wait till CR is published 16:01:49 SK: Homework for everyone... added "propose closing" labels to some issues 16:01:53 ... please have a look 16:02:38 [adjourned] 16:02:46 rrsagent, draft minutes 16:02:46 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 16:24:12 s/topic: TD// 16:24:20 s/topic: Agenda// 16:24:22 rrsagent, draft minutes 16:24:22 I have made the request to generate https://www.w3.org/2022/11/02-wot-td-minutes.html kaz 18:06:40 kaz has joined #wot-td 18:22:07 Zakim has left #wot-td