Skip to content

Commit

Permalink
Add <content-descriptor> registry table
Browse files Browse the repository at this point in the history 
Also tidy up some section ordering and some wording.
  • Loading branch information
@nigelmegitt
nigelmegitt committed Mar 28, 2024
1 parent 5bef65e commit 22c4bc8
Showing 1 changed file with 88 additions and 32 deletions.
120 changes: 88 additions & 32 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -542,31 +542,77 @@ <h3>DAPT Script</h3>
and, for <a>Dubbing Scripts</a>, <a>Characters</a>.</p>
<p>A <dfn>DAPT Document</dfn> is a TTML <a>Document Instance</a> representing a <a>DAPT Script</a>.
A <a>DAPT Document</a> has the structure and constraints defined in the following sections.</p>
<section>

<section>
<h4>Represents</h4>
<p>The <dfn>Represents</dfn> property is a mandatory property of a <a>DAPT Script</a> which
indicates which components of the <a>related media object</a>
the contents of the document provide an alternative for.
the contents of the document represent.
The contents of the document could be used as part of a mechanism
to provide an accessible alternative for those components.
</p>
<p>To represent this property, the <dfn><code>daptm:represents</code></dfn> attribute MUST be present on the <code>&lt;tt&gt;</code> element:</p>
<div class="exampleInner">
<pre class="language-abnf">
daptm:represents
: &lt;content-descriptor&gt; ( &lt;lwsp&gt;? "," &lt;lwsp&gt;? &lt;content-descriptor&gt;)*

&lt;content-descriptor&gt;
: "dialogue"
| "nonDialogueSounds"
| "visualNonText"
| "visualText"
&lt;content-descriptor&gt; # see registry table below

&lt;lwsp&gt; # as TTML2
&lt;lwsp&gt; # as TTML2
</pre>
</div>
<p>For example, a dubbing script would have <code>daptm:represents=&quot;dialogue&quot;</code>,
an audio description script would have <code>daptm:represents=&quot;visualNonText, visualText&quot;</code>,
and a post-production script that could be the precursor to a hard of hearing subtitle document
would have <code>daptm:represents=&quot;dialogue, nonDialogueSounds&quot;</code>.</p>
<p>The permitted values for <code>&lt;content-descriptor&gt;</code>
are listed in the following <a>registry table</a>:</p>
<div class="registry-table-section">
<table class="data">
<caption><a>Registry table</a> for the <code>&lt;content-descriptor&gt;</code> component
whose Registry Definition is at <a href="#registry-table-content-descriptor"></a></caption>
<thead>
<th><code>&lt;content-descriptor&gt;</code></th>
<th>Status</th>
<th>Description</th>
<th>Used in</th>
<th>Notes</th>
</thead>
<tbody>
<tr>
<td><code>dialogue</code></td>
<td>Provisional</td>
<td>Verbal communication, in audio</td>
<td>Dubbing, translation and hard of hearing subtitles and captions, pre- and post- production scripts</td>
<td>For example, a spoken conversation.</td>
</tr>
<tr>
<td><code>nonDialogueSounds</code></td>
<td>Provisional</td>
<td>Sounds that are not verbal communication, in audio</td>
<td>Translation and hard of hearing subtitles and captions, pre- and post- production scripts</td>
<td>For example, significant sounds, such as a door being slammed in anger.</td>
</tr>
<tr>
<td><code>visualNonText</code></td>
<td>Provisional</td>
<td>Parts of the visual image that are not textual</td>
<td>Audio Description</td>
<td>For example, a significant object in the scene</td>
</tr>
<tr>
<td><code>visualText</code></td>
<td>Provisional</td>
<td>Textual parts of the visual image</td>
<td>Audio Description</td>
<td>For example, a signpost, a clock, a newspaper headline, an instant message etc.</td>
</tr>
</tbody>
</table>
</div>
<aside class="example">
<p>A dubbing script might have <code>daptm:represents=&quot;dialogue&quot;</code>;</p>
<p>An audio description script might have <code>daptm:represents=&quot;visualNonText, visualText&quot;</code>;</p>
<p>A post-production script that could be the precursor to a hard of hearing subtitle document
might have <code>daptm:represents=&quot;dialogue, nonDialogueSounds&quot;</code>.</p>
</aside>
</section>

