An issue is raised for a possible erratum. The label of the issue SHOULD be set to “ErratumRaised”. It is o.k. for an erratum to have several labels. In some, exceptional, cases, i.e., when the erratum is very general, it is also acceptable not to have a reference to a document.
+
Issues labeled as “Editorial” are displayed separately, to make it easier to differentiate editorial errata from substantive ones.
+
The community discusses the issue. If it is accepted as a genuine erratum, the label “Errata” is added to the entry and the “ErratumRaised” label should be removed. Additionally, a new comment on the issue MAY be added, beginning with the word "Summary:" (if such a summary is useful based on the discussion).
+
If the community rejects the issue as an erratum, the issue should be closed.
+
Each errata may be labelled as “Editorial”; editorial errata are listed separately from the substantive ones.
+
ALL substantive errata are generally expected to have corresponding test(s) (such as a pull request in web-platform-tests), either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the erratum.
+
+
+
This report contains a reference to all open issues with the label Errata, displayed in the sections below. Each section collects the issues for a specific document, with a separate section for the issues not assigned to any.
+
+
If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Working Group, Atsushi Shimono.
+
+
Note: Following publication of IMSC 1.3 as Recommendation, this errata page has been turned into manually edited but not dynamically updated using data from GitHub.
Erratum summary:
+ The following paragraph is added to Section 4:
+ > A Feature or Extension designated as _partially supported_ is neither completely _prohibited_ nor
+ > completely _permitted_. Instead, the disposition of each of its subset _Feature_ or _Extension_ is specified
+ > individually.
+
+
+
+
"Errata to correct disposition of #bidi in IMSC 1.1"
+
Issue number:#498
+ Raised by:@palemieux
+ Extra Labels: imsc1.1
Erratum summary: The disposition of the `#bidi` feature in the _Image Profile_ is modified to:
+ _Partially supported via `#writingMode-horizontal`_
+
+
+
"Incompatible SMPTE ST 2052-1:2013 extension namespace name"
+
Issue number:#512
+ Raised by:@palemieux
+ Extra Labels: imsc1.1
+
Initial description: SMPTE ST 2052-1:2013 (SMPTE-TT) modified the extension namespace name originally defined in SMPTE ST 2052-1:2010, from `http://www.smpte-ra.org/schemas/2052-1/2010/smpte-tt` to `http://www.smpte-ra.org/schemas/2052-1/2013/smpte-tt`. [ed.: It is not clear why this change was made.]
+ IMSC 1.0.1 and IMSC 1.1 use `http://www.smpte-ra.org/schemas/2052-1/2010/smpte-tt` exclusively for the smpte:backgroundImage attribute.
+ IMSC 1.0.1 references undated SMPTE ST 2052-1.
+ IMSC 1.1 references SMPTE ST 2052-1:2013.
Erratum summary:
+ The normative reference:
+ > SMPTE ST 2052-1:2013 "Timed Text Format (SMPTE-TT)". SMPTE. URL: https://doi.org/10.5594/SMPTE.ST2052-1.2013
+ is modified to read:
+ > SMPTE ST 2052-1:2010 "Timed Text Format (SMPTE-TT)". SMPTE. URL: https://doi.org/10.5594/SMPTE.ST2052-1.2010
+
+
+
"#extent-root implies support for #extent-auto"
+
Issue number:#489
+ Raised by:@skynavga
+ Extra Labels: imsc1.1
+
Initial description: IMSC1.0 specifies that #extent-root is permitted, and #extent-root implies support for #extent-auto (see note in TTML2 §E.1.92); however, IMSC1.1 does not include #extent-auto in §6, which would mean that #extent-auto is prohibited in IMSC1.1. This makes IMSC1.1 incompatible with both IMSC1.0 and TTML2 regarding the semantics of #extent-root.
+
Erratum summary:
+ > 8.4.2 #extent-region
+ > The tts:extent attribute SHALL be present on all region elements, where it SHALL use px units, percentage values, or root container relative units.
+ is replaced with:
+ > 8.4.2 #extent-region
+ > For each region element defined in the Document Instance, the [specified value](https://www.w3.org/TR/ttml2/#semantics-style-resolved-value-category-specified) of the tts:extent style property SHALL consist of two length expressions
+ > that use pixel (px), percentage (%), or root container relative units.
+
An issue is raised for a possible erratum. The label of the issue SHOULD be set to “ErratumRaised”. It is o.k. for an erratum to have several labels. In some, exceptional, cases, i.e., when the erratum is very general, it is also acceptable not to have a reference to a document.
+
Issues labeled as “Editorial” are displayed separately, to make it easier to differentiate editorial errata from substantive ones.
+
The community discusses the issue. If it is accepted as a genuine erratum, the label “Errata” is added to the entry and the “ErratumRaised” label should be removed. Additionally, a new comment on the issue MAY be added, beginning with the word "Summary:" (if such a summary is useful based on the discussion).
+
If the community rejects the issue as an erratum, the issue should be closed.
+
Each errata may be labelled as “Editorial”; editorial errata are listed separately from the substantive ones.
+
ALL substantive errata are generally expected to have corresponding test(s) (such as a pull request in web-platform-tests), either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the erratum.
+
+
+
This report contains a reference to all open issues with the label Errata, displayed in the sections below. Each section collects the issues for a specific document, with a separate section for the issues not assigned to any.
+
+
If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Working Group, Atsushi Shimono.
+
+
Note: Following publication of IMSC 1.3 as Recommendation, this errata page has been turned into manually edited but not dynamically updated using data from GitHub.