Skip to content

Commit

Permalink
Merge pull request #154 from w3c/issue-111
Browse files Browse the repository at this point in the history
Addresses #111 ("Need algorithm to determine profile in absence of ttp:profile property")
  • Loading branch information
palemieux committed Feb 11, 2016
2 parents 8eaffc8 + c67e42f commit f227c28
Showing 1 changed file with 37 additions and 0 deletions.
37 changes: 37 additions & 0 deletions spec/ttml-ww-profiles.html
Expand Up @@ -117,6 +117,10 @@ <h2>Terms and Definitions</h2>

<p><dfn>Document Instance</dfn>. See Section 2.2 at [[!TTML1]].</p>

<p><dfn>Document Interchange Context</dfn>. See Section 2.2 at [[!TTML1]].</p>

<p><dfn>Document Processing Context</dfn>. See Section 2.2 at [[!TTML1]].</p>

<p><dfn>Intermediate synchronic document</dfn>. See Section 9.3.2 at [[!TTML1]].</p>

<p><dfn>Processor</dfn>. Either a <a>Presentation processor</a> or a <a>Transformation processor</a>.</p>
Expand Down Expand Up @@ -212,6 +216,39 @@ <h3>Image Profile</h3>

<p>The <dfn>Image Profile</dfn> consists of Sections <a href="#common-constraints"></a> and <a href=
"#image-profile-constraints"></a>.</p>
</section>


<section>
<h3>Profile Resolution Semantics</h3>


<p>For the purpose of content processing, the determination of the resolved
profile SHOULD take into account both the signaled profile, as defined
in <a href="#profile-signaling"></a>, and profile metadata, as designated by either (or both)
the <a>Document Interchange Context</a> or (and) the <a>Document Processing
Context</a>, which MAY entail inspecting document content.</p>

<p>If the resolved profile is not a profile supported by the <a>Processor</a>
but is feasibly interoperable with the <a>Text Profile</a>, then the resolved
profile is the <a>Text Profile</a>; otherwise, if the resolved profile is not
a profile supported by the <a>Processor</a> but is feasibly interoperable with
the <a>Image Profile</a>, then the resolved profile is the <a>Image Profile</a>.</p>


<p>If the resolved profile is a profile supported by the <a>Processor</a>, then
the <a>Processor</a> SHOULD process the <a>Document Instance</a> according to the
resolved profile. If the resolved profile is neither <a>Text Profile</a> nor
<a>Image Profile</a>, processing is outside the scope of this specification.</p>


<p>If the resolved profile is undetermined or not supported by the
<a>Processor</a>, then the <a>Processor</a> SHOULD nevertheless process the <a>Document
Instance</a> using one of its supported profiles, with a preference for the
<a>Text Profile</a> over the <a>Image Profile</a>; otherwise, processing MAY be
aborted.</p>


</section>
</section>

Expand Down

0 comments on commit f227c28

Please sign in to comment.