Merge
authorpal@sandflow.org
Wed, 11 Dec 2013 15:35:35 -0500
changeset 588 3260f001b226
parent 587 0d13d60e1154 (current diff)
parent 585 f146fb61885e (diff)
child 589 30f4ccc5a12d
Merge
--- a/ttml1-api/Overview.html	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml1-api/Overview.html	Wed Dec 11 15:35:35 2013 -0500
@@ -383,7 +383,7 @@
     width:  100%;
 }
 </style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-ED"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
-<body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
+<body style="" class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
   <p>
     
       <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
@@ -391,7 +391,7 @@
   </p>
   <h1 class="title p-name" id="title" property="dcterms:title">TTML API Level 1</h1>
   
-  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-09-09T02:32:06.000Z" id="w3c-editor-s-draft-08-september-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-09-08">08 September 2013</time></h2>
+  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-11-19T15:14:00.000Z" id="w3c-editor-s-draft-19-november-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-11-19">19 November 2013</time></h2>
   <dl>
     
       <dt>This version:</dt>
@@ -429,73 +429,132 @@
         <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
         (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
         <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
-        <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.
+        <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), 
+        
+        All Rights Reserved.
+        
         <abbr title="World Wide Web Consortium">W3C</abbr> <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.
+        
+          <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
+        
+        rules apply.
       </p>
     
   
   <hr>
 </div>
-<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2>
-<p>This document defines a Level 1 API for exposing unparsed Timed Text Markup Language (TTML) content to Web Applications.</p>
-</section>
+<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2>
+<p>This document defines a Level 1 API for exposing raw Timed Text Markup Language (TTML) content to <a title="Web application" href="#dfn-web-application" class="internalDFN">Web applications</a>.</p>
+</section><section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_sotd">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 <abbr title="World Wide Web Consortium">W3C</abbr> publications and the
+          latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at
+          http://www.w3.org/TR/.</em>
+        </p>
+        
+<p><b>This document is an editor's draft that has no official standing.</b></p>
 
-<section id="sotd">
-<h2>Status of this Document</h2>
-<p><b>This document is an editor's draft that has no official standing.</b></p>
-</section>
+        <p>
+          This document was published by the <a href="http://www.w3.org/AudioVideo/TT/">Timed Text Working Group</a> as an Editor's Draft.
+          
+          
+            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>).
+          
+          
+          
+          
+            All comments are welcome.
+          
+        </p>
+        
+        
+          <p>
+            Publication as an Editor's Draft does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr>
+            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 id="sotd_patent" about="" rel="w3p:patentRules" href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent
+            Policy</a>.
+          
+          
+          
+            
+              <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/34314/status" rel="disclosure">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 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+          
+          
+        </p>
+        
+      
+    
+  
+</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#use-cases" class="tocxref"><span class="secno">2. </span>Use Cases</a><ul class="toc"><li class="tocline"><a href="#web-application-rendering-of-raw-in-band-ttml-content" class="tocxref"><span class="secno">2.1 </span>Web Application Rendering of Raw In-band TTML Content</a></li><li class="tocline"><a href="#web-application-use-of-metadata-in-raw-in-band-ttml-content" class="tocxref"><span class="secno">2.2 </span>Web Application Use of Metadata in Raw In-band TTML Content</a></li></ul></li><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">3. </span>Definitions</a><ul class="toc"><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">3.1 </span>Terminology</a></li><li class="tocline"><a href="#externals" class="tocxref"><span class="secno">3.2 </span>External Definitions</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">4. </span>Conformance</a></li><li class="tocline"><a href="#apis" class="tocxref"><span class="secno">5. </span>API Definitions</a><ul class="toc"><li class="tocline"><a href="#RawTTMLCue" class="tocxref"><span class="secno">5.1 </span>RawTTMLCue Interface</a><ul class="toc"><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">5.1.1 </span>Attributes</a></li><li class="tocline"><a href="#constructors" class="tocxref"><span class="secno">5.1.2 </span>Constructors</a></li></ul></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">A. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">A.1 </span>Normative references</a></li></ul></li></ul></section>
 
-<section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#use-cases" class="tocxref"><span class="secno">2. </span>Use Cases</a><ul class="toc"><li class="tocline"><a href="#web-application-rendering-of-unparsed-in-band-ttml-content" class="tocxref"><span class="secno">2.1 </span>Web Application Rendering of Unparsed In-band TTML Content</a></li><li class="tocline"><a href="#web-application-use-of-metadata-in-unparsed-in-band-ttml-content" class="tocxref"><span class="secno">2.2 </span>Web Application Use of Metadata in Unparsed In-band TTML Content</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">3. </span>Conformance</a></li><li class="tocline"><a href="#dependencies" class="tocxref"><span class="secno">4. </span>Dependencies</a></li><li class="tocline"><a href="#apis" class="tocxref"><span class="secno">5. </span>API Definitions</a><ul class="toc"><li class="tocline"><a href="#UnparsedTTMLCue" class="tocxref"><span class="secno">5.1 </span>UnparsedTTMLCue Interface</a><ul class="toc"><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">5.1.1 </span>Attributes</a></li><li class="tocline"><a href="#constructors" class="tocxref"><span class="secno">5.1.2 </span>Constructors</a></li></ul></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">A. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">A.1 </span>Normative references</a></li></ul></li></ul></section>
-
-<section id="introduction" typeof="bibo:Chapter" resource="#introduction" rel="bibo:chapter">
+<section id="introduction" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
 <!--OddPage--><h2 aria-level="1" role="heading" id="h2_introduction"><span class="secno">1. </span>Introduction</h2>
 <p><em>This section is non-normative.</em></p>
-<p>This document defines a Level 1 API for exposing unparsed Timed Text Markup Language (TTML) content to Web Applications. It is expected
-that a Level 2 API will be defined that builds upon this API in order to expose parsed Timed Text Markup Language (TTML) content to Web Applications.</p>
+<p>This document defines a Level 1 API for exposing raw Timed Text Markup Language (TTML) content to <a title="Web application" href="#dfn-web-application" class="internalDFN">Web applications</a>. It is expected
+that a Level 2 API will be defined that builds upon this API in order to expose parsed Timed Text Markup Language (TTML) content
+to <a title="Web application" href="#dfn-web-application" class="internalDFN">Web applications</a>.</p>
 </section>
-<section id="use-cases" typeof="bibo:Chapter" resource="#use-cases" rel="bibo:chapter">
+<section id="use-cases" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
 <!--OddPage--><h2 aria-level="1" role="heading" id="h2_use-cases"><span class="secno">2. </span>Use Cases</h2>
 <p><em>This section is non-normative.</em></p>
 <p>This section describes common use cases for the TTML API Level 1.</p>
-<section id="web-application-rendering-of-unparsed-in-band-ttml-content">
-<h3 aria-level="2" role="heading" id="h3_web-application-rendering-of-unparsed-in-band-ttml-content"><span class="secno">2.1 </span>Web Application Rendering of Unparsed In-band TTML Content</h3>
+<section id="web-application-rendering-of-raw-in-band-ttml-content">
+<h3 aria-level="2" role="heading" id="h3_web-application-rendering-of-raw-in-band-ttml-content"><span class="secno">2.1 </span>Web Application Rendering of Raw In-band TTML Content</h3>
 <p>Some <a title="user agent" href="#dfn-user-agent" class="internalDFN">HTML user agents</a> do not parse or render <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> that is embedded in a media resource and potentially exposed to
-Web Applications as a <a href="#dfn-media-resource-specific-text-track" class="internalDFN">media-resource-specific text track</a> (i.e., <em>in-band</em> text track).
-In such cases, it is possible for a Web Application to parse and render this
+<a title="Web application" href="#dfn-web-application" class="internalDFN">Web applications</a> as a <a href="#dfn-media-resource-specific-text-track" class="internalDFN">media-resource-specific text track</a> (i.e., <em>in-band</em> text track).
+In such cases, it is possible for a <a href="#dfn-web-application" class="internalDFN">Web application</a> to parse and render this
 content by making use of client-side script provided the <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> is exposed by some well defined API.</p>
 </section>
-<section id="web-application-use-of-metadata-in-unparsed-in-band-ttml-content">
-<h3 aria-level="2" role="heading" id="h3_web-application-use-of-metadata-in-unparsed-in-band-ttml-content"><span class="secno">2.2 </span>Web Application Use of Metadata in Unparsed In-band TTML Content</h3>
+<section id="web-application-use-of-metadata-in-raw-in-band-ttml-content">
+<h3 aria-level="2" role="heading" id="h3_web-application-use-of-metadata-in-raw-in-band-ttml-content"><span class="secno">2.2 </span>Web Application Use of Metadata in Raw In-band TTML Content</h3>
 <p>Authors of <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> may include a variety of arbitrary metadata that provide additional layers of information about that content. For example, the
 <a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html#metadata-attribute-agent"><code>ttp:agent</code></a> attribute may be used to specify the
 agent(s) involved in the performance (production) of content (such as '<code>James Bond</code>', '<code>Doctor No</code>', etc.), and the
 <a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html#metadata-attribute-role"><code>ttp:role</code></a> attribute may be used to
 specify the role(s) of content (such as <code>action</code>, <code>dialog</code>, <code>music</code>, etc.),
-and so forth. In such cases, it is possible for a Web Application to parse and utilize this metadata
+and so forth. In such cases, it is possible for a <a href="#dfn-web-application" class="internalDFN">Web application</a> to parse and utilize this metadata
 by making use of client-side script provided the <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> containing the metadata is exposed by some well defined API.</p>
 <p>An example of utilizing this metadata would be providing a client script generated user interface to search for <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> associated with particular
 agents or roles, or automatically provide links from content so marked to other Web content or explanatory material.</p>
 </section>
 </section>
-<section id="conformance" typeof="bibo:Chapter" resource="#conformance" rel="bibo:chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">3. </span>Conformance</h2>
-<p>
-  As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
-  and notes in this specification are non-normative. Everything else in this specification is
-  normative.
-</p>
-<p>
-  The key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>, <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em>,
-  and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
-</p>
+<section id="terminology" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<!--OddPage--><h2 aria-level="1" role="heading" id="h2_terminology"><span class="secno">3. </span>Definitions</h2>
+<section id="terminology" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_terminology"><span class="secno">3.1 </span>Terminology</h3>
+<dl>
+<dt id="terms-raw-ttml-content">[raw TTML content]</dt>
+<dd>An unparsed form of <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> suitable for representation as a string data type.</dd>
 
-<p>An <a title="user agent" href="#dfn-user-agent" class="internalDFN">HTML user agent</a> that claims to support any profile of [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], or any subsequent version thereof, must implement
-support for the TTML Level 1 API defined herein, and, if it exposes <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> to Web Applications in any fashion, then it must also expose that
-content to Web Applications using this API.</p>
+</dl>
 </section>
-<section id="dependencies" typeof="bibo:Chapter" resource="#dependencies" rel="bibo:chapter">
-<!--OddPage--><h2 aria-level="1" role="heading" id="h2_dependencies"><span class="secno">4. </span>Dependencies</h2>
+<section id="externals" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_externals"><span class="secno">3.2 </span>External Definitions</h3>
 <p>This specification relies upon the certain concepts and APIs defined in other specifications as follows:</p>
 <dl>
 <dt>DOM</dt>
@@ -510,6 +569,7 @@
 <a href="http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#media-resource-specific-text-track"><dfn id="dfn-media-resource-specific-text-track">media-resource-specific text track</dfn></a>,
 <a href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#non-interactive"><dfn id="dfn-non-interactive-browsers">non-interactive browsers</dfn></a>, and
 <a href="http://www.w3.org/html/wg/drafts/html/master/introduction.html#a-quick-introduction-to-html"><dfn id="dfn-user-agent">user agent</dfn></a>,
+<a href="http://www.w3.org/html/wg/drafts/html/master/introduction.html#background"><dfn id="dfn-web-application">Web application</dfn></a>,
 and the interface
 <a href="http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#texttrackcue"><dfn id="dfn-texttrackcue"><code>TextTrackCue</code></dfn></a>.
 [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]</dd>
@@ -523,26 +583,38 @@
 <dd>The generic semantics that apply to IDL specifications. [<cite><a class="bibref" href="#bib-WEBIDL">WEBIDL</a></cite>]</dd>
 </dl>
 </section>
-<section id="apis" typeof="bibo:Chapter" resource="#apis" rel="bibo:chapter">
+</section>
+<section id="conformance" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">4. </span>Conformance</h2>
+<p>
+  As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
+  and notes in this specification are non-normative. Everything else in this specification is
+  normative.
+</p>
+<p>
+  The key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>, <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em>,
+  and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
+</p>
+
+<p>An <a title="user agent" href="#dfn-user-agent" class="internalDFN">HTML user agent</a> that claims to support any profile of [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], or any subsequent version thereof, <em class="rfc2119" title="MUST">MUST</em> implement
+support for the TTML Level 1 API defined herein, and, if it exposes <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> to <a title="Web application" href="#dfn-web-application" class="internalDFN">Web applications</a> in any fashion,
+then it also <em class="rfc2119" title="MUST">MUST</em> expose that content to <a title="Web application" href="#dfn-web-application" class="internalDFN">Web applications</a> using this API.</p>
+<div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_1"><span>Note</span></div><p class="">The above conformance requirement is not intended to proscribe exposing <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> to a <a href="#dfn-web-application" class="internalDFN">Web application</a> using an alternative mechanism to that defined herein. That is, <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> may be exposed to a <a href="#dfn-web-application" class="internalDFN">Web application</a> in multiple ways, provided one of those ways is the mechanism defined here.</p></div>
+</section>
+<section id="apis" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
 <!--OddPage--><h2 aria-level="1" role="heading" id="h2_apis"><span class="secno">5. </span>API Definitions</h2>
-<section id="UnparsedTTMLCue" typeof="bibo:Chapter" resource="#UnparsedTTMLCue" rel="bibo:chapter">
-<h3 aria-level="2" role="heading" id="h3_UnparsedTTMLCue"><span class="secno">5.1 </span>UnparsedTTMLCue Interface</h3>
-<div class="issue"><div class="issue-title" aria-level="3" role="heading" id="h_issue_1"><span>Issue 1</span></div><p class="">If a generic <code>UnparsedCue</code> interface is added to [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>] or defined in some other <abbr title="World Wide Web Consortium">W3C</abbr> REC track specification, then
-redefine the following to inherit from that interface rather than <code>TextTrackCue</code>.</p></div>
-<div class="issue"><div class="issue-title" aria-level="3" role="heading" id="h_issue_2"><span>Issue 2</span></div><p class="">Need a better definition of <a href="#dfn-ttml-intermediate-synchronic-document" class="internalDFN">TTML intermediate synchronic document</a> than presently defined in
-[<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], which does not define a concrete syntax. It is probably best to create a new specification that formally defines such concrete syntax and
-refer to that specification, which can in turn refer to [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>].</p></div>
-<div class="issue"><div class="issue-title" aria-level="3" role="heading" id="h_issue_3"><span>Issue 3</span></div><p class="">Need to cite definitions of <em>well-formed</em> and <em>UTF-16 encoded XML serialization</em>.</p></div>
-<pre class="idl"><span class="idlInterface" id="idl-def-UnparsedTTMLCue">[<span class="extAttr">Constructor(double startTime, double endTime, DOMString text)</span>]
-interface <span class="idlInterfaceID">UnparsedTTMLCue</span> : <span class="idlSuperclass"><a href="#dfn-texttrackcue" class="internalDFN">TextTrackCue</a></span> {
-<span class="idlAttribute">                attribute <span class="idlAttrType"><a>DOMString</a></span> <span class="idlAttrName"><a href="#widl-UnparsedTTMLCue-text">text</a></span>;</span>
-};</span></pre><section id="attributes"><h4 aria-level="3" role="heading" id="h4_attributes"><span class="secno">5.1.1 </span>Attributes</h4><dl class="attributes"><dt id="widl-UnparsedTTMLCue-text"><code>text</code> of type <span class="idlAttrType"><a>DOMString</a></span>,            </dt><dd>Access text representation of cue. Upon read, returns UTF-16 encoded XML serialization of the <a href="#dfn-ttml-intermediate-synchronic-document" class="internalDFN">TTML intermediate synchronic document</a> associated with cue.
+<section id="RawTTMLCue" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_RawTTMLCue"><span class="secno">5.1 </span>RawTTMLCue Interface</h3>
+<div class="issue"><div class="issue-title" aria-level="3" role="heading" id="h_issue_1"><span>Issue 1</span></div><p class="">Need to cite definitions of <em>well-formed</em> and <em>UTF-16 encoded XML serialization</em>.</p></div>
+<pre class="idl"><span class="idlInterface" id="idl-def-RawTTMLCue">[<span class="extAttr">Constructor(double startTime, double endTime, DOMString text)</span>]
+interface <span class="idlInterfaceID">RawTTMLCue</span> : <span class="idlSuperclass"><a href="#dfn-texttrackcue" class="internalDFN">TextTrackCue</a></span> {
+<span class="idlAttribute">                attribute <span class="idlAttrType">DOMString</span> <span class="idlAttrName"><a href="#widl-RawTTMLCue-text">text</a></span>;</span>
+};</span></pre><section id="attributes"><h4 aria-level="3" role="heading" id="h4_attributes"><span class="secno">5.1.1 </span>Attributes</h4><dl class="attributes"><dt id="widl-RawTTMLCue-text"><code>text</code> of type <span class="idlAttrType">DOMString</span>,            </dt><dd>Access text representation of cue. Upon read, returns UTF-16 encoded XML serialization of the <a href="#dfn-ttml-intermediate-synchronic-document" class="internalDFN">TTML intermediate synchronic document</a> associated with cue.
 Upon write, if specified value is a well-formed UTF-16 encoded XML serialization of a <a href="#dfn-ttml-intermediate-synchronic-document" class="internalDFN">TTML intermediate synchronic document</a>, then the content of the cue is
 set to the new value; otherwise, <a href="#dfn-throw" class="internalDFN">throw</a> a <a href="#dfn-syntaxerror" class="internalDFN"><code>SyntaxError</code></a> exception.</dd></dl></section>
 <section id="constructors">
 <h4 aria-level="3" role="heading" id="h4_constructors"><span class="secno">5.1.2 </span>Constructors</h4>
 <dl class="constructors">
