[imsc] merge with trunk
authorpal@sandflow.org
Thu, 13 Nov 2014 07:47:26 -0800
changeset 759 2ad594ff71d9
parent 758 0ddffaf8004c (current diff)
parent 757 5ee90ec0d897 (diff)
child 760 9e3d43442c3d
[imsc] merge with trunk
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ttml-status/index.html	Thu Nov 13 07:47:26 2014 -0800
@@ -0,0 +1,141 @@
+<!DOCTYPE html>
+<!-- vim: set expandtab ts=2 sw=2 tw=80: -->
+<html>
+  <head>
+    <title>TTML Recommendations, Snapshot 2014</title>
+    <meta charset="utf-8">
+    <!--script src="respec/respec.js" class="remove"></script-->
+	<script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
+    <script class="remove">
+      var respecConfig = {
+        // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use
+        specStatus: "NOTE",
+
+        // the specification's short name, as in
+        // http://www.w3.org/TR/short-name/
+        shortName:            "ttml-status",
+
+        // if your specification has a subtitle that goes below the main
+        // formal title, define it here
+        subtitle   :  "",
+
+        // if you wish the publication date to be other than today, set this
+        // publishDate:  "2009-08-06",
+
+        // if the specification's copyright date is a range of years, specify
+        // the start date here:
+        // copyrightStart: "2012"
+
+        // if there is a previously published draft, uncomment this and set
+        // its YYYY-MM-DD date and its maturity status
+        //previousPublishDate: "2013-02-06",
+		    //previousURI: "http://dev.w3.org/cvsweb/~checkout~/SVG/modules/streaming/index.html?rev=1.2;content-type=text%2Fhtml",
+        // previousMaturity: "WD",
+
+        // if there a publicly available Editor's Draft, this is the link
+        //edDraftURI: "https://dev.w3.org/SVG/streaming/index.html",
+
+        // if this is a LCWD, uncomment and set the end of its review period
+        // lcEnd: "2009-08-05",
+
+        // Turning off inlineCSS for now since if extraCSS points to
+        // a relative URL your testing from a file URL the XHR will fail.
+        // Probably should turn this back on once this is hosted on a server
+        // somewhere.
+        inlineCSS: false,
+
+        // editors, add as many as you like
+        // only "name" is required
+        editors:  [
+            { name: "Cyril Concolato", mailto: "[email protected]",
+              company: "Telecom ParisTech", companyURL: "http://www.telecom-paristech.fr/" }
+        ],
+
+        // authors, add as many as you like.
+        // This is optional, uncomment if you have authors as well as editors.
+        // only "name" is required. Same format as editors.
+
+        //authors:  [
+        //    { name: "Your Name", url: "http://example.org/",
+        //      company: "Your Company", companyURL: "http://example.com/" },
+        //],
+
+        // XXX If we continue using ReSpec then we need to tweak it to support
+        // multiple working groups. It includes updating the patent section
+        // prose to say "groups" instead of "group" etc.
+        // name of the WG
+        wg: "Timed Text Working Group (part of the Audio Video in The Web Activity)",
+
+        // URI of the public WG page
+        // wgURI: "http://www.w3.org/Graphics/SVG/",
+
+        // name (without the @w3c.org) of the public mailing to which comments
+        // are due
+        wgPublicList: "public-tt",
+
+        // URI of the patent status for this WG, for Rec-track documents
+        // !!!! IMPORTANT !!!!
+        // This is important for Rec-track documents, do not copy a patent URI
+        // from a random document unless you know what you're doing. If in
+        // doubt ask your friendly neighbourhood Team Contact.
+        wgPatentURI:  "",
+
+        noIDLSorting: true,
+        noIDLIn: true
+      };
+    </script>
+    <!--
+      ReSpec.js wishlist:
+
+      Add here any issues you find with ReSpec including missing features. It
+      will help us decide if we should continue using it and work out what we
+      need to fix.
+
+    -->
+  </head>
+  <body>
+    <section id='abstract'>
+    This document collects together into one place all the specifications (versions, profiles), as of 2014, produced by the Timed Text Working Group (TTWG) regarding the Timed Text Markup Language (TTML). The document is intended for TTML authors and TTML implementors to help them identifying which specification is relevant for their application.
+    </section>
+
+    <section class="informative">
+      <h2>Introduction</h2>
+      <p>The TTWG produces specifications for media online captioning, and in particular develops and maintains versions of the Timed Text Markup Language (TTML). Several versions of this language and several profiles have been produced. The purpose of this document is to collect all versions and profiles of the TTML language, as defined by the W3C. Extensions and other profiles of TTML may be defined by other entities and are not listed in this document.
+ 	    </p>
+    </section>
+
+    <section class='informative'>
+      <h2>TTML Versions</h2>
+
+      <section>
+        <h3>Timed Text Markup Language 1 (TTML1)</h3>
+        <p>[[TTML10]] is the first version of the TTML language developped by the TTWG. The <a href="http://www.w3.org/TR/2010/REC-ttaf1-dfxp-20101118/">first edition</a> was published in November 2010. Errata items were identified and integrated in a <a href="http://www.w3.org/TR/2013/REC-ttml1-20130924/">Second Edition</a> in September 2013. The TTWG also produced profiles related to this specification (see next section). The TTWG will continue the development of this specification, possibly publishing new editions integrating new features or errata items.</p>
+        <p></p>
+      </section>
+
+      <section>
+        <h3>Timed Text Markup Language 2 (TTML2)</h3>
+        <p>[[TTML2]], currently at draft stage, represents a new version of the TTML language that is intended to co-exist with [[TTML10]].</p>
+      </section>
+
+    </section>
+
+    <section class='informative'>
+      <h2>TTML Profiles</h2>
+  
+      <section>
+        <h3>TTML Simple Delivery Profile for Closed Captions (SPD-US)</h3>
+        <p>The <a href="http://www.w3.org/TR/ttml10-sdp-us/">Simple Delivery Profile for Closed Captions</a> is a TTWG Note whose goal is to establish a minimum level of interoperability between [[TTML10]] and legacy caption formats employed in US markets, such as [[CEA608] and [[CEA708].</p>
+      </section>
+
+      <section>
+        <h3>TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0 (IMSC1)</h3>
+        <p><a href="http://www.w3.org/TR/2014/WD-ttml-imsc1-20140930/">IMSC1</a>[[IMSC1]] specifies two profiles of [TTML1]: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats. The text profile is a superset of [[SDPUS]].</p>
+      </section>
+    </section>
+    
+    <section class='appendix'>
+      <h2>Acknowledgements</h2>
+    </section>
+  </body>
+</html>
\ No newline at end of file