[ttml2] regenerate ED
authorGlenn Adams <glenn@skynav.com>
Wed, 18 Feb 2015 18:48:43 -0700
changeset 891 c2ba34f71022
parent 890 0351b18118cf
child 892 58d71f630f01
[ttml2] regenerate ED
ttml2/spec/ttml2.html
--- a/ttml2/spec/ttml2.html	Wed Feb 18 18:47:13 2015 -0700
+++ b/ttml2/spec/ttml2.html	Wed Feb 18 18:48:43 2015 -0700
@@ -1,6 +1,6 @@
 <!DOCTYPE html
   PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en-us"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Timed Text Markup Language 2 (TTML2)</title><style type="text/css">
+<html lang="en-us"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Timed Text Markup Language 2 (TTML2) -- (Editor's copy)</title><style type="text/css">
 code           { font-family: monospace; }
 
 div.constraint,
@@ -83,13 +83,13 @@
 .obsoleted { background-color: #f26d7d }
 .reqattr { font-weight: bold }
 .optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-WD.css"></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p>
+</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2015/02/19 01:47:13 $<div id="revisions"></div><div class="head">
 <h1><a id="title"></a>Timed Text Markup Language 2 (TTML2)</h1>
-<h2><a id="w3c-doctype"></a>W3C First Public Working Draft 12 February 2015</h2><dl><dt>This version:</dt><dd>
-<a href="http://www.w3.org/TR/2015/WD-ttml2-20150212/">http://www.w3.org/TR/2015/WD-ttml2-20150212/</a>
-</dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ttml2/">http://www.w3.org/TR/ttml2/</a></dd><dt>Latest recommendation:</dt><dd><a href="http://www.w3.org/TR/ttml1/">http://www.w3.org/TR/ttml1/</a></dd><dt>Previous version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2015/02/19 01:47:13 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<a href="ttml2.html">ttml2.html</a>
+</dd><dt>Latest version:</dt><dd><a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8">https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8</a></dd><dt>Latest recommendation:</dt><dd><a href="http://www.w3.org/TR/ttml1/">http://www.w3.org/TR/ttml1/</a></dd><dt>Previous version:</dt><dd>
 None
-</dd><dt>Editor:</dt><dd>Glenn Adams, Skynav, Inc.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Sean Hayes, Microsoft</dd><dd>Frans de Jong, European Broadcasting Union</dd><dd>Pierre-Anthony Lemieux, MovieLabs</dd><dd>Nigel Megitt, British Broadcasting Corporation</dd><dd>Dave Singer, Apple Computer</dd><dd>Jerry Smith, Microsoft</dd><dd>Andreas Tai, Invited Expert</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;2015&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>). W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
+</dd><dt>Editor:</dt><dd>Glenn Adams, Skynav, Inc.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Sean Hayes, Microsoft</dd><dd>Frans de Jong, European Broadcasting Union</dd><dd>Pierre-Anthony Lemieux, MovieLabs</dd><dd>Nigel Megitt, British Broadcasting Corporation</dd><dd>Dave Singer, Apple Computer</dd><dd>Jerry Smith, Microsoft</dd><dd>Andreas Tai, Invited Expert</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>). W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
 <h2><a id="abstract"></a>Abstract</h2><p>This document specifies the Timed Text Markup Language (TTML), Version 2, also known as TTML2,
 in terms of a vocabulary and semantics thereof.</p><p>The Timed Text Markup Language is a content type that represents
 timed text media for the purpose of interchange among authoring
@@ -100,30 +100,10 @@
 subtitling and captioning functions.</p><p>In addition to being used for interchange among legacy distribution content
 formats, TTML Content may be used directly as a distribution format,
 for example, providing a standard content format to reference from a <code>&lt;track&gt;</code>
-element in an HTML5 document, or a <code>&lt;text&gt;</code> or
+element in an HTML5 document, or a <code>&lt;text&gt;</code> or 
 <code>&lt;textstream&gt;</code> media element in a <a href="#smil3">[SMIL 3.0]</a> document.</p></div><div>
-<h2><a id="status"></a>Status of this Document</h2><p><em>This section describes the status of this document at the
-time of its publication. Other documents may supersede this document.
-A list of current W3C publications and the latest revision of this
-technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
-http://www.w3.org/TR/.</em></p><p>This is the First Public Working Draft of the Timed Text Markup Language 2 (TTML2), and is intended to be progressed to a W3C Recommendation.
-If you wish to make comments regarding this document, please send them to
-<a href="mailto:[email protected]">[email protected]</a>
-(<a href="mailto:[email protected]?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-tt/">archives</a>)
-with a subject line starting with <code>[TTML2]</code>.</p><p>This document has been produced by the <a href="http://www.w3.org/AudioVideo/TT/">Timed Text (TT) Working Group</a> as
-part of the W3C <a href="http://www.w3.org/2008/WebVideo/">Video
-in the Web Activity</a>, following the procedures set out for the W3C <a href="http://www.w3.org/Consortium/Process/">Process</a>.  The authors of this
-document are listed in the header of this document.</p><p>Publication as a First Public Working Draft does not imply endorsement by
-the W3C Membership. This is a draft document and may be updated,
-replaced or obsoleted by other documents at any time. It is
-inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
-2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/34314/status#disclosures">public list of any patent
-disclosures</a> made in connection with the deliverables of the group;
-that page also includes instructions for disclosing a patent. An
-individual who has actual knowledge of a patent which the individual
-believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
-Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
-6 of the W3C Patent Policy</a>.</p><p>This document is governed by the <a href="http://www.w3.org/2014/Process-20140801/" id="w3c_process_revision">1 August 2014 W3C Process Document</a>. </p></div><div class="toc">
+<h2><a id="status"></a>Status of this Document</h2><p><strong>This document is an editor's copy that has
+        no official standing.</strong></p><p></p></div><div class="toc">
 <h2><a id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#model">System Model</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#example">Document Example</a><br>
@@ -548,11 +528,11 @@
 K <a href="#other-references">Other References</a> (Non-Normative)<br>
 L <a href="#requirements">Requirements</a> (Non-Normative)<br>
 M <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;M.1 <a href="#d3e38064">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;M.2 <a href="#d3e38581">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;M.1 <a href="#d3e38026">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;M.2 <a href="#d3e38543">Attribute Derivation</a><br>
 N <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;N.1 <a href="#d3e39574">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;N.2 <a href="#d3e39738">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;N.1 <a href="#d3e39536">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;N.2 <a href="#d3e39700">Guidelines</a><br>
 O <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
 P <a href="#common-styling">Common Caption Style Examples</a> (Non-Normative)<br>
 &nbsp;&nbsp;&nbsp;&nbsp;P.1 <a href="#pop-on-example">Pop-On Caption Example</a><br>
@@ -570,7 +550,7 @@
 satisfied.</p><p>In addition to being used for interchange among legacy distribution content
 formats, TTML Content may be used directly as a distribution format, providing, for
 example, a standard content format to reference from a <code>&lt;track&gt;</code>
-element in an HTML5 document, or a <code>&lt;text&gt;</code> or
+element in an HTML5 document, or a <code>&lt;text&gt;</code> or 
 <code>&lt;textstream&gt;</code> media element in a <a href="#smil3">[SMIL 3.0]</a> document. Certain properties of TTML support
 streamability of content, as described in <a href="#streaming"><b>O Streaming TTML Content</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>While TTML is not expressly designed for direct (embedded) integration into an
 HTML or a SMIL document instance, such integration is not precluded.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In some contexts of use, it may be appropriate to employ
@@ -628,7 +608,7 @@
   &lt;!-- alternative using yellow text but otherwise the same as style s1 --&gt;
   &lt;style xml:id="s2" style="s1" tts:color="yellow"/&gt;
   &lt;!-- a style based on s1 but justified to the right --&gt;
-  &lt;style xml:id="s1Right" style="s1" tts:textAlign="end" /&gt;
+  &lt;style xml:id="s1Right" style="s1" tts:textAlign="end" /&gt;     
   &lt;!-- a style based on s2 but justified to the left --&gt;
   &lt;style xml:id="s2Left" style="s2" tts:textAlign="start" /&gt;
 &lt;/styling&gt;
@@ -652,7 +632,7 @@
     tts:backgroundColor="black"
     tts:displayAlign="after"
   /&gt;
-&lt;/layout&gt;
+&lt;/layout&gt;  
 </pre></div>
 </td></tr></tbody></table><p>The content of a <a href="#terms-document-instance">document instance</a> is expressed in its
 body, which is organized in terms of block and inline text elements.
