- From: Thierry MICHEL <tmichel@w3.org>
- Date: Wed, 28 Mar 2018 19:41:06 +0200
- To: Nigel Megitt <nigel.megitt@bbc.co.uk>, David Singer <singer@apple.com>
- Cc: W3C Public TTWG <public-tt@w3.org>
now updated https://w3c.github.io/charter-timed-text/Draft-2018-TTWG-Charter.html On 28/03/2018 18:57, Nigel Megitt wrote: > Comments inline: > > On 28/03/2018, 17:50, "singer@apple.com on behalf of David Singer" > <singer@apple.com> wrote: > >> Some minor corrections from a colleague: >> >> 1) "captions for deaf and hard of hear² should be "captions for the deaf >> and hard of hearing² (insert ³the² and ³ing²) > > +1 done > >> >> 2) Not clear why this is a VTT-specific requirement: >> >> € Include all features that have at least two independent and >> interoperable implementations. removed >> 3) Is it ³TTML1² or ³TTML 1²? is it consistent with ³IMSC1²? > > We have used different styles for TTML and IMSC when it comes to appending > the numbering. I'm not really bothered about this, happy to make it > consistent or retain the inconsistency between them in favour of > consistency with prior usage. updated tp TTML1 > >> >> 4) TTML is defined as >> >> "This specification defines a content type that represents timed text >> media for the purpose of interchange among authoring systems." >> >> however, it now is the basis for IMSC, which is delivery. The scope >> should be expanded. > > Good catch. It also needs to be edited in the TTML2 Abstract, which says > the same thing. It should probably be "This specification defines a > content type that represents timed text media for the purpose of > interchange among authoring, distribution and playback systems." > updated >> 5) IMSC1.1 is documented here as based on TTML1, but isn¹t it based on >> TTML2? > > Yes, IMSC 1.1 is based on TTML2 with extensions from IMSC 1.0.1, whereas > IMSC 1.0.1 is based on TTML1. > >> >> 6) ³Entertainement² -> ³Entertainment² > > +1 updated > > Nigel > >> >> >> >>> On Mar 27, 2018, at 8:43 , Nigel Megitt <nigel.megitt@bbc.co.uk> wrote: >>> >>> One further thought: presumably if our current Charter is extended, >>> that would give some more time to publish WebVTT CR. >>> >>> Nigel >>> >>> >>> From: Nigel Megitt <nigel.megitt@bbc.co.uk> >>> Date: Tuesday, 27 March 2018 at 11:12 >>> To: W3C Public TTWG <public-tt@w3.org>, Thierry Michel >>> <tmichel@w3.org>, "David (Standards) Singer" <singer@apple.com> >>> Subject: Re: edited TTWG draft charter, VTT? >>> Resent-From: <public-tt@w3.org> >>> Resent-Date: Tuesday, 27 March 2018 at 11:12 >>> >>>> As I understand it Thierry needs to send the updated Charter to W3 >>>> Management today. I propose that he sends it in the current form as >>>> visible at: >>>> >>>> https://w3c.github.io/charter-timed-text/Draft-2018-TTWG-Charter.html >>>> >>>> This currently includes WebVTT. Alongside this I suggest that Thierry >>>> highlights the open issues on the Charter at: >>>> >>>> https://github.com/w3c/charter-timed-text/issues >>>> >>>> And the email thread beginning at >>>> https://lists.w3.org/Archives/Public/public-tt/2018Mar/0094.html >>>> >>>> If the transition of WebVTT to CR happens within the current Charter >>>> period, then the Lisbon resolution will not apply. In any case W3M >>>> should be aware of the challenges the WG has had and may wish to take >>>> actions. >>>> >>>> Kind regards, >>>> >>>> Nigel >>>> >> >> David Singer >> Manager, Software Standards, Apple Inc. >> > >
Received on Wednesday, 28 March 2018 17:41:10 UTC