[ttml1] prepare pre-final 2e REC package
authorGlenn Adams <glenn@skynav.com>
Thu, 19 Sep 2013 16:43:51 -0600
changeset 553 fcc954ad94f3
parent 552 aac96ebc6e18
child 554 6991d7d867ef
[ttml1] prepare pre-final 2e REC package
ttml1/spec/REC-ttml1-20130924.zip
ttml1/spec/build.xml
ttml1/spec/entities.dtd
ttml1/spec/entitiesrec.dtd
ttml1/spec/status.xml
ttml1/spec/ttml1-changes.html
ttml1/spec/ttml1-errata.html
ttml1/spec/ttml1-issues.html
ttml1/spec/ttml1.html
ttml1/spec/ttml1.xml
ttml1/spec/xmlspec-ttml1.dtd
ttml1/spec/xmlspec-ttml1.xsl
Binary file ttml1/spec/REC-ttml1-20130924.zip has changed
--- a/ttml1/spec/build.xml	Thu Sep 19 14:51:05 2013 -0600
+++ b/ttml1/spec/build.xml	Thu Sep 19 16:43:51 2013 -0600
@@ -1,6 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- Apache Ant script to build spec.
-     Philippe Le Hegaret, W3C -->
+<!-- Apache Ant script to build spec. Philippe Le Hegaret, W3C -->
       
 <project name="TimedText" default="generate" basedir=".">
     <path id="saxon8.classpath">
@@ -9,10 +8,6 @@
     <property name="html.dir" value="${basedir}"/>
     <property name="html.name" value="ttml1.html"/>
     <property name="stylesheet" value="xmlspec-ttml1.xsl"/>
-    <property name="glossary" value="extract-glist.xsl"/>
-    <property name="generateBPlist" value="generateBPlist.xsl"/>
-    <property name="diffformat" value="diffspec.xsl"/>
-    <property name="last-public-draft" value="20070706"/>
     
     <property name="jing.jar" value="${basedir}/jing/jing.jar"/>
     <property name="rnc.dir" value="${basedir}/rnc"/>
@@ -194,30 +189,6 @@
 
     <target name="validate" depends="validate-schemas,validate-examples,validate-xsl,validate-svg,validate-tt-specs,validate-schema-rnc,validate-profiles"/>
 
-    <target name="updateAcks"
-        description="Update acknowledgements. Before running this, 
-	update ackcurrent.xml via  and ackold.xml
-	via http://www.w3.org/2000/09/dbwg/details?group=34314&amp;former=1&amp;public=1 .">
-        <get src="http://www.w3.org/2000/09/dbwg/details?group=34314&amp;public=1" dest="ackcurrent.xml"/>
-        <get src="http://www.w3.org/2000/09/dbwg/details?group=34314&amp;former=1&amp;public=1" dest="ackold.xml"/>
-        <java fork="true" classname="net.sf.saxon.Transform">
-            <classpath refid="saxon8.classpath"/>
-            <arg value="-o"/>
-            <arg value="acknowledgements-current.txt"/>
-            <arg value="ackcurrent.xml"/>
-            <arg value="generate-acknowledgements.xsl"/>
-            <arg value="participating=1"/>
-        </java>
-        <java fork="true" classname="net.sf.saxon.Transform">
-            <classpath refid="saxon8.classpath"/>
-            <arg value="-o"/>
-            <arg value="acknowledgements-old.txt"/>
-            <arg value="ackold.xml"/>
-            <arg value="generate-acknowledgements.xsl"/>
-            <arg value="participating=0"/>
-        </java>
-    </target>
-
     <target name="html" description="Transforms xml into html.">
         <echo>Generating ttml1.html</echo>
         <java fork="true" classname="net.sf.saxon.Transform">
@@ -230,60 +201,12 @@
         </java>    
     </target>
 
-    <path id="diffmk.classpath">
-        <pathelement location="${basedir}/diffmk.jar"/>
-        <pathelement location="${basedir}/DiffMk.properties"/>
-    </path>
-    <target name="generateXMLdiff">
-        <java classname="com.sun.xtc.diffmk.DiffMk" fork="true">
-            <arg value="-doctype"/>
-            <arg value="xmlspec"/>
-            <arg value="-diff"/>
-            <arg value="both"/>
-            <arg value="-words"/>
-            <arg value="tt-tr${last-public-draft}.xml"/>
-            <arg value="ttml1.xml"/>
-            <arg value="tt-diff${last-public-draft}.xml"/>
-            <classpath path="diffmk.jar:DiffMk.properties"> </classpath>
-        </java>
-    </target>
-    <target name="generateHTMLdiff">
-        <java fork="true" classname="net.sf.saxon.Transform">
-            <classpath refid="saxon8.classpath"/>
-            <arg value="-o"/>
-            <arg value="${html.dir}/tt-diff${last-public-draft}.html"/>
-            <arg value="tt-diff${last-public-draft}.xml"/>
-            <arg value="diffspec.xsl"/>
-        </java>
-    </target>
-    <target name="postprocess-diff">
-      <java fork="true" classname="net.sf.saxon.Transform">
-            <classpath refid="saxon8.classpath"/>
-            <arg value="-o"/>
-            <arg value="temp-tt-diff${last-public-draft}.xml"/>
-            <arg value="tt-diff${last-public-draft}.xml"/>
-            <arg value="diff-postprocess.xsl"/>
-        </java>
-        <copy tofile="tt-diff${last-public-draft}.xml"
-            file="temp-tt-diff${last-public-draft}.xml" overwrite="true"/>
-        <delete file="temp-tt-diff${last-public-draft}.xml"/>
-    </target>
-
-    <target name="diff" depends="generateXMLdiff, postprocess-diff, generateHTMLdiff"/>
-
-    <target name="changelog" description="Update the CVS change log to be added into the specification">
-      <!--        <cvschangelog destfile="changelog.xml"/> -->
-      <get src="http://www.w3.org/2000/06/webdata/xslt?xslfile=http%3A%2F%2Fwww.w3.org%2F2008%2F05%2Fcvswebrss.xsl&amp;xmlfile=http%3A%2F%2Fcgi.w3.org%2Fcgi-bin%2Ftidy%3FdocAddr%3Dhttp%253A%252F%252Fdev.w3.org%252Fcvsweb%252F2008%252Fws%252Ftt%252Fttml1.xml%26forceXML%3Don" dest="changelog.xml"/>
-    </target>
-
-    <target name="generate" description="Generate the specification without updating changelog and acknowledgments sections"
+    <target name="generate" description="Generate the specification"
 	    depends="generate-schema-archives,validate-tt-specs,html">
