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

ISSUE-109 (inconsistent handling of profile conflicts): Proposal to unify handling of profile conflicts. [DFXP 1.0]

From: Timed Text Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 22 May 2009 21:56:59 +0000 (GMT)
To: public-tt@w3.org
Message-Id: <20090522215659.1EF556B63D@kent.w3.org>

ISSUE-109 (inconsistent handling of profile conflicts): Proposal to unify handling of profile conflicts. [DFXP 1.0]

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

Raised by: Sean Hayes
On product: DFXP 1.0

The following language appears in the definition of the profile element:

"If more than one ttp:profile element appears in a TT AF document instance, then all specified profiles apply simultaneously. In such a case, if some feature or some extension is specified by one profile to be required (mandatory) and by another profile to be optional (voluntary), then that feature or extension must be considered to be required (mandatory)."

This is inconsistent (and for no obvious reason) with the case where the same element is multiply defined within a single <profile> element; where the language below applies. This requires two different types of handling in the processor where one would suffice if the handling were unified.

"for each ttp:feature and ttp:extension element descendant of the ttp:profile element, using a post-order traversal, merge the specified feature or extension with the features and extensions of the profile, where merging a feature or extension entails replacing an existing feature or extension specification, if it already exists, or adding a new feature or extension specification, if it does not yet exist in the profile;"

propose to replace the latter language with something to the effect of:

for each ttp:feature and ttp:extension element descendant of the ttp:profile element, using a post-order traversal, merge the specified feature or extension with the features and extensions of the profile, where merging a feature or extension entails adding it if it does not yet exist in the profile; or where it does exist in the profile and one designation denotes it required (mandatory) and the other optional (voluntary), then that feature or extension must be made required (mandatory) in the profile.

(the alternate would be to treat the profile elements in document order would also be acceptable)
Received on Friday, 22 May 2009 21:57:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 November 2009 22:41:42 GMT