[imsc] preparing CR imsc-cr
authorpal@sandflow.org
Tue, 21 Oct 2014 17:53:26 -0700
branchimsc-cr
changeset 749 0c81794d1d8d
parent 748 97a40e97024a
child 750 828021fb3ac0
[imsc] preparing CR
ttml-ww-profiles/ttml-ww-profiles.html
ttml-ww-profiles/ttml-ww-profiles.source.html
--- a/ttml-ww-profiles/ttml-ww-profiles.html	Tue Oct 21 13:15:37 2014 -0700
+++ b/ttml-ww-profiles/ttml-ww-profiles.html	Tue Oct 21 17:53:26 2014 -0700
@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<html lang="en" dir="ltr" typeof="bibo:Document " about="" property="dcterms:language" content="en">
+<html lang="en" dir="ltr" typeof="bibo:Document w3p:CR" about="" property="dcterms:language" content="en">
 <head>
   <meta charset="utf-8">
 
@@ -207,7 +207,7 @@
 }
 
 
-</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-ED"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
+</style><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/W3C-CR"><!--[if lt IE 9]><script src='https://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head>
 
 <body class="h-entry" role="document" id="respecDocument"><div class="head" role="contentinfo" id="respecHeader">
   <p>
@@ -219,11 +219,11 @@
   </p>
   <h1 class="title p-name" id="title" property="dcterms:title">TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0</h1>
   
-  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-10-21T20:13:34.000Z" id="w3c-editor-s-draft-21-october-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Editor's Draft <time class="dt-published" datetime="2014-10-21">21 October 2014</time></h2>
+  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-11-15T08:00:00.000Z" id="w3c-candidate-recommendation-15-november-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Candidate Recommendation <time class="dt-published" datetime="2014-11-15">15 November 2014</time></h2>
   <dl>
     
       <dt>This version:</dt>
-      <dd><a class="u-url" href="https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml-ww-profiles/ttml-ww-profiles.html">https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml-ww-profiles/ttml-ww-profiles.html</a></dd>
+      <dd><a class="u-url" href="http://www.w3.org/TR/2014/CR-ttml-imsc1-20141115/">http://www.w3.org/TR/2014/CR-ttml-imsc1-20141115/</a></dd>
       <dt>Latest published version:</dt>
       <dd><a href="http://www.w3.org/TR/ttml-imsc1/">http://www.w3.org/TR/ttml-imsc1/</a></dd>
     
@@ -233,11 +233,15 @@
     
     
     
+      <dt>Implementation report:</dt>
+      <dd><a href="https://www.w3.org/wiki/TimedText/IMSC1_Implementation_Report">https://www.w3.org/wiki/TimedText/IMSC1_Implementation_Report</a></dd>
     
     
-      
     
     
+      <dt>Previous version:</dt>
+      <dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2014/WD-ttml-imsc1-20140930/">http://www.w3.org/TR/2014/WD-ttml-imsc1-20140930/</a></dd>
+    
     
     <dt>Editor:</dt>
     <dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><span property="foaf:name" class="p-name fn">Pierre Lemieux</span>, <span class="ed_mailto"><a class="u-email email" rel="foaf:mbox" href="mailto:[email protected]">[email protected]</a></span></span>
@@ -294,9 +298,27 @@
           http://www.w3.org/TR/.</em>
         </p>
         
+<div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_1"><span>Note</span></div><div class=""><p>During the Candidate Recommendation phase, the Working Group invites and encourages IMSC 1 implementers to contribute the following:</p><ul>
+<li>sample content for inclusion in the <a href="https://dvcs.w3.org/hg/ttml/file/tip/ttml-ww-profiles/test-content">test suite</a> [1]. The sample content should exercise features and constraints introduced by the IMSC 1 specification;</li>
+<li>results of processing and playback of the <a href="https://dvcs.w3.org/hg/ttml/file/tip/ttml-ww-profiles/test-content">test suite</a> content;</li>
+<li>any implementation experience, in general.</li>
+</ul>
+<p></p>
+<p>This information will be included in the <a href="https://www.w3.org/wiki/TimedText/IMSC1_Implementation_Report">implementation report</a> used to demonstrate <a href="http://www.w3.org/2014/Process-20140801/#implementation-experience">implementation experience</a> when transitioning IMSC 1 to Proposed Recommendation.</p>
+<p>When contributing implementation experience, implementers are requested to provide the following information:
+</p><ul>
+<li>general description of the implementation, including its scope (authoring tool and/or transformation processor and/or presentation processor); and</li>
+<li>links to detailed information and code repository (if available);</li>
+</ul>
+<p></p>
+<p>The Working Group expects the test suite to evolve significantly before the specification advances to Proposed Recommendation.</p>
+<p>The Working Group has not identified features "at risk" for this specification.</p>
+</div></div>
 	
         <p>
