15:06:55 RRSAgent has joined #wot-td 15:06:59 logging to https://www.w3.org/2022/12/21-wot-td-irc 15:07:44 dape has joined #wot-td 15:10:12 sebastian has joined #wot-td 15:11:25 brb 15:13:04 Meeting: WoT Thing Description 15:13:21 chair: Ege_Korkan, Sebastian_Kaebisch 15:17:19 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#December_21.2C_2022 15:18:06 s/Meeting: WoT Thing Description/Meeting: WoT-WG - TD-TF/ 15:19:24 back 15:20:45 s/back// 15:21:33 topic: Minutes 15:21:40 present+ Kaz_Ashimura, Ege_Korkan, Cristiano_Aguzzi, Daniel_Peintner, Michael_Koster, Sebastian_Kaebisch 15:21:42 -> https://www.w3.org/2022/12/07-wot-td-minutes.html 15:21:50 s/html/html Dec-7/ 15:24:38 any objections? 15:24:47 no 15:24:56 minutes approved 15:25:18 topic: Testfest results 15:25:53 EK: please check the at-risk list 15:26:31 -> https://github.com/w3c/wot-thing-description/blob/main/testing/atrisk.csv 15:26:54 EK: still some assertions where we need implementations 15:27:10 q+ 15:28:30 Kaz: we should clearify what is really problematic 15:29:26 q+ 15:29:58 q+ 15:30:07 ack k 15:30:33 DP: is it about the manuel or auto check? 15:30:38 ack dape 15:32:09 Kaz: we should clearify why implementator have done and not done implementations 15:32:47 q+ 15:32:57 ack s 15:34:00 SK: I understood that we should take care all yeallow highlighted assertions and ask implementators why they have trouble in implementaions 15:37:21 ack k 15:37:27 present+ Tomoaki_Mizushima 15:37:37 zakim, who is on the call? 15:37:37 Present: Kaz_Ashimura, Ege_Korkan, Cristiano_Aguzzi, Daniel_Peintner, Michael_Koster, Sebastian_Kaebisch, Tomoaki_Mizushima 15:38:15 Kaz: we should have a table which shows which data came from. We can double check or ask the implementors 15:38:26 q+ 15:38:34 q? 15:41:05 SK: I think we already have very good results so far. Still time to have implementions for the remeaning assertations 15:41:51 Kaz: for TD this is true, we should also consider Discovery and Architecture which has more missing assertions 15:42:09 s/this is/that is/ 15:42:17 s/, we/, but we/ 15:43:14 q+ 15:43:17 15:45:07 ack s 15:45:07 ack k 15:45:11 SK: lets check the results of Architecture 15:45:31 15:47:02 -> https://w3c.github.io/wot-architecture/testing/report11.html latest Implementation for WoT Architecture as an example 15:47:26 agree 15:49:18 https://w3c.github.io/wot-architecture#arch-security-consideration-communication-platform 15:49:47 i|https|31: arch-security-consideration-communication-platform| 15:49:57 SK: most likely we have already more implemtations of the asserations. Each TD that was generated for a device have to fullfill the security requirements, otherwise you are not able to interact 15:52:35 15:53:00 q+ 15:53:08 q+ 15:53:12 ack dape 15:54:00 q+ 15:54:31 ack c 15:54:38 ack k 15:55:31 q+ 15:57:02 ack cris_ 15:57:33 kaz: I don't think we're requiring people to implement device virtualization like VMware but using WoT Thing Description to describe device capability is already a kind of abstraction here 15:57:51 s/but/but do think/ 16:00:26 (all check some more assertions) 16:00:31 https://github.com/w3c/wot-architecture/issues/888 16:01:16 s/more assertions/more assertions, and create an Issue for wot-architecture) 16:01:24 s/https/-> https/ 16:09:43 s/888/888 wot-architecture issue 888 - Evaluating At Risk Assertions/ 16:12:54 (Ege records the comments within the issue 888 above) 16:13:00 rrsagent, make lg public 16:13:00 I'm logging. I don't understand 'make lg public', kaz. Try /msg RRSAgent help 16:13:05 s/rrsagent, make lg public// 16:13:08 rrsagent, make log public 16:13:16 rrsagent, draft minutes 16:13:17 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 16:13:28 q+ 16:14:34 sebastian has joined #wot-td 16:14:35 ack k 16:14:53 sorry, I had computer problem and needed to restart 16:14:58 kaz: let's check with Lagallly based on this comment tomorrow during the Architecture call 16:15:01 https://github.com/w3c/wot-thing-description/pull/1758 16:15:13 i/https/topic: TD/ 16:15:54 i/https/subtopic: PR 1758/ 16:16:07 s/https/-> https/ 16:16:48 I can take minutes again 16:16:58 s/1758/1758 PR 1758 - Updating at risk assertions in the main body/ 16:17:08 rrsagent, draft minutes 16:17:09 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 16:17:49 EK: there is still OAuth2 code flow implementation needed 16:17:57 s/brb// 16:17:59 rrsagent, draft minutes 16:18:01 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 16:18:13 topic: Binding Templates 16:18:14 i/don't think w/scribenick: kaz/ 16:18:33 subtopic: PRs 16:18:34 s/sorry, I had computer problem and needed to restart// 16:18:45 s/I can take minutes again// 16:18:49 rrsagent, draft minutes 16:18:50 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 16:19:51 -> https://github.com/w3c/wot-binding-templates/pull/223 16:20:14 s/223/223 PR 223 - Orphaned Section Reorg - Part 1: Protocols/ 16:20:18 rrsagent, draft minutes 16:20:19 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 16:20:29 EK: split commits into meaningful sections 16:21:37 16:21:42 q+ 16:22:47 q+ 16:23:03 Kaz: thanks for your efford 16:23:42 ack k 16:24:11 ... does it make sense to move the orphan section back the the main document? 16:24:34 s/efford/effort/ 16:26:37 EK: I would prefer as is. It easer for readers 16:26:42 s/does it make sense to move the orphan section back the the main document?/which would be easier, (1) this way (=putting the "orphaned sections" from the Appendix back to the main body of the current Editor's draft or (2) once revert to the published version of the Note, which includes all the "orphaned sections" already in it./ 16:26:59 s/in it/in it and then add necessary changes based on that/ 16:27:05 SK: not sure about the term "orphaned". Should be this used in a spec document? 16:27:06 rrsagent, draft minutes 16:27:07 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 16:27:44 q+ 16:27:44 ack s 16:28:08 ack k 16:28:35 EK: can also say uncategorized or temprary sections 16:29:16 https://github.com/w3c/wot-binding-templates/pull/224 16:29:38 s/about the term "orphaned"/if the term "orphaned" is appropriate here/ 16:29:54 s/Should be this/Should this be/ 16:30:03 EK: last time we also said that we should start working on a surcay to get feedback from developers 16:30:17 s/surcay/survey 16:31:08 q+ 16:31:17 16:32:55 Kaz: getting feedback is important for next WG, however, we should address more broader stakeholders 16:34:31 ... we should think who we want to contact rather than which meaöinglist we like to use 16:34:42 s/meaöinglist/mailinglist 16:36:10 ... we should think about Echonet, Microsoft, etc in this discussion 16:36:43 ack k 16:36:52 EK: are there other feedbacks? 16:37:06 s/we should think/for example, we should think/ 16:37:37 ... which tool should be use? From W3C? 16:37:48 Kaz: anything is fine 16:38:16 s/use/used 16:39:22 s/we like/we'd like/ 16:39:29 .. if there are quirenstions I can create W3C questionnaire 16:41:41 s/if there are quirenstions/if you can clarify the questions and the style,/ 16:41:46 q+ 16:42:06 ack k 16:42:10 s/quirenstions/questions 16:42:15 topic: TD 16:42:44 SK: we need a resolution about the ReSpec errors 16:43:40 -> https://w3c.github.io/wot-thing-description/publication/ver11/5-cr/#toc 16:44:24 SK: proposal is to use the "ignore" solution as given by ReSpec. Also agreed this in the charis call 16:44:24 [[ 16:44:25 * Normative reference to "base direction" found but term is defined "informatively" in "i18n-glossary". 16:44:25 How to fix: You can do one of the following... 16:44:25 * Get the source definition to be made normative 16:44:25 * Add a class="lint-ignore" attribute to the link. 16:44:25 * Use a local normative proxy for the definition à la term 16:44:27 To silence this warning entirely, set lint: { "informative-dfn": false } in your respecConfig. 16:44:29 Occurred 1 times at: 16:44:31 element 16:44:35 * Normative reference to "first-strong detection" found but term is defined "informatively" in "i18n-glossary". 16:44:38 How to fix: You can do one of the following... 16:44:40 * Get the source definition to be made normative 16:44:42 * Add a class="lint-ignore" attribute to the link. 16:44:44 * Use a local normative proxy for the definition à la term 16:44:46 To silence this warning entirely, set lint: { "informative-dfn": false } in your respecConfig. 16:44:48 Occurred 1 times at: 16:44:50 element 16:44:52 * Normative reference to "base direction" found but term is defined "informatively" in "i18n-glossary". 16:44:54 How to fix: You can do one of the following... 16:44:56 * Get the source definition to be made normative 16:44:58 * Add a class="lint-ignore" attribute to the link. 16:45:00 * Use a local normative proxy for the definition à la term 16:45:02 To silence this warning entirely, set lint: { "informative-dfn": false } in your respecConfig. 16:45:06 Occurred 1 times at: 16:45:08 element 16:45:10 dape has joined #wot-td 16:45:10 ]] 16:45:12 kaz: we should fix index.html and index.template.html at wot-thing-description 16:45:48 ... and index.html at wot-thing-description/publications/5-cr 16:45:58 EK: I can help here until tomorrow. 16:47:00 s/until/by/ 16:47:03 SK: we should do a resolution about decission 16:47:19 s/decission/our decission 16:47:27 Kaz: yes 16:47:34 proposal: In order to avoid ReSpec errors, the TF decided to add class="lint-ignore" to usage of "base direction" and "first-strong detection" definitions in the document 16:47:43 s/decission/decision/ 16:47:49 +1 16:48:02 RESOLUTION: In order to avoid ReSpec errors, the TF decided to add class="lint-ignore" to usage of "base direction" and "first-strong detection" definitions in the document 16:49:50 (Ege and Sebastian handle the files at wot-thing-description, Kaz will handle the files at wot-thing-description/publications/5-cr) 16:51:11 rrsagent, draft minutes 16:51:12 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 16:51:35 here is the -> https://github.com/w3c/wot-thing-description/issues/1759 16:51:54 s/here is the/here is the 'reminder' issue 16:51:55 i/need a resolution/subtopic: Publication/ 16:52:32 i|1759|subtopic: Issue 1759| 16:53:35 s|subtopic: Issue 1759|| 16:53:35 subtopic: PR 1684 - Fix shacl, context and ontology 16:53:45 -> https://github.com/w3c/wot-thing-description/pull/1684 16:54:32 EK: we will merge it after CR publication 16:54:57 https://github.com/w3c/wot-thing-description/issues/1350 16:55:12 subtopic: 'Propose closing' issues 16:55:36 s/subtopic: 'Propose closing' issues// 16:55:40 EK: no objections -> close 16:55:41 i|1350|subtopic: 'Propose closing' issues| 16:56:09 s/https/-> https/ 16:56:53 ok, many thanks for your support this year. Merry Christmas and happy new year :-) 16:57:06 s/1350/1350 Issue 1350 - Review use cases document / align terminology / identify gaps| 16:57:11 https://github.com/w3c/wot-thing-description/issues/1759 16:57:16 https://github.com/w3c/wot-thing-description/issues/1518 16:57:38 EK: both issues are redundant. I will close 1518 16:58:20 s|https://github.com/w3c/wot-thing-description/issues/1759|-> https://github.com/w3c/wot-thing-description/issues/1759 Issue 1759 - Reminder: ReSpec fixes| 16:58:25 https://github.com/w3c/wot-thing-description/issues/1539 16:58:42 s/https://github.com/w3c/wot-thing-description/issues/1539/-> https://github.com/w3c/wot-thing-description/issues/1539 16:58:52 EK: any objections? 16:58:52 s|https://github.com/w3c/wot-thing-description/issues/1518|-> https://github.com/w3c/wot-thing-description/issues/1518 Issue 1518 - ReSpec Warnings - Normative reference defined in informative document| 16:58:54 no 16:59:01 will be close 16:59:04 rrsagent, draft minutes 16:59:05 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 16:59:11 https://github.com/w3c/wot-thing-description/issues/1747 16:59:20 -> https://github.com/w3c/wot-thing-description/issues/1747 16:59:44 EK: decide to close 17:00:07 s|s/https://github.com/w3c/wot-thing-description/issues/1539/-> https://github.com/w3c/wot-thing-description/issues/1539|| 17:00:10 rrsagent, draft minutes 17:00:11 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 17:01:39 i|any objections|-> https://github.com/w3c/wot-thing-description/issues/1539 Issue 1539 - At risk section in TD| 17:02:37 s|https://github.com/w3c/wot-thing-description/issues/1747|-> https://github.com/w3c/wot-thing-description/issues/1747 Issue 1747 - Add a warning about the "other" Thing Model specification| 17:02:40 rrsagent, draft minutes 17:02:41 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 17:03:26 i|Dec-7|scribenick: sebastian| 17:03:51 i|EK: there is still|scribenick: sebastian| 17:04:04 rrsagent, draft minutes 17:04:05 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz 17:04:35 [adjourned] 17:04:36 rrsagent, draft minutes 17:05:07 I have made the request to generate https://www.w3.org/2022/12/21-wot-td-minutes.html kaz