Merge pull request #1151 from w3c/issue-1150-absolutize

Define and reference inline term absolutize (#1150).

spec/ttml2.xml

@@ -2936,8 +2936,9 @@ When defined internally (inline), a profile is referenced either implicitly
 or by means of a <loc href="#content-value-fragment-profile-designator">&lt;fragment-profile-designator&gt;</loc> expression.</p>
 <p>A profile designator must adhere to the <loc href="#content-value-uri">&lt;uri&gt;</loc> value syntax.
 If the profile designator is expressed as a relative URI,
-then it must be absolutized by using the TT Profile Namespace value as
-the base URI.</p>
+then it must be <termref def="defs-absolutize">absolutized</termref> by using the TT Profile Namespace value as
+the base URI, and where the term <termdef id="defs-absolutize" term=""><term>absolutize</term></termdef> means
+resolving a relative URL to an absolute URL as described by <bibref ref="uri"/>, &sect;5.</p>
 <p>All profile designators which have the TT Profile Namespace as a prefix but are otherwise not listed in <specref ref="profile-vocab-table"/>
 or in <bibref ref="ttpr"/>, &sect;4, <emph>Registry</emph>, are reserved for future standardization, and must not appear in a conformant
 <loc href="#terms-document-instance">document instance</loc>. Nothwithstanding this constraint, a profile designator is not restricted to the set of designators enumerated
@@ -4352,7 +4353,7 @@ feature namespace value expressed by the
 <att>xml:base</att> attribute of the
 nearest ancestor <el>ttp:features</el> element, it must express an
 absolute URI.  In either case (original absolute URI or resulting
-absolutized URI), the URI expressed by the <el>ttp:feature</el>
+<termref def="defs-absolutize">absolutized</termref> URI), the URI expressed by the <el>ttp:feature</el>
 element must further adhere to the syntax of a feature designation as
 defined by <specref ref="feature-designations"/>, and, furthermore,
 the specific designation that appears in this URI, i.e., the portion of the feature designation
@@ -4558,7 +4559,7 @@ extension namespace value expressed by the
 <att>xml:base</att> attribute of the
 nearest ancestor <el>ttp:extensions</el> element, it must express an
 absolute URI.  In either case (original absolute URI or resulting
-absolutized URI), the URI expressed by the <el>ttp:extension</el>
+<termref def="defs-absolutize">absolutized</termref> URI), the URI expressed by the <el>ttp:extension</el>
 element must further adhere to the syntax of an extension designation as
 defined by <specref ref="extension-designations"/>,
 while the URI expressed by the <att>extends</att> attribute and (or) the
@@ -4729,8 +4730,8 @@ designator
 </table>
 <p>If the list of designators is enclosed in the function syntax <code>all(...)</code> or no function syntax is used,
 then conformance is claimed with all designated <loc href="#terms-content-profile">content profiles</loc>.</p>
-<p>If multiple designators are specified, then the absolutized form of each designator must be distinct; that is,
-after converting to absolutized form, duplicate designators are not permitted.</p>
+<p>If multiple designators are specified, then the <termref def="defs-absolutize">absolutized</termref> form of each designator must be distinct; that is,
+after converting to <termref def="defs-absolutize">absolutized</termref> form, duplicate designators are not permitted.</p>
 <p>A <att>ttp:contentProfiles</att>
 attribute is considered to be significant only when specified on the
 <el>tt</el> element.</p>
@@ -5090,8 +5091,8 @@ designator
 then support is required for all designated <loc href="#terms-processor-profile">processor profiles</loc>. If the list
 of designators is enclosed in the function syntax <code>any(...)</code>, then support is required for at least one
 of the designated <loc href="#terms-processor-profile">processor profiles</loc>.</p>
-<p>If multiple designators are specified, then the absolutized form of each designator must be distinct; that is,
-after converting to absolutized form, duplicate designators are not permitted.</p>
+<p>If multiple designators are specified, then the <termref def="defs-absolutize">absolutized</termref> form of each designator must be distinct; that is,
+after converting to <termref def="defs-absolutize">absolutized</termref> form, duplicate designators are not permitted.</p>
 <p>A <att>ttp:processorProfiles</att>
 attribute is considered to be significant only when specified on the
 <el>tt</el> element.</p>
@@ -7067,7 +7068,7 @@ when constructing a <loc href="#terms-reduced-xml-infoset">reduced xml infoset</
 <div3 id="content-value-relative-profile-designator">
 <head>&lt;relative-profile-designator&gt;</head>
 <p>A &lt;relative-profile-designator&gt; value expression is used to refer to a standardized profile with respect to
-the TT Profile Namespace, which serves as the base URI with which relative profile designators are absolutized.</p>
+the TT Profile Namespace, which serves as the base URI with which relative profile designators are <termref def="defs-absolutize">absolutized</termref>.</p>
 <table id="relative-profile-designator-value-expression-syntax" role="syntax">
 <caption>Syntax Representation &ndash; &lt;relative-profile-designator&gt;</caption>
 <tbody>
@@ -7083,7 +7084,7 @@ the TT Profile Namespace, which serves as the base URI with which relative profi
 </table>
 <note role="example">
 <p>For example, if a relative profile designator is expressed as
-<code>ttml2-presentation</code>, then the absolutized profile designator
+<code>ttml2-presentation</code>, then the <termref def="defs-absolutize">absolutized</termref> profile designator
 would be
 <code>http://www.w3.org/ns/ttml/profile/ttml2-presentation</code>.</p>
 </note>