IRC log of wot-td on 2023-08-23

Timestamps are in UTC.

14:24:58 [RRSAgent]

RRSAgent has joined #wot-td

14:25:02 [RRSAgent]

logging to https://www.w3.org/2023/08/23-wot-td-irc

14:25:28 [kaz]

present+ Kaz_Ashimura, Ege_Korkan, Michael_McCool, Jan_Romann, Luca_Barbato

14:25:37 [McCool]

McCool has joined #wot-td

14:26:27 [kaz]

chair: Ege

14:27:11 [kaz]

scribenick: kaz

14:27:18 [kaz]

topic: Today's call

14:27:30 [luca_barbato]

q+

14:27:38 [kaz]

kaz: some of the WG participants are not aware there would be a TD call today

14:28:01 [kaz]

... so I'd suggest we have a casual chat about urgent issues but not make actual decision today

14:28:10 [kaz]

ack l

14:28:27 [kaz]

mm: agree

14:28:47 [kaz]

topic: Schedule

14:29:21 [kaz]

ek: August 30 call will be cancelled

14:29:35 [kaz]

... but September 6 call will be held

14:30:32 [kaz]

s/held/held if Sebastian or Koster can chair it (Ege will not be available)./

14:31:04 [kaz]

topic: Use case handling procedure

14:31:18 [kaz]

ek: wondering about the procedure for use case handling

14:32:56 [luca_barbato]

q+

14:33:11 [kaz]

-> 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 [kaz]

ek: a list of topics on TD has been generated for TPAC discussion

14:33:41 [kaz]

q+

14:34:15 [kaz]

s/topic: Use case handling procedure/topic: TPAC discussion/

14:34:49 [kaz]

... including use case review and manageable actions

14:35:16 [kaz]

ack l

14:35:32 [kaz]

ek: general use case handling procedure should be discussed

14:36:00 [kaz]

... on the other hand, how to deal with topics which have been already discussed, e.g., manageable actions?

14:37:59 [McCool]

q?

14:38:02 [McCool]

ack k

14:38:49 [kaz]

kaz: would agree with McCool, and think we should clarify use cases, environment settings and usage scenarios a bit more

14:39:29 [kaz]

... 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 [kaz]

... and should clarify the relationship with those mechanisms too when we think about use cases for advanced features

14:40:08 [kaz]

mm: yeah, smart cities also should be considered

14:40:29 [kaz]

q+

14:41:27 [kaz]

ack k

14:41:54 [kaz]

kaz: note that we still can have some initial chat about proposed use cases and features as brainstorming

14:42:36 [kaz]

... 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 [kaz]

topic: Clarification on existing PRs

14:43:49 [kaz]

subtopic: PR 1877

14:44:11 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1877 PR 1877 - Remove editor's notes and convert one to normal note

14:44:53 [kaz]

ek: would like to change "ednote" to "note"

14:45:03 [kaz]

mm: that's totally editorial and fine

14:45:28 [kaz]

q+

14:46:16 [kaz]

kaz: note that the PR removes some of the contents too

14:47:03 [kaz]

... thought some of them were kind of informative and helpful

14:47:13 [kaz]

mm: the first one is informative

14:47:25 [kaz]

... but the others are just notes for ourselves

14:49:19 [kaz]

kaz: so would like to keep only "Other Injection Risks"

14:49:57 [kaz]

mm: right

14:50:10 [kaz]

... but a bit concerned about JSON TM

14:50:57 [kaz]

ek: let me check again

14:51:04 [kaz]

ck k

14:51:05 [Ege]

https://www.iana.org/assignments/media-types/media-types.xhtml

14:51:11 [kaz]

s/ck k/

14:51:13 [kaz]

ack k

14:51:27 [kaz]

s|https|-> https|

14:51:30 [Ege]

https://www.iana.org/assignments/media-types/application/td+json

14:51:37 [kaz]

s/xhtml/xhtml IANA registration/

14:51:58 [kaz]

ek: "td+json" is registered

14:53:41 [kaz]

kaz: if we still have problem with TM, we should keep the note after changing it from "ednote" to "note"

14:57:22 [kaz]

ek: (updates the content of the note)

14:59:09 [kaz]

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 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1877/files PR 1877 has been updated

15:00:49 [kaz]

ek: would like to send an email to the whole group about this change

15:01:37 [kaz]

subtopic: PR 1861

15:02:02 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1861 PR 1861 - Desired namespaces for 1.0 and 1.1 resources

15:02:54 [kaz]

-> https://github.com/w3c/wot-thing-description/blob/main/NAMESPACES.md NAMESPACES.md

15:03:18 [kaz]

ek: namespaces URLs are clarified within the above "NAMESPACES.md"

15:03:56 [kaz]

mm: We should use the published W3C URL for that purpose

15:03:59 [kaz]

ek: yes

15:04:29 [kaz]

... we can use redirection from W3C to GitHub so that we can maintain the content easily

15:05:10 [kaz]

q+

15:11:13 [kaz]

ack k

15:11:13 [kaz]

kaz: two comments about this

15:12:45 [kaz]

... 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 [kaz]

... 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 [kaz]

mm: regarding #1, unfortunately, we chose to use the year name as part of the URL at some point :(

15:15:06 [Ege]

q?

15:15:11 [kaz]

... 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 [kaz]

s/subtopic: PR 1861/subtopic: PR 1861 and PR 1863/

15:17:39 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1863 Add rec11 resources

15:17:55 [kaz]

ek: (adds comments to PR 1863 about the proposed policy)

15:18:09 [kaz]

... will send an email to the WG as well

15:18:26 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1863#issuecomment-1690150791 updated comments

15:18:36 [kaz]

subtopic: PR 1864

15:19:08 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1864 PR 1864 - Add work-items.md to the list

15:19:28 [kaz]

ek: just fixing a MD

15:19:32 [kaz]

(merged)

15:19:39 [kaz]

subtopic: PR 1871

15:20:03 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1871 PR 1871 - Small README fixes

15:20:20 [kaz]

ek: fixing the README.md

15:20:44 [kaz]

mm: OK with merghing this

15:20:47 [kaz]

(merged)

15:21:50 [kaz]

subtopic: PR 1868

15:22:25 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1868 PR 1868 - Fix examples with wrong context url

15:22:31 [kaz]

mm: should check with the WG

15:22:37 [kaz]

subotpic: PR 1842

15:22:45 [kaz]

s/subotpic/subtopic/

15:23:31 [kaz]

-> https://github.com/w3c/wot-thing-description/pull/1842 PR 1842 - Data schema clarification

15:23:41 [kaz]

mm: fine but to be confirmed with the WG

15:25:03 [kaz]

topic: How to handle the resolution

15:25:18 [kaz]

mm: let's send a CfC to the group

15:25:37 [kaz]

s/group/group for Sep 6/

15:28:36 [kaz]

ek: CfC on creating a repo for namespace resources and copying the resources from wot-thing-description to the new repo

15:29:20 [Ege]

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]

kaz: and another notification message on 5 remaining editorial PRs (1877, 1870,1868, 1845 and 1842)

15:29:32 [kaz]

mm: right

15:29:45 [kaz]

[adjourned]

15:29:49 [kaz]

rrsagent, make log public

15:29:53 [kaz]

rrsagent, draft minutes

15:29:54 [RRSAgent]

I have made the request to generate https://www.w3.org/2023/08/23-wot-td-minutes.html kaz

17:18:46 [Zakim]

Zakim has left #wot-td