14:59:02 <RRSAgent> RRSAgent has joined #wot-td
14:59:06 <RRSAgent> logging to https://www.w3.org/2024/01/17-wot-td-irc
15:06:29 <dape> dape has joined #wot-td
15:08:44 <kaz> meeting: WoT-WG - TD-TF - Slot 1
15:08:55 <Ege> Ege has joined #wot-td
15:08:55 <mahda-noura> present+ Mahda_Noura
15:09:11 <kaz> present+ Kaz_Ashimura, Michael_Koster, Ege_Korkan, Daniel_Peintner, Kunihiko_Toumura, Luca_Barbato
15:09:18 <kaz> chair: Koster, Ege
15:09:25 <kaz> rrsagent, make log public
15:09:29 <kaz> rrsagent, draft minutes
15:09:30 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:09:49 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#January_17_and_18.2C_2024
15:09:53 <kaz> scribenick: Ege
15:10:10 <Ege> topic: Agenda
15:10:13 <Ege> q+
15:10:29 <kaz> present+ Tomoaki_Mizushima
15:10:52 <Ege> mk: any changes or feedback to the agenda?
15:11:43 <Ege> ek: one agenda per week from now on
15:11:49 <kaz> ack e
15:11:54 <Ege> mk: also we will review minutes accordingly
15:12:35 <Ege> ... wednesday of last week on wednesday of this week etc.
15:12:42 <Ege> topic: Minutes Review
15:13:17 <kaz> -> https://www.w3.org/2024/01/11-wot-td-minutes.html Jan-11
15:13:23 <Ege> kaz: I will fix the names
15:16:22 <Ege> kaz: there was a confusion with the links, now it should be fine
15:16:33 <Ege> -> https://www.w3.org/2024/01/10-wot-td-minutes.html
15:18:05 <cris_> cris_ has joined #wot-td
15:18:26 <Ege> mk: minutes are approved
15:18:41 <kaz> ss/html/html Jan-10 (which actually to be reviewed :)/
15:18:46 <kaz> rrsagent, draft minutes
15:18:47 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:18:57 <kaz> s/minutes are/Jan-10 minutes/
15:19:31 <Ege> topic: Resources
15:19:57 <kaz> q?
15:20:36 <Ege> subtopic: PR 1940
15:20:56 <kaz> s/html/html Jan-10 (which actually to be reviewed :)/
15:20:59 <kaz> rrsagent, draft minutes
15:21:00 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:21:56 <kaz> -> https://github.com/w3c/wot-thing-description/issues/1940 PR 1940 - Fixing the Ontology HTML files to static versions
15:22:12 <Ege> mk: should we review all files
15:22:23 <Ege> ek: no we have left it open for a week so that people can review
15:22:29 <JKRhb> JKRhb has joined #wot-td
15:22:36 <Ege> subtopic: PR 1933
15:23:16 <kaz> s|minuts.html|minuts.html Jan-10 (which actually to be reviewed :)|
15:23:18 <kaz> rrsagent, draft minutes
15:23:20 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:23:30 <Ege> mn: Ege has reviewed it and we have fixed some issues
15:23:43 <kaz> s|minutes.html|minutes.html Jan-10 (which actually to be reviewed :)|
15:23:59 <kaz> q+
15:24:06 <Ege> mk: it seems that quite some review went into it and this really closes a gap
15:24:18 <mjk_> mjk_ has joined #wot-td
15:24:32 <Ege> q+
15:24:43 <mahda-noura> q+
15:24:44 <kaz> ack k
15:26:35 <Ege> kaz: we should split the image and have an explanation so that a non-expert can use it
15:26:56 <Ege> ek: we cannot split the image since they are linked
15:27:07 <Ege> ... and we cannot expect a non-expert to use it
15:27:37 <ktoumura> ktoumura has joined #wot-td
15:27:44 <Ege> kaz: we need to know what is written and when
15:27:52 <Ege> ek: this is explained with the legend of the figure
15:28:16 <Ege> mn: this is correct. The legend and arrows explain it
15:29:12 <Ege> mn: I cannot provide more details, unless we explain "how to write an ontology"
15:29:31 <Ege> ek: Maybe we need to understand if kaz means a specific format
15:29:39 <Ege> mk: small arrow issue on top
15:31:19 <Ege> kaz: a short explanation like, change this ttl file and apply this script to get HTML
15:31:36 <Ege> mk: maybe what you want is a more abstract figure, not splitting into smaller files
15:31:59 <Ege> q+
15:32:02 <Ege> ack e
15:32:05 <Ege> ack m
15:32:07 <Ege> q+
15:32:40 <Mizushima> q+
15:32:48 <kaz> ack e
15:33:56 <kaz> rrsagent, draft minutes
15:33:57 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:34:03 <Ege> tm: what kind of IoT network is used and how are the TDs generated?
15:34:19 <Ege> mn: this is the tool for the specification. we do not manually edit the index.html
15:34:22 <Ege> q+
15:34:51 <Ege> ack m
15:34:52 <Ege> ack e
15:35:14 <kaz> i|Ege has revi|-> https://github.com/w3c/wot-thing-description/pull/1933 PR 1933 - toolchain description update|
15:35:15 <kaz> q+
15:36:12 <mjk_> q?
15:36:25 <kaz> ack k
15:36:51 <Ege> kaz: maybe you use one big script but there are modules right? they can be explained separately
15:36:52 <Ege> q+
15:37:41 <Ege> mk: Will it be similar for someone creating a binding?
15:37:50 <kaz> s/separately/separately. that kind of high-level description would be useful for maintenance purposes, specifically in case the original author lefts the WoT WG./
15:38:23 <kaz> ack e
15:38:34 <cris_> q+
15:39:06 <Ege> mn: it is similar
15:39:09 <kaz> rrsagent, draft minutes
15:39:10 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:39:17 <Ege> ek: yes, some steps are not needed
15:39:32 <Ege> ca: about 80% similar I would say
15:39:54 <kaz> i|Ege has rev|-> https://github.com/w3c/wot-thing-description/blob/3fea9d6570d662ca0f78759ddb28e70919fd86c5/toolchain/wot-toolchain-bpmn.png big picture of the tool chain|
15:39:57 <kaz> rrsagent, draft minutes
15:39:58 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:40:16 <JKRhb> q+
15:40:46 <Ege> ack c
15:40:52 <Ege> mk: we can merge right
15:40:58 <Ege> ek: yes
15:41:22 <Ege> jr: I did a similar thing for discovery. I think we can write a more generic tooling
15:41:22 <JKRhb> ack J
15:41:40 <Ege> mk: really good point
15:41:57 <kaz> ack cri
15:42:04 <kaz> rrsagent, draft minutes
15:42:06 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:43:30 <kaz> topic: TD
15:43:38 <kaz> subtopic: PR 1945
15:43:59 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1945 PR 1945 - Assertion id alignment
15:44:37 <kaz> q+
15:46:27 <kaz> ack k
15:46:36 <Ege> kaz: we should make this a policy
15:46:44 <Ege> ek: I can provide that to the wot repository
15:46:55 <Ege> mk: yeah that way we have a set working way
15:47:12 <kaz> s/we should/OK with merging this PR 1945 itself, but we should/
15:47:17 <kaz> rrsagent, draft minutes
15:47:18 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
15:47:25 <kaz> q?
15:47:33 <kaz> subtopic: PR 1165
15:47:59 <kaz> s/PR/wot PR/
15:48:14 <kaz> -> https://github.com/w3c/wot/pull/1165 wot PR 1165 - Initial expansion of the DataMapping work item
15:48:26 <Ege> mk: Luca, could you explain
15:48:39 <Ege> lb: I have expanded the description based on the description from last week
15:48:43 <kaz> s/explain/explain?/
15:49:57 <Ege> lb: we can extend this into a use case
15:50:57 <Ege> ... but we had talk about it already last year
15:51:55 <cris_> q+
15:52:07 <Ege> mk: we have a small discussion
15:52:11 <kaz> q+
15:52:34 <Ege> ek: we discussed yesterday. For me it is clear but I am not sure if it is for everyone
15:53:32 <Ege> lb: there is a proposal to rename it
15:53:37 <Ege> mk: maybe out of band
15:53:42 <Ege> lb: actually it is inband
15:53:50 <Ege> mk: or data that is not consumed by application?
15:54:03 <Ege> lb: actually it is consumed
15:54:12 <Ege> lb: (explains the examples)
15:54:14 <Ege> q+
15:55:28 <Ege> mk: ok I get it now
15:57:40 <mjk_> q?
15:57:44 <cris_> ack c
15:57:47 <Ege> ca: luca confirmed but basically I wanted to ask whether we also consider complex payloads
15:58:16 <kaz> ack e
15:58:22 <Ege> q+
16:00:10 <Ege> kaz: we should sync with the use cases task force
16:00:15 <kaz> ack k
16:00:40 <Ege> ... and use the new template
16:01:02 <Ege> mk: I agree
16:01:39 <kaz> s/we should sync with the use cases task force/this discussion is a good starting point, but we should sync with the use cases task force. for example, once the updated use case template is published by the Use Cases TF, we (as the TD TF) should clarify this idea based on that updated template./
16:02:13 <kaz> q?
16:03:25 <kaz> q+ luca_barbato
16:04:37 <Ege> ek: we need to be able to convey such technical information in the new use case template
16:04:51 <Ege> ... but we already have the requirements sort of ready
16:05:43 <Ege> ... maybe we should say that (sadly) td can express one channel and we need to express more
16:05:48 <Ege> lb: except uri variables
16:05:58 <kaz> rrsagent, draft minutes
16:05:59 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
16:06:06 <Ege> ... I will work on it this week but I will need help
16:06:06 <kaz> rrsagent, draft minutes
16:06:08 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
16:06:14 <Ege> mk: any other points?
16:06:14 <Ege> ... adjurned
16:06:14 <kaz> rrsagent, draft minutes
16:06:15 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/17-wot-td-minutes.html kaz
19:00:45 <Zakim> Zakim has left #wot-td