Skip to content

Commit

Permalink
Address #271
Browse files Browse the repository at this point in the history
* Make `daptm:descType` a defined term
* Permit user-defined values for `daptm:descType` as long as they are prefixed with `x-`
* Require that no key in the registry table begins with `x-`
* Add the TTML Metadata prefix `ttm:` to the Namespaces table
* Sort the TTML namespaces to have the same order as in the TTML2 specificaiton
* Define the `#descType` extension feature, and mark its disposition as Permitted.
  • Loading branch information
nigelmegitt committed Dec 10, 2024
1 parent 3e51f2a commit 5173629
Show file tree
Hide file tree
Showing 3 changed files with 40 additions and 8 deletions.
46 changes: 38 additions & 8 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1609,13 +1609,15 @@ <h4>Script Event Description</h4>
<p>Each <a>Description Type</a> is represented in a <a>DAPT Document</a> by
a <code>daptm:descType</code> attribute on the <code>&lt;ttm:desc&gt;</code> element.</p>
<p>The <code>&lt;ttm:desc&gt;</code> element MAY have zero or one <code>daptm:descType</code> attributes.
The <code>daptm:descType</code> attribute is defined below.</p>
The <dfn><code>daptm:descType</code></dfn> attribute is defined below.</p>
<div class="exampleInner">
<pre class="language-abnf">
daptm:descType : string
</pre>
</div>
<p>Its permitted values are listed in the following <a>registry table</a>:</p>
<p>The permitted values for <code>daptm:descType</code> are either
those listed in the following <a>registry table</a>,
or can be user-defined:</p>
<div class="registry-table-section">
<table class="data">
<caption><a>Registry table</a> for the <code>daptm:descType</code> attribute
Expand Down Expand Up @@ -1648,6 +1650,7 @@ <h4>Script Event Description</h4>
</tbody>
</table>
</div>
<p>Valid user-defined values MUST begin with <code>x-</code>.</p>
<pre class="example"
data-include="examples/event-desc-descType.xml"
data-include-format="text">
Expand Down Expand Up @@ -2120,6 +2123,7 @@ <h3>Namespaces</h3>
<td><code>http://www.w3.org/XML/1998/namespace</code></td>
<td>[[xml-names]]</td>
</tr>
<!-- TTML Namespaces are ordered the same as in the TTML2 Specification -->
<tr>
<td>TT</td>
<td><code>tt</code></td>
Expand All @@ -2132,18 +2136,24 @@ <h3>Namespaces</h3>
<td><code>http://www.w3.org/ns/ttml#parameter</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>TT Feature</td>
<td>none</td>
<td><code>http://www.w3.org/ns/ttml/feature/</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>TT Audio Style</td>
<td><code>tta</code></td>
<td><code>http://www.w3.org/ns/ttml#audio</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>TT Metadata</td>
<td><code>ttm</code></td>
<td><code>http://www.w3.org/ns/ttml#metadata</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>TT Feature</td>
<td>none</td>
<td><code>http://www.w3.org/ns/ttml/feature/</code></td>
<td>[[TTML2]]</td>
</tr>
<tr>
<td>DAPT Metadata</td>
<td><code>daptm</code></td>
Expand Down Expand Up @@ -3588,6 +3598,13 @@ <h4>Disposition of Features and Extensions</h4>
This is the profile expression of <a href="#dapt-origin-timecode"></a>.
</td>
</tr>
<tr>
<td><a href="#extension-descType"><code>#descType</code></a></td>
<td><span class="permitted label">permitted</span></td>
<td>
This is the profile expression of <a><code>daptm:descType</code></a>.
</td>
</tr>
<tr>
<td><a href="#extension-onScreen"><code>#onScreen</code></a></td>
<td><span class="permitted label">permitted</span></td>
Expand Down Expand Up @@ -3778,6 +3795,18 @@ <h3 id="extension-daptOriginTimecode">#daptOriginTimecode</h3>
<p>No <a>presentation processor</a> behaviour is defined for the <code>#daptOriginTimecode</code> extension.</p>
</section>

<section>
<h3 id="extension-descType">#descType</h3>
<p>A <a>transformation processor</a> supports the <code>#descType</code> extension if
it recognizes and is capable of transforming values of the
<a><code>daptm:descType</code></a> attribute
on the <code>&lt;ttm:desc&gt;</code> element.</p>

<p>A <a>presentation processor</a> supports the <code>#descType</code> extension if
it implements presentation semantic support of the
<a><code>daptm:descType</code></a> attribute on the <code>&lt;ttm:desc&gt;</code> element.</p>
</section>

<section>
<h3 id="extension-onScreen">#onScreen</h3>
<p>A <a>transformation processor</a> supports the <code>#onScreen</code> extension if
Expand Down Expand Up @@ -4144,6 +4173,7 @@ <h3><code>daptm:descType</code> registry table definition</h3>
<p>The <a>key</a> is the &quot;<code>daptm:descType</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-description"></a>.</p>
<p>The <a>key</a> values for this <a>registry table</a> MUST NOT begin with <code>x-</code> which is reserved for user extensions.</p>
</section>

<section id="registry-table-content-descriptor">
Expand Down
1 change: 1 addition & 0 deletions profiles/dapt-content-profile.xml
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,7 @@
<!-- optional (voluntary) extension support -->
<extension value="optional">#agent</extension>
<extension value="optional">#daptOriginTimecode</extension>
<extension value="optional">#descType</extension>
<extension value="optional">#onScreen</extension>
<extension value="optional">#scriptEventGrouping</extension>
<extension value="optional">#scriptEventMapping</extension>
Expand Down
1 change: 1 addition & 0 deletions profiles/dapt-processor-profile.xml
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,7 @@
<extension value="required">#agent</extension>
<extension value="required">#contentProfiles-root</extension>
<extension value="required">#daptOriginTimecode</extension>
<extension value="required">#descType</extension>
<extension value="required">#onScreen</extension>
<extension value="required">#represents</extension>
<extension value="required">#scriptEventGrouping</extension>
Expand Down

0 comments on commit 5173629

Please sign in to comment.