@@ -705,7 +685,7 @@
     &lt;p xml:id="subtitle9b" begin="53.5s" end="58.7s" style="s2"&gt;
       How truly delightful!
     &lt;/p&gt;
-  &lt;/div&gt;
+  &lt;/div&gt;    
 &lt;/body&gt;
 </pre></div>
 </td></tr></tbody></table><p>The first subtitle <a href="#ttml-example-subtitle-1"><b>Subtitle 1 – Time Interval [0.76, 3.45)</b></a> is
@@ -767,7 +747,7 @@
 purpose of being presented (rendered). Such an <a href="#embedded-content-vocabulary-audio"><code>audio</code></a> element
 may specify the audio data inline by using a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element within
 a <a href="#embedded-content-vocabulary-source"><code>source</code></a> element child, or it may reference another
-<a href="#embedded-content-vocabulary-audio"><code>audio</code></a> element specified in a
+<a href="#embedded-content-vocabulary-audio"><code>audio</code></a> element specified in a 
 <a href="#terms-audio-defining-context">audio defining context</a>, or it may do both.</p></dd><dt class="label"><a id="terms-audio-resource"></a>[audio resource]</dt><dd><p>A <a href="#terms-data-resource">data resource</a> that contains coded or unencoded audio samples.</p></dd><dt class="label"><a id="terms-authoring-viewport"></a>[authoring viewport]</dt><dd><p>A <a href="#terms-viewport">viewport</a> employed at authoring (content encoding) time.</p></dd><dt class="label"><a id="terms-baseline-profile"></a>[baseline profile]</dt><dd><p>A <a href="#terms-profile">profile</a> referenced by the <code>use</code> attribute of a <code>ttp:profile</code> element,
 which serves as a baseline (initial) set of specifications with which to populate the referencing profile.</p></dd><dt class="label"><a id="terms-block-display"></a>[block display]</dt><dd><p>Block display is a set of layout semantics that may be applied to a <a href="#terms-content-element">content element</a> in
 certain contexts, wherein child areas are composed sequentially in the block progression direction. In <a href="#css2">[CSS2]</a>,
@@ -787,7 +767,7 @@
 purpose of semantic binding (association). Such a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element
 may specify the data inline by using a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element within
 a <a href="#embedded-content-vocabulary-source"><code>source</code></a> element child, or it may reference another
-<a href="#embedded-content-vocabulary-data"><code>data</code></a> element specified in a
+<a href="#embedded-content-vocabulary-data"><code>data</code></a> element specified in a 
 <a href="#terms-data-defining-context">data defining context</a>, or it may do both. No presentation (rendering)
 semantics are implied by the mere presence of a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element in this (or any) context.</p></dd><dt class="label"><a id="terms-data-binding-context-for-metadata"></a>[data binding context for metadata]</dt><dd><p>A <a href="#embedded-content-vocabulary-data"><code>data</code></a> element the parent of which is a
 <a href="#metadata-vocabulary-metadata"><code>metadata</code></a> element.</p></dd><dt class="label"><a id="terms-data-binding-context-for-source"></a>[data binding context for source]</dt><dd><p>A <a href="#embedded-content-vocabulary-data"><code>data</code></a> element the parent of which is a
@@ -857,7 +837,7 @@
 purpose of being presented (rendered). Such an <a href="#embedded-content-vocabulary-image"><code>image</code></a> element
 may specify the image data inline by using a <a href="#embedded-content-vocabulary-data"><code>data</code></a> element within
 a <a href="#embedded-content-vocabulary-source"><code>source</code></a> element child, or it may reference another
-<a href="#embedded-content-vocabulary-image"><code>image</code></a> element specified in a
+<a href="#embedded-content-vocabulary-image"><code>image</code></a> element specified in a 
 <a href="#terms-image-defining-context">image defining context</a>, or it may do both.</p></dd><dt class="label"><a id="terms-image-resource"></a>[image resource]</dt><dd><p>A <a href="#terms-data-resource">data resource</a> that contains a raster image.</p></dd><dt class="label"><a id="terms-implied-inline-region"></a>[implied inline region]</dt><dd><p>An anonymous (unidentified) <a href="#terms-inline-region">inline region</a> that is implied in the context of a block level
 <a href="#terms-content-element">content element</a>
 due the presence of a <a href="#style-attribute-extent"><code>tts:extent</code></a> or <a href="#style-attribute-origin"><code>tts:origin</code></a>
@@ -893,11 +873,11 @@
 an <a href="#terms-intermediate-synchronic-document">intermediate synchronic document</a>.</p></dd><dt class="label"><a id="terms-nested-profile"></a>[nested profile]</dt><dd><p>A constituent <a href="#terms-profile">profile</a> of a <a href="#terms-nesting-profile">nesting profile</a>, i.e., one of the
 descendant <code>ttp:profile</code> element(s) of a higher level (ancestor) <code>ttp:profile</code> element. A given <code>ttp:profile</code> may serve
 as both a <a href="#terms-nested-profile">nested profile</a> and a <a href="#terms-nesting-profile">nesting profile</a>.</p></dd><dt class="label"><a id="terms-nesting-profile"></a>[nesting profile]</dt><dd><p>A <a href="#terms-profile">profile</a> defined by making reference to one or more child <code>ttp:profile</code> element(s), wherein a
-profile combination method determines how profile specifications from the multiple child <code>ttp:profile</code> element(s) are combined.</p></dd><dt class="label"><a id="terms-nested-embedded-source"></a>[nested embedded source]</dt><dd><p>A <a href="#embedded-content-vocabulary-source"><code>source</code></a> element that specifies a child
+profile combination method determines how profile specifications from the multiple child <code>ttp:profile</code> element(s) are combined.</p></dd><dt class="label"><a id="terms-nested-embedded-source"></a>[nested embedded source]</dt><dd><p>A <a href="#embedded-content-vocabulary-source"><code>source</code></a> element that specifies a child 
 <a href="#embedded-content-vocabulary-data"><code>data</code></a> element which embeds the actual bytes of the
-<a href="#terms-embedded-data-resource">embedded data resource</a>, whether by
+<a href="#terms-embedded-data-resource">embedded data resource</a>, whether by 
 <a href="#terms-simple-data-embedding">simple data embedding</a> or <a href="#terms-chunked-data-embedding">chunked data embedding</a>.</p></dd><dt class="label"><a id="terms-non-content-image"></a>[non-content image]</dt><dd><p>An <a href="#terms-image-resource">image resource</a> that does not contain semantically significant content, e.g., a raster image
-representing a background design, which, if not presented, would not affect the presentation of semntically significant content.</p></dd><dt class="label"><a id="terms-non-nested-embedded-source"></a>[non-nested embedded source]</dt><dd><p>A <a href="#embedded-content-vocabulary-source"><code>source</code></a> element that specifies a child
+representing a background design, which, if not presented, would not affect the presentation of semntically significant content.</p></dd><dt class="label"><a id="terms-non-nested-embedded-source"></a>[non-nested embedded source]</dt><dd><p>A <a href="#embedded-content-vocabulary-source"><code>source</code></a> element that specifies a child 
 <a href="#embedded-content-vocabulary-data"><code>data</code></a> element which does not embed a representation of the actual bytes of the
 <a href="#terms-embedded-data-resource">embedded data resource</a>.</p></dd><dt class="label"><a id="terms-non-nesting-profile"></a>[non-nesting profile]</dt><dd><p>A <a href="#terms-profile">profile</a> defined without making reference to one or more child <code>ttp:profile</code> element(s); that is,
 by including only child <code>ttp:features</code> and <code>ttp:extensions</code> element(s).</p></dd><dt class="label"><a id="terms-out-of-line-animation"></a>[out-of-line animation]</dt><dd><p>An <a href="#animation-vocabulary-animate"><code>animate</code></a> or <a href="#animation-vocabulary-set"><code>set</code></a> element that is defined out-of-line from
@@ -1077,7 +1057,7 @@
 generic processor criteria are
 satisfied:</p><ol class="enumar"><li><p>The processor provides at least one mechanism for notionally
 instantiating a <a href="#terms-reduced-xml-infoset">reduced xml infoset</a>
