- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Thu, 06 Jun 2013 09:56:56 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv26176
Modified Files:
its20-for-editing-sec1-sec2.html
its20-for-editing-sec1-sec2.odd its20.html its20.odd
Log Message:
update of sec. 2 in sec1-2.odd and added ed. note in its20.odd
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/03 20:36:27 1.11
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/06 09:56:55 1.12
@@ -31,8 +31,11 @@
<div class="toc1">2 <a href="#basic-concepts" shape="rect">Basic Concepts</a><div class="toc2">2.1 <a href="#basic-concepts-selection" shape="rect">Selection</a><div class="toc3">2.1.1 <a href="#basic-concepts-selection-local" shape="rect">Local Approach</a></div>
<div class="toc3">2.1.2 <a href="#basic-concepts-selection-global" shape="rect">Global Approach</a></div>
</div>
-<div class="toc2">2.2 <a href="#basic-concepts-overinher" shape="rect">Overriding and Inheritance</a></div>
+<div class="toc2">2.2 <a href="#basic-concepts-overinher" shape="rect">Overriding, Inheritance and Defaults</a></div>
<div class="toc2">2.3 <a href="#basic-concepts-addingpointing" shape="rect">Adding Information or Pointing to Existing Information</a></div>
+<div class="toc2">2.4 <a href="#mapping-conversion" shape="rect">Mapping and conversion</a></div>
+<div class="toc2">2.5 <a href="#tools-information" shape="rect">ITS Tools Annotation</a></div>
+<div class="toc2">2.6 <a href="#implementing-its20" shape="rect">Implementing ITS 2.0</a></div>
</div>
<div class="toc1">3 <a href="#notation-terminology" shape="rect">Notation and Terminology</a><div class="toc2">3.1 <a href="#notation" shape="rect">Notation</a></div>
<div class="toc2">3.2 <a href="#def-datacat" shape="rect">Data category</a></div>
@@ -53,9 +56,9 @@
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors" shape="rect">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage" shape="rect">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2228" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2352" shape="rect">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2473" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2597" shape="rect">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param" shape="rect">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules" shape="rect">Link to External Rules</a></div>
@@ -477,7 +480,8 @@
id information conveyed via a global <code class="its-elem-markup">idValueRule</code>.</p></li><li><p>The <a href="#elements-within-text" shape="rect">Elements within Text</a> data category has a set of HTML
elements defined as <a href="http://www.w3.org/TR/html51/dom.html#phrasing-content-1" shape="rect">phrasing content</a>. In the absence of an
<a href="#elements-within-text" shape="rect">Elements within Text</a> local attribute or global rules selecting the
- element in question, these elements are always interpreted as <code>withinText="yes"</code> by default, except for the elements <code class="its-elem-markup">iframe</code>, <code class="its-elem-markup">noscript</code>, <code class="its-elem-markup">script</code>
+ element in question, these elements are always interpreted as
+ <code>withinText="yes"</code> by default, except for the elements <code class="its-elem-markup">iframe</code>, <code class="its-elem-markup">noscript</code>, <code class="its-elem-markup">script</code>
and <code class="its-elem-markup">textarea</code> which are interpreted as <code>withinText="nested"</code>.</p></li><li><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category has a direct counterpart in
<a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, namely the HTML5
<code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute" shape="rect">the HTML5 definition</a>. The <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> definition also applies to nodes selected via global rules. That is, a <code class="its-elem-markup">translateRule</code> like <code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-and-existing-HTML5-markup" id="EX-its-and-existing-HTML5-markup" shape="rect"/>Example 6: The <a href="#language-information" shape="rect">Language Information</a>, <a href="#idvalue" shape="rect">Id Value</a>,
@@ -524,22 +528,22 @@
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.4.7 Extended implementation hints</h4><p>tbd</p></div></div></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts" id="basic-concepts" shape="rect"/>2 Basic Concepts</h2><p>
<em>This section is informative.</em>
- </p><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection" id="basic-concepts-selection" shape="rect"/>2.1 Selection</h3><p>Information (e.g. "translate this") captured by ITS markup (e.g.
- <code>its:translate='yes'</code>) always pertains to one or more XML or HTML nodes,
- primarily element and attribute nodes, as defined in <a title="XML Path Language (XPath)
 Version 1.0" href="#xpath" shape="rect">[XPath 1.0]</a>. In
