14:01:08 RRSAgent has joined #wot-td 14:01:12 logging to https://www.w3.org/2023/08/02-wot-td-irc 14:01:29 meeting: WoT-WG - TD-TF 14:01:37 present+ Kaz_Ashimura, Luca_Barbato, Ege_Korkan 14:02:08 agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#2_August_2023 14:02:19 chair: Ege 14:03:17 s|https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#2_August_2023|https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#August_2.2C_2023| 14:03:24 rrsagent, make log public 14:03:28 rrsagent, draft minutes 14:03:29 I have made the request to generate https://www.w3.org/2023/08/02-wot-td-minutes.html kaz 14:04:01 cris__ has joined #wot-td 14:04:08 regrets+ Koster 14:04:21 present+ Cristiano_Aguzzi 14:06:44 q+ 14:07:36 ack k 14:08:36 topic: Logistics 14:08:57 kaz: would it make sense to have a call today with 3 participants and a Team Contact? 14:09:08 ... should be discussed as part of the policy discussion as well, though 14:10:07 ... given we have several urgent issues, we still could discuss them 14:10:21 i/would it/scribenick: kaz/ 14:10:57 scribenick: luca_barbato 14:11:20 topic: Minutes 14:12:03 ege: I did an overall look and they look good for my point of view beside few typos 14:13:52 q? 14:13:57 typos fixed 14:14:06 present+ Tomoaki_Mizushima 14:14:08 ack k 14:14:14 sebastian has joined #wot-td 14:14:14 ege: Are the minutes fine now for everybody? 14:14:18 14:14:33 topic: Organization 14:15:04 s/Organization/Meeting schedule/ 14:15:05 ege: Shall we have a call on Aug 23rd 14:15:16 i|did an|-> https://www.w3.org/2023/07/26-wot-td-minutes.html July-26| 14:15:29 ca: not available 14:15:39 lb: should be available 14:15:42 mizu: not available 14:16:36 kaz: available if needed 14:16:36 i/ca:/scribenick: kaz/ 14:16:36 q+ 14:16:54 ek: will check with Koster too 14:18:10 kaz: given half of us mentioned they would not be available for 23rd, we can simply cancel it 14:18:41 ek: what about next week on Aug 9? 14:18:41 ... maybe Koster can chair the call. will check with him 14:19:06 topic: TPAC agenda 14:19:08 ek: being finalized 14:19:18 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda TPAC agenda 14:19:30 topic: Urgent PRs 14:20:13 ege: I add a new label for the changes in index.html 14:20:20 s/I add/I've added/ 14:20:20 https://github.com/w3c/wot-thing-description/pulls?q=is%3Aopen+is%3Apr+label%3A%22by+REC+publication%22+label%3A%22changes+index.html%22 14:20:29 s/https/-> https/ 14:21:45 s/html%22/html%22 TD PRs with "changes index.html" label/ 14:21:47 kaz: among all those four PRs, two of the (1858 and 1843) are important 14:21:58 ... the other two are truly editorial 14:22:05 i/among/scribenick: kaz/ 14:22:12 scribenick: luca_barbato 14:22:49 proposal: The TD Task Force agrees that the PRs 1842, 1843, 1845, 1858 should be merged after approval of PLH and incorporated into the Recommendation version of the Thing Description 1.1 14:22:52 JKRhb has joined #wot-td 14:23:35 kaz: Note that editorial bugfixes are allowed anytime, changes in the normative parts needs approval from the chairs 14:24:26 ege: shall we land them now or wait for a further approval? 14:24:35 proposal: The TD Task Force agrees that the PRs 1842, 1843, 1845, 1858 should be merged group resolution next wednesday and incorporated into the Recommendation version of the Thing Description 1.1 14:24:53 s/needs app/need app/ 14:25:35 proposal: The TD Task Force agrees that the PRs 1842, 1843, 1845, 1858 should be merged after a group resolution next wednesday and incorporated into the Recommendation version of the Thing Description 1.1 14:25:54 cris: Ok for me 14:27:03 proposal: The TD Task Force agrees that the PRs 1843, 1858 should be merged after a group resolution next wednesday and incorporated into the Recommendation version of the Thing Description 1.1 14:27:58 proposal: The TD Task Force agrees that the PRs 1843, 1858 should be merged after approval of PLH, incorporated into the Recommendation version of the Thing Description 1.1 and reported to the whole WG. 14:28:32 resolution: The TD Task Force agrees that the PRs 1843, 1858 should be merged after approval of PLH, incorporated into the Recommendation version of the Thing Description 1.1 and reported to the whole WG. 14:30:15 topic: TPAC Agenda 14:30:36 i/TPAC/(@@@ Kaz will remove the first 3 proposals from the minutes later)/ 14:30:51 rrsagent, draft minutes 14:30:53 I have made the request to generate https://www.w3.org/2023/08/02-wot-td-minutes.html kaz 14:31:12 s/TPAC Agenda/TPAC Agenda - revisited/ 14:33:27 q+ 14:33:33 ack k 14:33:38 q+ 14:33:50 ege: I'll change the priority to the current list 14:33:50 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda#Thing_Description Thing Description topics 14:34:25 cris: I second the proposed the prioritization 14:34:43 cris: The low priority topic can be discussed during other times? 14:35:05 ege: We have to be conservating on the amount of topics to touch since we just have 1 hour 14:35:27 kaz: We should concentrate on 1-2 topics 14:37:09 ege: We can move TD in RDF may be discussed in the joint session with JSON-LD 14:37:50 s/1-2 topics/1-2 topics given we have only 1h+15m for this slot. Also we need to consider the possible joint discussion with the JSON-LD guys./ 14:38:05 q? 14:38:11 ack c 14:38:12 ack k 14:38:25 ege: Manageable Actions might be discussed if we have participation from other people of the hypermedia community 14:38:26 q+ 14:41:26 kaz: Might be useful to discuss use-cases as well 14:41:49 +1 for kaz 14:48:11 q? 14:48:19 ack k 14:48:24 q+ 14:48:51 kaz: We should not focus on future features, but discuss more on use-cases and makes sure to extract requirements that justify the features more 14:50:51 ege: We should be already well set for some of our pending features (e.g. timeseries) 14:53:23 kaz: We've been holding discussion on topics for the next Charter period, so we should continue our discussion based on that result. 14:53:32 i/We've/scribenick: kaz/ 14:54:06 ack k 14:54:29 ack lu 14:54:31 q+ 14:54:54 s/We've been/Right. We've been/ 14:57:29 lu: use-cases and the process of extracting features should probably be part of a wider group discussion and given the allotted time at TPAC I would not spend time on it specifically 14:57:37 present+ Jan_Romann 14:57:43 q? 14:58:55 lu: we have already enough requirements (e.g. my set of current pain points in 1.1) so we somebody cares more about others should had already asked about them, we can discuss regarding how to improve the use-case process and do better outreach (e.g what we are doing with the mqtt community now) but 14:59:08 it is again something for the larger group to discuss in my opinion. 14:59:19 s/it is/... it is/ 15:00:21 kaz: We could discuss the pain points during the TPAC TD slot 15:01:01 ack k 15:01:27 ege: Can move on to the next topic 15:02:18 topic: PR 1862 (resource versioning/serving) 15:03:18 q+ 15:03:31 q+ 15:04:13 i|-> https://github.com/w3c/wot-thing-description/pull/1862 PR 1862 - Add rec10 resources 15:04:23 rrsagent, draft minutes 15:04:24 I have made the request to generate https://www.w3.org/2023/08/02-wot-td-minutes.html kaz 15:05:34 ack c 15:05:41 i/use-cases and the/scribenick: luca_barbato/ 15:05:47 rrsagent, draft minutes 15:05:48 I have made the request to generate https://www.w3.org/2023/08/02-wot-td-minutes.html kaz 15:05:55 q+ 15:05:55 q? 15:05:56 ack j 15:06:27 jkr: td-context-1.1 for rec10 ? 15:06:50 ege: It is correct, potentially it is because json-ld 1.1 15:07:34 ege: in 2.0 we should overahul everything so it is less confusing 15:08:07 ege: for rec10 and rec11 I'd not make radical changes 15:08:26 kaz: is it to be done now? 15:08:45 ege: I'd land them before the rec is published 15:09:31 kaz: Does it have impact to the implementations? 15:14:17 q+ 15:14:19 ack k 15:14:32 q+ 15:14:57 s/implementations?/implementations? All the mechanism around this update (and other proposed updates) should be described a bit more./ 15:15:06 rrsagent, draft minutes 15:15:07 I have made the request to generate https://www.w3.org/2023/08/02-wot-td-minutes.html kaz 15:15:18 topic: PR 1863 15:15:34 -> https://github.com/w3c/wot-thing-description/pull/1863 PR 1863 - Add rec11 resources 15:17:19 q+ 15:17:22 lu: Embedding date to the version we could do better and make it fitting semver 15:17:24 ack lu 15:18:07 cris: we needed to embedd the date to make so the npm packages fit 15:18:34 cris: We can change the schema on release to 1.1 15:19:31 ege: We might change the schema to include bugfixes 15:19:37 ... in the future 15:20:45 ack cris 15:20:46 ack k 15:20:54 cris: for reference this is the package that we are generating using the schema -> https://www.npmjs.com/package/wot-thing-description-types/v/1.1.0-20-July-2022?activeTab=versions 15:22:49 q+ 15:22:53 kaz: again, as I mentioned for PR 1862, we should summarize what is needed for what, and which implementation would get impacts from this proposed change too. Then should clarify what kind of notation would fit with the need./ 15:23:06 s|need./|need.| 15:23:56 _pre20231212 15:26:25 q? 15:26:27 ack l 15:26:29 topic: PR 1861 15:27:31 -> https://github.com/w3c/wot-thing-description/pull/1861 PR 1861 - Desired namespaces for 1.0 and 1.1 resources 15:27:32 ege: This PR updates the desidered namespaces for the resources 15:29:19 q+ 15:31:17 kaz: Do we really need so long urls? 15:31:48 q+ 15:31:57 ack k 15:32:16 s/long urls/long URLs under the publication subdirectory?/ 15:32:21 q+ 15:33:24 lu: Cannot we just rely on tags? 15:36:25 lu: we can customize the github action to publish to pages 15:38:36 kaz: it is not ideal to put ratified resources on github.io 15:38:55 kaz: we could use a separate repository for the ratified resources 15:39:24 q+ 15:40:17 ack l 15:40:18 ack k 15:41:13 s/it is not ideal to put ratified resources on github.io/The "publication" area is a temporary area for publication, e.g., Pubrules checker and Validator, so I don't think it would be ideal to put those resources under that area./ 15:41:59 lu: We should produce specific artifacts in github release 15:43:39 s/we could use a separate repository for the ratified resources/We should have some more discussion about where to pub. For example, we could even use a separate dedicated repository to manage this kind of resources if needed./ 15:43:46 ack k 15:43:50 ack c 15:45:04 kaz: Given this kind of resources are rather stable, we don't need to think about GitHub actions to maintain the resource but should still think about which location would be better for implementers later./ 15:45:10 s|later./|later.| 15:45:18 cris: it is better to make sure we put the resources in a permanent storage and not keep them as copies in git main branches 15:47:23 q+ 15:55:57 ack k 15:56:22 kaz: would suggest we ask JSON-LD/VC guys for advice about this 15:56:27 ek: good idea 15:58:06 topic: TPAC participation 15:58:22 (Ege ask people about their participation in TPAC 2023) 15:58:28 q+ 15:59:05 kaz: please update the TPAC WoT wiki's participation section based on your latest situation 16:00:03 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda#Presence Presence section 16:00:10 s/participation section/presence section/ 16:00:18 [adjourned] 16:00:23 rrsagent, draft minutes 16:00:24 I have made the request to generate https://www.w3.org/2023/08/02-wot-td-minutes.html kaz