- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Tue, 18 Apr 2017 09:31:50 +1000
- To: David Singer <singer@mac.com>
- Cc: "public-texttracks@w3.org" <public-texttracks@w3.org>, Thierry MICHEL <tmichel@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>
Hi all, I'm supportive of David's efforts to take WebVTT through the W3C standards process (https://www.w3.org/2017/Process-20170301/) which means going from Working Draft (WD) to Candidate Recommendation (CR) as next step. For that, closing out the open wide review comments and completing the test suite are invaluable. I'm therefore supportive of the 4 resolutions David lists and the progress on the test suite. About the new issues, my summary reading of the GitHub issues is: 1) lots about live captioning requirements, which is a new feature to be developed 2) a couple of normative bugs, particularly related to overlapped rendering, which should not hold us up 3) a couple of editorial bugs, which are not urgent One thing we should do as part of preparing another WD for review is update all the references. I agree, I think we're ready to kick off the process. Cheers, Silvia. On Tue, Apr 18, 2017 at 8:59 AM, David Singer <singer@mac.com> wrote: > Folks > > 1. the ‘wide review’ page <https://www.w3.org/wiki/WebVTT_Wide_Review#Review_Requests_and_Responses> documents the disposition of all comments received in wide review except two: > * I-5, incomplete ruby: we will document that <rb> support is required (a normal part of ruby) and leave rtc and rbc to future (and rp unmentioned as it’s about HTML) > * C-8, proposed text to select by region on the way > > We closed: > * I-12: more formal grammar. We prefer to keep the formal text to the parsing rules, and provide a separate informative authoring guide (which is on the wiki) > * C-7: we can’t make the proposed change without risking confusion between cue identifiers and region identifiers > > *** With these four resolutions, do you (community group) agree with the disposition? *** I will take silence as consent, but some positive responses appreciated. > > > 2. The test suite is in much better shape and we have filed an fixed some ambiguities etc. that developing it showed. Please try the test suite and comment! > > 3. New issues we’d need to resolve before shipping out a new wide review and, I hope, a CR. I don’t see any in the list of 30 open that need immediate attention; do you? > <https://github.com/w3c/webvtt/issues> > > > > > > > > > > Dave Singer > > singer@mac.com > >
Received on Monday, 17 April 2017 23:32:44 UTC