ISSUE-323: Note should not use normative compliance keywords.

Note should not use normative compliance keywords.

Raised by:
Nigel Megitt
Opened on:
The (informative) note in 6.2.22 ttp:version in the current TTML2 editor's draft describes content processor behaviour using normative language ("must not"). It looks as though this is normative text so I think it needs to be moved out of the Note and therefore be unambiguously normative.
Related Actions Items:
No related actions
Related emails:
  1. {agenda} TTWG Meeting 31/7/2014 (from on 2014-07-30)
  2. {agenda} TTWG Meeting 24/7/2014 (from on 2014-07-23)
  3. {agenda} TTWG Meeting 17/7/2014 (from on 2014-07-16)
  4. {agenda} TTWG Meeting 10/7/2014 (from on 2014-07-09)
  5. ISSUE-323 (Content Processor behaviour is normative): Content Processor behaviour is normative [TTML2] (from on 2014-07-09)

Related notes:


Glenn Adams, 17 Jul 2014, 04:41:17

The edit has removed the normative conformance language however there is now a (new?) outstanding question: should processor behaviour relative to the version attribute be normative or informative. I see there's an editor's note too, to the effect that if it should be informative only the attribute should be moved to the ttm namespace. I'm not sure of which direction we should go in here - it will be for the group to resolve.

Nigel Megitt, 17 Jul 2014, 11:18:34

The original issue was fixed. The larger issue raised in your note is a subject of Issue 276.

Glenn Adams, 31 Jul 2014, 04:19:32

See Issue-276

Nigel Megitt, 31 Jul 2014, 14:55:09

Display change log ATOM feed

David Singer <>, Nigel Megitt <>, Chairs, Thierry Michel <>, Philippe Le H├ęgaret <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 323.html,v 1.1 2019/11/12 10:07:00 carcone Exp $