-          This document was published by the <a href="http://www.w3.org/AudioVideo/TT/">Timed Text Working Group</a> as an Editor's Draft.
+          This document was published by the <a href="http://www.w3.org/AudioVideo/TT/">Timed Text Working Group</a> as a Candidate Recommendation.
+          
+            This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation.
           
           
             If you wish to make comments regarding this document, please send them to 
@@ -307,14 +329,24 @@
           
           
           
+            <abbr title="World Wide Web Consortium">W3C</abbr> publishes a Candidate Recommendation to indicate that the document is believed to be
+            stable and to encourage implementation by the developer community. This Candidate
+            Recommendation is expected to advance to Proposed Recommendation no earlier than
+            01 January 2015.
+          
           
             All comments are welcome.
           
         </p>
         
+          <p>
+            Please see the Working Group's  <a href="https://www.w3.org/wiki/TimedText/IMSC1_Implementation_Report">implementation
+            report</a>.
+          </p>
+        
         
           <p>
-            Publication as an Editor's Draft does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr>
+            Publication as a Candidate Recommendation does not imply endorsement by the <abbr title="World Wide Web Consortium">W3C</abbr>
             Membership. This is a draft document and may be updated, replaced or obsoleted by other
             documents at any time. It is inappropriate to cite this document as other than work in
             progress.
@@ -416,7 +448,7 @@
       provisions of the profile.</li>
     </ul>
 