- a sense, ITS markup “selects” the relevant node(s). Selection may be explicit or
+ </p><p>The purpose of this section is to provide basic knowledge about how ITS 2.0 “works”. The underlying formal definitions are given in the subsequent sections.</p><p>A key concept of ITS is the abstract notion of <a href="#def-datacat" shape="rect">data categories</a>. Data categories define the information that can be conveyed via ITS. An example is the <a href="#trans-datacat" shape="rect">Translate</a> data category. It conveys information about translatability of conent.</p><p>
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> provides the definition of data categories. It also provides their implementation, that is: ways to use the data categories. The motivation for separating data category definition from their implementation is to allow for flexibility: data categories can be implemented </p><ul><li><p>in various types of content (XML in general or <a href="#specific-HTML-support" shape="rect">HTML</a>).</p></li><li><p>for a single piece of markup, e.g. a <code>p</code> element. This is the so-called <a href="#basic-concepts-selection-local" shape="rect">local approach</a>.</p></li><li><p>for several pieces of markup in one or a set of documents. This is the so-called <a href="#basic-concepts-selection-global" shape="rect">global approach</a>.</p></li><li><p>For a complete markup vocabulary by adding <a href="#its-schemas" shape="rect">ITS markup declarations</a> to the underlying schema.</p></li></l><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection" id="basic-concepts-selection" shape="rect"/>2.1 Selection</h3><p>Information (e.g. "translate this") captured by ITS data categories (e.g.
+ “translate this piece of content”) always pertains to one or more XML or HTML nodes,
+ primarily element and attribute nodes. In
+ a sense, ITS “selects” the relevant node(s). Selection may be explicit or
implicit. ITS distinguishes two approaches to selection: (1) local, and (2) using global
rules.</p><p>The mechanisms defined for ITS selection resemble those defined in <a title="Cascading Style Sheets,
 level 2 revision 1 CSS 2.1 Specification" href="#css2-1" shape="rect">[CSS 2.1]</a>. The local approach can be compared to the