-representation of a conformant <a href="#terms-document-instance">document instance</a>.</p></li><li><p>If a processor does or can perform validation of a candidate
+representation of a conformant <a href="#terms-document-instance">document instance</a>.</p></li><li><p>If a processor does or can perform validation of a candidate 
 <a href="#terms-document-instance">document instance</a>, then it provides at least one mechanism to
 implicitly or explicitly associate the
 <a href="#terms-reduced-xml-infoset">reduced xml infoset</a> representation
@@ -1313,7 +1293,7 @@
 that corresponds with a set of <a href="#semantics-profile-state-profile-specification"><span class="strong">profile specifications</span></a>,
 additionally recording the constituent
 profiles from which these specifications were obtained (or derived)</p><dl><dt class="label"><a id="semantics-profile-state-combined-profile-specification-set-constituents"></a>constituents</dt><dd><p>ordered list of absolute profile designators, where each designator denotes a constituent profile, i.e.,
-a profile from which this combined profile specification set is composed</p></dd><dt class="label"><a id="semantics-profile-state-combined-profile-specification-set-specifications"></a>specifications</dt><dd><p>ordered list of <a href="#semantics-profile-state-profile-specification"><span class="strong">profile specifications</span></a></p></dd></dl></dd><dt class="label"><a id="semantics-profile-state-empty-profile-specification-set"></a>[empty profile specification set]</dt><dd><p>a <a href="#semantics-profile-state-combined-profile-specification-set"><span class="strong">combined profile specification set</span></a> which
+a profile from which this combined profile specification set is composed</p></dd><dt class="label"><a id="semantics-profile-state-combined-profile-specification-set-specifications"></a>specifications</dt><dd><p>ordered list of <a href="#semantics-profile-state-profile-specification"><span class="strong">profile specifications</span></a></p></dd></dl></dd><dt class="label"><a id="semantics-profile-state-empty-profile-specification-set"></a>[empty profile specification set]</dt><dd><p>a <a href="#semantics-profile-state-combined-profile-specification-set"><span class="strong">combined profile specification set</span></a> which 
 <a href="#semantics-profile-state-combined-profile-specification-set-constituents"><span class="strong">constituents</span></a> and
 <a href="#semantics-profile-state-combined-profile-specification-set-specifications"><span class="strong">specifications</span></a> fields are empty sets</p></dd><dt class="label"><a id="semantics-profile-state-profile"></a>[profile]</dt><dd><p>a <a href="#semantics-profile-state-profile"><span class="strong">profile</span></a> represents the following internal state information
 that corresponds with a <a href="#profile-vocabulary-profile"><code>ttp:profile</code></a> element, whether specified explicitly or implied</p><dl><dt class="label"><a id="semantics-profile-state-profile-designator"></a>designator</dt><dd><p>an absolute profile designator that is associated with (and uniquely labels) this profile</p></dd><dt class="label"><a id="semantics-profile-state-profile-type"></a>type</dt><dd><p><code>content|processor</code></p></dd><dt class="label"><a id="semantics-profile-state-profile-combine"></a>combine</dt><dd><p><code>leastRestrictive|mostRestrictive|replace</code></p></dd><dt class="label"><a id="semantics-profile-state-profile-use"></a>use</dt><dd><p>either <code>null</code> or an absolute profile designator denoting a profile that serves as the baseline profile for this profile</p></dd><dt class="label"><a id="semantics-profile-state-profile-constituents"></a>constituents</dt><dd><p>if profile is a <a href="#terms-nesting-profile">nesting profile</a>, then an ordered list of absolute profile designators, where each designator denotes a
@@ -1356,7 +1336,7 @@
 <a href="#terms-effective-processor-profile">effective processor profile</a> is the combined profile specification set
 produced by combining the combined profile specification sets of the designated profiles, where the <code>mostRestrictive</code>
 processor profile combination method applies;</p></li><li><p>otherwise, if the <code>ttp:processorProfiles</code> attribute is specified using the <code>any(...)</code> function syntax,
-then, for each designated profile, the
+then, for each designated profile, the 
 <a href="#terms-effective-processor-profile">effective processor profile</a> is the combined profile specification set
 of the first profile in the list of designated profiles that is supported by the
 <a href="#terms-content-processor">content processor</a>;</p></li></ol></li><li><p>otherwise, if one or more <a href="#terms-top-level-profile">top-level</a> <a href="#terms-processor-profile">processor profiles</a>
@@ -1663,10 +1643,10 @@
 that used a different naming convention.</p></div></div><div class="div3">
 <h4><a id="extension-vocabulary-overview"></a>5.3.2 Extension Catalog</h4><p>The extension vocabulary catalog is intended for use by future
 profiles of TTML, and is not further defined
-by this version of this specification.</p><p>In addition to standardized extension vocabulary, a conforming
+by this version of this specification.</p><p>In addition to standardized extension vocabulary, a conforming 
 <a href="#terms-document-instance">document instance</a> may contain arbitrary namespace qualified
 elements that reside in any namespace other than those namespaces
-defined for use with this specification. Furthermore, a conforming
+defined for use with this specification. Furthermore, a conforming 
 <a href="#terms-document-instance">document instance</a> may contain arbitrary namespace qualified
 attributes on TTML defined vocabulary where such attributes reside in
 any namespace other than those defined for use with this
@@ -2493,7 +2473,7 @@
 <a href="#semantics-timing"><b>12.4 Timing Semantics</b></a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When operating with <code>smpte</code> time base and
 <code>continuous</code> marker mode, there is an implied time coordinate
 space, the <a href="#terms-synthetic-smpte-document-syncbase">synthetic smpte document syncbase</a>,
-defined by the monotonically increasing (or decreasing)
+defined by the monotonically increasing (or decreasing) 
 <a href="#smpte12m">[SMPTE 12M]</a> time coordinates, while taking into account
 the computed frame rate and drop mode. All time expressions are interpreted
 in relationship to this time coordinate space based upon
@@ -2668,7 +2648,7 @@
 media time base is outside the scope of this specification.</p></div><p>If the time base is designated as <code>smpte</code>,
 then a time expression denotes a <a href="#smpte12m">[SMPTE 12M]</a> time
 coordinate with which the content of a <a href="#terms-document-instance">document instance</a> is to
-be synchronized.  In this case, the value of the <code>ttp:markerMode</code>
+be synchronized.  In this case, the value of the <code>ttp:markerMode</code> 
 and <code>ttp:dropMode</code> parameters apply, as defined by <a href="#parameter-attribute-markerMode"><b>7.2.6 ttp:markerMode</b></a> and <a href="#parameter-attribute-dropMode"><b>7.2.3 ttp:dropMode</b></a>, respectively.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>When the time base is designated as <code>smpte</code>,
 every time expression denotes a media marker value akin to that
 defined by <a href="#smil3">[SMIL 3.0]</a>, § 5.4.3, except instead
@@ -2862,7 +2842,7 @@
 with
 a <code>div</code> element in a <a href="#terms-document-instance">document instance</a>
 are available for style inheritance by descendant <a href="#terms-content-element">content elements</a> such as
-<code>div</code>,
+<code>div</code>, 
 <code>p</code>,
 <code>span</code>, and
 <code>br</code>.</p></div><p>If a
@@ -3873,15 +3853,15 @@
 that content.</p><p>Styling attributes are included in TTML to enable authorial intent of presentation
 to be included within a self-contained document. This section describes
 the semantics of style presentation in terms of a standard processing
-model. TTML Processors are not required to present <a href="#terms-document-instance">document instances</a> in any particular way;
+model. TTML Processors are not required to present <a href="#terms-document-instance">document instances</a> in any particular way; 
 but an implementation of this model by a TTML <a href="#terms-presentation-processor">presentation processor</a>
 that provides externally observable results that are consistent with this model is
 likely to lead to a user experience that closely resembles the experience intended by
-the documents' authors.</p><p>The semantics of TTML style presentation are described in terms of the model
-in <a href="#xsl11">[XSL 1.1]</a>. The effects of the attributes in this section
+the documents' authors.</p><p>The semantics of TTML style presentation are described in terms of the model 
+in <a href="#xsl11">[XSL 1.1]</a>. The effects of the attributes in this section 
 are intended to be compatible with the layout and formatting model of XSL; however, Presentation agents
-may use any technology to satisfy the authorial intent of the document. In particular
-since <a href="#css2">[CSS2]</a> is a subset of this model, a CSS processor may be used
+may use any technology to satisfy the authorial intent of the document. In particular 
+since <a href="#css2">[CSS2]</a> is a subset of this model, a CSS processor may be used 
 for the features that the models have in common.</p><p>No normative use of an
 <code>&lt;?xml-stylesheet ... ?&gt;</code> processing instruction is defined
 by this specification.</p><div class="div2">
