TTML 1.0 (Editorial)
TTML 1.0 Test Suite
TTML IMSC 1.0
TTML IMSC 2.0
TTML Simple Delivery Profile for Closed Captions (US)
TTML versions and profiles note
TTML WebVTT mapping note
Frans de Jong
Loretta Guarino Reid
Philippe Le Hégaret
In Section 12.1.1 appears:
"Metadata information may be expressed by a metadata element in one of two (non-mutually exclusive) manners: (1) by specifying one or more metadata attributes on the metadata element, and (2) by specifying one or more child elements in the metadata element that express metadata. Both types of metadata are referred to in this document as metadata items."
By using "may" in this normative prose, a reader may fail to notice that this mutual exclusive usage definition has the intended force of "must" in the sense that a given metadata element MUST NOT express metadata attributes and metadata element child elements.
To make this clear, the prose should be modified to read as follows:
"A metadata element must not express metadata information by both (1) specifying one or more metadata attributes and (2) specifying one or more metadata child elements. Both types of metadata are referred to in this document as metadata items."
"Note: In other words, a metadata element may specify, in a mutually exclusive manner, either (1) metadata attributes or (2) metadata child elements, but it may not specify both forms of metadata information together."
Note also that this constraint is not expressible in either XSD or RNC schemas, and must be verified during a semantics verification phase independently from schema validity assessment.
Add notes (no markup allowed, URIs get automatically hyperlinked):
Reverted change in https://dvcs.w3.org/hg/ttml/rev/70165fde28e1. Change prose to explicitly admit both metadata attributes and metadata child elements.