00:30:58 <Ege> Ege has joined #wot-td
01:47:41 <Ege> Ege has joined #wot-td
03:02:09 <Ege> Ege has joined #wot-td
03:20:08 <Ege> Ege has joined #wot-td
04:37:55 <Ege> Ege has joined #wot-td
05:02:49 <Ege> Ege has joined #wot-td
06:21:39 <Ege> Ege has joined #wot-td
06:42:33 <Ege> Ege has joined #wot-td
07:08:36 <ktoumura> ktoumura has joined #wot-td
07:59:47 <Ege> Ege has joined #wot-td
10:49:33 <ktoumura> ktoumura has joined #wot-td
13:11:01 <RRSAgent> RRSAgent has joined #wot-td
13:11:01 <RRSAgent> logging to https://www.w3.org/2025/10/23-wot-td-irc
13:11:06 <Zakim> Zakim has joined #wot-td
13:11:16 <Ege> chair: Ege_Korkan, Michael_Koster
13:11:20 <Ege> Meeting: WoT Thing Description
13:11:24 <Ege> rrsagent, draft minutes
13:11:25 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/23-wot-td-minutes.html Ege
13:11:29 <Ege> rrsagent, make log public
13:11:44 <Ege> present+ Ege_Korkan, Michael_Koster, Cristiano_Aguzzi, Tomoaki_Mizushima, Mahda_Noura
13:12:01 <cris> scribenick cris
13:12:10 <cris> topic minutes
13:12:21 <Ege> present+ Luca_Barbato
13:12:48 <cris> ege: any problems?
13:13:00 <Ege> https://www.w3.org/2025/10/16-wot-td-minutes.html
13:13:27 <cris> cris: are the names going to be corrected?
13:13:32 <cris> ege: we don't know how to fix it
13:14:20 <cris> s/topic minutes/topic: minutes/
13:15:17 <cris> mk: we capture more stuff than the other groups
13:15:38 <cris> ege: ok, even if in tpac I got the opposite impression
13:16:18 <cris> topic: pull requests
13:16:32 <cris> subtopic: PR 2154
13:16:56 <luca_barbato> luca_barbato has joined #wot-td
13:18:01 <cris> ege: based on last week discussion we were trying to reduce the number of times where you repeat the same ip address
13:18:32 <cris> ... you can use the connection to point to different IPs in the proposal
13:19:15 <luca_barbato> q+
13:21:30 <cris> luca: we have to consider the IP address is sort of a solved problem, you can have local dns or even mDNS. On the other hand, if we have to consider to describe a Thing that can be consumed in different ways (different local or remote ips).
13:21:42 <mjk> q+
13:22:03 <cris> ... or you even with different kind protocols
13:22:20 <cris> ack lu
13:22:49 <cris> mjk: another pattern in that you can use mixed protocols in different affordances
13:22:55 <mjk> ack m
13:23:52 <Mizushima> q+
13:24:09 <cris> ege: ok yes, I've prepared an example in the PR
13:25:16 <cris> mizushima: we should pay attention on the use case of using different IPs, for example ip4 or ip6
13:26:11 <cris> q+
13:26:48 <Ege> ack m
13:29:52 <Mizushima> q+
13:30:01 <cris> cris: here we are presenting our preferred why of modelling TDs using this new mechanism, but it should always possibile doing it in the old "verbose" way, right?
13:30:02 <cris> ege: yes
13:30:31 <cris> cris: moreover I think this mechanism could help clients to chose the right form by simply checking once the connect defintions
13:30:46 <cris> ... and prefer one connection type
13:33:14 <cris> ack c
13:33:47 <cris> mizushima: The issue depends on device implementation and complicated. We should investigate more
13:35:39 <cris> ege: the whole goal of this exercise is to see the impact before going to specification
13:36:12 <cris> ... next in the PR we have an example with a TD that support multiple protocols
13:37:01 <cris> ... I don't see very often double protocol
13:37:30 <cris> ... but it happens to have a mixed between modbus and modbus+tpc
13:37:42 <cris> ... do you think all of these are different patterns?
13:37:55 <cris> cris: I agree
13:39:05 <cris> q+
13:39:26 <Mizushima> ack Mizushima
13:39:37 <cris> ack c
13:41:06 <cris> ... I think it is a reasonable design
13:42:19 <dape> dape has joined #wot-td
13:43:00 <luca_barbato> +1
13:43:03 <luca_barbato> q+
13:44:11 <cris> cris: but now choosing a form is difficult and you can't use indexing
13:44:16 <cris> luca: yes you can
13:44:22 <cris> cris: right,
13:44:25 <dape> rrsagent, draft minutes
13:44:27 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/23-wot-td-minutes.html dape
13:45:35 <cris> ... or you could chose the connection
13:46:46 <cris> luca: you can always iterate over the connections array
13:47:09 <cris> ... and also you can use the connection term per afforandace level
13:48:55 <cris> ... you can also do expansion on demand
13:49:03 <Ege> q?
13:49:56 <Ege> ack l
13:50:54 <cris> ege: finally we have the use case of defaults
13:55:05 <cris> qè
13:55:10 <cris> q+
13:59:29 <dape> q+
13:59:41 <cris> cris: I think we should review op as array if we allow that
14:00:32 <cris> dape: I noticed that we were discussing some "desired extensions" (connection as array or even form at the affordance level). We just need to be sure to not over complicate everything
14:00:43 <cris> ... it should not be too complex to generate the extended TD
14:01:46 <cris> ege: I agree, I think if we implement till example 3 we are fine.
14:02:42 <cris> ege: AOB ?
14:02:51 <cris> [adjourned]
14:03:01 <dape> rrsagent, draft minutes
14:03:02 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/23-wot-td-minutes.html dape
14:03:50 <ktoumura> present+ Kunihiko_Toumura
14:07:59 <ktoumura> i/chair:/scribenick: cris
14:08:43 <ktoumura> rrsagent, draft minutes
14:08:45 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/23-wot-td-minutes.html ktoumura
14:14:21 <ktoumura> s/scribenick cris//
14:14:49 <ktoumura> rrsagent, draft minutes
14:14:50 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/23-wot-td-minutes.html ktoumura
14:56:53 <zkis> zkis has joined #wot-td
16:30:09 <Zakim> Zakim has left #wot-td
17:03:48 <Ege> Ege has joined #wot-td
17:21:48 <Ege> Ege has joined #wot-td
17:23:23 <Ege> Ege has joined #wot-td
18:39:14 <Ege> Ege has joined #wot-td