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:
  1. Minutes - 2013-07-18 (from on 2013-07-18)
  2. TTWG Meeting Minutes Feb 28 (from on 2013-02-28)

Related notes:

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".

Monica Martin, 28 Feb 2013, 06:44:37

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

Glenn Adams, 2 May 2013, 03:40:02

change title to reflect remaining action

Glenn Adams, 2 May 2013, 03:42:48

See also Issue 156.

Glenn Adams, 2 May 2013, 03:43:59


Glenn 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/action

Glenn Adams, 11 Jul 2013, 16:11:49

Display change log.

David Singer <>, Nigel Megitt <>, Chairs, Thierry Michel <>, Philippe Le H├ęgaret <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $