- From: Michael Dolan <mdolan@newtbt.com>
- Date: Wed, 26 Aug 2015 06:47:47 -0700
- To: "'Timed Text Working Group'" <public-tt@w3.org>
I am afraid that if W3C can't move this along much faster, that it will defacto be moved to another forum and the W3C registry will become irrelevant in practice. If W3C policy requires some supporting document, why can't it be a WG Report? There is zero IPR in a code point register. Mike -----Original Message----- From: Nigel Megitt [mailto:nigel.megitt@bbc.co.uk] Sent: Wednesday, August 26, 2015 3:16 AM To: Michael Dolan <mdolan@newtbt.com>; 'Timed Text Working Group' <public-tt@w3.org> Subject: Re: @codecs registry One way to move this along faster than TTML2 is to create a separate media registration Recommendation document for TTML and move this work there - that would require an update to the Charter and a volunteer to edit it, but since the document will hopefully be short it could be the quickest way to proceed. Kind regards, Nigel On 24/08/2015 16:54, "Michael Dolan" <mdolan@newtbt.com> wrote: >The table is a list of profile short-hand values. The values are >explicitly for use in DASH MPD for the @codecs parameter when the media >type is set to application/ttml+xml. I used "@codecs" so we remembered >why we did it :-) The table should more clearly indicate that they are >shorthand profile designators, one use of which is for DASH @codecs. > >This table is needed by the industry now for TTML1. Having explicit >enabling text in TTML 2 is good but not required in my view - >especially since the table applies equally to TTML1 profiles. The fact >that there is no explicit use of it in TTML1 syntax is not relevant as >its near term purpose is for external signaling. > >We need to find a way to move this along faster than TTML2. > >There is nothing to test as there is no supporting TTML1 document syntax. >So, I believe this table should be treated as though it were being >maintained by IANA and thus consensus of the WG and staff oversight >should suffice. > >Regards, > > Mike > >-----Original Message----- >From: Nigel Megitt [mailto:nigel.megitt@bbc.co.uk] >Sent: Monday, August 24, 2015 1:21 AM >To: David Singer <singer@apple.com> >Cc: Michael Dolan <mdolan@newtbt.com>; Timed Text Working Group ><public-tt@w3.org> >Subject: Re: @codecs registry > >We already used @profile for something very similar, so this is less >likely to be confused with that. I'm pretty sure we've been round this >loop already, but if I remember correctly the original propoasal (from >MPEG?) was to call it @codecs. > > >On 24/08/2015 09:14, "David Singer" <singer@apple.com> wrote: > >>stupid question — why is this called @codecs when it looks like profiles? >> >>> On Aug 24, 2015, at 17:07 , Nigel Megitt <nigel.megitt@bbc.co.uk> >>>wrote: >>> >>> Hi Mike, >>> >>> The current status of this is that: >>> >>> * We have in principle agreed to support the @codecs profile code >>>and registry. >>> * Glenn will put back into TTML2 ED the section on Media Type >>>Registration, including a description of the syntax etc for the >>>@codecs profile registry. >>> * The approval process for this will be the same as the process for >>>TTML2 advancement. >>> * On transition (to CR or PR or Rec? This is unclear to me), we can >>>make the registry page 'official' and then address the value set. >>> >>> There's nothing to stop us from modifying now the wiki page to >>>create entries for the profiles we expect to include. The only one I >>>would exclude from your list, for the time being, is IMSC2, since it >>>does not exist yet. >>> >>> The approval process for changes to the page is 'whatever the group >>>resolves to do by the normal consensus process'. >>> >>> Kind regards, >>> >>> Nigel >>> >>> >>> From: Michael Dolan <mdolan@newtbt.com> >>> Date: Friday, 21 August 2015 22:57 >>> To: 'Timed Text Working Group' <public-tt@w3.org> >>> Subject: @codecs registry >>> Resent-From: <public-tt@w3.org> >>> Resent-Date: Friday, 21 August 2015 22:57 >>> >>>> I was at DASH-IF meetings this week and they asked what the status >>>>was of the @codecs profile code registry: >>>> https://www.w3.org/wiki/TTML/CodecsRegistry >>>> >>>> Can we wrap this up and create entries for the profiles we know about: >>>> >>>> CFF-TT >>>> EBU-TT >>>> EBU-TT-D >>>> IMSC1 >>>> IMSC2 >>>> SDP-US >>>> >>>> Maybe give a week or two last call review for it? Is there a W3C >>>>approval process for such a thing? >>>> >>>> Regards, >>>> >>>> Mike >>>> >>>> ------------------------- >>>> Michael A DOLAN >>>> TBT, Inc. PO Box 190 >>>> Del Mar, CA 92014 >>>> (m) +1-858-882-7497 >>>> >>> >>> >>> ---------------------------- >>> >>> 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 Wednesday, 26 August 2015 13:48:21 UTC