@@ -3986,7 +3966,7 @@
 adhere to the <code>IDREFS</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
 § 3.3.10, and, furthermore, each IDREF must reference a <code>style</code> element
 which has a <code>styling</code> element as an ancestor.</p><p>If the same IDREF, <em>ID<sub>1</sub></em>, appears more than one time in the value of a <code>style</code>
-attribute, then there should be an intervening IDREF, <em>ID<sub>2</sub></em>, where
+attribute, then there should be an intervening IDREF, <em>ID<sub>2</sub></em>, where 
 <em>ID<sub>2</sub></em> is not equal to <em>ID<sub>1</sub></em>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This constraint is intended to discourage the use of redundant referential styling while still
 allowing the same style to be referenced multiple times in order to potentially override prior
 referenced styles, e.g., when an intervening, distinct style is referenced in the IDREFS list.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>See the specific element type definitions that permit use of the
@@ -4021,7 +4001,7 @@
   How &lt;span <span class="strong">tts:backgroundColor="green"</span>&gt;I wonder&lt;/span&gt; where you're at!
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><a id="style-attribute-backgroundColor-example-1-images"></a><table class="example-images"><caption>Example Rendition – Background Color</caption><tbody><tr><td><img src="images/backgroundColor.png" alt="TTML backgroundColor style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+</td></tr></tbody></table><p></p><a id="style-attribute-backgroundColor-example-1-images"></a><table class="example-images"><caption>Example Rendition – Background Color</caption><tbody><tr><td><img src="images/backgroundColor.png" alt="TTML backgroundColor style property"></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 that defined by <a href="#xsl11">[XSL 1.1]</a>, § 7.8.2.</p></div></div><div class="div3">
 <h4><a id="style-attribute-backgroundImage"></a>10.2.3 tts:backgroundImage</h4><p>The <code>tts:backgroundImage</code> attribute is used to specify a style property that
 designates a background <a href="#terms-non-content-image">non-content image</a> to be rendered as
@@ -4073,7 +4053,7 @@
   &lt;style tts:padding="3px 40px"/&gt;
 &lt;/region&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Image Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Image Example Image</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of backgroundImage example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Image Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Image Example Image</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of backgroundImage example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 that defined by <a href="#xsl11">[XSL 1.1]</a>, § 7.8.3.</p></div></div><div class="div3">
 <h4><a id="style-attribute-backgroundPosition"></a>10.2.4 tts:backgroundPosition</h4><p>The <code>tts:backgroundPosition</code> attribute is used to specify a style property that
 defines whether and how a background image is positioned in a region or an area generated by content flowed into a region.</p><p>This attribute may be specified by any element type
@@ -4101,7 +4081,7 @@
   &lt;style <span class="strong">tts:backgroundPosition="center"</span>/&gt;
 &lt;/region&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Position Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Position Example Image</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of backgroundPosition example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Position Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Position Example Image</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of backgroundPosition example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 that defined by <a href="#css2">[CSS2]</a>, § 14.2.</p></div></div><div class="div3">
 <h4><a id="style-attribute-backgroundRepeat"></a>10.2.5 tts:backgroundRepeat</h4><p>The <code>tts:backgroundRepeat</code> attribute is used to specify a style property that
 defines whether and how a background image is repeated (tiled) into a region or an area generated by content flowed into a region.</p><p>This attribute may be specified by any element type
@@ -4127,7 +4107,7 @@
   &lt;style <span class="strong">tts:backgroundRepeat="repeatX"</span>/&gt;
 &lt;/region&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Repeat Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Repeat Example Image</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of backgroundRepeat example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Background Repeat Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Background Repeat Example Image</b></td><td align="right" valign="top">2014-11-21</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of backgroundRepeat example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 that defined by <a href="#xsl11">[XSL 1.1]</a>, § 7.8.4.</p></div></div><div class="div3">
 <h4><a id="style-attribute-border"></a>10.2.6 tts:border</h4><p>The <code>tts:border</code> attribute is used to specify a style property that
 defines the border of a region or an area generated by content flowed into a region.</p><p>This attribute may be specified by any
@@ -4172,7 +4152,7 @@
   How &lt;span <span class="strong">tts:border="8px solid blue"</span>&gt;I wonder&lt;/span&gt; where you're at!
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Border Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Border Example Image</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of border example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Border Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Border Example Image</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of border example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 that defined by <a href="#xsl11">[XSL 1.1]</a>, § 7.31.3.</p></div></div><div class="div3">
 <h4><a id="style-attribute-bpd"></a>10.2.7 tts:bpd</h4><p>The <code>tts:bpd</code> attribute is used to specify the
 <em>block progression dimension</em>, or, more succinctly, the <em>bpd</em> of an area generated by content flowed into a region.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The term <em>block progression dimension</em> is interpreted in a writing mode relative manner
@@ -4425,7 +4405,7 @@
 </td></tr><tr><td><em>Inherited:</em></td><td>no</td></tr><tr><td><em>Percentages:</em></td><td>relative to width and height of <a href="#terms-root-container-region">root container region</a></td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>If the value of this attribute consists of two <a href="#style-value-measure">&lt;measure&gt;</a>
 specifications, then they must be interpreted as <em>width</em>
 and <em>height</em>, where the first specification is the
-<em>width</em>, and the second specification is the <em>height</em>.</p><p>The <a href="#style-value-measure">&lt;measure&gt;</a> value(s) used to express extent must be non-negative.</p><p>If applied to a <a href="#terms-region">region</a> other than the <a href="#terms-root-container-region">root container region</a> and
+<em>width</em>, and the second specification is the <em>height</em>.</p><p>The <a href="#style-value-measure">&lt;measure&gt;</a> value(s) used to express extent must be non-negative.</p><p>If applied to a <a href="#terms-region">region</a> other than the <a href="#terms-root-container-region">root container region</a> and 
 the value of this attribute is <code>auto</code>, then the computed value
 of the style property must be considered to be the same as the extent of the <a href="#terms-root-container-region">root container region</a>.</p><table border="1" class="ednote" summary="Editorial note: Semantics of contain and cover"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Semantics of contain and cover</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Define semantics of new <code>contain</code> and <code>cover</code> values. Exclude these values from use with an <code>image</code> element.</td></tr></table><p>The extent of the <a href="#terms-root-container-region">root container region</a> is determined either by a
 <code>tts:extent</code> specified on the <code>tt</code> element, if
@@ -4775,7 +4755,7 @@
 </p></li><li><p>
 Set the computed value of this style property to <em>LH</em>.
 </p></li></ol><div class="note"><p class="prefix"><b>Note:</b></p><p>If a content author wishes to avoid the possibility of different interpretations of <code>normal</code>, for example, due to differences in
-the set of available fonts, then it is recommended that a
+the set of available fonts, then it is recommended that a 
 <a href="#style-value-length">&lt;length&gt;</a> value expression be used to explicitly specify line height value.</p></div><p>If specified as a <a href="#style-value-length">&lt;length&gt;</a>, then the length must
 be non-negative.</p><p>If a computed value of the property associated with this attribute is not supported,
 then a <a href="#terms-presentation-processor">presentation processor</a> must use the closest supported value.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this context, the phrase <em>closest supported value</em> means the value for which the Euclidean distance between
@@ -5069,7 +5049,7 @@
    To simper at a table-cloth!"
 &lt;/p&gt;
 </pre></div>
-</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Position Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Position Example Image</b></td><td align="right" valign="top">2014-11-28</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of position example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+</td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Position Example Image"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Position Example Image</b></td><td align="right" valign="top">2014-11-28</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert image of position example.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 the <code>background-position</code> property defined by <a href="#css3-bb">[CSS Backgrounds and Borders]</a>, § 3.6.</p></div></div><div class="div3">
 <h4><a id="style-attribute-ruby"></a>10.2.30 tts:ruby</h4><p>The <code>tts:ruby</code> attribute is used to specify the application of ruby
 styling.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
@@ -5238,7 +5218,7 @@
 represented by this attribute are based upon that defined by <a href="#cssruby">[CSS Ruby]</a>, §4.3, and the examples and example
 renderings shown there apply.</p></div></div><div class="div3">
 <h4><a id="style-attribute-rubyOffset"></a>10.2.32 tts:rubyOffset</h4><p>The <code>tts:rubyOffset</code> attribute is used to specify the offset (distance) of ruby text with respect to its associated ruby base