-<dt id="widl-UnparsedTTMLCue-UnparsedTTMLCue-double-startTime-double-endTime-DOMString-text"><code>UnparsedTTMLCue</code></dt>
+<dt id="widl-RawTTMLCue-RawTTMLCue-double-startTime-double-endTime-DOMString-text"><code>RawTTMLCue</code></dt>
 <dd>
 <table class="parameters">
 <tbody><tr>
@@ -554,7 +626,7 @@
 </tr>
 <tr>
 <td class="prmName">startTime</td>
-<td class="prmType"><code><a>double</a></code></td>
+<td class="prmType"><code>double</code></td>
 <td class="prmNullFalse">✘</td>
 <td class="prmOptFalse">✘</td>
 <td class="prmDesc">
@@ -564,7 +636,7 @@
 </tr>
 <tr>
 <td class="prmName">endTime</td>
-<td class="prmType"><code><a>double</a></code></td>
+<td class="prmType"><code>double</code></td>
 <td class="prmNullFalse">✘</td>
 <td class="prmOptFalse">✘</td>
 <td class="prmDesc">
@@ -574,7 +646,7 @@
 </tr>
 <tr>
 <td class="prmName">text</td>
-<td class="prmType"><code><a>DOMString</a></code></td>
+<td class="prmType"><code>DOMString</code></td>
 <td class="prmNullFalse">✘</td>
 <td class="prmOptFalse">✘</td>
 <td class="prmDesc">
@@ -583,7 +655,7 @@
 </tr>
 </tbody></table>
 <p>If the <code>endTime</code> parameter is less than <code>startTime</code>, then set the cue's end time to <code>startTime</code>.</p>
-<div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_1"><span>Note</span></div><p class="">The value of the <code>text</code> parameter may be an empty string, in which case the constructed cue object represents
+<div class="note"><div class="note-title" aria-level="4" role="heading" id="h_note_2"><span>Note</span></div><p class="">The value of the <code>text</code> parameter may be an empty string, in which case the constructed cue object represents
 a <dfn id="dfn-cue-with-no-content">cue with no content</dfn>.</p></div>
 </dd>
 </dl>
@@ -592,8 +664,8 @@
 </section>
 
 
-<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_references"><span class="secno">A. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter"><h3 aria-level="2" role="heading" id="h3_normative-references"><span class="secno">A.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:requires">R. Berjon et al., Eds. <a href="http://www.w3.org/html/wg/drafts/html/master/Overview.html"><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href="http://www.w3.org/html/wg/drafts/html/master/Overview.html">http://www.w3.org/html/wg/drafts/html/master/Overview.html</a>
+<section id="references" class="appendix" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_references"><span class="secno">A. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_normative-references"><span class="secno">A.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:requires">R. Berjon et al., Eds. <a href="http://www.w3.org/html/wg/drafts/html/master/Overview.html"><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href="http://www.w3.org/html/wg/drafts/html/master/Overview.html">http://www.w3.org/html/wg/drafts/html/master/Overview.html</a>
 </dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
-</dd><dt id="bib-TTML1">[TTML1]</dt><dd rel="dcterms:requires">G. Adams et al., Eds. <a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html"><cite>Timed Text Markup Language 1 (TTML1) (Second Edition)</cite></a>, W3C Editor's Draft, URL: <a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html">http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html</a>
+</dd><dt id="bib-TTML1">[TTML1]</dt><dd rel="dcterms:requires">G. Adams et al., Eds. <a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/"><cite>Timed Text Markup Language 1 (TTML1) (Second Edition)</cite></a>, W3C Recommendation, URL: <a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/">http://www.w3.org/TR/2013/REC-ttml1-20130924/</a>
 </dd><dt id="bib-WEBIDL">[WEBIDL]</dt><dd rel="dcterms:requires">C. McCormack et al., Eds. <a href="http://dev.w3.org/2006/webapi/WebIDL/"><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href="http://dev.w3.org/2006/webapi/WebIDL/">http://dev.w3.org/2006/webapi/WebIDL/</a>
 </dd></dl></section></section></body></html>
\ No newline at end of file
--- a/ttml1-api/Overview.src.html	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml1-api/Overview.src.html	Wed Dec 11 15:35:35 2013 -0500
@@ -15,9 +15,6 @@
     // use respec source as current ED uri
     edDraftURI: "http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html",
 