-      <echo>WARNING: changelog.xml and acknowledgments.xml MAY be out of date. Use "main" target if necessary.</echo>
     </target>
     
-    <target name="sg" description="Shortened generation of the specification without updating changelog and acknowledgments sections, but without rebuilding escapes."
+    <target name="sg" description="Shortened generation of the specification, but without rebuilding escapes."
 	    depends="generate-schema-archives,validate-tt-specs-dont-build-escapes,html">
-      <echo>WARNING: changelog.xml and acknowledgments.xml MAY be out of date. Use "main" target if necessary.</echo>
     </target>
 
     <property name="per.name" value="PER-ttaf1-dfxp-20130709"/>
@@ -321,6 +244,44 @@
         </delete>
     </target>
 
+    <property name="rec.shortname" value="ttml1"/>
+    <property name="rec.name" value="REC-${rec.shortname}-20130924"/>
+    <property name="rec.target" value="${basedir}/${rec.name}"/>
+    <target name="rec-archive" description="Create REC Archive">
+        <fail>
+          <condition>
+            <not>
+              <resourcecount count="1">
+                <fileset dir="." includes="${rec.shortname}.html"/>
+              </resourcecount>
+            </not>
+          </condition>
+        </fail>
+        <delete includeemptydirs="true" quiet="true">
+          <fileset dir="${rec.target}"/>
+        </delete>
+        <mkdir dir="${rec.target}"/>
+        <mkdir dir="${rec.target}/images"/>
+        <mkdir dir="${rec.target}/rnc"/>
+        <mkdir dir="${rec.target}/xsd"/>
+        <copy file="${rec.shortname}.html" tofile="${rec.target}/${rec.name}.html"/>
+        <copy file="${rec.shortname}-changes.html" tofile="${rec.target}/${rec.shortname}-changes.html"/>
+        <copy file="${rec.shortname}-errata.html" tofile="${rec.target}/${rec.shortname}-errata.html"/>
+        <copy todir="${rec.target}/images">
+          <fileset dir="${basedir}/images" includes="*.png"/>
+        </copy>
+        <copy file="${rnc.dir}/schema.zip" todir="${rec.target}/rnc"/>
+        <copy file="${xsd.dir}/schema.zip" todir="${rec.target}/xsd"/>
+        <zip destfile="${rec.name}.zip">
+          <fileset dir="${rec.target}">
+            <include name="**/*"/>
+          </fileset>
+        </zip>
+        <delete includeemptydirs="true" quiet="true">
+          <fileset dir="${rec.target}"/>
+        </delete>
+    </target>
+
     <target name="kwexpand">
         <exec executable="hg">
           <arg value="kwexpand"/>
--- a/ttml1/spec/entities.dtd	Thu Sep 19 14:51:05 2013 -0600
+++ b/ttml1/spec/entities.dtd	Thu Sep 19 16:43:51 2013 -0600
@@ -1,9 +1,10 @@
 
 <!-- comment / uncomment the appropriate entity -->
-<!ENTITY % sub.entities SYSTEM "entitiesedcopy.dtd" >
+<!-- <!ENTITY % sub.entities SYSTEM "entitiesedcopy.dtd" > -->
 <!-- <!ENTITY % sub.entities SYSTEM "entitieswd.dtd" > -->
 <!-- <!ENTITY % sub.entities SYSTEM "entitiescr.dtd" > -->
 <!-- <!ENTITY % sub.entities SYSTEM "entitiesper.dtd" > -->
+<!ENTITY % sub.entities SYSTEM "entitiesrec.dtd" >
 %sub.entities;
 
 <!-- Titles -->
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml1/spec/entitiesrec.dtd	Thu Sep 19 16:43:51 2013 -0600
@@ -0,0 +1,34 @@
+<?xml version='1.0' encoding='ISO-8859-1' ?>
+
+<!--
+  Date parameters
+  -->
+<!ENTITY draft.year "2013">
+<!ENTITY draft.month "September">
+<!ENTITY draft.mm "09">
+<!ENTITY draft.day "24">
+<!ENTITY draft.dd "24">
+
+<!ENTITY draft.date "&draft.year;&draft.mm;&draft.dd;">
+
+<!ENTITY prefix "ttml1">
+
+<!ENTITY w3c.tr.latest  "http://www.w3.org/TR">	
+
+<!-- Latest version links. don't touch -->
+<!ENTITY latest "&w3c.tr.latest;/&prefix;/">
+
+<!ENTITY w3c.tr  "&w3c.tr.latest;/&draft.year;">	
+
+<!ENTITY document.role "public">
+
+<!-- The following is used for document .-->
+<!ENTITY document.status "W3C Recommendation">
+<!ENTITY w3c.status "REC">
+<!ENTITY doctype "rec">
+
+<!ENTITY w3c-designation
+  "&w3c.tr.latest;/&draft.year;/&w3c.status;-&prefix;-&draft.date;/">
+
+<!ENTITY prevloc "http://www.w3.org/TR/2013/PER-ttaf1-dfxp-20130709/">
+<!ENTITY prevrec "http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">
--- a/ttml1/spec/status.xml	Thu Sep 19 14:51:05 2013 -0600
+++ b/ttml1/spec/status.xml	Thu Sep 19 16:43:51 2013 -0600
@@ -1,64 +1,58 @@
 <?xml version='1.0' encoding='utf-8' ?>
 <status id="status">
-<p>
-<emph>This section describes the status of this document at the
+
+<p><emph>This section describes the status of this document at the
 time of its publication. Other documents may supersede this document.
 A list of current W3C publications and the latest revision of this
 technical report can be found in the <loc
 href="http://www.w3.org/TR/">W3C technical reports index</loc> at
-http://www.w3.org/TR/.</emph>
-</p>
-<p>
-This is the Proposed Recommendation of the Timed Text (TTML) &versionOfTT;. W3C publishes a technical report as a Proposed Recommendation
-to indicate that the document is believed to be stable, and to
-encourage implementation by the developer community. The W3C
-membership and other interested parties are invited to review the
-document and send comments to <loc
-href="mailto:[email protected]">[email protected]</loc> (with <loc
-href="http://lists.w3.org/Archives/Public/public-tt/">public
-archive</loc>) through 23 March 2010.
-</p>
-<p>This document is based on feedback from implementers. The list of
-changes made since the previous version is available in
-<specref ref="change-history-cr3-to-pr1"/>. A list of <a href='http://www.w3.org/2010/08/ttml-issues.html'>issues</a> is also available.
-</p>
-<p>
-A <loc href='http://www.w3.org/2008/10/dfxp-testsuite.zip'>test
-suite</loc> is available, along with
-its <loc href='http://www.w3.org/2008/10/dfxp-test-coverage.html'>coverage
-report</loc> and
-a <loc href='http://www.w3.org/2009/05/dfxp-results.html'>implementation
-report</loc>. Note that the test suite and implementations are work in
-progress and may not reflect all of the changes of this document.
-</p>
-<p>
-The entrance criteria to the Proposed Recommendation phase require at
-least two independently developed interoperable implementations of
-each required and optional feature.
-</p>
-<p>
-The dynamicFlow feature and the property value reverse oblique text
-have removed due to lack of implementations.
-</p>
+http://www.w3.org/TR/.</emph></p>
 