-in the block progression dimension.</p><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
+in the block progression dimension.</p><table border="1" class="ednote" summary="Editorial note: Auto Ruby Offset"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Auto Ruby Offset</b></td><td align="right" valign="top">2015-02-18</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add <code>auto</code> value to denote automatic offset determination. Change initial value to <code>auto</code>.</td></tr></table><p>This attribute may be specified by any element type that permits use of attributes in the TT Style Namespace; however,
 this attribute applies as a style property only to those element types indicated in the following table.</p><a id="style-property-details-rubyOffset"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <a href="#style-value-length">&lt;length&gt;</a>
 </td></tr><tr><td><em>Initial:</em></td><td><code>0px</code></td></tr><tr><td><em>Applies to:</em></td><td>
@@ -5378,7 +5358,7 @@
 span.</p><p>If the specified value of this attribute is <code>none</code>, then no combination processing applies.
 If the specified value of this attribute is <code>all</code>, then all affected characters should be combined.
 If the specified value of this attribute is <code>digits</code>, then all affected characters should be combined if they are a sequence of a digits which length is
-equal to or less than a specified count, or two (2) if no count is specified.</p><p>Combination must not cross an element boundary, a bidirectional boundary, or a non-glyph area boundary.</p><p>This attribute has no impact on or interaction with the nominal layout of glyph areas that constitute a Unicode combining character sequence.</p><table border="1" class="ednote" summary="Editorial note: Text Combine Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Combine Example</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textCombine.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+equal to or less than a specified count, or two (2) if no count is specified.</p><p>Combination must not cross an element boundary, a bidirectional boundary, or a non-glyph area boundary.</p><p>This attribute has no impact on or interaction with the nominal layout of glyph areas that constitute a Unicode combining character sequence.</p><table border="1" class="ednote" summary="Editorial note: Text Combine Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Combine Example</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textCombine.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 that defined by <a href="#css3-wm">[CSS Writing Modes]</a>, § 9.1.</p></div></div><div class="div3">
 <h4><a id="style-attribute-textDecoration"></a>10.2.37 tts:textDecoration</h4><p>The <code>tts:textDecoration</code> attribute is used to specify a style property that
 defines a text decoration effect to apply to glyph areas or other inline
@@ -5449,7 +5429,7 @@
 If no emphasis color is specified,
 then the emphasis color must be interpreted as if a color of <code>current</code> were specified.
 If no emphasis position is specified,
-then the emphasis position must be interpreted as if a position of <code>auto</code> were specified.</p><table border="1" class="ednote" summary="Editorial note: Text Emphasis Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Emphasis Example</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textEmphasis.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+then the emphasis position must be interpreted as if a position of <code>auto</code> were specified.</p><table border="1" class="ednote" summary="Editorial note: Text Emphasis Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Emphasis Example</b></td><td align="right" valign="top">2015-01-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textEmphasis.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 that defined by <a href="#css3-decoration">[CSS Text Decoration]</a>, § 3.</p></div></div><div class="div3">
 <h4><a id="style-attribute-textOrientation"></a>10.2.39 tts:textOrientation</h4><p>The <code>tts:textOrientation</code> attribute is used to specify a style property that
 defines a text orientation to apply to glyphs that are selected for glyph areas generated
@@ -5550,7 +5530,7 @@
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>relative to this element's font size</td></tr><tr><td><em>Animatable:</em></td><td>discrete, continuous</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
 each character child of a <code>p</code> element is considered to be enclosed in an anonymous
 span.</p><p>If a computed value of the property associated with this attribute is not supported,
-then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>none</code>.</p><table border="1" class="ednote" summary="Editorial note: Text Shadow Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Shadow Example</b></td><td align="right" valign="top">2015-01-08</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textShadow.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon
+then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>none</code>.</p><table border="1" class="ednote" summary="Editorial note: Text Shadow Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Shadow Example</b></td><td align="right" valign="top">2015-01-08</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of tts:textShadow.</td></tr></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The semantics of the style property represented by this attribute are based upon 
 that defined by <a href="#css3-decoration">[CSS Text Decoration]</a>, § 4.</p></div></div><div class="div3">
 <h4><a id="style-attribute-unicodeBidi"></a>10.2.42 tts:unicodeBidi</h4><p>The <code>tts:unicodeBidi</code> attribute is used to specify a style property that
 defines a directional embedding or override according to
@@ -5921,7 +5901,7 @@
 <div class="exampleInner"><pre>
 &lt;emphasis-style&gt;
   : none
-  | auto
+  | auto 
   | [ filled | open ] || [ circle | dot | sesame ]
   | <a href="#content-value-quoted-string">&lt;quoted-string&gt;</a>
 </pre></div>
@@ -6065,7 +6045,7 @@
 </pre></div>
 </td></tr></tbody></table><p>If no <em>units</em> component is specified in a &lt;length&gt; expression, then it is to be treated as
 if <code>px</code> (pixels) units were specified.</p><p>The semantics of
-the unit of measure <code>px</code> (pixel)
+the unit of measure <code>px</code> (pixel) 
 are as defined by <a href="#xsl11">[XSL 1.1]</a>, § 5.9.13.</p><div class="issue"><p class="prefix"><a id="issue-179"></a><b>Issue (issue-179):</b></p><p class="prefix"><b>Definition of Pixel</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/179">http://www.w3.org/AudioVideo/TT/tracker/issues/179</a></p><p>Replace unworkable (and unadopted) definition of pixel with an appropriate definition based on units of some viewport coordinate space.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div><p>When specified relative to a font whose size is expressed as a single length
 measure or as two length measures of equal length, the unit of measure <code>em</code> is considered to be
 identical to that defined by <a href="#xsl11">[XSL 1.1]</a>, § 5.9.13;
@@ -6591,7 +6571,7 @@
 separable. Layout matter specifies one or more spaces or areas into
 which content is intended to be presented, while style matter specifies the manner in
 which presentation occurs within the layout.</p><p>In certain cases, a content author may choose to embed (inline) style matter directly
-into layout or content matter. In such cases, an alternative
+into layout or content matter. In such cases, an alternative 
 exists – use of referential styling –
 in which the style
 matter is not embedded (inlined).</p></div><div class="div2">
@@ -6621,7 +6601,7 @@
 in the <a href="#element-vocab-group-block">Block.class</a> element group.
 In the former case, the region is referred to as an <a href="#terms-out-of-line-region">out-of-line region</a>, while in the latter
 case, it is referred to as an <a href="#terms-inline-region">inline region</a>.</p><p>In addition, and in accordance with
-<a href="#semantics-style-inheritance-region"><b>10.4.2.2 Region Style Inheritance</b></a>,
+<a href="#semantics-style-inheritance-region"><b>10.4.2.2 Region Style Inheritance</b></a>, 
 the <code>region</code> element may be used to specify inheritable style properties to be
 inherited by content that is flowed into it.</p><p>The <code>region</code> element accepts as its children zero or more
 elements in the <a href="#element-vocab-group-metadata"><code>Metadata.class</code></a> element group,
@@ -6807,7 +6787,7 @@
 <a href="#styling-vocabulary-styling"><code>styling</code></a> element, if present, and immediately before an
 <a href="#animation-vocabulary-animation"><code>animation</code></a> element, if present, or as the last child of
 the <a href="#document-structure-vocabulary-head"><code>head</code></a> element if neither are present;</p></li><li><p>append <em>R'&nbsp;</em> to the <code>[children]</code> information item property of the
-<a href="#layout-vocabulary-layout"><code>layout</code></a> element child of the
+<a href="#layout-vocabulary-layout"><code>layout</code></a> element child of the 
 <a href="#document-structure-vocabulary-head"><code>head</code></a> element;</p></li><li><p>add a <a href="#layout-attribute-region"><code>region</code></a> attribute with value <em>ID</em> to the <code>[attributes]</code> information
 item property of <em>B</em>;</p></li><li><p>remove <em>R</em> from the <code>[children]</code> information item property of <em>B</em>;</p></li></ol><div class="issue"><p class="prefix"><a id="issue-324"></a><b>Issue (issue-324):</b></p><p class="prefix"><b>Duration Restrictions</b></p><p><b>Source</b>: <a href="http://www.w3.org/AudioVideo/TT/tracker/issues/324">http://www.w3.org/AudioVideo/TT/tracker/issues/324</a></p><p>Handle case where use of <code>dur</code> is not permitted, e.g., when using discontinuous SMPTE time base.</p><p class="prefix"><b>Resolution:</b></p><p>None recorded.</p></div></dd></dl><p>The use of an <em>implied inline region specification</em> and the resulting generated inline region is shown by the following two example documents.</p><a id="semantics-inline-region-input-example-1-implied"></a><table class="example"><caption>Example – Implied Inline Region Specification</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -6866,7 +6846,7 @@
 duration of a <a href="#terms-document-instance">document instance</a> is divided into a sequence of time coordinates where at
 each time coordinate, some element becomes temporally active or inactive,
 then, at each such time coordinate, a <a href="#terms-document-instance">document instance</a> is mapped from its original, source
