- From: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Date: Thu, 10 Oct 2024 14:19:44 +0000
- To: "public-tt@w3.org" <public-tt@w3.org>
- Message-ID: <0266C10E-A366-40EA-A41E-22552E849542@bbc.co.uk>
TTWG, As discussed in our face to face meeting at TPAC, we believe that DAPT is ready for a transition to Candidate Recommendation. We effectively began the process of asking for a working group review during that meeting, on 27th September, but I did not issue a formal CfC at that time. Nevertheless the reviewing has begun, and some issues and associated pull requests have been raised – thank you Andreas! So that we have a formal record, this email is a Call for Consensus to publish DAPT as a Candidate Recommendation. As per our Decision Policy<https://www.w3.org/2023/04/timed-text-wg-charter.html#decisions>, if we have no unresolved objections in 10 working days, i.e. by 24th October, I will declare this to be a Working Group Decision. A note about what this applies to The version for review is the current Working Draft, at https://www.w3.org/TR/2024/WD-dapt-20241010/ - this incorporates some editorial changes made more recently than our last meeting. However, there are open pull requests<https://github.com/w3c/dapt/pulls> that address issues raised since 27th September. One of those (#256<https://github.com/w3c/dapt/pull/256>) is a substantive change. The final version for which we will request transition will be the current working draft with any approved pull requests merged, so in addition to reviewing the Working Draft, please take a look at the open pull requests and highlight any issues you see with them. Timeline * 10th October: Chair issues call for consensus (this email) * 10-24 October: group to review specification and raise any issues; also review pull requests * 24th October: Chair to assess whether we have consensus, and if so, Editors to merge pull requests and Chair to ask Team to make the transition request Horizontal Review updates As part of the preparation I prepared a substantive changes summary<https://www.w3.org/TR/dapt/substantive-changes-summary.txt> (since first public working draft). Looking at that list, I find it doubtful that any of the HR groups would want to re-assess DAPT since the review they already did, however it makes sense to point them to the list for information and/or a delta review, should they think it necessary. Atsushi, would you be able to send a pointer to the changes to the HR groups and notify them of our intent to transition to CR when this CfC has closed? Nigel (as Chair)
Received on Thursday, 10 October 2024 14:19:58 UTC