-<p>
-Publication as a Proposed Recommendation does not imply endorsement by
-the W3C Membership. This is a draft document and may be updated,
-replaced or obsoleted by other documents at any time. It is
-inappropriate to cite this document as other than work in progress.
-</p>
-<p>
-This document has been produced by the <loc
+<p>This document has been reviewed by W3C Members, by software developers,
+and by other W3C groups and interested parties, and is endorsed by the Director
+as a W3C Recommendation. It is a stable document and may be used as reference
+material or cited from another document. W3C's role in making the Recommendation
+is to draw attention to the specification and to promote its widespread
+deployment. This enhances the functionality and interoperability of the Web.</p>
+
+<p>This version reflects changes made as a result of applying errata and addressing
+comments received since the Recommendation was first published. With one minor
+exception noted below, these changes are editorial.</p>
+
+<p>This document is a revision of Timed Text Markup Language (TTML) 1.0
+<bibref ref="ttml10"/>, superseding that <loc href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">previous
+Recommendation</loc>. The only identified substantive difference between this version and
+its predecessor is a change of the default treatment of the <att>ttp:markerMode</att> parameter attribute
+from <code>continuous</code> to <code>discontinuous</code>. A cumulative summary of all changes applied
+to this version since the Recommendation was first published is available at
+<loc  href="ttml1-changes.html#change-history-rec-to-2e-per">Changes
+from Recommendation to Proposed Edited Recommendation (2nd Ed.)</loc> and
+<loc  href="ttml1-changes.html#change-history-2e-per-to-rec-2e">Changes
+from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</loc>.</p>
+
+<p>A <loc href="http://www.w3.org/2008/10/dfxp-testsuite.zip">sample test suite</loc> is available. This set of tests is not intended to
+be exhaustive. The <loc href="http://www.w3.org/2009/05/dfxp-results.html">implementation report</loc> used by the director to
+transition to Recommendation has been made available. There have been no formal objections
+to the publication of this document.</p>
+
+<p>This document was produced by the <loc
 href="http://www.w3.org/AudioVideo/TT/">Timed Text (TT) Working Group</loc> as
 part of the W3C <loc href="http://www.w3.org/2008/WebVideo/">Video
 in the Web Activity</loc>, following the procedures set out for the W3C <loc
 href="http://www.w3.org/Consortium/Process/">Process</loc>.  The authors of this
-document are listed in the header of this document.
-</p>
+document are listed in the header of this document, including input and review
+by liaisons from the <loc href="http://www3.ebu.ch/cms/en/home">European
+Broadcasting Union (EBU)</loc>, and the <loc href="https://www.smpte.org">Society
+of Motion Picture &amp; Television Engineers (SMPTE)</loc>.</p>
+
+<p>If you wish to report errors in or submit comments on this document, then please
+submit them to <loc href="mailto:[email protected]">[email protected]</loc>
+(<loc href="mailto:[email protected]">subscribe</loc>,
+<loc href="http://lists.w3.org/Archives/Public/public-tt/">archive</loc>). All comments are welcome.</p>
 
 <p>This document was produced by a group operating under the <loc
 href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
-2004 W3C Patent Policy</loc>. W3C maintains a <loc 
+2004 W3C Patent Policy</loc>. W3C maintains a <loc role="disclosure"
 href="http://www.w3.org/2004/01/pp-impl/34314/status#disclosures">public list of any patent
 disclosures</loc> made in connection with the deliverables of the group;
 that page also includes instructions for disclosing a patent. An
@@ -67,6 +61,6 @@
 href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
 Claim(s)</loc> must disclose the information in accordance with <loc
 href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
-6 of the W3C Patent Policy</loc>. </p>
+6 of the W3C Patent Policy</loc>.</p>
 
 </status>
--- a/ttml1/spec/ttml1-changes.html	Thu Sep 19 14:51:05 2013 -0600
+++ b/ttml1/spec/ttml1-changes.html	Thu Sep 19 16:43:51 2013 -0600
@@ -21,7 +21,7 @@
 <body>
 <h1>Timed Text Markup Language 1 (TTML1) Change Summary</h1>
 <p>1 <a href="#change-history">Change History</a> (Non-Normative)<br/>
-    1.1 <a href="#change-history-per-to-rec-23">Draft Changes from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</a><br/>
+    1.1 <a href="#change-history-2e-per-to-rec-2e">Changes from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</a><br/>
     1.2 <a href="#change-history-rec-to-2e-per">Changes from Recommendation to Proposed Edited Recommendation (2nd Ed.)</a><br/>
     1.3 <a href="#change-history-pr1-to-rec">Changes from Proposed Recommendation to Recommendation (1st Ed.)</a><br/>
     1.4 <a href="#change-history-cr3-to-pr1">Changes from Third Candidate Recommendation to Proposed Recommendation</a><br/>
@@ -36,13 +36,13 @@
 <p>Changes are ordered from most recent to least recent.</p>
 
 <div class="div2">
-<h3><a id="change-history-per-to-rec-2e"/>1.1 Changes from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</h3>
+<h3><a id="change-history-2e-per-to-rec-2e"/>1.1 Changes from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</h3>
 <div class="exampleInner">
 <pre>
 <span class="strong">Editorial Changes</span>
 