-form, <em>DOC<sub>source</sub></em> ,
+form, <em>DOC<sub>source</sub></em> , 
 to an intermediate
 synchronic document form,
 <em>DOC<sub>inter</sub></em> , according to the
@@ -6909,14 +6889,14 @@
 by <a href="#cea608e">[CEA-608-E]</a>, § C.3, and <a href="#ccreq">[CC-DECODER-REQ]</a>.</p></div></div><div class="div4">
 <h5><a id="semantics-region-layout-step-2"></a>11.3.1.4 Synchronic Flow Processing</h5><p>Subsequent to performing a temporal (synchronic) slice and subsequent
 remapping of regionally selected content hierarchy, the resulting intermediate
-synchronic document is subjected to a flow transformation step that produces
+synchronic document is subjected to a flow transformation step that produces 
 a rooted flow object tree represented as an XSL FO document instance as defined by <a href="#xsl11">[XSL 1.1]</a>,
 and semantically extended by TTML specific style properties that have no XSL
 FO counterpart.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In this section, the use of XSL FO is intended to be conceptual only, employed
 solely for the purpose of defining the normative presentation semantics of
 TTML. An actual implementation of this algorithm is not required to create or process
 XSL-FO representations. In particular, it is possible to implement these semantics
-using alternative presentation models, such as Cascading Style Sheets (CSS).</p></div><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>11.3.1.3 Intermediate Synchronic Document Construction</b></a> is mapped
+using alternative presentation models, such as Cascading Style Sheets (CSS).</p></div><p>Each intermediate synchronic document produced by <a href="#semantics-region-layout-step-1"><b>11.3.1.3 Intermediate Synchronic Document Construction</b></a> is mapped 
 to an XSL FO document instance, <em>F</em>, as follows:</p><ol class="enumar"><li><p>perform the following ordered sub-steps to create anonymous spans:</p><ol class="enumla"><li><p>for each significant text node in a <a href="#terms-content-element">content element</a>,
 synthesize an anonymous span to enclose the text node, substituting
 the new anonymous span for the original text node child in its sibling
@@ -6979,10 +6959,10 @@
 to the relevant formatting object produced by the input TTML <a href="#terms-content-element">content element</a> to
 which the style property applies;</p></li><li><p>optionally, synthesize a unique <code>id</code> attribute on each resulting
 formatting object element that relates that element to the input element that
-resulted in that formatting object element;</p></li></ol><p>For each resulting document instance F, if processing requires presentation on a
-visual medium, then apply formatting and rendering semantics consistent with that
-prescribed by <a href="#xsl11">[XSL 1.1]</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In an XSL FO area tree produced by formatting <em>F</em> using
-an <a href="#xsl11">[XSL 1.1]</a> formatting processor,
+resulted in that formatting object element;</p></li></ol><p>For each resulting document instance F, if processing requires presentation on a 
+visual medium, then apply formatting and rendering semantics consistent with that 
+prescribed by <a href="#xsl11">[XSL 1.1]</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>In an XSL FO area tree produced by formatting <em>F</em> using 
+an <a href="#xsl11">[XSL 1.1]</a> formatting processor, 
 the <code>page-viewport-area</code>,
 which is generated by <code>fo:page-sequence</code> element by
 reference to the sole generated <code>fo:simple-page-master</code>
@@ -7093,8 +7073,8 @@
   &lt;/head&gt;
 &lt;/tt&gt;
 </pre></div>
-</td></tr></tbody></table><p>An XSL FO document instance that would yield rendering consistent with TTML, and
-which may be produced by performing flow processing upon the first intermediate
+</td></tr></tbody></table><p>An XSL FO document instance that would yield rendering consistent with TTML, and 
+which may be produced by performing flow processing upon the first intermediate 
 document is illustrated below.</p><a id="region-mapping-example-1-f0"></a><table class="example"><caption>Example – XSL FO Document – [0s,1s)</caption><tbody><tr><td>
 <div class="exampleInner"><pre>&lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"&gt;
   &lt;fo:layout-master-set&gt;
@@ -7874,9 +7854,9 @@
   &lt;/head&gt;
   &lt;body&gt;
     &lt;div&gt;
-      ...
+      ...  
       &lt;p <span class="strong">ttm:agent="bond"</span>&gt;I travel, a sort of licensed troubleshooter.&lt;/p&gt;
-      ...
+      ...  
     &lt;/div&gt;
   &lt;/body&gt;
 &lt;/tt&gt;
@@ -8056,7 +8036,7 @@
   : <a href="#metadata-value-named-item">&lt;named-item&gt;</a>
   | <a href="http://www.w3.org/TR/xmlschema-2/#QName">xsd:QName</a>
 </pre></div>
-</td></tr></tbody></table><p>If an item name expression takes the form of a qualified name (<a href="http://www.w3.org/TR/xmlschema-2/#QName">xsd:QName</a>),
+</td></tr></tbody></table><p>If an item name expression takes the form of a qualified name (<a href="http://www.w3.org/TR/xmlschema-2/#QName">xsd:QName</a>), 
 then the prefix of that qualified name must have been declared in a namespace declaration as specified by <a href="#xmlns10">[XML Namespaces 1.0]</a>.</p><p>All values of &lt;item-name&gt; that do not take the form of qualified name (<a href="http://www.w3.org/TR/xmlschema-2/#QName">xsd:QName</a>)
 are reserved for future standardization by the W3C.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>It is intended that all item names defined by this specification are unqualified (without a prefix), whereas those defined by
 external specifications are qualified (with a prefix).</p></div></div><div class="div3">
@@ -8209,7 +8189,7 @@
   : { XML NameChar }                        // XML 1.1 Production [4a]
 </pre></div><p>All values of <code>feature-designation</code> not defined by this specification are reserved
 for future standardization.</p><p>The following sub-sections define all feature designations, expressed
-as relative URIs (fragment identifiers) with respect to the
+as relative URIs (fragment identifiers) with respect to the 
 TT Feature Namespace base URI.</p><table border="1" class="ednote" summary="Editorial note: #animation subset features"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: #animation subset features</b></td><td align="right" valign="top">2013-08-26</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add fine grained subset features of #animation.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: #inline-region features"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: #inline-region features</b></td><td align="right" valign="top">2014-03-27</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add feature(s) associated with support for explicit and implied inline regions.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: New style property features"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: New style property features</b></td><td align="right" valign="top">2014-10-02</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add features to cover new style properties: border, fontVariantPosition, ruby, rubyAlign, rubyOffset, rubyPosition, textOrientation, etc.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: New embedded content features"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: New embedded content features</b></td><td align="right" valign="top">2014-11-27</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Add features to cover new embedded content features: audio, data, font, image, etc.</td></tr></table><div class="div3">
 <h4><a id="feature-animation"></a>E.1.1 #animation</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> supports the <code>#animation</code>
 feature if it recognizes and is capable of transforming the following
@@ -8749,7 +8729,7 @@
 attribute.</p></div><div class="div3">
 <h4><a id="feature-presentation"></a>E.1.70 #presentation</h4><p>A TTML processor supports the
 <code>#presentation</code> feature if it
-(1) satisfies the generic processor criteria defined by
+(1) satisfies the generic processor criteria defined by 
 <a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a>,
 (2) implements support for the region and line layout
 semantics defined by <a href="#semantics-region-layout"><b>11.3.1 Region Layout and Presentation</b></a> and
@@ -8991,7 +8971,7 @@
 presentation semantic support for the same features and syntax
 specified above.</p></div><div class="div3">
 <h4><a id="feature-time-offset-with-ticks"></a>E.1.102 #time-offset-with-ticks</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> supports the
