14:08:06 RRSAgent has joined #wot-td 14:08:10 logging to https://www.w3.org/2023/07/19-wot-td-irc 14:08:52 meeting: WoT-WG - TD-TF 14:09:33 present+ Kaz_Ashimura, Ege_Korkan, Kazeem_Oladipupo 14:10:23 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#July_19.2C_2023 14:10:35 present+ Mahda_Noura 14:11:19 cris_ has joined #wot-td 14:12:25 dape has joined #wot-td 14:12:45 present+ Cristiano_Aguzzi 14:12:58 present+ Daniel_Peintner, Michael_Koster 14:13:06 q+ 14:14:25 ack k 14:15:38 q+ 14:16:49 luca_barbato has joined #wot-td 14:17:12 scribenick: Ege 14:18:37 scribenick: cris_ 14:18:52 topic: Organizational 14:19:04 topic: previous minutes 14:19:11 ege: names were fixed 14:19:24 ... found a error I didn't scribe 14:19:34 s/a e/an e/ 14:19:58 ... also daniel name is still using his nickname 14:20:01 i|kaz: would suggest we have one-hour call for TD for a while during this extended period. We can concentrate on urgent bug fixes and planning.| 14:20:06 ... we reached a resolution 14:20:12 i|previous|kaz: would suggest we have one-hour call for TD for a while during this extended period. We can concentrate on urgent bug fixes and planning.| 14:20:17 ... we need to write an email quickly 14:20:25 i|previous|ek: ok| 14:20:45 i|names were|-> https://www.w3.org/2023/07/12-wot-td-minutes.html July-12 14:20:50 rrsagent, make log public 14:20:55 rrsagent, draft minutes 14:20:56 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:21:05 kaz: Daniel's name fixed 14:21:05 ege: any other issues? 14:21:09 present+ Jan_Romann,Tomoaki_Mizushima 14:21:10 ... minutes approved 14:21:12 rrsagent, draft minutes 14:21:13 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:21:20 topic: TPAC topics 14:21:32 chair: Ege, Koster 14:21:42 ege: please if you have anyother topic that you want to discuss please edit the agenda 14:21:54 present+ Luca_Barbato 14:21:57 ... any other topics to discuss? 14:21:57 rrsagent, draft minutes 14:21:59 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:22:10 i/would suggest/scribenick: kaz/ 14:22:21 q+ 14:22:21 i/names were/scribenick: cris_/ 14:22:23 rrsagent, draft minutes 14:22:24 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:22:30 ack k 14:22:35 ack lu 14:22:43 JKRhb has joined #wot-td 14:23:52 i|please if|-> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda#Agenda_Items TPAC WoT agenda| 14:24:08 luca: talk about connected protocols would be nice 14:24:19 ege: do you mean websockets? 14:24:45 q+ 14:25:00 luca: yes doing better with anything that as a connection state 14:25:10 kaz: ok adding that item 14:25:32 ... but it is a big question, and it is related to whole WoT not just TD 14:25:49 q+ 14:26:30 ack k 14:26:49 mjk has joined #wot-td 14:27:39 kaz: note that we were planning to have additional vF2F meetings before and/or after TPAC, so those slots might be better opportunity for brainstorming discussion about bigger questions. 14:27:42 q? 14:27:47 i/note/scribenick: kaz/ 14:27:47 q+ 14:27:58 scribenick: cris_ 14:28:28 cris: how to choose a form is another long running question. Should we talk about it? 14:28:45 i/scribenick/... we can still add that kind of topics to the agenda proposals, and talk about that during the main call next week, though./ 14:28:56 rrsagent, make log public 14:28:57 ege: we can brainstorm without any restriction, than we can choose 14:29:06 rrsagent, draft minutes 14:29:07 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:30:29 q+ 14:30:48 q+ 14:30:53 ... how to choose a form goes around normative consumption topics. 14:31:07 cris: also manageable actions 14:31:25 ack cr 14:31:32 luca: they can be grouped inside Affordance design 14:31:39 ack lu 14:31:55 mk: We are making a list of TD items 14:32:19 ... we can just refer to the list that we are making 14:32:52 ack mj 14:33:08 ... there is even less ability to get together in tpac so it is better to discuss those topics in other places 14:33:48 ... we should point point unique opportunities that TPAC enables and discuss topic related to that 14:34:13 ege: I think we can use TPAC to resolve long-standing discussions 14:34:42 q? 14:35:20 ack mjk 14:35:52 kaz: yeah, I agree. We can use the TD work items list and select the ones that make sense. 14:36:00 ... TPAC is focused on joint meetings 14:36:22 +1 for mjk and kaz 14:36:43 q? 14:36:44 ack k 14:36:48 -> https://github.com/w3c/wot/blob/main/planning/ThingDescription/work-items.md wot/planning/THingDescription/work-items.md 14:36:51 ack k 14:37:45 topic: Binding Templates publication status check 14:37:45 s/make sense./make sense, because the work-items.md already has several categories like new features and refactoring./ 14:37:52 ege: we are getting closer 14:38:20 topic: Thing description 14:38:36 ege: I started creating the Github release for 1.1 14:38:48 ... most of it is automatically generated by github 14:39:23 q+ 14:39:25 ... any objections to do that? 14:40:00 kaz: ok, but generate the final diff between the previous version and the current one to be sure there is no error. 14:41:01 q? 14:41:02 ege: yes, I agree. We will come to that 14:41:04 ack k 14:41:06 ... any other points? 14:41:23 ege: github release published 14:41:36 ... note that we have a git tag now 14:41:47 ... so you can use it as reference 14:42:03 q+ 14:42:41 q+ 14:43:00 mk: is it the 1.1 release? 14:43:02 ege: no 14:43:34 dape: regarding the publication folder we have the same html 14:43:42 ege: I linked in the release 14:45:12 ... note that currently we don't have any diff with 6-pr folder 14:45:19 subtopic: PRs 14:45:31 s/subtopic:/topic:/ 14:45:31 https://github.com/w3c/wot-thing-description/pull/1853/files 14:45:36 s/... note/ege: note/ 14:45:38 subtopic: PR 1853 14:45:51 ege: daniel just update the date and readme text 14:45:57 ... nothing problematic 14:46:00 ... any objections? 14:46:10 q? 14:46:12 ack d 14:46:14 ack k 14:46:16 ack dape 14:46:23 subotpic: PR 1854 14:46:29 i|note|kaz: you should check the diff between wot-thing-description/index.html and wot-thing description/publication/ver11/6-pr/index.html| 14:46:32 ege: minor typos 14:46:40 ... in the README 14:46:40 i/you should/scribenick: kaz/ 14:46:44 ... any objections? 14:46:48 i/note/scribenick: cris_/ 14:46:54 rrsagent, draft minutes 14:46:55 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:47:28 subtopic: PR 1844 14:47:36 ege: we agreed in the main call that I will send a email 14:48:03 topic: Issues 14:48:31 ege: TM namespace is not really active 14:48:49 ... I tried to understand what we did before 14:48:55 ... and I found some issues 14:49:03 ... first we didn't document the process 14:49:29 ... for example, we somebody go to 2022/wot/td/11 we don't know which content has been served 14:49:49 i|daniel just update the date|-> https://github.com/w3c/wot-thing-description/pull/1853 PR 1853 - Update README.md with PR note| 14:49:58 s/subotpic:/subtopic: 14:50:03 ... it seems that previous TD 1 namespace is serving an updated version of the first context 14:50:24 ... last modified was July of this year 14:50:32 i|minor typos|-> https://github.com/w3c/wot-thing-description/pull/1854 PR 1854 - Update minor typos in README| 14:50:33 ... which is weird since it is an old 14:50:36 rrsagent, draft minutes 14:50:37 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:50:43 ... td version 14:50:57 ... using diff checker I was able to understand that we were pointing to a file in the current main branch 14:51:11 q+ 14:51:19 i|we agreed|-> https://github.com/w3c/wot-thing-description/pull/1844 PR 1844 - Update schema to not allow empty op array| 14:51:21 rrsagent, draft minutes 14:51:22 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:52:31 i|TM name|subtopic: Issue 1807| 14:52:54 i|TM name|-> https://github.com/w3c/wot-thing-description/issues/1807 Issue 1807 - TM namespace not active yet| 14:54:45 q? 14:54:47 q+ 14:54:48 cris: it is ok that is ok to modify td-contex.jsonld 14:54:54 rrsagent, draft minutes 14:54:55 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 14:55:02 ... it is how the render works 14:55:14 daniel: correct, the renderer generate td-contx-1.1.jsonld 14:55:27 ack c 14:55:29 ege: then right, it should to REC1.0 14:55:42 daniel: it is a w3c admin problem 14:55:50 ege: can you have a look at it kaz? 14:56:00 kaz: we talked about this issue many times 14:56:13 ... first we should not use year number 14:56:23 ... but just the version 14:56:49 ... but given that we are using this notation in the current PR we can't change that right now 14:57:46 ... second point is please clarify the mapping between w3c namespace -> github repository 14:57:53 ... victor did it 14:58:05 ... we can re-do it for 1.1 14:58:13 ege: I agree with the previous point 14:58:23 ... but year notation is suggested by w3c 14:58:38 ... where is the mapping the Victor made? 14:59:40 kaz: we can use ns (without director's approval) or use custom namespace (with director's approval) 15:00:22 ege: back on the Victor's table, where is it? 15:00:32 kaz: it is in an issue 15:01:13 -> https://www.w3.org/2005/07/13-nsuri Namespace URL Guideline 15:01:24 ege checked the table 15:02:03 ege: that is the problem we are using not tagged link to the files 15:02:09 cris: I agree 15:02:15 kaz: we can change it in the future 15:02:27 ege: yes, I agree but now I understand we have a bug 15:03:55 ... I'll create a document with the mapping 15:03:56 kaz: it is good 15:04:08 s/it is/that is/ 15:04:37 ege: with this release we have also json schemas for TM and TDs 15:04:53 ... for them we need to allocate a new uris 15:05:18 ... we could use content-negotiation to expose schema 15:05:19 q+ 15:05:51 ...as kaz mentioned we have diffferent options 15:05:56 s|we can use ns|As I suggested (I think 6 months ago or so), we can use "https://wwww.w3.org/ns/wot" as the base URI and add sub directories for future versions and resources.| 15:05:57 ... see the doc 15:05:58 ack k 15:07:53 ack c 15:08:10 cris: no content negotiation they are two separate resources 15:08:10 q+ 15:08:30 ... I would follow the current format, although I don't like it. 15:09:47 kaz: I'm ok with any kind 15:10:06 ... of URI, they are just a way to identify a resource 15:10:33 ... I don't like current format, but given that we already published it 15:10:46 ... we should follow it 15:12:26 ege: ok 15:12:45 q+ 15:12:53 ack k 15:13:28 q+ 15:13:30 ack c 15:16:16 cris: suggesting td-schema at the end 15:16:25 ege: what about v1.1-scheme 15:16:30 cris: that also works 15:16:53 kaz: final decision has to be brought to main call next year 15:16:59 s/year/week/ 15:17:29 ege: note that we need just two URI 15:17:38 ... one for tm schem and one for td schema 15:19:07 -> https://www.w3.org/TR/2023/PR-wot-thing-description11-20230711/#namespaces WoT Thing Description 1.1 Proposed Recommendation - 4. Namespaces 15:19:50 kaz: there are two points here: how to handle the URIs and the concrete mapping. 15:22:07 proposal: "We agree to use URIs with date for TD 1.1 and 1.0. For TD 2.0 we will reevaluate and possibly change to using /ns approach" 15:23:25 resolution: "We agree to use URIs with date for TD 1.1 and 1.0. For TD 2.0 we will reevaluate and possibly change to using /ns approach" 15:23:54 ege: we can brainstorm right now 15:23:59 ... and continue async 15:24:02 rrsagent, please draft the minutes 15:24:03 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html JKRhb 15:24:41 rrsagent, draft minutes 15:24:42 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html JKRhb 15:24:47 q+ 15:25:34 ack k 15:26:14 ack c 15:26:19 q? 15:26:24 q+ 15:28:20 kaz: we need to add several lines (one for each new uri) to the specification as well? 15:28:24 ege: yes that is correct 15:29:07 ... but is only in appendix B 15:29:22 ... is changing and existing link 15:29:44 q+ 15:30:14 sebastian_ has joined #wot-td 15:30:18 kaz: from our view point it is a minor change, but for the w3c is a big change 15:30:28 ... I need to talk with PL 15:31:21 s/I need to talk with PL/I'm afraid I still need to talk with PLH about this./ 15:32:00 kaz: before that, please clarify the concrete URIs from www.w3.org to be mapped to some URLs from github.com 15:32:11 i/before/scribenick: kaz/ 15:32:54 cris: we need to update the $id field too, but we already tagged the file. How can we correctly link it? 15:33:06 ege: right that is an issue, I'll think about it. 15:33:52 topic: final agenda items 15:34:04 ege: planning discussion is moved in the planning meeting 15:34:07 mk: I agree 15:34:15 ... we have the workitems 15:34:24 ... we just need to be sure to capture all of them 15:34:47 ... for today I was planning to go through usecase and requirement togheters 15:34:51 ege: any other points? 15:35:05 ... ok, we can close the meeting 15:35:51 [adjourned] 15:37:14 rrsagent, draft minutes 15:37:15 I have made the request to generate https://www.w3.org/2023/07/19-wot-td-minutes.html kaz 17:56:01 Zakim has left #wot-td