-* In Title, Abstract, and 1.0, use Timed Text Markup Language 1 (TTML1) to refer to the
-  first version of TTML. [The next version of TTML is expected to be called TTML2.]
+* In Title, Abstract, and Introduction (1.0), use Timed Text Markup Language 1 (TTML1)
+  to refer to the first version of TTML.
 
 * In 1.2, add note explaining that use of &lt;p/&gt; element may be presentational or
   semantic according to intentions of author.
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml1/spec/ttml1-errata.html	Thu Sep 19 16:43:51 2013 -0600
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>TTML1 - Errata</title>
+<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/>
+</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>
+</body>
+</html>
--- a/ttml1/spec/ttml1-issues.html	Thu Sep 19 14:51:05 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,217 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<title>TTML 1.0 - Errata</title>
-<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/>
-</head>
-<body>
-<h1>Errata for Timed Text Markup Language (TTML) 1.0; W3C REC, 18 November 2010</h1>
-
-<ol>
-<li><a href='#mediaType'>Update to TTML Media Type</a></li>
-<li><a href='#tts_extent'>XML schema error for tts:extent usage</a></li>
-<li><a href='#xsd_validation'>XML Schema is too restrictive</a></li>
-</ol>
-
-<p>Note: Updated Zip archives
-for <a href='/2012/02/rnc-schema.zip'>Relax NG</a>,
-and <a href='/2012/02/xsd-schema.zip'>XML Schema</a> schemas are
-available.</p>
-
-<h2 id='mediaType'>Update to TTML Media Type</h2>
-<div class="div1">
-<h2><a id="media-type-registration">C Media Type Registration</a></h2><p><em>This appendix is normative.</em></p><p>This appendix registers a new MIME media type,
-"application/ttml+xml" in conformance with
-<a href="http://www.ietf.org/rfc/rfc4288.txt">BCP 13</a> and
-<a href="http://www.w3.org/2002/06/registering-mediatype.html">W3CRegMedia</a>.
-The information in this appendix is being submitted to the Internet
-Engineering Steering Group (IESG) for review, approval, and
-registration with the Internet Assigned Numbers Authority (IANA).</p><dl>
-<dt class="label">Type name:</dt>
-<dd><p>application</p></dd>
-<dt class="label">Subtype name:</dt>
-<dd><p>ttml+xml</p></dd>
-<dt class="label">Required parameters:</dt>
-<dd><p>None.</p></dd>
-<dt class="label">Optional parameters:</dt>
-<dd>
-<dl>
-<dt class="label">charset</dt>
-<dd><p>Same as application/xml media type, as specified in <a href="#rfc3023">[XML Media Types]</a> or its successors.</p></dd>
-<dt class="label">profile</dt>
-<dd><p>The document profile of a TTML document may be specified using
-an optional <code>profile</code> parameter, which, if specified,
-the value of which must adhere to the syntax and semantics of
-<code>ttp:profile</code> parameter defined by
-Section
-<a href="#parameter-attribute-profile"><b>6.2.8 ttp:profile</b></a>
-of the published specification.</p></dd>
-</dl>
-</dd>
-<dt class="label">Encoding considerations:</dt>
-<dd><p>Same for application/xml. See <a href="#xml-media">[XML Media]</a>, Section
-3.2.</p></dd>
-<dt class="label">Security considerations:</dt>
-<dd><p>As with other XML types and as noted in
-<a href="#xml-media">[XML Media]</a>
-Section 10, repeated expansion of maliciously constructed XML entities
-can be used to consume large amounts of memory, which may cause XML
-processors in constrained environments to fail.</p><p>In addition, because of the extensibility features for TTML and of XML
-in general, it is possible that "application/ttml+xml" may describe content
-that has security implications beyond those described here. However,
-if the processor follows only the normative semantics of the published
-specification, this content will be outside TTML namespaces and
-may be ignored. Only in the case where the processor recognizes and
-processes the additional content, or where further processing of that
-content is dispatched to other processors, would security issues
-potentially arise. And in that case, they would fall outside the
-domain of this registration document.</p></dd>
-<dt class="label">Interoperability considerations:</dt>
-<dd><p>The published specification describes processing semantics that dictate
-behavior that must be followed when dealing with, among other things,
-unrecognized elements and attributes, both in TTML namespaces and in
-other namespaces.</p><p>Because TTML is extensible, conformant "application/ttml+xml" processors must
-expect that content received is well-formed XML, but it cannot be
-guaranteed that the content is valid to a particular DTD or Schema or
-that the processor will recognize all of the elements and attributes
-in the document.</p><p></p></dd>
-<dt class="label">Published specification:</dt>
-<dd><p><a href="http://www.w3.org/TR/ttaf1-dfxp/">Timed Text Markup Language (TTML) 1.0</a>.</p></dd>
-<dt class="label">Applications that use this media type:</dt>
-<dd><p>TTML is used in the television industry for the purpose of authoring,
-        transcoding and  exchanging timed text information and for delivering captions
-        for television material repurposed for the internet.</p>
-    <p>There is partial and full support of TTML in components used by several
-        Web browsers plugins, and in a number of caption authoring tools.</p></dd>
-
-<dt class="label">Additional information:</dt>
-<dd>
-<dl>
-<dt class="label">Magic number(s):</dt>
-<dd></dd>
-<dt class="label">File extension(s):</dt>
-<dd><p>.ttml</p></dd>
-<dt class="label">Macintosh file type code(s):</dt>
-<dd><p>"TTML"</p></dd>
-<dt class="label">Fragment identifiers:</dt>
-<dd><p>For documents labeled as application/ttml+xml, the fragment
-identifier notation is intended to be used with xml:id attributes, as
-described in section 7.2.1 of
-the <a href="http://www.w3.org/TR/ttaf1-dfxp/">Timed Text Markup
-Language (TTML) 1.0</a> specification.</p></dd>
-</dl>
-</dd>
-<dt class="label">Person &amp; email address to contact for further information:</dt>
-<dd><p>Timed Text Working Group ([email protected])</p></dd>
-<dt class="label">Intended usage:</dt>
-<dd><p>COMMON</p></dd>
-<dt class="label">Restrictions on usage:</dt>
-<dd><p>None</p></dd>
-<dt class="label">Author:</dt>
-<dd><p>The published specification is a work product of the World Wide Web
-Consortium's Timed Text (TT) Working Group.</p></dd>
-<dt class="label">Change controller:</dt>
-<dd><p>The W3C has change control over this specification.</p></dd>
-</dl></div>
-
-<h2 id='tts_extent'>XML schema error for tts:extent usage</h2>
-
-<h3>B.1.2.6 Document Module</h3>
-
-<div class="exampleInner"><pre># .......................................................................
-# TT-AF 1.0 DFXP Document Module ........................................
-# .......................................................................
-
-## tt - generic top-level document element type
-TTAF.tt =
-  element tt {
-    TTAF.tt.attlist,
-    TTAF.tt.content
-  }
-
-TTAF.tt.attlist &amp;=
-  TTAF.Core.required.attrib.class,
-  TTAF.Parameter.attrib.class,
-  TTAF.extent.attrib
-
-TTAF.tt.content =
-  (TTAF.head?, TTAF.body?)
-
-# .......................................................................
-# .......................................................................
-# .......................................................................
-</pre></div>
-
-<h3>B.2.2.5 Document Module</h3>
-
-<div class="exampleInner"><pre>&lt;xs:schema targetNamespace="http://www.w3.org/ns/ttml" xml:lang="en"
-  xmlns:xs="http://www.w3.org/2001/XMLSchema"
-  xmlns:tt="http://www.w3.org/ns/ttml"
-  xmlns:ttm="http://www.w3.org/ns/ttml#metadata"
-  xmlns:ttp="http://www.w3.org/ns/ttml#parameter"
-  xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
-  &lt;xs:import namespace="http://www.w3.org/ns/ttml#metadata"
-    schemaLocation="ttaf1-dfxp-metadata-items.xsd"/&gt;
-  &lt;xs:import namespace="http://www.w3.org/ns/ttml#parameter"
-    schemaLocation="ttaf1-dfxp-parameter-items.xsd"/&gt;
-  &lt;xs:import namespace="http://www.w3.org/ns/ttml#styling"
-    schemaLocation="ttaf1-dfxp-styling-attribs.xsd"/&gt;
-  &lt;xs:include schemaLocation="ttaf1-dfxp-core-attribs.xsd"/&gt;
-  &lt;xs:include schemaLocation="ttaf1-dfxp-timing-attribs.xsd"/&gt;
-  &lt;xs:include schemaLocation="ttaf1-dfxp-head.xsd"/&gt;
-  &lt;xs:include schemaLocation="ttaf1-dfxp-content.xsd"/&gt;
-  &lt;xs:attributeGroup name="tt.attlist"&gt;
-    &lt;xs:attributeGroup ref="tt:Core.required.attrib.class"/&gt;
-    &lt;xs:attributeGroup ref="ttp:Parameter.attrib.class"/&gt;
-    &lt;xs:attribute ref="tts:extent"/&gt;
-  &lt;/xs:attributeGroup&gt;
-  &lt;xs:complexType name="tt.eltype"&gt;
-    &lt;xs:sequence&gt;
-      &lt;xs:element ref="tt:head" minOccurs="0" maxOccurs="1"/&gt;
-      &lt;xs:element ref="tt:body" minOccurs="0" maxOccurs="1"/&gt;
-    &lt;/xs:sequence&gt;
-    &lt;xs:attributeGroup ref="tt:tt.attlist"/&gt;
-  &lt;/xs:complexType&gt;
-  &lt;xs:element name="tt" type="tt:tt.eltype"/&gt;
-&lt;/xs:schema&gt;
-</pre></div>
-
-<h2 id='xsd_validation'>XML Schema is too restrictive</h2>
-
-<h3>B.2.2.3 Core Attributes Module</h3>
-
-<pre>
-&lt;xs:schema targetNamespace="http://www.w3.org/ns/ttml" xml:lang="en"
-  xmlns:xs="http://www.w3.org/2001/XMLSchema"
-  xmlns:tt="http://www.w3.org/ns/ttml"
-  xmlns:xml="http://www.w3.org/XML/1998/namespace">
-  &lt;xs:import namespace="http://www.w3.org/XML/1998/namespace"
-    schemaLocation="xml.xsd"/>
-  &lt;xs:attributeGroup name="Core.ID.attrib.class">
-    &lt;xs:attribute ref="xml:id"/>
-  &lt;/xs:attributeGroup>
-  &lt;xs:attributeGroup name="Core.attrib.class">
-    &lt;xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
-    &lt;xs:attribute ref="xml:lang"/>
-    &lt;xs:attribute ref="xml:space"/>
-    &lt;xs:anyAttribute namespace="##other"/>
-  &lt;/xs:attributeGroup>
-  &lt;xs:attributeGroup name="Core.required.attrib.class">
-    &lt;xs:attributeGroup ref="tt:Core.ID.attrib.class"/>
-    &lt;xs:attribute ref="xml:lang" use="required"/>
-    &lt;xs:attribute ref="xml:space"/>
-    &lt;xs:anyAttribute namespace="##other"/>
-  &lt;/xs:attributeGroup>
-&lt;/xs:schema>
-</pre>
-
-<h3>B.2.2.12 Parameter Items Module</h3>
-
-<p><code>profile.attlist</code>, <code>features.attlist</code>, <code>feature.attlist</code>, <code>extensions.attlist</code>, and <code>extension.attlist</code> should also contain:</p>
-<pre>
-&lt;xs:anyAttribute namespace="##other"/>
-</pre>
-
-</body>
-</html>
--- a/ttml1/spec/ttml1.html	Thu Sep 19 14:51:05 2013 -0600
+++ b/ttml1/spec/ttml1.html	Thu Sep 19 16:43:51 2013 -0600
@@ -1,6 +1,6 @@
 <!DOCTYPE html
   PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en-us"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Timed Text Markup Language 1 (TTML1) (Second Edition) -- (Editor's copy)</title><style type="text/css">