-<code>#time-offset-with-ticks</code> feature if it supports the
+<code>#time-offset-with-ticks</code> feature if it supports the 
 <a href="#feature-tickRate"><code>#tickRate</code></a> feature
 and if it recognizes and is capable of
 transforming all values of the <a href="#timing-value-time-expression">&lt;time-expression&gt;</a> that
@@ -9008,7 +8988,7 @@
 same vocabulary enumerated above.</p></div><div class="div3">
 <h4><a id="feature-transformation"></a>E.1.104 #transformation</h4><p>A TTML processor supports the
 <code>#transformation</code> feature if it
-(1) satisfies the generic processor criteria defined by
+(1) satisfies the generic processor criteria defined by 
 <a href="#conformance-generic-processor"><b>3.2.1 Generic Processor Conformance</b></a> and
 (2) implements the transformation semantics of the following features:</p><ul><li><p><a href="#content"><code>#content</code></a></p></li><li><p><a href="#feature-core"><code>#core</code></a></p></li><li><p><a href="#feature-profile"><code>#profile</code></a></p></li><li><p><a href="#feature-structure"><code>#structure</code></a></p></li><li><p><a href="#feature-time-offset"><code>#time-offset</code></a></p></li><li><p><a href="#timing"><code>#timing</code></a></p></li></ul></div><div class="div3">
 <h4><a id="feature-unicodeBidi"></a>E.1.105 #unicodeBidi</h4><p>A TTML <a href="#terms-transformation-processor">transformation processor</a> supports the
@@ -9773,7 +9753,7 @@
 timed element exists, then <code>referenceBegin</code> is the SMPTE time that corresponds to the active end of the
 immediate prior sibling timed element;
 <br></p></blockquote>
-</td></tr></tbody></table><p>Given the derived media time base as described above, then
+</td></tr></tbody></table><p>Given the derived media time base as described above, then 
 media time base <span class="strong"><code>M</code></span> is related to the local real time <span class="strong"><code>R</code></span>
 as described in <a href="#time-expression-semantics-media"><b>H.2 Media Time Base</b></a> above.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The begin time of the <a href="#terms-root-temporal-extent">root temporal extent</a> is related to the begin time of a
 <a href="#terms-related-media-object">related media object</a> in accordance with the computed value of the
@@ -9792,7 +9772,7 @@
 <a href="#isd-vocabulary-isd"><code>isd:isd</code></a> element as its root document element. When an instance of a
 <a href="#terms-intermediate-synchronic-document">Intermediate Synchronic Document</a> is included in a
 <a href="#terms-intermediate-synchronic-document-sequence">Intermediate Synchronic Document Sequence</a> instance, then the ISD instance is represented
-by an <a href="#isd-vocabulary-isd"><code>isd:isd</code></a> child element of the root
+by an <a href="#isd-vocabulary-isd"><code>isd:isd</code></a> child element of the root 
 <a href="#isd-vocabulary-sequence"><code>isd:sequence</code></a> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>An ISD instance may contain one or more animate elements that denote continuous animation within the associated interval. Continuously animated styles are sub-divided across
 ISD interval boundaries such that their step-wise concatenation expresses an equivalent continuous animation over any intersecting ISD interval(s).</p></div><p>A TTML <a href="#terms-intermediate-synchronic-document-sequence">Intermediate Synchronic Document Sequence</a> represents a collection
 of temporally non-overlapping <a href="#terms-intermediate-synchronic-document">Intermediate Synchronic Document</a> instances ordered according
@@ -9863,7 +9843,7 @@
 of the source TTML document from which this <a href="#isd-vocabulary-isd"><code>isd:isd</code></a> element was derived.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Expressed in the terminology of <a href="#smil3">[SMIL 3.0]</a>, the values of these <code>begin</code> and <code>end</code> attributes
 correspond to the resolved begin and end times of the <em>active duration</em> with respect to the <em>document begin</em>.</p></div><p>An <a href="#content-attribute-xml-lang"><code>xml:lang</code></a> attribute must be specified on the
 <a href="#isd-vocabulary-isd"><code>isd:isd</code></a> element if it is a standalone <a href="#terms-intermediate-synchronic-document">Intermediate
-Synchronic Document</a> document; otherwise, it may be specified, and should be specified if the default language of the
+Synchronic Document</a> document; otherwise, it may be specified, and should be specified if the default language of the 
 <a href="#isd-vocabulary-sequence"><code>isd:isd</code></a> element differs from the default language of its
 parent <a href="#isd-vocabulary-sequence"><code>isd:sequence</code></a> element.
 If its value is empty, it signifies that there is no default language that applies
@@ -9917,7 +9897,7 @@
 set of initial style values that apply to <a href="#layout-vocabulary-region"><code>region</code></a>, then a
 <code>style</code> attribute must be specified which references an <a href="#isd-vocabulary-css"><code>isd:css</code></a> element that specifies the
 region's computed style set.</p><p>The following constraints apply to the <a href="#document-structure-vocabulary-body"><code>body</code></a> element
-and its descendant elements:</p><ul><li><p>no <code>animate</code> attribute is specified;</p></li><li><p>no <code>begin</code> attribute is specified;</p></li><li><p>no <code>dur</code> attribute is specified;</p></li><li><p>no <code>end</code> attribute is specified;</p></li><li><p>no <code>region</code> attribute is specified;</p></li><li><p>no <code>timeContainer</code> attribute is specified;</p></li><li><p>no attribute in the TT Style namespace is specified;</p></li><li><p>no <a href="#animation-vocabulary-set">set</a> element is present;</p></li><li><p>no significant text node, i.e., text node in a #PCDATA context, is not contained in a
+and its descendant elements:</p><ul><li><p>no <code>animate</code> attribute is specified;</p></li><li><p>no <code>begin</code> attribute is specified;</p></li><li><p>no <code>dur</code> attribute is specified;</p></li><li><p>no <code>end</code> attribute is specified;</p></li><li><p>no <code>region</code> attribute is specified;</p></li><li><p>no <code>timeContainer</code> attribute is specified;</p></li><li><p>no attribute in the TT Style namespace is specified;</p></li><li><p>no <a href="#animation-vocabulary-set">set</a> element is present;</p></li><li><p>no significant text node, i.e., text node in a #PCDATA context, is not contained in a 
 <a href="#content-vocabulary-span"><code>span</code></a> element that contains no other child.</p></li></ul><p>In addition, for the <a href="#document-structure-vocabulary-body"><code>body</code></a> element <em>B</em> and
 each of its descendant content elements <em>C</em>, if the computed style set of <em>B</em> or each <em>C</em> is
 not equal to the computed style set of its parent element, then that element, <em>B</em> or <em>C</em>, must specify a <code>style</code>