<section>
Expand Down Expand Up @@ -2896,7 +2942,26 @@ <h3>#profile-root</h3>
it implements presentation semantic support of the
<a><code>ttp:profile</code></a> attribute on the <code>&lt;tt&gt;</code> element.</p>
</section>

<section>
<h3>#represents-root</h3>
<p>A <a>transformation processor</a> supports the <code>#represents-root</code> extension if
it recognizes and is capable of transforming values of the
<a><code>daptm:represents</code></a> attribute on the <code>&lt;tt&gt;</code> element.</p>

<p>A <a>presentation processor</a> supports the <code>#represents-root</code> extension if
it implements presentation semantic support of the
<a><code>daptm:represents</code></a> attribute on the <code>&lt;tt&gt;</code> element.</p>

<p>An example of a <a>transformation processor</a> that supports this extension is
a validating processor that reports an error if the extension is required by a
<a>content profile</a> but the <a>Document Instance</a> claiming
conformance to that profile either does not have a
<a><code>daptm:represents</code></a> attribute on the <code>&lt;tt&gt;</code> element
or has one whose value is not conformant with the requirements defined herein.</p>

</section>

<section>
<h3>#scriptType-root</h3>
<p>A <a>transformation processor</a> supports the <code>#scriptType-root</code> extension if
Expand Down Expand Up @@ -2963,25 +3028,6 @@ <h3>#textLanguageSource</h3>
<a><code>daptm:langSrc</code></a> attribute.</p>
</section>

<section>
<h3>#represents-root</h3>
<p>A <a>transformation processor</a> supports the <code>#represents-root</code> extension if
it recognizes and is capable of transforming values of the
<a><code>daptm:represents</code></a> attribute on the <code>&lt;tt&gt;</code> element.</p>

<p>A <a>presentation processor</a> supports the <code>#represents-root</code> extension if
it implements presentation semantic support of the
<a><code>daptm:represents</code></a> attribute on the <code>&lt;tt&gt;</code> element.</p>

<p>An example of a <a>transformation processor</a> that supports this extension is
a validating processor that reports an error if the extension is required by a
<a>content profile</a> but the <a>Document Instance</a> claiming
conformance to that profile either does not have a
<a><code>daptm:represents</code></a> attribute on the <code>&lt;tt&gt;</code> element
or has one whose value is not conformant with the requirements defined herein.</p>

</section>

<section>
<h3>#xmlId-div</h3>
<p>A <a>transformation processor</a> supports the <code>#xmlId-div</code> extension if
Expand Down Expand Up @@ -3204,8 +3250,18 @@ <h3><code>daptm:eventType</code> registry table definition</h3>
<p>The <a>key</a> is the &quot;<code>daptm:eventType</code>&quot; field.
The &quot;description&quot; field describes the intended purpose of each value.</p>
<p>The <a>registry entries</a> for this <a>registry table</a> are located in <a href="#script-event-type"></a>.</p>
</section>
<section id="registry-table-content-descriptor">
<h3><code>&lt;content-descriptor&gt;</code> registry table definition</h3>
<p>The <a>registry table</a> for <code>&lt;content-descriptor&gt;</code> defines a set of values that can be
used in the <code>daptm:represents</code> attribute.</p>
<p>The <a>key</a> is the &quot;<code>&lt;content-descriptor&gt;</code>&quot; field.
The &quot;Description&quot; field describes the type of media content represented by each value.
The &quot;Used in&quot; field describes the type of script in which the content type
described are commonly found.</p>
<p>The <a>registry entries</a> for this <a>registry table</a> are located in <a href="#represents"></a>.</p>
</section>
</section>
</section>
</section>

<section class="appendix">
Expand Down

0 comments on commit 22c4bc8

Please sign in to comment.