[ttml11] Manually update from TTML10.
authorGlenn Adams <glenn@skynav.com>
Tue, 09 Jul 2013 14:39:28 -0600
changeset 428 9e3f6c1d5cd9
parent 427 44338eddeba5
child 429 f2ae6b048445
[ttml11] Manually update from TTML10.
ttml11/spec/ackcurrent.xml
ttml11/spec/acknowledgements-current.txt
ttml11/spec/acknowledgements-old.txt
ttml11/spec/acknowledgements.xml
ttml11/spec/ackold.xml
ttml11/spec/build.xml
ttml11/spec/changelog.xml
ttml11/spec/diffmk.jar
ttml11/spec/diffspec.xsl
ttml11/spec/editlist.txt
ttml11/spec/entities.dtd
ttml11/spec/entitiescr.dtd
ttml11/spec/entitieswd.dtd
ttml11/spec/examples/ex1-p-0.xml
ttml11/spec/examples/ex1-x-0.xml
ttml11/spec/examples/ex1-x-1.xml
ttml11/spec/examples/ex1-x-2.xml
ttml11/spec/examples/ex1.xml
ttml11/spec/examples/ex2-paint-on.xml
ttml11/spec/examples/ex2-pop-on.xml
ttml11/spec/examples/ex2-roll-up.xml
ttml11/spec/examples/ex3-all-elements.xml
ttml11/spec/examples/ex3-all-styles.xml
ttml11/spec/generate-acknowledgements.xsl
ttml11/spec/profiles/dfxp-full.xml
ttml11/spec/profiles/dfxp-presentation.xml
ttml11/spec/profiles/dfxp-transformation.xml
ttml11/spec/rnc/schema.zip
ttml11/spec/rnc/ttml11-datatypes.rnc
ttml11/spec/rnc/ttml11-metadata.rnc
ttml11/spec/rnc/ttml11.rnc
ttml11/spec/scm/.cvsignore
ttml11/spec/scm/adi.scm
ttml11/spec/scm/compile.scm
ttml11/spec/scm/dfxp.pkg
ttml11/spec/scm/dtf.scm
ttml11/spec/scm/fox.scm
ttml11/spec/scm/load.scm
ttml11/spec/scm/rxi.scm
ttml11/spec/scm/test.xml
ttml11/spec/scm/tir.scm
ttml11/spec/ttml-changes.html
ttml11/spec/ttml-issues.html
ttml11/spec/ttml11.xml
ttml11/spec/xmlspec-ttml11.dtd
ttml11/spec/xmlspec-ttml11.xsl
ttml11/spec/xmlspec.dtd
ttml11/spec/xmlspec.xsl
ttml11/spec/xsd/schema.zip
ttml11/spec/xsd/ttml11-animation.xsd
ttml11/spec/xsd/ttml11-bindings.xjb
ttml11/spec/xsd/ttml11-content.xsd
ttml11/spec/xsd/ttml11-core-attribs.xsd
ttml11/spec/xsd/ttml11-datatypes.xsd
ttml11/spec/xsd/ttml11-document.xsd
ttml11/spec/xsd/ttml11-head.xsd
ttml11/spec/xsd/ttml11-layout.xsd
ttml11/spec/xsd/ttml11-metadata-attribs.xsd
ttml11/spec/xsd/ttml11-metadata-items.xsd
ttml11/spec/xsd/ttml11-metadata.xsd
ttml11/spec/xsd/ttml11-parameter-attribs.xsd
ttml11/spec/xsd/ttml11-parameter-items.xsd
ttml11/spec/xsd/ttml11-parameters.xsd
ttml11/spec/xsd/ttml11-styling-attribs.xsd
ttml11/spec/xsd/ttml11-styling.xsd
ttml11/spec/xsd/ttml11-timing-attribs.xsd
ttml11/spec/xsd/ttml11.xsd
ttml11/spec/xsd/xml.xsd
--- a/ttml11/spec/acknowledgements-current.txt	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/acknowledgements-current.txt	Tue Jul 09 14:39:28 2013 -0600
@@ -1,1 +1,43 @@
-Glenn Adams (Samsung Electronics Co., Ltd.), John Birch (Invited expert), Kees Blom (CWI), Dick Bulterman (CWI), Frans de Jong (Invited expert), Mike Dolan (W3C Invited Experts), Geoff Freed (WGBH National Center for Accessible Media), Sean Hayes (Microsoft Corporation), David Kirby (British Broadcasting Corporation), Andrew Kirkpatrick (Adobe Systems Inc.), Philippe Le Hégaret (W3C/MIT), Matthew May (Adobe Systems Inc.), Soohong Daniel Park (Samsung Electronics Co., Ltd.), Brad Botkin, Donald Evans, Markus Gylling, Markku Hakkinen, Erik Hodge, Masahiko Kaneko, George Kerscher, Chris Lilley, Thierry Michel, Patrick Schmitz, David Singer.
+Glenn Adams,
+Thomas Bause-Mason,
+John Birch,
+Kees Blom,
+Bert Bos,
+Brad Botkin,
+Dick Bulterman,
+Frans de Jong,
+Mike Dolan,
+Martin D&uuml;rst,
+Donald Evans,
+Geoff Freed,
+Al Gilman,
+Giles Godart-Brown,
+Markus Gylling,
+Markku Hakkinen,
+Sean Hayes,
+Erik Hodge,
+Philipp Hoschka,
+Suzi Hyun,
+Michael Jordan,
+Masahiko Kaneko,
+Courtney Kennedy,
+George Kerscher,
+David Kirby,
+Andrew Kirkpatrick,
+Philippe Le Hégaret,
+Chris Lilley,
+Pierre-Anthony Lemieux,
+Jason Livingston,
+Monica Martin,
+Thierry Michel,
+Matthew May,
+Frank Olivier,
+Soohong Daniel Park,
+Silvia Pfeiffer,
+Brian Raymor,
+David Ronca,
+Patrick Schmitz,
+David Singer,
+Craig Smithpeters,
+Andreas Tai,
+and Mohamed Zergaoui.
--- a/ttml11/spec/acknowledgements.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/acknowledgements.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,32 +1,16 @@
 <?xml version="1.0" encoding="utf-8"?>
 <inform-div1 id="acknowledgments">
 <head>Acknowledgments</head>
-<p>The editor acknowledges the members of the Timed Text Working
+<p>The editor acknowledges the current and former members of the Timed Text Working
 Group, the members of other W3C Working Groups, and industry experts
 in other forums who have contributed directly or indirectly to the
-process or content of creating this document.</p>
-<p>The current and former members of the Timed Text Working Group are:
-&acknowledgements-current;
-</p>
+process or content of this document as follows:</p>
+<p>&acknowledgements-current;</p>
 <p>The editor wishes to especially acknowledge the following contributions
 by members: Micheal Dolan (SMPTE time codes, streaming; SMPTE liaison), David
 Kirby (introductory example document; SMPTE time codes, descriptive metadata; EBU/AAF liaison), Geoff Freed (styling
 and example images of style properties), Sean Hayes (advanced profile
 concepts, including applicative timing), Eric Hodge (timing),
 Thierry Michel (metadata), and Dave Singer (animation, scrolling).</p>
-<p>The Timed Text Working Group has benefited in its work from the
-participation and contributions of a number of people not currently
-members of the Working Group, including in particular those named
-below. Affiliations given are those current at the time of their work
-with the WG.</p>
-<p>
-John Birch, Screen Subtitling Systems;
-Bert Bos, W3C (chair, CSS WG);
-Martin D&uuml;rst, W3C (leader, I18N Activity);
-Al Gilman (chair, WAI Protocol and Formats WG);
-Philipp Hoschka, W3C (leader, Interaction Domain);
-Chris Lilley, W3C (chair, SVG WG).
-</p>
-<p>The editor wishes to especially acknowledge the following contributions
-by non-members: John Birch (dynamic flow).</p>
+<p>The Working Group dedicates this specification to our colleague David Kirby.</p>
 </inform-div1>
--- a/ttml11/spec/build.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/build.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -2,33 +2,32 @@
 <!-- Apache Ant script to build spec.
      Philippe Le Hegaret, W3C -->
       
-<project name="TimedText" default="main" basedir=".">
+<project name="TimedText" default="generate" basedir=".">
     <path id="saxon8.classpath">
         <pathelement location="saxon8/saxon8.jar"/>
     </path>
-    <property name="htmlOutputDir" value="./"/>
+    <property name="html.dir" value="${basedir}"/>
+    <property name="html.name" value="ttml11.html"/>
     <property name="stylesheet" value="xmlspec-ttml11.xsl"/>
     <property name="glossary" value="extract-glist.xsl"/>
-	<property name="generateBPlist" value="generateBPlist.xsl"/>
-    <property name="diffformat" value="diffspec.xsl"/>
+    <property name="generateBPlist" value="generateBPlist.xsl"/>
     <property name="last-public-draft" value="20070706"/>
     
     <property name="jing.jar" value="${basedir}/jing/jing.jar"/>
     <property name="rnc.dir" value="${basedir}/rnc"/>
     <property name="rnc.schema" value="${rnc.dir}/ttml11.rnc"/>
+    <property name="xsd.dir" value="${basedir}/xsd"/>
+    <property name="xsd.schema" value="${xsd.dir}/ttml11.xsd"/>
     <property name="profiles.dir" value="${basedir}/profiles"/>
+    <property name="examples.dir" value="${basedir}/examples"/>
 
     <patternset id="escapable">
       <include name="examples/*.xml"/>
-      <include name="rnc/*.rnc"/>
-      <include name="xsd/*.xsd"/>
       <include name="profiles/*.xml"/>
     </patternset>
 
     <patternset id="escaped">
       <include name="examples/*.esc"/>
-      <include name="rnc/*.esc"/>
-      <include name="xsd/*.esc"/>
       <include name="profiles/*.esc"/>
     </patternset>
 
@@ -41,7 +40,7 @@
     </target>
 
     <target name="clean" depends="clean-escapes">
-        <delete quiet="true" file="ttml11.html"/>
+        <delete quiet="true" file="${html.name}"/>
     </target>
 
     <target name="validate-schema-rnc" description="Validates DFXP's RNC Schema.">
@@ -51,6 +50,43 @@
         </java>
     </target>
 
+    <target name="generate-schema-archive-rnc" description="Generate DFXP's RNC Schema archive." depends="validate-schema-rnc">
+        <zip destfile="${rnc.dir}/schema.zip">
+            <fileset dir="${rnc.dir}">
+                <include name="*.rnc"/>
+            </fileset>
+        </zip>
+    </target>
+
+    <target name="create-xsd-bindings" description="Create JAXB Bindings for DFXP's XSD Schema.">
+        <exec executable="xjc" dir="xsd">
+          <arg value="-quiet"/>
+          <arg value="-b"/>
+          <arg value="ttml11-bindings.xjb"/>
+          <arg value="ttml11.xsd"/>
+        </exec>
+    </target>
+
+    <target name="delete-xsd-bindings" description="Delete JAXB Bindings for DFXP's XSD Schema.">
+        <delete includeemptydirs="true">
+          <fileset dir="xsd/org"/>
+        </delete>
+    </target>
+
+    <target name="validate-schema-xsd" description="Validates DFXP's XSD Schema using JAXB tool set." depends="create-xsd-bindings, delete-xsd-bindings"/>
+
+    <target name="generate-schema-archive-xsd" description="Generate DFXP's XSD Schema archive." depends="validate-schema-xsd">
+        <zip destfile="${xsd.dir}/schema.zip">
+            <fileset dir="${xsd.dir}">
+                <include name="*.xsd"/>
+            </fileset>
+        </zip>
+    </target>
+
+    <target name="validate-schemas" description="Validate DFXP schemas" depends="validate-schema-rnc, validate-schema-xsd"/>
+
+    <target name="generate-schema-archives" description="Generate DFXP schema archives" depends="generate-schema-archive-rnc, generate-schema-archive-xsd"/>
+
     <target name="validate-profile-transformation" description="Validates transformation profile.">
         <java fork="true" jar="${jing.jar}">
             <arg value="-c"/>
@@ -78,6 +114,47 @@
     <target name="validate-profiles"
 	    depends="validate-profile-transformation,validate-profile-presentation,validate-profile-full"/>
 
+    <target name="validate-example-1" description="Validates Example 1.">
+        <!-- validate using RNC schema -->
+        <java fork="true" jar="${jing.jar}">
+            <arg value="-c"/>
+            <arg value="${rnc.schema}"/>
+            <arg value="${examples.dir}/ex1.xml"/>
+        </java>
+        <!-- validate using XSD schema -->
+        <schemavalidate fullchecking="true" warn="true">
+          <schema namespace="http://www.w3.org/ns/ttml" file="${xsd.schema}"/>
+          <fileset dir="${examples.dir}">
+            <include name="ex3.xml"/>
+          </fileset>
+        </schemavalidate>
+    </target>
+
+    <target name="validate-example-3" description="Validates Example 3.">
+        <!-- validate using RNC schema -->
+        <java fork="true" jar="${jing.jar}">
+            <arg value="-c"/>
+            <arg value="${rnc.schema}"/>
+            <arg value="${examples.dir}/ex3-all-elements.xml"/>
+        </java>
+        <java fork="true" jar="${jing.jar}">
+            <arg value="-c"/>
+            <arg value="${rnc.schema}"/>
+            <arg value="${examples.dir}/ex3-all-styles.xml"/>
+        </java>
+        <!-- validate using XSD schema -->
+        <schemavalidate fullchecking="true" warn="true">
+          <schema namespace="http://www.w3.org/ns/ttml" file="${xsd.schema}"/>
+          <fileset dir="${examples.dir}">
+            <include name="ex3-all-elements.xml"/>
+            <include name="ex3-all-styles.xml"/>
+          </fileset>
+        </schemavalidate>
+    </target>
+
+    <target name="validate-examples"
+	    depends="validate-example-1, validate-example-3"/>
+
     <target name="validate-xsl" description="Validates all XML files.">
         <xmlvalidate lenient="true">
             <fileset dir="." includes="*.xsl"/>
@@ -110,101 +187,30 @@
         <xmlvalidate lenient="false" warn="yes" file="ttml11.xml"/>
     </target>
 
-    <target name="validate" depends="validate-xsl,validate-svg,validate-tt-specs,validate-schema-rnc,validate-profiles"/>
+    <target name="validate-tt-specs-dont-build-escapes" description="Validates all Timed Text spec files.">
+        <xmlvalidate lenient="false" warn="yes" file="ttml11.xml"/>
+    </target>
 
-    <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="validate" depends="validate-schemas,validate-examples,validate-xsl,validate-svg,validate-tt-specs,validate-schema-rnc,validate-profiles"/>
 
     <target name="html" description="Transforms xml into html.">
         <echo>Generating ttml11.html</echo>
         <java fork="true" classname="net.sf.saxon.Transform">
             <classpath refid="saxon8.classpath"/>
             <arg value="-o"/>
-            <arg value="${htmlOutputDir}ttml11.html"/>
+            <arg value="${html.dir}/${html.name}"/>
             <arg value="ttml11.xml"/>
             <arg value="${stylesheet}"/>
             <arg value="showAssertions=true"/>
         </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="ttml11.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="${htmlOutputDir}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%252Fttml11.xml%26forceXML%3Don" dest="changelog.xml"/>
-    </target>
-
-    <target name="generate" description="Generate the specification without updating changelog and acknowledgments sections"
-	    depends="validate-tt-specs,html">
-      <echo>WARNING: changelog.xml and acknowledgments.xml MAY be out of date. Use "main" target if necessary.</echo>
+    <target name="generate" description="Generate the specification without updating escaped entities."
+	    depends="generate-schema-archives,validate-tt-specs,html">
     </target>
     
-    <target name="main" description="Generate the specification for a CVS commit"
-	    depends="changelog,validate-tt-specs,html">
-<!--	    depends="updateAcks,changelog,validate-tt-specs,html"> -->
-      <echo>ttml11.html is ready for CVS commit</echo>
-      <echo>Use target "generate" to avoid regenerating changelog.xml and acknowledgments.xml</echo>
+    <target name="sg" description="Shortened generation of the specification without updating changelog and acknowledgments sections, but without rebuilding escapes."
+	    depends="generate-schema-archives,validate-tt-specs-dont-build-escapes,html">
     </target>
 
 </project>
