13:56:44 RRSAgent has joined #wot-td 13:56:48 logging to https://www.w3.org/2024/01/18-wot-td-irc 13:59:20 dape has joined #wot-td 13:59:26 meeting: WoT-WG - TD-TF - Slot 2 14:00:42 present+ Kaz_Ashimura, Jan_Romann 14:01:26 present+ Daniel_Peintner, Ege_Korkan 14:01:55 ktoumura has joined #wot-td 14:02:28 regrets+ Koster 14:03:25 Mizushima has joined #wot-td 14:04:10 present+ Kunihiko_Toumura 14:04:18 chair: Ege 14:05:29 cris_ has joined #wot-td 14:05:37 Ege has joined #wot-td 14:05:50 present+ Cristiano_Aguzzi, Tomoaki_Mizushima 14:06:02 scribe: dape 14:06:22 JKRhb has joined #wot-td 14:06:40 TOPIC: Minutes of last week 14:06:52 -> Thursday -> https://www.w3.org/2024/01/11-wot-td-minutes.html 14:07:23 EK: Any concern? 14:07:42 rrsagent, make log public 14:07:49 ... -> none -> minutes are approved 14:07:51 rrsagent, draft minutes 14:07:53 I have made the request to generate https://www.w3.org/2024/01/18-wot-td-minutes.html kaz 14:08:02 TOPIC: Binding Templates 14:08:22 SUBTOPIC: PR 346 14:08:37 -> https://github.com/w3c/wot-binding-templates/pull/346 14:08:50 EK: Decided to merge asynchronously 14:08:56 s/346/346 PR 346 - [Modbus] type fixes/ 14:08:59 rrsagent, draft minutes 14:09:00 I have made the request to generate https://www.w3.org/2024/01/18-wot-td-minutes.html kaz 14:09:09 SUBTOPIC: Registry Analysis 14:09:20 CA: PR 1161 not done yet 14:09:28 -> https://github.com/w3c/wot/pull/1161 14:09:44 CA: Proceeded further with different mechanism 14:10:09 ... added description for "first come first serve" 14:10:13 s/1161/1161 wot PR 1161 - docs: IANA procedures for registries summary/ 14:10:15 rrsagent, draft minutes 14:10:17 I have made the request to generate https://www.w3.org/2024/01/18-wot-td-minutes.html kaz 14:10:25 ... added also "Expert Review" 14:10:37 ... do next: report rules for URI Schemes 14:10:55 EK: Extend the generic policy? 14:11:08 CA: Yes, but not much.. 14:11:38 ... e.g., lower-case / upper case sensitiveness 14:11:46 ... usually additional constraints 14:12:41 present+ Mahda_Noura 14:13:09 EK: Expert Review is going to be important for us 14:13:31 CA: There is a dedicated section how to choose the "expert" 14:14:47 ... a lot of information to digest.. takes a bit of time 14:15:08 EK: Let's look at it next time again 14:15:29 ... another aspect is whether we should start writing our requirements 14:15:34 ... I think we can start 14:15:41 ... and extend later what we learn 14:15:43 q+ 14:15:48 CA: I think it is good to start 14:15:54 ... like a TOC 14:16:01 ... I have some ideas 14:16:04 q+ 14:16:10 ack c 14:16:10 ack cris_ 14:16:57 JR: Should we define use-cases as well where we can get requirements 14:17:26 EK: Need a solution for a use-case/requirement 14:17:35 ... maybe that is a good idea 14:19:01 ack jk 14:19:08 rrsagent, draft minutes 14:19:09 I have made the request to generate https://www.w3.org/2024/01/18-wot-td-minutes.html kaz 14:19:48 mahda-noura has joined #wot-td 14:20:46 EK: We can add story-line about registry (in registry-analysis/Readme.md) 14:20:50 present+ Mahda_Noura 14:21:46 q+ 14:21:52 ... a la "WoT to support multiple protocols" ...made interoperable with a descriptive approach 14:22:11 Kaz: Updated text might be also useful 14:22:27 ... however, can use text from charter as well 14:22:54 EK: Good point. I might have written some text for that 14:23:53 -> https://www.w3.org/2023/10/wot-wg-2023.html WoT WG Charter 14:25:34 EK: Maybe parts from Section 2 in charter document 14:25:49 ... will do some homework later 14:26:10 ack k 14:27:14 ... started PR 1169 14:27:34 ... please comment 14:28:04 SUBTOPIC: Reviews of the individual bindings 14:28:31 EK: related to DataMapping from yesterdays TD call 14:28:41 i|please|-> https://github.com/w3c/wot/pull/1169 wot PR 1169 - Use Case and Story for Registries| 14:28:44 rrsagent, draft minutes 14:28:45 I have made the request to generate https://www.w3.org/2024/01/18-wot-td-minutes.html kaz 14:29:00 EK: Interesting part: Missing protocol mechanisms 14:29:20 q+ 14:29:23 ... e.g., we cannot describe a given mechanism in a TD 14:29:50 ... people can also ask for help how to solve that in TD 14:30:14 CA: e.g., MQTT pattern 14:30:45 ... pretending we can describe it in a TD but we do not describe it 14:30:57 EK: Is lack of documentation, not a new use case 14:31:15 CA: Like the idea to ask experts for ideas 14:32:02 EK: for example HiveMQ feedback 14:32:19 ... with CoAP Klaus Hartke and Jan 14:32:42 JR: I would know some more people 14:34:44 EK: w.r.t. HTTP, people of WG are quite knowledgeable 14:34:54 ... WebSocket needs people 14:34:58 ... SSE needs people 14:35:18 ... w.r.t. Modbus we got a lot of input already 14:35:46 ... BACnet, quite recent, needs more time 14:36:31 TOPIC: Management 14:36:45 SUBTOPIC: Project Management Proposal: 14:37:01 -> https://github.com/w3c/wot-thing-description/pull/1954 14:37:53 EK: Last week we extended it in coordination call 14:38:09 s/1954/1954 wot-thing-description PR 1954 - Extending the project management proposal/ 14:38:19 ... issue coming from use case pipeline 14:38:34 i|1954|-> https://github.com/w3c/wot-thing-description/blob/main/proposals/project-management/project-management.md project-management.md| 14:38:36 rrsagent, draft minutes 14:38:38 I have made the request to generate https://www.w3.org/2024/01/18-wot-td-minutes.html kaz 14:38:45 ... TF working on planning the work 14:38:50 ... separation of concerns 14:39:09 q+ 14:39:11 EK: Any points or objections to merge this PR? 14:39:16 ack c 14:39:17 ack c 14:39:33 Kaz: Any update like this is fine. 14:40:07 ... we should think about which part is managed by use-case and Mizushima-San 14:40:20 EK: Good point. Should be in line 14:40:48 ... we might want to align the "naming" 14:41:10 ... "gap analysis" is missing in my document 14:41:48 ... I will link Process.md from wot-usecases 14:42:20 EK: Can I merge 1954 ? 14:42:20 +1 14:42:31 ... no objections -> merging 14:42:43 TOPIC: TD 14:42:54 SUBTOPIC: Data Mapping 14:43:02 -> https://github.com/w3c/wot/pull/1165 14:43:14 EK: Luca extended the PR 14:44:14 ... I added related issues and added them to the PR 14:44:31 ... others can do the same.. also from other task forces 14:45:02 SUBTOPIC: Formatting before starting work 14:45:09 -> https://github.com/w3c/wot-thing-description/issues/1926 14:45:19 EK: Consistent way of working 14:45:55 ... looked how prettier and editorconfig work together 14:46:09 ... unfortunately we need to use both 14:46:29 ... should keep them consistent 14:46:44 s/1165/1165 wot PR 1165 - Initial expansion of the DataMapping work item/ 14:47:24 EK: I don't think we should format output files which are generated 14:47:29 s/1926/1926 wot-thing-description Issue 1926 - Aligning formatting across files/ 14:47:30 q+ 14:48:43 EK: picked option "space" and "2 spaces" for indentation 14:49:08 ack k 14:49:22 EK: In the end I can format all files in one go 14:49:34 ... leads to a HUGE diff 14:50:23 ... e.g. removing trailing whitespaces 14:50:31 q+ 14:50:45 ... any concern or preferences on settings used 14:51:05 CA: Style is okay.. no strong preference 14:52:03 ... don't get some changes.. like line breaks 14:52:15 DP: I think there is a 80 character limit 14:52:51 EK: "printWidth" might be the option 14:53:04 ... default like 80 14:53:08 CA: Should go with 120 14:54:41 EK: BTW I excluded "publication" folder 14:55:13 rrsagent, draft minutes 14:55:15 I have made the request to generate https://www.w3.org/2024/01/18-wot-td-minutes.html dape 14:55:46 q+ 14:55:51 ack c 14:55:52 EK: Any other business? 14:55:52 ack c 14:56:33 [adjourned] 14:56:37 ack k 14:56:43 rrsagent, draft minutes 14:56:44 I have made the request to generate https://www.w3.org/2024/01/18-wot-td-minutes.html kaz