@@ -9958,12 +9938,12 @@
 </dd><dt class="label"><a id="media-queries"></a>Media Queries</dt><dd>Florian Rivoal,,
 <a href="http://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/"><cite>Media Queries</cite></a>, W3C Recommendation, 19 June 2012. (See
 <a href="http://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/">http://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/</a>.)
-</dd><dt class="label"><a id="mime"></a>MIME</dt><dd>Ned Freed and Nathaniel Borenstein,
+</dd><dt class="label"><a id="mime"></a>MIME</dt><dd>Ned Freed and Nathaniel Borenstein,  
 <a href="http://www.rfc-editor.org/rfc/rfc2045.txt"><cite>Multipurpose Internet
 Mail Extensions (MIME) Part One: Format of Internet Message Bodies</cite></a>,
 RFC 2045, November 1996, IETF.(See
 <a href="http://www.rfc-editor.org/rfc/rfc2045.txt">http://www.rfc-editor.org/rfc/rfc2045.txt</a>.)
-</dd><dt class="label"><a id="media-types"></a>MIME Media Types</dt><dd>Ned Freed and Nathaniel Borenstein,
+</dd><dt class="label"><a id="media-types"></a>MIME Media Types</dt><dd>Ned Freed and Nathaniel Borenstein,  
 <a href="http://www.rfc-editor.org/rfc/rfc2046.txt"><cite>Multipurpose Internet
 Mail Extensions (MIME) Part Two: Media Types</cite></a>,
 RFC 2046, November 1996, IETF.(See
@@ -10128,7 +10108,7 @@
 <a href="http://www.w3.org/TR/2013/NOTE-ttml10-sdp-us-20130205/"><cite>TTML Simple Delivery Profile for Closed Captions (US)</cite></a>,
 W3C WG Note, 5 February 2013. (See
 <a href="http://www.w3.org/TR/2013/NOTE-ttml10-sdp-us-20130205/">http://www.w3.org/TR/2013/NOTE-ttml10-sdp-us-20130205/</a>.)
-</dd><dt class="label"><a id="smpte170m"></a>SMPTE 170M</dt><dd>ANSI/SMPTE 170M,
+</dd><dt class="label"><a id="smpte170m"></a>SMPTE 170M</dt><dd>ANSI/SMPTE 170M, 
 <a href="http://www.smpte.org/"><cite>Television – Composite Analog Video
 Signal – NTSC for Studio Applications</cite></a>, SMPTE Standard.
 </dd><dt class="label"><a id="smpte2052"></a>SMPTE 2052-11</dt><dd>SMPTE 2052-11,
@@ -10163,7 +10143,7 @@
 <h2><a id="derivation"></a>M Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
 vocabulary, separately describing derivation of elements and
 attributes.</p><table border="1" class="ednote" summary="Editorial note: Update Derivation"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Update Derivation</b></td><td align="right" valign="top">2015-01-14</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Update derivation tables to include new vocabulary added in TTML2.</td></tr></table><div class="div2">
-<h3><a id="d3e38064"></a>M.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table M-1 – Elements</b></a>
+<h3><a id="d3e38026"></a>M.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table M-1 – Elements</b></a>
 specifies a TTML element vocabulary item; the second column specifies the
 syntactic and/or semantic model on which the vocabulary item is based;
 the third column specifies the reference that defines
@@ -10220,7 +10200,7 @@
 and <code>@version</code> on the <code>svg:svg</code> element.</p></li><li><p>Conceptually derived from existing <code>tt:layout</code> element,
 which is a generic container for layout specifications, but for use
 in defining animation specifications that apply to targeted elements.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e38581"></a>M.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table M-2 – Attributes</b></a>
+<h3><a id="d3e38543"></a>M.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table M-2 – Attributes</b></a>
 specifies a TTML attribute vocabulary item; the second column specifies the
 syntactic and/or semantic model on which the vocabulary item is based;
 the third column specifies the reference that defines
@@ -10312,9 +10292,9 @@
 <h2><a id="qa"></a>N QA Framework Compliance (Non-Normative)</h2><p>This appendix specifies the compliance of this specification with the
 requirements and guidelines defined by <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA
 Framework Specifications Guidelines</a>&nbsp;<a href="#qaf-sg">[QAF SG]</a>.</p><div class="div2">
-<h3><a id="d3e39574"></a>N.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table N-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
+<h3><a id="d3e39536"></a>N.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table N-1 – QA Framework Requirements Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Requirement</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#include-conformance-clause-principle">Requirement 01: Include a conformance
 clause</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-scope-principle">Requirement 02: Define the scope.</a></td><td><a href="#intro">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#implement-principle">Requirement 03: Identify who or what will implement the specification.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-norm-principle">Requirement 04: Make a list of normative references.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-principle">Requirement 05: Define the terms used in the normative parts of the specification.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conf-label-principle">Requirement 06: Create conformance labels for each part of the conformance model.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#consistent-style-principle">Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#req-opt-conf-principle">Requirement 08: Indicate which conformance requirements are mandatory, which are recommended, and which are optional.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-mandatory-principle">Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdiv-constraints-principle">Requirement 10: If the technology is subdivided, then address subdivision constraints.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#likehood-extension-principle">Requirement 11: Address Extensibility.</a></td><td><a href="#doctypes">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#deprecated-feature-principle">Requirement 12: Identify deprecated features.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#degree-support-principle">Requirement 13: Define how each class of product handles each deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>1</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>No feature is deprecated by this version of this specification.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e39738"></a>N.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table N-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiling">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
+<h3><a id="d3e39700"></a>N.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table N-2 – QA Framework Guidelines Checklist</caption><col width="76%" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><col width="6%" align="center" span="1"><tbody><tr><td><span class="strong">Guideline</span></td><td><span class="strong">YES</span></td><td><span class="strong">NO</span></td><td><span class="strong">N/A</span></td><td><span class="strong">Notes</span></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-model-gp">Good Practice 01: Define the specification's conformance model in the conformance clause.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#norm-informative-gp">Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.</a></td><td><a href="#conventions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#conformance-claim-gp">Good Practice 03: Provide the wording for conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-gp">Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.</a></td><td></td><td>NO</td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ics-claim-gp">Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.</a></td><td><a href="#claims">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#use-example-gp">Good Practice 06: Provide examples, use cases, and graphics.</a></td><td><a href="#example">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-sample-gp">Good Practice 07: Write sample code or tests.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#ref-define-practice">Good Practice 08: When imposing requirements by normative references, address conformance dependencies.</a></td><td><a href="#references">YES</a></td><td></td><td></td><td>1</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-terms-inline-gp">Good Practice 09: Define unfamiliar terms in-line and consolidate the definitions in a glossary section.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#reuse-terms-gp">Good Practice 10: Use terms already defined without changing their definition.</a></td><td><a href="#definitions">YES</a></td><td></td><td></td><td>2</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#formal-language-gp">Good Practice 11: Use formal languages when possible.</a></td><td><a href="#schemas">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#write-assertion-gp">Good Practice 12: Write Test Assertions.</a></td><td></td><td>NO</td><td></td><td>3</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#subdivide-foster-gp">Good Practice 13: Create subdivisions of the technology when warranted.</a></td><td><a href="#conformance">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#rules-profiles-gp">Good Practice 14: If the technology is profiled, define rules for creating new profiles.</a></td><td><a href="#vocabulary-profiling">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#need-option-gp">Good Practice 15:Use optional features as warranted.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#label-options-gp">Good Practice 16: Clearly identify optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#constraints-gp">Good Practice 17: Indicate any limitations or constraints on optional features.</a></td><td>YES</td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#extensions-prohibited-gp">Good Practice 18: If extensibility is allowed, define an extension mechanism.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#breaking-conformance-gp">Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.</a></td><td><a href="#extension-vocabulary-overview">YES</a></td><td></td><td></td><td></td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#define-error-gp">Good Practice 20: Define error-handling for unknown extensions.</a></td><td><a href="#conformance-processor">YES</a></td><td></td><td></td><td>4</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#workaround-gp">Good Practice 21: Explain how to avoid using a deprecated feature.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#obsolete-gp">Good Practice 22: Identify obsolete features.</a></td><td></td><td></td><td>N/A</td><td>5</td></tr><tr><td><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/#error-handling-gp">Good Practice 23: Define an error handling mechanism.</a></td><td><a href="#reduced-infoset">YES</a></td><td></td><td></td><td></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><ol class="enumar"><li><p>When making normative references to external specifications,
 specific clauses or sections are cited.</p></li><li><p>See also <a href="#derivation"><b>M Vocabulary Derivation</b></a>.</p></li><li><p>Test assertions and test suites will be provided prior to entering
 Proposed Recommendation (PR) phase.</p></li><li><p>See criterion #3 in <a href="#conformance-processor"><b>3.2 Processor Conformance</b></a> and definition of
 TTML <a href="#doctypes">Abstract Document Instance</a>.</p></li><li><p>No feature is deprecated or obsoleted by this version of this specification.</p></li></ol></div></div></div><div class="div1">
@@ -10408,7 +10388,7 @@
         &lt;span begin="3s"&gt;sit&lt;/span&gt;
       &lt;/p&gt;
       &lt;p&gt;
-        &lt;span begin="4s"&gt;Amet&lt;/span&gt;
+        &lt;span begin="4s"&gt;Amet&lt;/span&gt;                
         &lt;span begin="5s"&gt;consectetur&lt;/span&gt;
         &lt;span begin="6s"&gt;adipiscing&lt;/span&gt;
         &lt;span begin="7s"&gt;elit&lt;/span&gt;
@@ -10497,4 +10477,4 @@
 and example images of style properties), Sean Hayes (advanced profile
 concepts, including applicative timing, HTML/CSS mapping proposal), Erik Hodge (timing),
 Thierry Michel (metadata), and Dave Singer (animation, scrolling).</p><p>The editor also wishes to acknowledge the support of the following current and past sponsors of his work
-on this specification: Cox Communications, Netflix, Microsoft, and Samsung Electronics.</p><p>The Working Group dedicates this specification to our colleague David Kirby.</p></div></div></body></html>
+on this specification: Cox Communications, Netflix, Microsoft, and Samsung Electronics.</p><p>The Working Group dedicates this specification to our colleague David Kirby.</p></div></div></body></html>
\ No newline at end of file