- From: Courtney Kennedy <ckennedy@apple.com>
- Date: Fri, 18 Sep 2015 14:33:04 -0700
- To: Michael Dolan <mdolan@newtbt.com>
- Cc: Timed Text Working Group <public-tt@w3.org>
Hi Mike, To clarify- we defined a profile, with the abbreviation “T2VP”, to be used as part of a strategy for mapping from TTML documents to WebVTT. The profile constrains TTML to features that can be mapped straightforwardly to WebVTT. It is not intended to align with any other timed text formats or with any other profiles of TTML. The purpose and definition of the profile are described in section 2.1 of the Mapping document. So, with that clarification, does this issue become- “Change the abbreviation for the mapping profile because T2VP is confusingly similar to TTML2?” Courtney ______________________________ Courtney Kennedy Engineering Manager, Media Sharing mobile: 408-771-8615 > On Sep 18, 2015, at 10:56 AM, Michael Dolan <mdolan@newtbt.com> wrote: > > DS>>Ah. I rather hope we work out first what the best mapping is, and then > see whether that matches our hope that it uses features fully contained in > an existing profile. > > MD>>OK, that's a fine process. But my point is that if it does not fit > within IMSC1, then either WebVTT or IMSC1 or both may have issues WRT FCC > and 708 which was a requirements design point for both. Additionally, this > feature intersection profile has to meet some reasonable interpretation of > FCC requirements or such a profile is an academic exercise in the and not > commercially interesting. That is, when done, either WebVTT and/or IMSC1 may > have to change. > > Anyway, keep up the good work and we'll figure it out... > > Mike > > -----Original Message----- > From: singer@apple.com [mailto:singer@apple.com] > Sent: Friday, September 18, 2015 9:27 AM > To: Michael Dolan <mdolan@newtbt.com> > Cc: Timed Text Working Group <public-tt@w3.org> > Subject: Re: ISSUE-415 (TTML2): TTML2 is confusing [TTML WebVTT mapping > note] > > >> On Sep 18, 2015, at 7:32 , Michael Dolan <mdolan@newtbt.com> wrote: >> >> Then I guess we both misunderstood :-) >> >> Sorry for my sloppy precision on acronyms. The net is that I think >> more clarity is needed around using "2" as a shorthand for the English > word "to" >> as it is ambiguous. > > agreed! > >> >> I thought for sure it was stated in our call that the mapping was >> intended to be a subset of IMSC1. If it really is not, then it would >> be rather important to understand how they differ exactly. This would >> indicate that there is a mismatch between these two profiles and FCC >> 708 required decoder behavior that was probably not intended. > > Ah. I rather hope we work out first what the best mapping is, and then see > whether that matches our hope that it uses features fully contained in an > existing profile. > >> >> Regards, >> >> Mike >> >> -----Original Message----- >> From: Nigel Megitt [mailto:nigel.megitt@bbc.co.uk] >> Sent: Friday, September 18, 2015 6:36 AM >> To: Timed Text Working Group <public-tt@w3.org> >> Subject: Re: ISSUE-415 (TTML2): TTML2 is confusing [TTML WebVTT >> mapping note] >> >> Mike, >> >> I misunderstood the issue in our meeting yesterday. I thought you >> found "T2VP" confusing because it looks like it means TTML2 rather >> than TTML as it exists now. In other words one cannot distinguish >> between TTML to VTT and TTML 2 to VTT. >> >> I don't think it's appropriate to limit the mapping document to IMSC1. >> >> Kind regards >> >> Nigel >> >> >>> On 18 Sep 2015, at 10:39, Timed Text Working Group Issue Tracker >> <sysbot+tracker@w3.org> wrote: >>> >>> ISSUE-415 (TTML2): TTML2 is confusing [TTML WebVTT mapping note] >>> >>> http://www.w3.org/AudioVideo/TT/tracker/issues/415 >>> >>> Raised by: Mike Dolan >>> On product: TTML WebVTT mapping note >>> >>> Use of "TTML2" is doublely confusing - I understand the constraints >>> are >> against IMSC1, and thus neither TTML2 nor TTML(1). Suggest removing > "TTML2" >> and replace appropriate occurrences with "IMSC1". >>> >>> >>> >>> >>> >> >> >> ----------------------------- >> http://www.bbc.co.uk >> This e-mail (and any attachments) is confidential and may contain >> personal views which are not the views of the BBC unless specifically > stated. >> If you have received it in >> error, please delete it from your system. >> Do not use, copy or disclose the >> information in any way nor act in reliance on it and notify the sender >> immediately. >> Please note that the BBC monitors e-mails sent or received. >> Further communication will signify your consent to this. >> ----------------------------- >> >> > > David Singer > Manager, Software Standards, Apple Inc. > > >
Received on Friday, 18 September 2015 21:33:32 UTC