W3C home > Mailing lists > Public > public-tt@w3.org > February 2016

profile registry [was RE: {agenda} TTWG Meeting 2016-02-11]

From: Michael Dolan <mdolan@newtbt.com>
Date: Wed, 10 Feb 2016 09:12:38 -0800
To: "'W3C Public TTWG'" <public-tt@w3.org>
Message-ID: <047101d16426$3f598020$be0c8060$@newtbt.com>
Hi Thierry-

Thank you for doing the migration. Apologies for my delay in reviewing this.  It looks reasonable except for authors/editors that were added.

Although I act as a liaison to both ATSC and SMPTE from time to time, this work has nothing at all to do with SMPTE nor do I have any business relationship with SMPTE. Please back out the company addition and either delete the company field altogether or change it to my consulting corp, "TBT Inc.", whichever is more customary.

This work has been a serial collaboration starting with Glenn who wrote most of it originally. If the authors are intended to be complete, then I think Glenn should be listed.

As a reminder to all, this was drafted in response to two related needs:

1. A Request from ISO MPEG DASH that we create a short name registry to be used for DASH MPD @codecs; and

2. The WG desire to update the IANA media type registration to add an optional attribute ("codecs") that uses the short name syntax. This requires adding the standard IANA media type form (e.g.  see TTML, Appendix C [1]). 

We have completed #1, and in fact the wiki is being referenced today from DASH-IF IOP v3.2 [2]. FYI, I will inform them of our move to github for a future revision of their IOP.

We need to be rather careful at this point about changes.  I am OK with Andreas' proposal to add columns, but the other columns need to remain substantively as they were. I prefer, as Nigel proposed, that we make a new table.

We have yet to address need #2. This document was intended to be authoritative for the registry and the IANA media types registration. Due to timing I think it will also need to be authoritative for the profile shot name combinatorial syntax. So, I think we need to consider not in fact addressing issues 351 & 352 in TTML2, appendix D [3] as proposed, but consider a normative reference to this document.

I would prefer someone else maintain the document (or we all do) mostly since if all proposals fall to me to implement, progress may be slower.



[1] https://www.w3.org/TR/2013/REC-ttml1-20130924/#media-types-registration 
[2] http://dashif.org/wp-content/uploads/2015/12/DASH-IF-IOP-v3.2.pdf
[3] https://rawgit.com/w3c/ttml2/master/spec/ttml2.html?content-type=text/html;charset=utf-8#media-types-registration 

-----Original Message-----
From: Nigel Megitt [mailto:nigel.megitt@bbc.co.uk] 
Sent: Wednesday, February 10, 2016 7:05 AM
To: Thierry MICHEL <tmichel@w3.org>; W3C Public TTWG <public-tt@w3.org>
Subject: Re: {agenda} TTWG Meeting 2016-02-11

On 10/02/2016 15:01, "Thierry MICHEL" <tmichel@w3.org> wrote:

>Le 10/02/2016 12:46, Nigel Megitt a écrit :
>>>>          Timed Text Profile Registry:
>>>>          Move Info "Profile Signalling in Document" from Wiki to 
>>>>          <https://github.com/w3c/tt-profile-registry/issues/2>, Split
>>>>          Registry table up
>>>>          <https://github.com/w3c/tt-profile-registry/issues/4>
>>> I had published this draft to github. No news from Mike about it.
>>> Will Mike now update this document or should I do it ?
>> Mike has generally offered to look after this document, but has also  
>>clearly signalled that he's happy for others to make edits as needed. 
>>If  you have a change you'd like to make I suggest you go ahead and 
>>prepare a  PR for any issue you want to tackle. If there are things 
>>you'd like to fix  that are not yet documented please could you raise 
>>an issue for each thing?
>Nothing I want to personnaly change. The question was about the issue 
>raised for splitting table.

I'm sure nobody would object if you can prepare a PR for that issue!



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.
Received on Wednesday, 10 February 2016 17:13:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:43:58 UTC