00:22:51 <Ege> Ege has joined #wot-td
01:25:07 <Ege> Ege has joined #wot-td
01:52:54 <Ege> Ege has joined #wot-td
02:26:59 <Ege> Ege has joined #wot-td
03:01:21 <Ege> Ege has joined #wot-td
03:48:07 <Ege> Ege has joined #wot-td
04:22:15 <Ege> Ege has joined #wot-td
04:57:40 <Ege> Ege has joined #wot-td
05:34:23 <Ege> Ege has joined #wot-td
06:17:25 <Ege> Ege has joined #wot-td
06:43:17 <Ege> Ege has joined #wot-td
13:04:38 <RRSAgent> RRSAgent has joined #wot-td
13:04:38 <RRSAgent> logging to https://www.w3.org/2025/10/16-wot-td-irc
13:04:44 <Zakim> Zakim has joined #wot-td
13:04:50 <Ege> chair: Ege_Korkan, Michael_Koster
13:04:55 <Ege> Meeting: WoT Thing Description
13:05:03 <Ege> rrsagent, draft minutes
13:05:05 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/16-wot-td-minutes.html Ege
13:05:10 <Ege> rrsagent, make log public
13:05:56 <Mizushima> Mizushima has joined #wot-td
13:06:09 <Ege> Ege_Korkan, Michael_Koster, Tomoaki_Mizushima, Kunihiko_Toumura, Mahda_Noura, Luca_Barbato
13:09:07 <Ege> topic: Minutes
13:09:35 <Ege> https://www.w3.org/2025/10/09-wot-td-minutes.html
13:09:50 <Ege> ek: only major problems to be checked
13:09:55 <dape> dape has joined #wot-td
13:10:13 <Ege> ... any issues with minutes?
13:10:23 <Ege> ... hearing none, approved
13:11:08 <Ege> topic: Common Definitions
13:12:03 <Ege> s/topic: Common Definitions//
13:12:31 <Ege> topic: Binding Ontologies Alignment
13:13:58 <Ege> mh: there is misalignment on the usage of terms in different ontologies
13:14:28 <Ege> s/mh/mn
13:15:06 <Ege> ek: we can create a guideline to use in registry too
13:15:30 <dape> q+
13:15:47 <luca_barbato> +1
13:16:00 <Ege> mn: (shows the examples)
13:16:52 <Ege> mn: we can have a guideline in the top
13:17:50 <Ege> ek: what is the level of the guideline?
13:18:10 <Ege> mn: Typically it is provided as a guideline, not a standard
13:18:56 <luca_barbato> I have to go even earlier sadly, I'm all for consistency and automated lints
13:19:12 <Ege> dp: we should fix one first, like Modbus. Also consistency in a single one document would be good
13:19:20 <Ege> ... that would be the minimum
13:19:39 <dape> ack dape
13:21:03 <Ege> ek: any other misalignments?
13:22:13 <Ege> mn: like labels and comments
13:22:15 <Ege> https://github.com/w3c/wot-binding-templates/issues/448
13:22:20 <Ege> ek: I have created an issue
13:23:21 <Ege> topic: Common Definitions
13:23:37 <Ege> https://github.com/w3c/wot-thing-description/pull/2154
13:23:41 <Ege> ek: just extending examples
13:24:32 <Ege> ek: (shows screen with examples)
13:25:28 <dape> q+
13:26:05 <Ege> ... example 1 is about default content type cbor
13:26:23 <mahda> mahda has joined #wot-td
13:27:19 <mahda> present+ Mahda_Noura
13:28:48 <dape> rrsagent, draft minutes
13:28:49 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/16-wot-td-minutes.html dape
13:29:28 <dape> present+ Daniel_Peintner
13:29:31 <Ege> dp: not putting contentType should still default to JSON right?
13:29:37 <Ege> ek: not sure we removed it no?
13:29:47 <Ege> ek: (looks at the spec, it still has default)
13:29:48 <dape> present+ Tomoaki_Mizushima
13:29:59 <dape> present+ Kunihiko_Toumura
13:30:06 <Ege> ... https://github.com/w3c/wot-thing-description/pull/2081 can be analyzed
13:30:12 <dape> present+ Ege_Korkan
13:30:30 <dape> present+ Michael_Koster
13:30:34 <dape> rrsagent, draft minutes
13:30:36 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/16-wot-td-minutes.html dape
13:31:08 <Ege> mn: multi protocols mean multiple forms?
13:31:13 <Ege> ek: yes I will show it later
13:31:48 <dape> q+
13:32:27 <dape> ack dape
13:32:28 <mjk> mjk has joined #wot-td
13:34:58 <Ege> dp: can we remove href if there is only one href for all affordances like in websockets?
13:35:11 <Ege> ek: out of scope right now but can be added as an example at https://github.com/w3c/wot-thing-description/issues/2153
13:35:57 <Ege> ... for now we can leave the href empty in the form and provide that uri in the base field
13:37:37 <Ege> ek: example 2 is the same but with modbus protocol
13:37:46 <mjk> q?
13:39:11 <Ege> ek: example 3 is similar but shows overriding as well
13:39:42 <dape> q?
13:40:26 <Ege> ek: example 4 is multi ip address etc.
13:43:38 <mjk> q+
13:44:03 <Ege> ek: maybe we should have a connection with array value
13:44:06 <dape> q+
13:44:09 <mjk> ack m
13:44:24 <Ege> mk: we need a new construct for this case
13:45:39 <Ege> mn: I agree. You need to repeat
13:45:48 <Ege> ... how about doing it like security
13:46:00 <Ege> ek: yes but then the term types duplicate
13:48:52 <Ege> mn: a different direction would be to provide a TM with placeholders
13:49:02 <Ege> ... and a new TD is generated based on ipv4 or ipv6
13:49:43 <Ege> ... like initializing a class with different values
13:49:49 <Ege> ... so it is not a design problem
13:54:26 <Ege> ek: (shows the examples until 7(
13:54:35 <Ege> s/7(/7)
13:54:41 <dape> present+ Luca_Barbato
13:55:42 <Ege> lb: if we provide stacking rules, we can have a form array
13:59:10 <mahda> q+
13:59:16 <dape> ack dape
13:59:53 <Ege> rrsagent, draft minutes
13:59:54 <RRSAgent> I have made the request to generate https://www.w3.org/2025/10/16-wot-td-minutes.html Ege