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

ISSUE-221 (feature designator value): Require feature designator to be defined by (some) TTML specification. [TTML 1.0]

From: Timed Text Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 27 May 2013 00:39:12 +0000
Message-Id: <E1UglSy-0005lN-Lr@crusher.w3.org>
To: public-tt@w3.org
ISSUE-221 (feature designator value): Require feature designator to be defined by (some) TTML specification. [TTML 1.0]

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

Raised by: Glenn Adams
On product: TTML 1.0

The prose in 6.1.3 para 4:

"If the URI expressed by the content of the ttp:feature element is a relative URI, then, when combined with the feature namespace value expressed by the xml:base attribute of the nearest ancestor ttp:features element, it must express an absolute URI. In either case (original absolute URI or resulting absolutized URI), the URI expressed by the ttp:feature element must further adhere to the syntax of a feature designation as defined by D.1 Feature Designations."

requires that the absolutized feature designation adhere to the "feature-designator" syntax in D.1, but does not require its value to have been previously defined in some version of TTML. Since TTML reserves all values for standardization (see D.1, quoted below), we should make clear that the actual values of feature designators must be one of the values defined in TTML 1.0 or some future revision of TTML.

"All values of feature-designation not defined by this specification are reserved for future standardization."
Received on Monday, 27 May 2013 00:39:15 UTC

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