ISSUE-323: Note should not use normative compliance keywords.
Note should not use normative compliance keywords.
- State:
- CLOSED
- Product:
- TTML2
- Raised by:
- Nigel Megitt
- Opened on:
- 2014-07-09
- Description:
- 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:
- {agenda} TTWG Meeting 31/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-30)
- {agenda} TTWG Meeting 24/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-23)
- {agenda} TTWG Meeting 17/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-16)
- {agenda} TTWG Meeting 10/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-09)
- ISSUE-323 (Content Processor behaviour is normative): Content Processor behaviour is normative [TTML2] (from sysbot+tracker@w3.org on 2014-07-09)
Related notes:
Fixed. https://dvcs.w3.org/hg/ttml/rev/a3889aab0c75
Glenn Adams, 17 Jul 2014, 04:41:17The 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:34The original issue was fixed. The larger issue raised in your note is a subject of Issue 276.
Glenn Adams, 31 Jul 2014, 04:19:32See Issue-276
Nigel Megitt, 31 Jul 2014, 14:55:09Display change log