--- a/ttml-webvtt-mapping/mappingbetweenTTMLandWebVTTW3C.html Thu Sep 10 21:34:49 2015 +0200
+++ b/ttml-webvtt-mapping/mappingbetweenTTMLandWebVTTW3C.html Fri Sep 18 15:09:42 2015 -0700
@@ -8,10 +8,10 @@
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LCWD, WG-NOTE, etc.). If in doubt use ED.
- specStatus: "unofficial", // "WG-NOTE",
+ specStatus: "ED",
// the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "TTML2WebVTT",
+ shortName: "TTMLWebVTT",
previousURI: "https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml-webvtt-mapping/mappingbetweenTTMLandWebVTTW3C.html",
prevRecURI: "https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml-webvtt-mapping/mappingbetweenTTMLandWebVTTW3C.html",
prevRecURI: "https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml-webvtt-mapping/mappingbetweenTTMLandWebVTTW3C.html",
@@ -98,6 +98,11 @@
<p>
This is an editorial draft.
</p>
+
+ <p>If you wish to make comments regarding this document, please send them to <a href="mailto:public-tt@w3.org">public-tt@w3.org</a>
+(<a href="mailto:public-tt-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-tt/">archives</a>)
+with a subject line starting with <code>[TTML-WEBVTT]</code>.</p>
+
</section>
<section class='introductory'>
@@ -1169,7 +1174,7 @@
<section>
<h2>The TTML To WebVTT Profile</h2>
- <p>The TTML To WebVTT ( T2VP ) mapping profile constrains a TTML document structure to make the mapping between TTML and WebVTT simple and transparent. Many TTML documents will not conform to this profile.</p>
+ <p>The TTML To WebVTT ( TVTT ) mapping profile constrains a TTML document structure to make the mapping between TTML and WebVTT simple and transparent. Many TTML documents will not conform to this profile.</p>
<table class="simple" border="2px">
<tbody>
@@ -2470,14 +2475,14 @@
</section>
<section>
- <h2>Pre-processing: Converting TTML to T2VP</h2>
-
- <p>To ease conversion, a source TTML document can be transformed to a TTML document that conforms to the T2VP (TTML 2 WebVTT Document Profile). Below are some steps for how to pre-process a source TTML document so that it is valid against the T2VP.</p>
+ <h2>Pre-processing: Converting TTML to TVTT</h2>
+
+ <p>To ease conversion, a source TTML document can be transformed to a TTML document that conforms to the TVTT (TTML To WebVTT Document Profile). Below are some steps for how to pre-process a source TTML document so that it is valid against the TVTT.</p>
<section>
<h2>General Pre-processing</h2>
- <p>WebVTT does not define hierarchical elements such as the <code><body></code> or <code><div></code> elements found in TTML. Similarly, the T2VP profile constrains the use of hierarchical elements in documents that conform to it. As a result, when converting TTML documents to T2VP documents, all the information provided in the hierarchical elements must be applied to either the captions within those elements. Through this process, individual captions may have their timing, styling, layout and other information adjusted to take into account values inherited from sections that contain them. Within this document, the term “flattening” is used to designate this process.</p>
+ <p>WebVTT does not define hierarchical elements such as the <code><body></code> or <code><div></code> elements found in TTML. Similarly, the TVTT profile constrains the use of hierarchical elements in documents that conform to it. As a result, when converting TTML documents to TVTT documents, all the information provided in the hierarchical elements must be applied to either the captions within those elements. Through this process, individual captions may have their timing, styling, layout and other information adjusted to take into account values inherited from sections that contain them. Within this document, the term “flattening” is used to designate this process.</p>
<h2>Flattening</h2>
@@ -2631,11 +2636,11 @@
<h2>Apply Hierarchical Spatial Information to <code><p></code> Elements</h2>
- <p>In order to conform to the T2VP profile, all references to regions must be applied to <code><p></code>. If a <code><p></code> element is nested in other elements, any region references that exist on its parent elements should be moved to the <code><p></code> element.</p>
+ <p>In order to conform to the TVTT profile, all references to regions must be applied to <code><p></code>. If a <code><p></code> element is nested in other elements, any region references that exist on its parent elements should be moved to the <code><p></code> element.</p>
<h4>Remove Nested <code><style></code> Elements from <code><region></code> Elements</h4>
- <p>In order to conform to the T2VP profile, all nested <code><style></code> elements in <code><region></code> element definitions must be removed, with the attributes applied directly to the <code><region></code> itself. The sections below describe the details of this process.</p>
+ <p>In order to conform to the TVTT profile, all nested <code><style></code> elements in <code><region></code> element definitions must be removed, with the attributes applied directly to the <code><region></code> itself. The sections below describe the details of this process.</p>
</section>
<section>
@@ -2644,7 +2649,7 @@
<h2>Convert Inline Styling</h2>
- <p>Inline styles shall not be used in the T2VP apart from <code>@tts:textAlign</code> specified on <code><p></code> elements and <code>@tts:extent</code>, <code>@tts:origin</code>, <code>@tts:displayAlign</code> and <code>@tts:writingMode</code> on <code><region></code> elements. All other style attributes specified inline on <code><body></code>, <code><div></code>, <code><p></code> or <code><span></code> must be mapped to a <code><style></code> element that is then referenced by this content element. </p>
+ <p>Inline styles shall not be used in the TVTT apart from <code>@tts:textAlign</code> specified on <code><p></code> elements and <code>@tts:extent</code>, <code>@tts:origin</code>, <code>@tts:displayAlign</code> and <code>@tts:writingMode</code> on <code><region></code> elements. All other style attributes specified inline on <code><body></code>, <code><div></code>, <code><p></code> or <code><span></code> must be mapped to a <code><style></code> element that is then referenced by this content element. </p>
<p><strong>Example: Conversion of Inline Styling</strong> </p>
@@ -2782,7 +2787,7 @@
<h4>Styles that are Specified for <code><region></code> Elements</h4>
- <p>In a T2VP document, only the style attributes <code>@tts:extent</code>, <code>@tts:origin</code>, <code>@tts:displayAlign</code> and <code>@tts:writingMode</code> shall be specified on a <code><region></code>. The <code><region></code> shall not contain any style references nor <code><style></code> elements as children. If a source TTML document does not comply with this constraint, then all style references have to be resolved and merged, taking into account the style values of the <code><style></code> children of the <code><region></code>. A new <code><style></code> for the resolved set of style values is created. Every <code><p></code> that references that <code><region></code> should reference this <code><style></code>.</p>
+ <p>In a TVTT document, only the style attributes <code>@tts:extent</code>, <code>@tts:origin</code>, <code>@tts:displayAlign</code> and <code>@tts:writingMode</code> shall be specified on a <code><region></code>. The <code><region></code> shall not contain any style references nor <code><style></code> elements as children. If a source TTML document does not comply with this constraint, then all style references have to be resolved and merged, taking into account the style values of the <code><style></code> children of the <code><region></code>. A new <code><style></code> for the resolved set of style values is created. Every <code><p></code> that references that <code><region></code> should reference this <code><style></code>.</p>
<h4>Pruning of Unreferenced Styles</h4>
@@ -2790,7 +2795,7 @@
<h4>Translation of Incompatible Values</h4>
- <p>As mentioned above, there are a few incompatibilities between the set of styling attributes available in TTML and in WebVTT. These are expressed in the T2VP profile. Below are some recommendations how to handle these when translating a general TTML document into the T2VP profile.</p>
+ <p>As mentioned above, there are a few incompatibilities between the set of styling attributes available in TTML and in WebVTT. These are expressed in the TVTT profile. Below are some recommendations how to handle these when translating a general TTML document into the TVTT profile.</p>
<ul>
<li><p>tts:color</p>
@@ -2841,16 +2846,16 @@
<h2>Converting Timing Expressions</h2>
- <p>Because TTML supports many more timing expressions than those included in the T2VP profile, it may be necessary to perform a pre-processing step to convert a TTML document into a document that conforms to the T2VP profile. In many cases, this type of processing will require timing parameters to convert timing expressions into the format supported by T2VP.</p>
-
- <p>As a first step in mapping timing information from TTML to T2VP, convert all times in the TTML document into the time format supported by T2VP: hours: minutes: seconds.fractional-seconds, and limit the fractional-seconds to three decimal places. This conversion simplifies the mapping to WebVTT, as it results in all timing information expressed in the units supported by WebVTT. This section steps through the supported TTML timing expressions and describes how to convert from each of them into to the format that is included in the T2VP profile.</p>
+ <p>Because TTML supports many more timing expressions than those included in the TVTT profile, it may be necessary to perform a pre-processing step to convert a TTML document into a document that conforms to the TVTT profile. In many cases, this type of processing will require timing parameters to convert timing expressions into the format supported by TVTT.</p>
+
+ <p>As a first step in mapping timing information from TTML to TVTT, convert all times in the TTML document into the time format supported by TVTT: hours: minutes: seconds.fractional-seconds, and limit the fractional-seconds to three decimal places. This conversion simplifies the mapping to WebVTT, as it results in all timing information expressed in the units supported by WebVTT. This section steps through the supported TTML timing expressions and describes how to convert from each of them into to the format that is included in the TVTT profile.</p>
<h4>Time Expression: hours:minutes:seconds</h4>
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -2866,7 +2871,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -2888,7 +2893,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -2906,7 +2911,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -2927,7 +2932,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -2947,7 +2952,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -2961,7 +2966,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -2983,7 +2988,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -3001,7 +3006,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3022,7 +3027,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -3040,7 +3045,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3054,7 +3059,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3074,7 +3079,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -3092,7 +3097,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3106,7 +3111,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3126,7 +3131,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -3144,7 +3149,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3158,7 +3163,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3178,7 +3183,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -3196,7 +3201,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3210,7 +3215,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3223,7 +3228,7 @@
<ul>
<li>If the TTML document contains Time Base parameter equal to “clock”, and the Clock Mode parameter is present and has a value of “gps”, the TTML time must be converted to “utc” time, per the instructions in the TTML specification.</li>
- <li>Some rounding of timing expression values may be necessary if the value expressed in the TTML document has greater precision than is supported in the timing expression format supported by T2VP. </li>
+ <li>Some rounding of timing expression values may be necessary if the value expressed in the TTML document has greater precision than is supported in the timing expression format supported by TVTT. </li>
</ul>
<h4>Time Expression: frames.fractional-frames</h4>
@@ -3231,7 +3236,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -3249,7 +3254,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3263,7 +3268,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3284,7 +3289,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
<th>Relevant Parameters</th>
</tr>
</thead><tbody>
@@ -3302,7 +3307,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3316,7 +3321,7 @@
<table class='simple'><thead>
<tr>
<th>TTML Time Expression</th>
- <th>T2VP Time Expression</th>
+ <th>TVTT Time Expression</th>
</tr>
</thead><tbody>
<tr>
@@ -3333,7 +3338,7 @@
<h4>Converting Durations to End Times</h4>
- <p>The T2VP profile does not support durations, but rather requires that cue timings be expressed as begin and end times. Therefore, as part of transforming general TTML documents to conform with the T2VP profile, any timing expressed as duration must be transformed into an end time.</p>
+ <p>The TVTT profile does not support durations, but rather requires that cue timings be expressed as begin and end times. Therefore, as part of transforming general TTML documents to conform with the TVTT profile, any timing expressed as duration must be transformed into an end time.</p>
<p><strong>Example: Duration to End Time Conversion</strong></p>
<p>This example starts with an excerpt from a TTML file that uses "dur" to express the amount of time that <code><p></code> elements should be displayed.</p>
@@ -3362,7 +3367,7 @@
<h4>Calculate Cue Timing With Respect to the TTML Hierarchy</h4>
- <p>Once all timing expressions have been converted to be valid against the T2VP profile, the next step is to preserve and apply timing information from parent elements in order to calculate the correct timing to use for the WebVTT cue. </p>
+ <p>Once all timing expressions have been converted to be valid against the TVTT profile, the next step is to preserve and apply timing information from parent elements in order to calculate the correct timing to use for the WebVTT cue. </p>
<p>Below are several examples of TTML excerpts containing body, <code><div></code> and <code><p></code> elements, with timing information included in each element.</p>
@@ -3446,7 +3451,7 @@
</section>
<section>
- <h2>Converting from T2VP to WebVTT</h2>
+ <h2>Converting from TVTT to WebVTT</h2>
<section>
<h2>General</h2>
@@ -3662,7 +3667,7 @@
<h4>Creation of a CSS file</h4>
- <p>When starting from a TTML document that conforms to the T2VP profile, the first step is to create a CSS file where all of the <code><style></code> elements are mapped to ::cue pseudo elements with the value of <code>@xml:id</code> of the <code><style></code> element as a class name.</p>
+ <p>When starting from a TTML document that conforms to the TVTT profile, the first step is to create a CSS file where all of the <code><style></code> elements are mapped to ::cue pseudo elements with the value of <code>@xml:id</code> of the <code><style></code> element as a class name.</p>
<p><strong>Example: Creating CSS Style Class from TTML Style Element</strong></p>
@@ -3800,7 +3805,7 @@
<section>
<h2>Mapping Timing Information</h2>
- <p>Most of the transformation of timing information occurs during pre-processing. Once a document conforms to the T2VP format, only a few remaining transformations must be handled during the mapping to WebVTT:
+ <p>Most of the transformation of timing information occurs during pre-processing. Once a document conforms to the TVTT format, only a few remaining transformations must be handled during the mapping to WebVTT:
<ul>
<li>Convert span elements that contain timing information</li>
@@ -3810,7 +3815,7 @@
<h4>Calculate Timing for <code><span></code> Elements</h4>
- <p>Documents that employ <code><span></code> elements with timing information will require additional processing when mapping from T2VP to WebVTT.</p>
+ <p>Documents that employ <code><span></code> elements with timing information will require additional processing when mapping from TVTT to WebVTT.</p>
<p><strong>Example: <code><span></code> Elements</strong></p>
<p>This example starts with an excerpt from a TTML file that includes some <code><span></code> elements within <code><p></code> elements. </p>