+<html lang="en-us"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Timed Text Markup Language 1 (TTML1) (Second Edition)</title><style type="text/css">
 code           { font-family: monospace; }
 
 div.constraint,
@@ -80,14 +80,14 @@
 .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 02:31:56 $<div id="revisions"></div><div class="head">
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC.css"></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p>
 <h1><a id="title"></a>Timed Text Markup Language 1 (TTML1) (Second Edition)</h1>
-<h2><a id="w3c-doctype"></a>Editors' copy $Date: 2013/09/06 02:31:56 $ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
-<a href="ttml1.html">ttml1.html</a>
-</dd><dt>Latest version:</dt><dd><a href="http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml1/spec/ttml1.html?content-type=text/html;charset=utf-8">http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml1/spec/ttml1.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=ttml1"><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>
+<h2><a id="w3c-doctype"></a>W3C Recommendation 24 September 2013</h2><dl><dt>This version:</dt><dd>
+<a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/">http://www.w3.org/TR/2013/REC-ttml1-20130924/</a>
+</dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ttml1/">http://www.w3.org/TR/ttml1/</a></dd><dt>Previous version:</dt><dd>
+<a href="http://www.w3.org/TR/2013/PER-ttaf1-dfxp-20130709/">http://www.w3.org/TR/2013/PER-ttaf1-dfxp-20130709/</a>
+</dd><dt>Previous recommendation:</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="ttml1-errata.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=ttml1"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;©&nbsp;2013&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>
 <h2><a id="abstract"></a>Abstract</h2><p>This document specifies Timed Text Markup Language (TTML), Version 1, also known as TTML1,
 in terms of a vocabulary and semantics thereof.</p><p>The Timed Text Markup Language is a content type that represents
 timed text media for the purpose of interchange among authoring
@@ -100,8 +100,46 @@
 for example, providing a standard content format to reference from a <code>&lt;track&gt;</code>
 element in an HTML5 document, or a <code>&lt;text&gt;</code> or 
 <code>&lt;textstream&gt;</code> media element in a <a href="#smil21">[SMIL 2.1]</a> document.</p></div><div>