-    <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_1"><span>Note</span></div><p class="">The use of the term <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> (<a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a>) within this specification
+    <div class="note"><div class="note-title" aria-level="1" role="heading" id="h_note_2"><span>Note</span></div><p class="">The use of the term <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> (<a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a>) within this specification
     does not imply conformance to the DFXP Presentation Profile (DFXP Transformation Profile) specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>]. In other
     words, it is not considered an error for a <a href="#dfn-presentation-processor" class="internalDFN">presentation processor</a> (<a href="#dfn-transformation-processor" class="internalDFN">transformation processor</a>) to conform to a
     profile defined in this specification without also conforming to the DFXP Presentation Profile (DFXP Transformation
@@ -437,7 +469,7 @@
       subtitle document such that, when image content is encountered, assistive technologies have access to its corresponding text
       form.</p>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_2"><span>Note</span></div><p class="">The <code>ittm:altText</code> element specified <a href="#ttm-altText" class="sec-ref"><span class="secno">5.7.4</span> <span class="sec-title">ittm:altText</span></a> also allows text equivalent
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_3"><span>Note</span></div><p class="">The <code>ittm:altText</code> element specified <a href="#ttm-altText" class="sec-ref"><span class="secno">5.7.4</span> <span class="sec-title">ittm:altText</span></a> also allows text equivalent
       string to be associated with an image, e.g. to support indexation of the content and also facilitate quality checking of the
       document during authoring.</p></div>
 
@@ -626,7 +658,7 @@
       <p>Subtitle documents should be authored assuming strict clipping of content that falls out of region areas, regardless of
       the computed value of <code>tts:overflow</code> for the region.</p>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_3"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], <code>tts:overflow</code> has no effect on the extent of the region, and hence
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_4"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], <code>tts:overflow</code> has no effect on the extent of the region, and hence
       the total normalized drawing area S(En) at <a href="#paint-regions" class="sec-ref"><span class="secno">8.1.3</span> <span class="sec-title">Paint Regions</span></a>.</p></div>
     </section>
 
@@ -652,7 +684,7 @@
         object with a frame rate of 1000 / 1001 × 30 ≈ 29.97.
       </aside>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_4"><span>Note</span></div><p class="">In typical scenario, the same video program (the related video object) will be used for subtitle document
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_5"><span>Note</span></div><p class="">In typical scenario, the same video program (the related video object) will be used for subtitle document
       authoring, delivery and user playback. The mapping from media time expression to related video object above allows the author
       to precisely associate subtitle video content with video frames, e.g. around scene transitions. In circumstances where the
       video program is downsampled during delivery, the application can specify that, at playback, the relative video object be
@@ -662,7 +694,7 @@
       <p>If <code>ttp:frameRate</code> is specified, then the product of <code>ttp:frameRate</code> and
       <code>ttp:frameRateMultiplier</code> <em class="rfc2119" title="SHALL">SHALL</em> be the frame rate of the related video object.</p>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_5"><span>Note</span></div><p class="">A document can be made independent of the frame rate of the related video object by never using the
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_6"><span>Note</span></div><p class="">A document can be made independent of the frame rate of the related video object by never using the
       <em>frames</em> term in a time expression: as specified in <a href="#common-features" class="sec-ref"><span class="secno">5.10</span> <span class="sec-title">Features</span></a>, <code>ttp:frameRate</code> is
       required only if the document includes one or more time expressions that uses the <em>frames</em> term.</p></div>
     </section>
@@ -727,7 +759,7 @@
         <p>An <code>ittp:aspectRatio</code> attribute is considered to be significant only when specified on the <code>tt</code>
         element.</p>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_6"><span>Note</span></div><p class="">As specified in Section <a href="#common-features" class="sec-ref"><span class="secno">5.10</span> <span class="sec-title">Features</span></a>, <code>tts:extent</code> is present if the
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_7"><span>Note</span></div><p class="">As specified in Section <a href="#common-features" class="sec-ref"><span class="secno">5.10</span> <span class="sec-title">Features</span></a>, <code>tts:extent</code> is present if the
         <code>px</code> length measure is used anywhere within the document.</p></div>
 
         <p>Integer pixel positions on the related video object frame computed from real percentage length values <em class="rfc2119" title="SHALL">SHALL</em> use half-up
@@ -786,7 +818,7 @@
         asserted to be a <a href="#dfn-progressively-decodable-subtitle-document" class="internalDFN">progressively decodable subtitle document</a> nor asserted not to be a progressively decodable subtitle
         document.</p>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_7"><span>Note</span></div><div class="">
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_8"><span>Note</span></div><div class="">
           <p>[<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>] specifies explicitly referencing of elements identified using <code>xml:id</code> in the following
           circumstances:</p>
 
@@ -881,18 +913,18 @@
         <p>The algorithm for setting the <code>displayForcedOnlyMode</code> parameter based on the circumstances under which the
         subtitle document is presented is left to the application.</p>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_8"><span>Note</span></div><p class="">The background of a region is drawn even if the computed value of <code>tts:visibility</code> equals
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_9"><span>Note</span></div><p class="">The background of a region is drawn even if the computed value of <code>tts:visibility</code> equals
         "hidden" for all active content within. This can occur if <code>itts:forcedDisplay</code> equals "false" for all active
         content elements within a region for which <code>itts:forcedDisplay</code> equals "true", and
         <code>displayForcedOnlyMode</code> equals "true". Authors can avoid this situation, for instance, by ensuring that content
         elements and the regions that they are flowed into always have the same value of <code>itts:forcedDisplay</code>.</p></div>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_9"><span>Note</span></div><p class="">Although <code>itts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_10"><span>Note</span></div><p class="">Although <code>itts:forcedDisplay</code>, like all the TTML style attributes, has no defined semantics on a
         <code>br</code> content element, <code>itts:forcedDisplay</code> will apply to a <code>br</code> content element if it is
         either defined on an ancestor content element of the <code>br</code> content element or it is applied to a region element
         corresponding to a region that the <code>br</code> content element is being flowed into.</p></div>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_10"><span>Note</span></div><p class="">It is expected that the functionality of <code>itts:forcedDisplay</code> will be mapped to a conditional
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_11"><span>Note</span></div><p class="">It is expected that the functionality of <code>itts:forcedDisplay</code> will be mapped to a conditional
         style construct in a future revision of this specification.</p></div>
       </section>
 
@@ -926,7 +958,7 @@
 
         <p><a href="#image-profile-constraints" class="sec-ref"><span class="secno">7.</span> <span class="sec-title">Image Profile Constraints</span></a> specifies the use of the <code>ittm:altText</code> element with images.</p>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_11"><span>Note</span></div><p class="">In contrast to the common use of <code>alt</code> attributes in [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>], the <code>ittm:altText</code>
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_12"><span>Note</span></div><p class="">In contrast to the common use of <code>alt</code> attributes in [<cite><a class="bibref" href="#bib-HTML5">HTML5</a></cite>], the <code>ittm:altText</code>
         attribute content is not intended to be displayed in place of the element if the element is not loaded. The
         <code>ittm:altText</code> attribute content can however be read and used by assistive technologies. .</p></div>
       </section>
@@ -1419,7 +1451,7 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_12"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], a <code>#time-offset-with-frames</code> expression is translated to a media time
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_13"><span>Note</span></div><p class="">As specified in [<cite><a class="bibref" href="#bib-TTML1">TTML1</a></cite>], a <code>#time-offset-with-frames</code> expression is translated to a media time
       M according to M = 3600 · hours + 60 · minutes + seconds + (frames ÷ (<code>ttp:frameRateMultiplier</code> ·
       <code>ttp:frameRate</code>)).</p></div>
     </section>
@@ -1451,7 +1483,7 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_13"><span>Note</span></div><p class="">As specified in <a href="#common-features" class="sec-ref"><span class="secno">5.10</span> <span class="sec-title">Features</span></a>, the presence of the <code>ttp:profile</code> attribute is
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_14"><span>Note</span></div><p class="">As specified in <a href="#common-features" class="sec-ref"><span class="secno">5.10</span> <span class="sec-title">Features</span></a>, the presence of the <code>ttp:profile</code> attribute is
       not required by this profile. The profile designator specified above is intended to be generally used to signal conformance
       of a subtitle document to the profile. The details of such signaling depends on the application, and can, for instance, use
       metadata structures out-of-band of the subtitle document.</p></div>
@@ -1806,7 +1838,7 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_14"><span>Note</span></div><p class="">As specified in <a href="#common-features" class="sec-ref"><span class="secno">5.10</span> <span class="sec-title">Features</span></a>, the presence of the <code>ttp:profile</code> attribute is
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_15"><span>Note</span></div><p class="">As specified in <a href="#common-features" class="sec-ref"><span class="secno">5.10</span> <span class="sec-title">Features</span></a>, the presence of the <code>ttp:profile</code> attribute is
       not required by this profile. The profile designator specified above is intended to be generally used to signal conformance
       of a subtitle document to the profile. The details of such signaling depends on the application, and can, for instance, use
       metadata structures out-of-band of the subtitle document.</p></div>
@@ -2110,7 +2142,7 @@
         P<sub>n-1</sub> at the presentation time of <a href="#dfn-intermediate-synchronic-document" class="internalDFN">intermediate synchronic document</a> E<sub>n</sub>, making the latter
         available for display.</p>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_15"><span>Note</span></div><p class="">It is possible for the contents of Presentation Buffer P<sub>n-1</sub> to never be displayed. This can
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_16"><span>Note</span></div><p class="">It is possible for the contents of Presentation Buffer P<sub>n-1</sub> to never be displayed. This can
         happen if Presentation Buffer P<sub>n</sub> is copied twice to Presentation Buffer P<sub>n-1</sub> between two consecutive
         video frame boundaries of the related video object.</p></div>
 
@@ -2143,11 +2175,11 @@
           </tbody>
         </table>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_16"><span>Note</span></div><p class="">BDraw effectively sets a limit on fillings regions - for example, assuming that the root container is
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_17"><span>Note</span></div><p class="">BDraw effectively sets a limit on fillings regions - for example, assuming that the root container is
         ultimately rendered at 1920×1080 resolution, a BDraw of 12 s<sup>-1</sup> would correspond to a fill rate of
         1920×1080×12/s=23.7×2<sup>20</sup>pixels s<sup>-1</sup>.</p></div>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_17"><span>Note</span></div><p class="">IPD effectively sets a limit on the complexity of any given <a href="#dfn-intermediate-synchronic-document" class="internalDFN">intermediate synchronic document</a>.</p></div>
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_18"><span>Note</span></div><p class="">IPD effectively sets a limit on the complexity of any given <a href="#dfn-intermediate-synchronic-document" class="internalDFN">intermediate synchronic document</a>.</p></div>
       </section>
 
       <section id="paint-regions" typeof="bibo:Chapter" resource="#paint-regions" rel="bibo:Chapter">
@@ -2160,7 +2192,7 @@
 
         <p>where CLEAR(E<sub>0</sub>) = 0 and CLEAR(E<sub>n | n &gt; 0</sub>) = 1, i.e. the root container in its entirety.</p>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_18"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new <a href="#dfn-intermediate-synchronic-document" class="internalDFN">intermediate synchronic document</a> requires
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_19"><span>Note</span></div><p class="">To ensure consistency of the Presentation Buffer, a new <a href="#dfn-intermediate-synchronic-document" class="internalDFN">intermediate synchronic document</a> requires
         clearing of the root container.</p></div>
 
         <p>PAINT(E<sub>n</sub>) <em class="rfc2119" title="SHALL">SHALL</em> be the normalized area to be painted for all regions that are used in intermediate synchronic
@@ -2419,7 +2451,7 @@
           </tbody>
         </table>
 
-        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_19"><span>Note</span></div><p class="">NRGA(G<sub>i</sub>) does not take into account glyph decorations (e.g. underline), glyph effects (e.g.
+        <div class="note"><div class="note-title" aria-level="3" role="heading" id="h_note_20"><span>Note</span></div><p class="">NRGA(G<sub>i</sub>) does not take into account glyph decorations (e.g. underline), glyph effects (e.g.
         outline) or actual glyph aspect ratio. An implementation can determine an actual buffer size needs based on worst-case
         glyph size complexity.</p></div>
 
@@ -2500,10 +2532,10 @@
         </tbody>
       </table>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_20"><span>Note</span></div><p class="">Implementations can use use fonts other than those specified above. Two fonts with equal metrics can have a
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_21"><span>Note</span></div><p class="">Implementations can use use fonts other than those specified above. Two fonts with equal metrics can have a
       different appearance, but flow identically.</p></div>
 
-      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_21"><span>Note</span></div><p class="">proportionalSansSerif is not used in practice for Hebrew and Arabic captions and subtitles.</p></div>
+      <div class="note"><div class="note-title" aria-level="2" role="heading" id="h_note_22"><span>Note</span></div><p class="">proportionalSansSerif is not used in practice for Hebrew and Arabic captions and subtitles.</p></div>
     </section>
   </section>
 
--- a/ttml-ww-profiles/ttml-ww-profiles.source.html	Tue Oct 21 13:15:37 2014 -0700
+++ b/ttml-ww-profiles/ttml-ww-profiles.source.html	Tue Oct 21 17:53:26 2014 -0700
@@ -9,9 +9,12 @@
 </script>
   <script class='remove'>
 var respecConfig = {
-                        specStatus:   "ED"
+                        specStatus:   "CR"
+								,   crEnd: "2015-01-01"
+								,   implementationReportURI: "https://www.w3.org/wiki/TimedText/IMSC1_Implementation_Report"
                 ,   processVersion: "2014"
 								,   previousMaturity: "WD"
+								,   publishDate: "2014-11-15"
 								,   previousPublishDate: "2014-09-30"
           ,   shortName:    "ttml-imsc1"
           ,   editors:      [{ name: "Pierre Lemieux", mailto: "[email protected]" }]
@@ -66,6 +69,22 @@
   </section>
 
   <section id='sotd'>
+<div class="note"><p>During the Candidate Recommendation phase, the Working Group invites and encourages IMSC 1 implementers to contribute the following:<ul>
+<li>sample content for inclusion in the <a href="https://dvcs.w3.org/hg/ttml/file/tip/ttml-ww-profiles/test-content">test suite</a> [1]. The sample content should exercise features and constraints introduced by the IMSC 1 specification;</li>
+<li>results of processing and playback of the <a href="https://dvcs.w3.org/hg/ttml/file/tip/ttml-ww-profiles/test-content">test suite</a> content;</li>
+<li>any implementation experience, in general.</li>
+</ul>
+</p>
+<p>This information will be included in the <a href="https://www.w3.org/wiki/TimedText/IMSC1_Implementation_Report">implementation report</a> used to demonstrate <a href="http://www.w3.org/2014/Process-20140801/#implementation-experience">implementation experience</a> when transitioning IMSC 1 to Proposed Recommendation.</p>
+<p>When contributing implementation experience, implementers are requested to provide the following information:
+<ul>
+<li>general description of the implementation, including its scope (authoring tool and/or transformation processor and/or presentation processor); and</li>
+<li>links to detailed information and code repository (if available);</li>
+</ul>
+</p>
+<p>The Working Group expects the test suite to evolve significantly before the specification advances to Proposed Recommendation.</p>
+<p>The Working Group has not identified features "at risk" for this specification.</p>
+</div>
 	</section>
 
   <section id='scope'>