--- a/ttml11/spec/changelog.xml	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<feed xmlns:h="http://www.w3.org/1999/xhtml" xmlns="http://www.w3.org/2005/Atom">
-   <id>http://dev.w3.org</id>
-   <updated>-01-TZ</updated>
-   <title> CVS log</title>
-   <author>
-      <name>World Wide Web Consortium</name>
-      <uri>http://dev.w3.org</uri>
-   </author>
-   <link rel="alternate" type="text/html" href="http://dev.w3.org"/>
-   <link rel="self" href="http://dev.w3.org"/>
-   <rights>World Wide Web Consortium</rights>
-</feed>
\ No newline at end of file
Binary file ttml11/spec/diffmk.jar has changed
--- a/ttml11/spec/diffspec.xsl	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,373 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!--This file was created automatically by html2xhtml-->
-<!--from the HTML stylesheets. Do not edit this file.-->
-<!-- Version: $Id$ --><!-- Stylesheet for @diff markup in XMLspec --><!-- Author: Norman Walsh (Norman.Walsh@East.Sun.COM) --><!-- Date Created: 2000.07.21 --><!-- This stylesheet is copyright (c) 2000 by its authors.  Free
-     distribution and modification is permitted, including adding to
-     the list of authors and copyright holders, as long as this
-     copyright notice is maintained. --><!-- This stylesheet attempts to implement the XML Specification V2.1
-     DTD.  Documents conforming to earlier DTDs may not be correctly
-     transformed.
-
-     This stylesheet supports the use of change-markup with the @diff
-     attribute. If you use @diff, you should always use this stylesheet.
-     If you want to turn off the highlighting of differences, use this
-     stylesheet, but set show.diff.markup to 0.
-
-     Using the original xmlspec stylesheet with @diff markup will cause
-     @diff=del text to be presented.
---><!-- ChangeLog:
-     25 Sep 2000: (Norman.Walsh@East.Sun.COM)
-       - Use inline diff markup (as opposed to block) for name and
-         affiliation
-       - Handle @diff='del' correctly in bibl and other list-contexts.
-     14 Aug 2000: (Norman.Walsh@East.Sun.COM)
-       - Support additional.title param
-     27 Jul 2000: (Norman.Walsh@East.Sun.COM)
-       - Fix HTML markup problem with diff'd authors in authlist
-     26 Jul 2000: (Norman.Walsh@East.Sun.COM)
-       - Update pointer to latest xmlspec-stylesheet.
-     21 Jul 2000: (Norman.Walsh@East.Sun.COM)
-       - Initial version
---><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
-
-<xsl:import href="xmlspec.xsl"/>
-
-<xsl:param name="show.diff.markup" select="1"/>
-
-<xsl:param name="additional.css">
-<xsl:if test="$show.diff.markup != '0'">
-<xsl:text>
-div.diff-add  { background-color: #FFFF99; }
-div.diff-del  { text-decoration: line-through; }
-div.diff-chg  { background-color: #99FF99; }
-div.diff-off  {  }
-
-span.diff-add { background-color: #FFFF99; }
-span.diff-del { text-decoration: line-through; }
-span.diff-chg { background-color: #99FF99; }
-span.diff-off {  }
-
-td.diff-add   { background-color: #FFFF99; }
-td.diff-del   { text-decoration: line-through }
-td.diff-chg   { background-color: #99FF99; }
-td.diff-off   {  }
-</xsl:text>
-</xsl:if>
-</xsl:param>
-
-<xsl:param name="additional.title">
-  <xsl:if test="$show.diff.markup != '0'">
-    <xsl:text>Review Version</xsl:text>
-  </xsl:if>
-</xsl:param>
-
-<xsl:param name="called.by.diffspec" select="1"/>
-
-<!-- ==================================================================== -->
-
-  <!-- spec: the specification itself -->
-  <xsl:template match="spec">
-    <html xmlns="http://www.w3.org/1999/xhtml">
-      <xsl:if test="header/langusage/language">
-        <xsl:attribute name="lang">
-          <xsl:value-of select="header/langusage/language/@id"/>
-        </xsl:attribute>
-      </xsl:if>
-      <head>
-	
-        <title>
-          <xsl:apply-templates select="header/title"/>
-          <xsl:if test="header/version">
-            <xsl:text> </xsl:text>
-            <xsl:apply-templates select="header/version"/>
-          </xsl:if>
-          <xsl:if test="$additional.title != ''">
-            <xsl:text> -- </xsl:text>
-            <xsl:value-of select="$additional.title"/>
-	  </xsl:if>
-        </title>
-        <xsl:call-template name="css"/>
-      </head>
-      <body>
-        <xsl:if test="$show.diff.markup != 0">
-          <div>
-            <p>The presentation of this document has been augmented to
-            identify changes from a previous version. Three kinds of changes
-            are highlighted: <span class="diff-add">new, added text</span>,
-            <span class="diff-chg">changed text</span>, and
-            <span class="diff-del">deleted text</span>.</p>
-            <hr/>
-          </div>
-        </xsl:if>
-        <xsl:apply-templates/>
-        <xsl:if test="//footnote[not(ancestor::table)]">
-          <hr/>
-          <div class="endnotes">
-            <xsl:text>
-</xsl:text>
-            <h3>
-              <xsl:call-template name="anchor">
-                <xsl:with-param name="conditional" select="0"/>
-                <xsl:with-param name="default.id" select="'endnotes'"/>
-              </xsl:call-template>
-              <xsl:text>End Notes</xsl:text>
-            </h3>
-            <dl>
-              <xsl:apply-templates select="//footnote[not(ancestor::table)]" mode="notes"/>
-            </dl>
-          </div>
-        </xsl:if>
-      </body>
-    </html>
-  </xsl:template>
-
-<!-- ==================================================================== -->
-
-<xsl:template name="diff-markup">
-  <xsl:param name="diff">off</xsl:param>
-  <xsl:choose>
-    <xsl:when test="ancestor::scrap">
-      <!-- forget it, we can't add stuff inside tables -->
-      <!-- handled in base stylesheet -->
-      <xsl:apply-imports/>
-    </xsl:when>
-    <xsl:when test="self::gitem or self::bibl">
-      <!-- forget it, we can't add stuff inside dls; handled below -->
-      <xsl:apply-imports/>
-    </xsl:when>
-    <xsl:when test="ancestor-or-self::phrase">
-      <span xmlns="http://www.w3.org/1999/xhtml" class="diff-{$diff}">
-	<xsl:apply-imports/>
-      </span>
-    </xsl:when>
-    <xsl:when test="ancestor::p and not(self::p)">
-      <span xmlns="http://www.w3.org/1999/xhtml" class="diff-{$diff}">
-	<xsl:apply-imports/>
-      </span>
-    </xsl:when>
-    <xsl:when test="ancestor-or-self::affiliation">
-      <span xmlns="http://www.w3.org/1999/xhtml" class="diff-{$diff}">
-	<xsl:apply-imports/>
-      </span>
-    </xsl:when>
-    <xsl:when test="ancestor-or-self::name">
-      <span xmlns="http://www.w3.org/1999/xhtml" class="diff-{$diff}">
-	<xsl:apply-imports/>
-      </span>
-    </xsl:when>
-    <xsl:otherwise>
-      <div xmlns="http://www.w3.org/1999/xhtml" class="diff-{$diff}">
-	<xsl:apply-imports/>
-      </div>
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-<xsl:template match="*[@diff='chg']">
-  <xsl:choose>
-    <xsl:when test="$show.diff.markup != 0">
-      <xsl:call-template name="diff-markup">
-	<xsl:with-param name="diff">chg</xsl:with-param>
-      </xsl:call-template>
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:apply-imports/>
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-<xsl:template match="*[@diff='add']">
-  <xsl:choose>
-    <xsl:when test="$show.diff.markup != 0">
-      <xsl:call-template name="diff-markup">
-	<xsl:with-param name="diff">add</xsl:with-param>
-      </xsl:call-template>
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:apply-imports/>
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-<xsl:template match="*[@diff='del']">
-  <xsl:choose>
-    <xsl:when test="$show.diff.markup != 0">
-      <xsl:call-template name="diff-markup">
-	<xsl:with-param name="diff">del</xsl:with-param>
-      </xsl:call-template>
-    </xsl:when>
-    <xsl:otherwise>
-      <!-- suppress deleted markup -->
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-<xsl:template match="*[@diff='off']">
-  <xsl:choose>
-    <xsl:when test="$show.diff.markup != 0">
-      <xsl:call-template name="diff-markup">
-	<xsl:with-param name="diff">off</xsl:with-param>
-      </xsl:call-template>
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:apply-imports/>
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-<!-- ================================================================= -->
-
-  <xsl:template match="bibl[@diff]" priority="1">
-    <xsl:variable name="dt">
-      <xsl:if test="@id">
-	<a xmlns="http://www.w3.org/1999/xhtml" name="{@id}"/>
-      </xsl:if>
-      <xsl:choose>
-	<xsl:when test="@key">
-	  <xsl:value-of select="@key"/>
-	</xsl:when>
-	<xsl:otherwise>
-	  <xsl:value-of select="@id"/>
-	</xsl:otherwise>
-      </xsl:choose>
-    </xsl:variable>
-    <xsl:variable name="dd">
-      <xsl:apply-templates/>
-      <xsl:if test="@href">
-        <xsl:text>  (See </xsl:text>
-        <xsl:value-of select="@href"/>
-        <xsl:text>.)</xsl:text>
-      </xsl:if>
-    </xsl:variable>
-
-    <xsl:choose>
-      <xsl:when test="@diff and $show.diff.markup != 0">
-	<dt xmlns="http://www.w3.org/1999/xhtml" class="label">
-	  <span class="diff-{@diff}">
-	    <xsl:copy-of select="$dt"/>
-	  </span>
-	</dt>
-	<dd xmlns="http://www.w3.org/1999/xhtml">
-	  <div class="diff-{@diff}">
-	    <xsl:copy-of select="$dd"/>
-	  </div>
-	</dd>
-      </xsl:when>
-      <xsl:when test="@diff='del' and $show.diff.markup = 0">
-	<!-- suppressed -->
-      </xsl:when>
-      <xsl:otherwise>
-	<dt xmlns="http://www.w3.org/1999/xhtml" class="label">
-	  <xsl:copy-of select="$dt"/>
-	</dt>
-	<dd xmlns="http://www.w3.org/1999/xhtml">
-	  <xsl:copy-of select="$dd"/>
-	</dd>
-      </xsl:otherwise>
-    </xsl:choose>
-  </xsl:template>
-
-  <xsl:template match="gitem/label">
-    <xsl:variable name="diffval" select="ancestor-or-self::*/@diff"/>
-    <xsl:choose>
-      <xsl:when test="$diffval != '' and $show.diff.markup != 0">
-	<dt xmlns="http://www.w3.org/1999/xhtml" class="label">
-	  <span class="diff-{ancestor-or-self::*/@diff}">
-	    <xsl:apply-templates/>
-	  </span>
-	</dt>
-      </xsl:when>
-      <xsl:when test="$diffval='del' and $show.diff.markup = 0">
-	<!-- suppressed -->
-      </xsl:when>
-      <xsl:otherwise>
-	<dt xmlns="http://www.w3.org/1999/xhtml" class="label">
-	  <xsl:apply-templates/>
-	</dt>
-      </xsl:otherwise>
-    </xsl:choose>
-  </xsl:template>
-
-  <xsl:template match="gitem/def">
-    <xsl:variable name="diffval" select="ancestor-or-self::*/@diff"/>
-    <xsl:choose>
-      <xsl:when test="$diffval != '' and $show.diff.markup != 0">
-	<dd xmlns="http://www.w3.org/1999/xhtml">
-	  <div class="diff-{ancestor-or-self::*/@diff}">
-	    <xsl:apply-templates/>
-	  </div>
-	</dd>
-      </xsl:when>
-      <xsl:when test="$diffval='del' and $show.diff.markup = 0">
-	<!-- suppressed -->
-      </xsl:when>
-      <xsl:otherwise>
-	<dd xmlns="http://www.w3.org/1999/xhtml">
-	  <xsl:apply-templates/>
-	</dd>
-      </xsl:otherwise>
-    </xsl:choose>
-  </xsl:template>
-
-  <!-- authlist: list of authors (editors, really) -->
-  <!-- called in enforced order from header's template, in <dl>
-       context -->
-  <xsl:template match="authlist[@diff]">
-    <xsl:choose>
-      <xsl:when test="$show.diff.markup != 0">
-	<dt xmlns="http://www.w3.org/1999/xhtml">
-	  <span class="diff-{ancestor-or-self::*/@diff}">
-	    <xsl:text>Editor</xsl:text>
-	    <xsl:if test="count(author) &gt; 1">
-	      <xsl:text>s</xsl:text>
-	    </xsl:if>
-	    <xsl:text>:</xsl:text>
-	  </span>
-	</dt>
-      </xsl:when>
-      <xsl:when test="@diff='del' and $show.diff.markup = 0">
-	<!-- suppressed -->
-      </xsl:when>
-      <xsl:otherwise>
-	<dt xmlns="http://www.w3.org/1999/xhtml">
-	  <xsl:text>Editor</xsl:text>
-	  <xsl:if test="count(author) &gt; 1">
-	    <xsl:text>s</xsl:text>
-	  </xsl:if>
-	  <xsl:text>:</xsl:text>
-	</dt>
-      </xsl:otherwise>
-    </xsl:choose>
-    <xsl:apply-templates/>
-  </xsl:template>
-
-  <!-- author: an editor of a spec -->
-  <!-- only appears in authlist -->
-  <!-- called in <dl> context -->
-  <xsl:template match="author[@diff]" priority="1">
-    <xsl:choose>
-      <xsl:when test="@diff and $show.diff.markup != 0">
-	<dd xmlns="http://www.w3.org/1999/xhtml">
-	  <span class="diff-{ancestor-or-self::*/@diff}">
-	    <xsl:apply-templates/>
-	    <xsl:if test="@role = '2e'">
-	      <xsl:text> - Second Edition</xsl:text>
-	    </xsl:if>
-	  </span>
-	</dd>
-      </xsl:when>
-      <xsl:when test="@diff='del' and $show.diff.markup = 0">
-	<!-- suppressed -->
-      </xsl:when>
-      <xsl:otherwise>
-	<dd xmlns="http://www.w3.org/1999/xhtml">
-	  <xsl:apply-templates/>
-	  <xsl:if test="@role = '2e'">
-	    <xsl:text> - Second Edition</xsl:text>
-	  </xsl:if>
-	</dd>
-      </xsl:otherwise>
-    </xsl:choose>
-  </xsl:template>
-
-</xsl:stylesheet>
--- a/ttml11/spec/editlist.txt	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,125 +0,0 @@
-********************************************************************************
-*                                  EDIT LIST                                   *
-********************************************************************************
-
-ALREADY IMPLEMENTED
-
-[GA-A-024-20081214] 7.1.{4,6}   correct prose to accommodate nested divs and spans
-[GA-A-026-20090130] *           define default region
-[GA-A-027-20081214] 9.3.2 (7)   map anonymous spans to fo:inline only when parent is p or span
-[GA-A-028-20090130] *           move tts:extent from body to tt element
-[GA-A-029-20090130] *           fix inconsistency regarding time containment semantics
-[GA-A-030-20090130] 10.2        clarify semantics for dur and end
-[GA-A-032-20090130] 9.1.2       add ttm:role to region element
-[GA-A-033-20090415] *           unify and better formalize style resolution process
-[GA-A-034-20090427] 8.2.7       add "rollUp" shorthand value to tts:dynamicFlow
-[GA-A-035-20090504] 3.2         subdivide into transformation and presentation conformance
-[GA-A-036-20090504] C           update schemas
-[GA-I-008-20090415] 12.2.2      add "description" value to ttm:role enumeration
-[GA-I-009-20090504] 11,12       add examples to metadata and animation element vocabulary
-[GA-I-012-20090130] *           define default region
-[GA-I-015-20090415] *           change XML and XML Namespace references
-[GA-I-016-20081214] 10.2.*      fix incorrect reference to smil2 section (should be 10.4.1)
-[GA-I-017-20081214] 8.3.4       correct definition of <duration> syntax to <digit>+
-[GA-I-027-20081214] 8.2.20      correct names of textDecoration values (lineThrough)
-[GA-I-028-20090130] 8.2.13      elaborate prose to accommodate nested spans
-[GA-I-032-20090415] 8.4.3       style chaining an left preference
-[GA-I-033-20090415] 8.3.{5,14}  allow unquoted font family name that contains whitespace
-[GA-I-034-20090130] 9.3         elaborate processing of anonymous spans
-[GA-I-035-20090415] 8.3.1       opacity float value
-[GA-I-036-20090130] 8.2         inheritance by anonymous spans
-[GA-I-037-20081214] 9.3.2 (7)   map anonymous spans to fo:inline only when parent is p or span
-[GA-I-040-20090415] *           unify and better formalize style resolution process
-[GA-I-041-20090415] 7.1.3       change body to parallel time containment as default
-[GA-I-042-20090130] 9.3         processing in absence of region attribute
-[GA-I-043-20090415] 9.3.2       correct content hierarchy region mapping example code
-[GA-I-044-20081214] B.4         change typo "withing" to "within"
-[GA-I-045-20081214] 8.2.24      remove extra '"' at end of last line of wrap option example
-[GA-I-046-20081214] 8.2.23      missing inheritance and percentage constraints
-[GA-I-048-20090130] *           specify requiredExtensions and requiredFeatures
-[GA-I-050-20090130] *           improve consistency of style association prose on content elts
-[GA-I-051-20090130] 8.2.5       allow tts:display to apply to region element
-[GA-I-052-20090130] 8.3         fix order and missing entry in list of style value expressions
-[GA-I-054-20090427] 8.{2,4}     remove explicit inheritance
-[GA-I-055-20090427] 8.2.{20,21} make textDecoration and textOutline inheritable
-[GA-I-056-20090504] 8.2.20      fix indentation of tts:textDecoration example
-[GA-I-059-20090427] 8.2.*       make all style properties animatable
-[GA-I-060-20090504] 5.2,6.1     enhance profile specification mechanism
-[GA-I-061-20090427] B.3.{1,2}   correct flow interval computation with definite rate
-[GA-I-062-20090427] B.2         clarify meaning of "difference" in contents of flow buffer
-[GA-I-063-20090427] B.2         clarify meaning of "logical content position"
-[GA-I-064-20090427] B.5         clarify timeline used for dynamic flow
-[GA-I-065-20090427] 8.2.7,B     account for side effects of animation
-[GA-I-066-20090427] B.2         clarify assumptions regarding flow buffer state persistence
-[GA-I-067-20090427] B.2         clarify handling of temporal style changes w.r.t. flow buffer
-[GA-I-068-20090504] 9.3.3       ensure last block of body's block is filled out to region
-[GA-I-069-20090504] 8.2.8       mandate explicit lengths for tts:extent on tt:tt element
-[GA-I-070-20090504] 8.2.16      clarify "region's width and height were infinite"
-[GA-I-073-20090427] 1.2         remove superfluous text
-[GA-I-075-20090504] 5.2         clarify use of optional feature/extension
-[GA-I-076-20090427] 8.2.13      fix typo
-[GA-I-077-20090427] 8.2.*       add missing prose regarding anonymous spans
-[GA-I-078-20090427] 8.3.14      remove spurious reference to whitespace S syntactic element
-[GA-I-079-20090427] G           update XSL reference to XSL 1.1
-[GA-I-080-20090504] I           remove sample code appendix
-[GA-I-081-20090427] 8.3.6,B     remove 'pixel' flow unit and flow transitions
-[GA-I-082-20090427] 8.2.{13,16} change 'scroll' value to 'dynamic' for tts:overflow
-[GA-I-083-20090427] B.4         clarify flow operations prose logical vs formatted units
-[GA-I-084-20090427] 8.3.6       specify semantics if smooth or fade flow style not supported
-[GA-I-085-20090504] 6.2.4       ttp:frameRateMultiplier - missing default for denominator
-[GA-I-086-20090504] 8.3.6,B     tts:dynamicFlow - remove fade, within()
-[GA-I-087-20090504] 5.1         change TT style namespace value to #styling instead of #style
-[GA-I-088-20090504] *           remove editorial notes
-[GA-I-089-20090504] 12.2.2      ttm:role - allow multiple tokens
-[GA-I-090-20090504] 8.2.14      improve opacity semantics
-[GA-I-091-20090504] 8.2.*       implement style defaults
-[GA-I-092-20090529] 6.1.{2,4}   change base to xml:base
-[GA-I-093-20090529] 6.1.{2,4}   change base to xml:base
-[GA-I-094-20090529] 5.1,I       specify that TT namespaces are mutable
-[GA-I-096-20090529] G.3         create DFXP "Full" profile, requiring all features
-[GA-I-097-20090529] 12.1.1      fix metadata content model
-[GA-I-098-20090529] B           eliminate or clarify clear timing
-[GA-I-099-20090529] B           clarify semantics of blocked fill operation
-[GA-I-100-20090529] 8.3.6,B     remove block and inline fill units
-[GA-I-101-20090529] 8.2.7,I     add note justifying rollUp interval
-[GA-I-102-20090529] 8.[23].7,B  change names of intra() and inter() flow interval functions
-[GA-I-103-20090529] 8.2.7       proscribe multiple instances of same flow function
-[GA-I-104-20090529] B.{2,3}     clarify flow buffer language
-[GA-I-105-20090529] 8.2.16,B.4  clarify interaction between dynamic flow and wrap property
-[GA-I-106-20090529] 9.4,E       clarify line breaking, add line breaking feature designator
-[GA-I-108-20090529] G.1         remove redundant transformation requirement in transform profile
-[GA-I-110-20090529] 7.1.2       explicitly allow foreign attributes on head element
-[GA-I-111-20090529] 12.1.1      fix note regarding context of usage of metadata items
-[GA-I-112-20090529] 5.3.2       remove style, metadata, and parameter extension namespaces
-[GA-I-113-20090529] 3,E         remove circularity in definition of processor conformance
-[GA-I-114-20090529] E.2,G.2     reduce presentation profile requirements
-[GA-I-115-20090529] E.2,G.1     expand transformation profile requirements
-[GA-I-116-20090529] 5.2,6.{1,2} aggregate certain ttp:profile related text into one place
-[GA-I-117-20090529] 5.2,6.1     add 'use' value to ttp:{feature,extension} value attribute
-[GA-I-118-20090530] 9.3.2       clarify region association algorithm
-[GA-I-119-20090720] C.1         change #style to #styling, remove #*-extension NS in RNC schema
-[GA-I-120-20090720] C.1         add missing direction and unicodeBidi styles in RNC schema
-[GA-I-121-20090720] C.1         fix RNC schema problem with regard to ttm:agent
-[GA-I-122-20090720] 6.2.6       ttp:pixelAspectRatio - eliminate ':' separator
-[GA-I-122-20090720] 6.2.4       ttp:frameRateMultiplier - eliminate ':' separator
-[GA-I-123-20090720] 6.2.4       ttp:frameRateMultiplier - constrain numerator to non-zero
-[GA-I-125-20090720] 8.2.6       tts:displayAlign - remove inheritance
-[GA-I-126-20090720] 8.3.7       tts:dynamicFlow - needs flow style duration parameter
-[GA-I-128-20090720] B.5         tts:dynamicFlow - fix typos
-[GA-I-131-20090720] 5.1,6.1     profile, feature, and extension namespaces need trailing '/'
-[GA-I-132-20090720] *           miscellaneous typos
-[GA-I-133-20090720] 8.2.14      improve language regarding 'transparency'
-[GA-I-134-20090720] 8.2.15      reorder constraints on root container origin
-[GA-I-135-20090720] 10.2.3      add note regarding presence of both 'dur' and 'end' attributes
-[GA-I-136-20090720] 8.2.10      add note upon first use of 'c' length metric
-[GA-I-137-20090720] 12.1.1      tt:metadata - add example of foreign namespace element usage
-[GA-I-140-20090720] 10.2.3      @dur - add note on meaning of clock-time expressions
-[GA-I-141-20090720] 6.2.5,10.2.3 @dur - constrain usage with discontinuous marker mode
-[GA-I-142-20090720] *           change name of ttp:smpteMode to ttp:dropMode
-[GA-I-145-20090720] 4.1         elaborate note about potential false negative using RNC schema
-[GA-I-146-20090720] 8.2.7       tts:dynamicFlow - prohibit instances of same <flowFunction>
-[GA-I-127-20090905] 8.3.7,B     add 'break' flow interval argument
-[GA-I-129-20090905] 8.2.7       use 'break' flow interval argument in tts:dynamicFlow example
-[GA-I-130-20090905] E,G         add, rename feature designations
-[GA-I-147-20090905] 6.2.11      clarify 'media time' when using clock timebase
-[GA-I-148-20090905] 10.4        clarify 'offset based time' when using media or continuous smpte timebase
--- a/ttml11/spec/entities.dtd	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/entities.dtd	Tue Jul 09 14:39:28 2013 -0600
@@ -19,7 +19,6 @@
 
 <!ENTITY acknowledgements SYSTEM "acknowledgements.xml" >
 <!ENTITY acknowledgements-current SYSTEM "acknowledgements-current.txt" >
-<!ENTITY acknowledgements-old SYSTEM "acknowledgements-old.txt" >
 
 <!-- Misc entities. Feel free to add more -->
 
--- a/ttml11/spec/entitiescr.dtd	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,31 +0,0 @@
-<?xml version='1.0' encoding='ISO-8859-1' ?>
-
-<!--
-  Date parameters
-  -->
-<!ENTITY draft.year "2010">
-<!ENTITY draft.month "February">
-<!ENTITY draft.mm "02">
-<!ENTITY draft.day "23">
-<!ENTITY draft.dd "23">
-
-<!ENTITY draft.date "&draft.year;&draft.mm;&draft.dd;">
-
-<!ENTITY prefix "ttaf1-dfxp">
-
-<!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 Candidate Recommendation">
-<!ENTITY w3c.status "CR">
-<!ENTITY doctype "cr">
-
-<!ENTITY w3c-designation
-  "&w3c.tr.latest;/&draft.year;/&w3c.status;-&prefix;-&draft.date;/">
--- a/ttml11/spec/entitieswd.dtd	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,31 +0,0 @@
-<?xml version='1.0' encoding='ISO-8859-1' ?>
-
-<!--
-  Date parameters
-  -->
-<!ENTITY draft.year "2009">
-<!ENTITY draft.month "June">
-<!ENTITY draft.mm "06">
-<!ENTITY draft.day "02">
-<!ENTITY draft.dd "02">
-
-<!ENTITY draft.date "&draft.year;&draft.mm;&draft.dd;">
-
-<!ENTITY prefix "ttaf1-dfxp">
-
-<!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 Working Draft">
-<!ENTITY w3c.status "WD">
-<!ENTITY doctype "wd">
-
-<!ENTITY w3c-designation
-  "&w3c.tr.latest;/&draft.year;/&w3c.status;-&prefix;-&draft.date;/">
--- a/ttml11/spec/examples/ex1-p-0.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/examples/ex1-p-0.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,54 +1,64 @@
-<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
-  <fo:layout-master-set>
-    <fo:simple-page-master master-name="m1"
-      page-width="640px" page-height="480px">
-      <fo:region-body/>
-    </fo:simple-page-master>
-  </fo:layout-master-set>
-  <fo:page-sequence master-reference="m1">
-    <fo:flow flow-name="xsl-region-body">
-      <!-- region (r1) -->
-      <fo:block-container id="r1" absolute-position="absolute"
-        left="10px" top="100px" width="620px" height="96px"
-        background-color="black" display-align="center">
-        <!-- body (b1) -->
-        <fo:block id="b1-1">
-          <!-- div (d1) -->
-          <fo:block id="d1-1">
-            <!-- p (p1) -->
-            <fo:block id="p1" text-align="center">
-              <fo:inline font-size="40px" font-weight="bold"
-              color="red">Text 1</fo:inline>
-            </fo:block>
-          </fo:block>
-          <!-- body's space filler ->
-          <fo:block
-            space-after.optimum="96px"
-            space-after.maximum="96px"
-            space-after.conditionality="retain"/>
-        </fo:block>
-      </fo:block-container>
-      <!-- region (r2) -->
-      <fo:block-container id="r2" absolute-position="absolute"
-        left="10px" top="300px" width="620px" height="96px"
-        background-color="black" display-align="center">
-        <!-- body (b1) -->
-        <fo:block id="b1-2">
-          <!-- div (d1) -->
-          <fo:block id="d1-2">
-            <!-- p (p2) -->
-            <fo:block id="p2" text-align="center">
-              <fo:inline font-size="40px" font-weight="bold"
-              color="yellow">Text 2</fo:inline>
-            </fo:block>
-          </fo:block>
-          <!-- body's space filler ->
-          <fo:block
-            space-after.optimum="96px"
-            space-after.maximum="96px"
-            space-after.conditionality="retain"/>
-        </fo:block>
-      </fo:block-container>
-    </fo:flow>
-  </fo:page-sequence>
-</fo:root>
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
+  <fo:layout-master-set>
+    <fo:simple-page-master master-name="m1"
+      page-width="640px" page-height="480px">
+      <fo:region-body/>
+    </fo:simple-page-master>
+  </fo:layout-master-set>
+  <fo:page-sequence master-reference="m1">
+    <fo:flow flow-name="xsl-region-body">
+      <!-- region (r1) -->
+      <fo:block-container id="r1" absolute-position="absolute"
+        left="10px" top="100px" width="620px" height="96px"
+        background-color="black" display-align="center">
+        <!-- body (b1) -->
+        <fo:block id="b1-1">
+          <!-- body's space (before) filler -->
+          <fo:block
+            space-after.optimum="96px"
+            space-after.maximum="96px"
+            space-after.conditionality="retain"/>
+          <!-- div (d1) -->
+          <fo:block id="d1-1">
+            <!-- p (p1) -->
+            <fo:block id="p1" text-align="center">
+              <fo:inline font-size="40px" font-weight="bold"
+              color="red">Text 1</fo:inline>
+            </fo:block>
+          </fo:block>
+          <!-- body's space (after) filler -->
+          <fo:block
+            space-after.optimum="96px"
+            space-after.maximum="96px"
+            space-after.conditionality="retain"/>
+        </fo:block>
+      </fo:block-container>
+      <!-- region (r2) -->
+      <fo:block-container id="r2" absolute-position="absolute"
+        left="10px" top="300px" width="620px" height="96px"
+        background-color="black" display-align="center">
+        <!-- body (b1) -->
+        <fo:block id="b1-2">
+          <!-- body's space (before) filler -->
+          <fo:block
+            space-after.optimum="96px"
+            space-after.maximum="96px"
+            space-after.conditionality="retain"/>
+          <!-- div (d1) -->
+          <fo:block id="d1-2">
+            <!-- p (p2) -->
+            <fo:block id="p2" text-align="center">
+              <fo:inline font-size="40px" font-weight="bold"
+              color="yellow">Text 2</fo:inline>
+            </fo:block>
+          </fo:block>
+          <!-- body's space (after) filler -->
+          <fo:block
+            space-after.optimum="96px"
+            space-after.maximum="96px"
+            space-after.conditionality="retain"/>
+        </fo:block>
+      </fo:block-container>
+    </fo:flow>
+  </fo:page-sequence>
+</fo:root>
--- a/ttml11/spec/examples/ex1-x-0.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/examples/ex1-x-0.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,38 +1,38 @@
-<tt tts:extent="640px 480px" xml:lang="en"
-  xmlns="http://www.w3.org/ns/ttml"
-  xmlns:tts="http://www.w3.org/ns/ttml#styling">
-  <head>
-    <layout>
-      <region xml:id="r1">
-        <style tts:origin="10px 100px"/>
-        <style tts:extent="620px 96px"/>
-        <style tts:fontSize="40px"/>
-        <style tts:fontWeight="bold"/>
-        <style tts:backgroundColor="black"/>
-        <style tts:color="red"/>
-        <style tts:textAlign="center"/>
-        <style tts:displayAlign="center"/>
-        <body xml:id="b1-1">
-          <div xml:id="d1-1">
-            <p xml:id="p1">Text 1</p>
-          </div>
-        </body>
-      </region>
-      <region xml:id="r2">
-        <style tts:origin="10px 300px"/>
-        <style tts:extent="620px 96px"/>
-        <style tts:fontSize="40px"/>
-        <style tts:fontWeight="bold"/>
-        <style tts:backgroundColor="black"/>
-        <style tts:color="yellow"/>
-        <style tts:textAlign="center"/>
-        <style tts:displayAlign="center"/>
-        <body xml:id="b1-2">
-          <div xml:id="d1-2">
-            <p xml:id="p2">Text 2</p>
-          </div>
-        </body>
-      </region>
-    </layout>
-  </head>
-</tt>
+<tt tts:extent="640px 480px" xml:lang="en"
+  xmlns="http://www.w3.org/ns/ttml"
+  xmlns:tts="http://www.w3.org/ns/ttml#styling">
+  <head>
+    <layout>
+      <region xml:id="r1">
+        <style tts:origin="10px 100px"/>
+        <style tts:extent="620px 96px"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontWeight="bold"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:color="red"/>
+        <style tts:textAlign="center"/>
+        <style tts:displayAlign="center"/>
+        <body xml:id="b1-1">
+          <div xml:id="d1-1">
+            <p xml:id="p1">Text 1</p>
+          </div>
+        </body>
+      </region>
+      <region xml:id="r2">
+        <style tts:origin="10px 300px"/>
+        <style tts:extent="620px 96px"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontWeight="bold"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:color="yellow"/>
+        <style tts:textAlign="center"/>
+        <style tts:displayAlign="center"/>
+        <body xml:id="b1-2">
+          <div xml:id="d1-2">
+            <p xml:id="p2">Text 2</p>
+          </div>
+        </body>
+      </region>
+    </layout>
+  </head>
+</tt>
--- a/ttml11/spec/examples/ex1-x-1.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/examples/ex1-x-1.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,44 +1,44 @@
-<tt tts:extent="640px 480px" xml:lang="en"
-  xmlns="http://www.w3.org/ns/ttml"
-  xmlns:tts="http://www.w3.org/ns/ttml#styling">
-  <head>
-    <layout>
-      <region xml:id="r1">
-        <style tts:origin="10px 100px"/>
-        <style tts:extent="620px 96px"/>
-        <style tts:fontSize="40px"/>
-        <style tts:fontWeight="bold"/>
-        <style tts:backgroundColor="black"/>
-        <style tts:color="red"/>
-        <style tts:textAlign="center"/>
-        <style tts:displayAlign="center"/>
-        <body xml:id="b1-1">
-          <div xml:id="d1-1">
-            <p xml:id="p1">Text 1</p>
-          </div>
-          <div xml:id="d2-1">
-            <p xml:id="p4">Text 4</p>
-          </div>
-        </body>
-      </region>
-      <region xml:id="r2">
-        <style tts:origin="10px 300px"/>
-        <style tts:extent="620px 96px"/>
-        <style tts:fontSize="40px"/>
-        <style tts:fontWeight="bold"/>
-        <style tts:backgroundColor="black"/>
-        <style tts:color="yellow"/>
-        <style tts:textAlign="center"/>
-        <style tts:displayAlign="center"/>
-        <body xml:id="b1-2">
-          <div xml:id="d1-2">
-            <p xml:id="p2">Text 2</p>
-          </div>
-          <div xml:id="d2-2">
-            <p xml:id="p3">Text 3</p>
-          </div>
-        </body>
-      </region>
-    </layout>
-  </head>
-</tt>
+<tt tts:extent="640px 480px" xml:lang="en"
+  xmlns="http://www.w3.org/ns/ttml"
+  xmlns:tts="http://www.w3.org/ns/ttml#styling">
+  <head>
+    <layout>
+      <region xml:id="r1">
+        <style tts:origin="10px 100px"/>
+        <style tts:extent="620px 96px"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontWeight="bold"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:color="red"/>
+        <style tts:textAlign="center"/>
+        <style tts:displayAlign="center"/>
+        <body xml:id="b1-1">
+          <div xml:id="d1-1">
+            <p xml:id="p1">Text 1</p>
+          </div>
+          <div xml:id="d2-1">
+            <p xml:id="p4">Text 4</p>
+          </div>
+        </body>
+      </region>
+      <region xml:id="r2">
+        <style tts:origin="10px 300px"/>
+        <style tts:extent="620px 96px"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontWeight="bold"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:color="yellow"/>
+        <style tts:textAlign="center"/>
+        <style tts:displayAlign="center"/>
+        <body xml:id="b1-2">
+          <div xml:id="d1-2">
+            <p xml:id="p2">Text 2</p>
+          </div>
+          <div xml:id="d2-2">
+            <p xml:id="p3">Text 3</p>
+          </div>
+        </body>
+      </region>
+    </layout>
+  </head>
+</tt>
--- a/ttml11/spec/examples/ex1-x-2.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/examples/ex1-x-2.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,38 +1,38 @@
-<tt tts:extent="640px 480px" xml:lang="en"
-  xmlns="http://www.w3.org/ns/ttml"
-  xmlns:tts="http://www.w3.org/ns/ttml#styling">
-  <head>
-    <layout>
-      <region xml:id="r1">
-        <style tts:origin="10px 100px"/>
-        <style tts:extent="620px 96px"/>
-        <style tts:fontSize="40px"/>
-        <style tts:fontWeight="bold"/>
-        <style tts:backgroundColor="black"/>
-        <style tts:color="red"/>
-        <style tts:textAlign="center"/>
-        <style tts:displayAlign="center"/>
-        <body xml:id="b1-1">
-          <div xml:id="d2-1">
-            <p xml:id="p4">Text 4</p>
-          </div>
-        </body>
-      </region>
-      <region xml:id="r2">
-        <style tts:origin="10px 300px"/>
-        <style tts:extent="620px 96px"/>
-        <style tts:fontSize="40px"/>
-        <style tts:fontWeight="bold"/>
-        <style tts:backgroundColor="black"/>
-        <style tts:color="yellow"/>
-        <style tts:textAlign="center"/>
-        <style tts:displayAlign="center"/>
-        <body xml:id="b1-2">
-          <div xml:id="d2-2">
-            <p xml:id="p3">Text 3</p>
-          </div>
-        </body>
-      </region>
-    </layout>
-  </head>
-</tt>
+<tt tts:extent="640px 480px" xml:lang="en"
+  xmlns="http://www.w3.org/ns/ttml"
+  xmlns:tts="http://www.w3.org/ns/ttml#styling">
+  <head>
+    <layout>
+      <region xml:id="r1">
+        <style tts:origin="10px 100px"/>
+        <style tts:extent="620px 96px"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontWeight="bold"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:color="red"/>
+        <style tts:textAlign="center"/>
+        <style tts:displayAlign="center"/>
+        <body xml:id="b1-1">
+          <div xml:id="d2-1">
+            <p xml:id="p4">Text 4</p>
+          </div>
+        </body>
+      </region>
+      <region xml:id="r2">
+        <style tts:origin="10px 300px"/>
+        <style tts:extent="620px 96px"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontWeight="bold"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:color="yellow"/>
+        <style tts:textAlign="center"/>
+        <style tts:displayAlign="center"/>
+        <body xml:id="b1-2">
+          <div xml:id="d2-2">
+            <p xml:id="p3">Text 3</p>
+          </div>
+        </body>
+      </region>
+    </layout>
+  </head>
+</tt>
--- a/ttml11/spec/examples/ex1.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/examples/ex1.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,38 +1,38 @@
-<tt tts:extent="640px 480px" xml:lang="en"
-  xmlns="http://www.w3.org/ns/ttml"
-  xmlns:tts="http://www.w3.org/ns/ttml#styling">
-  <head>
-    <layout>
-      <region xml:id="r1">
-        <style tts:origin="10px 100px"/>
-        <style tts:extent="620px 96px"/>
-        <style tts:fontSize="40px"/>
-        <style tts:fontWeight="bold"/>
-        <style tts:backgroundColor="black"/>
-        <style tts:color="red"/>
-        <style tts:textAlign="center"/>
-        <style tts:displayAlign="center"/>
-      </region>
-      <region xml:id="r2">
-        <style tts:origin="10px 300px"/>
-        <style tts:extent="620px 96px"/>
-        <style tts:fontSize="40px"/>
-        <style tts:fontWeight="bold"/>
-        <style tts:backgroundColor="black"/>
-        <style tts:color="yellow"/>
-        <style tts:textAlign="center"/>
-        <style tts:displayAlign="center"/>
-      </region>
-    </layout>
-  </head>
-  <body xml:id="b1">
-    <div xml:id="d1" begin="0s" dur="2s">
-      <p xml:id="p1" region="r1">Text 1</p>
-      <p xml:id="p2" region="r2">Text 2</p>
-    </div>
-    <div xml:id="d2" begin="1s" dur="2s">
-      <p xml:id="p3" region="r2">Text 3</p>
-      <p xml:id="p4" region="r1">Text 4</p>
-    </div>
-  </body>
-</tt>
+<tt tts:extent="640px 480px" xml:lang="en"
+  xmlns="http://www.w3.org/ns/ttml"
+  xmlns:tts="http://www.w3.org/ns/ttml#styling">
+  <head>
+    <layout>
+      <region xml:id="r1">
+        <style tts:origin="10px 100px"/>
+        <style tts:extent="620px 96px"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontWeight="bold"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:color="red"/>
+        <style tts:textAlign="center"/>
+        <style tts:displayAlign="center"/>
+      </region>
+      <region xml:id="r2">
+        <style tts:origin="10px 300px"/>
+        <style tts:extent="620px 96px"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontWeight="bold"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:color="yellow"/>
+        <style tts:textAlign="center"/>
+        <style tts:displayAlign="center"/>
+      </region>
+    </layout>
+  </head>
+  <body xml:id="b1">
+    <div xml:id="d1" begin="0s" dur="2s">
+      <p xml:id="p1" region="r1">Text 1</p>
+      <p xml:id="p2" region="r2">Text 2</p>
+    </div>
+    <div xml:id="d2" begin="1s" dur="2s">
+      <p xml:id="p3" region="r2">Text 3</p>
+      <p xml:id="p4" region="r1">Text 4</p>
+    </div>
+  </body>
+</tt>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml11/spec/examples/ex2-paint-on.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -0,0 +1,47 @@
+<tt ttp:cellResolution="60 20" xml:lang="en" xmlns="http://www.w3.org/ns/ttml"
+  xmlns:tts="http://www.w3.org/ns/ttml#parameter" xmlns:tts="http://www.w3.org/ns/ttml#styling">
+  <head>
+    <layout>
+      <region xml:id="r1" tts:color="white" tts:origin="10c 4c" tts:extent="40c 5c"/>
+    </layout>
+  </head>
+  <body>
+    <div begin="0s" end="25s">
+      <p>
+        <span begin="0s">Lorem</span>
+        <span begin="1s">ipsum</span>
+        <span begin="2s">dolor</span>
+        <span begin="3s">sit</span>
+      </p>
+      <p>
+        <span begin="4s">Amet</span>                
+        <span begin="5s">consectetur</span>
+        <span begin="6s">adipiscing</span>
+        <span begin="7s">elit</span>
+      </p>
+      <p>
+        <span begin="8s">Sed</span>
+        <span begin="9s">do</span>
+        <span begin="10s">eiusmod</span>
+        <span begin="11s">tempor</span>
+        <span begin="12s">incididunt </span>
+        <span begin="13s">labore</span>
+     </p>
+     <p>
+        <span begin="14s">et</span>
+        <span begin="15s">dolore</span>
+        <span begin="16s">magna</span>
+        <span begin="17s">aliqua</span>
+      </p>
+      <p>
+        <span begin="18s">Ut</span>
+        <span begin="19s">enim</span>
+        <span begin="20s">ad</span>
+        <span begin="21s">minim</span>
+        <span begin="22s">veniam</span>
+        <span begin="23s">quis,</span>
+        <span begin="24s">nostrud</span>
+      </p>
+    </div>
+  </body>
+</tt>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml11/spec/examples/ex2-pop-on.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -0,0 +1,18 @@
+<tt ttp:cellResolution="60 20" xml:lang="en" xmlns="http://www.w3.org/ns/ttml"
+  xmlns:tts="http://www.w3.org/ns/ttml#parameter" xmlns:tts="http://www.w3.org/ns/ttml#styling">
+  <head>
+    <layout>
+      <region xml:id="r1" tts:color="white" tts:origin="10c 4c" tts:extent="40c 1c"/>
+      <region xml:id="r2" tts:color="yellow" tts:origin="10c 8c" tts:extent="40c 1c"/>
+    </layout>
+  </head>
+  <body>
+    <div timeContainer="seq">
+      <p region="r1" dur="4s">Lorem ipsum dolor sit</p
+      <p region="r2" dur="4s">Amet consectetur adipiscing elit</p>
+      <p region="r1" dur="6s">Sed do eiusmod tempor incididunt labore</p>
+      <p region="r2" dur="4s">et dolore magna aliqua</p>
+      <p region="r1" dur="7s">Ut enim ad minim veniam quis, nostrud</p>
+    </div>
+  </body>
+</tt>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml11/spec/examples/ex2-roll-up.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -0,0 +1,17 @@
+<tt ttp:cellResolution="60 20" xml:lang="en" xmlns="http://www.w3.org/ns/ttml"
+  xmlns:tts="http://www.w3.org/ns/ttml#parameter" xmlns:tts="http://www.w3.org/ns/ttml#styling">
+  <head>
+    <layout>
+      <region xml:id="r1" tts:color="white" tts:origin="10c 4c" tts:extent="40c 2c"/>
+    </layout>
+  </head>
+  <body>
+    <div region="r1">
+      <p begin="0s" end="8s">Lorem ipsum dolor sit</p
+      <p begin="4s" end="12s">Amet consectetur adipiscing elit</p>
+      <p begin="8s" end="18s">Sed do eiusmod tempor incididunt labore</p>
+      <p begin="14s" end="25s">et dolore magna aliqua</p>
+      <p begin="18s" end="29s">Ut enim ad minim veniam quis, nostrud</p>
+    </div>
+  </body>
+</tt>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml11/spec/examples/ex3-all-elements.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -0,0 +1,71 @@
+<tt:tt
+  tts:extent="640px 480px"
+  xml:lang="en"
+  xml:space="default"
+  ttp:cellResolution="3 5"
+  ttp:clockMode="utc"
+  ttp:dropMode="nonDrop"
+  ttp:frameRate="30"
+  ttp:frameRateMultiplier="1000 1001"
+  ttp:markerMode="discontinuous"
+  ttp:pixelAspectRatio="4 3"
+  ttp:profile="http://www.w3.org/ns/ttml/profile/dfxp-presentation"
+  ttp:subFrameRate="2"
+  ttp:tickRate="60"
+  ttp:timeBase="media"
+  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">
+  <tt:head>
+    <tt:metadata xml:id="m1"/>
+    <ttm:title xml:id="title">A Title</ttm:title>
+    <ttm:desc xml:id="description">This example TTML document attempts to use every element.</ttm:desc>
+    <ttm:copyright xml:id="copyright">Never and Anon.</ttm:copyright>
+    <ttm:agent xml:id="connery" type="person">
+      <ttm:name type="full">Sir Thomas Sean Connery</ttm:name>
+    </ttm:agent>
+    <ttm:agent xml:id="bond" type="character">
+      <ttm:name type="alias">007</ttm:name>
+      <ttm:actor agent="connery"/>
+    </ttm:agent>
+    <ttp:profile xml:id="profile" use="dfxp-presentation">
+      <tt:metadata xml:id="m2"/>
+      <ttp:features xml:id="f1set" xml:base="http://www.w3.org/ns/ttml/feature/">
+        <tt:metadata/>
+        <ttp:feature xml:id="f1" value="required">#fontStyle-italic</ttp:feature>
+      </ttp:features>
+      <ttp:extensions xml:id="e1set" xml:base="http://www.w3.org/ns/ttml/extension/">
+        <tt:metadata/>
+        <ttp:extension xml:id="e1" value="required">#smpte-tt-image</ttp:extension>
+      </ttp:extensions>
+    </ttp:profile>
+    <tt:styling>
+      <tt:metadata xml:id="m3"/>
+      <tt:style xml:id="s1" tts:color="red"/>
+    </tt:styling>
+    <tt:layout>
+      <tt:metadata xml:id="m4"/>
+      <tt:region xml:id="r1" style="s1">
+        <tt:metadata xml:id="m5"/>
+        <tt:set xml:id="a1" tts:zIndex="-1"/>
+        <tt:style xml:id="s2" tts:color="green"/>
+      </tt:region>
+    </tt:layout>
+  </tt:head>
+  <tt:body region="r1">
+    <tt:metadata xml:id="m6"/>
+    <tt:set xml:id="a2" tts:display="auto"/>
+    <tt:div>
+      <tt:metadata xml:id="m7"/>
+      <tt:set xml:id="a3" tts:writingMode="tb"/>
+      <tt:p ttm:agent="bond" ttm:role="caption x-extension-role-1">
+        <tt:metadata xml:id="m8"/>
+        <tt:set xml:id="a4" tts:visibility="hidden"/>
+        <tt:span><tt:metadata xml:id="m9"/><tt:set xml:id="a5" tts:fontSize="20px"/>Text 1</tt:span>
+        <tt:br><tt:metadata xml:id="m10"/><tt:set xml:id="a6" tts:display="none"/></tt:br>
+        <tt:span><tt:metadata xml:id="m11"/>Text 2</tt:span>
+      </tt:p>
+    </tt:div>
+  </tt:body>
+</tt:tt>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml11/spec/examples/ex3-all-styles.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -0,0 +1,363 @@
+<tt tts:extent="640px 480px" xml:lang="en" xmlns="http://www.w3.org/ns/ttml" xmlns:tts="http://www.w3.org/ns/ttml#styling">
+  <head>
+    <layout>
+      <region xml:id="r1">
+        <!-- legal backgroundColor values (not exhaustive) -->
+        <style tts:backgroundColor="#000000"/>
+        <style tts:backgroundColor="#c0c0c0"/>
+        <style tts:backgroundColor="#808080"/>
+        <style tts:backgroundColor="#ffffff"/>
+        <style tts:backgroundColor="#800000"/>
+        <style tts:backgroundColor="#ff0000"/>
+        <style tts:backgroundColor="#800080"/>
+        <style tts:backgroundColor="#ff00ff"/>
+        <style tts:backgroundColor="#008000"/>
+        <style tts:backgroundColor="#00ff00"/>
+        <style tts:backgroundColor="#808000"/>
+        <style tts:backgroundColor="#ffff00"/>
+        <style tts:backgroundColor="#000080"/>
+        <style tts:backgroundColor="#0000ff"/>
+        <style tts:backgroundColor="#008080"/>
+        <style tts:backgroundColor="#00ffff"/>
+        <style tts:backgroundColor="#00000000"/>
+        <style tts:backgroundColor="#000000ff"/>
+        <style tts:backgroundColor="#c0c0c0ff"/>
+        <style tts:backgroundColor="#808080ff"/>
+        <style tts:backgroundColor="#ffffffff"/>
+        <style tts:backgroundColor="#800000ff"/>
+        <style tts:backgroundColor="#ff0000ff"/>
+        <style tts:backgroundColor="#800080ff"/>
+        <style tts:backgroundColor="#ff00ffff"/>
+        <style tts:backgroundColor="#008000ff"/>
+        <style tts:backgroundColor="#00ff00ff"/>
+        <style tts:backgroundColor="#808000ff"/>
+        <style tts:backgroundColor="#ffff00ff"/>
+        <style tts:backgroundColor="#000080ff"/>
+        <style tts:backgroundColor="#0000ffff"/>
+        <style tts:backgroundColor="#008080ff"/>
+        <style tts:backgroundColor="#00ffffff"/>
+        <style tts:backgroundColor="rgb(0,0,0)"/>
+        <style tts:backgroundColor="rgb(192,192,192)"/>
+        <style tts:backgroundColor="rgb(128,128,128)"/>
+        <style tts:backgroundColor="rgb(255,255,255)"/>
+        <style tts:backgroundColor="rgb(128,0,0)"/>
+        <style tts:backgroundColor="rgb(255,0,0)"/>
+        <style tts:backgroundColor="rgb(128,0,128)"/>
+        <style tts:backgroundColor="rgb(255,0,255)"/>
+        <style tts:backgroundColor="rgb(255,0,255)"/>
+        <style tts:backgroundColor="rgb(0,128,0)"/>
+        <style tts:backgroundColor="rgb(0,255,0)"/>
+        <style tts:backgroundColor="rgb(128,128,0)"/>
+        <style tts:backgroundColor="rgb(255,255,0)"/>
+        <style tts:backgroundColor="rgb(0,0,128)"/>
+        <style tts:backgroundColor="rgb(0,0,255)"/>
+        <style tts:backgroundColor="rgb(0,128,128)"/>
+        <style tts:backgroundColor="rgb(0,255,255)"/>
+        <style tts:backgroundColor="rgb(0,255,255)"/>
+        <style tts:backgroundColor="rgba(0,0,0,0)"/>
+        <style tts:backgroundColor="rgba(0,0,0,255)"/>
+        <style tts:backgroundColor="rgba(192,192,192,255)"/>
+        <style tts:backgroundColor="rgba(128,128,128,255)"/>
+        <style tts:backgroundColor="rgba(255,255,255,255)"/>
+        <style tts:backgroundColor="rgba(128,0,0,255)"/>
+        <style tts:backgroundColor="rgba(255,0,0,255)"/>
+        <style tts:backgroundColor="rgba(128,0,128,255)"/>
+        <style tts:backgroundColor="rgba(255,0,255,255)"/>
+        <style tts:backgroundColor="rgba(255,0,255,255)"/>
+        <style tts:backgroundColor="rgba(0,128,0,255)"/>
+        <style tts:backgroundColor="rgba(0,255,0,255)"/>
+        <style tts:backgroundColor="rgba(128,128,0,255)"/>
+        <style tts:backgroundColor="rgba(255,255,0,255)"/>
+        <style tts:backgroundColor="rgba(0,0,128,255)"/>
+        <style tts:backgroundColor="rgba(0,0,255,255)"/>
+        <style tts:backgroundColor="rgba(0,128,128,255)"/>
+        <style tts:backgroundColor="rgba(0,255,255,255)"/>
+        <style tts:backgroundColor="rgba(0,255,255,255)"/>
+        <style tts:backgroundColor="transparent"/>
+        <style tts:backgroundColor="black"/>
+        <style tts:backgroundColor="silver"/>
+        <style tts:backgroundColor="gray"/>
+        <style tts:backgroundColor="white"/>
+        <style tts:backgroundColor="maroon"/>
+        <style tts:backgroundColor="red"/>
+        <style tts:backgroundColor="purple"/>
+        <style tts:backgroundColor="fuchsia"/>
+        <style tts:backgroundColor="magenta"/>
+        <style tts:backgroundColor="green"/>
+        <style tts:backgroundColor="lime"/>
+        <style tts:backgroundColor="olive"/>
+        <style tts:backgroundColor="yellow"/>
+        <style tts:backgroundColor="navy"/>
+        <style tts:backgroundColor="blue"/>
+        <style tts:backgroundColor="teal"/>
+        <style tts:backgroundColor="aqua"/>
+        <style tts:backgroundColor="cyan"/>
+        <!-- legal color values (not exhaustive) -->
+        <style tts:color="#000000"/>
+        <style tts:color="#c0c0c0"/>
+        <style tts:color="#808080"/>
+        <style tts:color="#ffffff"/>
+        <style tts:color="#800000"/>
+        <style tts:color="#ff0000"/>
+        <style tts:color="#800080"/>
+        <style tts:color="#ff00ff"/>
+        <style tts:color="#008000"/>
+        <style tts:color="#00ff00"/>
+        <style tts:color="#808000"/>
+        <style tts:color="#ffff00"/>
+        <style tts:color="#000080"/>
+        <style tts:color="#0000ff"/>
+        <style tts:color="#008080"/>
+        <style tts:color="#00ffff"/>
+        <style tts:color="#00000000"/>
+        <style tts:color="#000000ff"/>
+        <style tts:color="#c0c0c0ff"/>
+        <style tts:color="#808080ff"/>
+        <style tts:color="#ffffffff"/>
+        <style tts:color="#800000ff"/>
+        <style tts:color="#ff0000ff"/>
+        <style tts:color="#800080ff"/>
+        <style tts:color="#ff00ffff"/>
+        <style tts:color="#008000ff"/>
+        <style tts:color="#00ff00ff"/>
+        <style tts:color="#808000ff"/>
+        <style tts:color="#ffff00ff"/>
+        <style tts:color="#000080ff"/>
+        <style tts:color="#0000ffff"/>
+        <style tts:color="#008080ff"/>
+        <style tts:color="#00ffffff"/>
+        <style tts:color="rgb(0,0,0)"/>
+        <style tts:color="rgb(192,192,192)"/>
+        <style tts:color="rgb(128,128,128)"/>
+        <style tts:color="rgb(255,255,255)"/>
+        <style tts:color="rgb(128,0,0)"/>
+        <style tts:color="rgb(255,0,0)"/>
+        <style tts:color="rgb(128,0,128)"/>
+        <style tts:color="rgb(255,0,255)"/>
+        <style tts:color="rgb(255,0,255)"/>
+        <style tts:color="rgb(0,128,0)"/>
+        <style tts:color="rgb(0,255,0)"/>
+        <style tts:color="rgb(128,128,0)"/>
+        <style tts:color="rgb(255,255,0)"/>
+        <style tts:color="rgb(0,0,128)"/>
+        <style tts:color="rgb(0,0,255)"/>
+        <style tts:color="rgb(0,128,128)"/>
+        <style tts:color="rgb(0,255,255)"/>
+        <style tts:color="rgb(0,255,255)"/>
+        <style tts:color="rgba(0,0,0,0)"/>
+        <style tts:color="rgba(0,0,0,255)"/>
+        <style tts:color="rgba(192,192,192,255)"/>
+        <style tts:color="rgba(128,128,128,255)"/>
+        <style tts:color="rgba(255,255,255,255)"/>
+        <style tts:color="rgba(128,0,0,255)"/>
+        <style tts:color="rgba(255,0,0,255)"/>
+        <style tts:color="rgba(128,0,128,255)"/>
+        <style tts:color="rgba(255,0,255,255)"/>
+        <style tts:color="rgba(255,0,255,255)"/>
+        <style tts:color="rgba(0,128,0,255)"/>
+        <style tts:color="rgba(0,255,0,255)"/>
+        <style tts:color="rgba(128,128,0,255)"/>
+        <style tts:color="rgba(255,255,0,255)"/>
+        <style tts:color="rgba(0,0,128,255)"/>
+        <style tts:color="rgba(0,0,255,255)"/>
+        <style tts:color="rgba(0,128,128,255)"/>
+        <style tts:color="rgba(0,255,255,255)"/>
+        <style tts:color="rgba(0,255,255,255)"/>
+        <style tts:color="transparent"/>
+        <style tts:color="black"/>
+        <style tts:color="silver"/>
+        <style tts:color="gray"/>
+        <style tts:color="white"/>
+        <style tts:color="maroon"/>
+        <style tts:color="red"/>
+        <style tts:color="purple"/>
+        <style tts:color="fuchsia"/>
+        <style tts:color="magenta"/>
+        <style tts:color="green"/>
+        <style tts:color="lime"/>
+        <style tts:color="olive"/>
+        <style tts:color="yellow"/>
+        <style tts:color="navy"/>
+        <style tts:color="blue"/>
+        <style tts:color="teal"/>
+        <style tts:color="aqua"/>
+        <style tts:color="cyan"/>
+        <!-- legal direction values -->
+        <style tts:direction="ltr"/>
+        <style tts:direction="rtl"/>
+        <!-- legal display values -->
+        <style tts:display="auto"/>
+        <style tts:display="none"/>
+        <!-- legal displayAlign values -->
+        <style tts:displayAlign="before"/>
+        <style tts:displayAlign="center"/>
+        <style tts:displayAlign="after"/>
+        <!-- legal extent values (not exhaustive) -->
+        <style tts:extent="auto"/>
+        <style tts:extent="620px 96px"/>
+        <!-- legal fontFamily values (not exhaustive) -->
+        <style tts:fontFamily="default"/>
+        <style tts:fontFamily="monospace"/>
+        <style tts:fontFamily="sansSerif"/>
+        <style tts:fontFamily="serif"/>
+        <style tts:fontFamily="monospaceSansSerif"/>
+        <style tts:fontFamily="monospaceSerif"/>
+        <style tts:fontFamily="proportionalSansSerif"/>
+        <style tts:fontFamily="proportionalSerif"/>
+        <style tts:fontFamily="Courier New"/>
+        <style tts:fontFamily="'Courier New'"/>
+        <style tts:fontFamily="default, Courier New"/>
+        <style tts:fontFamily="default, 'Courier New'"/>
+        <style tts:fontFamily="Courier New, default"/>
+        <style tts:fontFamily="'Courier New', default"/>
+        <!-- legal fontSize values (not exhaustive) -->
+        <style tts:fontSize="1c"/>
+        <style tts:fontSize="40px"/>
+        <style tts:fontSize="40px 50px"/>
+        <style tts:fontSize="40px 1c"/>
+        <!-- legal fontStyle values -->
+        <style tts:fontStyle="normal"/>
+        <style tts:fontStyle="italic"/>
+        <style tts:fontStyle="oblique"/>
+        <!-- legal fontWeight values -->
+        <style tts:fontWeight="normal"/>
+        <style tts:fontWeight="bold"/>
+        <!-- legal lineHeight values (not exhaustive) -->
+        <style tts:lineHeight="normal"/>
+        <style tts:lineHeight="1c"/>
+        <style tts:lineHeight="40px"/>
+        <!-- legal opacity values (not exhaustive) -->
+        <style tts:opacity="0"/>
+        <style tts:opacity="0.5"/>
+        <style tts:opacity="1"/>
+        <!-- legal origin values (not exhaustive) -->
+        <style tts:origin="auto"/>
+        <style tts:origin="10px 100px"/>
+        <style tts:origin="1c 10c"/>
+        <style tts:origin="40px 10c"/>
+        <!-- legal overflow values -->
+        <style tts:overflow="visible"/>
+        <style tts:overflow="hidden"/>
+        <!-- legal padding values (not exhaustive) -->
+        <style tts:padding="1px"/>
+        <style tts:padding="1px 2px"/>
+        <style tts:padding="1px 2px 3px"/>
+        <style tts:padding="1px 2px 3px 4px"/>
+        <!-- legal showBackground values -->
+        <style tts:showBackground="always"/>
+        <style tts:showBackground="whenActive"/>
+        <!-- legal textAlign values -->
+        <style tts:textAlign="left"/>
+        <style tts:textAlign="center"/>
+        <style tts:textAlign="right"/>
+        <style tts:textAlign="start"/>
+        <style tts:textAlign="end"/>
+        <!-- legal textDecoration values -->
+        <style tts:textDecoration="none"/>
+        <style tts:textDecoration="underline"/>
+        <style tts:textDecoration="noUnderline"/>
+        <style tts:textDecoration="lineThrough"/>
+        <style tts:textDecoration="noLineThrough"/>
+        <style tts:textDecoration="overline"/>
+        <style tts:textDecoration="noOverline"/>
+        <style tts:textDecoration="noUnderline noLineThrough"/>
+        <style tts:textDecoration="noLineThrough noUnderline"/>
+        <style tts:textDecoration="noUnderline lineThrough"/>
+        <style tts:textDecoration="lineThrough noUnderline"/>
+        <style tts:textDecoration="underline noLineThrough"/>
+        <style tts:textDecoration="noLineThrough underline"/>
+        <style tts:textDecoration="underline lineThrough"/>
+        <style tts:textDecoration="lineThrough underline"/>
+        <style tts:textDecoration="noUnderline noOverline"/>
+        <style tts:textDecoration="noOverline noUnderline"/>
+        <style tts:textDecoration="noUnderline overline"/>
+        <style tts:textDecoration="overline noUnderline"/>
+        <style tts:textDecoration="underline noOverline"/>
+        <style tts:textDecoration="noOverline underline"/>
+        <style tts:textDecoration="underline overline"/>
+        <style tts:textDecoration="overline underline"/>
+        <style tts:textDecoration="noUnderline noLineThrough noOverline"/>
+        <style tts:textDecoration="noUnderline noOverline noLineThrough"/>
+        <style tts:textDecoration="noLineThrough noUnderline noOverline"/>
+        <style tts:textDecoration="noLineThrough noOverline noUnderline"/>
+        <style tts:textDecoration="noOverline noUnderline noLineThrough"/>
+        <style tts:textDecoration="noOverline noLineThrough noUnderline"/>
+        <style tts:textDecoration="noUnderline noLineThrough overline"/>
+        <style tts:textDecoration="noUnderline overline noLineThrough"/>
+        <style tts:textDecoration="noLineThrough noUnderline overline"/>
+        <style tts:textDecoration="noLineThrough overline noUnderline"/>
+        <style tts:textDecoration="overline noUnderline noLineThrough"/>
+        <style tts:textDecoration="overline noLineThrough noUnderline"/>
+        <style tts:textDecoration="noUnderline lineThrough noOverline"/>
+        <style tts:textDecoration="noUnderline noOverline lineThrough"/>
+        <style tts:textDecoration="lineThrough noUnderline noOverline"/>
+        <style tts:textDecoration="lineThrough noOverline noUnderline"/>
+        <style tts:textDecoration="noOverline noUnderline lineThrough"/>
+        <style tts:textDecoration="noOverline lineThrough noUnderline"/>
+        <style tts:textDecoration="noUnderline lineThrough overline"/>
+        <style tts:textDecoration="noUnderline overline lineThrough"/>
+        <style tts:textDecoration="lineThrough noUnderline overline"/>
+        <style tts:textDecoration="lineThrough overline noUnderline"/>
+        <style tts:textDecoration="overline noUnderline lineThrough"/>
+        <style tts:textDecoration="overline lineThrough noUnderline"/>
+        <style tts:textDecoration="underline noLineThrough noOverline"/>
+        <style tts:textDecoration="underline noOverline noLineThrough"/>
+        <style tts:textDecoration="noLineThrough underline noOverline"/>
+        <style tts:textDecoration="noLineThrough noOverline underline"/>
+        <style tts:textDecoration="noOverline underline noLineThrough"/>
+        <style tts:textDecoration="noOverline noLineThrough underline"/>
+        <style tts:textDecoration="underline noLineThrough overline"/>
+        <style tts:textDecoration="underline overline noLineThrough"/>
+        <style tts:textDecoration="noLineThrough underline overline"/>
+        <style tts:textDecoration="noLineThrough overline underline"/>
+        <style tts:textDecoration="overline underline noLineThrough"/>
+        <style tts:textDecoration="overline noLineThrough underline"/>
+        <style tts:textDecoration="underline lineThrough noOverline"/>
+        <style tts:textDecoration="underline noOverline lineThrough"/>
+        <style tts:textDecoration="lineThrough underline noOverline"/>
+        <style tts:textDecoration="lineThrough noOverline underline"/>
+        <style tts:textDecoration="noOverline underline lineThrough"/>
+        <style tts:textDecoration="noOverline lineThrough underline"/>
+        <style tts:textDecoration="underline lineThrough overline"/>
+        <style tts:textDecoration="underline overline lineThrough"/>
+        <style tts:textDecoration="lineThrough underline overline"/>
+        <style tts:textDecoration="lineThrough overline underline"/>
+        <style tts:textDecoration="overline underline lineThrough"/>
+        <style tts:textDecoration="overline lineThrough underline"/>
+        <!-- legal textOutline values (not exhaustive) -->
+        <style tts:textOutline="yellow 1px"/>
+        <style tts:textOutline="yellow 1px 2px"/>
+        <style tts:textOutline="1px"/>
+        <style tts:textOutline="1px 2px"/>
+        <!-- legal unicodeBidi values -->
+        <style tts:unicodeBidi="normal"/>
+        <style tts:unicodeBidi="embed"/>
+        <style tts:unicodeBidi="bidiOverride"/>
+        <!-- legal visibility values -->
+        <style tts:visibility="visible"/>
+        <style tts:visibility="hidden"/>
+        <!-- legal wrapOption values -->
+        <style tts:wrapOption="wrap"/>
+        <style tts:wrapOption="noWrap"/>
+        <!-- legal writingMode values -->
+        <style tts:writingMode="lrtb"/>
+        <style tts:writingMode="rltb"/>
+        <style tts:writingMode="tbrl"/>
+        <style tts:writingMode="tblr"/>
+        <style tts:writingMode="lr"/>
+        <style tts:writingMode="rl"/>
+        <style tts:writingMode="tb"/>
+        <!-- legal zIndex values (not exhaustive) -->
+        <style tts:zIndex="auto"/>
+        <style tts:zIndex="-1"/>
+        <style tts:zIndex="0"/>
+        <style tts:zIndex="1"/>
+      </region>
+    </layout>
+  </head>
+  <body region="r1">
+    <div>
+      <p>Text 1</p>
+    </div>
+  </body>
+</tt>
--- a/ttml11/spec/generate-acknowledgements.xsl	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-  xmlns:html="http://www.w3.org/1999/xhtml"
-  exclude-result-prefixes="html"
-  version="1.0">
-
-  <xsl:output
-    method="text"
-    indent="yes"
-    encoding="utf-8"
-    />
-
-  <xsl:param name="participating" />
-
-  <xsl:template match="/">
-    <xsl:call-template name="list-participants">
-      <xsl:with-param name="participating" select="$participating"/>
-    </xsl:call-template>
-  </xsl:template>
-
-  <xsl:template match="html:tr">
-      <xsl:value-of select="html:th[@class='name']/html:a"/>
-      <xsl:text> (</xsl:text>
-      <xsl:value-of select="html:td[@class='orgname']"/>
-      <xsl:text>)</xsl:text>
-  </xsl:template>
-
-  <xsl:template name="list-participants">
-    <xsl:param name="participating"/>
-    <xsl:variable name="status">
-      <xsl:choose>
-	<xsl:when test="$participating = 1">
-	  <xsl:text>good standing</xsl:text>
-	</xsl:when>
-	<xsl:otherwise>
-	  <xsl:text>no longer participating</xsl:text>	  
-	</xsl:otherwise>
-      </xsl:choose>
-    </xsl:variable>
-    <xsl:for-each select="//html:dl[contains(@class, 'group-member')
-			  and contains(normalize-space(html:dd[@class='status']), $status)]">
-      <xsl:value-of select="html:dt[@class='foaf-name']"/>
-      <xsl:if test="$participating = 1"><xsl:text> (</xsl:text>
-      <xsl:value-of select="html:dd[@class='orgname']"/>
-      <xsl:text>)</xsl:text></xsl:if>
-      <xsl:if test="position()!=last()">
-	<xsl:text>, </xsl:text>
-      </xsl:if>
-      <xsl:if test="position()=last()">
-	<xsl:text>.</xsl:text>
-      </xsl:if>
-    </xsl:for-each>
-  </xsl:template>
-
-</xsl:stylesheet>
--- a/ttml11/spec/profiles/dfxp-full.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/profiles/dfxp-full.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- this file defines the "dfxp-full" profile of ttaf1-dfxp -->
+<!-- this file defines the "dfxp-full" profile of ttml -->
 <profile xmlns="http://www.w3.org/ns/ttml#parameter">
   <features xml:base="http://www.w3.org/ns/ttml/feature/">
     <!-- required (mandatory) feature support -->
--- a/ttml11/spec/profiles/dfxp-presentation.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/profiles/dfxp-presentation.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- this file defines the "dfxp-presentation" profile of ttaf1-dfxp -->
+<!-- this file defines the "dfxp-presentation" profile of ttml -->
 <profile xmlns="http://www.w3.org/ns/ttml#parameter">
   <features xml:base="http://www.w3.org/ns/ttml/feature/">
     <!-- required (mandatory) feature support -->
--- a/ttml11/spec/profiles/dfxp-transformation.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/profiles/dfxp-transformation.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- this file defines the "dfxp-transformation" profile of ttaf1 -->
+<!-- this file defines the "dfxp-transformation" profile of ttml -->
 <profile xmlns="http://www.w3.org/ns/ttml#parameter">
   <features xml:base="http://www.w3.org/ns/ttml/feature/">
     <!-- required (mandatory) feature support -->
Binary file ttml11/spec/rnc/schema.zip has changed
--- a/ttml11/spec/rnc/ttml11-datatypes.rnc	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/rnc/ttml11-datatypes.rnc	Tue Jul 09 14:39:28 2013 -0600
@@ -3,7 +3,7 @@
 # .......................................................................
 
 TTAF.Alpha.datatype =
-  xsd:float { minInclusive = "0" maxInclusive = "1" }
+  xsd:float
 
 TTAF.Agent.datatype =
   xsd:IDREFS
@@ -72,13 +72,14 @@
   "bold"
 
 TTAF.FrameRate.datatype =
-  xsd:nonNegativeInteger
+  xsd:positiveInteger
 
 TTAF.FrameRateMultiplier.datatype =
   xsd:string { pattern = "\p{Nd}+\s+\p{Nd}+" }
 
 TTAF.LanguageCode.datatype =
-  xsd:NMTOKEN
+  "" |
+  xsd:language
 
 TTAF.LineHeight.datatype =
   string
@@ -121,7 +122,7 @@
   "transcription"
 
 TTAF.Opacity.datatype =
-  string
+  TTAF.Alpha.datatype
 
 TTAF.Origin.datatype =
   string
@@ -140,7 +141,11 @@
   TTAF.URI.datatype
 
 TTAF.Role.datatype =
-  xsd:NMTOKENS
+  list { TTAF.RoleItem.datatype+ }
+
+TTAF.RoleItem.datatype =
+  TTAF.MetadataRoleBaseType.datatype |
+  xsd:NMTOKEN { pattern = "x-\c+" }
 
 TTAF.ShowBackground.datatype =
   "always" |
@@ -160,10 +165,74 @@
   "none" |
   "underline" |
   "noUnderline" |
+  "lineThrough" |
+  "noLineThrough" |
   "overline" |
   "noOverline" |
-  "lineThrough" |
-  "noLineThrough"
+  "noUnderline noLineThrough" |
+  "noLineThrough noUnderline" |
+  "noUnderline lineThrough" |
+  "lineThrough noUnderline" |
+  "underline noLineThrough" |
+  "noLineThrough underline" |
+  "underline lineThrough" |
+  "lineThrough underline" |
+  "noUnderline noOverline" |
+  "noOverline noUnderline" |
+  "noUnderline overline" |
+  "overline noUnderline" |
+  "underline noOverline" |
+  "noOverline underline" |
+  "underline overline" |
+  "overline underline" |
+  "noUnderline noLineThrough noOverline" |
+  "noUnderline noOverline noLineThrough" |
+  "noLineThrough noUnderline noOverline" |
+  "noLineThrough noOverline noUnderline" |
+  "noOverline noUnderline noLineThrough" |
+  "noOverline noLineThrough noUnderline" |
+  "noUnderline noLineThrough overline" |
+  "noUnderline overline noLineThrough" |
+  "noLineThrough noUnderline overline" |
+  "noLineThrough overline noUnderline" |
+  "overline noUnderline noLineThrough" |
+  "overline noLineThrough noUnderline" |
+  "noUnderline lineThrough noOverline" |
+  "noUnderline noOverline lineThrough" |
+  "lineThrough noUnderline noOverline" |
+  "lineThrough noOverline noUnderline" |
+  "noOverline noUnderline lineThrough" |
+  "noOverline lineThrough noUnderline" |
+  "noUnderline lineThrough overline" |
+  "noUnderline overline lineThrough" |
+  "lineThrough noUnderline overline" |
+  "lineThrough overline noUnderline" |
+  "overline noUnderline lineThrough" |
+  "overline lineThrough noUnderline" |
+  "underline noLineThrough noOverline" |
+  "underline noOverline noLineThrough" |
+  "noLineThrough underline noOverline" |
+  "noLineThrough noOverline underline" |
+  "noOverline underline noLineThrough" |
+  "noOverline noLineThrough underline" |
+  "underline noLineThrough overline" |
+  "underline overline noLineThrough" |
+  "noLineThrough underline overline" |
+  "noLineThrough overline underline" |
+  "overline underline noLineThrough" |
+  "overline noLineThrough underline" |
+  "underline lineThrough noOverline" |
+  "underline noOverline lineThrough" |
+  "lineThrough underline noOverline" |
+  "lineThrough noOverline underline" |
+  "noOverline underline lineThrough" |
+  "noOverline lineThrough underline" |
+  "underline lineThrough overline" |
+  "underline overline lineThrough" |
+  "lineThrough underline overline" |
+  "lineThrough overline underline" |
+  "overline underline lineThrough" |
+  "overline lineThrough underline"
 
 TTAF.TextOutline.datatype =
   string
--- a/ttml11/spec/rnc/ttml11-metadata.rnc	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/rnc/ttml11-metadata.rnc	Tue Jul 09 14:39:28 2013 -0600
@@ -20,7 +20,6 @@
 TTAF.External.class =
   element * - ( tt:* | ttm:* ) {
     ( attribute * - ( xml:id ) { text }
-      | text
       | TTAF.External.class
     )*
   }
--- a/ttml11/spec/rnc/ttml11.rnc	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/rnc/ttml11.rnc	Tue Jul 09 14:39:28 2013 -0600
@@ -6,23 +6,23 @@
 default namespace tt = "http://www.w3.org/ns/ttml"
 
 # generic tt modules
-include "ttaf1-dfxp-datatypes.rnc"
-include "ttaf1-dfxp-classes.rnc"
-include "ttaf1-dfxp-core-attribs.rnc"
-include "ttaf1-dfxp-parameter-attribs.rnc"
-include "ttaf1-dfxp-metadata-attribs.rnc"
-include "ttaf1-dfxp-styling-attribs.rnc"
-include "ttaf1-dfxp-timing-attribs.rnc"
-include "ttaf1-dfxp-parameter-items.rnc"
-include "ttaf1-dfxp-parameters.rnc"
-include "ttaf1-dfxp-metadata-items.rnc"
-include "ttaf1-dfxp-metadata.rnc"
-include "ttaf1-dfxp-styling.rnc"
-include "ttaf1-dfxp-animation.rnc"
-include "ttaf1-dfxp-layout.rnc"
-include "ttaf1-dfxp-content.rnc"
-include "ttaf1-dfxp-head.rnc"
-include "ttaf1-dfxp-document.rnc"
+include "ttml11-datatypes.rnc"
+include "ttml11-classes.rnc"
+include "ttml11-core-attribs.rnc"
+include "ttml11-parameter-attribs.rnc"
+include "ttml11-metadata-attribs.rnc"
+include "ttml11-styling-attribs.rnc"
+include "ttml11-timing-attribs.rnc"
+include "ttml11-parameter-items.rnc"
+include "ttml11-parameters.rnc"
+include "ttml11-metadata-items.rnc"
+include "ttml11-metadata.rnc"
+include "ttml11-styling.rnc"
+include "ttml11-animation.rnc"
+include "ttml11-layout.rnc"
+include "ttml11-content.rnc"
+include "ttml11-head.rnc"
+include "ttml11-document.rnc"
 
 start = TTAF.tt | TTAF.parameters.profile
 
--- a/ttml11/spec/scm/.cvsignore	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,1 +0,0 @@
-*.esc
\ No newline at end of file
--- a/ttml11/spec/scm/adi.scm	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,124 +0,0 @@
-;;; -*-Scheme-*-
-;;; Package: (dfxp rxi adi)
-
-;
-; DFXP Abstrarct Document Instance Load, Save, Transformer
-;
-
-(declare (usual-integrations))
-
-(define *dfxp-preferred-reverse-bindings*
-  '(("http://www.w3.org/ns/ttml" . "")
-    ("http://www.w3.org/ns/ttml#parameter" . "ttp")
-    ("http://www.w3.org/ns/ttml#style" . "tts")
-    ("http://www.w3.org/ns/ttml#style-extension" . "ttsx")
-    ("http://www.w3.org/ns/ttml#metadata" . "ttm")
-    ("http://www.w3.org/ns/ttml#metadata-extension" . "ttmx")))
-
-(define *dfxp-namespaces-table*
-  (let ((t (make-string-hash-table)))
-    (for-each
-      (lambda (b)
-        (hash-table/put! t (car b) #t))
-      *dfxp-preferred-reverse-bindings*)
-    t))
-
-(define *dfxp-empty-element-types*
-  '(("br" . "http://www.w3.org/ns/ttml")
-    ("metadata" . "http://www.w3.org/ns/ttml")))
-
-(define (in-per-element-namespace? attr)
-  (let* ((name (rxi-attribute/name attr))
-         (namespace (rxi-name/namespace name)))
-    (null? namespace)))
-
-(define (in-dfxp-namespace? name)
-  (hash-table/get *dfxp-namespaces-table* (rxi-name/namespace name) #f))
-
-(define (in-xml-namespace? name)
-  (string=? (rxi-name/namespace name) (car *xml-default-reverse-binding*)))
-
-(define (in-dfxp-or-xml-namespace? name)
-  (or (in-dfxp-namespace? name)
-      (in-xml-namespace? name)))
-
-(define (empty-dfxp-element-type? elt)
-  (let* ((name (rxi-element/name elt))
-         (local (rxi-name/local name))
-         (namespace (rxi-name/namespace name)))
-    (find-matching-item
-      *dfxp-empty-element-types*
-      (lambda (n)
-        (and (string=? local (car n))
-             (string=? namespace (cdr n)))))))
-                        
-(define (only-whitespace-children? elt)
-  (let ((children (rxi-element/children elt)))
-    (not
-      (find-matching-item
-        children
-        (lambda (c)
-          (or (not (string? c))
-              (string-find-next-char-in-set c char-set:not-whitespace)))))))
-
-(define (rxi-document/adi-transform-element elt)
-  ;; prune and transform children
-  (set-rxi-element/children!
-    elt
-    (delete-matching-items
-      (map
-        (lambda (c)
-          (if (string? c)
-              c
-              (if (not (in-dfxp-namespace? (rxi-element/name c)))
-                  '()
-                  (rxi-document/adi-transform-element c))))
-        (rxi-element/children elt))
-      null?))
-  ;; prune remaining children if empty element type and only whitespace remains
-  (if (and (empty-dfxp-element-type? elt)
-           (only-whitespace-children? elt))
-      (set-rxi-element/children! elt '()))
-  ;; prune foreign namespace attributes
-  (set-rxi-element/attributes!
-    elt
-    (delete-matching-items
-      (rxi-element/attributes elt)
-      (lambda (a)
-          (not (or (in-per-element-namespace? a)
-                   (in-dfxp-or-xml-namespace? (rxi-attribute/name a)))))))
-  elt)
-
-(define (rxi-document/adi-transform document)
-  (if (not (null? (rxi-document/annotation document 'adi-transform)))
-      (warn "Document already transformed, ignoring re-transform.")
-      (let ((root (rxi-document/root document)))
-        (set-rxi-document/root! document (rxi-document/adi-transform-element root))
-        (set-rxi-document/annotation! document 'adi-transform #t)))
-  document)
-  
-;
-; Load TT AF document instance from PATHNAME using RXI loader,
-; then transform resulting RXI-DOCUMENT instance to an ADI-DOCUMENT
-; instance.
-;
-(define (adi-document/load pathname)
-  (rxi-document/adi-transform
-    (rxi-document/load pathname)))
-
-;
-; Save ADI-DOCUMENT instance DOCUMENT, which was created by ADI-DOCUMENT/LOAD,
-; to PATHNAME using underlying RXI-DOCUMENT's document serializer,
-; where optional argument OTHER-REVERSE-BINDINGS, if specified, consists
-; of an association list whose keys are namespace URIs and values are the
-; namespace prefixes to use to designate those namespaces.
-;
-; By default the set of refeverse bindings defined by *DFXP-PREFERRED-REVERSE-BINDING*
-; are used when serializaing. However, reverse bindings specified by using
-; OTHER-REVERSE-BINDINGS take precedence, overriding default reverse bindings.
-;
-(define (adi-document/save document pathname #!optional other-reverse-bindings)
-  (rxi-document/save document pathname
-    (if (default-object? other-reverse-bindings)
-        *dfxp-preferred-reverse-bindings*
-        (append other-reverse-bindings *dfxp-preferred-reverse-bindings*))))
--- a/ttml11/spec/scm/compile.scm	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,12 +0,0 @@
-;;; -*-Scheme-*-
-
-(load-option 'xml)
-(load-option 'cref)
-(with-working-directory-pathname (directory-pathname (current-load-pathname))
-  (lambda ()
-    (compile-file "rxi")
-    (compile-file "adi")
-    (compile-file "tir")
-    (compile-file "fox")
-    (compile-file "dtf")
-    (cref/generate-constructors "dfxp")))
--- a/ttml11/spec/scm/dfxp.pkg	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,39 +0,0 @@
-;;; -*-Scheme-*-
-
-(define-package (dfxp)
-  (parent()))
-
-(define-package (dfxp rxi)
-  (files "rxi")
-  (parent (dfxp))
-  (export ()
-          rxi-document/load
-          rxi-document/save
-          rxi-document->list))
-
-(define-package (dfxp rxi adi)
-  (files "adi")
-  (parent (dfxp rxi))
-  (export ()
-          rxi-document/adi-transform
-          adi-document/load
-          adi-document/save))
-
-(define-package (dfxp rxi adi tir)
-  (files "tir")
-  (parent (dfxp rxi adi))
-  (export ()
-          adi-document/tir-transform))
-
-(define-package (dfxp rxi adi tir fox)
-  (files "fox")
-  (parent (dfxp rxi adi tir))
-  (export ()
-          adi-document/fox-transform))
-
-(define-package (dfxp rxi adi tir dtf)
-  (files "dtf")
-  (parent (dfxp rxi adi tir))
-  (export ()
-          adi-document/dtf-process))
-
--- a/ttml11/spec/scm/dtf.scm	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,12 +0,0 @@
-;;; -*-Scheme-*-
-;;; Package: (dfxp rxi adi tir dtf)
-
-;;;; Dynamic Text Flow Processor
-
-(declare (usual-integrations))
-
-;
-; NOT YET IMPLEMENTED - TO BE PROVIDED PRIOR TO PROPOSED RECOMMENDATION PHASE
-;
-
-(define (adi-document/dtf-process document) document)
--- a/ttml11/spec/scm/fox.scm	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,12 +0,0 @@
-;;; -*-Scheme-*-
-;;; Package: (dfxp rxi adi tir fox)
-
-;;;; Flow Object Transformer
-
-(declare (usual-integrations))
-
-;
-; NOT YET IMPLEMENTED - TO BE PROVIDED PRIOR TO PROPOSED RECOMMENDATION PHASE
-;
-
-(define (adi-document/fox-transform document) document)
--- a/ttml11/spec/scm/load.scm	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,7 +0,0 @@
-;;; -*-Scheme-*-
-
-(load-option 'xml)
-(with-working-directory-pathname (directory-pathname (current-load-pathname))
-  (lambda ()
-    (package/system-loader "dfxp" '() 'query)))
-(add-subsystem-identification! "DFXP" '(0 8))
--- a/ttml11/spec/scm/rxi.scm	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,521 +0,0 @@
-;;; -*-Scheme-*-
-;;; Package: (dfxp rxi)
-
-;
-; DFXP Reduced XML Infoset Load, Save, Transformer
-;
-
-(declare (usual-integrations))
-
-;
-; The default reverse binding for the XML namespace is represented
-; by *XML-DEFAULT-REVERSE-BINDING*.
-;
-(define *xml-default-reverse-binding*
-  '("http://www.w3.org/XML/1998/namespace" . "xml"))
-
-;
-; An RXI-BINDINGS structure consists of a BINDINGS slot that contains a
-; stack represented as a list of association lists whose keys are XMLNS name
-; prefixes and whose values are XMLNS namespace URIs. A binding for the
-; "empty" or "null" namespace is designated by a prefix whose value is "".
-;
-(define-structure
-  (rxi-bindings
-    (conc-name rxi-bindings/)
-    (constructor make-rxi-bindings (#!optional bindings)))
-  (bindings '() read-only #f))
-
-;
-; Push a list of NEW bindings onto BINDINGS.
-;
-(define (rxi-bindings/push! bindings new)
-  (set-rxi-bindings/bindings!
-    bindings
-    (cons new (rxi-bindings/bindings bindings))))
-  
-;
-; Pop the list of bindings at the top of BINDINGS.
-;
-(define (rxi-bindings/pop! bindings)
-  (set-rxi-bindings/bindings!
-    bindings
-    (let ((old (rxi-bindings/bindings bindings)))
-      (if (pair? old)
-          (cdr old)
-          '()))))
-  
-;
-; Look up a binding for the designated XMLNS name PREFIX in BINDINGS,
-; returning either an associated XMLNS namespace URI string or '() if
-; not found.
-;
-
-(define (rxi-bindings/lookup bindings prefix)
-  (let find
-      ((bindings (rxi-bindings/bindings bindings)))
-    (cond ((null? bindings)
-           '())
-          (else
-            (let
-                ((b (find-matching-item
-                      (car bindings)
-                      (lambda (b) (string=? (car b) prefix)))))
-              (if (not (false? b))
-                  (cdr b)
-                  (find (cdr bindings))))))))
-
-;
-; Resolve qualified name QNAME to (VALUES LOCAL NSURI) where LOCAL is
-; the local (unqualified) component of QNAME and NSURI is the
-; associated namespace URI or '() if there is no associated namepsace
-; URI, where IS-ATTRIBUTE? indicates whether the QNAME is the name of
-; an attribute or an element.
-;
-; N.B. the lack of a namespace URI is permitted only for unqualified
-; attribute names; all element names must have an associated namespace URI
-; or an error is signaled. This implies that there must exist a binding for
-; the empty (null) namespace prefix when resolving unqualified element
-; names.
-;
-(define (rxi-bindings/resolve bindings qname is-attribute?)
-  (let* ((i (string-find-next-char qname #\:))
-         (pfx (substring qname 0 (if (false? i) 0 i)))
-         (local (string-tail qname (if (false? i) 0 (+ i 1)))))
-    (values
-      local
-      (if (or (> (string-length pfx) 0) (not is-attribute?))
-          (let ((uri (rxi-bindings/lookup bindings pfx)))
-            (or uri
-                (error "unbound XMLNS prefix on prefix" pfx)))
-          '()))))
-    
-;
-; An RXI-NAME structure represents the name and namespace properties of a
-; reduced XML infoset element or attribute information item and consists of
-; a local name LOCAL and an associated namespace NAMESPACE, a non-empty
-; string or '(), denoting that the name is not namespace qualified. An
-; RXI-NAME is essentially a representation of an XMLNS "expanded name".
-;
-(define-structure
-  (rxi-name (conc-name rxi-name/))
-  (local "" read-only #t)
-  (namespace '() read-only #t))
-
-;
-; Convert an RXI-NAME instance NAME to a list consisting of its constituent
-; slots.
-;
-(define (rxi-name->list name)
-  (list (rxi-name/local name)
-        (rxi-name/namespace name)))
-
-;
-; Transform an XML name IQNAME as defined by the XML package as an uninterned
-; symbol to an RXI-NAME, resolving qualified names into their XMLNS
-; "expanded name" form, where IS-ATTRIBUTE? indicates whether the QNAME is
-; the name of an attribute or an element.
-;
-(define (rxi-name/transform-from-xml iqname is-attribute? bindings)
-  (call-with-values
-    (lambda ()
-      (rxi-bindings/resolve bindings (symbol-name iqname) is-attribute?))
-    make-rxi-name))
-
-;
-; An RXI-ATTRIBUTE structure represents a reduced XML infoset attribute
-; information item and consists of a NAME represented as an RXI-NAME
-; instance and a VALUE represented as a string.
-;
-(define-structure
-  (rxi-attribute (conc-name rxi-attribute/))
-  (name '() read-only #t)
-  (value "" read-only #t))
-
-;
-; Convert an RXI-ATTRIBUTE instance ATTRIBUTE to a list consisting of its
-; constituent slots.
-;
-(define (rxi-attribute->list attribute)
-  (list (rxi-name->list (rxi-attribute/name attribute))
-        (rxi-attribute/value attribute)))
-
-;
-; Transform XML-ATTRIBUTE instance ATTRIBUTE to RXI-ATTRIBUTE instance,
-; where BINDINGS is the current bindings stack.
-;
-(define (rxi-attribute/transform-from-xml attribute bindings)
-  (let ((n (car attribute)) (v (cdr attribute)))
-    (make-rxi-attribute (rxi-name/transform-from-xml n #t bindings) v)))
-
-;
-; An RXI-ELEMENT structure represents a reduced XML infoset element
-; information item and consists of a NAME represented as an RXI-NAME
-; instance, a possibly empty set of ATTRIBUTES represented as a list of
-; RXI-ATTRIBUTE instances, and a possibly empty set of CHILDREN represented
-; as a list of string or RXI-ELEMENT instances.
-;
-(define-structure
-  (rxi-element (conc-name rxi-element/))
-  (name "" read-only #t)
-  (attributes '() read-only #f)
-  (children '() read-only #f))
-
-;
-; Convert an RXI-ELEMENT instance ELEMENT to a list consisting of its
-; constituent slots.
-;
-(define (rxi-element->list element)
-  (list (rxi-name->list (rxi-element/name element))
-        (map
-          rxi-attribute->list
-          (rxi-element/attributes element))
-        (map
-          (lambda (c)
-            (if (string? c)
-                c
-                (rxi-element->list c)))
-          (rxi-element/children element))))
-
-;
-; Determine if XML-ATTRIBUTE instance ATTRIBUTE, represented as a pair
-; (NAME . VALUE), is an XMLNS attribute or not, i.e., has a qualified name
-; whose prefix is "xmlns" or is the unqualified name "xmlns".
-;
-(define (namespace-attribute? attribute)
-  (let ((qname (symbol-name (car attribute))))
-    (and (string-prefix? "xmlns" qname)
-         (or (= (string-length qname) 5)
-             (let ((i (string-find-next-char qname #\:)))
-               (and (not (false? i)) (= i 5)))))))
-
-;
-; Given a list ATTRIBUTES of XML-ATTRIBUTE instances consisting only of
-; XMLNS attributes as determined by NAMESPACE-ATTRIBUTE? above, return a set
-; of bindings as an association list whose keys are namespace prefixes and
-; whose values are the associated namespace URIs.
-;
-(define (extract-namespace-bindings attributes)
-  (map
-    (lambda (a)
-      (let ((qname (symbol-name (car a))))
-        (if (= (string-match-forward qname "xmlns") 5)
-            (cons
-             (if (>= (string-length qname) 6)
-                 (string-tail qname 6)
-                 "")
-             (cdr a))
-            (error "Invalid namespace attribute" qname))))
-    attributes))
-
-;
-; Transform XML-ELEMENT instance ELEMENT to RXI-ELEMENT instance,
-; where BINDINGS is the current bindings stack.
-;
-(define (rxi-element/transform-from-xml element bindings)
-  (let* ((attributes
-           (xml-element-attributes element))
-         (ns-attributes
-           (keep-matching-items attributes namespace-attribute?))
-         (other-attributes
-           (keep-matching-items
-             attributes
-             (lambda (a) (not (namespace-attribute? a))))))
-    (rxi-bindings/push! bindings (extract-namespace-bindings ns-attributes))
-    (let ((rxi-element
-            (make-rxi-element
-              (rxi-name/transform-from-xml
-                (xml-element-name element) #f bindings)
-              (map
-                (lambda (a) (rxi-attribute/transform-from-xml a bindings))
-                other-attributes)
-              (map
-                (lambda (c)
-                  (if (string? c)
-                      c
-                      (rxi-element/transform-from-xml c bindings)))
-                (xml-element-contents element)))))
-      (rxi-bindings/pop! bindings)
-      rxi-element)))
-
-;
-; An RXI-DOCUMENT structure represents a reduced XML infoset document
-; information item and consists of an ANNOTATIONS association list, used for
-; internal book-keeping purposes, and an RXI-ELEMENT instance representing
-; the document's root element or '() if there is no root element.
-;
-(define-structure
-  (rxi-document (conc-name rxi-document/))
-  (annotations '() read-only #f)
-  (root '() read-only #f))
-
-;
-; Look up value of annotation named KEY on RXI-DOCUMENT instance DOCUMENT.
-;
-(define (rxi-document/annotation document key)
-  (assq key (rxi-document/annotations document)))
-
-;
-; Add annotation (KEY . VALUE) to RXI-DOCUMENT instance DOCUMENT.
-;
-(define (set-rxi-document/annotation! document key value)
-  (set-rxi-document/annotations! document (cons (cons key value) (rxi-document/annotations document))))
-
-;
-; Remove all annotations named KEY from RXI-DOCUMENT instance DOCUMENT.
-;
-(define (rxi-document/remove-annotation! document key)
-  (del-assq! key (rxi-document/annotations document)))
-
-;
-; Convert an RXI-DOCUMENT instance DOCUMENT to a list consisting of its
-; constituent slots.
-;
-(define (rxi-document->list document)
-  (list (rxi-document/annotations document)
-        (rxi-element->list (rxi-document/root document))))
-
-;
-; Transform XML-DOCUMENT instance DOCUMENT to RXI-DOCUMENT instance.
-;
-(define (rxi-document/transform-from-xml document)
-  (let
-    ((bindings
-      (make-rxi-bindings
-        (list (list (cons (cdr *xml-default-reverse-binding*)
-                          (car *xml-default-reverse-binding*)))))))
-    (make-rxi-document
-      '()
-      (rxi-element/transform-from-xml (xml-document-root document) bindings))))
-
-;
-; Load XML document instance from PATHNAME using XML package's XML parser,
-; then transform resulting XML-DOCUMENT instance to an RXI-DOCUMENT
-; instance.
-;
-(define (rxi-document/load pathname)
-  (rxi-document/transform-from-xml
-    (call-with-input-file pathname
-      (lambda (port)
-        (parse-xml-document (input-port->parser-buffer port))))))
-
-;
-; An RXI-REVERSE-BINDINGS structure consists of a REVERSE-BINDINGS slot
-; that contains an association list whose keys are XMLNS namespace URIs and
-; whose values are XMLNS name prefixes. The URI component of a reverse
-; binding entry MUST be a non-empty string.
-;
-(define-structure
-  (rxi-reverse-bindings
-    (conc-name rxi-reverse-bindings/)
-    (constructor make-rxi-reverse-bindings (#!optional reverse-bindings)))
-  (reverse-bindings '() read-only #f))
-
-(define (rxi-reverse-bindings/lookup reverse-bindings uri)
-  (if (and (string? uri)
-           (not (string-null? uri)))
-      (let find
-          ((rb (rxi-reverse-bindings/reverse-bindings reverse-bindings)))
-        (cond ((null? rb)
-               '())
-              (else
-               (let
-                   ((b (car rb)))
-                 (if (string=? (car b) uri)
-                     (cdr b)
-                     (find (cdr rb)))))))
-      (error "non-string or empty XMLNS namespace URI" uri)))
-
-(define (rxi-reverse-bindings/generate-prefix reverse-bindings)
-  (let ((g (lambda () (string-downcase (symbol-name (generate-uninterned-symbol)))))
-        (rb (rxi-reverse-bindings/reverse-bindings reverse-bindings)))
-    (let loop
-        ((pfx '()))
-      (cond ((null? pfx)
-             (loop (g)))
-            (else
-             (if (not (find-matching-item
-                        rb
-                        (lambda (b)
-                          (and (string? (cdr b)) (string=? (cdr b) pfx)))))
-                 pfx
-                 (loop (g))))))))
-
-(define (rxi-reverse-bindings/add! reverse-bindings uri pfx)
-  (set-rxi-reverse-bindings/reverse-bindings!
-    reverse-bindings
-    (cons (cons uri pfx) (rxi-reverse-bindings/reverse-bindings reverse-bindings))))
-  
-(define (rxi-reverse-bindings/sort! reverse-bindings)
-  (let
-      ((rb (rxi-reverse-bindings/reverse-bindings reverse-bindings)))
-    (set-rxi-reverse-bindings/reverse-bindings!
-      reverse-bindings
-      (sort rb
-            (lambda (x y)
-              (string<? (cdr x) (cdr y)))))))
-
-(define (rxi-reverse-bindings/normalize-preferred preferred-reverse-bindings)
-  (let ((rbt (make-string-hash-table (length preferred-reverse-bindings)))
-        (xrb *xml-default-reverse-binding*))
-    (let loop
-        ((prb preferred-reverse-bindings))
-      (cond ((null? prb)
-             (if (not (hash-table/get rbt (car xrb) #f))
-                 (hash-table/put! rbt (car xrb) (cdr xrb)))
-             (hash-table->alist rbt))
-            (else
-             (let ((b (car prb)))
-               (if (not (pair? b))
-                   (error "preferred reverse binding not a pair" b)
-                   (let ((u (car b))
-                         (p (cdr b)))
-                     (if (not (hash-table/get rbt u #f))
-                         (hash-table/put! rbt u p))
-                     (loop (cdr prb))))))))))
-
-;
-; Transform an RXI-NAME instance NAME to an XML name IQNAME as defined by the
-; XML package as an uninterned symbol, where IS-ATTRIBUTE? indicates whether
-; the IQNAME is the name of an attribute or an element, and where REVERSE-BINDINGS
-; is the current reverse bindings.
-;
-(define (rxi-name/transform-to-xml name is-attribute? reverse-bindings)
-  (let ((uri (rxi-name/namespace name))
-        (loc (rxi-name/local name)))
-    (xml-intern
-      (if (null? uri)
-          loc
-          (let ((pfx (rxi-reverse-bindings/lookup reverse-bindings uri)))
-            (if (string-null? pfx)
-                loc
-                (string-append
-                  pfx
-                  (string-append ":" loc))))))))
-  
-;
-; Transform RXI-ATTRIBUTE instance ATTRIBUTE to XML-ATTRIBUTE instance.
-;
-(define (rxi-attribute/transform-to-xml attribute reverse-bindings)
-  (cons
-    (rxi-name/transform-to-xml (rxi-attribute/name attribute) #t reverse-bindings)
-    (rxi-attribute/value attribute)))
-
-(define (maybe-add-reverse-binding! reverse-bindings name)
-  (let ((uri (rxi-name/namespace name)))
-    (if (not (null? uri))
-        (if (not (rxi-reverse-bindings/lookup reverse-bindings uri))
-            (rxi-reverse-bindings/add! reverse-bindings uri (rxi-reverse-bindings/generate-prefix reverse-bindings))))))
-
-(define (rxi-element/collect-reverse-bindings element reverse-bindings)
-  ;; collect element's binding
-  (maybe-add-reverse-binding! reverse-bindings (rxi-element/name element))
-  ;; collect attribute reverse-bindings
-  (let ((attributes (rxi-element/attributes element)))
-    (for-each
-      (lambda (a)
-        (maybe-add-reverse-binding! reverse-bindings (rxi-attribute/name a)))
-      attributes))
-  ;; collect childrens' reverse bindings
-  (let ((children (rxi-element/children element)))
-    (for-each 
-      (lambda (c)
-        (if (not (string? c))
-            (rxi-element/collect-reverse-bindings c reverse-bindings)))
-      children)))
-
-;
-; Transform RXI-ELEMENT instance ELEMENT to XML-ELEMENT instance.
-;
-(define (rxi-element/transform-to-xml element reverse-bindings)
-  (make-xml-element
-    (rxi-name/transform-to-xml (rxi-element/name element) #f reverse-bindings)
-    (map
-      (lambda (a)
-        (rxi-attribute/transform-to-xml a reverse-bindings))
-      (rxi-element/attributes element))
-    (map
-      (lambda (c)
-        (if (string? c)
-            c
-            (rxi-element/transform-to-xml c reverse-bindings)))
-      (rxi-element/children element))))
-
-;
-; Add XMLNS attributes that correspond with REVERSE-BINDINGS to the root
-; element of XML-DOCUMENT instance DOCUMENT. If DOCUMENT has no root
-; element, then do nothing.
-;
-(define (xml-document-add-bindings! document reverse-bindings)
-  (let ((root (xml-document-root document)))
-    (if (not (null? root))
-        (set-xml-element-attributes!
-          root
-          (append
-            (xml-element-attributes root)
-            (map
-              (lambda (b)
-                (let*
-                    ((prefix (cdr b))
-                     (ns-attr-name
-                       (if (string-null? prefix)
-                           "xmlns"
-                           (string-append "xmlns:" prefix))))
-                  (cons (xml-intern ns-attr-name) (car b))))
-              (rxi-reverse-bindings/reverse-bindings reverse-bindings)))))))
-  
-;
-; Collect 
-;
-(define (rxi-document/collect-reverse-bindings document reverse-bindings)
-  (let ((root (rxi-document/root document)))
-    (if (not (null? root))
-        (rxi-element/collect-reverse-bindings root reverse-bindings))
-    (rxi-reverse-bindings/sort! reverse-bindings)
-    reverse-bindings))
-
-;
-; Transform RXI-DOCUMENT instance DOCUMENT to XML-DOCUMENT instance.
-;
-(define (rxi-document/transform-to-xml document preferred-reverse-bindings)
-  (let
-      ((reverse-bindings
-         (make-rxi-reverse-bindings
-           (rxi-reverse-bindings/normalize-preferred preferred-reverse-bindings))))
-    (rxi-document/collect-reverse-bindings document reverse-bindings)
-    (let
-        ((xml-document
-          (make-xml-document
-           '()                          ; declaration
-           '()                          ; misc-1
-           '()                          ; dtd
-           '()                          ; misc-2
-           (rxi-element/transform-to-xml
-             (rxi-document/root document) reverse-bindings)
-           '())))                       ; misc-3
-      (xml-document-add-bindings! xml-document reverse-bindings)
-      xml-document)))
-
-;
-; Save RXI-DOCUMENT instance DOCUMENT by transforming to an XML-DOCUMENT
-; instance and serializing to PATHNAME using XML package's document serializer,
-; where optional argument PREFERRED-REVERSE-BINDINGS, if specified, consists
-; of an association list whose keys are namespace URIs and values are the
-; preferred namespace prefixes to use to designate those namespaces.
-;
-; If a namepsace URI appears in DOCUMENT and it has no preferred binding
-; specified, then a prefix is generated unless the namespace URI is
-; "http://www.w3.org/XML/1998/namespace", in which case the prefix "xml" is
-; used.
-;
-(define (rxi-document/save document pathname #!optional preferred-reverse-bindings)
-  (let
-      ((xml-document
-         (rxi-document/transform-to-xml
-          document
-          (if (default-object? preferred-reverse-bindings)
-              '()
-              preferred-reverse-bindings))))
-    (call-with-output-file pathname
-      (lambda (port)
-        (write-xml xml-document port)))))
--- a/ttml11/spec/scm/test.xml	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,80 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<tt ttp:profile="http://www.w3.org/ns/ttml#profile-dfxp"
-    xml:lang="en"
-    xmlns="http://www.w3.org/ns/ttml"
-    xmlns:ttp="http://www.w3.org/ns/ttml#parameter"
-    xmlns:ttm="http://www.w3.org/ns/ttml#metadata"
-    xmlns:tts="http://www.w3.org/ns/ttml#style">
-  <head>
-    <metadata>
-      <ttm:title>Timed Text DFXP Example</ttm:title>
-      <ttm:copyright>The Authors (c) 2006</ttm:copyright>
-    </metadata>
-    <styling>
-      <!-- s1 specifies default color, font, and text alignment -->
-      <style xml:id="s1"
-        tts:color="white"
-        tts:fontFamily="proportionalSansSerif"
-        tts:fontSize="22px"
-        tts:textAlign="center"
-      />
-      <!-- alternative using yellow text but otherwise the same as style s1 -->
-      <style xml:id="s2" style="s1" tts:color="yellow"/>
-      <!-- a style based on s1 but justified to the right -->
-      <style xml:id="s1Right" style="s1" tts:textAlign="end" />     
-      <!-- a style based on s2 but justified to the left -->
-      <style xml:id="s2Left" style="s2" tts:textAlign="start" />
-    </styling>
-    <layout>
-      <region xml:id="subtitleArea"
-        style="s1"
-        tts:extent="560px 62px"
-        tts:padding="5px 3px"
-        tts:backgroundColor="black"
-        tts:displayAlign="after"
-      />
-    </layout>  
-  </head>
-  <body region="subtitleArea">
-    <div>
-      <p xml:id="subtitle1" begin="0.76s" end="3.45s">
-        It seems a paradox, does it not,
-      </p>
-      <p xml:id="subtitle2" begin="5.0s" end="10.0s">
-        that the image formed on<br/>
-        the Retina should be inverted?
-      </p>
-      <p xml:id="subtitle3" begin="10.0s" end="16.0s" style="s2">
-        It is puzzling, why is it<br/>
-        we do not see things upside-down?
-      </p>
-      <p xml:id="subtitle4" begin="17.2s" end="23.0s">
-        You have never heard the Theory,<br/>
-        then, that the Brain also is inverted?
-      </p>
-      <p xml:id="subtitle5" begin="23.0s" end="27.0s" style="s2">
-        No indeed! What a beautiful fact!
-      </p>
-      <p xml:id="subtitle6a" begin="28.0s" end="34.6s" style="s2Left">
-        But how is it proved?
-      </p>
-      <p xml:id="subtitle6b" begin="28.0s" end="34.6s" style="s1Right">
-        Thus: what we call
-      </p>
-      <p xml:id="subtitle7" begin="34.6s" end="45.0s" style="s1Right">
-        the vertex of the Brain<br/>
-        is really its base
-      </p>
-      <p xml:id="subtitle8" begin="45.0s" end="52.0s" style="s1Right">
-        and what we call its base<br/>
-        is really its vertex,
-      </p>
-      <p xml:id="subtitle9a" begin="53.5s" end="58.7s">
-        it is simply a question of nomenclature.
-      </p>
-      <p xml:id="subtitle9b" begin="53.5s" end="58.7s" style="s2">
-        How truly delightful!
-      </p>
-    </div>    
-  </body>
-</tt>
--- a/ttml11/spec/scm/tir.scm	Tue Jul 09 11:28:27 2013 -0600
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,12 +0,0 @@
-;;; -*-Scheme-*-
-;;; Package: (dfxp rxi adi tir)
-
-;;;; DFXP Timing Interval Resolver
-
-(declare (usual-integrations))
-
-;
-; NOT YET IMPLEMENTED - TO BE PROVIDED PRIOR TO PROPOSED RECOMMENDATION PHASE
-;
-
-(define (adi-document/tir-transform document) document)
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml11/spec/ttml-changes.html	Tue Jul 09 14:39:28 2013 -0600
@@ -0,0 +1,48 @@
+<?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.1 - List of changes</title>
+<style type="text/css">
+div.exampleInner pre { margin-left: 1em;
+                       margin-top: 0em; margin-bottom: 0em}
+div.exampleInner { background-color: #d5dee3;
+                   border-top-width: 4px;
+                   border-top-style: double;
+                   border-top-color: #d3d3d3;
+                   border-bottom-width: 4px;
+                   border-bottom-style: double;
+                   border-bottom-color: #d3d3d3;
+                   padding: 4px; margin: 0em }
+.strong { font-weight: bold; }
+</style>
+<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/>
+</head>
+<body>
+<h1>Timed Text Markup Language (TTML) 1.1 Change Summary</h1>
+<p>1 <a href="#change-history">Change History</a> (Non-Normative)<br/>
+    1.1 <a href="#change-history-ttml10-rec-2e-to-ttml11-fpwd">Draft Changes from Proposed Edited Recommendation (2nd Ed.) to Recommendation (2nd Ed.)</a><br/>
+</p>
+<div class="div1">
+<h2><a id="change-history"/>1 Change History (Non-Normative)</h2>
+<p>Changes are ordered from most recent to least recent.</p>
+
+<div class="div2">
+<h3><a id="change-history-ttml10-rec-2e-to-ttml11-fpwd"/>1.1 Draft Changes from TTML1.0 (2nd Ed.) to TTML1.1 First Public Working Draft</h3>
+<div class="exampleInner">
+<span class="strong">Technical Changes</span>
+
+* 
+
+</pre>
+<pre>
+<span class="strong">Editorial Changes</span>
+
+* 
+
+</pre>
+</div>
+</div>
+</div>
+</body>
+</html>
--- a/ttml11/spec/ttml-issues.html	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/ttml-issues.html	Tue Jul 09 14:39:28 2013 -0600
@@ -4,212 +4,7 @@
 <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/>
 </head>
 <body>
-<h1>Timed Text Markup Language (TTML) 1.0: Issues</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" name="media-type-registration">C Media Type Registration</a></h2><p><a id="media-type-registration" name="media-type-registration"><em>This appendix is normative.</em></a></p><p><a id="media-type-registration" name="media-type-registration">This appendix registers a new MIME media type,
-"application/ttml+xml" in conformance with
-</a><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 (public-tt@w3.org)</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:
-<pre>
-&lt;xs:anyAttribute namespace="##other"/>
-</pre>
-
+<h1>Timed Text Markup Language (TTML) 1.1: Errata</h1>
+<p>None</p>
 </body>
 </html>
--- a/ttml11/spec/ttml11.xml	Tue Jul 09 11:28:27 2013 -0600
+++ b/ttml11/spec/ttml11.xml	Tue Jul 09 14:39:28 2013 -0600
@@ -1,12974 +1,13566 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Id$ -->
-<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.10//EN" "xmlspec-ttml11.dtd" [
-<!ENTITY % entities SYSTEM "entities.dtd" >
-%entities;
-<!ENTITY status SYSTEM "status.xml">
-<!ENTITY document.status "Editors' copy $Date$">
-<!ENTITY title "&title;">
-<!ENTITY prevloc "http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">
-<!ENTITY versionOfTT "1.0">
-<!ENTITY tbd "<phrase role='tbd'>To Be Defined</phrase>">
-<!ENTITY sp "&#x0020;">
-<!ENTITY sect "&#x00a7;">
-<!ENTITY aring "&#x00e5;">
-<!ENTITY ccedil "&#x00e7;">
-<!ENTITY Ccedil "&#x00c7;">
-<!ENTITY mult "&#x00d7;">
-<!ENTITY uuml "&#x00fc;">
-<!ENTITY nbsp "&#x00a0;">
-<!ENTITY ndash "&#x2013;">
-<!ENTITY mdash "&#x2014;">
-<!ENTITY prime "&#x2032;">
-<!ENTITY hArr "&#x21d4;">
-<!ENTITY trade "&#x2122;">
-<!ENTITY hellip "&#x2026;">
-<!ENTITY isin "&#x2208;">
-<!ENTITY minus "&#x2212;">
-<!ENTITY le "&#x2264;">
-<!ENTITY ge "&#x2265;">
-<!ENTITY plusmn "&#x00B1;">
-<!ENTITY dfxp-ex1 SYSTEM "./examples/ex1.xml.esc">
-<!ENTITY dfxp-ex1-x-0 SYSTEM "./examples/ex1-x-0.xml.esc">
-<!ENTITY dfxp-ex1-p-0 SYSTEM "./examples/ex1-p-0.xml.esc">
-<!ENTITY dfxp-ex1-x-1 SYSTEM "./examples/ex1-x-1.xml.esc">
-<!ENTITY dfxp-ex1-x-2 SYSTEM "./examples/ex1-x-2.xml.esc">
-<!ENTITY rnc-dfxp-driver SYSTEM "./rnc/ttml11.rnc.esc">
-<!ENTITY rnc-dfxp-animation-module SYSTEM "./rnc/ttml11-animation.rnc.esc">
-<!ENTITY rnc-dfxp-classes-module SYSTEM "./rnc/ttml11-classes.rnc.esc">
-<!ENTITY rnc-dfxp-content-module SYSTEM "./rnc/ttml11-content.rnc.esc">
-<!ENTITY rnc-dfxp-core-attribs-module SYSTEM "./rnc/ttml11-core-attribs.rnc.esc">
-<!ENTITY rnc-dfxp-datatypes-module SYSTEM "./rnc/ttml11-datatypes.rnc.esc">
-<!ENTITY rnc-dfxp-document-module SYSTEM "./rnc/ttml11-document.rnc.esc">
-<!ENTITY rnc-dfxp-head-module SYSTEM "./rnc/ttml11-head.rnc.esc">
-<!ENTITY rnc-dfxp-metadata-module SYSTEM "./rnc/ttml11-metadata.rnc.esc">
-<!ENTITY rnc-dfxp-metadata-items-module SYSTEM "./rnc/ttml11-metadata-items.rnc.esc">
-<!ENTITY rnc-dfxp-metadata-attribs-module SYSTEM "./rnc/ttml11-metadata-attribs.rnc.esc">
-<!ENTITY rnc-dfxp-parameters-module SYSTEM "./rnc/ttml11-parameters.rnc.esc">
-<!ENTITY rnc-dfxp-parameter-items-module SYSTEM "./rnc/ttml11-parameter-items.rnc.esc">
-<!ENTITY rnc-dfxp-parameter-attribs-module SYSTEM "./rnc/ttml11-parameter-attribs.rnc.esc">
-<!ENTITY rnc-dfxp-styling-attribs-module SYSTEM "./rnc/ttml11-styling-attribs.rnc.esc">
-<!ENTITY rnc-dfxp-styling-module SYSTEM "./rnc/ttml11-styling.rnc.esc">
-<!ENTITY rnc-dfxp-layout-module SYSTEM "./rnc/ttml11-layout.rnc.esc">
-<!ENTITY rnc-dfxp-timing-attribs-module SYSTEM "./rnc/ttml11-timing-attribs.rnc.esc">
-<!ENTITY xsd-dfxp-driver SYSTEM "./xsd/ttml11.xsd.esc">
-<!ENTITY xsd-dfxp-animation-module SYSTEM "./xsd/ttml11-animation.xsd.esc">
-<!ENTITY xsd-dfxp-content-module SYSTEM "./xsd/ttml11-content.xsd.esc">
-<!ENTITY xsd-dfxp-core-attribs-module SYSTEM "./xsd/ttml11-core-attribs.xsd.esc">
-<!ENTITY xsd-dfxp-datatypes-module SYSTEM "./xsd/ttml11-datatypes.xsd.esc">
-<!ENTITY xsd-dfxp-document-module SYSTEM "./xsd/ttml11-document.xsd.esc">
-<!ENTITY xsd-dfxp-head-module SYSTEM "./xsd/ttml11-head.xsd.esc">
-<!ENTITY xsd-dfxp-metadata-module SYSTEM "./xsd/ttml11-metadata.xsd.esc">
-<!ENTITY xsd-dfxp-metadata-items-module SYSTEM "./xsd/ttml11-metadata-items.xsd.esc">
-<!ENTITY xsd-dfxp-metadata-attribs-module SYSTEM "./xsd/ttml11-metadata-attribs.xsd.esc">
-<!ENTITY xsd-dfxp-parameters-module SYSTEM "./xsd/ttml11-parameters.xsd.esc">
-<!ENTITY xsd-dfxp-parameter-items-module SYSTEM "./xsd/ttml11-parameter-items.xsd.esc">
-<!ENTITY xsd-dfxp-parameter-attribs-module SYSTEM "./xsd/ttml11-parameter-attribs.xsd.esc">
-<!ENTITY xsd-dfxp-styling-attribs-module SYSTEM "./xsd/ttml11-styling-attribs.xsd.esc">
-<!ENTITY xsd-dfxp-styling-module SYSTEM "./xsd/ttml11-styling.xsd.esc">
-<!ENTITY xsd-dfxp-layout-module SYSTEM "./xsd/ttml11-layout.xsd.esc">
-<!ENTITY xsd-dfxp-timing-attribs-module SYSTEM "./xsd/ttml11-timing-attribs.xsd.esc">
-<!ENTITY xsd-dfxp-xml-attrs-module SYSTEM "./xsd/xml.xsd.esc">
-<!ENTITY profile-dfxp-presentation SYSTEM "./profiles/dfxp-presentation.xml.esc">
-<!ENTITY profile-dfxp-transformation SYSTEM "./profiles/dfxp-transformation.xml.esc">
-<!ENTITY profile-dfxp-full SYSTEM "./profiles/dfxp-full.xml.esc">
-]>
-<?xml-stylesheet type='text/xsl' href='xmlspec-ttml11.xsl'?>
-<spec w3c-doctype="&doctype;" role="&document.role;">
-<header>
-<title>&title;</title>
-<w3c-designation>&w3c-designation;</w3c-designation>
-<w3c-doctype>&document.status;</w3c-doctype>
-<pubdate>
-<day>&draft.day;</day>
-<month>&draft.month;</month>
-<year>&draft.year;</year>
-</pubdate>
-<publoc>
-<loc href="&w3c-designation;">&w3c-designation;</loc>
-</publoc>
-<prevlocs>
-<loc href="&prevloc;">&prevloc;</loc>
-</prevlocs>
-<latestloc>
-<loc href="&latest;">&latest;</loc>
-</latestloc>
-<authlist id="editors" role="editor">
-<author>
-<name>Glenn Adams</name>
-<affiliation>Cox Communications, Inc.</affiliation>
-</author>
-</authlist>
-<authlist id="contributors" role="contributor">
-<author>
-<name>Mike Dolan</name>
-<affiliation>Invited Expert</affiliation>
-</author>
-<author>
-<name>Geoff Freed</name>
-<affiliation>WGBH National Center for Accessible Media</affiliation>
-</author>
-<author>
-<name>Sean Hayes</name>
-<affiliation>Microsoft</affiliation>
-</author>
-<author>
-<name>Erik Hodge</name>
-<affiliation>RealNetworks</affiliation>
-</author>
-<author>
-<name>David Kirby</name>
-<affiliation>British Broadcasting Corporation (BBC)</affiliation>
-</author>
-<author>
-<name>Thierry Michel</name>
-<affiliation>W3C</affiliation>
-</author>
-<author>
-<name>Dave Singer</name>
-<affiliation>Apple Computer</affiliation>
-</author>
-</authlist>
-<abstract id="abstract">
-<p>This document specifies the Timed Text Markup Language (TTML) 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
-systems. Timed text is textual information that is intrinsically or
-extrinsically associated with timing information.</p>
-<p>It is intended to be used
-for the purpose of transcoding or exchanging timed text information
-among legacy distribution content formats presently in use for
-subtitling and captioning functions.</p>
-<p>In addition to being used for interchange among legacy distribution content
-formats, TTML content may be used directly as a distribution format,
-for example, providing a standard content format to reference from a <el>&lt;text&gt;</el> or 
-<el>&lt;textstream&gt;</el> media object element in a <bibref
-ref="smil21"/> document.</p>
-</abstract>
-&status;
-<langusage><language id='en-us'>English</language></langusage>
-<revisiondesc><p>Last Modified: $Date$</p></revisiondesc>
-</header>
-<body>
-<div1 id="intro">
-<head>Introduction</head>
-<p><emph>Unless specified otherwise, this section and its sub-sections are non-normative.</emph></p>
-<p>The Timed Text Markup Language (TTML) 1.0
-provides a standardized representation of a particular subset of
-textual information with which stylistic, layout, and timing semantics are associated by
-an author or an authoring system for the purpose of interchange and potential presentation.</p>
-<p>TTML is expressly designed to meet only a limited set of requirements
-established by <bibref ref="ttaf1-req"/>, and summarized in <specref
-ref="requirements"/>. In particular, only those requirements which service the
-need of performing interchange with existing, legacy distribution systems are
-satisfied.</p>
-<p>In addition to being used for interchange among legacy distribution content
-formats, TTML content may be used directly as a distribution format, providing, for
-example, a standard content format to reference from a <el>&lt;text&gt;</el> or 
-<el>&lt;textstream&gt;</el> media object element in a <bibref
-ref="smil21"/> document. Certain properties of TTML support
-streamability of content, as described in <specref ref="streaming"/>.</p>
-<note>
-<p>While TTML was not expressly designed for direct (embedded) integration into a
-SMIL document instance, such integration is not precluded.</p>
-</note>
-<note>
-<p>In some contexts of use, it may be appropriate to employ
-animated content to depict sign language representations of the same content
-as expressed by a Timed Text document instance. This use case is not
-explicitly addressed by TTML mechanisms, but may be addressed by some
-external multimedia integration technology, such as SMIL.</p>
-</note>
-<div2 id="model">
-<head>System Model</head>
-<p>Use of TTML is intended to function in a wider context of Timed Text
-Authoring and Distribution mechanisms that are based upon a system
-model, depicted in <specref ref="model-graphic"/>, wherein the Timed Text Markup Language
-serves as a bidirectional interchange format among a heterogeneous collection of
-authoring systems, and as a unidirectional interchange format to a
-heterogeneous collection of distribution formats after undergoing transcoding
-or compilation to the target distribution formats as required, and where one
-particular distribution format is TTML.</p>
-<table id="model-graphic" role="example-images">
-<caption>Figure 1 &ndash; System Model</caption>
-<tbody>
-<tr>
-<td><graphic id="graphic-model" source="images/model.png" alt="System Model"/></td>
-</tr>
-</tbody>
-</table>
-</div2>
-<div2 id="example">
-<head>Document Example</head>
-<p>A TTML document instance consists of a <el>tt</el> document element that contains
-a header and a body, where the header specifies document level metadata, styling
-definitions and layout definitions, and the body specifies text content intermixed
-with references to style and layout information and inline timing information.</p>
-<table id="dfxp-example-document-structure" role="example">
-<caption>Example Fragment &ndash; TTML Document Structure</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"&gt;
-  &lt;head&gt;
-    &lt;metadata/&gt;
-    &lt;styling/&gt;
-    &lt;layout/&gt;
-  &lt;/head&gt;
-  &lt;body/&gt;
-&lt;/tt&gt;
-</eg>
-</td></tr>
-</tbody>
-</table>
-<p>Document level metadata may specify a document title, description,
-and copyright information. In addition, arbitrary metadata drawn from
-other namespaces may be specified.</p>
-<table id="dfxp-example-metadata" role="example">
-<caption>Example Fragment &ndash; TTML Metadata</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;metadata xmlns:ttm="http://www.w3.org/ns/ttml#metadata"&gt;
-  &lt;ttm:title&gt;Timed Text TTML Example&lt;/ttm:title&gt;
-  &lt;ttm:copyright&gt;The Authors (c) 2006&lt;/ttm:copyright&gt;
-&lt;/metadata&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>Styling information may be specified in the form of style specification
-definitions that are referenced by layout and content information.</p>
-<p>In <specref ref="dfxp-example-styling"/>, four style sets of specifications
-are defined, with one set serving as a collection of default styles.</p>
-<table id="dfxp-example-styling" role="example">
-<caption>Example Fragment &ndash; TTML Styling</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;styling xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
-  &lt;!-- s1 specifies default color, font, and text alignment --&gt;
-  &lt;style xml:id="s1"
-    tts:color="white"
-    tts:fontFamily="proportionalSansSerif"
-    tts:fontSize="22px"
-    tts:textAlign="center"
-  /&gt;
-  &lt;!-- alternative using yellow text but otherwise the same as style s1 --&gt;
-  &lt;style xml:id="s2" style="s1" tts:color="yellow"/&gt;
-  &lt;!-- a style based on s1 but justified to the right --&gt;
-  &lt;style xml:id="s1Right" style="s1" tts:textAlign="end" /&gt;     
-  &lt;!-- a style based on s2 but justified to the left --&gt;
-  &lt;style xml:id="s2Left" style="s2" tts:textAlign="start" /&gt;
-&lt;/styling&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>Layout information defines one or more regions into which content
-is intended to be presented. A region definition may reference one or
-more sets of style specifications in order to permit content flowed in the
-region to inherit from these styles.
-In <specref ref="dfxp-example-layout"/>, the region definition makes
-reference to style specification <code>s1</code> which allows all content
-flowed into the region to inherit from the region's styles (in the case
-that a style is not already explicitly specified on content or inherited
-via the content hierarchy.)</p>
-<table id="dfxp-example-layout" role="example">
-<caption>Example Fragment &ndash; TTML Layout</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;layout xmlns:tts="http://www.w3.org/ns/ttml#styling"&gt;
-  &lt;region xml:id="subtitleArea"
-    style="s1"
-    tts:extent="560px 62px"
-    tts:padding="5px 3px"
-    tts:backgroundColor="black"
-    tts:displayAlign="after"
-  /&gt;
-&lt;/layout&gt;  
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>The content of a TTML document instance is expressed in its
-body, which is organized in terms of block and inline text elements.
-The hierarchical organization of content elements serves a primary role in
-determining both spatial and temporal relationships. For example, in
-<specref ref="dfxp-example-body"/>, each paragraph (<el>p</el> element)
-is flowed into its target region in the specified lexical order; furthermore,
-the active time interval of each paragraph is timed in accordance to its
-parent or sibling according to the applicable time containment semantics &mdash;
-in this case, the division parent is interpreted as a parallel time
-container.</p>
-<table id="dfxp-example-body" role="example">
-<caption>Example Fragment &ndash; TTML Body</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;body region="subtitleArea"&gt;
-  &lt;div&gt;
-    &lt;p xml:id="subtitle1" begin="0.76s" end="3.45s"&gt;
-      It seems a paradox, does it not,
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle2" begin="5.0s" end="10.0s"&gt;
-      that the image formed on&lt;br/&gt;
-      the Retina should be inverted?
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle3" begin="10.0s" end="16.0s" style="s2"&gt;
-      It is puzzling, why is it&lt;br/&gt;
-      we do not see things upside-down?
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle4" begin="17.2s" end="23.0s"&gt;
-      You have never heard the Theory,&lt;br/&gt;
-      then, that the Brain also is inverted?
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle5" begin="23.0s" end="27.0s" style="s2"&gt;
-      No indeed! What a beautiful fact!
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle6a" begin="28.0s" end="34.6s" style="s2Left"&gt;
-      But how is it proved?
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle6b" begin="28.0s" end="34.6s" style="s1Right"&gt;
-      Thus: what we call
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle7" begin="34.6s" end="45.0s" style="s1Right"&gt;
-      the vertex of the Brain&lt;br/&gt;
-      is really its base
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle8" begin="45.0s" end="52.0s" style="s1Right"&gt;
-      and what we call its base&lt;br/&gt;
-      is really its vertex,
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle9a" begin="53.5s" end="58.7s"&gt;
-      it is simply a question of nomenclature.
-    &lt;/p&gt;
-    &lt;p xml:id="subtitle9b" begin="53.5s" end="58.7s" style="s2"&gt;
-      How truly delightful!
-    &lt;/p&gt;
-  &lt;/div&gt;    
-&lt;/body&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>The first subtitle <specref ref="dfxp-example-subtitle-1"/> is
-presented during the time interval 0.76 to 3.45 seconds.
-This
-subtitle inherits its font family, font size,
-foreground color, and text alignment from the region into which it is
-presented. Since no region is explicitly specified on the paragraph,
-the nearest ancestor that specifies a region determines the
-region. Note also that content is presented
-at the bottom (after edge) of the containing region due to the <code>tts:displayAlign="after"</code>
-being specified on the region definition.</p>
-<note role="explanation">
-<p>The notation "[<emph>X</emph>,<emph>Y</emph>]" denotes a closed
-interval from <emph>X</emph> to <emph>Y</emph>, including
-<emph>X</emph> and <emph>Y</emph>;
-"[<emph>X</emph>,<emph>Y</emph>)" denotes a right half-open
-interval from <emph>X</emph> to <emph>Y</emph>, including
-<emph>X</emph> but not including <emph>Y</emph>;
-"(<emph>X</emph>,<emph>Y</emph>]" denotes a left half-open
-interval from <emph>X</emph> to <emph>Y</emph>, not including
-<emph>X</emph> but including <emph>Y</emph>;
-"(<emph>X</emph>,<emph>Y</emph>)" denotes an open
-interval from <emph>X</emph> to <emph>Y</emph>, not including
-<emph>X</emph> or <emph>Y</emph>.
-</p>
-</note>
-<table id="dfxp-example-subtitle-1" role="example-images">
-<caption>Subtitle 1 &ndash; Time Interval [0.76, 3.45)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle1.png" alt="Subtitle 1"/></td>
-</tr>
-</tbody>
-</table>
-<p>The second subtitle continues with the default style, except that it contains
-two lines of text with an intervening author-specified line break. Note the effects of
-the use of <code>tts:textAlign="center"</code> to specify the paragraph's alignment
-in the inline progression direction.</p>
-<table id="dfxp-example-subtitle-2" role="example-images">
-<caption>Subtitle 2 &ndash; Time Interval [5.0, 10.0)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle2.png" alt="Subtitle 2"/></td>
-</tr>
-</tbody>
-</table>
-<p>The third subtitle continues, using a variant style which overrides the default style's
-foreground color with a different color.</p>
-<table id="dfxp-example-subtitle-3" role="example-images">
-<caption>Subtitle 3 &ndash; Time Interval [10.0, 16.0)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle3.png" alt="Subtitle 3"/></td>
-</tr>
-</tbody>
-</table>
-<p>The fourth subtitle reverts to the default style.</p>
-<table id="dfxp-example-subtitle-4" role="example-images">
-<caption>Subtitle 4 &ndash; Time Interval [17.2, 23.0)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle4.png" alt="Subtitle 4"/></td>
-</tr>
-</tbody>
-</table>
-<p>The fifth subtitle continues, again using a variant style which
-overrides the default style's foreground color with a different color.</p>
-<table id="dfxp-example-subtitle-5" role="example-images">
-<caption>Subtitle 5 &ndash; Time Interval [23.0, 27.0)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle5.png" alt="Subtitle 5"/></td>
-</tr>
-</tbody>
-</table>
-<p>During the next active time interval, two distinct subtitles are simultaneously active, with
-the paragraph expressing each subtitle using a different style that overrides color and paragraph
-text alignment of the default style. Note that the flow order is determined by the lexical
-order of elements as they appear in the content hierarchy.</p>
-<table id="dfxp-example-subtitle-6" role="example-images">
-<caption>Subtitles 6a and 6b &ndash; Time Interval [28.0, 34.6)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle6.png" alt="Subtitles 6a and 6b"/></td>
-</tr>
-</tbody>
-</table>
-<p>The next subtitle is specified in a similar manner using
-a style override to give a paragraph right (end) justified in the
-inline progression direction.</p>
-<table id="dfxp-example-subtitle-7" role="example-images">
-<caption>Subtitle 7 &ndash; Time Interval [34.6, 45.0)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle7.png" alt="Subtitles 7a and 7b"/></td>
-</tr>
-</tbody>
-</table>
-<p>The eighth subtitle uses the same style override as the previous
-subtitle in order to maintain the right (end) justification of the
-paragraph.</p>
-<table id="dfxp-example-subtitle-8" role="example-images">
-<caption>Subtitle 8 &ndash; Time Interval [47.3, 49.0)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle8.png" alt="Subtitle 8"/></td>
-</tr>
-</tbody>
-</table>
-<p>During the final (ninth) active time interval, two distinct
-subtitles are again simultaneously active, but with a different
-style applied to the second paragraph to override the default color.
-Note that the flow order is determined by the lexical order of
-elements as they appear in the content hierarchy.</p>
-<table id="dfxp-example-subtitle-9" role="example-images">
-<caption>Subtitles 9a and 9b &ndash; Time Interval [53.5, 58.7)</caption>
-<tbody>
-<tr>
-<td><graphic source="images/subtitle9.png" alt="Subtitles 9a and 9b"/></td>
-</tr>
-</tbody>
-</table>
-<p>The examples shown above demonstrate the primary types of information that may
-be authored using TTML: metadata, styling, layout, timing, and content. In typical cases,
-styling and layout information are separately specified in a document instance. Content information
-is expressed in a hierarchical fashion that embodies the organization of both spatial (flow) and
-timing information. Content makes direct or indirect references to styling and layout information
-and may specify inline overrides to styling.</p>
-</div2>
-</div1>
-<div1 id="definitions">
-<head>Definitions</head>
-<div2 id="acronyms">
-<head>Acronyms</head>
-<glist role="acronyms">
-<gitem>
-<label>DFXP</label>
-<def>
-<p>Distribution Format Exchange Profile</p>
-</def>
-</gitem>
-<gitem>
-<label>TT</label>
-<def>
-<p>Timed Text</p>
-</def>
-</gitem>
-  <gitem>
-    <label>TTML</label>
-    <def>
-      <p>Timed Text Markup Language</p>
-    </def>
-  </gitem>
-  <gitem>
-<label>TT AS</label>
-<def>
-<p>Timed Text Authoring System</p>
-</def>
-</gitem>
-<gitem>
-<label>TT AF</label>
-<def>
-<p>Timed Text Authoring Format</p>
-</def>
-</gitem>
-<gitem>
-<label>TT WG</label>
-<def>
-<p>Timed Text Working Group</p>
-</def>
-</gitem>
-</glist>
-</div2>
-<div2 id="terms">
-<head>Terminology</head>
-<glist>
-<gitem>
-<label>Abstract Document Instance</label>
-<def>
-<p>An instance of an abstract data set as represented by a
-<emph>Reduced XML Infoset</emph>.</p>
-</def>
-</gitem>
-<gitem>
-<label>Abstract Document Type</label>
-<def>
-<p>A set of constraints that defines a class of <emph>XML Information
-Set</emph>s <bibref ref="infoset"/>.</p>
-</def>
-</gitem>
-<gitem>
-<label>Attribute Information Item</label>
-<def>
-<p>Each specified or defaulted attribute  of an XML document corresponds with an attribute information
-item as defined by <bibref ref="infoset"/>, &sect;2.3.</p>
-</def>
-</gitem>
-<gitem>
-<label>Character Information Item</label>
-<def>
-<p>Each data character appearing in an XML document corresponds with a character information
-item as defined by <bibref ref="infoset"/>, &sect;2.6.</p>
-</def>
-</gitem>
-<gitem>
-<label>Content Processor</label>
-<def>
-<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>
-</def>
-</gitem>
-<gitem>
-<label>Content Profile</label>
-<def>
-<p>A collection of features and extensions that are (or may be) employed by
-Timed Text Markup Language content.</p>
-</def>
-</gitem>
-<gitem>
-<label>Content Region</label>
-<def>
-<p>A logical region into which rendered content is placed when modeling or
-performing presentation processing.</p>
-</def>
-</gitem>
-<gitem>
-<label>Element Information Item</label>
-<def>
-<p>Each element appearing in an XML document corresponds with an element information
-item as defined by <bibref ref="infoset"/>, &sect;2.2.</p>
-</def>
-</gitem>
-<gitem>
-<label>Exchange Profile</label>
-<def>
-<p>A content profile that serves a set of needs
-for content interchange.</p>
-</def>
-</gitem>
-<gitem>
-<label>Extension</label>
-<def>
-<p>A syntactic or semantic expression or capability that is defined and
-labeled (using a extension designation) in another (public or private)
-specification.</p>
-</def>
-</gitem>
-<gitem>
-<label>Feature</label>
-<def>
-<p>A syntactic or semantic expression or capability that is defined and
-labeled (using a feature designation) in this specification (or a
-future revision of this specification).</p>
-</def>
-</gitem>
-<gitem>
-<label>Processor</label>
-<def>
-<p>See <emph>Content Processor</emph>.</p>
-</def>
-</gitem>
-<gitem>
-<label>Processor Profile</label>
-<def>
-<p>A collection of features and extensions that must or may be implemented (supported) by
-a content processor.</p>
-</def>
-</gitem>
-<gitem>
-<label>Profile Definition Document</label>
-<def>
-<p>A document that defines a specific collection of features and extensions
-for which support is required or optional in a recipient content
-processor.</p>
-</def>
-</gitem>
-<gitem>
-<label>Region</label>
-<def>
-<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>
-</def>
-</gitem>
-<gitem>
-<label>Reduced XML Infoset</label>
-<def>
-<p>An XML Information Set <bibref ref="infoset"/> that satisfieds the
-constraints specify by <specref ref="reduced-infoset"/>.</p>
-</def>
-</gitem>
-<gitem>
-<label>Root Container Region</label>
-<def>
-<p>A logical region that establishes a coordinate system into which
-content regions are placed and optionally clipped.</p>
-</def>
-</gitem>
-<gitem>
-<label>Timed Text</label>
-<def>
-<p>Textual information that is intrinsically or extrinsically
-associated with timing information.</p>
-</def>
-</gitem>
-<gitem>
-<label>Timed Text Markup Language</label>
-<def>
-<p>A content type that represents timed text media for the purpose of
-interchange among authoring systems.</p>
-</def>
-</gitem>
-<gitem>
-<label>Timed Text Authoring System</label>
-<def>
-<p>A content authoring system capable of importing and exporting
-Timed Text Markup Language content.</p>
-</def>
-</gitem>
-</glist>
-</div2>
-<div2 id="conventions">
-<head>Documentation Conventions</head>
-<p>Within normative prose in this specification, the words
-<emph>may</emph>, <emph>should</emph>, and <emph>must</emph> are
-defined as follows:</p>
-<glist role="conformance-keywords">
-<gitem>
-<label>may</label>
-<def>
-<p>Conforming documents and/or TTML processors are permitted to,
-but need not behave as described. </p>
-</def>
-</gitem>
-<gitem>
-<label>should</label>
-<def>
-<p>Conforming documents and/or TTML processors are strongly
-recommended to, but need not behave as described.</p>
-</def>
-</gitem>
-<gitem>
-<label>must</label>
-<def>
-<p>Conforming documents and/or TTML processors are required
-to behave as described; otherwise, they are in error. </p>
-</def>
-</gitem>
-</glist>
-<p>All normative syntactic definitions of XML representations and
-other related terms are depicted with a light orange background color
-and labeled as "XML Representation" or "Syntax Representation", such
-as in the following:</p>
-<table id="elt-syntax-example" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: example</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;example
-  <phrase role="reqattr">count</phrase> = integer
-  size = (<emph>large</emph>|<emph>medium</emph>|<emph>small</emph>) : medium&gt;
-  <emph>Content:</emph> (all | any*)
-&lt;/example&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>In an XML representation, bold-face attribute names (e.g. <phrase
-role="strong">count</phrase> above) indicate a required attribute
-information item, and the rest are optional. Where an attribute
-information item has an enumerated type definition, the values are
-shown separated by vertical bars, as for <code>size</code> above; if
-there is a default value, it is shown following a colon. Where an
-attribute information item has a built-in simple type definition
-defined in <bibref ref="xsd-2"/>, a hyperlink to its definition
-therein is given.</p>
-<p>The allowed content of the information item is shown as a grammar
-fragment, using the Kleene operators <code>?</code>, <code>*</code>
-and <code>+</code>. Each element name therein is a hyperlink to its
-own illustration.</p>
-<p>All content of this specification that is not explicitly marked as
-non-normative is considered to be normative. If a section or appendix
-header contains the expression "Non-Normative", then the entirety
-of the section or appendix is considered non-normative.</p>
-<p>All paragraphs marked as a <phrase role="strong">Note</phrase> are considered non-normative.</p>
-<p>Example code fragments are depicted with a light blue-green
-background color and labeled as "Example Fragment", such as in
-the following:</p>
-<table id="example-fragment-1" role="example">
-<caption>Example Fragment &ndash; Sample</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"&gt;
-  &lt;head&gt;
-    &lt;metadata/&gt;
-    &lt;styling/&gt;
-    &lt;layout/&gt;
-  &lt;/head&gt;
-  &lt;body/&gt;
-&lt;/tt&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-</div2>
-</div1>
-<div1 id="conformance">
-<head>Conformance</head>
-<p>This section specifies the general conformance requirements for
-TTML content and processors.</p>
-<div2 id="conformance-content">
-<head>Content Conformance</head>
-<p>A TTML document instance conforms to this specification if the following criteria are
-satisfied:</p>
-<olist>
-<item>
-<p>When transporting a document instance in a context in which a MIME
-Media Type <bibref ref="mime-media"/> identifies the content type of the interchanged document
-instance, then the specified media type is
-<code>application/ttml+xml</code> in conformance with <bibref
-ref="rfc3023"/> &sect; 7, with which an optional
-<code>profile</code> parameter may appear, the value of which
-conforms to
-a profile designator as
-defined by
-<specref ref="vocabulary-profiles"/>.</p>
-</item>
-<item>
-<p>The document instance is or can be represented as a Reduced XML
-Infoset as defined by <specref ref="reduced-infoset"/>.</p>
-</item>
-<item>
-<p>The Reduced XML
-Infoset that corresponds to the document instance is or can
-be associated with one of the TTML Abstract
-Document Types defined by
-<specref ref="doctypes"/>.</p>
-</item>
-<item>
-<p>The Reduced XML Infoset that corresponds to the document instance is a
-Valid Abstract Document Instance of the associated
-Abstract Document Type.</p>
-</item>
-<item>
-<p>The Reduced XML Infoset satisfies all additional mandatory syntactic and
-semantic constraints defined by this specification. In addition, this Infoset
-should satisfy the web content accessibility guidelines specified by
-<bibref ref="wcag"/>.</p>
-</item>
-</olist>
-</div2>
-<div2 id="conformance-processor">
-<head>Processor Conformance</head>
-<div3 id="conformance-generic-processor">
-<head>Generic Processor Conformance</head>
-<p>A TTML processor conforms to this specification if the following
-generic processor criteria are
-satisfied:</p>
-<olist>
-<item>
-<p>The processor provides at least one mechanism for notionally
-instantiating a Reduced XML
-Infoset representation of a conformant TTML document
-instance.</p>
-</item>
-<item>
-<p>If a process does or can perform validation of a candidate TTML
-document instance, then it provides at least one mechanism to
-implicitly or explicitly associate the
-Reduced XML Infoset representation
-of a conformant TTML document instance with one of the
-TTML Abstract Document Types defined by
-<specref ref="doctypes"/>.</p>
-</item>
-<item>
-<p>The processor does not <emph>a priori</emph> reject or abort the
-processing of a conformant TTML document instance
-unless the processor does not support some required
-(mandatory) feature specified or implied by a TTML content profile
-declared to apply to the document instance.</p>
-</item>
-<item>
-<p>The processor supports all mandatory processing semantics defined by this specification.</p>
-</item>
-<item>
-<p>If the processor supports some optional processing semantics defined by this specification,
-then it does so in a manner consistent with the defined semantics.</p>
-</item>
-</olist>
-</div3>
-<div3 id="conformance-transformation-processor">
-<head>Transformation Processor Conformance</head>
-<p>A TTML processor is a conformant TTML transformation processor if
-the following criteria are satisfied:</p>
-<olist>
-<item>
-<p>The processor satisfies all requirements specified by
-<specref ref="conformance-generic-processor"/>.</p>
-</item>
-<item>
-<p>The processor supports the DFXP Transformation profile as specified
-by <specref ref="profile-dfxp-transformation"/>.</p>
-</item>
-</olist>
-</div3>
-<div3 id="conformance-presentation-processor">
-<head>Presentation Processor Conformance</head>
-<olist>
-<item>
-<p>The processor satisfies all requirements specified by
-<specref ref="conformance-generic-processor"/>.</p>
-</item>
-<item>
-<p>The processor supports the DFXP Presentation profile as specified
-by <specref ref="profile-dfxp-presentation"/>.</p>
-</item>
-</olist>
-</div3>
-</div2>
-<div2 id="claims">
-<head>Claims</head>
-<p>Any claim of compliance with respect to TTML content or processor
-conformance must make
-reference to an implementation compliance statement (ICS).</p>
-<p>An implementation compliance statement must identify all mandatory
-and optional features of this specification that are satisfied by the
-content or processor implementation. In particular, the statement must
-identify the utilized or supported TTML vocabulary profile(s) as
-defined by <specref ref="vocabulary-profiles"/>, and, if a subset or
-superset profile is used or supported, then what features are excluded
-or included in the subset or superset profile.</p>
-<p>A TTML document instance for which a compliance claim is made
-must specify
-either (1)
-a <att>ttp:profile</att> attribute on its root
-<el>tt</el>
-element
-as defined by <specref ref="parameter-attribute-profile"/>
-or (2)
-a <el>ttp:profile</el> element as a child of the
-<el>head</el> element as defined by
-<specref ref="parameter-vocabulary-profile"/>.</p>
-</div2>
-</div1>
-<div1 id="doctypes">
-<head>Document Types</head>
-<p>This section defines the following TTML Abstract Document Types:</p>
-<ulist>
-<item><p><specref ref="dfxp-content-doctype"/></p></item>
-</ulist>
-<p>Each abstract document type consists of the following constraints:</p>
-<ulist>
-<item><p>a non-empty collection of element types, where each element type consists of a name,
-a (possibly empty) collection of attributes, and a content specification</p></item>
-<item><p>a non-empty collection of element types that may appear as the document element</p></item>
-</ulist>
-<p>An Abstract Document Instance may be assessed in terms of validity,
-and is considered to be a Valid Abstract Document Instance if it
-satisfies the following condition: if after</p>
-<olist>
-<item>
-<p>pruning all element information
-items whose names are not members of the collection of element types defined
-by the associated abstract document type, then</p>
-</item>
-<item>
-<p>pruning character
-information item children from any remaining element in case that all
-character children of the element denote XML whitespace characters and the element's type
-is defined as empty in the associated Abstract Document Type, and then</p>
-</item>
-<item>
-<p>pruning all attribute
-information items having expanded names such that the namespace URI of the
-expanded names are not listed in <specref
-ref="namespace-vocab-table"/>,</p>
-</item>
-</olist>
-<p>then the document element is one of the document
-element types permitted by the associated abstract document type,
-the descendants of the document
-element satisfy their respective element type's content
-specifications, all required attributes are present, and the declared
-value of each attribute satisfies the type declared by the
-associated abstract document type.</p>
-<note>
-<p>While a conformant processor may not <emph>a priori</emph> reject a
-conformant document instance that adheres to a
-supported content profile, a given document instance may be
-constrained by the author or authoring tool to satisfy a more
-restrictive definition of validity.</p>
-</note>
-<div2 id="dfxp-content-doctype">
-<head>DFXP Content</head>
-<p>DFXP Content is an abstract document type of a profile of the Timed Text Markup Language intended
-to be used for interchange among distribution systems. This document type
-is defined in terms of the
-element and attribute vocabulary
-specified in <specref ref="vocabulary"/>.</p>
-<p>This specification defines two types of normative schemas that may be used to validate a subset of
-conformant DFXP Content document instances:</p>
-<ulist>
-<item><p><specref ref="dfxp-schema-rnc"/></p></item>
-<item><p><specref ref="dfxp-schema-xsd"/></p></item>
-</ulist>
-<p>The (root) document element of a DFXP Content document instance must be a
-<el>tt</el> element, as defined by <specref
-ref="document-structure-vocabulary-tt"/>.</p>
-<note role="clarification">
-<p>The schemas included in this specification do not validate all syntactic constraints
-defined by this specification. In particular, performing validation with one of the above
-referenced schemas may result in a <emph>false positive</emph> indication of validity.
-However, with one exception, their
-use will not produce a <emph>false negative</emph> indication of validity
-when used with a compliant validating
-processor.</p>
-<p>In exception to the above statement about false negatives,
-if the Relax NG schema included in this specification is used to validate a
-TTML Document containing elements in a foreign namespace and the <att>xml:id</att>
-attribute is used with any of those (foreign) elements,
-then an error will be reported even though such usage is permitted by this
-specification. In this case, the false negative arises due
-to a specific limitation in expressing wildcard patterns involving <code>xsd:ID</code>
-typed attributes in Relax NG schemas.
-Note that this specification defines the formal validity of a TTML Document to be
-based on an abstract document instance from which all foreign namespace elements and
-attributes have been removed. Therefore, the exceptional reporting of this false
-negative does not impact the formal assessment of TTML Document validity.</p>
-</note>
-</div2>
-</div1>
-<div1 id="vocabulary">
-<head>Vocabulary</head>
-<p>This section defines the
-namespaces, profiles, and vocabulary (as an element an attribute
-catalog) of the Timed Text Markup Language (TTML) as follows:</p>
-<ulist>
-<item><p><specref ref="vocabulary-namespaces"/></p></item>
-<item><p><specref ref="vocabulary-profiles"/></p></item>
-<item><p><specref ref="vocabulary-overview"/></p></item>
-</ulist>
-<div2 id="vocabulary-namespaces">
-<head>Namespaces</head>
-<p>The Timed Text Markup Language (TTML) employs a number of
-namespaces for elements and certain
-global attributes. The following table specifies this set of namespaces
-and indicates the default prefix used within this specification and the
-normative URI that denotes each namespace.</p>
-<note role="explanation">
-<p>In a specific document instance, it is not required that the default
-prefixes shown below are used. Any prefix or namespace binding that satisfies the constraints
-of XML Namespaces may be used that is associated with the specified namespace URI.</p>
-</note>
-<table id="namespace-vocab-table" role="common">
-<caption>Table 1 &ndash; Namespaces</caption>
-<col width="30%"/>
-<tbody>
-<tr>
-<th>Name</th>
-<th>Prefix</th>
-<th>Value</th>
-</tr>
-<tr>
-<td>TT</td>
-<td><code>tt:</code></td>
-<td><code>http://www.w3.org/ns/ttml</code></td>
-</tr>
-<tr>
-<td>TT Parameter</td>
-<td><code>ttp:</code></td>
-<td><code>http://www.w3.org/ns/ttml#parameter</code></td>
-</tr>
-<tr>
-<td>TT Style</td>
-<td><code>tts:</code></td>
-<td><code>http://www.w3.org/ns/ttml#styling</code></td>
-</tr>
-<tr>
-<td>TT Metadata</td>
-<td><code>ttm:</code></td>
-<td><code>http://www.w3.org/ns/ttml#metadata</code></td>
-</tr>
-<tr>
-<td>TT Profile</td>
-<td><emph>none</emph></td>
-<td><code>http://www.w3.org/ns/ttml/profile/</code></td>
-</tr>
-<tr>
-<td>TT Feature</td>
-<td><emph>none</emph></td>
-<td><code>http://www.w3.org/ns/ttml/feature/</code></td>
-</tr>
-<tr>
-<td>TT Extension</td>
-<td><emph>none</emph></td>
-<td><code>http://www.w3.org/ns/ttml/extension/</code></td>
-</tr>
-</tbody>
-</table>
-<note role="clarification">
-<p>If a reference to an element type is used in this specification and the name
-of the element type is not namespace qualified, then the TT Namespace applies.</p>
-<p>For certain namespaces defined above, the default prefix
-is specified as <emph>none</emph> if no XML vocabulary is defined in
-the namespace by this specification (nor expected to be defined in a
-future version of this specification). In such cases, the use of the
-namespace URI is for purposes other than defining XML vocabulary,
-e.g., for designating profiles, features, extensions and for
-dereferencing standard profile definitions.</p>
-</note>
-<p>All TTML Namespaces are <loc
-href="http://www.w3.org/2001/tag/doc/namespaceState#namespacedef"><emph>mutable</emph></loc>
-<bibref ref="nsstate"/>; all undefined names in these namespaces are reserved for future
-standardization by the W3C.</p>
-</div2>
-<div2 id="vocabulary-profiles">
-<head>Profiles</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
-profiles, indicating
-a normative name
-and designator for each
-predefined profile,
-and where each of these profiles is formally elaborated in
-<specref ref="profiles"/>.</p>
-<table id="profile-vocab-table" role="common">
-<caption>Table 2 &ndash; Profiles</caption>
-<col width="25%"/>
-<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>
-</tbody>
-</table>
-<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>dfxp-presentation</code>, then the absolutized profile designator
-would be
-<code>http://www.w3.org/ns/ttml/profile/dfxp-presentation</code>.</p>
-</note>
-<p>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 Profile Definition Document.</p>
-<p>The profile of TTML that must be supported by a
-TTML content processor in order to process a document
-instance is specified either (1) by specifying a
-<att>ttp:profile</att> attribute on the root <el>tt</el> element, as
-defined by <specref ref="parameter-attribute-profile"/>, or (2) by
-including one or more <el>ttp:profile</el>
-elements in the <el>head</el> element, in
-accordance with <specref ref="parameter-vocabulary-profile"/>.</p>
-<p>If a <el>ttp:profile</el> element appears as a
-descendant of the <el>tt</el> element, then the <loc
-href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
-attribute should not be specified on the <el>tt</el> element. If both
-a <el>ttp:profile</el> element and a <att>ttp:profile</att>
-attribute are present (in a given document instance), then the
-<att>ttp:profile</att> attribute must be ignored for the purpose of
-determining the declared profile requirements.</p>
-<p>If more than one <el>ttp:profile</el> element appears in
-a TTML document instance, then all specified profiles apply
-simultaneously.  In such a case, if some feature or some extension is
-specified by one profile to be used (mandatory and enabled) and by
-another profile to be required (mandatory) or optional (voluntary),
-then that feature or extension must be considered to be used
-(mandatory and enabled); if some feature or some extension is
-specified by one profile to be merely required (mandatory) and by
-another profile to be optional (voluntary), then that feature or
-extension must be considered to be required (mandatory).</p>
-<p>If neither
-<loc href="#parameter-attribute-profile"><att>ttp:profile</att></loc>
-attribute nor
-<loc href="#parameter-vocabulary-profile"><el>ttp:profile</el></loc>
-element is present in a TTML document instance, and if the document
-interchange context does not specify a profile,
-then the DFXP Transformation
-profile applies.</p>
-<note role="elaboration">
-<p>It is intended that the <att>ttp:profile</att> attribute be used when
-the author wishes to reference one of the standard, predefined profiles of
-TTML content, and does not wish to modify (by supersetting or subsetting)
-that profile. This attribute may also be used by an author to indicate the use
-of a non-standard profile, in which case the specified profile designator expresses
-a URI that denotes an externally defined TTML Profile Definition Document.
-However, it is not required that a conformant TTML content processor be able
-to dereference such an externally specified profile definition.</p>
-<p>In contrast, it is intended that the <el>ttp:profile</el> element be
-used when the author wishes to make use of a modified predefined profile or
-wishes to include in the document instance a non-standard profile definition
-not based upon one of the predefined profiles.</p>
-<p>A predefined profile is supersetted by specifying some feature or extension to
-be required (mandatory) that was either not specified in the underlying, baseline
-profile or was specified as optional (voluntary) in the baseline profile.
-A predefined profile is subsetted by specifying some feature or extension to
-be optional (voluntary) that was specified as required in the underlying, baseline
-profile.</p>
-<p>When a baseline profile is modified by subsetting, the resulting, derived profile
-is referred to as a <emph>subtractive</emph> profile; when modified by supersetting, the result
-is referred to as an <emph>additive</emph> profile.
-It is also possible to define a derived profile that is simultaneously subtractive
-and additive.</p>
-</note>
-<p>If a TTML document instance makes use of a feature defined by
-<specref ref="feature-designations"/> and if the intended use of the
-document requires the recognition and processing of that feature, then
-the document must include a <emph>required feature</emph> or
-a <emph>used feature</emph>
-specification in one of its declared or
-referenced profiles.  If a TTML document instance makes use
-of an extension designatable by <specref
-ref="extension-designations"/> and if the intended use of the document
-requires the recognition and processing of that extension, then the
-document must include a <emph>required extension</emph> or
-a <emph>used extension</emph> specification
-in one of its declared or referenced
-profiles.</p>
-<note role="elaboration">
-<p>A required or used feature
-specification is expressed directly (or indirectly by referring to a
-profile) by means of a <loc
-href="#parameter-vocabulary-feature"><el>ttp:feature</el></loc>
-element where the value of its <att>value</att> attribute is
-<code>required</code> or <code>use</code>,
-respectively.  A required or used
-extension specification is expressed directly (or indirectly by
-referring to a profile) by means of a <loc
-href="#parameter-vocabulary-extension"><el>ttp:extension</el></loc>
-element where the value of its <att>value</att> attribute is
-<code>required</code> or <code>use</code>,
-respectively.</p>
-</note>
-<p>An example of an author defined
-additive, derived profile of the DFXP Presentation
-profile is shown
-below in <specref ref="dfxp-example-sub-profile"/>.</p>
-<table id="dfxp-example-sub-profile" role="example">
-<caption>Example Fragment &ndash; DFXP Additive Profile</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;tt xml:lang="" xmlns="http://www.w3.org/ns/ttml"&gt;
- &lt;head&gt;
-   &lt;profile use="dfxp-presentation" xmlns="http://www.w3.org/ns/ttml#parameter"&gt;
-     &lt;features xml:base="http://www.w3.org/ns/ttml/feature/"&gt;
-       &lt;feature value="required"&gt;#fontStyle-italic&lt;/feature&gt;
-     &lt;/features&gt;
-   &lt;/profile&gt;
- &lt;/head&gt;
- &lt;body/&gt;
-&lt;/tt&gt;
-</eg>
-</td></tr>
-</tbody>
-</table>
-<note role="explanation">
-<p>In the above example, the baseline profile is declared to be
-the DFXP Presentation profile, which is then additively modified by making the
-<code>#fontStyle-italic</code> feature required (rather than
-optional as it is defined
-in <specref ref="profile-dfxp-presentation"/>). Note also the resetting of the
-default XMLNS binding on the <el>profile</el> element to the TT Parameter Namespace.</p>
-</note>
-</div2>
-<div2 id="vocabulary-overview">
-<head>Catalog</head>
-<p>The vocabulary of the Timed Text Markup Language (TTML) is
-defined in the following major catalogs (divisions of vocabulary):</p>
-<ulist>
-<item><p><specref ref="core-vocabulary-overview"/></p></item>
-<item><p><specref ref="extension-vocabulary-overview"/></p></item>
-</ulist>
-<p>The core catalog defines the baseline, core vocabulary of TTML,
-and, in particular, the vocabulary of DFXP Content. The extension catalog
-serves as a placeholder for extensions to the core vocabulary defined
-by TTML.</p>
-<div3 id="core-vocabulary-overview">
-<head>Core Catalog</head>
-<p>The core vocabulary catalog is intended to satisfy the needs of
-TTML while providing a baseline vocabulary for future profiles. This vocabulary
-is divided into distinct categories, specified in detail
-in the following sections:</p>
-<ulist>
-<item><p><specref ref="parameters"/></p></item>
-<item><p><specref ref="content"/></p></item>
-<item><p><specref ref="styling"/></p></item>
-<item><p><specref ref="layout"/></p></item>
-<item><p><specref ref="timing"/></p></item>
-<item><p><specref ref="animation"/></p></item>
-<item><p><specref ref="metadata"/></p></item>
-</ulist>
-<p>The core element vocabulary specified for use with a TTML document
-instance is enumerated in
-<specref ref="element-vocab-table"/>.</p>
-<table id="element-vocab-table" role="common">
-<caption>Table 3 &ndash; Element Vocabulary</caption>
-<col width="25%"/>
-<tbody>
-<tr>
-<th>Module</th>
-<th>Elements</th>
-</tr>
-<tr>
-<td>
-Animation
-</td>
-<td>
-<loc href="#animation-vocabulary-set">set</loc>
-</td>
-</tr>
-<tr>
-<td>
-Content
-</td>
-<td>
-<loc href="#document-structure-vocabulary-body">body</loc>,
-<loc href="#content-vocabulary-div">div</loc>,
-<loc href="#content-vocabulary-p">p</loc>,
-<loc href="#content-vocabulary-span">span</loc>,
-<loc href="#content-vocabulary-br">br</loc>
-</td>
-</tr>
-<tr>
-<td>
-Document
-</td>
-<td>
-<loc href="#document-structure-vocabulary-tt">tt</loc>
-</td>
-</tr>
-<tr>
-<td>
-Head
-</td>
-<td>
-<loc href="#document-structure-vocabulary-head">head</loc>
-</td>
-</tr>
-<tr>
-<td>
-Layout
-</td>
-<td>
-<loc href="#layout-vocabulary-layout">layout</loc>,
-<loc href="#layout-vocabulary-region">region</loc>
-</td>
-</tr>
-<tr>
-<td>
-Metadata
-</td>
-<td>
-<loc href="#metadata-vocabulary-metadata">metadata</loc>
-</td>
-</tr>
-<tr>
-<td>
-Metadata Items
-</td>
-<td>
-<loc href="#metadata-vocabulary-actor">ttm:actor</loc>,
-<loc href="#metadata-vocabulary-agent">ttm:agent</loc>,
-<loc href="#metadata-vocabulary-copyright">ttm:copyright</loc>,
-<loc href="#metadata-vocabulary-desc">ttm:desc</loc>,
-<loc href="#metadata-vocabulary-name">ttm:name</loc>,
-<loc href="#metadata-vocabulary-title">ttm:title</loc>
-</td>
-</tr>
-<tr>
-<td>Parameter Items</td>
-<td><loc href="#parameter-vocabulary-profile">ttp:profile</loc>,
-<loc href="#parameter-vocabulary-features">ttp:features</loc>,
-<loc href="#parameter-vocabulary-feature">ttp:feature</loc>,
-<loc href="#parameter-vocabulary-extensions">ttp:extensions</loc>,
-<loc href="#parameter-vocabulary-extension">ttp:extension</loc>
-</td>
-</tr>
-<tr>
-<td>
-Styling
-</td>
-<td>
-<loc href="#styling-vocabulary-styling">styling</loc>,
-<loc href="#styling-vocabulary-style">style</loc>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<p>Element vocabulary groups that are used in defining content models
-for TTML element types are enumerated in <specref ref="element-vocab-group-table"/>.</p>
-<table id="element-vocab-group-table" role="common">
-<caption>Table 4 &ndash; Element Vocabulary Groups</caption>
-<col width="25%"/>
-<tbody>
-<tr>
-<th>Group</th>
-<th>Elements</th>
-</tr>
-<tr>
-<td>
-Animation.class
-</td>
-<td>
-<loc href="#animation-vocabulary-set">set</loc>
-</td>
-</tr>
-<tr>
-<td>
-Block.class
-</td>
-<td>
-<loc href="#content-vocabulary-div">div</loc> |
-<loc href="#content-vocabulary-p">p</loc>
-</td>
-</tr>
-<tr>
-<td>
-Inline.class
-</td>
-<td>
-<loc href="#content-vocabulary-span">span</loc> |
-<loc href="#content-vocabulary-span">br</loc> |
-<code>#PCDATA</code>
-</td>
-</tr>
-<tr>
-<td>
-Metadata.class
-</td>
-<td>
-<loc href="#metadata-vocabulary-metadata">metadata</loc> |
-<loc href="#metadata-vocabulary-copyright">ttm:agent</loc> |
-<loc href="#metadata-vocabulary-copyright">ttm:copyright</loc> |
-<loc href="#metadata-vocabulary-desc">ttm:desc</loc> |
-<loc href="#metadata-vocabulary-title">ttm:title</loc>
-</td>
-</tr>
-<tr>
-<td>Parameters.class</td>
-<td><loc
-href="#parameter-vocabulary-profile">ttp:profile</loc></td>
-</tr>
-</tbody>
-</table>
-<p/>
-<p>The attribute vocabulary specified for use with the core vocabulary
-catalog is enumerated in
-<specref ref="attribute-vocab-table"/>.</p>
-<table id="attribute-vocab-table" role="common">
-<caption>Table 5 &ndash; Attribute Vocabulary</caption>
-<col width="25%"/>
-<tbody>
-<tr>
-<th>Module</th>
-<th>Attributes</th>
-</tr>
-<tr>
-<td>
-Core Attributes
-</td>
-<td>
-<loc href="#content-attribute-id">xml:id</loc>,
-<loc href="#content-attribute-lang">xml:lang</loc>,
-<loc href="#content-attribute-space">xml:space</loc>
-</td>
-</tr>
-<tr>
-<td>
-Layout
-</td>
-<td>
-<loc href="#layout-attribute-region">region</loc>
-</td>
-</tr>
-<tr>
-<td>
-Metadata Attributes
-</td>
-<td>
-<loc href="#metadata-attribute-agent">ttm:agent</loc>,
-<loc href="#metadata-attribute-role">ttm:role</loc>
-</td>
-</tr>
-<tr>
-<td>
-Parameter Attributes
-</td>
-<td>
-<loc href="#parameter-attribute-cellResolution">ttp:cellResolution</loc>,
-<loc href="#parameter-attribute-clockMode">ttp:clockMode</loc>,
-<loc href="#parameter-attribute-dropMode">ttp:dropMode</loc>,
-<loc href="#parameter-attribute-frameRate">ttp:frameRate</loc>,
-<loc href="#parameter-attribute-frameRateMultiplier">ttp:frameRateMultipler</loc>,
-<loc href="#parameter-attribute-markerMode">ttp:markerMode</loc>,
-<loc href="#parameter-attribute-pixelAspectRatio">ttp:pixelAspectRatio</loc>,
-<loc href="#parameter-attribute-profile">ttp:profile</loc>,
-<loc href="#parameter-attribute-subFrameRate">ttp:subFrameRate</loc>,
-<loc href="#parameter-attribute-tickRate">ttp:tickRate</loc>,
-<loc href="#parameter-attribute-timeBase">ttp:timeBase</loc>
-</td>
-</tr>
-<tr>
-<td>
-Styling
-</td>
-<td>
-<loc href="#style-attribute-style">style</loc>
-</td>
-</tr>
-<tr>
-<td>
-Styling Attributes
-</td>
-<td>
-<loc href="#style-attribute-backgroundColor">tts:backgroundColor</loc>,
-<loc href="#style-attribute-color">tts:color</loc>,
-<loc href="#style-attribute-direction">tts:direction</loc>,
-<loc href="#style-attribute-display">tts:display</loc>,
-<loc href="#style-attribute-displayAlign">tts:displayAlign</loc>,
-<loc href="#style-attribute-extent">tts:extent</loc>,
-<loc href="#style-attribute-fontFamily">tts:fontFamily</loc>,
-<loc href="#style-attribute-fontSize">tts:fontSize</loc>,
-<loc href="#style-attribute-fontStyle">tts:fontStyle</loc>,
-<loc href="#style-attribute-fontWeight">tts:fontWeight</loc>,
-<loc href="#style-attribute-lineHeight">tts:lineHeight</loc>,
-<loc href="#style-attribute-opacity">tts:opacity</loc>,
-<loc href="#style-attribute-origin">tts:origin</loc>,
-<loc href="#style-attribute-overflow">tts:overflow</loc>,
-<loc href="#style-attribute-padding">tts:padding</loc>,
-<loc href="#style-attribute-showBackground">tts:showBackground</loc>,
-<loc href="#style-attribute-textAlign">tts:textAlign</loc>,
-<loc href="#style-attribute-textDecoration">tts:textDecoration</loc>,
-<loc href="#style-attribute-textOutline">tts:textOutline</loc>,
-<loc href="#style-attribute-unicodeBidi">tts:unicodeBidi</loc>,
-<loc href="#style-attribute-visibility">tts:visibility</loc>,
-<loc href="#style-attribute-wrapOption">tts:wrapOption</loc>,
-<loc href="#style-attribute-writingMode">tts:writingMode</loc>,
-<loc href="#style-attribute-zIndex">tts:zIndex</loc>
-</td>
-</tr>
-<tr>
-<td>
-Timing Attributes
-</td>
-<td>
-<loc href="#timing-attribute-begin">begin</loc>,
-<loc href="#timing-attribute-dur">dur</loc>,
-<loc href="#timing-attribute-end">end</loc>,
-<loc href="#timing-attribute-timeContainer">timeContainer</loc>
-</td>
-</tr>
-</tbody>
-</table>
-<note role="explanation">
-<p>Only those attributes defined as either (1) global, i.e., namespace qualified, or
-(2) shared element-specific, i.e., not namespace qualified but shared across multiple
-element types, are listed in <specref ref="attribute-vocab-table"/> above.
-</p>
-</note>
-<note role="explanation">
-<p>All vocabulary defined by TTML consistently makes use of
-the so-called <emph>lowerCamelCase</emph> naming convention. In some cases, this results in the
-change of a name when the name was based upon another specification
-that used a different naming convention.</p>
-</note>
-</div3>
-<div3 id="extension-vocabulary-overview">
-<head>Extension Catalog</head>
-<p>The extension vocabulary catalog is intended for use by future
-profiles of TTML, and is not further defined
-by this version of this specification.</p>
-<p>In addition to standardized extension vocabulary, a conforming TTML
-document instance may contain arbitrary namespace qualified
-elements that reside in any namespace other than those namespaces
-defined for use with this specification. Furthermore, a conforming TTML
-document instance may contain arbitrary namespace qualified
-attributes on TTML defined vocabulary where such attributes reside in
-any namespace other than those defined for use with this
-specification.</p>
-</div3>
-</div2>
-</div1>
-<div1 id="parameters">
-<head>Parameters</head>
-<p>This section specifies the <emph>parameters</emph> matter of the
-core vocabulary catalog, where
-parameters are to be understood as information that is either (1)
-essential or (2) of significant importance for the purpose of
-interpreting the semantics of other types of information expressed by
-core vocabulary items or for establishing a processing context by means
-of which TTML content can be related to an external environment.</p>
-<div2 id="parameter-element-vocabulary">
-<head>Parameter Element Vocabulary</head>
-<p>The following elements, all defined in the TT Parameter
-Namespace, specify parametric information that applies to a document
-or a content processor:</p>
-<ulist>
-<item><p><specref ref="parameter-vocabulary-profile"/></p></item>
-<item><p><specref ref="parameter-vocabulary-features"/></p></item>
-<item><p><specref ref="parameter-vocabulary-feature"/></p></item>
-<item><p><specref ref="parameter-vocabulary-extensions"/></p></item>
-<item><p><specref ref="parameter-vocabulary-extension"/></p></item>
-</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
-may be supported by a TTML content processor in order to process a TTML
-document that makes use (or may make use) of such features and
-extensions.</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:
-if defined in this specification (or a future revision thereof) and
-labeled with a feature designation in <specref ref="features"/>, then
-it is considered to be a feature; if defined in another specification
-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>
-</note>
-<p>This specification defines two distinct uses of the <el>ttp:profile</el> element:</p>
-<ulist>
-<item>
-<p>as a child of the <el>head</el> element within a TTML document
-instance;</p>
-</item>
-<item>
-<p>as the root element of a TTML Profile Definition document
-instance;</p>
-</item>
-</ulist>
-<p>When a <el>tt:profile</el> element appears within a TTML document
-instance, its purpose is to express authorial intentions about which
-features and extensions must or may be supported by a recipient
-content processor. In addition, the element indirectly expresses
-information about the set of features or extensions that are (or may
-expected to be) used by the document instance.</p>
-<p>When a <el>tt:profile</el> element is used by a TTML
-Profile Definition document instance, it serves to publish a machine
-readable specification of a specific TTML content profile, of which
-this specification defines three such Profile Definition Documents in
-<specref ref="profiles"/>.</p>
-<p>The <el>ttp:profile</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group, followed by
-zero or more <el>ttp:features</el> elements, followed by
-zero or more <el>ttp:extensions</el> elements.</p>
-<table id="elt-syntax-parameter-profile" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: ttp:profile</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;ttp:profile
-  use = string
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#parameter-vocabulary-features">ttp:features</loc>*, <loc href="#parameter-vocabulary-extensions">ttp:extensions</loc>*
-&lt;/ttp:profile&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If specified, the <att>use</att> attribute must adhere to the
-<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-&sect;3.2.17, and, furthermore, must denote a profile designator in
-accordance with <specref ref="vocabulary-profiles"/>. In this case,
-the profile designator must refer to (1) a standard, predefined
-TTML Profile Definition Document as defined by <specref ref="profiles"/>,
-or (2) a dereferenceable resource representing a valid TTML Profile Definition
-document instance. In either case, the referenced profile serves as the
-baseline profile of the specifying <el>ttp:profile</el> element.</p>
-<p>If the <att>use</att> attribute is not specified, then the baseline
-profile of the <el>ttp:profile</el> element must be considered to be
-the empty (null) profile, i.e., a profile definition containing no
-feature or extension specifications.</p>
-<p>The collection of features and extensions of a profile are determined according
-to the following ordered rules:</p>
-<olist>
-<item>
-<p>initialize the features and extensions of the profile to the empty
-set;</p>
-</item>
-<item>
-<p>if a <att>use</att> attribute is present, then augment the profile
-with the set of features and extensions specified by the referenced
-baseline profile;</p>
-</item>
-<item>
-<p>for each <el>ttp:feature</el> and <el>ttp:extension</el> element
-descendant of the <el>ttp:profile</el> element, using a post-order
-traversal, merge the specified feature or extension with the features
-and extensions of the profile, where merging a feature or extension
-entails replacing an existing feature or extension specification, if
-it already exists, or adding a new feature or extension specification,
-if it does not yet exist in the profile;</p>
-</item>
-</olist>
-<p>A conformant TTML processor is not required to be able to
-dereference a TTML Profile Definition Document that is not one of the
-standard, predefined profiles defined by <specref ref="profiles"/>.  A
-conformant TTML processor may make use of a built-in, static
-form of each standard, predefined profile so as not to require
-dereferencing a network resource.</p>
-<p>If a TTML processor is unable to dereference a non-standard TTML
-Profile Definition Document, then it must not further process the
-document without the presence of an explicit override from an end-user
-or some implementation specific parameter traceable to an end-user or
-to a user or system configuration setting. If a TTML processor aborts
-processing of a TTML document instance due to the inability to
-reference a non-standard TTML Profile Definition Document, then some
-end-user notification should be given unless the end-user or system
-has disabled such a notification, or if the processor does not permit
-or entail the intervention of an end-user.</p>
-<p>The <el>ttp:profile</el> element is illustrated by the following example.</p>
-<table id="parameter-vocabulary-profile-example-1" role="example">
-<caption>Example Fragment &ndash; ttp:profile</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;ttp:profile use="dfxp-presentation"&gt;
-  &lt;ttp:features xml:base="http://www.w3.org/ns/ttml/feature/"&gt;
-    &lt;ttp:feature&gt;#text-outline&lt;/ttp:feature&gt;
-  &lt;/ttp:features&gt;
-&lt;/ttp:profile&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<note role="explanation">
-<p>In the above example, the DFXP presentation profile is used as the
-baseline profile. This baseline profile is then supersetted (thus
-creating an additive derived profile) by requiring support for
-<code>#text-outline</code> feature.</p>
-</note>
-</div3>
-<div3 id="parameter-vocabulary-features">
-<head>ttp:features</head>
-<p>The <el>ttp:features</el> element is a container element used to group
-infomation about feature support requirements.</p>
-<p>The <el>ttp:features</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group, followed by
-zero or more <el>ttp:feature</el> elements.</p>
-<table id="elt-syntax-parameter-features" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: ttp:features</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;ttp:features
-  xml:base = string : <emph>TT Feature Namespace</emph>
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#parameter-vocabulary-feature">ttp:feature</loc>*
-&lt;/ttp:features&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If specified, the <att>xml:base</att>
-attribute must (1) adhere to the
-<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-&sect;3.2.17, (2) express an absolute URI that
-adheres to <bibref ref="xmlbase"/> and,
-(3) express a feature namespace as defined by
-<specref ref="feature-designations"/>. If not specified, the
-<att>xml:base</att> attribute's default
-value applies, which is the TT Feature Namespace.</p>
-<p>The <att>xml:base</att> attribute is
-used to permit the abbreviation of feature designation URIs expressed
-by child <el>ttp:feature</el> elements.</p>
-</div3>
-<div3 id="parameter-vocabulary-feature">
-<head>ttp:feature</head>
-<p>The <el>ttp:feature</el> element is used to specify
-infomation about support requirements for a particular feature.</p>
-<p>The children of the <el>ttp:feature</el> element must express a non-empty
-sequence of character information items that adheres to the
-<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-&sect;3.2.17.</p>
-<table id="elt-syntax-parameter-feature" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: ttp:feature</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;ttp:feature
-  value = (optional|required|use) : required
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> #PCDATA
-&lt;/ttp:feature&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If the URI expressed by the content of the <el>ttp:feature</el>
-element is a relative URI, then, when combined with the
-feature namespace value expressed by the
-<att>xml:base</att> attribute of the
-nearest ancestor <el>ttp:features</el> element, it must express an
-absolute URI.  In either case (original absolute URI or resulting
-absolutized URI), the URI expressed by the <el>ttp:feature</el>
-element must further adhere to the syntax of a feature designation as
-defined by <specref ref="feature-designations"/>.</p> <p>If
-the URI expressed by the content of the <el>ttp:feature</el> element
-is a relative URI, then an <att>xml:base</att> attribute should be
-specified on the nearest ancestor <el>ttp:features</el> element.</p>
-<p>The <att>value</att> attribute specifies whether a conforming TTML
-processor must or may implement the designated feature in order to
-process the document. If the value of the <att>value</att> attribute
-is <code>optional</code>, then the processor need
-not implement or otherwise support the feature in order to process the
-document; if the value is <code>required</code>, then the processor
-must implement or otherwise support the feature in order to process
-the document; if the value is
-<code>use</code>, then the processor must both (1) implement or
-otherwise support the feature and (2) enable (activate) use of the
-feature.</p>
-
-<note role="clarification">
-<p>The default value of the <att>value</att> attribute is
-<code>required</code>, as indicated in the above element information
-item definition. Therefore, if a <att>value</att> attribute is not
-specified on a <el>ttp:feature</el> element, it is equivalent to
-specifying that support for the feature is required.</p>
-</note>
-<p>If the value of the <att>value</att> attribute is
-<code>required</code> or <code>use</code>,
-and if the TTML processor implementation does
-not support the feature, then it must not further process the document
-without the presence of an explicit override from an end-user or some
-implementation specific parameter traceable to an end-user or to a
-user or system configuration setting.  If a TTML processor aborts
-processing of a TTML document instance due to the specification of a
-required, but unsupported feature by this element, then some end-user
-notification should be given unless the end-user or system has
-disabled such a notification, or if the processor does not permit or
-entail the intervention of an end-user.</p>
-<p>If the value of the <att>value</att> attribute is
-<code>optional</code>, and if the TTML processor implementation does
-not support the feature, then it may further process the document even
-in the case that some use of the feature is present in the document.
-In the case of actual use of a feature designated as optional, the
-default semantics associated with that feature apply; that is, the
-processor may behave as if the feature were not actually used or
-referenced by the document. Notwithstanding the above, the syntactic
-presence or reference to an optional feature by a document must not be
-considered to be a violation of document validity or a barrier to
-further processing if the syntactic expression is well-formed and
-valid.</p>
-<p>The <el>ttp:feature</el> element is illustrated by the following example.</p>
-<table id="parameter-vocabulary-feature-example-1" role="example">
-<caption>Example Fragment &ndash; ttp:feature</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;ttp:profile use="http://www.w3.org/ns/ttml/profile/dfxp-presentation"&gt;
-  &lt;ttp:features xml:base="http://www.w3.org/ns/ttml/feature/"&gt;
-    <phrase role="strong">&lt;ttp:feature value="required"&gt;#fontStyle-italic&lt;/ttp:feature&gt;</phrase>
-    <phrase role="strong">&lt;ttp:feature value="required"&gt;#textDecoration-under&lt;/ttp:feature&gt;</phrase>
-  &lt;/ttp:features&gt;
-&lt;/ttp:profile&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<note role="explanation">
-<p>In the above example, the DFXP presentation profile is used as the
-baseline profile. This baseline profile is then modified by two
-<el>ttp:feature</el> elements in order to
-superset the baseline profile (since neither
-<code>#fontStyle-italic</code> nor <code>#textDecoration-under</code>
-are required by the DFXP presentation profile).  
-<!-- removed text:
-Note that
-the explicit specification of <code>required</code> on the
-<att>value</att> attribute on these two
-<el>ttp:feature</el> elements is not strictly
-necessary, since it is the default value of this
-attribute.--></p> 
-<p>The effect of this example is to express authorial intentions that
-italic font style and text underlining must be
-supported.</p>
-</note>
-</div3>
-<div3 id="parameter-vocabulary-extensions">
-<head>ttp:extensions</head>
-<p>The <el>ttp:extensions</el> element is a container element used to group
-infomation about extension support requirements.</p>
-<p>The <el>ttp:extensions</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group, followed by
-zero or more <el>ttp:extension</el> elements.</p>
-<table id="elt-syntax-parameter-extensions" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: ttp:extensions</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;ttp:extensions
-  xml:base = string : <emph>TT Extension Namespace</emph>
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#parameter-vocabulary-extension">ttp:extension</loc>*
-&lt;/ttp:extensions&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If specified, the <att>xml:base</att>
-attribute must (1) adhere to the
-<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-&sect;3.2.17, (2) express an absolute URI that
-adheres to <bibref ref="xmlbase"/> and,
-(3) express an extension namespace as defined by
-<specref ref="extension-designations"/>. If not specified, the
-<att>xml:base</att> attribute's default
-value applies, which is the TT Extension Namespace.</p>
-<p>The <att>xml:base</att> attribute is
-used to permit the abbreviation of feature designation URIs expressed
-by child <el>ttp:extension</el> elements.</p>
-</div3>
-<div3 id="parameter-vocabulary-extension">
-<head>ttp:extension</head>
-<p>The <el>ttp:extension</el> element is used to specify
-infomation about support requirements for a particular extension.</p>
-<p>The children of the <el>ttp:extension</el> element must express a non-empty
-sequence of character information items that adheres to the
-<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-&sect;3.2.17.</p>
-<table id="elt-syntax-parameter-extension" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: ttp:extension</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;ttp:extension
-  value = (optional|required|use) : required
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> #PCDATA
-&lt;/ttp:extension&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If the URI expressed by the content of the <el>ttp:extension</el>
-element is a relative URI, then, when combined with the
-extension namespace value expressed by the
-<att>xml:base</att> attribute of the
-nearest ancestor <el>ttp:extensions</el> element, it must express an
-absolute URI.  In either case (original absolute URI or resulting
-absolutized URI), the URI expressed by the <el>ttp:extension</el>
-element must further adhere to the syntax of an extension designation
-as defined by <specref ref="extension-designations"/>.</p>
-<p>If the URI expressed by the content of the
-<el>ttp:feature</el> element is a relative URI, then an
-<att>xml:base</att> attribute should be specified on the nearest
-ancestor <el>ttp:extensions</el> element.</p>
-<p>The <att>value</att> attribute specifies whether a conforming TTML
-processor must or may implement the designated extension in order to
-process the document. If the value of the <att>value</att> attribute
-is <code>optional</code>, then the processor need
-not implement or otherwise support the extension in order to process the
-document; if the value is <code>required</code>, then the processor
-must implement or otherwise support the extension in order to process
-the document; if the value is
-<code>use</code>, then the processor must both (1) implement or
-otherwise support the extension and (2) enable (activate) use of the
-extension.</p>
-<note role="clarification">
-<p>The default value of the <att>value</att> attribute is
-<code>required</code>, as indicated in the above element information
-item definition. Therefore, if a <att>value</att> attribute is not
-specified on a <el>ttp:extension</el> element, it is equivalent to
-specifying that support for the extension is required.</p>
-</note>
-<p>If the value of the <att>value</att> attribute is
-<code>required</code> or <code>use</code>,
-and if the TTML processor implementation does not support the
-extension, then it must not further process the document without the
-presence of an explicit override from an end-user or some
-implementation specific parameter traceable to an end-user or to a
-user or system configuration setting.  If a TTML processor aborts
-processing of a TTML document instance due to the specification of a
-required, but unsupported extension by this element, then some
-end-user notification should be given unless the end-user or system
-has disabled such a notification, or if the processor does not permit
-or entail the intervention of an end-user.</p>
-<p>If the value of the <att>value</att> attribute is
-<code>optional</code>, and if the TTML processor implementation does
-not support the extension, then it may further process the document even
-in the case that some use of the extension is present in the document.
-In the case of actual use of an extension designated as optional, the
-default semantics associated with that extension apply; that is, the
-processor may behave as if the extension were not actually used or
-referenced by the document. Notwithstanding the above, the syntactic
-presence or reference to an optional extension by a document must not be
-considered to be a violation of document validity or a barrier to
-further processing if the syntactic expression is well-formed and
-valid.</p>
-<p>The <el>ttp:extension</el> element is illustrated by the following example.</p>
-<table id="parameter-vocabulary-extension-example-1" role="example">
-<caption>Example Fragment &ndash; ttp:extension</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;ttp:profile use="http://www.w3.org/ns/ttml/profile/dfxp-transformation"&gt;
-  &lt;ttp:extensions xml:base="http://foo.bar.example.org/ttaf1/extension/"&gt;
-    <phrase role="strong">&lt;ttp:extension value="use"&gt;#prefilter-by-language&lt;/ttp:extension&gt;</phrase>
-  &lt;/ttp:extensions&gt;
-&lt;/ttp:profile&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<note role="explanation">
-<p>In the above example, the DFXP transformation profile is used as
-the baseline profile. This baseline profile is then supersetted by
-specifying that support and use is required for a private extension
-defined in a third party namespace.</p>
-<p>The effect of this example is to express authorial intentions that
-a recipient processor must support the DFXP transformation profile and
-must also support and use an extension defined by a third party.</p>
-</note>
-</div3>
-</div2>
-<div2 id="parameter-attribute-vocabulary">
-<head>Parameter Attribute Vocabulary</head>
-<p>The following attributes are defined in the TT Parameter Namespace.</p>
-<ulist>
-<item><p><specref ref="parameter-attribute-cellResolution"/></p></item>
-<item><p><specref ref="parameter-attribute-clockMode"/></p></item>
-<item><p><specref ref="parameter-attribute-dropMode"/></p></item>
-<item><p><specref ref="parameter-attribute-frameRate"/></p></item>
-<item><p><specref ref="parameter-attribute-frameRateMultiplier"/></p></item>
-<item><p><specref ref="parameter-attribute-markerMode"/></p></item>
-<item><p><specref ref="parameter-attribute-pixelAspectRatio"/></p></item>
-<item><p><specref ref="parameter-attribute-profile"/></p></item>
-<item><p><specref ref="parameter-attribute-subFrameRate"/></p></item>
-<item><p><specref ref="parameter-attribute-tickRate"/></p></item>
-<item><p><specref ref="parameter-attribute-timeBase"/></p></item>
-</ulist>
-<p>Unless explicitly stated otherwise, linear white-space (LWSP) may
-appear between tokens of a value of a TT Parameter.</p>
-<div3 id="parameter-attribute-cellResolution">
-<head>ttp:cellResolution</head>
-<p>The <att>ttp:cellResolution</att> attribute may be used by an author
-to express the number of horizontal and vertical cells into which the root container region
-area is divided for the purpose of expressing presentation semantics in terms of
-a uniform grid.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-cellResolution-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:cellResolution</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:cellResolution
-  : columns rows                            // <emph>columns</emph> != 0; <emph>rows</emph> != 0
-
-columns | rows
-  : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If not specified, the number of columns and rows must be considered
-to be 32 and 15, respectively. If specified, then columns or rows must not be zero (0).</p>
-<note role="motivation">
-<p>The choice of values 32 and 15 are based on this being the
-maximum number of columns and rows defined by <bibref
-ref="cea608c"/>.</p>
-</note>
-<p>A <att>ttp:cellResolution</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-<note role="explanation">
-<p>The use of a uniform grid is employed only for the purpose of
-measuring lengths and expressing coordinates. In particular, it is not
-assumed that the presentation of text or the alignment of individual
-glyph areas is
-coordinated with this grid. Such alignment is possible, but
-requires the use of a monospaced font and a font size whose EM square exactly
-matches the cell size.</p>
-</note>
-</div3>
-<div3 id="parameter-attribute-clockMode">
-<head>ttp:clockMode</head>
-<p>The <att>ttp:clockMode</att> attribute is used to specify the
-interpretation of time expressions as real-time time coordinates when
-operating with time base of <code>clock</code> as defined by <specref
-ref="parameter-attribute-timeBase"/>.</p>
-<note role="explanation">
-<p>See <specref ref="timing-time-value-expressions"/> for the
-specification of time expression syntax.</p>
-</note>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-clockMode-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:clockMode</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:clockMode
-  : "local"
-  | "gps"
-  | "utc"
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If the time base, defined by <specref
-ref="parameter-attribute-timeBase"/>, is designated as
-<code>clock</code>, then this parameter applies as follows: if the
-parameter's value is <code>local</code>, then time expressions are
-interpreted as local wall-clock time coordinates;
-if <code>utc</code>, then time expressions are
-interpreted as UTC time coordinates
-<bibref ref="utc"/>;
-if <code>gps</code>, then time expressions are
-interpreted as GPS time coordinates
-<bibref ref="gps"/>.</p>
-<note role="explanation">
-<p>The primary difference between GPS time and UTC time is that GPS
-time is not adjusted for leap seconds, while UTC time is adjusted as
-follows: UTC = TAI (<emph>Temp Atomique International</emph>) + <emph>leap seconds
-accumulated since 1972</emph>. TAI is maintained by the <emph>Bureau
-International des Poids et Mesures</emph> (BIPM) in Sevres, France.
-The GPS system time is steered to a Master Clock (MC) at the US Naval
-Observatory which is kept within a close but unspecified
-tolerance of TAI.</p>
-</note>
-<p>If not specified, the value of this parameter must be considered
-to be <code>utc</code>.</p>
-<p>A <att>ttp:clockMode</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-</div3>
-<div3 id="parameter-attribute-dropMode">
-<head>ttp:dropMode</head>
-<p>The <att>ttp:dropMode</att> attribute is used to specify
-constraints on the interpretation and use of frame counts
-that correspond with <bibref ref="smpte12m"/> time coordinates when operating
-with time base of <code>smpte</code> as defined by
-<specref ref="parameter-attribute-timeBase"/>.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-dropMode-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:dropMode</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:dropMode
-  : "dropNTSC"
-  | "dropPAL"
-  | "nonDrop"
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If the time base, defined by <specref
-ref="parameter-attribute-timeBase"/>, is designated as
-<code>smpte</code>, then this parameter applies as follows: if the
-parameter's value is <code>nonDrop</code>, then, within any given
-second of a time expression, frames count from 0 to
-<emph>N&minus;1</emph>, where <emph>N</emph> is the value specified by
-the <att>ttp:frameRate</att> parameter, but while ignoring any value
-specified by the <att>ttp:frameRateMultiplier</att> parameter.</p>
-<note role="clarification"> <p>When operating in <code>nonDrop</code>
-mode, a second of a time expression may or may not be equal to a
-second of real time during normal (1x speed) forward playback. If the
-<att>ttp:frameRateMultiplier</att> parameter is specified and is not
-equal to 1:1, then a second of a time expression will either be
-shorter or longer than a second of elapsed play in real
-time.</p></note>
-<p>If this parameter's value is <code>dropNTSC</code>, then, within any
-given second of a time expression except the second <code>00</code>,
-frames count from 0 to <emph>N&minus;1</emph>, where <emph>N</emph> is
-the value specified by the <att>ttp:frameRate</att> parameter, but
-while ignoring any value specified by the
-<att>ttp:frameRateMultiplier</att> parameter. If the second of a time
-expression is <code>00</code> and the minute of the time expression is
-not <code>00</code>, <code>10</code>, <code>20</code>, <code>30</code>,
-<code>40</code>, or <code>50</code>, then frame codes <code>00</code>
-and <code>01</code> are dropped during that second; otherwise, these
-frame codes are not dropped.</p>
-<note role="example"> <p>For example, when operating in <code>dropNTSC</code>
-mode with <att>ttp:frameRate</att> of <code>30</code>, a discontinuity
-in frame count occurs between consecutive frames as shown in the
-following sequence of time expressions: <code>01:08:59:28</code>,
-<code>01:08:59:29</code>, <code>01:09:00:02</code>,
-<code>01:09:00:03</code>.</p></note>
-<p>If this parameter's value is <code>dropPAL</code>, then, within any
-given second of a time expression except the second <code>00</code>,
-frames count from 0 to <emph>N&minus;1</emph>, where <emph>N</emph> is
-the value specified by the <att>ttp:frameRate</att> parameter, but
-while ignoring any value specified by the
-<att>ttp:frameRateMultiplier</att> parameter. If the second of a time
-expression is <code>00</code> and the minute of the time expression is
-even but not <code>00</code>, <code>20</code>, or <code>40</code>,
-then frame codes <code>00</code> through <code>03</code> are dropped
-during that second; otherwise, these frame codes are not dropped.</p>
-<note role="example"><p>For example, when operating in <code>dropPAL</code>
-mode with <att>ttp:frameRate</att> of <code>30</code>, a discontinuity
-in frame count occurs between consecutive frames as shown in the
-following sequence of time expressions: <code>01:09:59:28</code>,
-<code>01:09:59:29</code>, <code>01:10:00:04</code>,
-<code>01:10:00:04</code>.</p></note>
-<note role="explanation">
-<p>The <code>dropPAL</code> mode is also known as the
-<emph>M/PAL</emph> or <emph>PAL (M)</emph> drop-frame
-code, which uses PAL modulation with the NTSC frame rate of ~29.97
-frames/second. The M/PAL system is used primarily in Brazil.</p>
-</note>
-<p>If not specified, then <code>nonDrop</code> must be assumed to apply.</p>
-<p>A <att>ttp:dropMode</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-</div3>
-<div3 id="parameter-attribute-frameRate">
-<head>ttp:frameRate</head>
-<p>The <att>ttp:frameRate</att> attribute is used to specify the frame rate of a related
-media object or the intrinsic frame rate of a document instance in case it is intended
-to function as an independent media object.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-frameRate-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:frameRate</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:frameRate
-  : <loc href="#style-value-digit">&lt;digit&gt;</loc>+                                // <emph>value</emph> > 0
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>The frame rate that applies to a document instance is used to
-interpret time expressions that are expressed in <emph>frames</emph>
-as defined by <specref ref="timing-value-timeExpression"/>.</p>
-<p>A frame is interpreted as a division of a second of media
-time, such that if the frame rate is specified as <emph>F</emph>, then
-a second of media time is divided into <emph>F</emph> intervals of
-equal duration, where each interval is labeled as frame <emph>f</emph>,
-with <emph>f</emph> &isin; [0&hellip;<emph>F&minus;1</emph>].</p>
-<p>If not specified, the frame rate must be considered to be equal to some
-application defined frame rate, or if no application defined frame rate applies,
-then thirty (30) frames per second. If specified, then the frame rate must
-be greater than zero (0).</p>
-<p>A <att>ttp:frameRate</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-</div3>
-<div3 id="parameter-attribute-frameRateMultiplier">
-<head>ttp:frameRateMultiplier</head>
-<p>The <att>ttp:frameRateMultiplier</att> attribute is used to
-specify a multiplier to be applied to the frame rate specified by a
-<att>ttp:frameRate</att> attribute in order to compute the effective
-frame rate.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-frameRateMultiplier-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:frameRateMultiplier</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:frameRateMultiplier
-  : numerator denominator                   // <emph>numerator</emph> != 0; <emph>denominator</emph> != 0
-
-numerator | denominator
-  : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>A frame rate multiplier is used when the desired frame rate cannot
-be expressed as an integral number of frames per second.</p>
-<p>If not specified, the frame rate multiplier must be considered to be equal to one (1:1).
-Both numerator and denominator must be non-zero.</p>
-<p>A <att>ttp:frameRateMultiplier</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-<note role="example">
-<p>The frame rate multiplier used for synchronizing with NTSC <bibref
-ref="smpte170m"/>
-formatted video objects at 30 frames per second is nominally
-1000:1001. The nominal frame rate of NTSC video is defined as the chrominance
-sub-carrier frequency of 3,579,545.45&hellip;Hz (= 5.0MHz &mult; 63/88) times the ratio 2/455 divided by
-the number of horizontal lines per frame of 525, which yields a frame
-rate of 29.970029970029&hellip; (= 30 &mult; 1000/1001) frames per
-second. Other frame rate multipliers apply to different regions of
-usage and video format standards.</p>
-</note>
-<note role="example">
-<p>Except in the case of PAL/M, the frame rate multiplier used for synchronizing with PAL
-formatted video objects at 25 frames per second is nominally 1:1.</p>
-</note>
-</div3>
-<div3 id="parameter-attribute-markerMode">
-<head>ttp:markerMode</head>
-<p>The <att>ttp:markerMode</att> attribute is used to specify
-constraints on the interpretation and use of time expressions
-that correspond with <bibref ref="smpte12m"/> time coordinates when operating
-with time base of <code>smpte</code> as defined by
-<specref ref="parameter-attribute-timeBase"/>.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-markerMode-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:markerMode</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:markerMode
-  : "continuous"
-  | "discontinuous"
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If the time base, defined by <specref
-ref="parameter-attribute-timeBase"/>, is designated as
-<code>smpte</code>, then this parameter applies as follows: if the
-parameter's value is <code>continuous</code>, then <bibref ref="smpte12m"/> time coordinates
-may be assumed to be linear and either monotonically increasing or
-decreasing; however, if <code>discontinuous</code>, then any assumption
-must not be made regarding linearity or monotonicity of time coordinates.</p>
-<p>If not specified, the value of this parameter must be considered
-to be <code>continuous</code>.</p>
-<p>A <att>ttp:markerMode</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-<p>If a value of <code>discontinuous</code> applies, then time
-expressions must not be converted to either media time or real time
-coordinates, arithmetical operators (addition, multiplication) are not
-defined on time expressions, and, consequently, any expression of a
-duration must be considered to be invalid.</p>
-<note role="explanation">
-<p>When operating with <code>smpte</code> time base and
-<code>discontinuous</code> marker mode, there is no effective time coordinate
-space; rather, all time expressions are interpreted as labeled
-synchronization events (markers), where some external synchronization
-context emits these events, which, when they correspond with time
-expressions that denote the same label, cause a temporal interval to
-begin or end accordingly.</p>
-<p>An additional side-effect of operating in <code>discontinuous</code>
-mode is that time expressions of children have no necessary
-relationship with time expressions of their temporal container; that
-is, temporal containers and children of these containers are
-temporally activated and inactivated independently based on the
-occurrence of a labeled synchronization (marker) event.</p>
-</note>
-<note role="explanation">
-<p>The notion of marker discontinuity as captured by this parameter
-is logically independent from the method used to count frames as
-expressed by the <att>ttp:dropMode</att> parameter. In particular,
-even if the <att>ttp:dropMode</att> parameter is specified as
-<code>dropNTSC</code> or <code>dropPAL</code>, the marker mode may be
-specified as <code>continuous</code>, even in the presence of frame count
-discontinuities induced by the frame counting method, unless there
-were some other non-linearity or discontinuity in marker labeling, for
-example, two consecutive frames labeled as <code>10:00:00:00</code>
-and <code>10:00:01:00</code>.
-</p>
-</note>
-</div3>
-<div3 id="parameter-attribute-pixelAspectRatio">
-<head>ttp:pixelAspectRatio</head>
-<p>The <att>ttp:pixelAspectRatio</att> attribute may be used by a content author
-to express the aspect ratio of non-square pixels in the production of content that
-makes use of pixel coordinates.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-pixelAspectRatio-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:pixelAspectRatio</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:pixelAspectRatio
-  : width height                            // <emph>width</emph> != 0; <emph>height</emph> != 0
-
-width | height
-  : <loc href="#style-value-digit">&lt;digit&gt;</loc>+
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If not specified, then square pixels (i.e., aspect ratio 1:1) must be assumed to apply.
-If specified, then both width and height must be non-zero.</p>
-<p>A <att>ttp:pixelAspectRatio</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-<note role="explanation">
-<p>This parameter may be used by a content transcoder or translator in
-order to convert pixel measurements between different pixel aspect
-ratios while still maintaining authorial layout intentions.</p>
-</note>
-</div3>
-<div3 id="parameter-attribute-profile">
-<head>ttp:profile</head>
-<p>The <att>ttp:profile</att> attribute may be used by a content author
-to express the profile of the Timed Text Markup Language (TTML) used
-in a document instance.</p>
-<p>If specified, the value of this attribute must adhere to the
-<code>xsd:anyURI</code> data type defined by <bibref ref="xsd-2"/>,
-&sect;3.2.17, and, further, must specify a
-profile designator in accordance with
-<specref ref="vocabulary-profiles"/>.</p>
-<p>A <att>ttp:profile</att>
-attribute is considered to be significant only when specified on the
-<el>tt</el> element.</p>
-</div3>
-<div3 id="parameter-attribute-subFrameRate">
-<head>ttp:subFrameRate</head>
-<p>The <att>ttp:subFrameRate</att> attribute is used to specify the sub-frame rate of a related
-media object or the intrinsic sub-frame rate of a document instance in case it is intended
-to function as an independent media object.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-subFrameRate-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:subFrameRate</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:subFrameRate
-  : <loc href="#style-value-digit">&lt;digit&gt;</loc>+                                // <emph>value</emph> > 0
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>The sub-frame rate that applies to a document instance is used to
-interpret time expressions that are expressed in <emph>sub-frames</emph>
-as defined by <specref ref="timing-value-timeExpression"/>.</p>
-<p>A sub-frame is interpreted as a division of a frame of media
-time, such that if the sub-frame rate is specified as <emph>S</emph>, then
-a frame of media time is divided into <emph>S</emph> intervals of
-equal duration, where each interval is labeled as sub-frame <emph>s</emph>,
-with <emph>s</emph> &isin; [0&hellip;<emph>S&minus;1</emph>].</p>
-<p>If not specified, the sub-frame rate must be considered to be
-equal to one (1). If specified, then the sub-frame rate must be greater than zero (0).</p>
-<p>A <att>ttp:subFrameRate</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-<note role="clarification">
-<p>The sub-frame is sometimes referred to as a <emph>field</emph> in
-the context of synchronization with an interlaced video media object.</p>
-</note>
-</div3>
-<div3 id="parameter-attribute-tickRate">
-<head>ttp:tickRate</head>
-<p>The <att>ttp:tickRate</att> attribute is used to specify the tick rate of a related
-media object or the intrinsic tick rate of content of a document instance in case it is intended
-to function as an independent media object.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-tickRate-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:tickRate</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:tickRate
-  : <loc href="#style-value-digit">&lt;digit&gt;</loc>+                                // <emph>value</emph> > 0
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>The tick rate that applies to a document instance is used to
-interpret time expressions that are expressed in <emph>ticks</emph> by
-using the <code>t</code> metric as defined by <specref
-ref="timing-value-timeExpression"/>.</p>
-<p>A tick is interpreted as an integral division of a second of media
-time, such that if the tick rate is specified as <emph>T</emph>, then
-a second of media time is divided into <emph>T</emph> intervals of
-equal duration, where each interval is labeled as tick <emph>t</emph>,
-with <emph>t</emph> &isin; [0&hellip;<emph>T&minus;1</emph>].</p>
-<p>If not specified, then if a frame rate is specified, the tick rate
-must be considered to be the effective frame rate multiplied by the
-sub-frame rate (i.e., ticks are interpreted as sub-frames); or, if no
-frame rate is specified, the tick rate must be considered to be one (1)
-tick per second of media time. If specified, then the tick rate
-must not be zero (0).</p>
-<note role="clarification">
-<p>There is no predefined relationship between ticks and frames or
-sub-frames. Ticks are an arbitrary division of seconds that permit
-use of fixed point arithmetic rather than fractional (and potentially
-inexact) expressions of seconds.</p>
-</note>
-<p>A <att>ttp:tickRate</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-</div3>
-<div3 id="parameter-attribute-timeBase">
-<head>ttp:timeBase</head>
-<p>The <att>ttp:timeBase</att> attribute is used to specify the
-temporal coordinate system by means of which time expressions are
-interpreted in a document instance.</p>
-<p>If specified, the value of this attribute must adhere to the following syntax:</p>
-<table id="parameter-attribute-timeBase-syntax" role="syntax">
-<caption>Syntax Representation &ndash; ttp:timeBase</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-ttp:timeBase
-  : "media"
-  | "smpte"
-  | "clock"
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If the time base is designated as <code>media</code>, then a time
-expression denotes a coordinate in some media object's time line,
-where the media object may be an external media object with which the
-content of a document instance is to be synchronized, or it may
-be the content of a document instance itself in a case where
-the timed text content is intended to establish an independent time
-line.</p>
-<note role="explanation">
-<p>When using a media time base, if that time base is paused or
-scaled positively or negatively, then it is expected that the
-presentation of associated Timed Text content will be similarly
-paused, accelerated, or decelerated, respectively. The means for
-controlling an external
-media time base is outside the scope of this specification.</p>
-</note>
-<p>If the time base is designated as <code>smpte</code>,
-then a time expression denotes a <bibref ref="smpte12m"/> time
-coordinate with which the content of a document instance is to
-be synchronized.  In this case, the value of the <att>ttp:markerMode</att> 
-and <att>ttp:dropMode</att> parameters apply, as defined by <specref
-ref="parameter-attribute-markerMode"/> and <specref
-ref="parameter-attribute-dropMode"/>, respectively.</p>
-<p>If the time base is designated as <code>clock</code>, then the time
-expression denotes a coordinate in some real-world time line as
-established by some real-time clock, such as the local wall-clock time
-or UTC (Coordinated Universal Time) or GPS (Global Positioning System)
-time lines.</p>
-<p>If not specified, the default time base must be considered to be
-<code>media</code>.</p>
-<p>A <att>ttp:timeBase</att> attribute is considered to be significant only
-when specified on the <el>tt</el> element.</p>
-<p>When operating with either <code>media</code> or <code>smpte</code>
-time bases, a diachronic presentation of a document instance may
-be subject to transformations of the controlling time line, such as
-temporal reversal, dilation (expansion), or constriction
-(compression); however, when operating with the <code>clock</code>
-time base, no transformations are permitted, and diachronic
-presentation proceeds on a linear, monotonically increasing time line
-based on the passage of real time.</p>
-<note role="example">
-<p>Due to there being only one time base parameter that applies to a
-given document instance, the interpretation of time expressions
-is uniform throughout the document instance.</p>
-</note>
-<p>When operating with the <code>clock</code> time base,
-the expression <emph>media time</emph> as used in this specification is
-to be interpreted as the real-time clock selected by
-<specref ref="parameter-attribute-clockMode"/>.</p>
-</div3>
-</div2>
-</div1>
-<div1 id="content">
-<head>Content</head>
-<p>This section specifies the <emph>content</emph> matter of the core
-vocabulary catalog.</p>
-<div2 id="content-element-vocabulary">
-<head>Content Element Vocabulary</head>
-<p>The following elements specify the structure and principal content aspects of a
-document instance:</p>
-<ulist>
-<item><p><specref ref="document-structure-vocabulary-tt"/></p></item>
-<item><p><specref ref="document-structure-vocabulary-head"/></p></item>
-<item><p><specref ref="document-structure-vocabulary-body"/></p></item>
-<item><p><specref ref="content-vocabulary-div"/></p></item>
-<item><p><specref ref="content-vocabulary-p"/></p></item>
-<item><p><specref ref="content-vocabulary-span"/></p></item>
-<item><p><specref ref="content-vocabulary-br"/></p></item>
-</ulist>
-<div3 id="document-structure-vocabulary-tt">
-<head>tt</head>
-<p>The <el>tt</el> element serves as the root document element of a document
-instance.</p>
-<p>The <el>tt</el> element accepts as its children zero or one <el>head</el> element followed by
-zero or one <el>body</el> element.</p>
-<table id="elt-syntax-tt" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: tt</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;tt
-  <loc href="#style-attribute-extent">tts:extent</loc> = string
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang"><phrase role="reqattr">xml:lang</phrase></loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>) : default
-  {<emph>any attribute in TT Parameter namespace</emph>}
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc href="#document-structure-vocabulary-head">head</loc>?, <loc href="#document-structure-vocabulary-body">body</loc>?
-&lt;/tt&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>The temporal beginning and ending of a document instance represented by a
-<el>tt</el> element is defined in relationship with some external
-application or presentation context. The temporal interval defined by
-these points is referred to subsequently as the <emph>external time interval</emph>.
-</p>
-<p>A document instance has an implicit duration that is equal to the
-implicit duration of the <el>body</el> element of the document, if present, or zero,
-if not present.</p>
-<p>If the <att>tts:extent</att> attribute is specified on the <el>tt</el>
-element, then it must adhere to <specref ref="style-attribute-extent"/>, in which case it
-specifies the spatial extent of the root container region in
-which content regions are located and presented. If no <att>tts:extent</att>
-attribute is specified, then the spatial extent of the root container region is
-considered to be determined by the external authoring or presentation
-context. The root container origin is determined by the external
-authoring context.</p>
-<p>An <att>xml:lang</att> attribute must be specified on the <el>tt</el> element.
-If the attribute value is empty, it signifies that there is no default language that applies
-to the text contained within the document instance.</p>
-<p>If no <att>xml:space</att> attribute is specified upon the <el>tt</el> element, then it must
-be considered as if the attribute had been specified with a value of <code>default</code>.</p>
-</div3>
-<div3 id="document-structure-vocabulary-head">
-<head>head</head>
-<p>The <el>head</el> element is a container element used to group
-header matter, including metadata,
-profile, styling, and layout information.</p>
-<p>The <el>head</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group,
-followed by zero or more elements in the
-<code>Parameters.class</code> element group,
-followed by zero or one <el>styling</el> element,
-followed by zero or one <el>layout</el> element.</p>
-<p>Any metadata specified by children in the <code>Metadata.class</code>
-element group applies semantically to the document instance as a
-whole, and not just the <el>head</el> element.</p>
-<p>Any parameters specified by children in the <code>Parameters.class</code>
-element group applies semantically to the document instance as a
-whole, and not just the <el>head</el> element.</p>
-<p>A <el>styling</el> child element is used to specify style constructs
-that are referenced from other style constructs, by layout constructs, and by
-content elements.</p>
-<p>A <el>layout</el> child element is used to specify layout constructs that
-are referenced by content elements.</p>
-<table id="elt-syntax-head" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: head</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;head
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang">xml:lang</loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#element-vocab-group-table">Parameters.class</loc>*, <loc href="#styling-vocabulary-styling">styling</loc>?, <loc href="#layout-vocabulary-layout">layout</loc>?
-&lt;/head&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>To the extent that time semantics apply to the content of the
-<el>head</el> element, the implied time interval of this element is
-defined to be coterminous with the external time interval.</p>
-</div3>
-<div3 id="document-structure-vocabulary-body">
-<head>body</head>
-<p>The <el>body</el> element functions as a logical container and a temporal
-structuring element for a sequence of textual content units represented as
-logical divisions.</p>
-<p>The <el>body</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group,
-followed by zero or more
-elements in the <code>Animation.class</code> element group,
-followed by
-zero or more <el>div</el> elements.</p>
-<p>Any metadata specified by children in the <code>Metadata.class</code>
-element group applies semantically to the <el>body</el> element and its descendants as a whole.</p>
-<p>Any animation elements specified by children in the <code>Animation.class</code>
-element group apply semantically to the <el>body</el> element.</p>
-<table id="elt-syntax-body" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: body</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;body
-  <loc href="#timing-attribute-begin">begin</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#timing-attribute-dur">dur</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#timing-attribute-end">end</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#layout-attribute-region">region</loc> = IDREF
-  <loc href="#style-attribute-style">style</loc> = IDREFS
-  <loc href="#timing-attribute-timeContainer">timeContainer</loc> = (<emph>par</emph>|<emph>seq</emph>)
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang">xml:lang</loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
-  {<emph>any attribute in TT Metadata namespace</emph>}
-  {<emph>any attribute in TT Style namespace</emph>}
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#element-vocab-group-table">Animation.class</loc>*, <loc href="#content-vocabulary-div">div</loc>*
-&lt;/body&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>An author may specify a temporal interval for a <el>body</el> element using
-the <att>begin</att>, <att>dur</att>, and <att>end</att> attributes. If the begin point
-of this interval remains unspecified, then the begin point is interpreted as the begin
-point of the external time interval. Similarly, if the end point of this interval remains unspecified, then the
-end point is interpreted as the end point of the external time interval.</p>
-<note role="explanation">
-<p>A TTML document instance referenced from a SMIL presentation
-is expected to follow the same timing rules as apply to other SMIL media
-objects.</p>
-</note>
-<p>If relative begin or end times are specified on the <el>body</el>
-element, then these times are resolved by reference to the begin and
-end time of the external time interval.</p>
-<p>If the external time interval is shorter than the computed duration of the
-<el>body</el> element, then the active time interval of a document instance is
-truncated to the active end point of the external time interval.</p>
-<p>An author may associate a set of style properties with a
-<el>body</el> element by means of either the <att>style</att>
-attribute or inline style attributes or a combination thereof.</p>
-<note role="explanation">
-<p>Style properties that are associated with a <el>body</el> element
-in a document instance are available for style inheritance by
-descendant content elements such as <el>div</el>, <el>p</el>,
-<el>span</el>
-and <el>br</el>.</p>
-</note>
-<p>If no <att>timeContainer</att> attribute is specified on a
-<el>body</el> element, then it must be interpreted as having
-<emph>parallel</emph>
-time containment semantics.</p>
-</div3>
-<div3 id="content-vocabulary-div">
-<head>div</head>
-<p>The <el>div</el> element functions as a logical container and a temporal
-structuring element for a sequence of textual content units represented as
-logical sub-divisions or paragraphs.</p>
-<note role="explanation">
-<p>When rendered on a continuous (non-paged) visual presentation medium,
-a <el>div</el> element is expected to generate
-one or more block
-areas
-that contain zero or more child block areas
-generated by the <el>div</el> element's
-descendant
-<el>p</el> elements.
-</p>
-<p>If some
-block area generated by a <el>div</el> element does
-not contain any child areas, then it is not expected to be presented.</p>
-</note>
-<p>The <el>div</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group,
-followed by zero or more
-elements in the <code>Animation.class</code> element group,
-followed by
-zero or more
-<el>div</el> or 
-<el>p</el> elements.</p>
-<p>Any metadata specified by children in the <code>Metadata.class</code>
-element group applies semantically to the <el>div</el> element and its descendants as a whole.</p>
-<p>Any animation elements specified by children in the <code>Animation.class</code>
-element group apply semantically to the <el>div</el> element.</p>
-<table id="elt-syntax-div" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: div</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;div
-  <loc href="#timing-attribute-begin">begin</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#timing-attribute-dur">dur</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#timing-attribute-end">end</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#layout-attribute-region">region</loc> = IDREF
-  <loc href="#style-attribute-style">style</loc> = IDREFS
-  <loc href="#timing-attribute-timeContainer">timeContainer</loc> = (<emph>par</emph>|<emph>seq</emph>)
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang">xml:lang</loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
-  {<emph>any attribute in TT Metadata namespace</emph>}
-  {<emph>any attribute in TT Style namespace</emph>}
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc
-  href="#element-vocab-group-table">Metadata.class</loc>*, <loc
-  href="#element-vocab-group-table">Animation.class</loc>*, <loc
-  href="#element-vocab-group-table">Block.class</loc>*
-&lt;/div&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>An author may associate a set of style properties with a <el>div</el> element by means of either
-the <att>style</att> attribute or inline style attributes or a combination thereof.</p>
-<note role="explanation">
-<p>Style properties that are associated
-with
-a <el>div</el> element in a document instance
-are available for style inheritance by descendant content elements such as
-<el>div</el>, 
-<el>p</el>,
-<el>span</el>, and
-<el>br</el>.</p>
-</note>
-<p>If no <att>timeContainer</att> attribute is specified on
-a <el>div</el> element, then it must be interpreted as having
-<emph>parallel</emph> time containment semantics.</p>
-</div3>
-<div3 id="content-vocabulary-p">
-<head>p</head>
-<p>A <el>p</el> element represents a logical paragraph, serving as
-a transition between block level and inline level formatting semantics.</p>
-<p>The <el>p</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group,
-followed by zero or more
-elements in the <code>Animation.class</code> element group,
-followed by
-zero or more
-<code>span</code> element,
-<code>br</code> element,
-or text nodes interpreted as anonymous spans.</p>
-<p>Any metadata specified by children in the <code>Metadata.class</code>
-element group applies semantically to the <el>p</el> element and its descendants as a whole.</p>
-<p>Any animation elements specified by children in the <code>Animation.class</code>
-element group apply semantically to the <el>p</el> element.</p>
-<table id="elt-syntax-p" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: p</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;p
-  <loc href="#timing-attribute-begin">begin</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#timing-attribute-dur">dur</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#timing-attribute-end">end</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#layout-attribute-region">region</loc> = IDREF
-  <loc href="#style-attribute-style">style</loc> = IDREFS
-  <loc href="#timing-attribute-timeContainer">timeContainer</loc> = (<emph>par</emph>|<emph>seq</emph>)
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang">xml:lang</loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
-  {<emph>any attribute in TT Metadata namespace</emph>}
-  {<emph>any attribute in TT Style namespace</emph>}
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc
-  href="#element-vocab-group-table">Metadata.class</loc>*, <loc
-  href="#element-vocab-group-table">Animation.class</loc>*, <loc
-  href="#element-vocab-group-table">Inline.class</loc>*
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>An author may associate a set of style properties with a
-<el>p</el> element by means of either the <att>style</att>
-attribute or inline style attributes or a combination thereof.</p>
-<note role="explanation">
-<p>Style properties that are associated with a <el>p</el> element
-in a document instance are available for style inheritance by
-descendant content elements such as <el>span</el> and
-<el>br</el>.</p>
-</note>
-<p>If no <att>timeContainer</att> attribute is specified on
-a <el>p</el> element, then it must be interpreted as having
-<emph>parallel</emph> time containment semantics.</p>
-<p>If a sequence of children of a <el>p</el> element
-consists solely of character information items, then that sequence must
-be considered to be an <emph>anonymous span</emph> for the purpose of
-applying style properties that apply to <el>span</el> elements.</p>
-</div3>
-<div3 id="content-vocabulary-span">
-<head>span</head>
-<p>The <el>span</el> element functions as a logical container and a temporal
-structuring element for a sequence of textual content units having inline
-level formatting semantics.</p>
-<p>When presented on a visual medium, a <el>span</el> element is intended to
-generate a sequence of inline areas, each containing one or more glyph areas.</p>
-<p>The <el>span</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group,
-followed by zero or more
-elements in the <code>Animation.class</code> element group,
-followed by
-zero or more
-<el>span</el> elements,
-<el>br</el> elements,
-or text nodes interpreted as anonymous spans.</p>
-<p>Any metadata specified by children in the <code>Metadata.class</code>
-element group applies semantically to the <el>span</el> element and its descendants as a whole.</p>
-<p>Any animation elements specified by children in the <code>Animation.class</code>
-element group apply semantically to the <el>span</el> element.</p>
-<table id="elt-syntax-span" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: span</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;span
-  <loc href="#timing-attribute-begin">begin</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#timing-attribute-dur">dur</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#timing-attribute-end">end</loc> = <loc href="#timing-value-timeExpression">&lt;timeExpression&gt;</loc>
-  <loc href="#layout-attribute-region">region</loc> = IDREF
-  <loc href="#style-attribute-style">style</loc> = IDREFS
-  <loc href="#timing-attribute-timeContainer">timeContainer</loc> = (<emph>par</emph>|<emph>seq</emph>)
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang">xml:lang</loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
-  {<emph>any attribute in TT Metadata namespace</emph>}
-  {<emph>any attribute in TT Style namespace</emph>}
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc
-  href="#element-vocab-group-table">Metadata.class</loc>*, <loc
-  href="#element-vocab-group-table">Animation.class</loc>*, <loc
-  href="#element-vocab-group-table">Inline.class</loc>*
-&lt;/span&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>An author may associate a set of style properties with a
-<el>span</el> element by means of either the <att>style</att>
-attribute or inline style attributes or a combination thereof.</p>
-<note role="explanation">
-<p>Style properties that are associated with a <el>span</el> element
-in a document instance are available for style inheritance by
-descendant content elements such as <el>span</el> and
-<el>br</el>.</p>
-</note>
-<p>If no <att>timeContainer</att> attribute is specified on
-a <el>span</el> element, then it must be interpreted as having
-<emph>parallel</emph> time containment semantics.</p>
-</div3>
-<div3 id="content-vocabulary-br">
-<head>br</head>
-<p>The <el>br</el> element denotes an explicit line break.</p>
-<table id="elt-syntax-br" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: br</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;br
-  <loc href="#style-attribute-style">style</loc> = IDREFS
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang">xml:lang</loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
-  {<emph>any attribute in TT Metadata namespace</emph>}
-  {<emph>any attribute in TT Style namespace</emph>}
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#element-vocab-group-table">Animation.class</loc>*
-&lt;/br&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>When presented on a visual medium, the presence of a <el>br</el> element must be
-interpreted as a forced line break.</p>
-<note>
-<p>The visual presentation of a <el>br</el> element is
-intended to produce the same effect as the ASCII control code
-<code>CR</code>
-followed by the control code <code>NL</code> when presented on a teletype device.
-Therefore, two <el>br</el> elements in sequence will produce a
-different effect than a single <el>br</el> element.</p>
-</note>
-</div3>
-</div2>
-<div2 id="content-attribute-vocabulary">
-<head>Content Attribute Vocabulary</head>
-<p>This section defines the following common attributes used with many or all element types
-in the core vocabulary catalog:</p>
-<ulist>
-<item><p><specref ref="content-attribute-id"/></p></item>
-<item><p><specref ref="content-attribute-lang"/></p></item>
-<item><p><specref ref="content-attribute-space"/></p></item>
-</ulist>
-<div3 id="content-attribute-id">
-<head>xml:id</head>
-<p>The <att>xml:id</att> attribute is used as defined by
-<bibref ref="xmlid"/>.</p>
-<p>The <att>xml:id</att> attribute may be used with any element in the
-core vocabulary catalog.</p>
-</div3>
-<div3 id="content-attribute-lang">
-<head>xml:lang</head>
-<p>The <att>xml:lang</att> attribute is used as defined by
-<bibref ref="xml10"/>, &sect;2.12, <emph>Language Identification</emph>.</p>
-<p>The <att>xml:lang</att> attribute must be specified on the <el>tt</el>
-element and may be specified by an instance of any other element type
-in the core vocabulary catalog.</p>
-</div3>
-<div3 id="content-attribute-space">
-<head>xml:space</head>
-<p>The <att>xml:space</att> attribute is used as defined by
-<bibref ref="xml10"/>, &sect;2.10, <emph>White Space Handling</emph>.</p>
-<p>The <att>xml:space</att> attribute may be used with any element in
-the core vocabulary catalog.</p>
-<!-- OLD DEFINITION
-<p>The semantics of the value <code>default</code> are fixed to mean that
-white space that appears in element content as defined by <bibref
-ref="xml10"/>, &sect;3.2.1, must be normalized at the
-application layer during subsequent processing, such as presentation or
-transformation processing, as follows:</p>
-<olist>
-<item><p>replace each TAB character (<code>&amp;#x0009;</code>) and NEWLINE character (<code>&amp;#x000A;</code>) with a SPACE
-character (<code>&amp;#x0020;</code>);</p></item>
-<item><p>replace each sequence of two or more SPACE characters with a
-single SPACE character;</p></item>
-<item><p>for every maximum sequence of sibling character information
-items, if there is a leading or trailing SPACE character in the
-sequence, then remove the character.</p></item>
-</olist>
--->
-<!-- NEW DEFINITION -->
-<p>The semantics of the value <code>default</code> are fixed to mean that
-when performing presentation processing of a document instance as
-described by <specref ref="semantics-region-layout-step-2"/>,
-processing must occur as
-if the following properties were specified on the affected
-<!-- changed for future CSS compatibility
-elements of the intermediate XSL-FO document:</p> 
--->
-elements of an equivalent intermediate XSL-FO document:</p>
-<ulist>
-<item>
-<p><code>suppress-at-line-break="auto"</code></p>
-</item>
-<item>
-<p><code>linefeed-treatment="treat-as-space"</code></p>
-</item>
-<item>
-<p><code>white-space-collapse="true"</code></p>
-</item>
-<item>
-<p><code>white-space-treatment="ignore-if-surrounding-linefeed"</code></p>
-</item>
-</ulist>
-<p>Similarly, the semantics of the value <code>preserve</code> are fixed to mean that
-when performing presentation processing, processing must occur as
-if the following properties were specified on the affected
-<!-- changed for future CSS compatibility
-elements of the intermediate XSL-FO document:</p> 
--->
-elements of an equivalent intermediate XSL-FO document:
-</p>
-<ulist>
-<item>
-<p><code>suppress-at-line-break="retain"</code></p>
-</item>
-<item>
-<p><code>linefeed-treatment="preserve"</code></p>
-</item>
-<item>
-<p><code>white-space-collapse="false"</code></p>
-</item>
-<item>
-<p><code>white-space-treatment="preserve"</code></p>
-</item>
-</ulist>
-<p>When performing other types of processing intended to eventually
-result in a visual presentation by means other than those described
-in this specification, the semantics of space collapsing and
-preservation as described above should be respected. For other types
-of processing, the treatment of the <att>xml:space</att> attribute
-is processor dependent, but should respect the semantics described
-above if possible.</p>
-</div3>
-</div2>
-</div1>
-<div1 id="styling">
-<head>Styling</head>
-<p>This section specifies the <emph>styling</emph> matter of the core
-vocabulary catalog, where
-styling is to be understood as a separable layer of information that applies to
-content and that denotes authorial intentions about the presentation of
-that content.</p>
-  <!-- added for future CSS compatibility -->
-  <p>
-    Styling attributes are included in TTML to enable authorial intent of presentation
-    to be included within a self-contained document. This section describes
-    the semantics of style presentation in terms of a standard processing
-    model. TTML Processors are not required to present TTML documents in any particular way; 
-    but an implementation of this model by a TTML Presentation Processor
-    that provides externally observable results that are consistent with this model is
-    likely to lead to a user experience that closely resembles the experience intended by
-    the documents' authors.
-  </p>
-  <p>
-    The semantics of TTML style presentation are described in terms of the model 
-    in <bibref ref="xsl11"/>. The intended effect of the attributes in this section 
-    are to be compatible with  the layout model of XSL. Presentation agents may however 
-    use any technology to satisfy the authorial intent of the document. In particular 
-    since <bibref ref="css2"/> is a subset of this model, a CSS processor may be used 
-    for the features that the models have in common.
-  </p>
-  <!-- end addition -->
-  <p>No normative use of an
-<code>&lt;?xml-stylesheet ... ?&gt;</code> processing instruction is defined
-by this specification.</p>
-<div2 id="styling-element-vocabulary">
-<head>Styling Element Vocabulary</head>
-<p>The following elements specify the structure and principal styling aspects of a
-document instance:</p>
-<ulist>
-<item><p><specref ref="styling-vocabulary-styling"/></p></item>
-<item><p><specref ref="styling-vocabulary-style"/></p></item>
-</ulist>
-<div3 id="styling-vocabulary-styling">
-<head>styling</head>
-<p>The <el>styling</el> element is a container element used to group
-styling matter, including metadata that applies to styling matter.</p>
-<p>The <el>styling</el> element accepts as its children zero or more
-elements in the <code>Metadata.class</code> element group, followed by
-zero or more <el>style</el> elements.</p>
-<table id="elt-syntax-styling" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: styling</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;styling
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang">xml:lang</loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*, <loc href="#styling-vocabulary-style">style</loc>*
-&lt;/styling&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>To the extent that time semantics apply to the content of the
-<el>styling</el> element, the implied time interval of this element is
-defined to be coterminous with the external time interval.</p>
-</div3>
-<div3 id="styling-vocabulary-style">
-<head>style</head>
-<p>The <el>style</el> element is used to define
-a set of style specifications expressed as a
-specified style set in accordance with
-<specref ref="semantics-style-resolution-processing-sss"/>.</p>
-<p>The <el>style</el> element accepts as its children zero or more <el>metadata</el> elements.</p>
-<table id="elt-syntax-style" role="syntax">
-<caption>XML Representation &ndash; Element Information Item: style</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;style
-  <loc href="#style-attribute-style">style</loc> = IDREFS
-  <loc href="#content-attribute-id">xml:id</loc> = ID
-  <loc href="#content-attribute-lang">xml:lang</loc> = string
-  <loc href="#content-attribute-space">xml:space</loc> = (<emph>default</emph>|<emph>preserve</emph>)
-  {<emph>any attribute in TT Style namespace</emph>}
-  {<emph>any attribute not in default or any TT namespace</emph>}&gt;
-  <!-- change for future CSS compatibility
-  <emph>Content:</emph> <loc href="#element-vocab-group-table">Metadata.class</loc>*
-  -->
-  <emph>Content:</emph> EMPTY
-&lt;/style&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>If a <el>style</el> element appears as a descendant of a
-<el>region</el> element, then the <el>style</el> element must be
-ignored for the purpose of computing referential styles as defined by
-<specref ref="semantics-style-association-referential"/> and <specref
-ref="semantics-style-association-chained-referential"/>.</p>
-<note role="explanation">
-<p>That is to say, when referential styling is used by an element to
-refer to a <el>style</el> element, then the referenced <el>style</el>
-element must appear as a descendant of the <el>styling</el> element, and
-not in any other context.</p>
-</note>
-</div3>
-</div2>
-<div2 id="styling-attribute-vocabulary">
-<head>Styling Attribute Vocabulary</head>
-<p>This section defines the <specref ref="style-attribute-style"/> attribute used
-with both style definition elements as well as content elements.</p>
-<p>In addition, this section specifies the following attributes in the TT Style Namespace
-for use with style definition elements, certain layout elements, and content elements
-that support inline style specifications:</p>
-<ulist>
-<item><p><specref ref="style-attribute-backgroundColor"/></p></item>
-<item><p><specref ref="style-attribute-color"/></p></item>
-<item><p><specref ref="style-attribute-direction"/></p></item>
-<item><p><specref ref="style-attribute-display"/></p></item>
-<item><p><specref ref="style-attribute-displayAlign"/></p></item>
-<item><p><specref ref="style-attribute-extent"/></p></item>
-<item><p><specref ref="style-attribute-fontFamily"/></p></item>
-<item><p><specref ref="style-attribute-fontSize"/></p></item>
-<item><p><specref ref="style-attribute-fontStyle"/></p></item>
-<item><p><specref ref="style-attribute-fontWeight"/></p></item>
-<item><p><specref ref="style-attribute-lineHeight"/></p></item>
-<item><p><specref ref="style-attribute-opacity"/></p></item>
-<item><p><specref ref="style-attribute-origin"/></p></item>
-<item><p><specref ref="style-attribute-overflow"/></p></item>
-<item><p><specref ref="style-attribute-padding"/></p></item>
-<item><p><specref ref="style-attribute-showBackground"/></p></item>
-<item><p><specref ref="style-attribute-textAlign"/></p></item>
-<item><p><specref ref="style-attribute-textDecoration"/></p></item>
-<item><p><specref ref="style-attribute-textOutline"/></p></item>
-<item><p><specref ref="style-attribute-unicodeBidi"/></p></item>
-<item><p><specref ref="style-attribute-visibility"/></p></item>
-<item><p><specref ref="style-attribute-wrapOption"/></p></item>
-<item><p><specref ref="style-attribute-writingMode"/></p></item>
-<item><p><specref ref="style-attribute-zIndex"/></p></item>
-</ulist>
-<p>Unless explicitly stated otherwise, linear white-space (LWSP) may
-appear between tokens of a value of a TT
-Style or TT Style Extension
-Property.</p>
-<note role="explanation">
-<p>This specification makes use of <emph>lowerCamelCased</emph> local
-names for style attributes that
-are based upon like-named properties defined by <bibref ref="xsl11"/>.
-This convention is likewise extended to token values of such
-properties.</p>
-</note>
-<note role="clarification">
-<p>A style property may be expressed as a specified attribute on any content
-element type independently of whether the property applies to that
-element type. This capability permits the expression of an inheritable
-style property on ancestor elements to which the property
-does not apply.</p>
-</note>
-<div3 id="style-attribute-style">
-<head>style</head>
-<p>The <att>style</att> attribute is used
-by referential style association
-to reference one or more <el>style</el>
-elements each of which define a
-specified
-style set.</p>
-<p>The <att>style</att> attribute may be specified by an instance of the following
-element types:</p>
-<ulist>
-<item><p><loc href="#document-structure-vocabulary-body"><el>body</el></loc></p></item>
-<item><p><loc href="#content-vocabulary-div"><el>div</el></loc></p></item>
-<item><p><loc href="#content-vocabulary-p"><el>p</el></loc></p></item>
-<item><p><loc href="#layout-vocabulary-region"><el>region</el></loc></p></item>
-<item><p><loc href="#content-vocabulary-span"><el>span</el></loc></p></item>
-<item><p><loc href="#styling-vocabulary-style"><el>style</el></loc></p></item>
-</ulist>
-<note role="usage">
-<p>See the specific element type definitions that permit use of the
-<att>style</att> attribute, as well as <specref
-ref="semantics-style-association-referential"/> and <specref
-ref="semantics-style-association-chained-referential"/>, for
-further information on its semantics.</p>
-</note>
-</div3>
-<div3 id="style-attribute-backgroundColor">
-<head>tts:backgroundColor</head>
-<p>The <att>tts:backgroundColor</att> attribute is used to specify a style property that
-defines the background color of a region or an area generated by content flowed into a region.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-backgroundColor" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<loc href="#style-value-color">&lt;color&gt;</loc>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>transparent</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#document-structure-vocabulary-body"><el>body</el></loc>,
-<loc href="#content-vocabulary-div"><el>div</el></loc>,
-<loc href="#content-vocabulary-p"><el>p</el></loc>,
-<loc href="#layout-vocabulary-region"><el>region</el></loc>,
-<loc href="#content-vocabulary-span"><el>span</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>The <att>tts:backgroundColor</att> style is illustrated by the following example.</p>
-<table id="style-attribute-backgroundColor-example-1" role="example">
-<caption>Example Fragment &ndash; Background Color</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="306px 114px"/&gt;
-  &lt;style <phrase role="strong">tts:backgroundColor="red"</phrase>/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="after"/&gt;
-  &lt;style tts:padding="3px 40px"/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1" <phrase role="strong">tts:backgroundColor="purple"</phrase> tts:textAlign="center"&gt;
-  Twinkle, twinkle, little bat!&lt;br/&gt;
-  How &lt;span <phrase role="strong">tts:backgroundColor="green"</phrase>&gt;I wonder&lt;/span&gt; where you're at!
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-backgroundColor-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Background Color</caption>
-<tbody>
-<tr>
-<td><graphic source="images/backgroundColor.png" alt="TTML backgroundColor style property"/></td>
-</tr>
-</tbody>
-</table>
-  <!-- CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property represented by this attribute are based upon 
-that defined by <bibref ref="xsl11"/>, &sect; 7.8.2.</p>
-</note> -->
-  
-</div3>
-<div3 id="style-attribute-color">
-<head>tts:color</head>
-<p>The <att>tts:color</att> attribute is used to specify a style property that
-defines the foreground color of marks associated with an area generated by content flowed into a region.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-color" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<loc href="#style-value-color">&lt;color&gt;</loc>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td>see prose</td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#content-vocabulary-span"><el>span</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>The initial value of the <att>tts:color</att> property
-is considered to be implementation dependent. In the absence of
-end-user preference information, a conformant presentation processor
-should use an initial value that is highly contrastive to the
-background color of the root container region.</p>
-<p>The <att>tts:color</att> style is illustrated by the following example.</p>
-<table id="style-attribute-color-example-1" role="example">
-<caption>Example Fragment &ndash; Color</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style <phrase role="strong">tts:color="white"</phrase>/&gt;
-  &lt;style tts:displayAlign="after"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  In spring, when woods are &lt;span <phrase role="strong">tts:color="green"</phrase>&gt;getting green&lt;/span&gt;,&lt;br/&gt;
-  I'll try and tell you what I mean.
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-color-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Color</caption>
-<tbody>
-<tr>
-<td><graphic source="images/color.png" alt="TTML color style property"/></td>
-</tr>
-</tbody>
-</table>
-  <!-- CSS compatibility - remove derivation note 
-  <note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.18.1.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-direction">
-<head>tts:direction</head>
-<p>The <att>tts:direction</att> attribute is used to specify a style property that
-defines the directionality of an embedding or override according to
-the Unicode bidirectional algorithm.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-direction" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>ltr</code> |
-<code>rtl</code>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td>
-<code>ltr</code>
-</td>
-</tr>
-<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>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must ignore the attribute.</p>
-<p>The <att>tts:direction</att> style is illustrated by the following example.</p>
-<table id="style-attribute-direction-example-1" role="example">
-<caption>Example Fragment &ndash; Direction</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="265px 84px"/&gt;
-  &lt;style tts:padding="5px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="after"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  Little birds are playing&lt;br/&gt;
-  Bagpipes on the shore,&lt;br/&gt;
-  &lt;span tts:unicodeBidi="bidiOverride" <phrase role="strong">tts:direction="rtl"</phrase>&gt;where the tourists snore.&lt;/span&gt;
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-direction-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Direction</caption>
-<tbody>
-<tr>
-<td>
-<graphic source="images/direction.png" alt="TTML direction style property"/>
-</td>
-</tr>
-</tbody>
-</table>
-  <!-- CSS compatibility - remove derivation note 
-  <note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.29.1.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-display">
-<head>tts:display</head>
-<p>The <att>tts:display</att> attribute is used to specify a style property that
-defines whether an element is a candidate for layout and composition
-in a region.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-display" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>auto</code> |
-<code>none</code>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td>
-<code>auto</code>
-</td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#document-structure-vocabulary-body"><el>body</el></loc>,
-<loc href="#content-vocabulary-div"><el>div</el></loc>,
-<loc href="#content-vocabulary-p"><el>p</el></loc>,
-<loc href="#layout-vocabulary-region"><el>region</el></loc>,
-<loc href="#content-vocabulary-span"><el>span</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>If the value of this attribute is <code>auto</code>,
-then the affected element is a candidate for region layout and
-presentation; however, if the value is <code>none</code>, then the
-affected element and its descendants must be considered ineligible for region
-layout and presentation.</p>
-<p>The <att>tts:display</att> style is illustrated by the following example.</p>
-<table id="style-attribute-display-example-1" role="example">
-<caption>Example Fragment &ndash; Display</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="369px 119px"
-            tts:backgroundColor="black"
-            tts:color="white"
-            tts:displayAlign="before"
-            tts:textAlign="start"/&gt;
-&lt;/region&gt;
-...
-&lt;div region="r1"&gt;
-  &lt;p dur="5s"&gt;
-    [[[
-    &lt;span <phrase role="strong">tts:display="none"</phrase>&gt;
-      &lt;set begin="1s" dur="1s" <phrase role="strong">tts:display="auto"</phrase>/&gt;
-      Beautiful soup,
-    &lt;/span&gt;
-    &lt;span <phrase role="strong">tts:display="none"</phrase>&gt;
-      &lt;set begin="2s" dur="1s" <phrase role="strong">tts:display="auto"</phrase>/&gt;
-      so rich and green,
-    &lt;/span&gt;
-    &lt;span <phrase role="strong">tts:display="none"</phrase>&gt;
-      &lt;set begin="3s" dur="1s" <phrase role="strong">tts:display="auto"</phrase>/&gt;
-      waiting in a hot tureen!
-    &lt;/span&gt;
-    ]]]
-  &lt;/p&gt;
-&lt;/div&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-display-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Display</caption>
-<tbody>
-<tr>
-<td>
-<graphic source="images/display_0.png" alt="TTML display style property - [0,1)"/>
-</td>
-</tr>
-<tr>
-<td>
-<graphic source="images/display_1.png" alt="TTML display style property - [1,2)"/>
-</td>
-</tr>
-<tr>
-<td>
-<graphic source="images/display_2.png" alt="TTML display style property - [2,3)"/>
-</td>
-</tr>
-<tr>
-<td>
-<graphic source="images/display_3.png" alt="TTML display style property - [3,4)"/>
-</td>
-</tr>
-<tr>
-<td>
-<graphic source="images/display_4.png" alt="TTML display style property - [4,5)"/>
-</td>
-</tr>
-</tbody>
-</table>
-  <!-- CSS compatibility - remove derivation note 
-  <note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref
-ref="css2"/>,
-&sect; 9.2.5.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-displayAlign">
-<head>tts:displayAlign</head>
-<p>The <att>tts:displayAlign</att> attribute is used to specify a style property that
-defines the alignment of block areas in the block progression direction.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-displayAlign" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>before</code> |
-<code>center</code> |
-<code>after</code>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td>
-<code>before</code>
-</td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#layout-vocabulary-region"><el>region</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>before</code> were specified.</p>
-<p>The <att>tts:displayAlign</att> style is illustrated by the following example.</p>
-<table id="style-attribute-displayAlign-example-1" role="example">
-<caption>Example Fragment &ndash; Display Align</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="128px 66px" tts:origin="0px 0px"
-       tts:backgroundColor="black" tts:color="white"/&gt;
-  &lt;style <phrase role="strong">tts:displayAlign="before"</phrase>/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-&lt;/region&gt;
-&lt;region xml:id="r2"&gt;
-  &lt;style tts:extent="192px 66px" tts:origin="128px 66px"/&gt;
-       tts:backgroundColor="green" tts:color="white"/&gt;
-  &lt;style <phrase role="strong">tts:displayAlign="after"</phrase>/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-&lt;/region&gt;
-&lt;region xml:id="r3"&gt;
-  &lt;style tts:extent="128px 66px"/&gt; style tts:origin="0px 132px"
-       tts:backgroundColor="black" tts:color="white"/&gt;
-  &lt;style <phrase role="strong">tts:displayAlign="before"</phrase>/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-&lt;/region&gt;
-&lt;region xml:id="r4"&gt;
-  &lt;style tts:extent="192px 66px" tts:origin="128px 198px"/&gt;
-       tts:backgroundColor="green" tts:color="white"/&gt;
-  &lt;style <phrase role="strong">tts:displayAlign="after"</phrase>/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-&lt;/region&gt;
-...
-&lt;div&gt;
-  &lt;p region="r1"&gt;I sent a message to the fish:&lt;/p&gt;
-  &lt;p region="r2"&gt;I told them&lt;br/&gt; "This is what I wish."&lt;/p&gt;
-  &lt;p region="r3"&gt;The little fishes of the sea,&lt;/p&gt;
-  &lt;p region="r4"&gt;They sent an&lt;br/&gt; answer back to me.&lt;/p&gt;
-&lt;/div&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-displayAlign-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Display Align</caption>
-<tbody>
-<tr>
-<td><graphic source="images/displayAlign.png" alt="TTML displayAlign style property"/></td>
-</tr>
-</tbody>
-</table>
-<!-- CSS compatibility - remove derivation note   
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.14.4.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-extent">
-<head>tts:extent</head>
-<p>The <att>tts:extent</att> attribute is used to specify the
-<emph>width</emph> and <emph>height</emph> of a region area
-(which may be the root container region).</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-extent" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>auto</code> |
-<loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>auto</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#document-structure-vocabulary-tt"><el>tt</el></loc>,
-<loc href="#layout-vocabulary-region"><el>region</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>relative to width and height of root container region</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If the value of this attribute consists of two <loc href="#style-value-length">&lt;length&gt;</loc>
-specifications, then they must be interpreted as <emph>width</emph>
-and <emph>height</emph>, where the first specification is the
-<emph>width</emph>, and the second specification is the
-<emph>height</emph>.</p>
-<p>If the value of this attribute is <code>auto</code>, then the initial value
-of the style property must be considered to be the same as the root container extent.
-</p>
-<p>
-The root container extent is determined either by a
-<att>tts:extent</att> specified on the <el>tt</el> element, if
-present, or by the external authoring context, if not present.
-If
-<att>tts:extent</att> is specified on the <el>tt</el> element,
-then
-the width and height
-must be
-expressed in terms of two
-<loc href="#style-value-length">&lt;length&gt;</loc> specifications,
-and
-these specifications must be expressed as non-percentage,
-definite lengths using pixel units.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>auto</code> were specified.</p>
-<p>The <att>tts:extent</att> style is illustrated by the following example.</p>
-<table id="style-attribute-extent-example-1" role="example">
-<caption>Example Fragment &ndash; Extent</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style <phrase role="strong">tts:extent="330px 122px"</phrase>/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="after"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  'Tis the voice of the Lobster:&lt;br/&gt;
-  I heard him declare,&lt;br/&gt;
-  "You have baked me too brown,&lt;br/&gt;
-  I must sugar my hair."
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-extent-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Extent</caption>
-<tbody>
-<tr>
-<td><graphic source="images/extent.png" alt="TTML extent style property"/></td>
-</tr>
-</tbody>
-</table>
-</div3>
-<div3 id="style-attribute-fontFamily">
-<head>tts:fontFamily</head>
-<p>The <att>tts:fontFamily</att> attribute is used to specify a style property that
-defines the font family from which glyphs are selected for glyph areas generated
-by content flowed into a region.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-fontFamily" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-(<loc href="#style-value-familyName">&lt;familyName&gt;</loc> | <loc href="#style-value-genericFamilyName">&lt;genericFamilyName&gt;</loc>)
-(<code>","</code>
-&nbsp;(<loc href="#style-value-familyName">&lt;familyName&gt;</loc> | <loc href="#style-value-genericFamilyName">&lt;genericFamilyName&gt;</loc>))*
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>default</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#content-vocabulary-span"><el>span</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<note role="clarification">
-<p>The initial value, <code>default</code>, is a generic font family name, and is
-further described in <specref ref="style-value-genericFamilyName"/> below.</p>
-</note>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>If a specified font family is not available, then a
-presentation processor must attempt to map the specified font family
-to an available font family that has similar typographic
-characteristics, or, in the absence of such a mapping, it must
-interpret the font family as if the value <code>default</code> were
-specified.</p>
-<p>The <att>tts:fontFamily</att> style is illustrated by the following example.</p>
-<table id="style-attribute-fontFamily-example-1" role="example">
-<caption>Example Fragment &ndash; Font Family</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="474px 146px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="center"/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-  &lt;style <phrase role="strong">tts:fontFamily="proportionalSansSerif"</phrase>/&gt;
-&lt;/region&gt;
-...
-&lt;div region="r1"&gt;
-  &lt;p&gt;
-    "The time has come," the Walrus said,&lt;br/&gt;
-    "to talk of many things:
-  &lt;/p&gt;
-  &lt;p tts:textAlign="end" <phrase role="strong">tts:fontFamily="monospaceSerif"</phrase>&gt;
-    Of shoes, and ships, and sealing wax,&lt;br/&gt;
-    Of cabbages and kings,
-  &lt;/p&gt;
-  &lt;p&gt;
-    And why the sea is boiling hot,&lt;br/&gt;
-    and whether pigs have wings."
-  &lt;/p&gt;
-&lt;/div&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-fontFamily-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Font Family</caption>
-<tbody>
-<tr>
-<td><graphic source="images/fontFamily.png" alt="TTML fontFamily style property"/></td>
-</tr>
-</tbody>
-</table>
-<!--CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.9.2.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-fontSize">
-<head>tts:fontSize</head>
-<p>The <att>tts:fontSize</att> attribute is used to specify a style property
-that defines the font size for glyphs that are selected for glyph areas
-generated by content flowed into a region, where font size is interpreted as a
-scaling transform to the font's design EM square.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-fontSize" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc>?
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>1c</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#content-vocabulary-span"><el>span</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>relative to parent element's font size</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If a single <loc href="#style-value-length">&lt;length&gt;</loc> value is specified, then this length applies
-equally to horizontal and vertical scaling of a glyph's EM square; if two
-<loc href="#style-value-length">&lt;length&gt;</loc> values are specified, then the first expresses the horizontal
-scaling and the second expresses vertical scaling.</p>
-<note role="example">
-<p>Use of independent horizontal and vertical font sizes is expected to be used
-with cell based units in order to denote fonts that are two rows in height and
-one column in width.</p>
-</note>
-<p>If horizontal and vertical sizes are expressed independently, then the
-units of the <loc href="#style-value-length">&lt;length&gt;</loc> values must be the same.</p>
-<p>The <loc href="#style-value-length">&lt;length&gt;</loc> value(s) used to express font size must be non-negative.</p>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>1c</code> were specified.</p>
-<note role="elaboration">
-<p>The expression <code>1c</code> means one cell, where <code>'c'</code> expresses
-the <emph>cell</emph> length unit as defined by <specref ref="style-value-length"/>.</p>
-</note>
-<p>The <att>tts:fontSize</att> style is illustrated by the following example.</p>
-<table id="style-attribute-fontSize-example-1" role="example">
-<caption>Example Fragment &ndash; Font Size</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="299px 97px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="center"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-  &lt;style tts:fontFamily="proportionalSansSerif"/&gt;
-  &lt;style <phrase role="strong">tts:fontSize="18px"</phrase>/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  Then fill up the glasses&lt;br/&gt;
-  with treacle and ink,&lt;br/&gt;
-  Or anything else&lt;br/&gt;
-  that is &lt;span <phrase role="strong">tts:fontSize="24px"</phrase>&gt;pleasant&lt;/span&gt; to drink.
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-fontSize-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Font Size</caption>
-<tbody>
-<tr>
-<td><graphic source="images/fontSize.png" alt="TTML fontSize style property"/></td>
-</tr>
-</tbody>
-</table>
-<!--CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.9.4.</p>
-</note>
--->  
-</div3>
-<div3 id="style-attribute-fontStyle">
-<head>tts:fontStyle</head>
-<p>The <att>tts:fontStyle</att> attribute is used to specify a style property that
-defines the font style to apply to glyphs that are selected for glyph areas generated
-by content flowed into a region, where the mapping from font
-style value to specific font face or style parameterization is not determined
-by this specification.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-fontStyle" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>normal</code> |
-<code>italic</code> |
-<code>oblique</code>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>normal</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#content-vocabulary-span"><el>span</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>Use of the value <code>oblique</code>
-denote a shear transformation (at an unspecified
-angle) in the inline progression dimension.</p>
-<p>If a specified font style is not available, then a
-presentation processor must attempt to map the specified font style
-to an available font style that has similar typographic
-characteristics, or, in the absence of such a mapping, it must
-interpret the font style as if the value <code>normal</code> were
-specified.</p>
-<p>The <att>tts:fontStyle</att> style is illustrated by the following example.</p>
-<table id="style-attribute-fontStyle-example-1" role="example">
-<caption>Example Fragment &ndash; Font Style</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="331px 84px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="after"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-  &lt;style tts:fontFamily="proportionalSansSerif"/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  In autumn, when the leaves are brown,&lt;br/&gt;
-  Take pen and ink, and &lt;span <phrase role="strong">tts:fontStyle="italic"</phrase>&gt;write it down.&lt;/span&gt;
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-fontStyle-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Font Style</caption>
-<tbody>
-<tr>
-<td><graphic source="images/fontStyle.png" alt="TTML fontStyle style property"/></td>
-</tr>
-</tbody>
-</table>
-<p/>
-<!-- CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.9.7.</p>
-</note>
--->  
-</div3>
-<div3 id="style-attribute-fontWeight">
-<head>tts:fontWeight</head>
-<p>The <att>tts:fontWeight</att> attribute is used to specify a style property
-that defines the font weight to apply to glyphs that are selected for glyph
-areas generated by content flowed into a region, where the mapping from font
-weight value to specific font face or weight parameterization is not determined
-by this specification.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-fontWeight" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>normal</code> |
-<code>bold</code>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>normal</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#content-vocabulary-span"><el>span</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>If a specified font weight is not available, then a
-presentation processor must attempt to map the specified font weight
-to an available font weight that has similar typographic
-characteristics, or, in the absence of such a mapping, it must
-interpret the font weight as if the value <code>normal</code> were
-specified.</p>
-<p>The <att>tts:fontWeight</att> style is illustrated by the following example.</p>
-<table id="style-attribute-fontWeight-example-1" role="example">
-<caption>Example Fragment &ndash; Font Weight</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="376px 95px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="center"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-  &lt;style tts:fontFamily="proportionalSansSerif"/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  They told me you had been to her,&lt;br/&gt;
-  &lt;span <phrase role="strong">tts:fontWeight="bold"</phrase>&gt;and mentioned me to him:&lt;/span&gt;&lt;br/&gt;
-  She gave me a good character&lt;br/&gt;
-  &lt;span <phrase role="strong">tts:fontWeight="bold"</phrase>&gt;but said I could not swim.&lt;/span&gt;
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-fontWeight-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Font Weight</caption>
-<tbody>
-<tr>
-<td><graphic source="images/fontWeight.png" alt="TTML fontWeight style property"/></td>
-</tr>
-</tbody>
-</table>
-<!--CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.9.9.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-lineHeight">
-<head>tts:lineHeight</head>
-<p>The <att>tts:lineHeight</att> attribute is used to specify a style property that
-defines the inter-baseline separation between line areas generated by content flowed into a region.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-lineHeight" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>normal</code> |
-<loc href="#style-value-length">&lt;length&gt;</loc>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>normal</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#content-vocabulary-p"><el>p</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>relative to this element's font size</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If the value of this attribute is <code>normal</code>, then the
-initial value of the style property must be considered to be the same
-as the largest font size that applies to any
-descendant element.</p>
-<p>If specified as a <loc
-href="#style-value-length">&lt;length&gt;</loc>, then the length must
-be non-negative.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>normal</code> were specified.</p>
-<p>The <att>tts:lineHeight</att> style is illustrated by the following example.</p>
-<table id="style-attribute-lineHeight-example-1" role="example">
-<caption>Example Fragment &ndash; Line Height</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="255px 190px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="center"/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-  &lt;style tts:fontFamily="proportionalSansSerif"/&gt;
-  &lt;style tts:fontSize="16px"/&gt;
-  &lt;style <phrase role="strong">tts:lineHeight="32px"</phrase>/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  He thought he saw an elephant,&lt;br/&gt;
-  That practised on a fife:&lt;br/&gt;
-  He looked again, and found it was&lt;br/&gt;
-  A letter from his wife.&lt;br/&gt;
-  "At length I realise," he said,&lt;br/&gt;
-  "The bitterness of Life.
-"&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-lineHeight-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Line Height</caption>
-<tbody>
-<tr>
-<td><graphic source="images/lineHeight.png" alt="TTML lineHeight style property"/></td>
-</tr>
-</tbody>
-</table>
-<p/>
-<!-- CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.16.4.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-opacity">
-<head>tts:opacity</head>
-<p>The <att>tts:opacity</att> attribute is used to specify a style property that
-defines the opacity (or conversely, the transparency)
-of marks associated with a region.</p>
-<p>When presented onto a visual medium, the opacity of the region is applied uniformly and on a linear scale
-to all marks produced by content targeted to the
-region.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-opacity" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<loc href="#style-value-alpha">&lt;alpha&gt;</loc>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td>
-<code>1.0</code>
-</td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#layout-vocabulary-region"><el>region</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>An <loc href="#style-value-alpha">&lt;alpha&gt;</loc> value greater
-than 1.0 must be considered equivalent to an <loc
-href="#style-value-alpha">&lt;alpha&gt;</loc> value of 1.0.</p>
-<p>The <att>tts:opacity</att> style is illustrated by the following example.</p>
-<table id="style-attribute-opacity-example-1" role="example">
-<caption>Example Fragment &ndash; Opacity</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1" dur="5s"&gt;
-  &lt;set begin="0s" dur="1s" <phrase role="strong">tts:opacity="1.00"</phrase>/&gt;
-  &lt;set begin="1s" dur="1s" <phrase role="strong">tts:opacity="0.75"</phrase>/&gt;
-  &lt;set begin="2s" dur="1s" <phrase role="strong">tts:opacity="0.50"</phrase>/&gt;
-  &lt;set begin="3s" dur="1s" <phrase role="strong">tts:opacity="0.25"</phrase>/&gt;
-  &lt;set begin="4s" dur="1s" <phrase role="strong">tts:opacity="0.00"</phrase>/&gt;
-  &lt;style tts:extent="304px 77px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="after"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  The sun was shining on the sea
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-opacity-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Opacity</caption>
-<tbody>
-<tr>
-<td>
-<graphic source="images/opacity_0.png" alt="TTML opacity style property - [0,1)"/>
-</td>
-</tr>
-<tr>
-<td>
-<graphic source="images/opacity_1.png" alt="TTML opacity style property - [1,2)"/>
-</td>
-</tr>
-<tr>
-<td>
-<graphic source="images/opacity_2.png" alt="TTML opacity style property - [2,3)"/>
-</td>
-</tr>
-<tr>
-<td>
-<graphic source="images/opacity_3.png" alt="TTML opacity style property - [3,4)"/>
-</td>
-</tr>
-<tr>
-<td>
-<graphic source="images/opacity_4.png" alt="TTML opacity style property - [4,5)"/>
-</td>
-</tr>
-</tbody>
-</table>
-<!--CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="css3-color"/>,
-&sect; 3.2.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-origin">
-<head>tts:origin</head>
-<p>The <att>tts:origin</att> attribute is used to specify the
-<emph>x</emph> and <emph>y</emph> coordinates of the origin of a
-region area with respect to the origin of the root container extent,
-if specified, or the external authoring context, if not specified.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-origin" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>auto</code> |
-<loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>auto</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#layout-vocabulary-region"><el>region</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>relative to width and height of root container region</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If the value of this attribute consists of two <loc href="#style-value-length">&lt;length&gt;</loc> specifications,
-then they must be interpreted as <emph>x</emph> and <emph>y</emph> coordinates, where the first specification
-is the <emph>x</emph> coordinate, and the second specification is the <emph>y</emph> coordinate.</p>
-<p>If the value of this attribute is <code>auto</code>, then the initial value
-of the style property must be considered to be the same as the root container
-origin.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>auto</code> were specified.</p>
-<p>The <att>tts:origin</att> style is illustrated by the following example.</p>
-<table id="style-attribute-origin-example-1" role="example">
-<caption>Example Fragment &ndash; Origin</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style <phrase role="strong">tts:origin="40px 40px"</phrase>/&gt;
-  &lt;style tts:extent="308px 92px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="center"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  "To dine!" she shrieked in dragon-wrath.&lt;br/&gt;
-  "To swallow wines all foam and froth!&lt;br/&gt;
-   To simper at a table-cloth!"
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-origin-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Origin</caption>
-<tbody>
-<tr>
-<td><graphic source="images/origin.png" alt="TTML origin style property"/></td>
-</tr>
-</tbody>
-</table>
-</div3>
-<div3 id="style-attribute-overflow">
-<head>tts:overflow</head>
-<p>The <att>tts:overflow</att> attribute is used to specify a style property that
-defines whether a region area is clipped or not if the descendant areas of the region overflow
-its extent.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-overflow" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>visible</code> |
-<code>hidden</code>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>hidden</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#layout-vocabulary-region"><el>region</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If the value of this attribute is <code>visible</code>, then content should
-not be clipped outside of the affected region, and region composition and layout
-must be performed as if the region's width and height were
-unconstrained,
-but with
-a well-defined origin.  If the value is <code>hidden</code>, then content should
-be clipped outside of the affected region.</p>
-<note role="explanation">
-<p>Unless a manual line break element <el>br</el> is used by the content author,
-a paragraph of a given region will generate no more than one line area in that
-region if the value of the <att>tts:overflow</att> style that applies to the
-region is <code>visible</code> and if the applicable <att>tts:wrapOption</att>
-style is <code>noWrap</code>.</p>
-</note>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>hidden</code> were specified.</p>
-<p>The <att>tts:overflow</att> style is illustrated by the following example.</p>
-<table id="style-attribute-overflow-example-1" role="example">
-<caption>Example Fragment &ndash; Overflow</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="232px 40px"/&gt;
-  &lt;style tts:origin="0px 0px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="red"/&gt;
-  &lt;style tts:displayAlign="before"/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-  &lt;style tts:fontFamily="proportionalSansSerif"/&gt;
-  &lt;style tts:fontSize="18px"/&gt;
-  &lt;style tts:wrapOption="noWrap"/&gt;
-  &lt;style <phrase role="strong">tts:overflow="visible"</phrase>/&gt;
-&lt;/region&gt;
-&lt;region xml:id="r2"&gt;
-  &lt;style tts:extent="232px 40px"/&gt;
-  &lt;style tts:origin="0px 43px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="red"/&gt;
-  &lt;style tts:displayAlign="before"/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-  &lt;style tts:fontFamily="proportionalSansSerif"/&gt;
-  &lt;style tts:fontSize="18px"/&gt;
-  &lt;style tts:wrapOption="noWrap"/&gt;
-  &lt;style <phrase role="strong">tts:overflow="hidden"</phrase>/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  "But wait a bit," the Oysters cried,&lt;br/&gt;
-  "Before we have our chat;
-&lt;/p&gt;
-&lt;p region="r2"&gt;
-  For some of us are out of breath,&lt;br/&gt;
-  And all of us are fat!"
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-overflow-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Overflow</caption>
-<tbody>
-<tr>
-<td><graphic source="images/overflow.png" alt="TTML overflow style property"/></td>
-</tr>
-</tbody>
-</table>
-<note role="explanation">
-<p>In the above example, the <att>tts:noWrap</att> is set to
-<code>noWrap</code> to prevent automatic line wrapping (breaking);
-if this were not specified, then overflow would occur in the block
-progression direction as opposed to the inline progression direction.</p>
-</note>
-<!-- CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.21.2.</p>
-</note>
--->  
-</div3>
-<div3 id="style-attribute-padding">
-<head>tts:padding</head>
-<p>The <att>tts:padding</att> attribute is used to specify padding (or inset)
-space on all sides of a region area.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-padding" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<loc href="#style-value-length">&lt;length&gt;</loc> |
-<loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc> |
-<loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc> |
-<loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc> <loc href="#style-value-length">&lt;length&gt;</loc>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>0px</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#layout-vocabulary-region"><el>region</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>relative to width and height of region</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If the value of this attribute consists of one <loc href="#style-value-length">&lt;length&gt;</loc> specification,
-then that length applies to all edges of the affected areas. If the value
-consists of two <loc href="#style-value-length">&lt;length&gt;</loc> specifications, then the first applies to the
-before and after edges, and the second applies to the start and end edges.
-If three <loc href="#style-value-length">&lt;length&gt;</loc> specifications are provided, then the first applies to the
-before edge, the second applies to the start and end edges, and the third applies
-to the after edge.
-If four <loc href="#style-value-length">&lt;length&gt;</loc> specifications are provided, then they apply to before, end,
-after, and start edges, respectively.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>0px</code> were specified.</p>
-<p>The <att>tts:padding</att> style is illustrated by the following example.</p>
-<table id="style-attribute-padding-example-1" role="example">
-<caption>Example Fragment &ndash; Padding</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="446px 104px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="after"/&gt;
-  &lt;style tts:textAlign="center"/&gt;
-  &lt;style <phrase role="strong">tts:padding="10px 40px"</phrase>/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1" tts:backgroundColor="red"&gt;
-  Just the place for a Snark! I have said it twice:&lt;br/&gt;
-  That alone should encourage the crew.&lt;br/&gt;
-  Just the place for a Snark! I have said it thrice:&lt;br/&gt;
-  What I tell you three times is true.
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p>When rendering an area to which padding applies, the background color that
-applies to the area is rendered into the padded portion of the area.</p>
-<table id="style-attribute-padding-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Padding</caption>
-<tbody>
-<tr>
-<td>
-<graphic source="images/padding.png" alt="TTML padding style property"/>
-</td>
-</tr>
-</tbody>
-</table>
- <!-- CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.31.15, except that individual shorthand values map to writing
-  mode relative padding values as defined by <bibref ref="xsl11"/>,
-&sect; 7.8.31, 7.8.32, 7.8.33, and 7.8.34.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-showBackground">
-<head>tts:showBackground</head>
-<p>The <att>tts:showBackground</att> attribute is used to specify
-constraints on when the background color of a region is intended to be
-presented.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-showBackground" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>always</code> |
-<code>whenActive</code>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>always</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#layout-vocabulary-region"><el>region</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>no</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If the value of this attribute is <code>always</code>, then the
-background color of a region is always rendered when performing presentation
-processing on a visual medium; if the value is <code>whenActive</code>,
-then the background color of a region is rendered only when some
-content is selected into the region.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>always</code> were specified.</p>
-<p>The <att>tts:showBackground</att> style is illustrated by the following example.</p>
-<table id="style-attribute-showBackground-example-1" role="example">
-<caption>Example Fragment &ndash; Show Background</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:origin="0px 0px"/&gt;
-  &lt;style tts:extent="265px 100px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style <phrase role="strong">tts:showBackground="always"</phrase>/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="before"/&gt;
-  &lt;style tts:textAlign="start"/&gt;
-&lt;/region&gt;
-&lt;region xml:id="r2"&gt;
-  &lt;style tts:origin="205px 60px"/&gt;
-  &lt;style tts:extent="290px 100px"/&gt;
-  &lt;style tts:backgroundColor="red"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:displayAlign="before"/&gt;
-  &lt;style tts:textAlign="end"/&gt;
-  &lt;style <phrase role="strong">tts:showBackground="whenActive"</phrase>/&gt;
-&lt;/region&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<!--
-<table id="style-attribute-showBackground-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Show Background</caption>
-<tbody>
-<tr>
-<td>
-<graphic source="images/showBackground.png" alt="TTML showBackground style property"/>
-</td>
-</tr>
-</tbody>
-</table>
--->
-<!-- CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="smil21"/>,
-&sect; 5.3.1.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-textAlign">
-<head>tts:textAlign</head>
-<p>The <att>tts:textAlign</att> attribute is used to specify a style property that
-defines how inline areas are aligned within a containing block area in the inline progression
-direction.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-textAlign" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>left</code> |
-<code>center</code> |
-<code>right</code> |
-<code>start</code> |
-<code>end</code>
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>start</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#content-vocabulary-p"><el>p</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>start</code> were specified.</p>
-<p>The <att>tts:textAlign</att> style is illustrated by the following example.</p>
-<table id="style-attribute-textAlign-example-1" role="example">
-<caption>Example Fragment &ndash; Text Align</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="355px 43px"/&gt;
-  &lt;style tts:origin="0px 0px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style <phrase role="strong">tts:textAlign="start"</phrase>/&gt;
-&lt;/region&gt;
-&lt;region xml:id="r2"&gt;
-  &lt;style tts:extent="355px 43px"/&gt;
-  &lt;style tts:origin="0px 47px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style <phrase role="strong">tts:textAlign="end"</phrase>/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  Beware the Jabberwock, my son!&lt;br/&gt;
-  The jaws that bite, the claws that catch!
-&lt;/p&gt;
-&lt;p region="r2"&gt;
-  Beware the Jubjub bird, and shun&lt;br/&gt;
-  The frumious Bandersnatch!
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-textAlign-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Text Align</caption>
-<tbody>
-<tr>
-<td><graphic source="images/textAlign.png" alt="TTML textAlign style property"/></td>
-</tr>
-</tbody>
-</table>
-<!--CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.16.9.</p>
-</note>
--->
-</div3>
-<div3 id="style-attribute-textDecoration">
-<head>tts:textDecoration</head>
-<p>The <att>tts:textDecoration</att> attribute is used to specify a style property that
-defines a text decoration effect to apply to glyph areas or other inline
-areas that are generated by content flowed into a region.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-textDecoration" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>none</code> |
-[ [
-<code>underline</code> |
-<code>noUnderline</code>
-] || [
-<code>lineThrough</code> |
-<code>noLineThrough</code>
-] || [
-<code>overline</code> |
-<code>noOverline</code>
-] ]
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>none</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td><loc
-href="#content-vocabulary-span"><el>span</el></loc></td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>N/A</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>For the purpose of determining applicability of this
-style property, each character child of a <el>p</el> element is
-considered to be enclosed in an anonymous span.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>none</code> were specified.</p>
-<p>The <att>tts:textDecoration</att> style is illustrated by the following example.</p>
-<table id="style-attribute-textDecoration-example-1" role="example">
-<caption>Example Fragment &ndash; Text Decoration</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:extent="385px 82px"/&gt;
-  &lt;style tts:origin="0px 0px"/&gt;
-  &lt;style tts:backgroundColor="black"/&gt;
-  &lt;style tts:color="white"/&gt;
-  &lt;style tts:padding="5px 2px"/&gt;
-  &lt;style <phrase role="strong">tts:textDecoration="underline"</phrase>/&gt;
-&lt;/region&gt;
-...
-&lt;p region="r1"&gt;
-  The sea was wet&lt;span <phrase role="strong">tts:textDecoration="noUnderline"</phrase>&gt; as &lt;/span&gt;wet
-  &lt;span <phrase role="strong">tts:textDecoration="noUnderline"</phrase>&gt;
-    could be,&lt;br/&gt;
-    The sand was dry as dry.&lt;br/&gt;
-    &lt;span <phrase role="strong">tts:textDecoration="lineThrough"</phrase>&gt;There weren't any&lt;/span&gt;
-    You &lt;span <phrase role="strong">tts:textDecoration="lineThrough"</phrase>&gt;couldn't&lt;/span&gt;
-    could not see a cloud&lt;br/&gt;
-    Because no cloud was in the sky.
-  &lt;/span&gt;
-&lt;/p&gt;
-</eg>
-</td>
-</tr>
-</tbody>
-</table>
-<p/>
-<table id="style-attribute-textDecoration-example-1-images" role="example-images">
-<caption>Example Rendition &ndash; Text Decoration</caption>
-<tbody>
-<tr>
-<td><graphic source="images/textDecoration.png" alt="TTML textDecoration style property"/></td>
-</tr>
-</tbody>
-</table>
-<!--CSS compatibility - remove derivation note
-<note role="derivation">
-<p>The semantics of the style property
-represented by this attribute are based upon that defined by <bibref ref="xsl11"/>,
-&sect; 7.16.4.</p>
-</note>
--->  
-</div3>
-<div3 id="style-attribute-textOutline">
-<head>tts:textOutline</head>
-<p>The <att>tts:textOutline</att> attribute is used to specify a style property that
-defines a text outline effect to apply to glyphs that are selected for glyph areas generated
-by content flowed into a region.</p>
-<p>This attribute may be specified by any
-element type
-that permits use of attributes in the TT Style Namespace; however, this attribute applies
-as a style property only to those element types indicated in the following table.</p>
-<table id="style-property-details-textOutline" role="common">
-<col width="25%"/>
-<tbody>
-<tr>
-<td><emph>Values:</emph></td>
-<td>
-<code>none</code> |
-<loc href="#style-value-color">&lt;color&gt;</loc>?
-<loc href="#style-value-length">&lt;length&gt;</loc>
-<loc href="#style-value-length">&lt;length&gt;</loc>?
-</td>
-</tr>
-<tr>
-<td><emph>Initial:</emph></td>
-<td><code>none</code></td>
-</tr>
-<tr>
-<td><emph>Applies to:</emph></td>
-<td>
-<loc href="#content-vocabulary-span"><el>span</el></loc>
-</td>
-</tr>
-<tr>
-<td><emph>Inherited:</emph></td>
-<td>yes</td>
-</tr>
-<tr>
-<td><emph>Percentages:</emph></td>
-<td>relative to this element's font size</td>
-</tr>
-<tr>
-<td><emph>Animatable:</emph></td>
-<td>discrete</td>
-</tr>
-</tbody>
-</table>
-<p>For the purpose of determining applicability of this style property,
-each character child of a <el>p</el> element is considered to be enclosed in an anonymous
-span.</p>
-<p>The value of this attribute consists of an optional <loc href="#style-value-color">&lt;color&gt;</loc> term
-followed by one or two <loc href="#style-value-length">&lt;length&gt;</loc> terms.  If a <emph>color</emph> term is
-present, then it denotes the outline color; if no <emph>color</emph> term is
-present, the computed value of the <att>tts:color</att> applies.  The first
-<emph>length</emph> term denotes the outline thickness and the second length
-term, if present, indicates the blur radius.</p>
-<p>If a specified value of this attribute is not supported,
-then a presentation processor must interpret the attribute as if the
-value <code>none</code> were specified.</p>
-<p>The <att>tts:textOutline</att> style is illustrated by the following
-example.</p>
-<table id="style-attribute-textOutline-example-1" role="example">
-<caption>Example Fragment &ndash; Text Outline</caption>
-<tbody>
-<tr>
-<td>
-<eg xml:space="preserve">
-&lt;region xml:id="r1"&gt;
-  &lt;style tts:backgroundColor="transparent"/&gt;
-  &lt;style tts:color="yellow"/&gt;
-  &lt;style <phrase role="strong">tts:textOutline="black 2px 0px"</phrase>/&gt;
-  &lt;style tts:fontFamily="proportionalSansSerif"/&gt;
-  &lt;style tts:fontSize="24px"/&gt;
-&lt;/region&gt;
-...
-&lt;p&gt;
-  How doth the little crocodile&lt;br/&gt;
-  Improve its shining tail,&lt;br/&gt;