-<h2><a id="status"></a>Status of this Document</h2><p><strong>This document is an editor's copy that has
-        no official standing.</strong></p><p></p></div><div class="toc">
+<h2><a id="status"></a>Status of this Document</h2><p><em>This section describes the status of this document at the
+time of its publication. Other documents may supersede this document.
+A list of current W3C publications and the latest revision of this
+technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
+http://www.w3.org/TR/.</em></p><p>This document has been reviewed by W3C Members, by software developers,
+and by other W3C groups and interested parties, and is endorsed by the Director
+as a W3C Recommendation. It is a stable document and may be used as reference
+material or cited from another document. W3C's role in making the Recommendation
+is to draw attention to the specification and to promote its widespread
+deployment. This enhances the functionality and interoperability of the Web.</p><p>This version reflects changes made as a result of applying errata and addressing
+comments received since the Recommendation was first published. With one minor
+exception noted below, these changes are editorial.</p><p>This document is a revision of Timed Text Markup Language (TTML) 1.0
+<a href="#ttml10">[TTML10]</a>, superseding that <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">previous
+Recommendation</a>. The only identified substantive difference between this version and
+its predecessor is a change of the default treatment of the <code>ttp:markerMode</code> parameter attribute
+from <code>continuous</code> to <code>discontinuous</code>. A cumulative summary of all changes applied
+to this version since the Recommendation was first published is available at
+<a href="ttml1-changes.html#change-history-rec-to-2e-per">Changes
+from Recommendation to Proposed Edited Recommendation (2nd Ed.)</a> and
+<a href="ttml1-changes.html#change-history-2e-per-to-rec-2e">Changes
+from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</a>.</p><p>A <a href="http://www.w3.org/2008/10/dfxp-testsuite.zip">sample test suite</a> is available. This set of tests is not intended to
+be exhaustive. The <a href="http://www.w3.org/2009/05/dfxp-results.html">implementation report</a> used by the director to
+transition to Recommendation has been made available. There have been no formal objections
+to the publication of this document.</p><p>This document was produced by the <a href="http://www.w3.org/AudioVideo/TT/">Timed Text (TT) Working Group</a> as
+part of the W3C <a href="http://www.w3.org/2008/WebVideo/">Video
+in the Web Activity</a>, following the procedures set out for the W3C <a href="http://www.w3.org/Consortium/Process/">Process</a>.  The authors of this
+document are listed in the header of this document, including input and review
+by liaisons from the <a href="http://www3.ebu.ch/cms/en/home">European
+Broadcasting Union (EBU)</a>, and the <a href="https://www.smpte.org">Society
+of Motion Picture &amp; Television Engineers (SMPTE)</a>.</p><p>If you wish to report errors in or submit comments on this document, then please
+submit them to <a href="mailto:[email protected]">[email protected]</a>
+(<a href="mailto:[email protected]">subscribe</a>,
+<a href="http://lists.w3.org/Archives/Public/public-tt/">archive</a>). All comments are welcome.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
+2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/34314/status#disclosures" 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 W3C Patent Policy</a>.</p></div><div class="toc">
 <h2><a id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#model">System Model</a><br>
 &nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#example">Document Example</a><br>
@@ -392,11 +430,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="#d3e18825">Element Derivation</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e19307">Attribute Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.1 <a href="#d3e18942">Element Derivation</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;J.2 <a href="#d3e19424">Attribute Derivation</a><br>
 K <a href="#qa">QA Framework Compliance</a> (Non-Normative)<br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e20192">Requirements</a><br>
-&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e20356">Guidelines</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.1 <a href="#d3e20309">Requirements</a><br>
+&nbsp;&nbsp;&nbsp;&nbsp;K.2 <a href="#d3e20473">Guidelines</a><br>
 L <a href="#streaming">Streaming TTML Content</a> (Non-Normative)<br>
 M <a href="#concrete-encoding">Concrete Encoding</a> (Non-Normative)<br>
 N <a href="#time-expression-semantics">Time Expression Semantics</a> (Non-Normative)<br>
@@ -425,10 +463,16 @@
 animated content to depict sign language representations of the same content
 as expressed by a Timed Text <em>Document Instance</em>. This use case is not
 explicitly addressed by TTML mechanisms, but may be addressed by some
