14:19:10 RRSAgent has joined #wot-td 14:19:14 logging to https://www.w3.org/2023/10/11-wot-td-irc 14:19:20 meeting: WoT-WG - TD-TF 14:21:08 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#October_11.2C_2023 14:25:16 chair: Ege 14:25:28 present+ Ege_Korkan, Michael_Koster, Kaz_Ashimura 14:25:31 scribenick: mjk 14:25:45 topic: organizational 14:26:04 ege: we plan to publish the agenda 1 week in advance 14:26:38 subtopic: TF moderators process 14:27:42 kaz: OK with the current moderators but will follow the process 14:27:59 topic: PR #1141 14:29:19 ege: made some minor corrections, looks OK 14:29:26 ... there is a lot of information 14:30:22 present+ Jan_Romann, Tomoaki_Mizushima 14:30:22 ... any objections to merge? 14:30:25 ... merged 14:31:06 i|made some|-> https://github.com/w3c/wot/pull/1141 wot PR 1141 - Create 2023-09-WoT-TPAC-TD-Discussion.md| 14:31:08 q+ 14:32:13 ack k 14:32:53 kaz: is the binding topic included? 14:33:03 mjk: yes, it is two sections 14:33:11 i/PR #1141/topic: Previous minutes/ 14:33:46 i|PR #1141|-> https://www.w3.org/2023/10/04-wot-td-minutes.html Oct-4| 14:33:52 i/PR #1141/(approved) 14:33:58 rrsagent, make log public 14:34:03 rrsagent, draft minutes 14:34:04 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 14:34:12 ege: break the summary into 2 separate sections 14:34:42 topic: PRs for REC preparation 14:34:53 subtopic: PR #1893 14:34:58 s/topic: Pre/subtopic: Pre/ 14:34:58 rrsagent, draft minutes 14:34:59 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 14:35:12 i/we plan to/topic: Agenda/ 14:35:21 s/organizational/Organizational/ 14:35:23 rrsagent, draft minutes 14:35:24 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 14:35:39 ege: updates names to clearly indicate version 1.0 content 14:35:42 s/topic: Agenda/subtopic: Agenda/ 14:35:46 rrsagent, draft minutes 14:35:47 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 14:36:17 ... it will be the same for 1.0 and 1.1 14:36:31 s/93/96/ 14:36:39 ... this is the staging area 14:36:57 i|updates|-> https://github.com/w3c/wot-thing-description/pull/1896 PR 1896 - Version 1.0 publication folder| 14:37:00 rrsagent, draft minutes 14:37:01 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 14:37:31 ege: merged 14:37:46 sub-topic: PR #1895 14:38:45 ege: corrects the affiliation for past contributors to be correct for the time they were contributors 14:38:54 i|corrects|-> https://github.com/w3c/wot-thing-description/pull/1897 PR 1897 - Adjust affiliations| 14:39:01 s/#1895/#1897/ 14:39:19 ... any objections to merge? 14:40:00 ... merged 14:40:54 ege: with this, TD 1.1 should be ready for publication 14:40:54 https://w3c.github.io/wot-thing-description/publication/ver11/7-rec/Overview 14:41:13 i/https/subtopic: Draft for REC publication/ 14:42:22 ege: should we send an email to the group asking for a resolution? 14:42:58 kaz: yes, the next step is a resolution 14:43:22 kaz: then there are steps to send it on to the review team 14:43:44 ... asked McCool to update the documentation with these steps 14:43:55 -> https://github.com/w3c/wot/blob/main/planning/schedule.md schedule.md to be updated 14:44:43 ege: OK, will send email and ask for the resolution next week 14:44:55 topic: binding templates 14:45:31 ege: mjk, did you do any updates? 14:45:48 mjk: no updates this week 14:46:00 ege: there is a comment from Joel Bender 14:46:36 ... comment on the spelling of terms and additional COV parameters 14:47:18 ... also, BACnet doesn't use the standard IP layer for internetworking 14:47:20 i|there is|subtopic: Issue 302| 14:47:33 i|there is|-> https://github.com/w3c/wot-binding-templates/issues/302 Issue 302 - URI Variable for BACnet| 14:48:00 subtopic: Issue 303| 14:48:13 -> https://github.com/w3c/wot-binding-templates/issues/303 Issue 303 - bacv context URL in examples| 14:48:43 ege: brief review of the 4 open issues on the BACnet binding 14:49:10 topic: td.next 14:49:48 ege: the goal is to create a roadmap 14:50:06 ... we need to gather all of the relevant documents 14:50:22 q+ 14:50:48 ... review of a list of documents and PRs 14:51:03 ... where should we gather these? 14:51:22 kaz: consolidating the information makes sense 14:51:55 we should categorize document reorganization vs. technical extension 14:52:11 s/we/kaz: we 14:52:38 ... we should then evaluate each item wrt. priority and impact on other documents 14:53:35 ege: review the work items draft proposal (work-items.md) 14:54:34 ... PR #1111 to reorganize the work item list 14:55:05 -> https://github.com/w3c/wot/pull/1111 wot PR 1111 - Reorganize TD work items 14:55:10 rrsagent, make log public 14:55:14 rrsagent, draft minutes 14:55:16 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 14:55:30 present+ Cristiano_Aguzzi 14:55:34 ... there are 3 categories: usability and design, features, and supporting items 14:55:59 ... feature items need use cases 14:56:00 s/binding templates/Binding Templates/ 14:56:02 rrsagent, draft minutes 14:56:04 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 14:56:49 cris__ has joined #wot-td 14:57:01 ... supporting items are not technical features 14:57:14 ... like canonicalization, versioning 14:57:35 q? 14:57:37 ack k 14:57:54 i|there are 3|-> https://github.com/w3c/wot/blob/main/planning/ThingDescription/work-items.md work-itmes.md 14:57:57 rrsagent, draft minutes 14:57:58 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 14:58:05 ege: should we merge this now? 14:58:22 q+ 14:58:49 kaz: since it's identified as a draft, it's OK to merge 14:59:15 ... maybe we should add the rest of the items, e.g. long running actions, etc. 14:59:39 ... Also should indicate draft status in square brackets 14:59:53 ege: OK 15:00:56 q? 15:01:00 q- 15:01:18 rrsagent, draft minutes 15:01:20 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 15:02:56 ege: walk through the changes in the document 15:03:58 ... everything is still there, just moved around 15:04:04 +1 for merging 15:04:04 ... any objections to merge? 15:04:24 ... merged 15:05:16 ... link this into the planning document 15:05:36 sub-topic: roadmap 15:06:24 q+ 15:06:36 ... review the charter document 15:06:53 ... is the FPWD expected in Q1? 15:07:03 kaz: it could be the end of the quarter 15:07:34 ... this was worked back from the end, so maybe the time frame will need to be updated 15:08:05 ... this was done before we knew the actual charter start data 15:08:40 ... we should add a link from the charter page to a status page with the actual schedule 15:09:27 ... we can manage the actual schedule without having to update the charter page 15:09:35 ege: wher eis the status page? 15:09:48 s/wher eis/where is 15:10:23 ege: reviewing the current status page 15:10:35 ... it is all in one table 15:10:47 kaz: separate tables would be better 15:11:03 q- 15:11:25 i|review the char|-> https://www.w3.org/2023/10/wot-wg-2023.html New WoT WG Charter| 15:12:53 ege: reviewing the schedule, working back to CR transition 6 months before publication, March 2025 15:13:45 ... everything between now and then is for us to organize 15:14:06 ... does anyone have comments/ideas for organizing the schedule? 15:14:37 ... implementation time will require some decisions earlier 15:14:53 q+ 15:14:58 ... new features need to be defined in time to implement 15:15:05 -> https://w3c.github.io/spec-releases/milestones/ milestone calculator 15:16:53 (Ege plays with the milestone calculator) 15:16:57 ege: configuring the milestone calculator dates 15:18:50 ... we need to think about implementation time and plugtests and set feature freeze dates 15:19:49 ... roughly by the end of next year we need to have big features 15:19:55 q? 15:19:56 q- 15:20:04 ... document restructure can be done in parallel 15:20:27 q+ 15:20:46 JKRhb has joined #wot-td 15:21:05 cris: it's hard to predict the implementation time, hard to know what will break 15:21:20 ... there is a 1-2 month uncertainty 15:21:23 q+ 15:21:25 ack c 15:22:00 ... accommodating use cases will take longer 15:22:34 ... also there will be different number of people working on a feature 15:23:34 ack k 15:23:42 kaz: this is an initial schedule, it is more important to have a process to keep it up to date 15:24:10 ege: we can put a schedule review/update in every agenda 15:24:18 kaz: weeklu check-ups 15:24:25 s/weeklu/weekly 15:25:56 ege: this month we can gather everything needed for work items in one place, in the TD repository 15:27:35 q+ 15:27:53 ege: I have a related resources area already started, we can add the other feature items to that 15:28:42 ... for example, PR #1126 - registry analysis 15:29:10 ... this contains the background we need to start work on each item 15:29:44 ... it would be good to share the load 15:30:04 ack k 15:30:22 kaz: agreed, we should clarify what kind of mechanisms we need to use 15:30:56 i|this contains|-> https://github.com/w3c/wot/pull/1126 wot PR 1126 - Create registry analysis folder and its readme| 15:31:02 rrsagent, draft minutes 15:31:04 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 15:31:14 ege: what is available from other registry systems in W3C and IANA 15:32:04 q? 15:34:00 ... is anyone interested in analyzing the existing registry mechanisms? 15:34:23 mjk: we can write down our use case needs for our binding registry 15:34:48 ege: we can look at something we're already doing 15:35:17 ... we are expecting protocol experts to contribute documents 15:36:44 ... the registry is bound to the TD spec version 15:37:26 ... the registry entries outlive the TD specification updates 15:40:12 rrsagent, draft minutes 15:40:13 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 15:40:49 ... What needs to be registered? Name, stable link, prefix, context 15:40:49 q+ 15:41:22 kaz: we can start with the template for the IANA media type registry 15:42:18 ege: we will have some requirements for the documents 15:42:39 q? 15:42:42 q- 15:43:02 i|we will|-> https://w3c.github.io/wot-thing-description/#iana-section TD spec - 12. IANA Considerations 15:43:06 rrsagent, draft minutes 15:43:08 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 15:44:36 mjk: this is a good start, to reserve names and point to controlling documents 15:44:50 ege: any volunteers? 15:45:10 cris: I will review the IANA registry 15:46:33 mjk: I will review an W3C registry 15:46:54 ege: there is the DID registry 15:48:25 ... assign links to volunteers in the document 15:48:58 q+ 15:49:56 kaz: there is another approach for markup languages that is about 10 years old 15:50:59 mjk: there is a short list of W3C registries in the TPAC summary 15:51:10 s/there is/would suggest we start with those popular ones. there is/ 15:52:24 i|there is a|-> https://www.w3.org/2005/04/xpointer-policy XPointer Scheme Name Registry Policy| 15:52:28 q? 15:53:34 ack k 15:54:24 ege: do you know of others? 15:54:36 kaz: you can go to w3c.org/TR 15:54:51 -> https://www.w3.org/TR/?filter-tr-name=&status%5B%5D=dry&status%5B%5D=cry&status%5B%5D=ry Registries on /TR 15:55:05 s/w3c.org/w3.org/ 15:55:11 rrsagent, draft minutes 15:55:13 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 15:55:19 q? 15:55:49 ege: any objections to merge PR #1126 as a starting place? 15:56:08 jan: should we update this document? 15:56:30 ege: yes. update this document 15:56:33 ... merged 15:57:47 https://github.com/w3c/wot/issues/1144 15:58:37 ege: issue created for assignment 15:59:09 jan: we can also create a task list 15:59:29 https://github.com/w3c/wot/issues/1145 16:00:31 ege: if someone comments on the issue, we can assign it to them 16:01:05 ... we are done with today's agenda 16:01:14 is there any other business? 16:01:24 s/is/ege: is 16:01:32 ege: adjourned 16:01:39 rrsagent, draft minutes 16:01:40 I have made the request to generate https://www.w3.org/2023/10/11-wot-td-minutes.html kaz 18:37:19 Zakim has left #wot-td