ACTION-146: add prohibited value for feature definitions
add prohibited value for feature definitions
- Glenn Adams
- Due on:
- August 1, 2013
- Created on:
- February 21, 2013
- Associated Product:
- Related emails:
Glenn to get text by March 7. Discuss 2 parts - author and implications to the player.
Draft text for 2 resolutions: RESOLVED: in 1.1, add value of "prohibited" for feature definitions, also add attribute "disposition" with values "error" and "ignore" and RESOLVED: in SE, add text indicating that absence of a feature in profile means same as "optional".
The second part of this (for SE) has already been implemented in 6.1.3 with:
"If some defined (i.e., standardized) or otherwise well known feature is not specified by a ttp:feature element in a given profile, then it must be interpreted as if the feature were specified with the value attribute equal to optional."
Remarking this option for TTML.next.
change title to reflect remaining actionGlenn Adams, 2 May 2013, 03:42:48
See also Issue 156.Glenn Adams, 2 May 2013, 03:43:59
Implemented. https://dvcs.w3.org/hg/ttml/rev/8c8571a4d0b2Glenn Adams, 10 Jul 2013, 18:26:20
issue-156 now closed, so closing this action; however, "disposition" attribute not yet added, which should be the subject of a different issue/actionGlenn Adams, 11 Jul 2013, 16:11:49
Display change log.