14:24:58 RRSAgent has joined #wot-td 14:25:02 logging to https://www.w3.org/2023/08/23-wot-td-irc 14:25:28 present+ Kaz_Ashimura, Ege_Korkan, Michael_McCool, Jan_Romann, Luca_Barbato 14:25:37 McCool has joined #wot-td 14:26:27 chair: Ege 14:27:11 scribenick: kaz 14:27:18 topic: Today's call 14:27:30 q+ 14:27:38 kaz: some of the WG participants are not aware there would be a TD call today 14:28:01 ... so I'd suggest we have a casual chat about urgent issues but not make actual decision today 14:28:10 ack l 14:28:27 mm: agree 14:28:47 topic: Schedule 14:29:21 ek: August 30 call will be cancelled 14:29:35 ... but September 6 call will be held 14:30:32 s/held/held if Sebastian or Koster can chair it (Ege will not be available)./ 14:31:04 topic: Use case handling procedure 14:31:18 ek: wondering about the procedure for use case handling 14:32:56 q+ 14:33:11 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda#Thing_Description_Final_Topics TD topics for TPAC 14:33:32 ek: a list of topics on TD has been generated for TPAC discussion 14:33:41 q+ 14:34:15 s/topic: Use case handling procedure/topic: TPAC discussion/ 14:34:49 ... including use case review and manageable actions 14:35:16 ack l 14:35:32 ek: general use case handling procedure should be discussed 14:36:00 ... on the other hand, how to deal with topics which have been already discussed, e.g., manageable actions? 14:37:59 q? 14:38:02 ack k 14:38:49 kaz: would agree with McCool, and think we should clarify use cases, environment settings and usage scenarios a bit more 14:39:29 ... for example, we need to think about combination with ECHONET-based systems for smart homes and OPC UA-based systems for smart factories 14:39:52 ... and should clarify the relationship with those mechanisms too when we think about use cases for advanced features 14:40:08 mm: yeah, smart cities also should be considered 14:40:29 q+ 14:41:27 ack k 14:41:54 kaz: note that we still can have some initial chat about proposed use cases and features as brainstorming 14:42:36 ... but we need to think about how to handle the use case discussion as a whole followed by requirements extraction and gap analysis 14:42:52 topic: Clarification on existing PRs 14:43:49 subtopic: PR 1877 14:44:11 -> https://github.com/w3c/wot-thing-description/pull/1877 PR 1877 - Remove editor's notes and convert one to normal note 14:44:53 ek: would like to change "ednote" to "note" 14:45:03 mm: that's totally editorial and fine 14:45:28 q+ 14:46:16 kaz: note that the PR removes some of the contents too 14:47:03 ... thought some of them were kind of informative and helpful 14:47:13 mm: the first one is informative 14:47:25 ... but the others are just notes for ourselves 14:49:19 kaz: so would like to keep only "Other Injection Risks" 14:49:57 mm: right 14:50:10 ... but a bit concerned about JSON TM 14:50:57 ek: let me check again 14:51:04 ck k 14:51:05 https://www.iana.org/assignments/media-types/media-types.xhtml 14:51:11 s/ck k/ 14:51:13 ack k 14:51:27 s|https|-> https| 14:51:30 https://www.iana.org/assignments/media-types/application/td+json 14:51:37 s/xhtml/xhtml IANA registration/ 14:51:58 ek: "td+json" is registered 14:53:41 kaz: if we still have problem with TM, we should keep the note after changing it from "ednote" to "note" 14:57:22 ek: (updates the content of the note) 14:59:09 i/mm: should say "Please look at the current IANA registration; in the future .td.json and .td.jsonld may also be allowed./ 14:59:43 -> https://github.com/w3c/wot-thing-description/pull/1877/files PR 1877 has been updated 15:00:49 ek: would like to send an email to the whole group about this change 15:01:37 subtopic: PR 1861 15:02:02 -> https://github.com/w3c/wot-thing-description/pull/1861 PR 1861 - Desired namespaces for 1.0 and 1.1 resources 15:02:54 -> https://github.com/w3c/wot-thing-description/blob/main/NAMESPACES.md NAMESPACES.md 15:03:18 ek: namespaces URLs are clarified within the above "NAMESPACES.md" 15:03:56 mm: We should use the published W3C URL for that purpose 15:03:59 ek: yes 15:04:29 ... we can use redirection from W3C to GitHub so that we can maintain the content easily 15:05:10 q+ 15:11:13 ack k 15:11:13 kaz: two comments about this 15:12:45 ... 1. don't think it would be really nice to use year name like "2019" and "2022" as part of the URL, because we need to use "2024" for 2.0 version next year 15:13:31 ... 2. don't think it would be really nice to use the "wot-thing-description" repo's "publication" area for name space resources, because that area is used as a tentative area for publication preparation 15:14:32 mm: regarding #1, unfortunately, we chose to use the year name as part of the URL at some point :( 15:15:06 q? 15:15:11 ... on the other hand, regarding #2, we could use, e.g., a separate repo like "wot-resources" to manage the namespace files 15:17:28 s/subtopic: PR 1861/subtopic: PR 1861 and PR 1863/ 15:17:39 -> https://github.com/w3c/wot-thing-description/pull/1863 Add rec11 resources 15:17:55 ek: (adds comments to PR 1863 about the proposed policy) 15:18:09 ... will send an email to the WG as well 15:18:26 -> https://github.com/w3c/wot-thing-description/pull/1863#issuecomment-1690150791 updated comments 15:18:36 subtopic: PR 1864 15:19:08 -> https://github.com/w3c/wot-thing-description/pull/1864 PR 1864 - Add work-items.md to the list 15:19:28 ek: just fixing a MD 15:19:32 (merged) 15:19:39 subtopic: PR 1871 15:20:03 -> https://github.com/w3c/wot-thing-description/pull/1871 PR 1871 - Small README fixes 15:20:20 ek: fixing the README.md 15:20:44 mm: OK with merghing this 15:20:47 (merged) 15:21:50 subtopic: PR 1868 15:22:25 -> https://github.com/w3c/wot-thing-description/pull/1868 PR 1868 - Fix examples with wrong context url 15:22:31 mm: should check with the WG 15:22:37 subotpic: PR 1842 15:22:45 s/subotpic/subtopic/ 15:23:31 -> https://github.com/w3c/wot-thing-description/pull/1842 PR 1842 - Data schema clarification 15:23:41 mm: fine but to be confirmed with the WG 15:25:03 topic: How to handle the resolution 15:25:18 mm: let's send a CfC to the group 15:25:37 s/group/group for Sep 6/ 15:28:36 ek: CfC on creating a repo for namespace resources and copying the resources from wot-thing-description to the new repo 15:29:20 https://github.com/w3c/wot-thing-description/pulls?q=is%3Apr+is%3Aopen+label%3A%22Changes+to+PR+HTML%22+-label%3A%22Requires+Director+Approval%22 will be merged in 1 week 15:29:30 kaz: and another notification message on 5 remaining editorial PRs (1877, 1870,1868, 1845 and 1842) 15:29:32 mm: right 15:29:45 [adjourned] 15:29:49 rrsagent, make log public 15:29:53 rrsagent, draft minutes 15:29:54 I have made the request to generate https://www.w3.org/2023/08/23-wot-td-minutes.html kaz 17:18:46 Zakim has left #wot-td