W3C home > Mailing lists > Public > public-tt@w3.org > May 2013

RE: ISSUE-203 (ttp:version): Add ttp:version to allow author to indicate which version of TTML content was created for. [TTML.next]

From: Michael Dolan <mdolan@newtbt.com>
Date: Mon, 13 May 2013 19:07:58 -0700
To: "'Timed Text Working Group'" <public-tt@w3.org>
Message-ID: <005001ce5047$edcf77e0$c96e67a0$@newtbt.com>
OK, minimally we have to change “full”.  But until we define all the new features in TTML.next, it’s unclear about the others.

 

As I said, I don’t object. But the need for it seems to be dependent on other decisions.

 

                Mike

 

From: Glenn Adams [mailto:glenn@skynav.com] 
Sent: Monday, May 13, 2013 4:30 PM
To: Michael Dolan
Cc: Timed Text Working Group
Subject: Re: ISSUE-203 (ttp:version): Add ttp:version to allow author to indicate which version of TTML content was created for. [TTML.next]

 

 

On Mon, May 13, 2013 at 12:39 PM, Michael Dolan <mdolan@newtbt.com> wrote:

Even if we keep the old NS, we’ll have to create a new set of profiles.

 

I don't believe we *have* to. We wouldn't need to change the current dfxp-transformation or dfxp-presentation profiles, which are already too minimal to be of much use (without extensions). We would define a new dfxp-full profile, thought we might assign it a new designator, like dfxp-full-2.

 

So I'm thinking having a version would still be useful unless we introduce a new NS, and I think that might not be a good idea. We did go to the trouble of defining the existing NSs as "mutable" in order to grow them in the future without having to change NS URIs.

 

 

From: Glenn Adams [mailto:glenn@skynav.com] 
Sent: Monday, May 13, 2013 10:35 AM
To: Michael Dolan
Cc: Timed Text Working Group
Subject: Re: ISSUE-203 (ttp:version): Add ttp:version to allow author to indicate which version of TTML content was created for. [TTML.next]

 

I'm presently assuming we won't change the NS URL. If we do, then it wouldn't be needed.

 

On Mon, May 13, 2013 at 9:17 AM, Michael Dolan <mdolan@newtbt.com> wrote:

Don't we already have the tools to implicitly (but clearly) signal the version with both the namespace and the pre-defined profiles? Don't all these have to change in TTML.next? What does the version (as defined in SVG) add?

        Mike


-----Original Message-----
From: Timed Text Working Group Issue Tracker [mailto:sysbot+tracker@w3.org <mailto:sysbot%2Btracker@w3.org> ]
Sent: Sunday, May 12, 2013 1:46 PM
To: public-tt@w3.org
Subject: ISSUE-203 (ttp:version): Add ttp:version to allow author to indicate which version of TTML content was created for. [TTML.next]

ISSUE-203 (ttp:version): Add ttp:version to allow author to indicate which version of TTML content was created for. [TTML.next]

http://www.w3.org/AudioVideo/TT/tracker/issues/203

Raised by: Glenn Adams
On product: TTML.next

Add ttp:version to allow author to indicate which version of TTML content was created for. See <svg version> [1] as an analogy.

[1] http://www.w3.org/TR/SVG/struct.html#SVGElementVersionAttribute





 

 
Received on Tuesday, 14 May 2013 02:09:17 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:09 UTC