-    // if you want to have extra CSS, append them to this list
-    extraCSS: [],
-
     // editors, add as many as you like
     // only "name" is required
     editors:  [
@@ -45,7 +42,7 @@
 
     localBiblio: {
       "HTML5" : "R. Berjon et al., Eds. <a href='http://www.w3.org/html/wg/drafts/html/master/Overview.html'><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href='http://www.w3.org/html/wg/drafts/html/master/Overview.html'>http://www.w3.org/html/wg/drafts/html/master/Overview.html</a>",
-      "TTML1" : "G. Adams et al., Eds. <a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html'><cite>Timed Text Markup Language 1 (TTML1) (Second Edition)</cite></a>, W3C Editor's Draft, URL: <a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html'>http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html</a>",
+      "TTML1" : "G. Adams et al., Eds. <a href='http://www.w3.org/TR/2013/REC-ttml1-20130924/'><cite>Timed Text Markup Language 1 (TTML1) (Second Edition)</cite></a>, W3C Recommendation, URL: <a href='http://www.w3.org/TR/2013/REC-ttml1-20130924/'>http://www.w3.org/TR/2013/REC-ttml1-20130924/</a>",
       "WEBIDL" : "C. McCormack et al., Eds. <a href='http://dev.w3.org/2006/webapi/WebIDL/'><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href='http://dev.w3.org/2006/webapi/WebIDL/'>http://dev.w3.org/2006/webapi/WebIDL/</a>",
     },
 
@@ -155,12 +152,6 @@
 <h2>API Definitions</h2>
 <section id='RawTTMLCue'>
 <h2>RawTTMLCue Interface</h2>
-<p class='issue'>If a generic <code>GenericCue</code> interface is added to [[!HTML5]] or defined in some other W3C REC track specification, and
-that interface is appropriate for exposing raw cue content (in a text form), then
-redefine the following to inherit from that interface rather than <code>TextTrackCue</code>.</p>
-<p class='issue'>Need a better definition of <a>TTML intermediate synchronic document</a> than presently defined in
-[[!TTML1]], which does not define a concrete syntax. It is probably best to create a new specification that formally defines such concrete syntax and
-refer to that specification, which can in turn refer to [[!TTML1]].</p>
 <p class='issue'>Need to cite definitions of <em>well-formed</em> and <em>UTF-16 encoded XML serialization</em>.</p>
 <dl class='idl' title='[Constructor(double startTime, double endTime, DOMString text)] interface RawTTMLCue : TextTrackCue'>
 <dt>attribute DOMString text</dt>
--- a/ttml1/spec/ttml1-errata.html	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml1/spec/ttml1-errata.html	Wed Dec 11 15:35:35 2013 -0500
@@ -7,6 +7,7 @@
 </head>
 <body>
 <h1>Errata for Timed Text Markup Language 1 (TTML1); W3C REC, 24 September 2013</h1>
-<p><em>No errata defined at this time.</em></p>
+<h2>Section 5.2 - Profiles</h2>
+<p>In the third paragraph under Table 2, change "... and must not be appear ..." to read "... and must not appear ...".</p>
 </body>
 </html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml2-api/Overview.html	Wed Dec 11 15:35:35 2013 -0500
@@ -0,0 +1,666 @@
+<!DOCTYPE html>
+<html lang="en" dir="ltr" typeof="bibo:Document " about="" property="dcterms:language" content="en">
+<head>
+<meta charset="utf-8">
+<title>TTML API Level 2</title>
+
+
+<style>/*****************************************************************
+ * ReSpec 3 CSS
+ * Robin Berjon - http://berjon.com/
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 { 
+    text-transform:     lowercase;
+    font-variant:       small-caps;
+    font-style:         normal;
+    color:              #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+    border: none;
+}
+
+dfn {
+    font-weight:    bold;
+}
+
+a.internalDFN {
+    color:  inherit;
+    border-bottom:  1px solid #99c;
+    text-decoration:    none;
+}
+
+a.externalDFN {
+    color:  inherit;
+    border-bottom:  1px dotted #ccc;
+    text-decoration:    none;
+}
+
+a.bibref {
+    text-decoration:    none;
+}
+
+cite .bibref {
+    font-style: normal;
+}
+
+code {
+    color:  #ff4500;
+}
+
+/* --- TOC --- */
+.toc a, .tof a {
+    text-decoration:    none;
+}
+
+a .secno, a .figno {
+    color:  #000;
+}
+
+ul.tof, ol.tof {
+    list-style: none outside none;
+}
+
+.caption {
+    margin-top: 0.5em;
+    font-style:   italic;
+}
+
+/* --- TABLE --- */
+table.simple {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    border-bottom:  3px solid #005a9c;
+}
+
+.simple th {
+    background: #005a9c;
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+}
+
+.simple th[scope="row"] {
+    background: inherit;
+    color:  inherit;
+    border-top: 1px solid #ddd;
+}
+
+.simple td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+    background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+    margin-top: 0;
+}
+
+.section dd > p:last-child {
+    margin-bottom: 0;
+}
+
+.section dd {
+    margin-bottom:  1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+    margin-bottom:  0;
+}
+</style><style>/* --- WEB IDL --- */
+pre.idl {
+    border-top: 1px solid #90b8de;
+    border-bottom: 1px solid #90b8de;
+    padding:    1em;
+    line-height:    120%;
+}
+
+pre.idl::before {
+    content:    "WebIDL";
+    display:    block;
+    width:      150px;
+    background: #90b8de;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.idlType {
+    color:  #ff4500;
+    font-weight:    bold;
+    text-decoration:    none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID, .idlCallbackID, .idlEnumID {
+    font-weight:    bold;
+    color:  #005a9c;
+}
+a.idlEnumItem {
+    color:  #000;
+    border-bottom:  1px dotted #ccc;
+    text-decoration: none;
+}
+
+.idlSuperclass {
+    font-style: italic;
+    color:  #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+    color:  #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+    color:  #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType, .idlCallbackType {
+    color:  #005a9c;
+}
+.idlMethName {
+    color:  #ff4500;
+}
+.idlMethName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlCtor*/
+.idlCtorName {
+    color:  #ff4500;
+}
+.idlCtorName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+    color:  #005a9c;
+}
+.idlParamName, .idlDefaultValue {
+    font-style: italic;
+}
+
+.extAttr {
+    color:  #666;
+}
+
+/*.idlSectionComment*/
+.idlSectionComment {
+    color: gray;
+}
+
+/*.idlConst*/
+.idlConstType {
+    color:  #005a9c;
+}
+.idlConstName {
+    color:  #ff4500;
+}
+.idlConstName a {
+    color:  #ff4500;
+    border-bottom:  1px dotted #ff4500;
+    text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+    font-weight:    bold;
+    color:  #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+    color:  #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+    color:  #c00;
+    font-weight:    normal;
+}
+
+.excName a {
+    font-family:    monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+    border-bottom:  1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+    width:  45px;
+    text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color:  #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color:  #c00; }
+
+.idlImplements a {
+    font-weight:    bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.constructors, dl.fields, dl.dictionary-members {
+    margin-left:    2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .constructors dt, .fields dt, .dictionary-members dt {
+    font-weight:    normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .constructors dt code, .fields dt code, .dictionary-members dt code {
+    font-weight:    bold;
+    color:  #000;
+    font-family:    monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+    background:  #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+    color:  #005a9c;
+    background:  transparent;
+    font-family:    inherit;
+    font-weight:    normal;
+    font-style: italic;
+}
+
+.methods dt code {
+    background:  #d9e6f8;
+}
+
+.constants dt code {
+    background:  #ddffd2;
+}
+
+.constructors dt code {
+    background:  #cfc;
+}
+
+.attributes dd, .methods dd, .constants dd, .constructors dd, .fields dd, .dictionary-members dd {
+    margin-bottom:  1em;
+}
+
+table.parameters, table.exceptions {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    margin: 0.5em 0;
+    width:  100%;
+}
+table.parameters { border-bottom:  1px solid #90b8de; }
+table.exceptions { border-bottom:  1px solid #deb890; }
+
+.parameters th, .exceptions th {
+    color:  #fff;
+    padding:    3px 5px;
+    text-align: left;
+    font-family:    initial;
+    font-weight:    normal;
+    text-shadow:    #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+    padding:    3px 10px;
+    border-top: 1px solid #ddd;
+    vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+    border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+    width:  100px;
+}
+
+.parameters td.prmType {
+    width:  120px;
+}
+
+table.exceptions table {
+    border-spacing: 0;
+    border-collapse:    collapse;
+    width:  100%;
+}
+</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-ED"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+<body style="" class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
+  <p>
+    
+      <a href="http://www.w3.org/"><img width="72" height="48" src="https://www.w3.org/Icons/w3c_home" alt="W3C"></a>
+    
+  </p>
+  <h1 class="title p-name" id="title" property="dcterms:title">TTML API Level 2</h1>
+  
+  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-11-19T15:15:48.000Z" id="w3c-editor-s-draft-19-november-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2013-11-19">19 November 2013</time></h2>
+  <dl>
+    
+      <dt>This version:</dt>
+      <dd><a class="u-url" href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2-api/Overview.html">http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2-api/Overview.html</a></dd>
+      <dt>Latest published version:</dt>
+      <dd><a href="http://www.w3.org/TR/ttml2-api/">http://www.w3.org/TR/ttml2-api/</a></dd>
+    
+    
+      <dt>Latest editor's draft:</dt>
+      <dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2-api/Overview.html">http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2-api/Overview.html</a></dd>
+    
+    
+    
+    
+      
+    
+    
+    
+    <dt>Editor:</dt>
+    <dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><span property="foaf:name" class="p-name fn">Glenn Adams</span>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.cox.com/">Cox Communications, Inc.</a></span>
+</dd>
+
+    
+    
+  </dl>
+  
+  
+  
+  
+    
+      <p class="copyright">
+        <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
+        2013
+        
+        <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
+        (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
+        <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
+        <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), 
+        
+        All Rights Reserved.
+        
+        <abbr title="World Wide Web Consortium">W3C</abbr> <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>
+    
+  
+  <hr>
+</div>
+<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_abstract">Abstract</h2>
+<p>This document defines a Level 2 API for exposing parsed and formatted Timed Text Markup Language (TTML) content to Web Applications.</p>
+</section><section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h2 aria-level="1" role="heading" id="h2_sotd">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 <abbr title="World Wide Web Consortium">W3C</abbr> publications and the
+          latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at
+          http://www.w3.org/TR/.</em>
+        </p>
+        
+<p><b>This document is an editor's draft that has no official standing.</b></p>
+
+        <p>
+          This document was published by the <a href="http://www.w3.org/AudioVideo/TT/">Timed Text Working Group</a> as an Editor's Draft.
+          
+          
+            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>).
+          
+          
+          
+          
+            All comments are welcome.
+          
+        </p>
+        
+        
+          <p>
+            Publication as an Editor's Draft does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr>
+            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 id="sotd_patent" about="" rel="w3p:patentRules" href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <abbr title="World Wide Web Consortium">W3C</abbr> Patent
+            Policy</a>.
+          
+          
+          
+            
+              <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a href="http://www.w3.org/2004/01/pp-impl/34314/status" rel="disclosure">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 <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
+          
+          
+        </p>
+        
+      
+    
+  
+</section><section id="toc"><h2 class="introductory" aria-level="1" role="heading" id="h2_toc">Table of Contents</h2><ul class="toc" role="directory" id="respecContents"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#use-cases" class="tocxref"><span class="secno">2. </span>Use Cases</a><ul class="toc"><li class="tocline"><a href="#user-agent-rendering-of-parsed-ttml-content" class="tocxref"><span class="secno">2.1 </span>User Agent Rendering of Parsed TTML Content</a></li><li class="tocline"><a href="#web-application-rendering-of-parsed-ttml-content" class="tocxref"><span class="secno">2.2 </span>Web Application Rendering of Parsed TTML Content</a></li><li class="tocline"><a href="#web-application-use-of-parsed-ttml-content-metadata" class="tocxref"><span class="secno">2.3 </span>Web Application Use of Parsed TTML Content Metadata</a></li></ul></li><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">3. </span>Definitions</a><ul class="toc"><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">3.1 </span>Terminology</a></li><li class="tocline"><a href="#externals" class="tocxref"><span class="secno">3.2 </span>External Definitions</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">4. </span>Conformance</a></li><li class="tocline"><a href="#dependencies" class="tocxref"><span class="secno">5. </span>Dependencies</a></li><li class="tocline"><a href="#apis" class="tocxref"><span class="secno">6. </span>API Definitions</a><ul class="toc"><li class="tocline"><a href="#TTMLCue" class="tocxref"><span class="secno">6.1 </span>TTMLCue Interface</a><ul class="toc"><li class="tocline"><a href="#attributes" class="tocxref"><span class="secno">6.1.1 </span>Attributes</a></li><li class="tocline"><a href="#methods" class="tocxref"><span class="secno">6.1.2 </span>Methods</a></li><li class="tocline"><a href="#constructors" class="tocxref"><span class="secno">6.1.3 </span>Constructors</a></li></ul></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">A. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">A.1 </span>Normative references</a></li></ul></li></ul></section>
+
+<section id="introduction" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<!--OddPage--><h2 aria-level="1" role="heading" id="h2_introduction"><span class="secno">1. </span>Introduction</h2>
+<p><em>This section is non-normative.</em></p>
+<p>This document defines a Level 2 API for exposing parsed and formatted Timed Text Markup Language (TTML) content to Web Applications. The parsed form
+of TTML is exposed as a DOM representation of a <a href="#dfn-ttml-intermediate-synchronic-document" class="internalDFN">TTML intermediate synchronic document</a>. The formatted form of TTML is exposed as an HTML document
+fragment that encodes a renderable representation of the parsed form.</p>
+</section>
+<section id="use-cases" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<!--OddPage--><h2 aria-level="1" role="heading" id="h2_use-cases"><span class="secno">2. </span>Use Cases</h2>
+<p><em>This section is non-normative.</em></p>
+<p>This section describes common use cases for the TTML API Level 2.</p>
+<section id="user-agent-rendering-of-parsed-ttml-content">
+<h3 aria-level="2" role="heading" id="h3_user-agent-rendering-of-parsed-ttml-content"><span class="secno">2.1 </span>User Agent Rendering of Parsed TTML Content</h3>
+<p>When a <a href="#dfn-text-track" class="internalDFN">text track</a> is in the <a href="#dfn-showing-mode" class="internalDFN">showing mode</a> and the <a href="#dfn-text-track-s-list-of-cues" class="internalDFN">text track's list of cues</a> includes an instance of <a href="#idl-def-TTMLCue" class="idlType"><code>TTMLCue</code></a>,
+then a <a href="#dfn-user-agent" class="internalDFN">user agent</a> attempts to render the cue using the HTML document fragment associated with the cue.</p>
+</section>
+<section id="web-application-rendering-of-parsed-ttml-content">
+<h3 aria-level="2" role="heading" id="h3_web-application-rendering-of-parsed-ttml-content"><span class="secno">2.2 </span>Web Application Rendering of Parsed TTML Content</h3>
+<p>When a <a href="#dfn-text-track" class="internalDFN">text track</a> is not in the <a href="#dfn-showing-mode" class="internalDFN">showing mode</a> and the <a href="#dfn-text-track-s-list-of-cues" class="internalDFN">text track's list of cues</a> includes an instance of <a href="#idl-def-TTMLCue" class="idlType"><code>TTMLCue</code></a>,
+then a Web Application may render the cue, for example, by making direct use of the cue's parsed form or by using the cue's formatted HTML form.</p>
+</section>
+<section id="web-application-use-of-parsed-ttml-content-metadata">
+<h3 aria-level="2" role="heading" id="h3_web-application-use-of-parsed-ttml-content-metadata"><span class="secno">2.3 </span>Web Application Use of Parsed TTML Content Metadata</h3>
+<p>When a <a href="#dfn-text-track" class="internalDFN">text track</a> is not in the <a href="#dfn-showing-mode" class="internalDFN">showing mode</a> and the <a href="#dfn-text-track-s-list-of-cues" class="internalDFN">text track's list of cues</a> includes an instance of <a href="#idl-def-TTMLCue" class="idlType"><code>TTMLCue</code></a>,
+then a Web Application may access parsed TTML metadata contained in the TTML DOM representation exposed by the cue.</p>
+</section>
+</section>
+<section id="terminology" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<!--OddPage--><h2 aria-level="1" role="heading" id="h2_terminology"><span class="secno">3. </span>Definitions</h2>
+<section id="terminology" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_terminology"><span class="secno">3.1 </span>Terminology</h3>
+<dl>
+<dt>[TBS]</dt>
+<dd>To Be Supplied.</dd>
+
+</dl>
+</section>
+<section id="externals" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_externals"><span class="secno">3.2 </span>External Definitions</h3>
+<p>This specification relies upon the certain concepts and APIs defined in other specifications as follows:</p>
+<dl>
+<dt>DOM</dt>
+<dd>The concepts
+<a href="http://dom.spec.whatwg.org#concept-throw"><dfn id="dfn-throw">throw</dfn></a>, and
+<a href="http://dom.spec.whatwg.org#xml-document"><dfn id="dfn-xml-document">XML document</dfn></a>,
+the interfaces
+<a href="http://dom.spec.whatwg.org#document"><dfn id="dfn-document"><code>Document</code></dfn></a>,
+<a href="http://dom.spec.whatwg.org#documentfragment"><dfn id="dfn-documentfragment"><code>DocumentFragment</code></dfn></a>, and
+<a href="http://dom.spec.whatwg.org#element"><dfn id="dfn-element"><code>Element</code></dfn></a>, and
+and the exception
+<a href="http://dom.spec.whatwg.org#syntaxerror"><dfn id="dfn-syntaxerror"><code>SyntaxError</code></dfn></a>.
+[<cite><a class="bibref" href="#bib-DOM4">DOM4</a></cite>]</dd>
+<dt>HTML</dt>
+<dd>The concepts
+<a href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#interactive"><dfn id="dfn-interactive-browsers">interactive browsers</dfn></a>,
+<a href="http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#media-resource-specific-text-track"><dfn id="dfn-media-resource-specific-text-track">media-resource-specific text track</dfn></a>,
+<a href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#non-interactive"><dfn id="dfn-non-interactive-browsers">non-interactive browsers</dfn></a>, and
+<a href="http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#structured-clone"><dfn id="dfn-structured-clone">structured clone</dfn></a>,
+<a href="http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#showing-0"><dfn id="dfn-showing-mode">showing mode</dfn></a>,
+<a href="http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#text-track-model"><dfn id="dfn-text-track">text track</dfn></a>,
+<a href="http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#text-track-model"><dfn id="dfn-text-track-s-list-of-cues">text track's list of cues</dfn></a>, and
+<a href="http://www.w3.org/html/wg/drafts/html/master/introduction.html#a-quick-introduction-to-html"><dfn id="dfn-user-agent">user agent</dfn></a>,
+and the interfaces
+<a href="http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#texttrack"><dfn id="dfn-texttrack"><code>TextTrack</code></dfn></a> and
+<a href="http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#texttrackcue"><dfn id="dfn-texttrackcue"><code>TextTrackCue</code></dfn></a>.
+[<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>]</dd>
+<dt>TTML</dt>
+<dd>The concepts
+<a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html#ttml-content-doctype"><dfn id="dfn-ttml-content">TTML content</dfn></a>,
+<a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html#semantics-region-layout-step-2"><dfn id="dfn-ttml-intermediate-synchronic-document">TTML intermediate synchronic document</dfn></a>, and
+<a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html#time-expression-semantics-media"><dfn id="dfn-ttml-media-time">TTML media time</dfn></a>.
+[<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>]</dd>
+<dt>TTML API Level 1</dt>
+<dd>The interface
+<a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html#RawTTMLCue"><dfn id="dfn-rawttmlcue"><code>RawTTMLCue</code></dfn></a>.
+[<cite><a class="bibref" href="#bib-TTML1API">TTML1API</a></cite>]</dd>
+<dt>WebIDL</dt>
+<dd>The generic semantics that apply to IDL specifications. [<cite><a class="bibref" href="#bib-WEBIDL">WEBIDL</a></cite>]</dd>
+</dl>
+</section>
+</section>
+<section id="conformance" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_conformance"><span class="secno">4. </span>Conformance</h2>
+<p>
+  As well as sections marked as non-normative, all authoring guidelines, diagrams, examples,
+  and notes in this specification are non-normative. Everything else in this specification is
+  normative.
+</p>
+<p>
+  The key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>, <em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em>,
+  and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification are to be interpreted as described in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].
+</p>
+
+<p>An <a title="user agent" href="#dfn-user-agent" class="internalDFN">HTML user agent</a> that claims to support the rendering of any profile of [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>] or claims to support any profile of [<cite><a class="bibref" href="#bib-TTML2">TTML2</a></cite>],
+or any subsequent version thereof, <em class="rfc2119" title="MUST">MUST</em> implement
+support for the TTML Level 2 API defined herein, and, if it renders <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> in any fashion or exposes <a href="#dfn-ttml-content" class="internalDFN">TTML content</a> to Web Applications in any fashion,
+then it also <em class="rfc2119" title="MUST">MUST</em> render or expose that content to Web Applications using this API.</p>
+</section>
+<section id="dependencies" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<!--OddPage--><h2 aria-level="1" role="heading" id="h2_dependencies"><span class="secno">5. </span>Dependencies</h2>
+</section>
+<section id="apis" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<!--OddPage--><h2 aria-level="1" role="heading" id="h2_apis"><span class="secno">6. </span>API Definitions</h2>
+<section id="TTMLCue" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter">
+<h3 aria-level="2" role="heading" id="h3_TTMLCue"><span class="secno">6.1 </span>TTMLCue Interface</h3>
+<pre class="idl"><span class="idlInterface" id="idl-def-TTMLCue">[<span class="extAttr">Constructor(double startTime, double endTime, Document? content)</span>]
+interface <span class="idlInterfaceID">TTMLCue</span> : <span class="idlSuperclass"><a href="#dfn-rawttmlcue" class="internalDFN">RawTTMLCue</a></span> {
+<span class="idlAttribute">                attribute <span class="idlAttrType">boolean</span>  <span class="idlAttrName"><a href="#widl-TTMLCue-deferUpdates">deferUpdates</a></span>;</span>
+<span class="idlAttribute">    [<span class="extAttr">SameObject</span>]
+    readonly    attribute <span class="idlAttrType"><a href="#dfn-document" class="internalDFN">Document</a></span> <span class="idlAttrName"><a href="#widl-TTMLCue-ttml">ttml</a></span>;</span>
+<span class="idlMethod">    <span class="idlMethType"><a href="#dfn-documentfragment" class="internalDFN">DocumentFragment</a></span> <span class="idlMethName"><a href="#widl-TTMLCue-getCueAsHTML-DocumentFragment">getCueAsHTML</a></span> ();</span>
+};</span></pre><section id="attributes"><h4 aria-level="3" role="heading" id="h4_attributes"><span class="secno">6.1.1 </span>Attributes</h4><dl class="attributes"><dt id="widl-TTMLCue-deferUpdates"><code>deferUpdates</code> of type <span class="idlAttrType">boolean</span>,            </dt><dd><p>Access deferred update flag of cue.</p>
+<p>Upon read, return <code>true</code> if rendering updates are being deferred; otherwise, return <code>false</code>.
+Upon write, perform the following ordered steps:</p>
+<ol>
+<li>if the current value is the same as the new value, then return;</li>
+<li>if the current value is <code>false</code> and the new value is <code>true</code>, then set the current value to <code>true</code> and
+begin deferring rendering updates;</li>
+<li>if the current value is <code>true</code> and the new value is <code>false</code>, then set the current value to <code>false</code> and
+asynchronously perform a rendering update.</li>
+</ol></dd><dt id="widl-TTMLCue-ttml"><code>ttml</code> of type <span class="idlAttrType"><a href="#dfn-document" class="internalDFN">Document</a></span>, readonly   </dt><dd>Obtain a reference to a live copy of an <a href="#dfn-xml-document" class="internalDFN">XML document</a> that represents the current content of the cue.</dd></dl></section><section id="methods"><h4 aria-level="3" role="heading" id="h4_methods"><span class="secno">6.1.2 </span>Methods</h4><dl class="methods"><dt id="widl-TTMLCue-getCueAsHTML-DocumentFragment"><code>getCueAsHTML</code></dt><dd>Obtain a reference to a (non-live) structured clone of the HTML rendition that represents the content of the cue at the time of the immediately preceding completed rendering update.<div><em>No parameters.</em></div><div><em>Return type: </em><code><a href="#dfn-documentfragment" class="internalDFN">DocumentFragment</a></code></div></dd></dl></section>
+<section id="constructors">
+<h4 aria-level="3" role="heading" id="h4_constructors"><span class="secno">6.1.3 </span>Constructors</h4>
+<dl class="constructors">
+<dt id="widl-TTMLCue-TTMLCue-double-startTime-double-endTime-DocumentFragment-content"><code>TTMLCue</code></dt>
+<dd>
+<table class="parameters">
+<tbody><tr>
+<th>Parameter</th>
+<th>Type</th>
+<th>Nullable</th>
+<th>Optional</th>
+<th>Description</th>
+</tr>
+<tr>
+<td class="prmName">startTime</td>
+<td class="prmType"><code>double</code></td>
+<td class="prmNullFalse">✘</td>
+<td class="prmOptFalse">✘</td>
+<td class="prmDesc">
+A <a href="#dfn-ttml-media-time" class="internalDFN">TTML media time</a> relative cue starting time, as further defined by
+<a href="http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#dom-TextTrackCue-startTime"><dfn id="dfn-starttime"><code>startTime</code></dfn></a> [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>].
+</td>
+</tr>
+<tr>
+<td class="prmName">endTime</td>
+<td class="prmType"><code>double</code></td>
+<td class="prmNullFalse">✘</td>
+<td class="prmOptFalse">✘</td>
+<td class="prmDesc">
+A <a href="#dfn-ttml-media-time" class="internalDFN">TTML media time</a> relative cue ending time, as further defined by
+<a href="http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#dom-TextTrackCue-endTime"><dfn id="dfn-endtime"><code>endTime</code></dfn></a> [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>].
+</td>
+</tr>
+<tr>
+<td class="prmName">content</td>
+<td class="prmType"><code><a href="#dfn-document" class="internalDFN">Document</a></code></td>
+<td class="prmNullTrue">✔</td>
+<td class="prmOptFalse">✘</td>
+<td class="prmDesc">
+A <a href="#dfn-document" class="internalDFN"><code>Document</code></a> representing a <a href="#dfn-ttml-intermediate-synchronic-document" class="internalDFN">TTML intermediate synchronic document</a>.
+</td>
+</tr>
+</tbody></table>
+<p>If the <code>startTime</code> argument is less than zero, then <a href="#dfn-throw" class="internalDFN">throw</a> a <a href="#dfn-syntaxerror" class="internalDFN"><code>SyntaxError</code></a> exception.</p>
+<p>If the <code>endTime</code> argument is less than zero, then <a href="#dfn-throw" class="internalDFN">throw</a> a <a href="#dfn-syntaxerror" class="internalDFN"><code>SyntaxError</code></a> exception.
+If the <code>endTime</code> argument is less than <code>startTime</code>, then set the cue's end time to <code>startTime</code>.</p>
+<p>If the <code>content</code> argument is <code>null</code>, then the constructed cue object represents
+a <dfn id="dfn-cue-with-no-content">cue with no content</dfn>. Otherwise, if any of the following constraints are not true, then
+<a href="#dfn-throw" class="internalDFN">throw</a> a <a href="#dfn-syntaxerror" class="internalDFN"><code>SyntaxError</code></a> exception:</p>
+<ul>
+<li>The value of <code><var>content</var>.contentType</code> is either "<code>application/ttml+xml</code>" or "<code>application/xml</code>".</li>
+<li>The value of <code><var>content</var>.documentElement</code> is not <code>null</code>.
+</li><li>The value of <code><var>content</var>.documentElement.namespaceURI</code> is "<code>http://www.w3.org/ns/ttml</code>".
+</li><li>The value of <code><var>content</var>.documentElement.localName</code> is "<code>tt</code>".
+</li></ul>
+<p>Otherwise, set the cue's content to a <a href="#dfn-structured-clone" class="internalDFN">structured clone</a> of <code><var>content</var></code>.</p>
+</dd>
+</dl>
+</section>
+</section>
+</section>
+
+
+<section id="references" class="appendix" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><!--OddPage--><h2 aria-level="1" role="heading" id="h2_references"><span class="secno">A. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#ref" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_normative-references"><span class="secno">A.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-DOM4">[DOM4]</dt><dd rel="dcterms:requires">A. van Kesteren et al., Eds. <a href="http://www.w3.org/TR/2013/WD-dom-20131107/"><cite>W3C DOM4</cite></a>, W3C Working Draft, URL: <a href="http://www.w3.org/TR/2013/WD-dom-20131107/">http://www.w3.org/TR/2013/WD-dom-20131107/</a>
+</dd><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:requires">R. Berjon et al., Eds. <a href="http://www.w3.org/html/wg/drafts/html/master/Overview.html"><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href="http://www.w3.org/html/wg/drafts/html/master/Overview.html">http://www.w3.org/html/wg/drafts/html/master/Overview.html</a>
+</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
+</dd><dt id="bib-TTML1">[TTML1]</dt><dd rel="dcterms:requires">G. Adams et al., Eds. <a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/"><cite>Timed Text Markup Language 1 (TTML1) (Second Edition)</cite></a>, W3C Recommendation, URL: <a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/">http://www.w3.org/TR/2013/REC-ttml1-20130924/</a>
+</dd><dt id="bib-TTML1API">[TTML1API]</dt><dd rel="dcterms:requires">G. Adams et al., Eds. <a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html"><cite>TTML API Level 1</cite></a>, W3C Editor's Draft, URL: <a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html">http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html</a>
+</dd><dt id="bib-TTML2">[TTML2]</dt><dd rel="dcterms:requires">G. Adams et al., Eds. <a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html"><cite>Timed Text Markup Language 2 (TTML2)</cite></a>, W3C Editor's Draft, URL: <a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html">http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html</a>
+</dd><dt id="bib-WEBIDL">[WEBIDL]</dt><dd rel="dcterms:requires">C. McCormack et al., Eds. <a href="http://dev.w3.org/2006/webapi/WebIDL/"><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href="http://dev.w3.org/2006/webapi/WebIDL/">http://dev.w3.org/2006/webapi/WebIDL/</a>
+</dd></dl></section></section></body></html>
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml2-api/Overview.src.html	Wed Dec 11 15:35:35 2013 -0500
@@ -0,0 +1,249 @@
+<!DOCTYPE html>
+<html>
+<head>
+<meta charset='utf-8' />
+<title>TTML API Level 2</title>
+<script src='http://www.w3.org/Tools/respec/respec-w3c-common' class=remove async></script>
+<script class=remove>
+respecConfig = {
+    // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+    specStatus:           "ED",
+
+    // the specification's short name, as in http://www.w3.org/TR/short-name/
+    shortName:            "ttml2-api",
+
+    // use respec source as current ED uri
+    edDraftURI: "http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2-api/Overview.html",
+
+    // editors, add as many as you like
+    // only "name" is required
+    editors:  [
+        { name: "Glenn Adams",
+          company: "Cox Communications, Inc.", companyURL: "http://www.cox.com/" },
+    ],
+
+    // name of the WG
+    wg:           "Timed Text Working Group",
+
+    // URI of the public WG page
+    wgURI:        "http://www.w3.org/AudioVideo/TT/",
+
+    // name (without the @w3c.org) of the public mailing to which comments are due
+    wgPublicList: "public-tt",
+
+    // URI of the patent status for this WG, for Rec-track documents
+    // !!!! IMPORTANT !!!!
+    // This is important for Rec-track documents, do not copy a patent URI from a random
+    // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+    // Team Contact.
+    wgPatentURI: "http://www.w3.org/2004/01/pp-impl/34314/status",
+
+    noRecTrack: false,
+
+    localBiblio: {
+      "DOM4" : "A. van Kesteren et al., Eds. <a href='http://www.w3.org/TR/2013/WD-dom-20131107/'><cite>W3C DOM4</cite></a>, W3C Working Draft, URL: <a href='http://www.w3.org/TR/2013/WD-dom-20131107/'>http://www.w3.org/TR/2013/WD-dom-20131107/</a>",
+      "HTML5" : "R. Berjon et al., Eds. <a href='http://www.w3.org/html/wg/drafts/html/master/Overview.html'><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href='http://www.w3.org/html/wg/drafts/html/master/Overview.html'>http://www.w3.org/html/wg/drafts/html/master/Overview.html</a>",
+      "TTML1" : "G. Adams et al., Eds. <a href='http://www.w3.org/TR/2013/REC-ttml1-20130924/'><cite>Timed Text Markup Language 1 (TTML1) (Second Edition)</cite></a>, W3C Recommendation, URL: <a href='http://www.w3.org/TR/2013/REC-ttml1-20130924/'>http://www.w3.org/TR/2013/REC-ttml1-20130924/</a>",
+      "TTML1API" : "G. Adams et al., Eds. <a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html'><cite>TTML API Level 1</cite></a>, W3C Editor's Draft, URL: <a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html'>http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html</a>",
+      "TTML2" : "G. Adams et al., Eds. <a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html'><cite>Timed Text Markup Language 2 (TTML2)</cite></a>, W3C Editor's Draft, URL: <a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html'>http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html</a>",
+      "WEBIDL" : "C. McCormack et al., Eds. <a href='http://dev.w3.org/2006/webapi/WebIDL/'><cite>HTML 5.1 Nightly</cite></a>, W3C Editor's Draft, URL: <a href='http://dev.w3.org/2006/webapi/WebIDL/'>http://dev.w3.org/2006/webapi/WebIDL/</a>",
+    },
+
+};
+function term(doc, content) {
+    // perform transformations to make it render and prettier
+    return '<span class="ttmlTerm">' + doc._esc(content) + '</span>';
+}
+function template(doc, content) {
+    // perform transformations to make it render and prettier
+    return '<div class="template">' + content + '</div>';
+}
+var examples = 0;
+function example(doc, content) {
+    // perform transformations to make it render and prettier
+    var prefix = examples < 9 ? "E000" : "E00";
+    return '<div class=numbered title=' + prefix + (++examples) + '>' + content + '</div>';
+}
+</script>
+</head>
+<body>
+<section id='abstract'>
+<p>This document defines a Level 2 API for exposing parsed and formatted Timed Text Markup Language (TTML) content to Web Applications.</p>
+</section>
+<section id='sotd'>
+<p><b>This document is an editor's draft that has no official standing.</b></p>
+</section>
+<section id='introduction'>
+<h2>Introduction</h2>
+<p><em>This section is non-normative.</em></p>
+<p>This document defines a Level 2 API for exposing parsed and formatted Timed Text Markup Language (TTML) content to Web Applications. The parsed form
+of TTML is exposed as a DOM representation of a <a>TTML intermediate synchronic document</a>. The formatted form of TTML is exposed as an HTML document
+fragment that encodes a renderable representation of the parsed form.</p>
+</section>
+<section id='use-cases'>
+<h2>Use Cases</h2>
+<p><em>This section is non-normative.</em></p>
+<p>This section describes common use cases for the TTML API Level 2.</p>
+<section>
+<h3>User Agent Rendering of Parsed TTML Content</h3>
+<p>When a <a>text track</a> is in the <a>showing mode</a> and the <a>text track's list of cues</a> includes an instance of <a><code>TTMLCue</code></a>,
+then a <a>user agent</a> attempts to render the cue using the HTML document fragment associated with the cue.</p>
+</section>
+<section>
+<h3>Web Application Rendering of Parsed TTML Content</h3>
+<p>When a <a>text track</a> is not in the <a>showing mode</a> and the <a>text track's list of cues</a> includes an instance of <a><code>TTMLCue</code></a>,
+then a Web Application may render the cue, for example, by making direct use of the cue's parsed form or by using the cue's formatted HTML form.</p>
+</section>
+<section>
+<h3>Web Application Use of Parsed TTML Content Metadata</h3>
+<p>When a <a>text track</a> is not in the <a>showing mode</a> and the <a>text track's list of cues</a> includes an instance of <a><code>TTMLCue</code></a>,
+then a Web Application may access parsed TTML metadata contained in the TTML DOM representation exposed by the cue.</p>
+</section>
+</section>
+<section id='terminology'>
+<h2>Definitions</h2>
+<section id='terminology'>
+<h3>Terminology</h3>
+<dl>
+<dt>[TBS]</dt>
+<dd>To Be Supplied.</dd>
+</dd>
+</dl>
+</section>
+<section id='externals'>
+<h3>External Definitions</h3>
+<p>This specification relies upon the certain concepts and APIs defined in other specifications as follows:</p>
+<dl>
+<dt>DOM</dt>
+<dd>The concepts
+<a href='http://dom.spec.whatwg.org#concept-throw'><dfn>throw</dfn></a>, and
+<a href='http://dom.spec.whatwg.org#xml-document'><dfn>XML document</dfn></a>,
+the interfaces
+<a href='http://dom.spec.whatwg.org#document'><dfn><code>Document</code></dfn></a>,
+<a href='http://dom.spec.whatwg.org#documentfragment'><dfn><code>DocumentFragment</code></dfn></a>, and
+<a href='http://dom.spec.whatwg.org#element'><dfn><code>Element</code></dfn></a>, and
+and the exception
+<a href='http://dom.spec.whatwg.org#syntaxerror'><dfn><code>SyntaxError</code></dfn></a>.
+[[!DOM4]]</dd>
+<dt>HTML</dt>
+<dd>The concepts
+<a href='http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#interactive'><dfn>interactive browsers</dfn></a>,
+<a href='http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#media-resource-specific-text-track'><dfn>media-resource-specific text track</dfn></a>,
+<a href='http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#non-interactive'><dfn>non-interactive browsers</dfn></a>, and
+<a href='http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#structured-clone'><dfn>structured clone</dfn></a>,
+<a href='http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#showing-0'><dfn>showing mode</dfn></a>,
+<a href='http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#text-track-model'><dfn>text track</dfn></a>,
+<a href='http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#text-track-model'><dfn>text track's list of cues</dfn></a>, and
+<a href='http://www.w3.org/html/wg/drafts/html/master/introduction.html#a-quick-introduction-to-html'><dfn>user agent</dfn></a>,
+and the interfaces
+<a href='http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#texttrack'><dfn><code>TextTrack</code></dfn></a> and
+<a href='http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#texttrackcue'><dfn><code>TextTrackCue</code></dfn></a>.
+[[!HTML5]]</dd>
+<dt>TTML</dt>
+<dd>The concepts
+<a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html#ttml-content-doctype'><dfn>TTML content</dfn></a>,
+<a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html#semantics-region-layout-step-2'><dfn>TTML intermediate synchronic document</dfn></a>, and
+<a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1/spec/ttml1.html#time-expression-semantics-media'><dfn>TTML media time</dfn></a>.
+[[!TTML1]]</dd>
+<dt>TTML API Level 1</dt>
+<dd>The interface
+<a href='http://dvcs.w3.org/hg/ttml/raw-file/default/ttml1-api/Overview.html#RawTTMLCue'><dfn><code>RawTTMLCue</code></dfn></a>.
+[[!TTML1API]]</dd>
+<dt>WebIDL</dt>
+<dd>The generic semantics that apply to IDL specifications. [[!WEBIDL]]</dd>
+</dl>
+</section>
+</section>
+<section id='conformance'>
+<p>An <a title='user agent'>HTML user agent</a> that claims to support the rendering of any profile of [[!TTML1]] or claims to support any profile of [[!TTML2]],
+or any subsequent version thereof, MUST implement
+support for the TTML Level 2 API defined herein, and, if it renders <A>TTML content</a> in any fashion or exposes <a>TTML content</a> to Web Applications in any fashion,
+then it also MUST render or expose that content to Web Applications using this API.</p>
+</section>
+<section id='dependencies'>
+<h2>Dependencies</h2>
+</section>
+<section id='apis'>
+<h2>API Definitions</h2>
+<section id='TTMLCue'>
+<h2>TTMLCue Interface</h2>
+<dl class='idl' title='[Constructor(double startTime, double endTime, Document? content)] interface TTMLCue : RawTTMLCue'>
+<dt>attribute boolean deferUpdates</dt>
+<dd><p>Access deferred update flag of cue.</p>
+<p>Upon read, return <code>true</code> if rendering updates are being deferred; otherwise, return <code>false</code>.
+Upon write, perform the following ordered steps:</p>
+<ol>
+<li>if the current value is the same as the new value, then return;</li>
+<li>if the current value is <code>false</code> and the new value is <code>true</code>, then set the current value to <code>true</code> and
+begin deferring rendering updates;</li>
+<li>if the current value is <code>true</code> and the new value is <code>false</code>, then set the current value to <code>false</code> and
+asynchronously perform a rendering update.</li>
+</dd>
+<dt>[SameObject] readonly attribute Document ttml</dt>
+<dd>Obtain a reference to a live copy of an <a>XML document</a> that represents the current content of the cue.</dd>
+<dt>DocumentFragment getCueAsHTML()</dt>
+<dd>Obtain a reference to a (non-live) structured clone of the HTML rendition that represents the content of the cue at the time of the immediately preceding completed rendering update.</dd>
+</dl>
+<section>
+<h3>Constructors</h3>
+<dl class='constructors'>
+<dt id='widl-TTMLCue-TTMLCue-double-startTime-double-endTime-DocumentFragment-content'><code>TTMLCue</code></dt>
+<dd>
+<table class='parameters'>
+<tr>
+<th>Parameter</th>
+<th>Type</th>
+<th>Nullable</th>
+<th>Optional</th>
+<th>Description</th>
+</tr>
+<tr>
+<td class='prmName'>startTime</td>
+<td class='prmType'><code><a>double</a></code></td>
+<td class='prmNullFalse'>✘</td>
+<td class='prmOptFalse'>✘</td>
+<td class='prmDesc'>
+A <a>TTML media time</a> relative cue starting time, as further defined by
+<a href='http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#dom-TextTrackCue-startTime'><dfn><code>startTime</code></dfn></a> [[!HTML5]].
+</td>
+</tr>
+<tr>
+<td class='prmName'>endTime</td>
+<td class='prmType'><code><a>double</a></code></td>
+<td class='prmNullFalse'>✘</td>
+<td class='prmOptFalse'>✘</td>
+<td class='prmDesc'>
+A <a>TTML media time</a> relative cue ending time, as further defined by
+<a href='http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#dom-TextTrackCue-endTime'><dfn><code>endTime</code></dfn></a> [[!HTML5]].
+</td>
+</tr>
+<tr>
+<td class='prmName'>content</td>
+<td class='prmType'><code><a>Document</a></code></td>
+<td class='prmNullTrue'>✔</td>
+<td class='prmOptFalse'>✘</td>
+<td class='prmDesc'>
+A <a><code>Document</code></a> representing a <a>TTML intermediate synchronic document</a>.
+</td>
+</tr>
+</table>
+<p>If the <code>startTime</code> argument is less than zero, then <a>throw</a> a <a><code>SyntaxError</code></a> exception.</p>
+<p>If the <code>endTime</code> argument is less than zero, then <a>throw</a> a <a><code>SyntaxError</code></a> exception.
+If the <code>endTime</code> argument is less than <code>startTime</code>, then set the cue's end time to <code>startTime</code>.</p>
+<p>If the <code>content</code> argument is <code>null</code>, then the constructed cue object represents
+a <dfn>cue with no content</dfn>. Otherwise, if any of the following constraints are not true, then
+<a>throw</a> a <a><code>SyntaxError</code></a> exception:</p>
+<ul>
+<li>The value of <code><var>content</var>.contentType</code> is either "<code>application/ttml+xml</code>" or "<code>application/xml</code>".</li>
+<li>The value of <code><var>content</var>.documentElement</code> is not <code>null</code>.
+<li>The value of <code><var>content</var>.documentElement.namespaceURI</code> is "<code>http://www.w3.org/ns/ttml</code>".
+<li>The value of <code><var>content</var>.documentElement.localName</code> is "<code>tt</code>".
+</ul>
+<p>Otherwise, set the cue's content to a <a>structured clone</a> of <code><var>content</var></code>.</p>
+</dd>
+</dl>
+</section>
+</section>
+</section>
+</body>
+</html>
Binary file ttml2/design/TPAC2013-TTMLAnimations.pdf has changed
Binary file ttml2/design/TPAC2013-TTMLProfiles.pdf has changed
--- a/ttml2/spec/entitiesedcopy.dtd	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml2/spec/entitiesedcopy.dtd	Wed Dec 11 15:35:35 2013 -0500
@@ -19,7 +19,7 @@
 
 <!ENTITY w3c-designation "&prefix;.html">
 
-<!ENTITY w3c.tr.latest  "http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec">
+<!ENTITY w3c.tr.latest  "https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec">
 
 <!-- Latest version links. don't touch -->
 <!ENTITY latest "&w3c.tr.latest;/&w3c-designation;?content-type=text/html;charset=utf-8">
Binary file ttml2/spec/rnc/schema.zip has changed
--- a/ttml2/spec/rnc/ttml2-datatypes.rnc	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml2/spec/rnc/ttml2-datatypes.rnc	Wed Dec 11 15:35:35 2013 -0500
@@ -294,6 +294,8 @@
 TTAF.TextOrientation.datatype =
   "mixed" |
   "sideways" |
+  "sidewaysLeft" |
+  "sidewaysRight" |
   "upright"
 
 TTAF.TextOutline.datatype =
--- a/ttml2/spec/ttml2-changes.html	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml2/spec/ttml2-changes.html	Wed Dec 11 15:35:35 2013 -0500
@@ -76,8 +76,21 @@
 * In 8.2.1, add 'set' element to enumeration of element types to which 'style'
   attribute applies.
 
-* In 8.2.13, make use of 125% of largest applicable font size a normative
-  requirement for interpreting 'normal' value of tts:lineHeight.
+* In 8.2.9, add 'p' element to enumeration  of element types to which
+  tts:fontFamily applies.
+
+* In 8.2.10, add 'p' element to enumeration  of element types to which
+  tts:fontSize applies.
+
+* In 8.2.11, add 'p' element to enumeration  of element types to which
+  tts:fontStyle applies.
+
+* In 8.2.12, add 'p' element to enumeration  of element types to which
+  tts:fontWeight applies.
+
+* In 8.2.13, specify algorithm for resolving the 'normal' value of
+  tts:lineHeight that takes into account the use of per-font-metrics for
+  ascent, descent, and line gap, using 125% of font size as a fall back.
 
 * In 8.2.14, add content elements to enumeration of element types to which
   tts:opacity applies.
@@ -126,8 +139,10 @@
 
 <span class="strong">Editorial Changes</span>
 
-* In 2.2, add definitions: "Inline Animation", "Inline Region", "Out-of-line Animation",
-  "Out-of-line Region".
+* In 2.2, add definitions: "anonymous profile", "content profile", "designated profile",
+  "fragment identifier", "inline animation", "inline region", "out-of-line animation",
+   "out-of-line region", "profile", "profile designator", "profile fragment identifier",
+   "undesignated profile".
 
 * In 8.2, add note about the use of non-applicable style attributes.
 
@@ -149,6 +164,9 @@
 
 * In Appendix J, add derivation of tts:border and tts:textOrientation attributes.
 
+* Change convention for labeling and citing definitions to use "[lower case]" in
+  definitions and hyperlinked "lower case" in citations.
+
 * Update SMIL section number references to track SMIL3.
 </pre>
 </div>
--- a/ttml2/spec/ttml2.html	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml2/spec/ttml2.html	Wed Dec 11 15:35:35 2013 -0500
@@ -80,11 +80,11 @@
 .strong { font-weight: bold }
 .reqattr { font-weight: bold }
 .optattr { font-style: italic }
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/09/06 04:01:47 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/W3C-ED.css"></head><body>Last Modified: $Date: 2013/12/05 22:38:51 $<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>Editors' copy $Date: 2013/09/06 04:01:47 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
+<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/12/05 22:38:51 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
 <a href="ttml2.html">ttml2.html</a>
-</dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/spec/ttml2.html?content-type=text/html;charset=utf-8</a></dd><dt>Previous version:</dt><dd>
+</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>Previous version:</dt><dd>
 <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</a>
 </dd><dt>Editor:</dt><dd>Glenn Adams, Cox Communications, Inc.</dd><dt>Contributing Authors:</dt><dd>Mike Dolan, Invited Expert</dd><dd>Geoff Freed, WGBH National Center for Accessible Media</dd><dd>Sean Hayes, Microsoft</dd><dd>Erik Hodge, RealNetworks</dd><dd>David Kirby, British Broadcasting Corporation (BBC)</dd><dd>Thierry Michel, W3C</dd><dd>Dave Singer, Apple Computer</dd></dl><p>Please refer to the <a href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml10/spec/ttml-issues.html">errata</a> for this document, which may
       include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ttml2"><strong>translations</strong></a>.</p><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>), All Rights Reserved. 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>
@@ -121,6 +121,14 @@
 5 <a href="#vocabulary">Vocabulary</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#vocabulary-namespaces">Namespaces</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#vocabulary-profiles">Profiles</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#vocabulary-profile-introduction">Introduction</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#vocabulary-profile-designators">Profile Designators</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2.1 <a href="#vocabulary-profile-standard-designators">Standard Designators</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3 <a href="#vocabulary-profile-semantics">Profile Semantics</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3.1 <a href="#vocabulary-profile-combination">Profile Combination</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3.2 <a href="#vocabulary-content-profile-processing">Content Profile Semantics</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3.3 <a href="#vocabulary-processor-profile-processing">Processor Profile Semantics</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.4 <a href="#vocabulary-profile-examples">Profile Examples</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;5.3 <a href="#vocabulary-overview">Catalog</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.1 <a href="#core-vocabulary-overview">Core Catalog</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.2 <a href="#extension-vocabulary-overview">Extension Catalog</a><br>
@@ -419,11 +427,11 @@
 H <a href="#other-references">Other References</a> (Non-Normative)<br>
 I <a href="#requirements">Requirements</a> (Non-Normative)<br>
 J <a href="#derivation">Vocabulary Derivation</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e21921">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e22438">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e22290">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e22807">Attribute Derivation</a><br>
 K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e23431">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e23595">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e23800">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e23964">Guidelines</a><br>
 L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
 M <a href="#concrete-encoding">Concrete Encoding</a><br>
 N <a href="#time-expression-semantics">Time Expression Semantics</a><br>
@@ -635,15 +643,16 @@
 <h3><a id="acronyms"></a>2.1 Acronyms</h3><table class="acronyms" summary="Glossary List"><tr><td class="label"><b>DFXP</b></td><td class="def"><p>Distribution Format Exchange Profile</p></td></tr><tr><td class="label"><b>TT</b></td><td class="def"><p>Timed Text</p></td></tr><tr><td class="label"><b>TTML</b></td><td class="def"><p>Timed Text Markup Language</p></td></tr><tr><td class="label"><b>TTAF</b></td><td class="def"><p>Timed Text Authoring Format</p></td></tr><tr><td class="label"><b>TTWG</b></td><td class="def"><p>Timed Text Working Group</p></td></tr></table></div><div class="div2">
 <h3><a id="terms"></a>2.2 Terminology</h3><dl><dt class="label"><a id="terms-abstract-document-instance"></a>[abstract document instance]</dt><dd><p>An instance of an abstract data set as represented by a
 <a href="#terms-reduced-xml-infoset">reduced xml infoset</a>.</p></dd><dt class="label"><a id="terms-abstract-document-type"></a>[abstract document type]</dt><dd><p>A set of constraints that defines a class of <em>XML Information
-Sets</em> <a href="#infoset">[XML InfoSet]</a>.</p></dd><dt class="label"><a id="terms-attribute-information-item"></a>[attribute information item]</dt><dd><p>Each specified or defaulted attribute  of an XML document corresponds with an attribute information
+Sets</em> <a href="#infoset">[XML InfoSet]</a>.</p></dd><dt class="label"><a id="terms-anonymous-profile"></a>[anonymous profile]</dt><dd><p>See <a href="#terms-undesignated-profile">undesignated profile</a>.</p></dd><dt class="label"><a id="terms-attribute-information-item"></a>[attribute information item]</dt><dd><p>Each specified or defaulted attribute  of an XML document corresponds with an attribute information
 item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.3.</p></dd><dt class="label"><a id="terms-character-information-item"></a>[character information item]</dt><dd><p>Each data character appearing in an XML document corresponds with a character information
 item as defined by <a href="#infoset">[XML InfoSet]</a>, §2.6.</p></dd><dt class="label"><a id="terms-computed-cell-size"></a>[computed cell size]</dt><dd><p>The size (extent) of a cell computed by dividing the width of the <a href="#terms-root-container-region">root container region</a>
 by the column count, i.e., the number of cells in the horizontal axis, and by dividing
 the height of the <a href="#terms-root-container-region">root container region</a> by the row count, i.e., the number of cells in the vertical
 axis, where the column and row counts are determined by the <code>ttp:cellResolution</code> parameter attribute.</p></dd><dt class="label"><a id="terms-content-element"></a>[content element]</dt><dd><p>Any of the element types defined by the <a href="#element-vocab-type-content">Content Module</a>.</p></dd><dt class="label"><a id="terms-content-processor"></a>[content processor]</dt><dd><p>A processing system capable of importing (receiving) Timed Text Markup Language
-content for the purpose of transforming, presenting, or otherwise processing the content.</p></dd><dt class="label"><a id="terms-content-profile"></a>[content profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that are (or may be) employed by
+content for the purpose of transforming, presenting, or otherwise processing the content.</p></dd><dt class="label"><a id="terms-content-profile"></a>[content profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that must, may, or must not be employed by
 Timed Text Markup Language content.</p><table border="1" class="ednote" summary="Editorial note: Content Profile"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Content Profile</b></td><td align="right" valign="top">2013-08-23</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Need to update and elaborate definition of content profile based on new profiling mechanisms.</td></tr></table><p></p></dd><dt class="label"><a id="terms-content-region"></a>[content region]</dt><dd><p>A logical region into which rendered content is placed when modeling or
-performing presentation processing.</p></dd><dt class="label"><a id="terms-designated-profile"></a>[designated profile]</dt><dd><p><span class="tbd">To Be Defined</span></p></dd><dt class="label"><a id="terms-document-instance"></a>[document instance]</dt><dd><p>A concrete realization of a Timed Text Markup Language document, where the concrete form
+performing presentation processing.</p></dd><dt class="label"><a id="terms-designated-profile"></a>[designated profile]</dt><dd><p>A <a href="#terms-profile">profile</a> that is associated with a <a href="#terms-profile-designator">profile designator</a> by
+means of a <code>designator</code> attribute or prose text in a specification of profile.</p></dd><dt class="label"><a id="terms-document-instance"></a>[document instance]</dt><dd><p>A concrete realization of a Timed Text Markup Language document, where the concrete form
 is specific to the context of reference. For example, a sequence of bytes that represents an
 XML serialization of a Timed Text document, an internal, parsed representation of such a
 Timed Text document, etc.</p></dd><dt class="label"><a id="terms-document-interchange-context"></a>[document interchange context]</dt><dd><p>The implied context or environment external to a <a href="#terms-content-processor">content processor</a> in
@@ -656,7 +665,8 @@
 labeled (using a extension designation) in another (public or private)
 specification.</p></dd><dt class="label"><a id="terms-feature"></a>[feature]</dt><dd><p>A syntactic or semantic expression or capability that is defined and
 labeled (using a feature designation) in this specification (or a past or
-future revision of this specification).</p></dd><dt class="label"><a id="terms-inline-animation"></a>[inline 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
+future revision of this specification).</p></dd><dt class="label"><a id="terms-fragment-identifier"></a>[fragment identifier]</dt><dd><p>A syntactic expression that adheres to the fragment identifer syntax defined by <a href="#uri">[URI]</a>,
+Section 4.1.</p></dd><dt class="label"><a id="terms-inline-animation"></a>[inline 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 inline as an immediate child of
 a <a href="#terms-content-element">content element</a> or <a href="#layout-vocabulary-region"><code>region</code></a> element targetted by the animation.
 There is a one-to-one relation between
@@ -682,9 +692,10 @@
 and the <a href="#terms-content-element">content element(s)</a> to be selected into (targetted to) the region.</p></dd><dt class="label"><a id="terms-presentation-processor"></a>[presentation processor]</dt><dd><p>A <a href="#terms-content-processor">content processor</a> which purpose is to layout, format, and render,
 i.e., to present, <a href="#terms-timed-text-markup-language">Timed Text Markup Language</a> content by applying the presentation semantics
 defined in this specification.</p></dd><dt class="label"><a id="terms-processor"></a>[processor]</dt><dd><p>See <a href="#terms-content-processor">content processor</a>.</p></dd><dt class="label"><a id="terms-processor-profile"></a>[processor profile]</dt><dd><p>A collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a> that must or may be implemented (supported) by
-a content processor.</p><table border="1" class="ednote" summary="Editorial note: [processor profile]"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: [processor profile]</b></td><td align="right" valign="top">2013-08-23</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Need to update and elaborate definition of processor profile based on new profiling mechanisms.</td></tr></table><p></p></dd><dt class="label"><a id="terms-profile-definition-document"></a>[profile definition document]</dt><dd><p>A document that defines a specific collection of <a href="#terms-feature">features</a> and <a href="#terms-extension">extensions</a>
-for which support is required or optional in a recipient content
-processor.</p></dd><dt class="label"><a id="terms-region"></a>[region]</dt><dd><p>A logical construct that models authorial intention regarding
+a content processor.</p><table border="1" class="ednote" summary="Editorial note: [processor profile]"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: [processor profile]</b></td><td align="right" valign="top">2013-08-23</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Need to update and elaborate definition of processor profile based on new profiling mechanisms.</td></tr></table><p></p></dd><dt class="label"><a id="terms-profile"></a>[profile]</dt><dd><p>A <a href="#terms-content-profile">content profile</a> or <a href="#terms-processor-profile">processor profile</a>.</p></dd><dt class="label"><a id="terms-profile-definition-document"></a>[profile definition document]</dt><dd><p>A document that formally specifies a <a href="#terms-profile">profile</a>, where such document is a valid TTML document instance
+which has a root element type of <code>ttp:profile</code>.</p></dd><dt class="label"><a id="terms-profile-designator"></a>[profile designator]</dt><dd><p>An absolute URI used to label or reference an externally defined <a href="#terms-profile">profile</a>, where
+external refers to being external to a <a href="#terms-document-instance">document instance</a>.</p></dd><dt class="label"><a id="terms-profile-fragment-identifier"></a>[profile fragment identifier]</dt><dd><p>A <a href="#terms-fragment-identifier">fragment identifier</a> used to label or reference an internally defined <a href="#terms-profile">profile</a>, where
+internal refers to being internal to a <a href="#terms-document-instance">document instance</a>.</p></dd><dt class="label"><a id="terms-region"></a>[region]</dt><dd><p>A logical construct that models authorial intention regarding
 desired or potential presentation processing, and which is represented as
 a rectangular area of a presentation surface into which content
 is composed and rendered during presentation processing.</p></dd><dt class="label"><a id="terms-reduced-xml-infoset"></a>[reduced xml infoset]</dt><dd><p>An XML Information Set <a href="#infoset">[XML InfoSet]</a> that satisfies the
@@ -712,7 +723,8 @@
 or rewrites TTML features so as to conform to a profile of TTML. An example of the latter is
 a processor that translates TTML into a completely different timed text format. Because this
 specification does not otherwise define a target profile or format for transformation processing,
-no further transformation semantics are defined by this specification.</p></dd><dt class="label"><a id="terms-undesignated-profile"></a>[undesignated profile]</dt><dd><p><span class="tbd">To Be Defined</span></p></dd><dt class="label"><a id="terms-valid-abstract-document-instance"></a>[valid abstract document instance]</dt><dd><p>An <a href="#terms-abstract-document-instance">abstract document instance</a> which has been assessed for validity
+no further transformation semantics are defined by this specification.</p></dd><dt class="label"><a id="terms-undesignated-profile"></a>[undesignated profile]</dt><dd><p>A <a href="#terms-profile">profile</a> that is not associated with a <a href="#terms-profile-designator">profile designator</a>, and which is
+referred to implicitly in the context of the profile's definition. Also referred to as an <em>anonymous profile</em>.</p></dd><dt class="label"><a id="terms-valid-abstract-document-instance"></a>[valid abstract document instance]</dt><dd><p>An <a href="#terms-abstract-document-instance">abstract document instance</a> which has been assessed for validity
 and found to be valid as defined by <a href="#doctypes"><b>4 Document Types</b></a>.</p></dd></dl></div><div class="div2">
 <h3><a id="conventions"></a>2.3 Documentation Conventions</h3><p>Within normative prose in this specification, the words
 <em>may</em>, <em>should</em>, and <em>must</em> are
@@ -902,18 +914,29 @@
 dereferencing standard profile definitions.</p></div><p>All TTML Namespaces are <a href="http://www.w3.org/2001/tag/doc/namespaceState#namespacedef"><em>mutable</em></a>
 <a href="#nsstate">[NSState]</a>; all undefined names in these namespaces are reserved for future
 standardization by the W3C.</p></div><div class="div2">
-<h3><a id="vocabulary-profiles"></a>5.2 Profiles</h3><p>The Timed Text Markup Language (TTML) employs a number of
-standard, predefined profiles of its
-vocabulary and associated semantics.
-The following table specifies this set of
-profiles, indicating
-a normative name
-and designator for each
-predefined profile,
-and where each of these profiles is formally elaborated in
-<a href="#profiles"><b>F Profiles</b></a>, in <a href="#ttml1">[TTML1]</a>,
-or in another TTWG specification.</p><a id="profile-vocab-table"></a><table class="common"><caption>Table 2 – Profiles</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Name</th><th>Designator</th></tr><tr><td>DFXP Transformation</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-transformation</code></td></tr><tr><td>DFXP Presentation</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code></td></tr><tr><td>DFXP Full</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-full</code></td></tr><tr><td>SDP US</td><td><code>http://www.w3.org/ns/ttml/profile/sdp-us</code></td></tr><tr><td>TTML2 Transformation</td><td><code>http://www.w3.org/ns/ttml/profile/ttml2-transformation</code></td></tr><tr><td>TTML2 Presentation</td><td><code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code></td></tr><tr><td>TTML2 Full</td><td><code>http://www.w3.org/ns/ttml/profile/ttml2-full</code></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>For definitions of the DFXP profiles, see <a href="#ttml1">[TTML1]</a>. For definition of the SDP US profile, see <a href="#sdpus">[SDP US]</a>.</p></div><table border="1" class="ednote" summary="Editorial note: Referencing Undesignated Profile"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Referencing Undesignated Profile</b></td><td align="right" valign="top">2013-09-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Need to update following to allow referring to a local (embedded) profile definition using
-a fragment identifier that references an undesignated ttp:profile element rather than a profile designator URI.</td></tr></table><p>A profile designator must adhere to the
+<h3><a id="vocabulary-profiles"></a>5.2 Profiles</h3><p>This section describes the TTML profiling sub-system and high level requirements that apply to this sub-system. At the end of this section
+appears a sub-section containing examples of profile specifications and examples of how these specifications are referenced and used.</p><div class="div3">
+<h4><a id="vocabulary-profile-introduction"></a>5.2.1 Introduction</h4><p><em>This sub-section is non-normative.</em></p><p>A given profile may be used by a Timed Text Markup Language content author for one of two functions: (1) to declare that a
+<a href="#terms-document-instance">document instance</a> adheres to a collection of constraints on what
+vocabulary is used and how it is used, or (2) to declare that a <a href="#terms-processor">processor</a> must satisfy certain conditions on how
+content is processed. The first of these functions is termed a <a href="#terms-content-profile">content profile</a>, while
+the second is termed a <a href="#terms-processor-profile">processor profile</a>.</p><p>A <a href="#terms-content-profile">content profile</a> is generally used to allow an author to declare, at authoring time,
+what constraints the author intends to apply to a <a href="#terms-document-instance">document instance</a>. Such a
+declaration permits downstream processors to perform content validation or verification, as well as to guide or limit subsequent
+transformation or editing of content in order to maintain adherence to an author specified content profile. In addition, a
+downstream processor may use a content profile declaration to perform an early determination of its ability to process the features
+implied by the content profile.</p><p>A <a href="#terms-processor-profile">processor profile</a> is generally used to allow an author to declare, at authoring time,
+what processing must be supported when processing a <a href="#terms-document-instance">document instance</a>, such that, if a
+processor is not able to perform the indicated processing, then processing should be aborted. Such a declaration permits downstream
+processors to avoid processing content that cannot be processed in a manner that meets the requirements of the content author.</p><p>A content author is not limited to using a single profile, but may make reference to multiple profiles of either type, i.e.,
+multiple content profiles and/or multiple processor profiles. When multiple profiles are referenced, their respective specifications
+are combined to form a single effective content profile that applies to the document and a single effective processor profile
+that applies to a processor when processing the document. In addition, an author is not limited to making reference to externally
+defined profiles, but may define one or more profiles inline within a document.</p></div><div class="div3">
+<h4><a id="vocabulary-profile-designators"></a>5.2.2 Profile Designators</h4><p>A profile is referenced in one of two ways according to whether the profile is defined externally to the referring document or
+is defined inline within the referring document. When defined externally, a profile is referenced by means of a
+<a href="#terms-profile-designator">profile designator</a>. When defined internally (inline), a profile is referenced either implicitly
+or by means of <a href="#terms-profile-fragment-identifier">profile fragment identifier</a>.</p><p>A profile designator must adhere to the
 <code>xsd:anyURI</code> data type defined by <a href="#xsd-2">[XML Schema Part 2]</a>,
 §3.2.17. If the profile designator is expressed as a relative URI,
 then it must be absolutized by using the TT Profile Namespace value as
@@ -921,10 +944,24 @@
 <code>ttml2-presentation</code>, then the absolutized profile designator
 would be
 <code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code>.</p></div><p>All profile designators which have the TT Profile Namespace as a prefix but are otherwise not listed in
-<a href="#profile-vocab-table"><b>Table 2 – Profiles</b></a> are reserved for future standardization, and must not be appear in a conformant
+<a href="#profile-vocab-table"><b>Table 2 – Profiles</b></a> are reserved for future standardization, and must not appear in a conformant
 <a href="#terms-document-instance">document instance</a>. Nothwithstanding this constraint, a profile designator is not restricted to the set of designators enumerated
 in <a href="#profile-vocab-table"><b>Table 2 – Profiles</b></a>, but may be any URI that feasibly dereferences a TTML <a href="#terms-profile-definition-document">profile definition document</a>
-provided it does not use the TT Profile Namespace as a prefix.</p><p>The profile of TTML that must be supported by a
+provided it does not use the TT Profile Namespace as a prefix.</p><div class="div4">
+<h5><a id="vocabulary-profile-standard-designators"></a>5.2.2.1 Standard Designators</h5><p>The Timed Text Markup Language (TTML) employs a number of
+standard, predefined profiles of its
+vocabulary and associated semantics.</p><p>The following table specifies this set of
+profiles, indicating
+a normative name
+and designator for each
+predefined profile,
+and where each of these profiles is formally elaborated in
+<a href="#profiles"><b>F Profiles</b></a>, in <a href="#ttml1">[TTML1]</a>,
+or in another TTWG specification.</p><a id="profile-vocab-table"></a><table class="common"><caption>Table 2 – Profiles</caption><col width="25%" span="1"><col span="1"><tbody><tr><th>Name</th><th>Designator</th></tr><tr><td>DFXP Transformation</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-transformation</code></td></tr><tr><td>DFXP Presentation</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code></td></tr><tr><td>DFXP Full</td><td><code>http://www.w3.org/ns/ttml/profile/dfxp-full</code></td></tr><tr><td>SDP US</td><td><code>http://www.w3.org/ns/ttml/profile/sdp-us</code></td></tr><tr><td>TTML2 Transformation</td><td><code>http://www.w3.org/ns/ttml/profile/ttml2-transformation</code></td></tr><tr><td>TTML2 Presentation</td><td><code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code></td></tr><tr><td>TTML2 Full</td><td><code>http://www.w3.org/ns/ttml/profile/ttml2-full</code></td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>For definitions of the DFXP profiles, see <a href="#ttml1">[TTML1]</a>. For definition of the SDP US profile, see <a href="#sdpus">[SDP US]</a>.</p></div></div></div><div class="div3">
+<h4><a id="vocabulary-profile-semantics"></a>5.2.3 Profile Semantics</h4><div class="div4">
+<h5><a id="vocabulary-profile-combination"></a>5.2.3.1 Profile Combination</h5></div><div class="div4">
+<h5><a id="vocabulary-content-profile-processing"></a>5.2.3.2 Content Profile Semantics</h5></div><div class="div4">
+<h5><a id="vocabulary-processor-profile-processing"></a>5.2.3.3 Processor Profile Semantics</h5><p>The profile of TTML that must be supported by a
 TTML <a href="#terms-content-processor">content processor</a> in order to process a <a href="#terms-document-instance">document instance</a> is determined either (1) by specifying a
 <code>ttp:profile</code> attribute on the root <code>tt</code> element, as
 defined by <a href="#parameter-attribute-profile"><b>6.2.9 ttp:profile</b></a>, or (2) by
@@ -1000,7 +1037,8 @@
 referring to a profile) by means of a <a href="#parameter-vocabulary-extension"><code>ttp:extension</code></a>
 element where the value of its <code>value</code> attribute is
 <code>required</code> or <code>use</code>,
-respectively.</p></div><p>An example of an author defined
+respectively.</p></div></div></div><div class="div3">
+<h4><a id="vocabulary-profile-examples"></a>5.2.4 Profile Examples</h4><p>An example of an author defined
 additive, derived profile of the TTML Presentation
 profile is shown
 below in <a href="#ttml-example-sub-profile"><b>Example Fragment – TTML Additive Profile</b></a>.</p><a id="ttml-example-sub-profile"></a><table class="example"><caption>Example Fragment – TTML Additive Profile</caption><tbody><tr><td>
@@ -1021,7 +1059,7 @@
 <code>#fontStyle-italic</code> feature required (rather than
 optional as it is defined
 in <a href="#profile-ttml2-presentation"><b>F.2 TTML2 Presentation Profile</b></a>). Note also the resetting of the
-default XMLNS binding on the <code>profile</code> element to the TT Parameter Namespace.</p></div></div><div class="div2">
+default XMLNS binding on the <code>profile</code> element to the TT Parameter Namespace.</p></div></div></div><div class="div2">
 <h3><a id="vocabulary-overview"></a>5.3 Catalog</h3><p>The vocabulary of the Timed Text Markup Language (TTML) is
 defined in the following major catalogs (divisions of vocabulary):</p><ul><li><p><a href="#core-vocabulary-overview"><b>5.3.1 Core Catalog</b></a></p></li><li><p><a href="#extension-vocabulary-overview"><b>5.3.2 Extension Catalog</b></a></p></li></ul><p>The core catalog defines the baseline, core vocabulary of TTML,
 and, in particular, the vocabulary of TTML Content. The extension catalog
@@ -1211,15 +1249,18 @@
 <h3><a id="parameter-element-vocabulary"></a>6.1 Parameter Element Vocabulary</h3><p>The following elements, all defined in the TT Parameter
 Namespace, specify parametric information that applies to a <a href="#terms-document-instance">document instance</a>
 or <a href="#terms-content-processor">content processor</a>:</p><ul><li><p><a href="#parameter-vocabulary-profile"><b>6.1.1 ttp:profile</b></a></p></li><li><p><a href="#parameter-vocabulary-features"><b>6.1.2 ttp:features</b></a></p></li><li><p><a href="#parameter-vocabulary-feature"><b>6.1.3 ttp:feature</b></a></p></li><li><p><a href="#parameter-vocabulary-extensions"><b>6.1.4 ttp:extensions</b></a></p></li><li><p><a href="#parameter-vocabulary-extension"><b>6.1.5 ttp:extension</b></a></p></li></ul><div class="div3">
-<h4><a id="parameter-vocabulary-profile"></a>6.1.1 ttp:profile</h4><p>The <code>ttp:profile</code> element is used to specify a collection of
-used (mandatory and enabled), required (mandatory),
-and optional (voluntary) features and extensions that must or
+<h4><a id="parameter-vocabulary-profile"></a>6.1.1 ttp:profile</h4><p>The <code>ttp:profile</code> element is used to specify a
+<a href="#terms-processor-profile">processor profile</a> or a
+<a href="#terms-content-profile">content profile</a>.
+A <a href="#terms-processor-profile">processor profile</a> specifies a
+collection of required (mandatory) and optional (voluntary) features and extensions that must or
 may be supported by a <a href="#terms-content-processor">content processor</a> in order to process a
 <a href="#terms-document-instance">document instance</a> that makes (or may make) use of such features and
-extensions. In addition, a feature or extension may be specified as
-prohibited, in which case it must not appear (be specified) in
-a <a href="#terms-document-instance">document instance</a>, and, if it does appear, may result in
-the <a href="#terms-document-instance">document instance</a> being rejected or processing otherwise aborted.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The difference between a <em>feature</em> and an
+extensions.
+A <a href="#terms-content-profile">content profile</a> specifies a
+collection of required, optional, and prohibited features and extensions that, respectively,
+must, may, and must not be present in a <a href="#terms-document-instance">document instance</a> that declares its
+adherence to the profile.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The difference between a <em>feature</em> and an
 <em>extension</em> is where it is defined and how it is labeled:
 if defined in this specification (or a future revision thereof) and
 labeled with a feature designation in <a href="#features"><b>D Features</b></a>, then
@@ -1227,7 +1268,7 @@
 and labeled there with an extension designation, then it is considered
 to be an extension. In general, features are expected to be defined by
 the W3C standards process, while extensions are expected to be defined by
-third parties.</p></div><p>This specification defines two distinct uses of the <code>ttp:profile</code> element:</p><ul><li><p>as a child of the <code>head</code> element within a TTML <a href="#terms-document-instance">document instance</a>;</p></li><li><p>as the root element of a TTML <a href="#terms-profile-definition-document">profile definition document</a>
+third parties.</p></div><p>This specification defines two distinct contexts of use of the <code>ttp:profile</code> element:</p><ul><li><p>as a child of the <code>head</code> element within a TTML <a href="#terms-document-instance">document instance</a>;</p></li><li><p>as the root element of a TTML <a href="#terms-profile-definition-document">profile definition document</a>
 instance;</p></li></ul><p>When a <code>ttp:profile</code> element appears within a TTML <a href="#terms-document-instance">document instance</a>,
 its purpose is to express authorial intentions about which
 features and extensions must or may be supported by a recipient
@@ -1247,13 +1288,18 @@
 &lt;ttp:profile
   combine = (replace|union|intersection) : replace
   designator = string
+  type = (processor|content) : processor
   use = string
   <a href="#content-attribute-id">xml:id</a> = ID
   {<em>any attribute not in default or any TT namespace</em>}&gt;
   <em>Content:</em> <a href="#element-vocab-group-table">Metadata.class</a>*, <a href="#parameter-vocabulary-features">ttp:features</a>*, <a href="#parameter-vocabulary-extensions">ttp:extensions</a>*
 &lt;/ttp:profile&gt;
 </pre></div>
-</td></tr></tbody></table><p>The <code>combine</code> attribute may be used to specify how
+</td></tr></tbody></table><p>The <code>type</code> attribute is used to determine whether a profile is a
+<a href="#terms-processor-profile">processor profile</a> or a
+<a href="#terms-content-profile">content profile</a>. If not specified,
+the profile is considered to be a <a href="#terms-processor-profile">processor profile</a>.
+</p><p>The <code>combine</code> attribute may be used to specify how
 feature or extension specifications are combined in the case that
 multiple specifications apply to the same feature or extension, respectively.
 If the value of the <code>combine</code> attribute is <code>replace</code>, then a
@@ -2407,7 +2453,8 @@
 then the border width must be interpreted as if a width of
 <code>medium</code> were specified.</p><p>If a computed value of the border width 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
-the computed border width and the supported border width is minimized.</p></div><p>If no border style is specified in the value of the <code>tts:border</code> property,
+the computed border width and the supported border width is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value most distant from 0, i.e., the greatest border width, is used.</p></div><p>If no border style is specified in the value of the <code>tts:border</code> property,
 then the border style must be interpreted as if a style of
 <code>none</code> were specified.</p><p>If a computed value of the border style associated with this attribute is not supported,
 then a <a href="#terms-presentation-processor">presentation processor</a> must use the value <code>solid</code>.</p><p>If no border color is specified in the value of the <code>tts:border</code> property,
@@ -2633,7 +2680,8 @@
 the width and height must be expressed in terms of two <a href="#style-value-length">&lt;length&gt;</a> specifications,
 and these specifications must be expressed as non-percentage, definite lengths using pixel units.</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
-the computed extent and the supported extent is minimized.</p></div><p>The <code>tts:extent</code> style is illustrated by the following example.</p><a id="style-attribute-extent-example-1"></a><table class="example"><caption>Example Fragment – Extent</caption><tbody><tr><td>
+the computed extent and the supported extent is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value most distant from [0,0], i.e., of greatest extent, is used.</p></div><p>The <code>tts:extent</code> style is illustrated by the following example.</p><a id="style-attribute-extent-example-1"></a><table class="example"><caption>Example Fragment – Extent</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style <span class="strong">tts:extent="330px 122px"</span>/&gt;
@@ -2661,6 +2709,7 @@
 (<code>","</code>
 &nbsp;(<a href="#style-value-familyName">&lt;familyName&gt;</a> | <a href="#style-value-genericFamilyName">&lt;genericFamilyName&gt;</a>))*
 </td></tr><tr><td><em>Initial:</em></td><td><code>default</code></td></tr><tr><td><em>Applies to:</em></td><td>
+<a href="#content-vocabulary-p"><code>p</code></a>,
 <a href="#content-vocabulary-span"><code>span</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The initial value, <code>default</code>, is a generic font family name, and is
 further described in <a href="#style-value-genericFamilyName"><b>8.3.9 &lt;genericFamilyName&gt;</b></a> below.</p></div><p>For the purpose of determining applicability of this style property,
@@ -2705,6 +2754,7 @@
 as a style property only to those element types indicated in the following table.</p><a id="style-property-details-fontSize"></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> <a href="#style-value-length">&lt;length&gt;</a>?
 </td></tr><tr><td><em>Initial:</em></td><td><code>1c</code></td></tr><tr><td><em>Applies to:</em></td><td>
+<a href="#content-vocabulary-p"><code>p</code></a>,
 <a href="#content-vocabulary-span"><code>span</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>if not <a href="#content-vocabulary-span"><code>region</code></a> element,
 then relative to parent element's font size; otherwise, relative to the
@@ -2719,7 +2769,9 @@
 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 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
-the computed font size and the supported font size is minimized.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
+the computed font size and the supported font size is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value most distant from 0 (single length specification) or [0,0] (two length specifications) is used,
+i.e., the largest font size, is used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
 the <em>cell</em> length unit as defined by <a href="#style-value-length"><b>8.3.12 &lt;length&gt;</b></a>.
 When a single &lt;length&gt; is expressed using cell units, then it refers to the height of
 the <a href="#terms-computed-cell-size">computed cell size</a>.
@@ -2760,6 +2812,7 @@
 <code>italic</code> |
 <code>oblique</code>
 </td></tr><tr><td><em>Initial:</em></td><td><code>normal</code></td></tr><tr><td><em>Applies to:</em></td><td>
+<a href="#content-vocabulary-p"><code>p</code></a>,
 <a href="#content-vocabulary-span"><code>span</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</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
@@ -2796,6 +2849,7 @@
 <code>normal</code> |
 <code>bold</code>
 </td></tr><tr><td><em>Initial:</em></td><td><code>normal</code></td></tr><tr><td><em>Applies to:</em></td><td>
+<a href="#content-vocabulary-p"><code>p</code></a>,
 <a href="#content-vocabulary-span"><code>span</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</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
@@ -2831,13 +2885,31 @@
 </td></tr><tr><td><em>Initial:</em></td><td><code>normal</code></td></tr><tr><td><em>Applies to:</em></td><td>
 <a href="#content-vocabulary-p"><code>p</code></a>
 </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</td></tr></tbody></table><p>If the value of this attribute is <code>normal</code>, then the
-computed value of the style property must be considered to be the same
-as 125% of the largest font size that applies to the element and its
-descendant elements in the intermediate synchronic document as determined by
-<a href="#semantics-region-layout-step-1"><b>9.3.3 Intermediate Synchronic Document Construction</b></a>.</p><p>If specified as a <a href="#style-value-length">&lt;length&gt;</a>, then the length must
+computed value of this style property is determined as follows:</p><ol class="enumar"><li><p>
+Let <em>P</em> be the <code>p</code> element to which this style property applies.
+</p></li><li><p>
+Let <em>FF</em> be the computed value of the <code>tts:fontFamily</code> style property that applies to <em>P</em>.
+</p></li><li><p>
+Let <em>FS</em> be the computed value of the <code>tts:fontSize</code> style property that applies to <em>P</em>.
+</p></li><li><p>
+Let <em>F0</em> be the first font obtained when sequentially mapping each font family in <em>FF</em> to a set of available fonts,
+where this set of available fonts is constrained as needed to satisfy the computed values of the <code>tts:fontStyle</code> and <code>tts:fontWeight</code>
+style properties that apply to <em>P</em>.
+</p></li><li><p>
+If <em>F0</em> is associated with font metrics that specify altitude <em>A</em>, descent <em>D</em>, and line gap <em>G</em>,
+then set <em>LH</em> to the sum of scaled(<em>A</em>), scaled(<em>D</em>), and scaled(<em>G</em>),
+where scaled(<em>X</em>) denotes font metric <em>X</em> scaled according to font size <em>FS</em>.
+</p></li><li><p>
+Otherwise, set <em>LH</em> to 125% of <em>FS</em>.
+</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 
+<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
-the computed line height and the supported line height is minimized.</p></div><p>The <code>tts:lineHeight</code> style is illustrated by the following example.</p><a id="style-attribute-lineHeight-example-1"></a><table class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
+the computed line height and the supported line height is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value most distant from 0, i.e., the largest line height, is used.</p></div><p>The <code>tts:lineHeight</code> style is illustrated by the following example.</p><a id="style-attribute-lineHeight-example-1"></a><table class="example"><caption>Example Fragment – Line Height</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="255px 190px"/&gt;
@@ -2929,7 +3001,8 @@
 is the <em>x</em> coordinate, and the second specification is the <em>y</em> coordinate.</p><p>If 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 origin of the <a href="#terms-root-container-region">root container region</a>.</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
-the computed origin and the supported origin is minimized.</p></div><p>The <code>tts:origin</code> style is illustrated by the following example.</p><a id="style-attribute-origin-example-1"></a><table class="example"><caption>Example Fragment – Origin</caption><tbody><tr><td>
+the computed origin and the supported origin is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value least distant from [0,0], i.e., closest to the coordinate space origin, is used.</p></div><p>The <code>tts:origin</code> style is illustrated by the following example.</p><a id="style-attribute-origin-example-1"></a><table class="example"><caption>Example Fragment – Origin</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style <span class="strong">tts:origin="40px 40px"</span>/&gt;
@@ -3035,7 +3108,8 @@
 If four <a href="#style-value-length">&lt;length&gt;</a> specifications are provided, then they apply to before, end,
 after, and start edges, respectively.</p><p>The <a href="#style-value-length">&lt;length&gt;</a> value(s) used to express padding 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
-the computed padding and the supported padding is minimized.</p></div><p>The <code>tts:padding</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Enhance Padding Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Enhance Padding Example</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Enhance padding example to demonstrate padding on content elements.</td></tr></table><p></p><a id="style-attribute-padding-example-1"></a><table class="example"><caption>Example Fragment – Padding</caption><tbody><tr><td>
+the computed padding and the supported padding is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value most distant from 0, i.e., the greatest padding, is used.</p></div><p>The <code>tts:padding</code> style is illustrated by the following example.</p><table border="1" class="ednote" summary="Editorial note: Enhance Padding Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Enhance Padding Example</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Enhance padding example to demonstrate padding on content elements.</td></tr></table><p></p><a id="style-attribute-padding-example-1"></a><table class="example"><caption>Example Fragment – Padding</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:extent="446px 104px"/&gt;
@@ -3199,8 +3273,10 @@
 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-textOrientation"></a><table class="common"><col width="25%" span="1"><col span="1"><tbody><tr><td><em>Values:</em></td><td>
 <code>mixed</code> |
-<code>upright</code> |
-<code>sideways</code>
+<code>sideways</code> |
+<code>sidewaysLeft</code> |
+<code>sidewaysRight</code> |
+<code>upright</code>
 </td></tr><tr><td><em>Initial:</em></td><td><code>mixed</code></td></tr><tr><td><em>Applies to:</em></td><td>
 <a href="#content-vocabulary-span"><code>span</code></a>
 </td></tr><tr><td><em>Inherited:</em></td><td>yes</td></tr><tr><td><em>Percentages:</em></td><td>N/A</td></tr><tr><td><em>Animatable:</em></td><td>discrete</td></tr></tbody></table><p>For the purpose of determining applicability of this style property,
@@ -3208,17 +3284,19 @@
 span.</p><p>If the value of this attribute is <code>mixed</code>, then, in vertical writing modes,
 glyphs from horizontal scripts are set sideways, i.e., 90° clockwise from
 their nominal orientation in horizontal text, while glyphs from vertical scripts are not
+affected.</p><p>If the value of this attribute is <code>sidewaysLeft</code>, then, in vertical writing modes,
+glyphs from horizontal scripts are set sideways with 90° counter-clockwise rotation.</p><p>If the value of this attribute is <code>sidewaysRight</code>, then, in vertical writing modes,
+glyphs from horizontal scripts are set sideways with 90° clockwise rotation.</p><p>If the value of this attribute is <code>sideways</code>, then, in vertical writing modes,
+glyphs from horizontal scripts are set sideways, either 90° clockwise or
+90° counter-clockwise, according to whether the writing mode is
+<code>tbrl</code> or <code>tblr</code>, respectively. Glyphs from vertical scripts are not
 affected.</p><p>If the value of this attribute is <code>upright</code>, then, in vertical writing modes,
 glyphs from horizontal scripts are set upright, i.e., using their
 nominal orientation in horizontal text, while glyphs from vertical scripts are not
 affected. In addition, for purposes of bidirectional processing, this value causes all
 affected characters to be treated as strong left-to-right, i.e., to be treated as if
 a <code>tts:direction</code> of <code>ltr</code> and <code>tts:unicodeOverride</code> of
-<code>override</code> were applied.</p><p>If the value of this attribute is <code>sideways</code>, then, in vertical writing modes,
-glyphs from horizontal scripts are set sideways, either 90° clockwise or
-90° counter-clockwise, according to whether the writing mode is
-<code>tbrl</code> or <code>tblr</code>, respectively. Glyphs from vertical scripts are not
-affected.</p><p>If a vertical writing mode does not apply, then this style property has no effect.</p><p>If a computed value of the property associated with this attribute is not supported,
+<code>override</code> were applied.</p><p>If a vertical writing mode does not apply, then this style property has no effect.</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>mixed</code>.</p><p>The <code>tts:textOrientation</code> style is illustrated by the following
 example.</p><table border="1" class="ednote" summary="Editorial note: Text Orientation Example"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Text Orientation Example</b></td><td align="right" valign="top">2013-08-24</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Insert example fragment and image of text orientation.</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 Level 3]</a>,
@@ -3467,7 +3545,8 @@
 <a href="#xsl11">[XSL 1.1]</a>, § 7.30.18, where the <code>tt</code> element
 is considered to establish the root stacking context.</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
-the computed z-index and the supported z-index is minimized.</p></div><p>The <code>tts:zIndex</code> style is illustrated by the following example.</p><a id="style-attribute-zIndex-example-1"></a><table class="example"><caption>Example Fragment – Z Index</caption><tbody><tr><td>
+the computed z-index and the supported z-index is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value least distant from 0, i.e., closest to the base stack level of the current stacking context, is used.</p></div><p>The <code>tts:zIndex</code> style is illustrated by the following example.</p><a id="style-attribute-zIndex-example-1"></a><table class="example"><caption>Example Fragment – Z Index</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;region xml:id="r1"&gt;
   &lt;style tts:origin="0px 0px"/&gt;
@@ -3544,7 +3623,8 @@
 less than 0, or greater than 1.</p><p>If a <a href="#terms-presentation-processor">presentation processor</a> does not support a specific,
 valid opacity value, then it must interpret it as being equal to 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
-the computed opacity and the supported opacity is minimized.</p></div></div><div class="div3">
+the computed opacity and the supported opacity is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value most distant from 0, i.e., the greatest opacity, is used.</p></div></div><div class="div3">
 <h4><a id="style-value-border-color"></a>8.3.2 &lt;border-color&gt;</h4><p>A &lt;border-color&gt; expression is used to express the color of one
 or more borders.</p><a id="border-color-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;border-color&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
@@ -3619,7 +3699,8 @@
 used here to the YUV color space for rendition on a television device.</p></div><p>If a <a href="#terms-presentation-processor">presentation processor</a> does not support a specific,
 valid color or alpha value, then it must interpret it as being equal
 to 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
-the computed color or alpha and the supported color or alpha in the RGB color space is minimized.</p></div></div><div class="div3">
+the computed color and alpha and the supported color and alpha in the RGB color space is minimized. If there are multiple closest supported values equally distant from
+the computed value, then the value least distant from opaque black <code>rgb(0,0,0,255)</code>, i.e., the closest to opaque black, is used.</p></div></div><div class="div3">
 <h4><a id="style-value-digit"></a>8.3.6 &lt;digit&gt;</h4><p>A &lt;digit&gt; is used to express integers and other types of numbers or tokens.</p><a id="digit-style-expression-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;digit&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;digit&gt;
@@ -4921,7 +5002,11 @@
 &lt;/animate&gt;
 </pre></div>
 </td></tr></tbody></table><p></p><table border="1" class="ednote" summary="Editorial note: Change xlink:href to href"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Change xlink:href to href</b></td><td align="right" valign="top">2013-09-05</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">The SVG WG is deprecating xlink:href, in favor of using an unqualified href attribute. See
-<a href="http://www.w3.org/Graphics/SVG/WG/wiki/Href">SVG Wiki: Href</a>. We should probably just specify the use of unqualified href.</td></tr></table><p>Except for the constraints or variations enumerated below, the semantics of the <code>animate</code> element and its attributes
+<a href="http://www.w3.org/Graphics/SVG/WG/wiki/Href">SVG Wiki: Href</a>. We should probably just specify the use of unqualified href.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Extend style property expression syntax to support multi-valued expressions."><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Extend style property expression syntax to support multi-valued expressions.</b></td><td align="right" valign="top">2013-11-14</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">The <code>animate</code> element will require multi-valued style property expressions.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Remove @accumulate"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Remove @accumulate</b></td><td align="right" valign="top">2013-11-13</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">CSS Animation does not support SVG @accumulate functionality. Consequently, it should be removed from TTML2. It can be re-introduced in
+the feature when CSS adds support for accumulate semantics.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Remove @additive"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Remove @additive</b></td><td align="right" valign="top">2013-11-13</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">CSS Animation does not support SVG @additive functionality. Consequently, it should be removed from TTML2. It can be re-introduced in
+the feature when CSS adds support for additive semantics.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Remove @attributeName"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Remove @attributeName</b></td><td align="right" valign="top">2013-11-14</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Use only style value expression syntax introduced by TTML1.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Remove @by, @from, @to, @values"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Remove @by, @from, @to, @values</b></td><td align="right" valign="top">2013-11-14</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">Use of @by, @from, @to, and @values can be expressed by multi-valued style property expression.</td></tr></table><p></p><table border="1" class="ednote" summary="Editorial note: Remove @repeatDur"><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Remove @repeatDur</b></td><td align="right" valign="top">2013-11-13</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">CSS Animation does not support a repeat duration parameter on an animation; however, it supports non-integer values of
+repeat count (via <code>animation-iteration-count</code>). Since the duration of a single animation iteration is known, it is
+straightforward to map @repeatDur to an appropriate non-integer repeat count.</td></tr></table><p>Except for the constraints or variations enumerated below, the semantics of the <code>animate</code> element and its attributes
 enumerated above are defined to be those specified by <a href="#svg11">[SVG 1.1]</a>, §19.2.12:</p><ol class="enumar"><li><p>For the purpose of interpreting an <code>attributeName</code> attribute, an <code>attributeType</code>
 with a value of <code>XML</code> applies, about which see <a href="#svg11">[SVG 1.1]</a>, §19.2.5.</p></li><li><p>If no <code>accumulate</code> attribute is specified, then an <em>accumlate</em> value of <code>none</code> applies.</p></li><li><p>If no <code>additive</code> attribute is specified, then an <em>additive</em> value of <code>replace</code> applies.</p></li><li><p>If no <code>calcMode</code> attribute is specified, then a <em>calcMode</em> value of <code>linear</code> applies.</p></li><li><p>If no <code>fill</code> attribute is specified, then a <em>fill</em> value of <code>remove</code> applies.</p></li><li><p>If an <code>xlink:href</code> attribute is specified, then the <code>animate</code> element must be a child of an
 <a href="#animation-vocabulary-animation">animation</a> element; conversely, if an <code>animate</code> element is a child of
@@ -5084,11 +5169,12 @@
 &lt;calcMode&gt;
   : "discrete"
   | "linear"
-  | "displaced"
+  | "paced"
   | "spline"
 </pre></div>
 </td></tr></tbody></table><p>The semantics of a &lt;calcMode&gt; expression are those defined by
-<a href="#svg11">[SVG 1.1]</a>, §19.2.9.</p></div><div class="div3">
+<a href="#svg11">[SVG 1.1]</a>, §19.2.9.</p><p></p><table border="1" class="ednote" summary="Editorial note: Consider removing support for paced."><tr class="ednote-r1"><td align="left" valign="top"><b>Editorial note: Consider removing support for paced.</b></td><td align="right" valign="top">2013-11-14</td></tr><tr class="ednote-r2"><td colspan="2" align="left" valign="top">CSS Animations doesn't directly support paced values; however, it is possible to translate a paced timing function to a linear function
+with explicit @keyTimes.</td></tr></table></div><div class="div3">
 <h4><a id="animation-value-fill"></a>11.3.6 &lt;fill&gt;</h4><p>A &lt;fill&gt; expression is used to determine effect of the animation after the active end of the animation.</p><a id="fill-syntax"></a><table class="syntax"><caption>Syntax Representation – &lt;fill&gt;</caption><tbody><tr><td>
 <div class="exampleInner"><pre>
 &lt;fill&gt;
@@ -7111,7 +7197,7 @@
 <h2><a id="derivation"></a>J Vocabulary Derivation (Non-Normative)</h2><p>This appendix provides information about the derivation of TTML
 vocabulary, separately describing derivation of elements and
 attributes.</p><div class="div2">
-<h3><a id="d3e21921"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-1 – Elements</b></a>
+<h3><a id="d3e22290"></a>J.1 Element Derivation</h3><p>The first column of <a href="#element-vocab-derivation-table"><b>Table J-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
@@ -7168,7 +7254,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 targetted elements.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e22438"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-2 – Attributes</b></a>
+<h3><a id="d3e22807"></a>J.2 Attribute Derivation</h3><p>The first column of <a href="#attribute-vocab-derivation-table"><b>Table J-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
@@ -7260,9 +7346,9 @@
 <h2><a id="qa"></a>K 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="d3e23431"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-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="d3e23800"></a>K.1 Requirements</h3><a id="qa-framework-requirements-table"></a><table class="common"><caption>Table K-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="d3e23595"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-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-profiles">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="d3e23964"></a>K.2 Guidelines</h3><a id="qa-framework-guidelines-table"></a><table class="common"><caption>Table K-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-profiles">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>J 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">
--- a/ttml2/spec/ttml2.xml	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml2/spec/ttml2.xml	Wed Dec 11 15:35:35 2013 -0500
@@ -539,6 +539,12 @@
 Sets</emph> <bibref ref="infoset"/>.</p>
 </def>
 </gitem>
+<gitem id="terms-anonymous-profile">
+<label>[anonymous profile]</label>
+<def>
+<p>See <loc href="#terms-undesignated-profile">undesignated profile</loc>.</p>
+</def>
+</gitem>
 <gitem id="terms-attribute-information-item">
 <label>[attribute information item]</label>
 <def>
@@ -578,7 +584,7 @@
 <gitem id="terms-content-profile">
 <label>[content profile]</label>
 <def>
-<p>A collection of <loc href="#terms-feature">features</loc> and <loc href="#terms-extension">extensions</loc> that are (or may be) employed by
+<p>A collection of <loc href="#terms-feature">features</loc> and <loc href="#terms-extension">extensions</loc> that must, may, or must not be employed by
 Timed Text Markup Language content.</p>
 <ednote>
 <name>Content Profile</name>
@@ -598,7 +604,8 @@
 <gitem id="terms-designated-profile">
 <label>[designated profile]</label>
 <def>
-<p>&tbd;</p>
+<p>A <loc href="#terms-profile">profile</loc> that is associated with a <loc href="#terms-profile-designator">profile designator</loc> by
+means of a <att>designator</att> attribute or prose text in a specification of profile.</p>
 </def>
 </gitem>
 <gitem id="terms-document-instance">
@@ -656,6 +663,13 @@
 future revision of this specification).</p>
 </def>
 </gitem>
+<gitem id="terms-fragment-identifier">
+<label>[fragment identifier]</label>
+<def>
+<p>A syntactic expression that adheres to the fragment identifer syntax defined by <bibref ref="uri"/>,
+Section 4.1.</p>
+</def>
+</gitem>
 <gitem id="terms-inline-animation">
 <label>[inline animation]</label>
 <def>
@@ -730,12 +744,31 @@
 <p></p>
 </def>
 </gitem>
+<gitem id="terms-profile">
+<label>[profile]</label>
+<def>
+<p>A <loc href="#terms-content-profile">content profile</loc> or <loc href="#terms-processor-profile">processor profile</loc>.</p>
+</def>
+</gitem>
 <gitem id="terms-profile-definition-document">
 <label>[profile definition document]</label>
 <def>
-<p>A document that defines a specific collection of <loc href="#terms-feature">features</loc> and <loc href="#terms-extension">extensions</loc>
-for which support is required or optional in a recipient content
-processor.</p>
+<p>A document that formally specifies a <loc href="#terms-profile">profile</loc>, where such document is a valid TTML document instance
+which has a root element type of <el>ttp:profile</el>.</p>
+</def>
+</gitem>
+<gitem id="terms-profile-designator">
+<label>[profile designator]</label>
+<def>
+<p>An absolute URI used to label or reference an externally defined <loc href="#terms-profile">profile</loc>, where
+external refers to being external to a <loc href="#terms-document-instance">document instance</loc>.</p>
+</def>
+</gitem>
+<gitem id="terms-profile-fragment-identifier">
+<label>[profile fragment identifier]</label>
+<def>
+<p>A <loc href="#terms-fragment-identifier">fragment identifier</loc> used to label or reference an internally defined <loc href="#terms-profile">profile</loc>, where
+internal refers to being internal to a <loc href="#terms-document-instance">document instance</loc>.</p>
 </def>
 </gitem>
 <gitem id="terms-region">
@@ -847,7 +880,8 @@
 <gitem id="terms-undesignated-profile">
 <label>[undesignated profile]</label>
 <def>
-<p>&tbd;</p>
+<p>A <loc href="#terms-profile">profile</loc> that is not associated with a <loc href="#terms-profile-designator">profile designator</loc>, and which is
+referred to implicitly in the context of the profile's definition. Also referred to as an <emph>anonymous profile</emph>.</p>
 </def>
 </gitem>
 <gitem id="terms-valid-abstract-document-instance">
@@ -1290,10 +1324,74 @@
 </div2>
 <div2 id="vocabulary-profiles">
 <head>Profiles</head>
+
+<p>This section describes the TTML profiling sub-system and high level requirements that apply to this sub-system. At the end of this section
+appears a sub-section containing examples of profile specifications and examples of how these specifications are referenced and used.</p>
+
+<div3 id="vocabulary-profile-introduction">
+<head>Introduction</head>
+
+<p><emph>This sub-section is non-normative.</emph></p>
+
+<p>A given profile may be used by a Timed Text Markup Language content author for one of two functions: (1) to declare that a
+<loc href="#terms-document-instance">document instance</loc> adheres to a collection of constraints on what
+vocabulary is used and how it is used, or (2) to declare that a <loc href="#terms-processor">processor</loc> must satisfy certain conditions on how
+content is processed. The first of these functions is termed a <loc href="#terms-content-profile">content profile</loc>, while
+the second is termed a <loc href="#terms-processor-profile">processor profile</loc>.</p>
+
+<p>A <loc href="#terms-content-profile">content profile</loc> is generally used to allow an author to declare, at authoring time,
+what constraints the author intends to apply to a <loc href="#terms-document-instance">document instance</loc>. Such a
+declaration permits downstream processors to perform content validation or verification, as well as to guide or limit subsequent
+transformation or editing of content in order to maintain adherence to an author specified content profile. In addition, a
+downstream processor may use a content profile declaration to perform an early determination of its ability to process the features
+implied by the content profile.</p>
+
+<p>A <loc href="#terms-processor-profile">processor profile</loc> is generally used to allow an author to declare, at authoring time,
+what processing must be supported when processing a <loc href="#terms-document-instance">document instance</loc>, such that, if a
+processor is not able to perform the indicated processing, then processing should be aborted. Such a declaration permits downstream
+processors to avoid processing content that cannot be processed in a manner that meets the requirements of the content author.</p>
+
+<p>A content author is not limited to using a single profile, but may make reference to multiple profiles of either type, i.e.,
+multiple content profiles and/or multiple processor profiles. When multiple profiles are referenced, their respective specifications
+are combined to form a single effective content profile that applies to the document and a single effective processor profile
+that applies to a processor when processing the document. In addition, an author is not limited to making reference to externally
+defined profiles, but may define one or more profiles inline within a document.</p>
+
+</div3>
+
+<div3 id="vocabulary-profile-designators">
+<head>Profile Designators</head>
+
+<p>A profile is referenced in one of two ways according to whether the profile is defined externally to the referring document or
+is defined inline within the referring document. When defined externally, a profile is referenced by means of a
+<loc href="#terms-profile-designator">profile designator</loc>. When defined internally (inline), a profile is referenced either implicitly
+or by means of <loc href="#terms-profile-fragment-identifier">profile fragment identifier</loc>.</p>
+
+<p>A profile designator must adhere to the
+<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
+&sect;3.2.17. If the profile designator is expressed as a relative URI,
+then it must be absolutized by using the TT Profile Namespace value as
+the base URI.</p>
+<note role="example">
+<p>For example, if a profile designator is expressed as
+<code>ttml2-presentation</code>, then the absolutized profile designator
+would be
+<code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code>.</p>
+</note>
+<p>All profile designators which have the TT Profile Namespace as a prefix but are otherwise not listed in
+<specref ref="profile-vocab-table"/> are reserved for future standardization, and must not appear in a conformant
+<loc href="#terms-document-instance">document instance</loc>. Nothwithstanding this constraint, a profile designator is not restricted to the set of designators enumerated
+in <specref ref="profile-vocab-table"/>, but may be any URI that feasibly dereferences a TTML <loc href="#terms-profile-definition-document">profile definition document</loc>
+provided it does not use the TT Profile Namespace as a prefix.</p>
+
+<div4 id="vocabulary-profile-standard-designators">
+<head>Standard Designators</head>
+
 <p>The Timed Text Markup Language (TTML) employs a number of
 standard, predefined profiles of its
-vocabulary and associated semantics.
-The following table specifies this set of
+vocabulary and associated semantics.</p>
+
+<p>The following table specifies this set of
 profiles, indicating
 a normative name
 and designator for each
@@ -1343,28 +1441,26 @@
 <note role="seealso">
 <p>For definitions of the DFXP profiles, see <bibref ref="ttml1"/>. For definition of the SDP US profile, see <bibref ref="sdpus"/>.</p>
 </note>
-<ednote>
-<name>Referencing Undesignated Profile</name>
-<date>2013-09-05</date>
-<edtext>Need to update following to allow referring to a local (embedded) profile definition using
-a fragment identifier that references an undesignated ttp:profile element rather than a profile designator URI.</edtext>
-</ednote>
-<p>A profile designator must adhere to the
-<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-&sect;3.2.17. If the profile designator is expressed as a relative URI,
-then it must be absolutized by using the TT Profile Namespace value as
-the base URI.</p>
-<note role="example">
-<p>For example, if a profile designator is expressed as
-<code>ttml2-presentation</code>, then the absolutized profile designator
-would be
-<code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code>.</p>
-</note>
-<p>All profile designators which have the TT Profile Namespace as a prefix but are otherwise not listed in
-<specref ref="profile-vocab-table"/> are reserved for future standardization, and must not be appear in a conformant
-<loc href="#terms-document-instance">document instance</loc>. Nothwithstanding this constraint, a profile designator is not restricted to the set of designators enumerated
-in <specref ref="profile-vocab-table"/>, but may be any URI that feasibly dereferences a TTML <loc href="#terms-profile-definition-document">profile definition document</loc>
-provided it does not use the TT Profile Namespace as a prefix.</p>
+</div4>
+
+</div3>
+
+<div3 id="vocabulary-profile-semantics">
+<head>Profile Semantics</head>
+
+<div4 id="vocabulary-profile-combination">
+<head>Profile Combination</head>
+
+</div4>
+
+<div4 id="vocabulary-content-profile-processing">
+<head>Content Profile Semantics</head>
+
+</div4>
+
+<div4 id="vocabulary-processor-profile-processing">
+<head>Processor Profile Semantics</head>
+
 <p>The profile of TTML that must be supported by a
 TTML <loc href="#terms-content-processor">content processor</loc> in order to process a <loc href="#terms-document-instance">document instance</loc> is determined either (1) by specifying a
 <att>ttp:profile</att> attribute on the root <el>tt</el> element, as
@@ -1467,6 +1563,14 @@
 <code>required</code> or <code>use</code>,
 respectively.</p>
 </note>
+
+</div4>
+
+</div3>
+
+<div3 id="vocabulary-profile-examples">
+<head>Profile Examples</head>
+
 <p>An example of an author defined
 additive, derived profile of the TTML Presentation
 profile is shown
@@ -1499,6 +1603,9 @@
 in <specref ref="profile-ttml2-presentation"/>). Note also the resetting of the
 default XMLNS binding on the <el>profile</el> element to the TT Parameter Namespace.</p>
 </note>
+
+</div3>
+
 </div2>
 <div2 id="vocabulary-overview">
 <head>Catalog</head>
@@ -1860,15 +1967,18 @@
 </ulist>
 <div3 id="parameter-vocabulary-profile">
 <head>ttp:profile</head>
-<p>The <el>ttp:profile</el> element is used to specify a collection of
-used (mandatory and enabled), required (mandatory),
-and optional (voluntary) features and extensions that must or
+<p>The <el>ttp:profile</el> element is used to specify a
+<loc href="#terms-processor-profile">processor profile</loc> or a
+<loc href="#terms-content-profile">content profile</loc>.
+A <loc href="#terms-processor-profile">processor profile</loc> specifies a
+collection of required (mandatory) and optional (voluntary) features and extensions that must or
 may be supported by a <loc href="#terms-content-processor">content processor</loc> in order to process a
 <loc href="#terms-document-instance">document instance</loc> that makes (or may make) use of such features and
-extensions. In addition, a feature or extension may be specified as
-prohibited, in which case it must not appear (be specified) in
-a <loc href="#terms-document-instance">document instance</loc>, and, if it does appear, may result in
-the <loc href="#terms-document-instance">document instance</loc> being rejected or processing otherwise aborted.</p>
+extensions.
+A <loc href="#terms-content-profile">content profile</loc> specifies a
+collection of required, optional, and prohibited features and extensions that, respectively,
+must, may, and must not be present in a <loc href="#terms-document-instance">document instance</loc> that declares its
+adherence to the profile.</p>
 <note role="clarification">
 <p>The difference between a <emph>feature</emph> and an
 <emph>extension</emph> is where it is defined and how it is labeled:
@@ -1880,7 +1990,7 @@
 the W3C standards process, while extensions are expected to be defined by
 third parties.</p>
 </note>
-<p>This specification defines two distinct uses of the <el>ttp:profile</el> element:</p>
+<p>This specification defines two distinct contexts of use of the <el>ttp:profile</el> element:</p>
 <ulist>
 <item>
 <p>as a child of the <el>head</el> element within a TTML <loc href="#terms-document-instance">document instance</loc>;</p>
@@ -1916,6 +2026,7 @@
 &lt;ttp:profile
   combine = (replace|union|intersection) : replace
   designator = string
+  type = (processor|content) : processor
   use = string
   <loc href="#content-attribute-id">xml:id</loc> = ID
   {<emph>any attribute not in default or any TT namespace</emph>}&gt;
@@ -1926,6 +2037,11 @@
 </tr>
 </tbody>
 </table>
+<p>The <att>type</att> attribute is used to determine whether a profile is a
+<loc href="#terms-processor-profile">processor profile</loc> or a
+<loc href="#terms-content-profile">content profile</loc>. If not specified,
+the profile is considered to be a <loc href="#terms-processor-profile">processor profile</loc>.
+</p>
 <p>The <att>combine</att> attribute may be used to specify how
 feature or extension specifications are combined in the case that
 multiple specifications apply to the same feature or extension, respectively.
@@ -4600,6 +4716,7 @@
 <tr>
 <td><emph>Applies to:</emph></td>
 <td>
+<loc href="#content-vocabulary-p"><el>p</el></loc>,
 <loc href="#content-vocabulary-span"><el>span</el></loc>
 </td>
 </tr>
@@ -4704,6 +4821,7 @@
 <tr>
 <td><emph>Applies to:</emph></td>
 <td>
+<loc href="#content-vocabulary-p"><el>p</el></loc>,
 <loc href="#content-vocabulary-span"><el>span</el></loc>
 </td>
 </tr>
@@ -4833,6 +4951,7 @@
 <tr>
 <td><emph>Applies to:</emph></td>
 <td>
+<loc href="#content-vocabulary-p"><el>p</el></loc>,
 <loc href="#content-vocabulary-span"><el>span</el></loc>
 </td>
 </tr>
@@ -4928,6 +5047,7 @@
 <tr>
 <td><emph>Applies to:</emph></td>
 <td>
+<loc href="#content-vocabulary-p"><el>p</el></loc>,
 <loc href="#content-vocabulary-span"><el>span</el></loc>
 </td>
 </tr>
@@ -5036,10 +5156,39 @@
 </tbody>
 </table>
 <p>If the value of this attribute is <code>normal</code>, then the
-computed value of the style property must be considered to be the same
-as 125% of the largest font size that applies to the element and its
-descendant elements in the intermediate synchronic document as determined by
-<specref ref="semantics-region-layout-step-1"/>.</p>
+computed value of this style property is determined as follows:</p>
+<olist>
+<item><p>
+Let <emph>P</emph> be the <el>p</el> element to which this style property applies.
+</p></item>
+<item><p>
+Let <emph>FF</emph> be the computed value of the <att>tts:fontFamily</att> style property that applies to <emph>P</emph>.
+</p></item>
+<item><p>
+Let <emph>FS</emph> be the computed value of the <att>tts:fontSize</att> style property that applies to <emph>P</emph>.
+</p></item>
+<item><p>
+Let <emph>F0</emph> be the first font obtained when sequentially mapping each font family in <emph>FF</emph> to a set of available fonts,
+where this set of available fonts is constrained as needed to satisfy the computed values of the <att>tts:fontStyle</att> and <att>tts:fontWeight</att>
+style properties that apply to <emph>P</emph>.
+</p></item>
+<item><p>
+If <emph>F0</emph> is associated with font metrics that specify altitude <emph>A</emph>, descent <emph>D</emph>, and line gap <emph>G</emph>,
+then set <emph>LH</emph> to the sum of scaled(<emph>A</emph>), scaled(<emph>D</emph>), and scaled(<emph>G</emph>),
+where scaled(<emph>X</emph>) denotes font metric <emph>X</emph> scaled according to font size <emph>FS</emph>.
+</p></item>
+<item><p>
+Otherwise, set <emph>LH</emph> to 125% of <emph>FS</emph>.
+</p></item>
+<item><p>
+Set the computed value of this style property to <emph>LH</emph>.
+</p></item>
+</olist>
+<note role="elaboration">
+<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 
+<loc href="#style-value-length">&lt;length&gt;</loc> value expression be used to explicitly specify line height value.</p>
+</note>
 <p>If specified as a <loc
 href="#style-value-length">&lt;length&gt;</loc>, then the length must
 be non-negative.</p>
@@ -5873,8 +6022,10 @@
 <td><emph>Values:</emph></td>
 <td>
 <code>mixed</code> |
-<code>upright</code> |
-<code>sideways</code>
+<code>sideways</code> |
+<code>sidewaysLeft</code> |
+<code>sidewaysRight</code> |
+<code>upright</code>
 </td>
 </tr>
 <tr>
@@ -5908,6 +6059,15 @@
 glyphs from horizontal scripts are set sideways, i.e., 90&deg; clockwise from
 their nominal orientation in horizontal text, while glyphs from vertical scripts are not
 affected.</p>
+<p>If the value of this attribute is <code>sidewaysLeft</code>, then, in vertical writing modes,
+glyphs from horizontal scripts are set sideways with 90&deg; counter-clockwise rotation.</p>
+<p>If the value of this attribute is <code>sidewaysRight</code>, then, in vertical writing modes,
+glyphs from horizontal scripts are set sideways with 90&deg; clockwise rotation.</p>
+<p>If the value of this attribute is <code>sideways</code>, then, in vertical writing modes,
+glyphs from horizontal scripts are set sideways, either 90&deg; clockwise or
+90&deg; counter-clockwise, according to whether the writing mode is
+<code>tbrl</code> or <code>tblr</code>, respectively. Glyphs from vertical scripts are not
+affected.</p>
 <p>If the value of this attribute is <code>upright</code>, then, in vertical writing modes,
 glyphs from horizontal scripts are set upright, i.e., using their
 nominal orientation in horizontal text, while glyphs from vertical scripts are not
@@ -5915,11 +6075,6 @@
 affected characters to be treated as strong left-to-right, i.e., to be treated as if
 a <att>tts:direction</att> of <code>ltr</code> and <att>tts:unicodeOverride</att> of
 <code>override</code> were applied.</p>
-<p>If the value of this attribute is <code>sideways</code>, then, in vertical writing modes,
-glyphs from horizontal scripts are set sideways, either 90&deg; clockwise or
-90&deg; counter-clockwise, according to whether the writing mode is
-<code>tbrl</code> or <code>tblr</code>, respectively. Glyphs from vertical scripts are not
-affected.</p>
 <p>If a vertical writing mode does not apply, then this style property has no effect.</p>
 <p>If a computed value of the property associated with this attribute is not supported,
 then a <loc href="#terms-presentation-processor">presentation processor</loc> must use the value <code>mixed</code>.</p>
@@ -8759,6 +8914,46 @@
 <edtext>The SVG WG is deprecating xlink:href, in favor of using an unqualified href attribute. See
 <loc href="http://www.w3.org/Graphics/SVG/WG/wiki/Href">SVG Wiki: Href</loc>. We should probably just specify the use of unqualified href.</edtext>
 </ednote>
+<p></p>
+<ednote>
+<name>Extend style property expression syntax to support multi-valued expressions.</name>
+<date>2013-11-14</date>
+<edtext>The <code>animate</code> element will require multi-valued style property expressions.</edtext>
+</ednote>
+<p></p>
+<ednote>
+<name>Remove @accumulate</name>
+<date>2013-11-13</date>
+<edtext>CSS Animation does not support SVG @accumulate functionality. Consequently, it should be removed from TTML2. It can be re-introduced in
+the feature when CSS adds support for accumulate semantics.</edtext>
+</ednote>
+<p></p>
+<ednote>
+<name>Remove @additive</name>
+<date>2013-11-13</date>
+<edtext>CSS Animation does not support SVG @additive functionality. Consequently, it should be removed from TTML2. It can be re-introduced in
+the feature when CSS adds support for additive semantics.</edtext>
+</ednote>
+<p></p>
+<ednote>
+<name>Remove @attributeName</name>
+<date>2013-11-14</date>
+<edtext>Use only style value expression syntax introduced by TTML1.</edtext>
+</ednote>
+<p></p>
+<ednote>
+<name>Remove @by, @from, @to, @values</name>
+<date>2013-11-14</date>
+<edtext>Use of @by, @from, @to, and @values can be expressed by multi-valued style property expression.</edtext>
+</ednote>
+<p></p>
+<ednote>
+<name>Remove @repeatDur</name>
+<date>2013-11-13</date>
+<edtext>CSS Animation does not support a repeat duration parameter on an animation; however, it supports non-integer values of
+repeat count (via <code>animation-iteration-count</code>). Since the duration of a single animation iteration is known, it is
+straightforward to map @repeatDur to an appropriate non-integer repeat count.</edtext>
+</ednote>
 <p>Except for the constraints or variations enumerated below, the semantics of the <el>animate</el> element and its attributes
 enumerated above are defined to be those specified by <bibref ref="svg11"/>, &sect;19.2.12:</p>
 <olist>
@@ -9104,7 +9299,7 @@
 &lt;calcMode&gt;
   : "discrete"
   | "linear"
-  | "displaced"
+  | "paced"
   | "spline"
 </eg>
 </td>
@@ -9113,6 +9308,13 @@
 </table>
 <p>The semantics of a &lt;calcMode&gt; expression are those defined by
 <bibref ref="svg11"/>, &sect;19.2.9.</p>
+<p></p>
+<ednote>
+<name>Consider removing support for paced.</name>
+<date>2013-11-14</date>
+<edtext>CSS Animations doesn't directly support paced values; however, it is possible to translate a paced timing function to a linear function
+with explicit @keyTimes.</edtext>
+</ednote>
 </div3>
 <div3 id="animation-value-fill">
 <head>&lt;fill&gt;</head>
--- a/ttml2/spec/xmlspec.xsl	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml2/spec/xmlspec.xsl	Wed Dec 11 15:35:35 2013 -0500
@@ -2727,7 +2727,7 @@
     </style>
     <link rel="stylesheet" type="text/css">
       <xsl:attribute name="href">
-        <xsl:text>http://www.w3.org/StyleSheets/TR/</xsl:text>
+        <xsl:text>https://www.w3.org/StyleSheets/TR/</xsl:text>
         <xsl:choose>
           <xsl:when test="/spec/@role='editors-copy'">W3C-ED</xsl:when>
           <xsl:otherwise>
Binary file ttml2/spec/xsd/schema.zip has changed
--- a/ttml2/spec/xsd/ttml2-datatypes.xsd	Wed Dec 11 15:00:38 2013 -0500
+++ b/ttml2/spec/xsd/ttml2-datatypes.xsd	Wed Dec 11 15:35:35 2013 -0500
@@ -480,6 +480,8 @@
     <xs:restriction base="xs:token">
       <xs:enumeration value="mixed"/>
       <xs:enumeration value="sideways"/>
+      <xs:enumeration value="sidewaysLeft"/>
+      <xs:enumeration value="sidewaysRight"/>
       <xs:enumeration value="upright"/>
     </xs:restriction>
   </xs:simpleType>