Meeting minutes
Organizational
Agenda
Ege: we plan to publish the agenda 1 week in advance
TF moderators process
Kaz: OK with the current moderators but will follow the process
Previous minutes
<kaz> Oct-4
<kaz> (approved)
PR #1141
<kaz> wot PR 1141 - Create 2023-09-WoT-TPAC-TD-Discussion.md
Ege: made some minor corrections, looks OK
… there is a lot of information
… any objections to merge?
… merged
Kaz: is the binding topic included?
Koster: yes, it is two sections
Ege: break the summary into 2 separate sections
PRs for REC preparation
PR #1896
<kaz> PR 1896 - Version 1.0 publication folder
Ege: updates names to clearly indicate version 1.0 content
… it will be the same for 1.0 and 1.1
… this is the staging area
Ege: merged
PR #1897
<kaz> PR 1897 - Adjust affiliations
Ege: corrects the affiliation for past contributors to be correct for the time they were contributors
… any objections to merge?
… merged
Ege: with this, TD 1.1 should be ready for publication
Draft for REC publication
<Ege> https://
Ege: should we send an email to the group asking for a resolution?
Kaz: yes, the next step is a resolution
Kaz: then there are steps to send it on to the review team
… asked McCool to update the documentation with these steps
<kaz> schedule.md to be updated
Ege: OK, will send email and ask for the resolution next week
Binding Templates
Ege: mjk, did you do any updates?
Koster: no updates this week
Issue 302
<kaz> Issue 302 - URI Variable for BACnet
Ege: there is a comment from Joel Bender
… comment on the spelling of terms and additional COV parameters
… also, BACnet doesn't use the standard IP layer for internetworking
Issue 303|
<kaz> Issue 303 - bacv context URL in examples|
Ege: brief review of the 4 open issues on the BACnet binding
td.next
Ege: the goal is to create a roadmap
… we need to gather all of the relevant documents
… review of a list of documents and PRs
… where should we gather these?
Kaz: consolidating the information makes sense
Kaz: we should categorize document reorganization vs. technical extension
… we should then evaluate each item wrt. priority and impact on other documents
Ege: review the work items draft proposal (work-items.md)
… PR #1111 to reorganize the work item list
<kaz> wot PR 1111 - Reorganize TD work items
<kaz> work-itmes.md
Ege: there are 3 categories: usability and design, features, and supporting items
… feature items need use cases
… supporting items are not technical features
… like canonicalization, versioning
Ege: should we merge this now?
Kaz: since it's identified as a draft, it's OK to merge
… maybe we should add the rest of the items, e.g. long running actions, etc.
… Also should indicate draft status in square brackets
Ege: OK
Ege: walk through the changes in the document
… everything is still there, just moved around
<cris__> +1 for merging
Ege: any objections to merge?
… merged
… link this into the planning document
roadmap
<kaz> New WoT WG Charter
Ege: review the charter document
… is the FPWD expected in Q1?
Kaz: it could be the end of the quarter
… this was worked back from the end, so maybe the time frame will need to be updated
… this was done before we knew the actual charter start data
… we should add a link from the charter page to a status page with the actual schedule
… we can manage the actual schedule without having to update the charter page
Ege: where is the status page?
Ege: reviewing the current status page
… it is all in one table
Kaz: separate tables would be better
Ege: reviewing the schedule, working back to CR transition 6 months before publication, March 2025
… everything between now and then is for us to organize
… does anyone have comments/ideas for organizing the schedule?
… implementation time will require some decisions earlier
… new features need to be defined in time to implement
<kaz> milestone calculator
<kaz> (Ege plays with the milestone calculator)
Ege: configuring the milestone calculator dates
… we need to think about implementation time and plugtests and set feature freeze dates
… roughly by the end of next year we need to have big features
… document restructure can be done in parallel
cris: it's hard to predict the implementation time, hard to know what will break
… there is a 1-2 month uncertainty
… accommodating use cases will take longer
… also there will be different number of people working on a feature
Kaz: this is an initial schedule, it is more important to have a process to keep it up to date
Ege: we can put a schedule review/update in every agenda
Kaz: weekly check-ups
Ege: this month we can gather everything needed for work items in one place, in the TD repository
Ege: I have a related resources area already started, we can add the other feature items to that
… for example, PR #1126 - registry analysis
<kaz> wot PR 1126 - Create registry analysis folder and its readme
Ege: this contains the background we need to start work on each item
… it would be good to share the load
Kaz: agreed, we should clarify what kind of mechanisms we need to use
Ege: what is available from other registry systems in W3C and IANA
… is anyone interested in analyzing the existing registry mechanisms?
Koster: we can write down our use case needs for our binding registry
Ege: we can look at something we're already doing
… we are expecting protocol experts to contribute documents
… the registry is bound to the TD spec version
… the registry entries outlive the TD specification updates
… What needs to be registered? Name, stable link, prefix, context
Kaz: we can start with the template for the IANA media type registry
<kaz> TD spec - 12. IANA Considerations
Ege: we will have some requirements for the documents
Koster: this is a good start, to reserve names and point to controlling documents
Ege: any volunteers?
cris: I will review the IANA registry
Koster: I will review an W3C registry
Ege: there is the DID registry
… assign links to volunteers in the document
Kaz: there is another approach for markup languages that is about 10 years old
<kaz> XPointer Scheme Name Registry Policy
Koster: would suggest we start with those popular ones. there is a short list of W3C registries in the TPAC summary
Ege: do you know of others?
Kaz: you can go to w3.org/TR
<kaz> Registries on /TR
Ege: any objections to merge PR #1126 as a starting place?
jan: should we update this document?
Ege: yes. update this document
… merged
<Ege> w3c/
Ege: issue created for assignment
jan: we can also create a task list
<Ege> w3c/
Ege: if someone comments on the issue, we can assign it to them
… we are done with today's agenda
Ege: is there any other business?
Ege: adjourned