<code>style</code> attribute in HTML/XHTML, and the approach with global rules is
similar to the <code>style</code> element in HTML/XHTML. ITS usually uses XPath for
identifying nodes although CSS Selectors and other query languages can be used if
- supported by the application. Thus,</p><ul><li><p>the local approach puts ITS markup in the relevant element of the host vocabulary
+ supported by the application.</p><ul><li><p>the local approach puts ITS markup in the relevant element of the markup host vocabulary
(e.g. the <code>author</code> element in DocBook)</p></li><li><p>the <a href="#selection-global" shape="rect">rule-based, global approach</a> puts the ITS
- markup in elements defined by ITS itself (namely the <code class="its-elem-markup">rules</code> element)</p></li></ul><p>ITS markup can be used with XML documents (e.g. a DocBook article), or schemas (e.g. an
+ markup in elements defined by ITS itself (namely the <code class="its-elem-markup">rules</code> element)</p></li></ul><p>ITS markup can be used with XML documents (e.g. a DocBook article), HTML documents, or schemas (e.g. an
XML Schema document for a proprietary document format).</p><p>The following two examples sketch the distinction between the local and global
- approaches, using the <code class="its-attr-markup">translate</code> as one example of ITS
- markup.</p><div class="div3">
+ approaches, using the <a href="#trans-datacat" shape="rect">Translate</a> data category as one example.</p><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"/>2.1.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 7</a> shows how a content
author may use the ITS <code class="its-attr-markup">translate</code> attribute to indicate that
all content inside the <code>author</code> element should be protected from
@@ -561,11 +565,12 @@
<strong class="hl-tag" style="color: #000096"></info></strong>
<strong class="hl-tag" style="color: #000096"><para></strong>This is a short article.<strong class="hl-tag" style="color: #000096"></para></strong>
<strong class="hl-tag" style="color: #000096"></article></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-1.xml" shape="rect">examples/xml/EX-basic-concepts-1.xml</a>]</p></div><p>For this example to work, the schema developer will need to add the <code class="its-attr-markup">translate</code> attribute to the schema as a common attribute or on all the
+</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-1.xml" shape="rect">examples/xml/EX-basic-concepts-1.xml</a>]</p></div><p>For this example to work for a whole markup vocabulary, the schema developer will need to add the <code class="its-attr-markup">translate</code> attribute to the schema as a common attribute or on all the
relevant element definitions. Note how there is an expectation in this case that
- inheritance plays a part in identifying which content does have to be translated and
+ <a href="#basic-concepts-overinher" shape="rect">inheritance</a> plays a part in identifying which content does have to be translated and
which does not. Tools that process this content for translation will need to implement
- the expected inheritance.</p><p id="local-approach-not-applicable-to-attributes">The local approach cannot be applied on a particular attribute. It can be applied for the content of the current element and all its inherited nodes as described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p></div><div class="div3">
+ the expected inheritance.</p><p id="local-approach-not-applicable-to-attributes">For XML content, the local approach cannot be applied on a particular attribute.
+ It can be applied for the content of the current element and all its inherited nodes as described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>. For the <a href="#trans-datacat" shape="rect">Translate</a> data category used in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, this is different, see the explanation of the <a href="#translate-in-html5" shape="rect">HTML5 definition of Translate</a>.</p></div><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"/>2.1.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 8</a> shows a different
approach to identifying non-translatable content, similar to that used with a
<code>style</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>, but using an
@@ -575,8 +580,9 @@
example <code class="its-elem-markup">translateRule</code>). Each of these specific elements contains a
<code class="its-attr-markup">selector</code> attribute. As its name suggests, this attribute selects the node
or nodes to which a corresponding ITS information pertains. The values of ITS selector
- attributes are XPath absolute location paths (or CSS Selectors if <a href="#queryLanguage" shape="rect">queryLanguage</a> is set to "css"). Information for the
- handling of namespaces in these path expressions is taken from namespace declarations
+ attributes are XPath absolute location paths (or CSS Selectors if <a href="#queryLanguage" shape="rect">queryLanguage</a> is set to "css"). Via the <a href="#its-param" shape="rect">param</a> element
+ variables can be provided and then be used in the selectors.</p><p>Information for the
+ handling of namespaces in XPath expressions is taken from namespace declarations
<a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> at the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 8: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><prolog></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>Using ITS<strong class="hl-tag" style="color: #000096"></title></strong>
@@ -605,12 +611,12 @@
local markup throughout a document (or documents, if the <code class="its-elem-markup">rules</code> element is
stored as an external entity)</p></li><li><p>ITS data categories can designate attribute values as well as elements.</p></li><li><p>It is possible to associate ITS markup with existing markup (for example the
<code>term</code> element in DITA)</p></li></ul><p>The commonality in both examples above is the markup <code>translate='no'</code>.
- This piece of ITS markup can be interpreted as follows:</p><ul><li><p>it pertains to the <a href="#trans-datacat" shape="rect">Translate</a> data category </p></li><li><p>the attribute <code class="its-attr-markup">translate</code> holds a value of "no"</p></li></ul><p>The ITS <code class="its-attr-markup">selector</code> attribute allows:</p><ul><li><p>ITS data category attributes to appear in global rules (even outside of an XML
- document or schema)</p></li><li><p>ITS data categories attributes to pertain to sets of XML nodes (for example all
+ This piece of ITS markup can be interpreted as follows:</p><ul><li><p>it pertains to the <a href="#trans-datacat" shape="rect">Translate</a> data category </p></li><li><p>the attribute <code class="its-attr-markup">translate</code> holds a value of "no"</p></li></ul><p>The ITS <code class="its-attr-markup">selector</code> attribute allows:</p><ul><li><p>ITS data category attributes to appear in global rules (even outside of an XML or HTML
+ document or schema)</p></li><li><p>ITS data categories attributes to pertain to sets of document nodes (for example all
<code>p</code> elements in an XML document)</p></li><li><p>ITS markup to pertain to attributes</p></li><li><p>ITS markup to <a href="#associating-its-with-existing-markup" shape="rect"> associate
with existing markup</a> (for example the <code>term</code> element in
DITA)</p></li></ul></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"/>2.2 Overriding and Inheritance</h3><p>The power of the ITS selection mechanisms comes at a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a>, and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a>, have to be established.</p><p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 9</a> shows how inheritance
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"/>2.2 Overriding, Inheritance and Defaults</h3><p>The power of the ITS selection mechanisms comes at a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a>, and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a>, have to be established.</p><p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 9</a> shows how inheritance
and overriding work for the <a href="#trans-datacat" shape="rect">Translate</a> data category.
By default elements are translatable. Here, the <code class="its-elem-markup">translateRule</code> element declared
in the header overrides the default for the <code>head</code> element inside
@@ -638,7 +644,7 @@
<strong class="hl-tag" style="color: #000096"></div></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></text></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-3.xml" shape="rect">examples/xml/EX-basic-concepts-3.xml</a>]</p></div></div><div class="div2">
+</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-3.xml" shape="rect">examples/xml/EX-basic-concepts-3.xml</a>]</p></div><p>For XML content, <a href="#datacategories-overview" shape="rect">data category specific defaults</a> are provided. These are independent of the actual XML markup vocabulary. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence, that HTML markup is normatively interpreted as ITS 2.0 data category information: See <a class="section-ref" href="#html5-existing-markup-versus-its" shape="rect">Section 1.4.1.3: Relation between HTML markup and ITS 2.0 data categories</a> for more information.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-addingpointing" id="basic-concepts-addingpointing" shape="rect"/>2.3 Adding Information or Pointing to Existing Information</h3><p>For some data categories, special attributes add or point to information about the
selected nodes. For example, the <a href="#locNote-datacat" shape="rect">Localization Note</a>
data category can add information to selected nodes (using a <code class="its-elem-markup">locNote</code> element),
@@ -646,7 +652,10 @@
<code class="its-attr-markup">locNotePointer</code> attribute).</p><p>The <a href="#datacategories-overview" shape="rect">data category overview table</a>, in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>, provides an overview of what
data categories allow to point to existing information or to add information.</p><p>The functionalities of adding information and pointing to existing information are
<em>mutually exclusive</em>. That is to say, attributes for pointing and adding
- the same information must not appear at the same rule element.</p></div></div><div class="div1">
+ the same information must not appear at the same rule element.</p></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-conversion" id="mapping-conversion" shape="rect"/>2.4 Mapping and conversion</h3><p>tbd - here <a class="section-ref" href="#mappings" shape="rect">Section 1.4.5: Mappings</a>.</p></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="tools-information" id="tools-information" shape="rect"/>2.5 ITS Tools Annotation</h3><p>tbd - here partially content of <a class="section-ref" href="#additional-mechanisms" shape="rect">Section 1.4.4: Additional or modified mechanisms</a>.</p></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="implementing-its20" id="implementing-its20" shape="rect"/>2.6 Implementing ITS 2.0</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer, see <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a>, targeted at different types of implementers.</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema" shape="rect">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> tell implementer how to process XML content applying ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-class-html5-its" shape="rect">Section 4.4: Conformance Class for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">Section 4.3: Conformance Type 3: Processing Expectatins for ITS Markup in HTML</a> make clear: what information needs to be made available for given pieces of markup then processing a dedicated ITS 2.0 data category? To allow for flexibility, an implementation can choose whether it wants to process only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in seperate conformances clauses and also in the <a href="@@@@" shape="rect">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only cover above aspect, that is: what information needs to be made available. They do not define how that information actually should be applied. This is due to the fact that there is a huge variety of usage scenarios of ITS 2.0, and a huge variety of tools for working with ITS 2.0. Each of these tools has their own way of using ITS 2.0 data categories. See <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a> for more information.</p><span class=editor-note">[Ed. note: Add link to test suite]</span></div></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="notation-terminology" id="notation-terminology" shape="rect"/>3 Notation and Terminology</h2><p>
<em>This section is normative.</em>
</p><div class="div2">
@@ -667,7 +676,7 @@
and localization of XML schemas and documents.] The concept of a data
category is independent of its implementation in an XML and HTML environment (e.g. using
an element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "implementation" subsections in
- <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1317" id="d0e1317" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1441" id="d0e1441" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
to whether a piece of content should be translated or not.</p><p>The simplest formalization of this prose description on a schema language independent
level is a <code class="its-attr-markup">translate</code> attribute with two possible values:
"yes" and "no". An implementation on a schema language specific
@@ -932,9 +941,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2228" id="d0e2228" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2352" id="d0e2352" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2239" id="d0e2239" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+<h5><a name="d0e2363" id="d0e2363" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
which starts with "<code>/</code>". That is, it must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a>s as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
@@ -979,14 +988,14 @@
implementations can be used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-and-attributes">CSS selectors have no ability to point to
attributes.</p></div><p>CSS Selectors are identified by <code>css</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2450" id="d0e2450" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2574" id="d0e2574" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Both simple selectors
and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2460" id="d0e2460" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2584" id="d0e2584" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Selector is not
evaluated against the complete document tree but only against subtrees rooted at
nodes selected by selector in the <code class="its-attr-markup">selector</code> attribute.</p></div></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2473" id="d0e2473" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2597" id="d0e2597" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
languages. For each additional query language the processor <a href="#rfc-keywords" shape="rect">MUST</a> define:</p><ul><li><p>identifier of query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating absolute selector to collection of nodes;</p></li><li><p>rules for evaluating relative selector to collection of nodes.</p></li></ul><p>Because future versions of this specification are likely to define additional query
languages, the following query language identifiers are reserved: <code>xpath</code>,
<code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
@@ -1647,7 +1656,8 @@
communicate notes to localizers about a particular item of content.</p><p>This data category can be used for several purposes, including, but not limited
to:</p><ul><li><p>Tell the translator how to translate parts of the content</p></li><li><p>Expand on the meaning or contextual usage of a specific element, such as what a
variable refers to or how a string will be used in the user interface</p></li><li><p>Clarify ambiguity and show relationships between items sufficiently to allow
- correct translation (e.g., in many languages it is impossible to translate the word"<span class="quote">enabled</span>" in isolation without knowing the gender, number and case of
+ correct translation (e.g., in many languages it is impossible to translate the word
+ "<span class="quote">enabled</span>" in isolation without knowing the gender, number and case of
the thing it refers to.)</p></li><li><p>Indicate why a piece of text is emphasized (important, sarcastic, etc.)</p></li></ul><p>Two types of informative notes are needed:</p><ul><li><p>An alert contains information that the translator must read before translating a
piece of text. Example: an instruction to the translator to leave parts of the text
in the source language.</p></li><li><p>A description provides useful background information that the translator will
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/03 20:36:27 1.13
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/06 09:56:55 1.14
@@ -579,22 +579,22 @@
in HTML markup. For theses data categories, ITS 2.0 defines the following specific
behaviour:</p>
<list type="unordered">
- <item>The <ref target="#language-information">Language Information</ref> data category has the HTML <code>lang</code>
+ <item><p>The <ref target="#language-information">Language Information</ref> data category has the HTML <code>lang</code>
attribute counterpart; in XHTML this is the <code>xml:lang</code> attribute. These attributes act as
local markup for the <ref target="#language-information">Language Information</ref> data category in HTML and
- take <ref target="#selection-precedence">precedence</ref> over language information conveyed via a global <gi>langRule</gi>.</item>
- <item>The <ref target="#idvalue">Id Value</ref> data category has the HTML or XHTML <code>id</code> attribute.
+ take <ref target="#selection-precedence">precedence</ref> over language information conveyed via a global <gi>langRule</gi>.</p></item>
+ <item><p>The <ref target="#idvalue">Id Value</ref> data category has the HTML or XHTML <code>id</code> attribute.
This attribute acts as local markup for the <ref target="#idvalue">Id Value</ref> data category in HTML and take <ref target="#selection-precedence">precedence</ref> over
- id information conveyed via a global <gi>idValueRule</gi>.</item>
- <item>The <ref target="#elements-within-text">Elements within Text</ref> data category has a set of HTML
+ id information conveyed via a global <gi>idValueRule</gi>.</p></item>
+ <item><p>The <ref target="#elements-within-text">Elements within Text</ref> data category has a set of HTML
elements defined as <ref target="http://www.w3.org/TR/html51/dom.html#phrasing-content-1">phrasing content</ref>. In the absence of an
<ref target="#elements-within-text">Elements within Text</ref> local attribute or global rules selecting the
element in question, these elements are always interpreted as
<code>withinText="yes"</code> by default, except for the elements <gi>iframe</gi>, <gi>noscript</gi>, <gi>script</gi>
- and <gi>textarea</gi> which are interpreted as <code>withinText="nested"</code>.</item>
- <item>The <ref target="#trans-datacat">Translate</ref> data category has a direct counterpart in
+ and <gi>textarea</gi> which are interpreted as <code>withinText="nested"</code>.</p></item>
+ <item xml:id="translate-in-html5"><p>The <ref target="#trans-datacat">Translate</ref> data category has a direct counterpart in
<ptr target="#html5" type="bibref"/>, namely the HTML5
- <code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <ref target="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">the HTML5 definition</ref>. The <ptr target="#html5" type="bibref"/> definition also applies to nodes selected via global rules. That is, a <gi>translateRule</gi> like <code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to <val>yes</val>.</item>
+ <code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <ref target="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">the HTML5 definition</ref>. The <ptr target="#html5" type="bibref"/> definition also applies to nodes selected via global rules. That is, a <gi>translateRule</gi> like <code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to <val>yes</val>.</p></item>
</list>
<exemplum xml:id="EX-its-and-existing-HTML5-markup">
<head>The <ref target="#language-information">Language Information</ref>, <ref target="#idvalue">Id Value</ref>,
@@ -771,14 +771,24 @@
<p>
<emph>This section is informative.</emph>
</p>
+
+ <p>The purpose of this section is to provide basic knowledge about how ITS 2.0 <q>works</q>. The underlying formal definitions are given in the subsequent sections.</p>
+
+ <p>A key concept of ITS is the abstract notion of <ref target="#def-datacat">data categories</ref>. Data categories define the information that can be conveyed via ITS. An example is the <ref target="#trans-datacat">Translate</ref> data category. It conveys information about translatability of conent.</p>
+
+ <p><ptr target="#datacategory-description" type="specref"/> provides the definition of data categories. It also provides their implementation, that is: ways to use the data categories. The motivation for separating data category definition from their implementation is to allow for flexibility: data categories can be implemented </p>
+ <list type="unordered"><item>in various types of content (XML in general or <ref target="#specific-HTML-support">HTML</ref>).</item>
+ <item>for a single piece of markup, e.g. a <code>p</code> element. This is the so-called <ref target="#basic-concepts-selection-local">local approach</ref>.</item>
+ <item>for several pieces of markup in one or a set of documents. This is the so-called <ref target="#basic-concepts-selection-global">global approach</ref>.</item>
+ <item>For a complete markup vocabulary by adding <ref target="#its-schemas">ITS markup declarations</ref> to the underlying schema.</item>
+ </list>
<div xml:id="basic-concepts-selection">
<head>Selection</head>
-
- <p>Information (e.g. "translate this") captured by ITS markup (e.g.
- <code>its:translate='yes'</code>) always pertains to one or more XML or HTML nodes,
- primarily element and attribute nodes, as defined in <ptr type="bibref" target="#xpath"/>. In
- a sense, ITS markup “selects” the relevant node(s). Selection may be explicit or
+ <p>Information (e.g. "translate this") captured by ITS data categories (e.g.
+ <q>translate this piece of content</q>) always pertains to one or more XML or HTML nodes,
+ primarily element and attribute nodes. In
+ a sense, ITS “selects” the relevant node(s). Selection may be explicit or
implicit. ITS distinguishes two approaches to selection: (1) local, and (2) using global
rules.</p>
<p>The mechanisms defined for ITS selection resemble those defined in <ptr
@@ -786,20 +796,19 @@
<code>style</code> attribute in HTML/XHTML, and the approach with global rules is
similar to the <code>style</code> element in HTML/XHTML. ITS usually uses XPath for
identifying nodes although CSS Selectors and other query languages can be used if
- supported by the application. Thus,</p>
+ supported by the application.</p>
<list>
- <item>the local approach puts ITS markup in the relevant element of the host vocabulary
+ <item>the local approach puts ITS markup in the relevant element of the markup host vocabulary
(e.g. the <code>author</code> element in DocBook)</item>
<item>the <ref target="#selection-global">rule-based, global approach</ref> puts the ITS
markup in elements defined by ITS itself (namely the <gi>rules</gi> element)</item>
</list>
- <p>ITS markup can be used with XML documents (e.g. a DocBook article), or schemas (e.g. an
+ <p>ITS markup can be used with XML documents (e.g. a DocBook article), HTML documents, or schemas (e.g. an
XML Schema document for a proprietary document format).</p>
<p>The following two examples sketch the distinction between the local and global
- approaches, using the <att type="class">translate</att> as one example of ITS
- markup.</p>
-
+ approaches, using the <ref target="#trans-datacat">Translate</ref> data category as one example.</p>
+
<div xml:id="basic-concepts-selection-local">
<head>Local Approach</head>
@@ -813,18 +822,20 @@
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-basic-concepts-1.xml"/>
</exemplum>
- <p>For this example to work, the schema developer will need to add the <att type="class"
+ <p>For this example to work for a whole markup vocabulary, the schema developer will need to add the <att type="class"
>translate</att> attribute to the schema as a common attribute or on all the
relevant element definitions. Note how there is an expectation in this case that
- inheritance plays a part in identifying which content does have to be translated and
+ <ref target="#basic-concepts-overinher">inheritance</ref> plays a part in identifying which content does have to be translated and
which does not. Tools that process this content for translation will need to implement
the expected inheritance.</p>
- <p xml:id="local-approach-not-applicable-to-attributes">The local approach cannot be applied on a particular attribute. It can be applied for the content of the current element and all its inherited nodes as described in <ptr target="#datacategories-defaults-etc" type="specref"/>.</p>
-
+ <p xml:id="local-approach-not-applicable-to-attributes">For XML content, the local approach cannot be applied on a particular attribute.
+ It can be applied for the content of the current element and all its inherited nodes as described in <ptr target="#datacategories-defaults-etc" type="specref"/>. For the <ref target="#trans-datacat">Translate</ref> data category used in <ptr target="#html5" type="bibref"/>, this is different, see the explanation of the <ref target="#translate-in-html5">HTML5 definition of Translate</ref>.</p>
+
</div>
<div xml:id="basic-concepts-selection-global">
<head>Global Approach</head>
-
+
+
<p>The document in <ptr target="#EX-basic-concepts-2" type="exref"/> shows a different
approach to identifying non-translatable content, similar to that used with a
<code>style</code> element in <ptr type="bibref" target="#xhtml10"/>, but using an
@@ -835,9 +846,12 @@
<att>selector</att> attribute. As its name suggests, this attribute selects the node
or nodes to which a corresponding ITS information pertains. The values of ITS selector
attributes are XPath absolute location paths (or CSS Selectors if <ref
- target="#queryLanguage">queryLanguage</ref> is set to "css"). Information for the
- handling of namespaces in these path expressions is taken from namespace declarations
- <ptr target="#xmlns" type="bibref"/> at the current rule element.</p>
+ target="#queryLanguage">queryLanguage</ref> is set to "css"). Via the <ref target="#its-param">param</ref> element
+ variables can be provided and then be used in the selectors.</p>
+ <p>Information for the
+ handling of namespaces in XPath expressions is taken from namespace declarations
+ <ptr target="#xmlns" type="bibref"/> at the current rule element.</p>
+
<exemplum xml:id="EX-basic-concepts-2">
<head>ITS global markup in an XML document (rule-based approach) </head>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
@@ -895,9 +909,9 @@
<p>The ITS <att>selector</att> attribute allows:</p>
<list>
- <item>ITS data category attributes to appear in global rules (even outside of an XML
+ <item>ITS data category attributes to appear in global rules (even outside of an XML or HTML
document or schema)</item>
- <item>ITS data categories attributes to pertain to sets of XML nodes (for example all
+ <item>ITS data categories attributes to pertain to sets of document nodes (for example all
<code>p</code> elements in an XML document)</item>
<item>ITS markup to pertain to attributes</item>
<item>ITS markup to <ref target="#associating-its-with-existing-markup"> associate
@@ -908,8 +922,9 @@
</div>
</div>
+
<div xml:id="basic-concepts-overinher">
- <head>Overriding and Inheritance</head>
+ <head>Overriding, Inheritance and Defaults</head>
<p>The power of the ITS selection mechanisms comes at a price: rules related to <ref
target="#selection-precedence">overriding/precedence</ref>, and <ref
@@ -929,7 +944,7 @@
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-basic-concepts-3.xml"/>
</exemplum>
-
+ <p>For XML content, <ref target="#datacategories-overview">data category specific defaults</ref> are provided. These are independent of the actual XML markup vocabulary. For <ptr target="#html5" type="bibref"/>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence, that HTML markup is normatively interpreted as ITS 2.0 data category information: See <ptr target="#html5-existing-markup-versus-its" type="specref"/> for more information.</p>
</div>
<div xml:id="basic-concepts-addingpointing">
<head>Adding Information or Pointing to Existing Information</head>
@@ -946,6 +961,31 @@
<emph>mutually exclusive</emph>. That is to say, attributes for pointing and adding
the same information must not appear at the same rule element.</p>
</div>
+
+
+<div xml:id="mapping-conversion">
+ <head>Mapping and conversion</head>
+ <p>tbd - here <ptr target="#mappings" type="specref"/>.</p>
+</div>
+
+
+ <div xml:id="tools-information">
+ <head>ITS Tools Annotation</head>
+ <p>tbd - here partially content of <ptr target="#additional-mechanisms" type="specref"/>.</p>
+ </div>
+ <div xml:id="implementing-its20">
+ <head>Implementing ITS 2.0</head>
+ <p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer, see <ptr type="specref" target="#conformance"/>, targeted at different types of implementers.</p>
+ <list type="unordered">
+ <item>Conformance clauses in <ptr type="specref" target="#conformance-product-schema"/> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</item>
+ <item>Conformance clauses in <ptr target="#conformance-product-processing-expectations" type="specref"/> tell implementers how to process XML content applying ITS 2.0 data categories.</item>
+ <item>Conformance clauses in <ptr type="specref" target="#conformance-product-html-processing-expectations"/> tell implementers how to process <ptr target="#html5" type="bibref"/> content.</item>
+ <item>Conformance clauses in <ptr target="#conformance-class-html5-its" type="specref"/> tell implementers how ITS 2.0 markup is integrated into <ptr type="bibref" target="#html5"/>.</item>
+ </list>
+ <p>The conformance clauses in <ptr target="#conformance-product-processing-expectations" type="specref"/> and <ptr type="specref" target="#conformance-product-html-processing-expectations"/> make clear: what information needs to be made available for given pieces of markup then processing a dedicated ITS 2.0 data category? To allow for flexibility, an implementation can choose whether it wants to process only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in seperate conformances clauses and also in the <ref target="@@@@">ITS 2.0 test suite</ref>.</p>
+ <p>ITS 2.0 processing expectations only cover above aspect, that is: what information needs to be made available. They do not define how that information actually should be applied. This is due to the fact that there is a huge variety of usage scenarios of ITS 2.0, and a huge variety of tools for working with ITS 2.0. Each of these tools has their own way of using ITS 2.0 data categories. See <ptr type="bibref" target="#mlw-metadata-us-impl"/> for more information.</p>
+ <note type="ed">Add link to test suite</note>
+ </div>
</div>
<div xml:id="notation-terminology">
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/03 18:53:38 1.440
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/06 09:56:55 1.441
@@ -61,9 +61,9 @@
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors" shape="rect">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage" shape="rect">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2365" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2368" shape="rect">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2610" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2613" shape="rect">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param" shape="rect">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules" shape="rect">Link to External Rules</a></div>
@@ -778,7 +778,7 @@
<code>head</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>).</p></li><li><p id="its-conformance-1-3">
<em>1-4:</em> If the <code class="its-elem-markup">span</code> element is
used, it <a href="#rfc-keywords" shape="rect">SHOULD</a> be declared as an inline
- element.</p></li></ul><p id="its-markup-conformance-claims">Full implementations of this conformance type
+ element.</p></li></ul><span class="editor-note">[Ed. note: Above numbering is wrong.]</span><p id="its-markup-conformance-claims">Full implementations of this conformance type
will implement all markup declarations for ITS. Statements related to this conformance
type <a href="#rfc-keywords" shape="rect">MUST</a> list all markup declarations they
implement.</p><p>
@@ -954,9 +954,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2365" id="d0e2365" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2368" id="d0e2368" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2376" id="d0e2376" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+<h5><a name="d0e2379" id="d0e2379" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
that starts with "<code>/</code>". That is, it must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a>s as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
@@ -1001,14 +1001,14 @@
be used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-and-attributes">CSS selectors have no ability to point to
attributes.</p></div><p>CSS Selectors are identified by the value <code>css</code> in the
<code class="its-attr-markup">queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d0e2587" id="d0e2587" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2590" id="d0e2590" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Both simple
selectors and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2597" id="d0e2597" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2600" id="d0e2600" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. A selector is
not evaluated against the complete document tree but only against subtrees rooted at
nodes selected by the selector in the <code class="its-attr-markup">selector</code> attribute.</p></div></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2610" id="d0e2610" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2613" id="d0e2613" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
languages. For each additional query language the processor <a href="#rfc-keywords" shape="rect">MUST</a> define:</p><ul><li><p>the identifier of the query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating an absolute selector to a collection of nodes;</p></li><li><p>rules for evaluating a relative selector to a collection of nodes.</p></li></ul><p>Because future versions of this specification are likely to define additional query
languages, the following query language identifiers are reserved: <code>xpath</code>,
<code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/03 18:53:38 1.440
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/06 09:56:55 1.441
@@ -1029,6 +1029,7 @@
element.</p></item>
</list>
+ <note type="ed">Above numbering is wrong.</note>
<p xml:id="its-markup-conformance-claims">Full implementations of this conformance type
will implement all markup declarations for ITS. Statements related to this conformance
type <ref target="#rfc-keywords">MUST</ref> list all markup declarations they
Received on Thursday, 6 June 2013 09:56:58 UTC