15:03:48 <RRSAgent> RRSAgent has joined #wot-td
15:03:53 <RRSAgent> logging to https://www.w3.org/2024/01/24-wot-td-irc
15:04:07 <kaz> meeting: WoT-WG - TD-TF - Slot 1
15:04:47 <kaz> present+ Kaz_Ashimura, Ege_Korkan, Jan_Romann, Luca_Barbato
15:06:48 <ktoumura_> ktoumura_ has joined #wot-td
15:07:00 <cris_> cris_ has joined #wot-td
15:07:00 <dape> dape has joined #wot-td
15:07:38 <cris_> q+
15:08:15 <JKRhb> JKRhb has joined #wot-td
15:08:57 <mahda-noura> present+ Mahda_Noura
15:09:24 <cris_> topic: agenda
15:09:36 <cris_> cris: next time we might report issues from Scripting API
15:09:38 <cris_> ege: ok
15:09:41 <kaz> present+ Cristiano_Aguzzi, Daniel_Peintner, Kunihiko_Toumura
15:09:47 <kaz> rrsagent, make log public
15:09:51 <kaz> rrsagent, draft minutes
15:09:52 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/24-wot-td-minutes.html kaz
15:09:59 <cris_> ege: we are going to talk about versioning tomorrow, we need Mccool
15:10:09 <cris_> ... we will focus on the use case discussion
15:10:50 <cris_> topic: minutes
15:11:05 <cris_> ege: they look fine
15:11:09 <cris_> ... any other remarks?
15:11:10 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#January_24_and_25.2C_2024
15:11:21 <kaz> i|they|-> https://www.w3.org/2024/01/17-wot-td-minutes.html Jan-17|
15:11:26 <cris_> ... minutes approved
15:11:28 <kaz> rrsagent, draft minutes
15:11:29 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/24-wot-td-minutes.html kaz
15:12:22 <cris_> topic: Carry over changes
15:12:43 <cris_> ege: it's a pr that is carring over static files in to wot repo
15:12:49 <kaz> s/Carry over changes/WoT resources/
15:13:13 <cris_> ege: any point to make ?
15:13:20 <kaz> i|it's|-> https://github.com/w3c/wot-resources/pull/19 wot-resources PR 19 - Carry over changes from the TD repo|
15:13:33 <cris_> ... ok then merging
15:13:34 <kaz> q+
15:13:49 <cris_> ack c
15:13:58 <kaz> ack
15:14:02 <kaz> s/ack//
15:14:03 <kaz> ack k
15:14:20 <cris_> kaz: do the TD task force want to merge this PR today and make a report next Wensday
15:14:24 <cris_> ege: yes
15:14:43 <kaz> q+
15:15:11 <cris_> kaz: it might be nicer to merge this PR after clarifying the version policy
15:15:45 <cris_> ... I'm fine merging now, but are we all ok to merge it now and talk about version management later?
15:16:08 <cris_> ege: good point, we had a discussion reguarding versioning but it is something to apply for future changes
15:17:04 <kaz> q?
15:17:10 <kaz> ack k
15:17:16 <cris_> ege: wotsec should not be changed...
15:17:18 <kaz> chair: Ege, Koster
15:17:25 <cris_> mahda: correct
15:17:29 <cris_> ... maybe something minor
15:17:43 <cris_> ege: I can look after the call
15:17:47 <kaz> q+
15:18:24 <cris_> kaz: how to validate this kind of updates?
15:18:37 <kaz> ack k
15:18:38 <cris_> ... who is responsible? are they any guidelines to follow?
15:20:29 <kaz> present+ Michael_Koster, Tomoaki_Mizushima
15:20:29 <cris_> ege: changes on the json schema I validated in playground
15:20:34 <kaz> rrsagent, draft minutes
15:20:35 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/24-wot-td-minutes.html kaz
15:20:41 <cris_> q+
15:21:04 <kaz> q?
15:21:36 <cris_> ack
15:21:38 <cris_> ack c
15:22:15 <cris_> cris: about versioning the scripting api task force needs to publish a new tag with fixed version (e.g. 1.1.0) something. We need to collaborate on this
15:22:23 <cris_> ege: correct let me note this down
15:22:35 <kaz> ack c
15:22:50 <cris_> topic: Data mapping - PR 1165
15:22:57 <cris_> ege: we discussed last week
15:23:04 <cris_> ... I added comments
15:23:12 <cris_> ... luca do you want to discuss this?
15:23:26 <kaz> i/Data ma/topic: TD/
15:23:35 <kaz> s/topic: Data/subtopic: Data/
15:23:42 <cris_> luca: I missed your review
15:23:50 <cris_> ... everything else should be fixed
15:24:10 <kaz> i|we discussed|-> https://github.com/w3c/wot/pull/1165 wot PR 1165 - Initial expansion of the DataMapping work item|
15:24:22 <kaz> q+
15:25:07 <cris_> ege: ok for mergining
15:25:22 <cris_> ... this will be submitted as use case later on
15:25:34 <cris_> ... it is preliminary work within TD task force
15:25:35 <cris_> q?
15:25:52 <cris_> kaz: ok merging
15:26:13 <cris_> ... but how to deal with compatibility with existing binary data handling like Webassembly
15:26:19 <cris_> luca: not really related
15:26:35 <cris_> kaz: not this PR, but maybe in the next discussions
15:26:49 <cris_> ... we need to take into account how browsers deal with binary data
15:27:08 <cris_> luca: as explained in the document the content-type is dealing the data.
15:27:32 <cris_> ... but sometimes we have to handle side-channels (n.d.r. like headers)
15:27:54 <cris_> ... current solution will not impact browsers
15:28:25 <cris_> kaz: webassembly is a middleware that is capable of handling different binary data and formats in web browser
15:28:34 <cris_> ... we can take them as inspiration
15:28:50 <cris_> luca: not related, webassembly is yet another bytecode
15:29:22 <cris_> kaz: not suggesting wot need to be compatible with webassembly, I just want to look at it as a possible approach
15:29:25 <JKRhb> q+
15:29:45 <cris_> ege: there has been some progress
15:30:00 <cris_> kaz: also other WGs are working on this topic
15:30:06 <cris_> ... media group is working on it
15:30:07 <mjk> mjk has joined #wot-td
15:30:13 <cris_> q?
15:30:15 <cris_> ack k
15:30:15 <mjk> q?
15:33:28 <cris_> ege: I agree that is not really related to this PR, but I note this down as a reminder for future WoT work
15:33:51 <kaz> q?
15:34:15 <cris_> jk: we run into a problem in Discovery and scripting and we saw the need for mapping of information for http headers
15:34:24 <cris_> ... we should take this into account
15:34:39 <cris_> ege: do you have a link for that?
15:34:46 <kaz> s/jk:/jr:/
15:35:13 <luca_barbato> https://github.com/eclipse-thingweb/node-wot/issues/1221
15:35:45 <kaz> rrsagent, draft minutes
15:35:46 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/24-wot-td-minutes.html kaz
15:36:41 <cris_> ege: thank you, I propose to merge it and have a follow up discussion later
15:36:48 <cris_> ... merged
15:36:58 <cris_> subtopic: Formatting
15:37:07 <cris_> ege: I worked on this
15:37:21 <kaz> s/but how to deal with compatibility with existing binary data handling like Webassembly/but we should think about how to deal with existing binary handling mechanisms on the Web like Web Assembly and MiniApps as potential Consumers as well./
15:37:27 <kaz> rrsagent, draft minutes
15:37:28 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/24-wot-td-minutes.html kaz
15:38:06 <cris_> ege: this is applying formatting and fixed html errors automatically
15:38:14 <cris_> ... there is actually no real diff on html
15:38:22 <cris_> ... it is purely formatting
15:38:37 <kaz> s/we need to take into account how browsers deal with binary data/we need to see how the data mapping mechanism on the WoT side can work with the browser as a possible Consumer as well./
15:39:50 <cris_> ... I also wrote down the list of the changes
15:39:50 <kaz> s/we can take them as inspiration/we should see how the WoT mechanism based on this data mapping proposal would be able to work with the mechanism on the browser side, e.g., Web Assembly./
15:40:06 <cris_> ... the whole idea is that we will have fewer of this
15:40:37 <cris_> q+
15:40:41 <JKRhb> ack j
15:40:44 <JKRhb> q+
15:41:18 <kaz> s/not suggesting wot need to be compatible with webassembly, I just want to look at it as a possible approach/my point is not that WoT's data mapping mechanism to be based on Web Assembly but that we need to see WoT can work with Web browser as a possible Consumer./
15:42:14 <kaz> s/media group is working on it/not only Web Assembly but MiniApp (also Devices and Sensors, Web&Networks, etc.)/
15:42:16 <cris_> cris: do you remember putting gitattribute file?
15:42:27 <cris_> ege: no, I'll add later
15:42:38 <cris_> ... CI too
15:43:19 <cris_> jk: I like trailing commas, why did you disable them?
15:43:25 <cris_> ege: it messes with our examples
15:44:06 <cris_> ... I couldn't find a way to cleanly deal with examples without disrupting them
15:44:08 <mahda-noura> mahda-noura has joined #wot-td
15:44:11 <kaz> rrsagent, draft minutes
15:44:12 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/24-wot-td-minutes.html kaz
15:44:25 <cris_> jk: the problem is that they are javascript files
15:44:39 <cris_> ege: we need a smarter prettier
15:44:42 <dape> q+
15:44:43 <cris_> ... maybe I can skip that files
15:45:12 <Ege> ack c
15:45:14 <Ege> ack j
15:45:14 <kaz> i|worked on this|-> https://github.com/w3c/wot-thing-description/pull/1960 PR 1960 - Auto formatting|
15:45:26 <cris_> jk: it is worth look into it because commas can prevent some common issues.
15:45:39 <luca_barbato> q+
15:46:15 <cris_> dape: I see Jan's point, but having serveral of different prietter config files it is not ideal
15:46:18 <cris_> ... we can discuss later
15:46:25 <cris_> ... we should keep clean and simple
15:46:32 <dape> ack dape
15:46:51 <cris_> luca: I don't know biome is able to perform better here
15:46:53 <kaz> s/jk:/jr:/
15:46:56 <luca_barbato> https://biomejs.dev/
15:46:58 <cris_> ... it is suppose to be nicer
15:47:01 <kaz> s/jk:/jr:/g
15:47:10 <kaz> rrsagent, draft minutes
15:47:12 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/24-wot-td-minutes.html kaz
15:47:31 <cris_> ... it is also faster
15:47:42 <cris_> ege: I'll check it in a separate PR
15:47:51 <kaz> s/to be based on/to be implemented based on/
15:47:52 <cris_> q+
15:48:52 <cris_> ack lu
15:49:21 <cris_> cris: watch out that if you merge it and then try biome we might get another big diff
15:49:39 <cris_> ege: got it, I prefer to do it quickly to avoid conflicts with other PRs
15:50:17 <cris_> ... instead of duplicating prettier files we can add prittier ignore comments
15:51:48 <cris_> jk: we can do this another time
15:52:31 <cris_> q?
15:52:32 <cris_> ack c
15:53:09 <cris_> topic: use cases
15:53:24 <cris_> ege: I cleaned up the text in the wiki
15:53:35 <cris_> ... I moved it as an issue to use cases repository
15:54:30 <cris_> ... the question is what do we want to do for UC ?
15:54:40 <cris_> ... we can look into issues for use cases
15:54:49 <cris_> ... I used a label
15:54:58 <cris_> ... Needs Use Case
15:55:19 <cris_> ... we can change it if needed
15:55:36 <kaz> q+
15:55:40 <cris_> ... my proposal is to go through issues and label them accordingly
15:55:59 <cris_> q+
15:56:19 <cris_> kaz: this organization is very important
15:56:22 <kaz> ack k
15:57:12 <kaz> s/this organization is very important/this kind of clarification on "TF collaboration vs separation of tasks" is very important./
15:57:18 <cris_> cris: suggest to assign ranges of issues to people. to split workload
15:57:44 <kaz> q+
15:57:47 <cris_> ack c
15:57:56 <cris_> ege: ok we can split in 10 people
15:58:25 <cris_> ... we can try to assign pages to people
16:00:04 <cris_> q?
16:01:10 <mahda-noura> +1
16:01:29 <cris_> kaz: we don't need to work on all the issues
16:01:32 <mjk> q?
16:01:40 <cris_> ... we can identify which one are important
16:02:12 <cris_> ... we can group for feature importance
16:02:34 <cris_> ege: good ponts
16:02:53 <kaz> ack k
16:02:55 <cris_> kaz: all the assignees have to keep in mind which use cases are important
16:03:45 <kaz> s/important/important to implement actual services and systems like grouping multiple Things for Smart Cities./
16:05:13 <cris_> ege: let's start this work from next week
16:05:26 <cris_> +1
16:05:35 <luca_barbato> +1
16:06:10 <cris_> ege: tomorrow we are going to discuss registry analysis and versioning
16:06:12 <Ege> https://github.com/w3c/wot/pull/1169
16:06:32 <cris_> [adjourned]
16:06:41 <kaz> i/tomorrow/topic: Tomorrow/
16:11:30 <kaz> rrsagent, draft minutes
16:11:32 <RRSAgent> I have made the request to generate https://www.w3.org/2024/01/24-wot-td-minutes.html kaz
18:07:17 <Zakim> Zakim has left #wot-td