-external multimedia integration technology, such as SMIL.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In previous drafts of this specification, TTML was referred to as DFXP (Distribution
+external multimedia integration technology, such as SMIL.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In the first edition of this specification, the version number <code>1.0</code> was
+used to refer to this version of TTML. In this second edition, this version number is simplified
+to <code>1</code> as a result of a determination to call the next (future) version <code>2</code>
+instead of <code>1.1</code>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In previous drafts of this specification, TTML was referred to as DFXP (Distribution
 Format Exchange Profile). This latter term is retained for historical reasons in
 certain contexts, such as profile names and designators, and the short name
-<code>ttaf1-dfxp</code> used in older URLs to refer to this specification.</p></div><div class="div2">
+<code>ttaf1-dfxp</code> used in older URLs to refer to this specification. Starting in
+this edition of the first version of TTML, the short name <code>ttml1</code> will be
+used, and subsequent versions of TTML are expected to use short names of
+<code>ttml2</code>, etc., with integer version numbers.</p></div><div class="div2">
 <h3><a id="model"></a>1.1 System Model</h3><p>Use of TTML is intended to function in a wider context of Timed Text
 Authoring and Distribution mechanisms that are based upon the system
 model depicted in <a href="#model-graphic"><b>Figure 1 – System Model</b></a>, wherein the Timed Text Markup Language
@@ -2400,7 +2444,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 presentation processor 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;
@@ -2486,7 +2531,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 presentation processor 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.9 &lt;length&gt;</b></a>.
 When a single &lt;length&gt; is expressed using cell units, then it refers to the height of
 the <em>Computed Cell Size</em>.
@@ -2607,7 +2654,8 @@
 to obtain a line height of <code>1c</code>.</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 presentation processor 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;
@@ -2695,7 +2743,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 <em>Root Container Region</em>.</p><p>If a computed value of the property associated with this attribute is not supported,
 then a presentation processor 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;
@@ -2797,7 +2846,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 presentation processor 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><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><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;
@@ -3198,7 +3248,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 presentation processor 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;
@@ -3275,7 +3326,8 @@
 less than 0, or greater than 1.</p><p>If a presentation processor 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-color"></a>8.3.2 &lt;color&gt;</h4><p>A &lt;color&gt; expression is used to specify a named color, exact RGB color triple,
 or exact RGBA color tuple, where the alpha component, if expressed,
 is maximum (255) at 100% opacity
@@ -3316,7 +3368,8 @@
 used here to the YUV color space for rendition on a television device.</p></div><p>If a presentation processor 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 or alpha and the supported color or 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.3 &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;
@@ -4910,7 +4963,7 @@
 <a href="http://www.w3.org/2002/06/registering-mediatype.html">W3CRegMedia</a>.
 The information in this appendix is being submitted to the Internet
 Engineering Steering Group (IESG) for review, approval, and
-registration with the Internet Assigned Numbers Authority (IANA).</p><dl><dt class="label">Type name:</dt><dd><p>application</p></dd><dt class="label">Subtype name:</dt><dd><p>ttml+xml</p></dd><dt class="label">Required parameters:</dt><dd><p>None.</p></dd><dt class="label">Optional parameters:</dt><dd><dl><dt class="label">charset</dt><dd><p>If specified, the <code>charset</code> parameter must match the XML encoding declaration, or if absent, the actual encoding.</p></dd><dt class="label">profile</dt><dd><p>The document profile of a TTMLDocument Instance may be specified using
+registration with the Internet Assigned Numbers Authority (IANA).</p><dl><dt class="label">Type name:</dt><dd><p>application</p></dd><dt class="label">Subtype name:</dt><dd><p>ttml+xml</p></dd><dt class="label">Required parameters:</dt><dd><p>None.</p></dd><dt class="label">Optional parameters:</dt><dd><dl><dt class="label">charset</dt><dd><p>If specified, the <code>charset</code> parameter must match the XML encoding declaration, or if absent, the actual encoding. See also Encoding Considerations below.</p></dd><dt class="label">profile</dt><dd><p>The document profile of a TTMLDocument Instance may be specified using
 an optional <code>profile</code> parameter, which, if specified,
 the value of which must adhere to the syntax and semantics of
 <code>ttp:profile</code> parameter defined by
@@ -6460,6 +6513,10 @@
 Cases and Requirements</cite></a>,
 W3C Working Group Note, 27 April 2006. (See
 <a href="http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427/">http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427/</a>.)
+</dd><dt class="label"><a id="ttml10"></a>TTML10</dt><dd>Glenn Adams, Ed.,
+<a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/"><cite>Timed Text Markup Language (TTML) 1.0</cite></a>,
+W3C Recommendation, 18 November 2010. (See
+<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 class="label"><a id="xhtml10"></a>XHTML 1.0</dt><dd>Steven Pemberton, et al.,
 <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/"><cite>XHTML™ 1.0,
 The Extensible Hypertext Markup Language (Second Edition)</cite></a>,
@@ -6480,7 +6537,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="d3e18825"></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="d3e18942"></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
@@ -6535,7 +6592,7 @@
 and <code>@requiredFeatures</code> on the <code>svg:svg</code> element,
 but extended to support distinct specification of optionality.</p></li><li><p>Derived from the use of <code>@baseProfile</code>
 and <code>@version</code> on the <code>svg:svg</code> element.</p></li></ol></div></div><div class="div2">
-<h3><a id="d3e19307"></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="d3e19424"></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
@@ -6607,9 +6664,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="d3e20192"></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="d3e20309"></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="d3e20356"></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="d3e20473"></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/ttml1/spec/ttml1.xml	Thu Sep 19 14:51:05 2013 -0600
+++ b/ttml1/spec/ttml1.xml	Thu Sep 19 16:43:51 2013 -0600
@@ -59,12 +59,15 @@
 <publoc>
 <loc href="&w3c-designation;">&w3c-designation;</loc>
 </publoc>
+<latestloc>
+<loc href="&latest;">&latest;</loc>
+</latestloc>
 <prevlocs>
 <loc href="&prevloc;">&prevloc;</loc>
 </prevlocs>
-<latestloc>
-<loc href="&latest;">&latest;</loc>
-</latestloc>
+<prevrecs>
+<loc href="&prevrec;">&prevrec;</loc>
+</prevrecs>
 <authlist id="editors" role="editor">
 <author>
 <name>Glenn Adams</name>
@@ -101,7 +104,7 @@
 <affiliation>Apple Computer</affiliation>
 </author>
 </authlist>
-<errataloc href="https://dvcs.w3.org/hg/ttml/raw-file/default/ttml10/spec/ttml-issues.html"/>
+<errataloc href="ttml1-errata.html"/>
 <translationloc href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ttml1"/>
 <abstract id="abstract">
 <p>This document specifies Timed Text Markup Language (TTML), Version 1, also known as TTML1,
@@ -169,7 +172,7 @@
 <code>ttaf1-dfxp</code> used in older URLs to refer to this specification. Starting in
 this edition of the first version of TTML, the short name <code>ttml1</code> will be
 used, and subsequent versions of TTML are expected to use short names of
-<code>ttml2</code>, etc., with whole integer version numbers.</p>
+<code>ttml2</code>, etc., with integer version numbers.</p>
 </note>
 <div2 id="model">
 <head>System Model</head>
@@ -11586,6 +11589,11 @@
 <xspecref
 href="http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427/">http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427/</xspecref>.)
 </bibl>
+<bibl id="ttml10" key="TTML10">Glenn Adams, Ed.,
+<titleref href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">Timed Text Markup Language (TTML) 1.0</titleref>,
+W3C Recommendation, 18 November 2010. (See
+<xspecref href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/</xspecref>.)
+</bibl>
 <bibl id="xhtml10" key="XHTML 1.0">Steven Pemberton, et al.,
 <titleref
 href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">XHTML&trade; 1.0,
--- a/ttml1/spec/xmlspec-ttml1.dtd	Thu Sep 19 14:51:05 2013 -0600
+++ b/ttml1/spec/xmlspec-ttml1.dtd	Thu Sep 19 16:43:51 2013 -0600
@@ -14,8 +14,8 @@
 <!-- parameter entity overrides -->
 <!ENTITY % header.mdl
         "title, subtitle?, version?, w3c-designation, w3c-doctype,
-        pubdate, notice*, publoc, altlocs?, ((prevlocs, latestloc?) |
-        (latestloc, prevlocs?))?, authlist+, errataloc?, preverrataloc?,
+        pubdate, notice*, publoc, altlocs?, latestloc, prevlocs, prevrecs,
+        authlist+, errataloc?, preverrataloc?,
         translationloc?, copyright?,
         ((status, abstract) | (abstract, status)), pubstmt?,
         sourcedesc?, langusage, revisiondesc">
@@ -31,3 +31,8 @@
 
 <!-- element definition overrides -->
 <!ELEMENT loc (#PCDATA|phrase|el|att|code|emph)*>
+
+<!-- prevrecs definition -->
+<!ELEMENT prevrecs (loc)*>
+<!ATTLIST prevrecs %common.att;>
+
--- a/ttml1/spec/xmlspec-ttml1.xsl	Thu Sep 19 14:51:05 2013 -0600
+++ b/ttml1/spec/xmlspec-ttml1.xsl	Thu Sep 19 16:43:51 2013 -0600
@@ -118,6 +118,155 @@
   </html>
 </xsl:template>
 
+<!-- header: metadata about the spec -->
+<!-- pull out information into standard W3C layout -->
+<xsl:template match="header">
+  <div class="head">
+    <xsl:if test="not(/spec/@role='editors-copy')">
+      <p>
+        <a href="http://www.w3.org/">
+          <img src="http://www.w3.org/Icons/w3c_home"
+            alt="W3C" height="48" width="72"/>
+        </a>
+        <xsl:choose>
+          <xsl:when test="/spec/@w3c-doctype='memsub'">
+            <a href='http://www.w3.org/Submission/'>
+              <img alt='Member Submission'
+                   src='http://www.w3.org/Icons/member_subm'/>
+            </a>
+          </xsl:when>
+          <xsl:when test="/spec/@w3c-doctype='teamsub'">
+            <a href='http://www.w3.org/2003/06/TeamSubmission'>
+              <img alt='Team Submission'
+                   src='http://www.w3.org/Icons/team_subm'/>
+            </a>
+          </xsl:when>
+        </xsl:choose>
+      </p>
+    </xsl:if>
+    <xsl:text>&#10;</xsl:text>
+    <h1>
+      <xsl:call-template name="anchor">
+        <xsl:with-param name="node" select="title[1]"/>
+        <xsl:with-param name="conditional" select="0"/>
+        <xsl:with-param name="default.id" select="'title'"/>
+      </xsl:call-template>
+
+      <xsl:apply-templates select="title"/>
+      <xsl:if test="version">
+        <xsl:text> </xsl:text>
+        <xsl:apply-templates select="version"/>
+      </xsl:if>
+    </h1>
+    <xsl:if test="subtitle">
+      <xsl:text>&#10;</xsl:text>
+      <h2>
+        <xsl:call-template name="anchor">
+          <xsl:with-param name="node" select="subtitle[1]"/>
+          <xsl:with-param name="conditional" select="0"/>
+          <xsl:with-param name="default.id" select="'subtitle'"/>
+        </xsl:call-template>
+        <xsl:apply-templates select="subtitle"/>
+      </h2>
+    </xsl:if>
+    <xsl:text>&#10;</xsl:text>
+    <h2>
+      <xsl:call-template name="anchor">
+        <xsl:with-param name="node" select="w3c-doctype[1]"/>
+        <xsl:with-param name="conditional" select="0"/>
+        <xsl:with-param name="default.id" select="'w3c-doctype'"/>
+      </xsl:call-template>
+
+      <xsl:choose>
+        <xsl:when test="/spec/@w3c-doctype = 'review'">
+          <xsl:text>Editor's Draft</xsl:text>
+        </xsl:when>
+        <xsl:otherwise>
+          <xsl:value-of select="w3c-doctype[1]"/>
+        </xsl:otherwise>
+      </xsl:choose>
+      <xsl:text> </xsl:text>
+      <xsl:if test="pubdate/day">
+        <xsl:apply-templates select="pubdate/day"/>
+        <xsl:text> </xsl:text>
+      </xsl:if>
+      <xsl:apply-templates select="pubdate/month"/>
+      <xsl:text> </xsl:text>
+      <xsl:apply-templates select="pubdate/year"/>
+    </h2>
+    <dl>
+      <xsl:apply-templates select="publoc"/>
+      <xsl:apply-templates select="latestloc"/>
+      <xsl:apply-templates select="prevlocs"/>
+      <xsl:apply-templates select="prevrecs"/>
+      <xsl:apply-templates select="authlist"/>
+    </dl>
+
+    <!-- output the errataloc and altlocs -->
+    <xsl:apply-templates select="errataloc"/>
+    <xsl:apply-templates select="preverrataloc"/>
+    <xsl:apply-templates select="translationloc"/>
+    <xsl:apply-templates select="altlocs"/>
+
+    <xsl:choose>
+      <xsl:when test="copyright">
+        <xsl:apply-templates select="copyright"/>
+      </xsl:when>
+      <xsl:otherwise>
+        <p class="copyright">
+          <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">
+            <xsl:text>Copyright</xsl:text>
+          </a>
+          <xsl:text>&#xa0;&#xa9;&#xa0;</xsl:text>
+          <xsl:apply-templates select="pubdate/year"/>
+          <xsl:text>&#xa0;</xsl:text>
+          <a href="http://www.w3.org/">
+            <acronym title="World Wide Web Consortium">W3C</acronym>
+          </a>
+          <sup>&#xae;</sup>
+          <xsl:text> (</xsl:text>
+          <a href="http://www.csail.mit.edu/">
+            <acronym title="Massachusetts Institute of Technology">MIT</acronym>
+          </a>
+          <xsl:text>, </xsl:text>
+          <a href="http://www.ercim.eu/">
+            <acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym>
+          </a>
+          <xsl:text>, </xsl:text>
+          <a href="http://www.keio.ac.jp/">Keio</a>
+          <xsl:text>, </xsl:text>
+          <a href="http://ev.buaa.edu.cn/">Beihang</a>
+          <xsl:text>), All Rights Reserved. W3C </xsl:text>
+          <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>
+          <xsl:text>, </xsl:text>
+          <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
+          <xsl:text> and </xsl:text>
+          <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
+          <xsl:text> rules apply.</xsl:text>
+        </p>
+      </xsl:otherwise>
+    </xsl:choose>
+  </div>
+  <hr/>
+  <xsl:apply-templates select="notice"/>
+  <xsl:apply-templates select="abstract"/>
+  <xsl:apply-templates select="status"/>
+  <xsl:apply-templates select="revisiondesc"/>
+</xsl:template>
+
+<!-- prevrecs: previous locations for this spec -->
+<!-- called in a <dl> context from header -->
+<xsl:template match="prevrecs">
+  <dt>
+    <xsl:text>Previous recommendation</xsl:text>
+    <xsl:if test="count(loc) &gt; 1">s</xsl:if>
+    <xsl:text>:</xsl:text>
+  </dt>
+  <dd>
+    <xsl:apply-templates/>
+  </dd>
+</xsl:template>
+
 <!-- specref: reference to another part of teh current specification -->
 <xsl:template match="specref">
   <xsl:param name="target" select="key('ids', @ref)[1]"/>