Add DAPT conformance signaling

imsc1/spec/ttml-ww-profiles.html

@@ -448,7 +448,7 @@ <h2>Text Profile</h2>
 
     <section>
       <h3>General</h3>
-       <p>The <dfn>Text Profile</dfn> consists of Sections <a href="#supported-features-and-extensions"></a> and <a href=
+       <p>The <dfn class="export" data-lt="Text Profile|IMSC Text Profile">Text Profile</dfn> consists of Sections <a href="#supported-features-and-extensions"></a> and <a href=
       "#common-constraints"></a>.</p>
     </section>
 
@@ -2820,6 +2820,7 @@ <h4>Signaling conformance using EBU-TT metadata</h4>
         <p class="note">See <a href="#ebu-tt-d-interop"></a> for a sample <a>Document Instance</a> that follows the recommendations
         of this section.</p>
       </section>
+
     </section>
 
     <section id='style-resolution-procedure'>
@@ -3883,9 +3884,10 @@ <h2>Compatibility with other TTML-based specifications</h2>
       <h3>Overview</h3>
 
       <p>This specification is designed to be compatible with [[ttml-imsc1]], [[ttml-imsc1.0.1]], [[ttml-imsc1.1]],
-      [[ttml-imsc1.2]], [[SMPTE2052-1]], [[EBU-TT-D]] and [[ttml10-sdp-us]]. Specifically, by selecting a subset of the features and
+      [[ttml-imsc1.2]], [[SMPTE2052-1]], [[EBU-TT-D]], [[ttml10-sdp-us]]
+      and [[dapt]]. Specifically, by selecting a subset of the features and
       extensions defined in this specification, it is possible to create a document that:conforms to one or more of [[ttml-imsc1]],
-      [[ttml-imsc1.0.1]], [[ttml-imsc1.1]], [[ttml-imsc1.2]], [[SMPTE2052-1]], [[EBU-TT-D]] or [[ttml10-sdp-us]], and also conforms
+      [[ttml-imsc1.0.1]], [[ttml-imsc1.1]], [[ttml-imsc1.2]], [[SMPTE2052-1]], [[EBU-TT-D]], [[ttml10-sdp-us]] or [[dapt]], and also conforms
       to <a>Text Profile</a>.</p>
 
       <p>This specification is also intended to allow straightforward conversion of a document that conforms to the text profile of
@@ -3999,6 +4001,77 @@ <h3>CFF-TT</h3>
       such as extracting text content from images.</p>
     </section>
 
+    <section class="appendix" id="dapt-interop">
+      <h3>DAPT</h3>
+
+      <p>It is possible for a <a>Document Instance</a> also to be a
+        <a data-cite="dapt#dfn-dapt-document">DAPT document</a> by meeting the conformance requirements of
+        both.</p>
+
+      <p>The DAPT <a data-cite="dapt#extension-serialization"><code>#serialization</code></a>
+        feature is effectively a superset of the <a href="#document-encoding"></a>
+        constraints.
+      </p>
+
+      <p><a href="#foreign-elements"></a> allows
+        vocabulary defined by other profiles, including [[dapt]],
+        for example metadata, to be present within a <a>Document Instance</a>;
+        similarly, [[dapt]] allows vocabulary defined herein
+        to be present within a <a data-cite="dapt#dfn-dapt-document">DAPT document</a>.
+      </p>
+
+      <p><a href="#resources-constraints"></a> prohibits embedded audio
+        within <a>Document Instances</a>.
+        A <a data-cite="dapt#dfn-dapt-document">DAPT document</a> that uses this feature
+        can therefore not be a conformant <a>Document Instance</a>.</p>
+
+      <section id="dapt-signaling">
+        <h4>Signaling conformance to DAPT</h4>
+
+        <p>A document conforming to this specification and to [[dapt]]
+          signals its conformance to both by
+          including in the <code>ttp:contentProfiles</code> attribute
+          both the designators for <a>Text Profile</a> and [=DAPT 1.0 Content Profile=],
+          in addition to any other profiles to which the document conforms.
+        </p>
+      </section>
+
+      <section>
+        <h4>Using DAPT metadata in subtitle and caption workflows</h4>
+
+        <p>Subtitle and caption authoring workflows that begin with a
+          [[dapt]] transcription stage, and optional translation stages,
+          can use the DAPT metadata to direct the
+          production or presentation of IMSC Text profile documents.
+          For example:</p>
+
+        <ul>
+          <li>speaker (<a data-cite="dapt#dfn-character">Character</a>)
+            data can be used to apply styling or to insert content 
+            that indicates changes of speaker, such as prefixing text with
+            commonly used change of speaker symbols, or with the
+            name of the speaker.</li>
+          <li>representation data (i.e. metadata that
+            <a data-cite="dapt#dfn-content-descriptor">describes what content</a> in
+            the <a>Related Video Object</a> the text content represents) can be
+            used to filter or select sub-sets of the text content, for example
+            to include or exclude non-dialogue sound captions.</li>
+          <li>language and <a data-cite="dapt#dfn-text-language-source">Text language source</a>
+            metadata can be used to generate
+            translation subtitle documents including <a data-cite="dapt#dfn-text">Text</a>
+            that has been translated into the desired language.</li>
+          <li>language and <a data-cite="dapt#dfn-text-language-source">Text language source</a>
+            metadata can be used to identify
+            subtitles that are <a data-cite="dapt#dfn-translation">Translations</a>,
+            either to flag as
+            <a href="#forced-content">forced content</a> or to trigger
+            text to speech for subtitles that are translated, where appropriate
+            to meet the user's preferences, a practice known as
+            "spoken subtitles".</li>
+        </ul>
+      </section>
+    </section>
+
     <!-- Preserves links to document fragments made to previous versions of IMSC through IMSC's undated URL, e.g.,
     https://www.w3.org/TR/ttml-imsc/#image-profile-designator -->
     <div id="image-profile-constraints"></div>