14:01:35 RRSAgent has joined #wot-td 14:01:39 logging to https://www.w3.org/2023/05/24-wot-td-irc 14:01:50 present+ Kaz_Ashimura, Ege_Korkan, Luca_Barbato 14:07:30 present+ Michael_Koster 14:07:44 McCool_ has joined #wot-td 14:07:54 (lurking for now, will join call in an hour) 14:08:27 mjk_ has joined #wot-td 14:08:40 scribenick: mjk_ 14:09:02 scribenick: kaz 14:10:11 chair: Ege/Koster 14:10:24 present+ Cristiano_Aguzzi 14:10:37 topic: Minutes 14:11:09 -> https://www.w3.org/2023/05/17-wot-td-minutes.html May-17 14:14:42 present+ Tomoaki_Mizushima 14:16:14 topic: TPAC 14:16:25 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda TPAC wiki 14:16:49 ek: any changes about the attendance? 14:17:07 ca: not sure yet 14:17:20 ... so pleas add me to "not Clear" 14:17:30 lb: same here 14:17:44 ek: (adds Cristiano and Luca to "not Clear") 14:18:04 ... what about you Koster? 14:18:06 sebastian has joined #wot-td 14:18:10 mjk: remote 14:18:43 ek: topics for TD? 14:19:03 ... at least JSON-LD collab 14:19:15 present+ Sebastian_Kaebisch 14:19:31 lb: might want to talk about data mapping in general 14:19:39 ... how to use data schema, etc. 14:19:50 q+ 14:20:25 mjk: RDF applications and design pattern in general 14:20:37 ... sort of related to data mapping 14:21:01 ... could be handled by RDF or maybe by JSON 14:21:08 ... what is the pattern for that purpose? 14:21:25 cris__ has joined #wot-td 14:21:28 ek: think what Luca means is rather payload level 14:21:34 q+ 14:22:29 ack k 14:23:36 kaz: "data mapping in general" is a bit vague 14:23:45 ... could you elaborate it a bit more? 14:24:06 ... what king of data withing TD or Binding Template to be mapped to what? 14:24:34 lb: supporting JSON-LD without full JSON-LD processing 14:24:43 ... also how to use data schema 14:24:56 q+ 14:25:30 ... in my use case of labeling some device 14:26:00 ... how to use the data schema in a clearer manner 14:26:25 ack k 14:26:36 kaz: ok 14:26:48 ... would be helpful if you could describe that based on a concrete use case scenario 14:26:56 ... when we discuss the topic (not now :) 14:27:06 lb: ok, will prepare something for that purpose 14:27:12 q? 14:27:38 ek: Koster, do you want to talk about TD in RDF? 14:28:44 mjk: semantic annotation to have richer information 14:28:54 ... all the information to be integrated 14:29:04 ... maybe need to elaborate the idea a bit more 14:29:06 q? 14:29:07 q+ 14:29:19 q+ 14:29:31 ca: basically would support those points 14:29:49 ... also validaton of different ontology models 14:29:57 ... how to work with Things 14:30:53 ... btw, are we starting with brainstorming there during TPAC? 14:30:55 ek: yeah 14:31:07 q+ 14:31:08 ca: how long? 14:31:11 ack c 14:31:23 ek: would have topics first 14:31:38 ca: maybe less than two hours? 14:31:42 ek: need to check 14:34:08 kaz: please think about concrete use cases 14:34:27 ... and if possibly try some broader example like smart cities, smart building, etc. 14:35:00 ... also please remember McCool mentioned we could have a preleminary or followup meeting before or after TPAC 14:35:01 ack k 14:35:02 ack m 14:35:25 mizu: we should build consensus about what to be described by TD spec 14:35:37 kaz: you mean refactoring of the spec? 14:35:40 mizu: yes 14:36:02 ... the expected spec will be Ver. 2.0 14:36:06 ... so it's a major version up 14:36:14 present+ Jan_Romann 14:36:29 ... therefore we should make consensus about what to do there 14:36:34 q? 14:36:38 ek: right 14:37:08 ... explaining the major version udpate 14:37:10 q? 14:37:19 ... including major refactoring 14:37:21 ack s 14:37:41 sk: be aware TPAC will be held in September 14:38:23 ... on the other hand, many of the topics here are relevant for the upcoming months too 14:38:25 q? 14:38:27 q+ 14:39:10 ek: yeah 14:39:28 ... we don't need to wait 14:40:25 kaz: as McCool mentioned during the main call, we're planning to have a dedicated meeting in June 14:40:37 ... to think about what to do in the next Charter period 14:40:45 ... so we can talk about some of these topics there 14:41:08 ek: you can add further update to the wiki 14:41:20 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda TPAC wiki 14:41:29 ek: please put your name when you add edits 14:42:02 topic: Binding Templates 14:42:17 subtopic: PR 290 14:42:42 -> https://github.com/w3c/wot-binding-templates/pull/290 wot-binding-templates PR 290 - Publication Prep 14:42:57 ek: Kaz let us know about the basic procedure for publication 14:43:18 https://deploy-preview-290--wot-binding-templates.netlify.app/publication/note3/overview 14:43:27 ... put the information to README.md under wot-binding-templates 14:43:44 ... checking the document using the Pubrules checker 14:44:11 ... wondering how to change the document status 14:44:12 q+ 14:45:03 ack k 14:45:35 kaz: you can specify the document type using the ReSpec parameter 14:45:47 ... you can look at the ReSpec page to see the detail 14:46:16 ek: ok 14:46:41 -> https://respec.org/docs/ ReSpec documentation 14:48:35 ek: seems HTML Tidy doesn't work properly 14:49:04 kaz: please try "tidy -i -m Overview.html" 14:49:38 ... note that if there is some fatal/difficult error, Tidy gives up to fix the HTML 14:50:03 ... there is a Tidy documentation, also you can simply use "tidy --help" 14:50:36 -> https://www.html-tidy.org HTML Tidy documentation 14:51:49 kaz: I myself usually use a Makefile for that purpose, and can share that file with you 14:53:46 ek: t 14:53:51 s/: t/: tx/ 14:55:30 -> https://www.w3.org/Guide /Guide 14:56:59 kaz: once you've confirmed the HTML is OK with the Pubrules checker, Validator, Link Checker, etc., I can double check it and work on the publication 14:57:20 ek: how to get the information on the Validator and the Link Checker? 14:57:38 kaz: there are links from the Pubrules checker results 14:57:53 ... please see also the /Guide page above 14:57:57 ek: ok 14:58:04 ... will work on the checker again 14:58:59 scribenick: mjk_ 14:58:59 topic: Thing Description 14:58:59 topic: TD 14:58:59 s/topic: Thing Description// 14:59:12 present+ Michael_McCool 14:59:16 q? 14:59:40 subtopic: Issue 1831 14:59:54 subtopic: issue #1831 15:00:04 -> https://github.com/w3c/wot-thing-description/issues/1831 wot-thing-description Issue 1831 - Problem with Respec 15:00:09 s/subtopic: Issue 1831// 15:00:10 ege: close 15:00:21 ege: PRs 15:00:33 subtopic: PR #1826 15:01:23 mm: internal immutable identifier 15:01:37 i|inter|-> https://github.com/w3c/wot-thing-description/pull/1826 wot-thing-description PR 1826 - Resolve privacy-immutable-id-as-property| 15:01:43 rrsagent, make log public 15:01:46 rrsagent, draft miutes 15:01:46 I'm logging. I don't understand 'draft miutes', kaz. Try /msg RRSAgent help 15:02:00 ... didn't get implementations, removed assertion and changed language to should (lower case) 15:02:01 q? 15:02:14 ege: any objections to merge? 15:02:45 ... merged 15:03:04 subtopic: PR #1827 15:03:25 ege: try https first for remote links 15:03:47 ... also removed assertion and changed language to should 15:04:00 i|try|-> https://github.com/w3c/wot-thing-description/pull/1827 wot-thing-description PR 1827 - Resolve security-context-secure-fetch| 15:04:01 ... any objections to merging? 15:04:51 mm: maybe belongs as part of RDF framework 15:05:09 ... merged 15:05:24 subtopic: PR #1828 15:05:41 ege: remove device flow from Oauth 15:06:48 mm: removes the RFC reference 15:07:09 ... only client and code flows are left 15:07:37 ... also removed a reference to the device flow in the discovery spec 15:07:42 ... any objections to merge? 15:08:00 s/.../ege: 15:08:17 ege: merged 15:08:42 mm: will regenerate the implementation report, any other changes? 15:08:59 ege: changed editors notes (PR #1811) 15:09:19 mm: change the document first, then will update the report 15:09:35 subtopic: PR #1811\ 15:09:53 s/1811\/1811 15:10:06 ege: changed editors notes to notes 15:10:28 mm: fixing some grammatical errors 15:12:15 jr: is this paragraph still a note in the document? 15:12:35 mm: it would be consistent with the previous revision to keep it as a note 15:13:03 Instead of a periodic POST call to the Thing 15:13:09 mm: (updating the grammatical error) 15:14:00 i|remove dev|-> https://github.com/w3c/wot-thing-description/pull/1828 wot-thing-description PR 1828 - Resolve td-security-oauth2-device-flow| 15:14:44 i|changed editors n|-> https://github.com/w3c/wot-thing-description/pull/1811 wot-thing-description PR 1811 - Resolve 3 editors notes| 15:14:49 rrsagent, draft minutes 15:14:51 I have made the request to generate https://www.w3.org/2023/05/24-wot-td-minutes.html kaz 15:15:05 rrsagent, make log public 15:15:27 q? 15:16:43 ege: (edited the PR online) 15:16:50 ... any objections ? 15:17:03 ... merged 15:17:22 ... these are all the editorial PRs 15:17:43 subtopic: PR #1830 15:17:54 Implementation Report update 15:18:02 mm: will update now 15:18:06 meeting: WoT-WG - TD-TF 15:18:08 rrsagent, make log public 15:18:10 rrsagent, draft minutes 15:18:11 I have made the request to generate https://www.w3.org/2023/05/24-wot-td-minutes.html kaz 15:18:34 ege: should remove the "at-risk" list 15:18:45 mm: will clean up before publication 15:19:31 i|Implementation Rep|-> https://github.com/w3c/wot-thing-description/pull/1830 wot-thing-description PR 1830 - WIP: Final Implementation Report update| 15:19:33 rrsagent, draft minutes 15:19:34 I have made the request to generate https://www.w3.org/2023/05/24-wot-td-minutes.html kaz 15:20:43 mm: updated and pushed 15:21:37 ege: (display the rendered file) 15:21:46 mm: still some cleanup to do 15:22:04 ... all at-risk items should be gone 15:23:27 mm: name to interim implementation report 15:23:38 ege: any objections to merge? 15:23:42 ... merged 15:24:11 mm: will send an email when ready, please review and check for any more changes needed 15:24:35 ege: done with the agenda 15:25:14 subtopic: PR #1807 TM namespace not active yet 15:25:35 mm: some other ontology files are also not active 15:26:00 ... the reference needs to change from 2019 to 2022 vesion 15:26:09 mm: will anything break? 15:26:48 ege: no, it could fail validation 15:27:05 s/no, // 15:27:07 q+ 15:27:45 kaz: we need the specific from and to URLs 15:28:04 ... for the mapping 15:28:54 ... it would be easier to create a subdirectory under the main directory 15:29:14 ege: don't see a tm context 15:29:43 kaz: otherwise a level of approval is needed 15:30:22 s/needed/needed for each revision/ 15:30:55 ege: we are done, any other business? 15:31:12 -> https://www.w3.org/2005/07/13-nsuri Namespace allocation guide 15:31:32 rrsagent, draft minutes 15:31:33 I have made the request to generate https://www.w3.org/2023/05/24-wot-td-minutes.html kaz 15:31:49 ege: thank you, adjourned 15:32:19 kaz you have finished the meeting 15:32:48 i|some other ont|-> https://github.com/w3c/wot-thing-description/issues/1807 wot-thing-description Issue 1807 - TM namespace not active yet| 15:33:22 no I wanted to talk regarding the coordination 15:33:35 together with Michael Koster 15:33:50 Michael are you still around? 15:37:18 rrsagent, draft minutes 15:37:19 I have made the request to generate https://www.w3.org/2023/05/24-wot-td-minutes.html kaz