14:02:43 RRSAgent has joined #wot-td 14:02:47 logging to https://www.w3.org/2023/09/06-wot-td-irc 14:04:40 meeting: WoT-WG - TD-TF 14:04:55 present+ Kaz_Ashimura, Michael_Koster, Sebastian_Kaebisch 14:05:14 regrets+ Ege 14:08:42 present+ Tomoaki_Mizushima 14:10:23 cris__ has joined #wot-td 14:11:41 scribenick: kaz 14:11:43 sebastian has joined #wot-td 14:11:45 chair: Koster 14:11:47 mjk has joined #wot-td 14:12:03 topic: Agenda 14:12:10 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#September_6.2C_2023 agenda for today 14:12:37 kaz: given we just have 3 participants a team contact, I'm not sure if it would make sense to have an official call 14:12:47 ... However, we can still share ideas for TPAC preparation 14:13:10 topic: Binding Templates publication 14:14:11 kaz: working the publication after the summer vacation and procedures on Proposed RECs and Charter 14:14:28 ... need some editorial updates on Process 2023, etc. 14:15:11 q+ 14:15:16 ... would like to publish the Notes (Binding and Scripting) this week or next using the auto publishing tool, Echidna 14:15:47 sk: after the publication, we should publish the Binding Template sub document for MQTT, etc., as well 14:15:55 q+ 14:15:57 ack s 14:16:49 kaz: for that purpose, we need to clarify the document structure, e.g., TD and Binding sub document, or potential registry 14:17:14 sk: that's partly true, but we already have an HTML document 14:17:17 ack k 14:18:03 kaz: we should be careful about the document structure as a whole 14:18:40 mjk: what we've been working on informally is having TD 2.0 spec and Binding registry 14:18:51 ... also using protocol binding less defined 14:19:13 ... we had Modbus and so on, though 14:19:35 ... we could probably look at what the document requirement would be 14:20:10 ... my question is about the structure requirement 14:20:16 present+ Luca_Barbato 14:20:29 ... do we have enough requirements already? 14:21:14 q? 14:21:16 q+ 14:21:29 q+ 14:22:08 kaz: btw, Luca has just joined, and now we could make the call an official one 14:22:15 mjk: ok 14:22:35 topic: Minutes 14:23:11 -> https://www.w3.org/2023/08/23-wot-td-minutes.html Aug-23 14:23:34 mjk: Aug 23 call was the latest one 14:24:36 ... (goes through the minutes) 14:28:57 kaz: regarding PR 1868 and 1842, Ege should have mentioned them on the mailing list as well 14:29:09 ... I can respond to his original email mentioning this 14:29:14 present+ Cristiano_Aguzzi 14:29:47 mjk: regarding the minutes themselves, I don't see any problems 14:29:52 minutes approved 14:30:05 rrsagent, make log public 14:30:37 rrsagent, draft minutes 14:30:38 I have made the request to generate https://www.w3.org/2023/09/06-wot-td-minutes.html kaz 14:30:45 topic: Next meetings after TPAC 14:30:57 mjk: do we want to have a meeting immediately after TPAC? 14:31:08 ... on September 20 14:31:32 (no objections) 14:31:45 mjk: let's have the next TD meeting on September 20 14:32:33 sk: maybe we might want to think about changing the date/time for the next Charter period 14:33:09 mjk: ok 14:33:29 ... what about availabilities and public holidays? 14:33:37 ... don't think any for September 14:33:56 topic: Thing Description 1.1 14:34:14 subtopic: PRs 14:34:26 q+ 14:34:30 -> https://github.com/w3c/wot-thing-description/pulls PRs 14:34:34 ack kaz 14:34:36 ack seb 14:35:32 subtopic: PR 1867 14:35:49 -> https://github.com/w3c/wot-thing-description/pull/1867 PR 1867 - Documenting TD resources next to the spec 14:36:01 ca: reviewed the proposed description 14:36:02 q+ 14:36:04 ack c 14:36:48 luca_barbato has joined #wot-td 14:37:38 mjk: there is a list of documents within the README.md. right? 14:37:41 ca: right 14:39:03 kaz: OK with adding this kind of description on the resources related to the WoT Thing Description spec 14:39:21 ... However, the description of the PR itself should be also more descriptive :) 14:39:51 ... we can merge this PR and think about how to improve the README.md later 14:39:53 (merged) 14:40:00 subtopic: PR 1861 14:40:46 -> https://github.com/w3c/wot-thing-description/pull/1861 PR 1861 - Desired namespaces for 1.0 and 1.1 resources 14:40:47 q+ 14:41:05 ca: clarifying the current status and the desired status of the URL redirections 14:42:05 q+ 14:42:21 kaz: OK with merging this as an initial proposal, but would suggest we add "DRAFT" to the title of the file 14:43:31 ack c 14:43:33 EGE has joined #wot-td 14:43:43 ... Given Ege is not here, we should wait for this PR, though 14:44:25 present+ Ege_Korkan_listen-only 14:44:45 q? 14:44:48 ack k 14:44:49 q+ 14:45:05 sk: good to summarize this kind of information 14:47:02 We can add DRAFT without an issue 14:48:44 kaz: given Ege is OK to add "[DRAFT]", let's add that to the title, and then merge this PR 14:48:50 mjk: ok 14:49:12 ... (adds "[Draft]" to the title) 14:50:02 ... any objections to merge this PR? 14:50:35 (no objections) 14:50:43 merged 14:51:15 q+ 14:51:52 topic: Quick preview of TPAC discussion 14:51:55 ack k 14:52:36 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda TPAC WoT agenda wiki 14:53:33 mjk: need to clarify our prioritization 14:54:21 sk: we won't have very long time during TPAC for TD/Binding 14:54:37 q? 14:54:40 q+ 14:55:18 kaz: if the three topics listed at "Thing Description Final Topics", that's fine 14:55:26 ... summarizing planned activities 14:55:30 ... binding registry 14:55:39 ... and potentially, manageable actions 14:55:50 mjk: yeah, those topics would be good 14:56:04 I find the registry topic important since we can get feedback from a wider w3c presence 14:56:23 (just what koster said now :) ) 14:56:44 mjk: would be good to talk about binding registry during TPAC to get wider input 14:57:02 q+ 14:57:39 ... the procedure on who does what would be also important 14:58:04 ... regarding "manageable actions", Matthias did much about that 14:58:23 ... maybe I can use 5 minutes 14:59:07 kaz: I'd assume Sebastian will moderate the slot 14:59:30 ... and we should clarify who will talk about which item within how long time 14:59:38 I can talk about the registry mechanism and kickstart the discussion 15:01:38 mjk: Sebastian can talk about the summary 15:01:51 ... 20mins for summary 15:01:57 ... 20mins for registry 15:02:07 ... 5mins for manageable actions 15:02:10 q+ 15:02:11 ... then Q&A 15:02:13 ack k 15:03:45 ca: so we'll have a slot for manageable actions too 15:03:59 mjk: yes. just 5mins, though 15:04:17 q+ 15:04:25 ack cr 15:04:42 ack k 15:07:09 kaz: (added time assignment and speakers to the agenda wiki) 15:07:23 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda#Thing_Description_Final_Topics updated TD topics 15:07:32 topic: AOB 15:07:39 mjk: those are the items for today 15:07:43 ... any other business? 15:07:46 (nothing) 15:07:51 [adjourned] 15:07:54 rrsagent, make log public 15:08:00 rrsagent, draft minutes 15:08:01 I have made the request to generate https://www.w3.org/2023/09/06-wot-td-minutes.html kaz 15:08:07 q+ 15:08:20 s/[adjourned]// 15:08:39 lb: might be good to start to think about something 15:08:55 ... what you can expect for the WoT Thing Description 15:09:07 s/tion/tion?/ 15:09:30 ... e.g., about the base URL 15:09:56 ... would like to open some discussion for WoT Discovery too 15:10:01 q+ 15:10:04 ack lu 15:10:21 ... would be good to expand the capability of TD too 15:10:29 q? 15:10:37 mjk: sounds like we need essential clarification 15:11:44 lb: sometimes TD would not really be self-contained 15:12:49 kaz: we could talk about that during the commercial use case session next Friday with some use case description 15:13:11 lb: you can not reject valid TD even with a broken consumption 15:13:58 ack k 15:13:59 q+ 15:14:28 mjk: maybe we should clarify best practices 15:16:02 kaz: we don't have any dedicated slot for best practices or implementation guidelines during TPAC 15:16:31 ... so my suggestion is talking about the problem during the use case discussion 15:18:08 ... "use case discussion" doesn't only mean the "WoT Use Cases and Requirements Note" but also means possible setting for WoT-based IoT implementations including various Internet standards 15:18:18 See you there! 15:19:53 ... So having this discussion during the use case session would be useful not only for the use case discussion itself but also for the implementation guideline discussion. 15:19:53 [adjourned] 15:19:53 rrsagent, draft minutes 15:19:54 I have made the request to generate https://www.w3.org/2023/09/06-wot-td-minutes.html kaz 17:25:40 kaz has joined #wot-td 18:55:35 Zakim has left #wot-td