- From: CVS User alommel <cvsmail@w3.org>
- Date: Fri, 30 Nov 2012 14:13:00 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv23851
Modified Files:
its20.html its20.odd
Log Message:
changes to Localization Quality Issue type values to respond to Daniel Naber’s comments (two explanatory, one normative, which brings the text into line with the actual intent)
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/11/30 11:30:06 1.286
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/11/30 14:13:00 1.287
@@ -164,12 +164,13 @@
with the exceptions of <a href="#directionality" shape="rect">Directionality</a> and <a href="#ruby-annotation" shape="rect">Ruby</a>.</p></li><li><p>ITS 2.0 adds a number of new data categories not found in ITS 1.0.</p></li><li><p>While ITS 1.0 addressed only XML, ITS 2.0 specifies implementations of data
categories in <em>both</em> XML <em>and</em> HTML.</p></li></ul></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="new-principles" id="new-principles" shape="rect"/>1.1.2 New Principles</h4><p>ITS 2.0 also adds the following principles and features not found in ITS 1.0:</p><ul><li><p>ITS 2.0 data categories are intended to be format neutral, with support for XML,
- HTML, and NIF: a data category implementation only needs to support a single
- content format mapping in order to support a claim of ITS 2.0 conformance.</p></li><li><p>ITS 2.0 provides algorithms to generate NIF out of HTML or XML with ITS 2.0
+ HTML, and NIF: a data category implementation only needs to support a single content
+ format mapping in order to support a claim of ITS 2.0 conformance.</p></li><li><p>ITS 2.0 provides algorithms to generate NIF out of HTML or XML with ITS 2.0
metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the XPath version 1.0.
Other versions of XPath or other query languages (e.g., CSS selectors) can be
expressed via a dedicated <a href="#queryLanguage" shape="rect">queryLanguage</a>
- attribute.</p></li></ul><p id="its20-new-data-categories">The new data categories included in ITS 2.0 are:</p><ul><li><p><a href="#domain" shape="rect">Domain</a></p></li><li><p><a href="#Disambiguation" shape="rect">Disambiguation</a></p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a></p></li><li><p><a href="#provenance" shape="rect">Provenance</a></p></li><li><p><a href="#externalresource" shape="rect">External Resource</a></p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a></p></li><li><p><a href="#idvalue" shape="rect">Id Value</a></p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a></p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a></p></li><li><p><a href="#lqrating" shape="rect">Localization Quality Rating</a></p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a></p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a></p></li><li><p><a href="#storagesize" shape="rec">Storage Size</a></p></li></ul></div></div><div class="div2">
+ attribute.</p></li></ul><p id="its20-new-data-categories">The new data categories included in ITS 2.0
+ are:</p><ul><li><p><a href="#domain" shape="rect">Domain</a></p></li><li><p><a href="#Disambiguation" shape="rect">Disambiguation</a></p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a></p></li><li><p><a href="#provenance" shape="rect">Provenance</a></p></li><li><p><a href="#externalresource" shape="rect">External Resource</a></p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a></p></li><li><p><a href="#idvalue" shape="rect">Id Value</a></p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a></p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a></p></li><li><p><a href="#lqrating" shape="rect">Localization Quality Rating</a></p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a></p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a></p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a></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="motivation-its" id="motivation-its" shape="rect"/>1.2 Motivation for ITS</h3><p>Content or software that is authored in one language (the <span class="new-term">source language</span>)
is often made available in additional languages or adapted with regard to other cultural
aspects. This is done through a process called <span class="new-term">localization</span>, where the
@@ -275,7 +276,13 @@
producers by relating the ITS information to relevant bits of content in a global
manner (see <a href="#selection-global" shape="rect">global, rule-based approach</a>). This
global work, however, may fall to information architects, rather than the content
- producers themselves.</p><p id="cms-plain-text-fields">Content producers often work with content management systems (CMS). In various CMS, some of the CMS fields only allow to store plain text. For these fields, the current ITS 2.0 data categories can only be applied globally and not with local attributes. This issue should be addressed in another way, apart from the ITS 2.0 standard. One way would be to allow HTML in these fields if possible, or using an extra field which allows HTML input and save the plain text of this extra field in the plain text field.</p></div><div class="div4">
+ producers themselves.</p><p id="cms-plain-text-fields">Content producers often work with content management
+ systems (CMS). In various CMS, some of the CMS fields only allow to store plain
+ text. For these fields, the current ITS 2.0 data categories can only be applied
+ globally and not with local attributes. This issue should be addressed in another
+ way, apart from the ITS 2.0 standard. One way would be to allow HTML in these fields
+ if possible, or using an extra field which allows HTML input and save the plain text
+ of this extra field in the plain text field.</p></div><div class="div4">
<h5><a name="users_machine-translation" id="users_machine-translation" shape="rect"/>1.3.1.5Machine Translation Systems</h5><p>This type of service is intended for a broad user community ranging from developers
and integrators through translation companies and agencies, freelance translators
and post-editors to ordinary translation consumers and other types of MT employment.
@@ -318,8 +325,8 @@
by looking at them from the perspectives of certain user types. For the purpose of
illustration, we will demonstrate how ITS can indicate that certain parts of content
should or should not be translated.</p><ul><li><p>A content author uses an attribute on a particular element to say that the text
- in the element should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-ways-to-use-its-1" id="EX-ways-to-use-its-1" shape="rect"/>Example 3: Use of ITS by content author</div><p>The <code>its:translate="no"</code> attributes indicate that the <code>path</code> and
- the <code>cmd</code> elements should not be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
+ in the element should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-ways-to-use-its-1" id="EX-ways-to-use-its-1" shape="rect"/>Example 3: Use of ITS by content author</div><p>The <code>its:translate="no"</code> attributes indicate that the <code>path</code>
+ and the <code>cmd</code> elements should not be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>Building the Zebulon Toolkit<strong class="hl-tag" style="color: #000096"></title></strong>
<strong class="hl-tag" style="color: #000096"></head></strong>
@@ -417,12 +424,11 @@
<strong class="hl-tag" style="color: #000096"></xs:element></strong>
<strong class="hl-tag" style="color: #000096"></xs:schema></strong></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-5.xsd" shape="rect">examples/xml/EX-ways-to-use-its-5.xsd</a>]</p></div><p>The first two approaches above can be likened to the use of CSS in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>. Using a <code>style</code> attribute, an XHTML
content author may assign a color to a particular paragraph. That author could also
- have used the <code>style</code> element at the top of the page to say that all paragraphs
- of a particular class or in a particular context would be colored red.</p></div></div><div class="div2">
+ have used the <code>style</code> element at the top of the page to say that all
+ paragraphs of a particular class or in a particular context would be colored red.</p></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="usage-in-html5" id="usage-in-html5" shape="rect"/>1.4 Usage in HTML</h3><p>ITS 2.0 adds support for usage in HTML. In HTML, ITS local selection is realized via
dedicated, <a href="#html5-local-attributes" shape="rect">data category specific
- attributes</a>.</p><span class="editor-note">[Ed. note: Add example of HTML with local attributes for illustration
- purposes]</span><p>For the so-called “<a href="#basic-concepts-selection-global" shape="rect">global
+ attributes</a>.</p><span class="editor-note">[Ed. note: Add example of HTML with local attributes for illustration purposes]</span><p>For the so-called “<a href="#basic-concepts-selection-global" shape="rect">global
approach</a>” in HTML, this specification defines a link type for referring to files
with global rules in <a class="section-ref" href="#html5-global-rules" shape="rect">Section 6.2: Global rules</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 8: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
<code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
@@ -474,8 +480,8 @@
on the other hand, need an efficient way to manage translations of large document sets
based on the same schema. These needs could by realized by a specification of defaults
for the <a href="#trans-datacat" shape="rect">Translate</a> data category along with exceptions
- to those defaults (e.g. all <code>p</code> elements should be translated, but not <code>p</code>
- elements inside of an <code>index</code> element).</p><p>To meet these requirements this specification introduces mechanisms that add ITS
+ to those defaults (e.g. all <code>p</code> elements should be translated, but not
+ <code>p</code> elements inside of an <code>index</code> element).</p><p>To meet these requirements this specification introduces mechanisms that add ITS
information to XML documents, see <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. These
mechanisms also provide a means for specifying ITS information for attributes (a task
for which no standard means previously existed).</p><p>The ITS selection mechanisms allows you to provide information about content <a href="#selection-local" shape="rect">locally</a> (specified at the XML or HTML element to which
@@ -513,9 +519,9 @@
markup.</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 10</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 translation.
- Translation tools that are aware of the meaning of this attribute can then screen the
- relevant content from the translation process.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 10: ITS markup on elements in an XML document (local approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
+ all content inside the <code>author</code> element should be protected from
+ translation. Translation tools that are aware of the meaning of this attribute can
+ then screen the relevant content from the translation process.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 10: ITS markup on elements in an XML document (local approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
<span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
<span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"5.0"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><info></strong>
@@ -551,9 +557,9 @@
<a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> at the current rule element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Caveat Related to XSLT-based Processing of ITS Selector Attributes</p><p> The values of ITS <code class="its-attr-markup">selector</code> attributes are XPath absolute location
paths. Accordingly, the following is a legitimate value:</p><p>myElement/descendant-or-self::*/@*</p><p>Unfortunately, values like this cause trouble when they are used in XSLT-based
processing of ITS where the values of the ITS <code class="its-attr-markup">selector</code> attributes are
- used as values of <code>match</code> attributes of XSLT templates. The reason for this
- is the following: <code>match</code> attributes may only contain a restriction/subset
- of XPath expressions, so-called <a href="http://www.w3.org/TR/xslt#patterns" shape="rect">patterns</a>.</p><p>Basically the following restrictions hold for patterns: </p><ul><li><p>only axes "child" or "attribute" allowed</p></li><li><p>"//" or "/" possible</p></li><li><p>id() or key() function possible</p></li><li><p>predicates possible</p></li></ul><p>Using only XSLT patterns in ITS <code class="its-attr-markup">selector</code> attributes helps to avoid this
+ used as values of <code>match</code> attributes of XSLT templates. The reason for
+ this is the following: <code>match</code> attributes may only contain a
+ restriction/subset of XPath expressions, so-called <a href="http://www.w3.org/TR/xslt#patterns" shape="rect">patterns</a>.</p><p>Basically the following restrictions hold for patterns: </p><ul><li><p>only axes "child" or "attribute" allowed</p></li><li><p>"//" or "/" possible</p></li><li><p>id() or key() function possible</p></li><li><p>predicates possible</p></li></ul><p>Using only XSLT patterns in ITS <code class="its-attr-markup">selector</code> attributes helps to avoid this
issue. In many cases, this is possible by using patterns with predicates. The value
above may for example be rewritten as follows:</p><p>*[self::myElement]/@* | myElement//*/@*</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 11: 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>
@@ -581,7 +587,8 @@
associated with sets of nodes (for example all <code>p</code> elements in an XML
instance)</p></li><li><p>Changes can be made in a single location, rather than by searching and modifying
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>.
+ 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
<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
@@ -590,13 +597,13 @@
<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 12</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 <code>text</code>
- and for all its children. Because the <code>title</code> element is actually translatable,
- the global rule needs to be overridden by a local <code>its:translate="yes"</code>. Note
- that the global rule is processed first, regardless of its position inside the document.
- In the main body of the document, the default applies, and here it is
- <code>its:translate="no"</code> that is used to set “faux pas” as
- non-translatable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 12: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
+ in the header overrides the default for the <code>head</code> element inside
+ <code>text</code> and for all its children. Because the <code>title</code> element is
+ actually translatable, the global rule needs to be overridden by a local
+ <code>its:translate="yes"</code>. Note that the global rule is processed first,
+ regardless of its position inside the document. In the main body of the document, the
+ default applies, and here it is <code>its:translate="no"</code> that is used to set
+ “faux pas” as non-translatable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 12: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><revision></strong>Sep-10-2006 v5<strong class="hl-tag" style="color: #000096"></revision></strong>
<strong class="hl-tag" style="color: #000096"><author></strong>Ealasaidh McIan<strong class="hl-tag" style="color: #000096"></author></strong>
@@ -641,8 +648,8 @@
[<a name="t002" id="t002" title="data category" shape="rect">Definition</a>: ITS defines <span class="new-term">data category</span>
as an abstract concept for a particular type of information for internationalization
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
+ 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="d0e1177" id="d0e1177" shape="rect"/>Example 13: 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:
@@ -662,12 +669,12 @@
<a href="#def-adding-pointing" shape="rect">point to existing information</a> which is
related to selected nodes. </p><div class="note"><p class="prefix"><b>Note:</b></p><p id="note-object-selection">The selection of the ITS data categories applies to
textual values contained within element or attribute nodes. In some cases these nodes
- form pointers to other resources; a well-known example is the <code>src</code> attribute
- on the <code>img</code> element in HTML. The ITS <a href="#trans-datacat" shape="rect">Translate</a> data category applies to the text of the pointer itself, not the
- object to which it points. Thus in the following example, the translation information
- specified via the <code class="its-elem-markup">translateRule</code> element applies to the filename
- "instructions.jpg", and is not an instruction to open the graphic and
- change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-notation-terminology-1" id="EX-notation-terminology-1" shape="rect"/>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></strong>
+ form pointers to other resources; a well-known example is the <code>src</code>
+ attribute on the <code>img</code> element in HTML. The ITS <a href="#trans-datacat" shape="rect">Translate</a> data category applies to the text of the
+ pointer itself, not the object to which it points. Thus in the following example, the
+ translation information specified via the <code class="its-elem-markup">translateRule</code> element applies to
+ the filename "instructions.jpg", and is not an instruction to open the
+ graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-notation-terminology-1" id="EX-notation-terminology-1" shape="rect"/>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span>
<span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//p/img/@src"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -688,11 +695,13 @@
all elements defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> as
elements for global rules.]
</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="iri-usage" id="iri-usage" shape="rect"/>3.6 Usage of Internationalized Resource Identifiers in ITS</h3><p>All attributes that have the type <code>anyURI</code> in the normative RELAX NG schema in <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a>
+<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="iri-usage" id="iri-usage" shape="rect"/>3.6 Usage of Internationalized Resource Identifiers in ITS</h3><p>All attributes that have the type <code>anyURI</code> in the normative RELAX NG schema
+ in <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a>
<a href="#rfc-keywords" shape="rect">MUST</a> allow the usage of Internationalized Resource
Identifiers (IRIs, <a title="Internationalized Resource
 Identifiers (IRIs)" href="#rfc3987" shape="rect">[RFC 3987]</a> or its successor) to ease the
adoption of ITS in international application scenarios.</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="def-html" id="def-html" shape="rect"/>3.7 The Term HTML</h3><p>This specification uses the term <code>HTML</code> to refer to HTML5 or its successor <a title="HTML5 – A vocabulary and associated APIs for
 HTML and XHTML" href="#html5" shape="rect">[HTML5]</a>.</p></div></div><div class="div1">
+<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="def-html" id="def-html" shape="rect"/>3.7 The Term HTML</h3><p>This specification uses the term <code>HTML</code> to refer to HTML5 or its successor
+ <a title="HTML5 – A vocabulary and associated APIs for
 HTML and XHTML" href="#html5" shape="rect">[HTML5]</a>.</p></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="conformance" id="conformance" shape="rect"/>4 Conformance</h2><p>
<em>This section is normative.</em>
</p><p>The usage of the term <em>conformance clause</em> in this section is in compliance
@@ -735,8 +744,8 @@
existing schemas are given in a separate document <a title="Best
 Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</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="conformance-product-processing-expectations" id="conformance-product-processing-expectations" shape="rect"/>4.2 Conformance Type 2: The Processing Expectations for ITS Markup</h3><p>
<em>Description:</em> Processors need to compute the ITS information that pertains
- to a node in an XML document. The ITS processing expectations define how the
- computation has to be carried out. Correct computation involves support for <a href="#def-selection" shape="rect">selection mechanism</a>, <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
+ to a node in an XML document. The ITS processing expectations define how the computation
+ has to be carried out. Correct computation involves support for <a href="#def-selection" shape="rect">selection mechanism</a>, <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
characteristics</a>, and <a href="#selection-precedence" shape="rect">precedence</a>. The
markup <a href="#rfc-keywords" shape="rect">MAY</a> be valid against a schema which conforms to
the clauses in <a class="section-ref" href="#conformance-product-schema" shape="rect">Section 4.1: Conformance Type 1: ITS Markup Declarations</a>.</p><p>
@@ -766,30 +775,31 @@
on a <code class="its-elem-markup">rules</code> elements.</p></li><li><p id="its-conformance-2-3">
<em>2-3:</em> If an application claims to
process ITS markup implementing the conformance clauses 2-1, 2-2 and 2-3, it <a href="#rfc-keywords" shape="rect">MUST</a> process that markup with XML
- documents.</p></li><li><p id="its-conformance-2-4">
+ documents.</p></li><li><p id="its-conformance-2-4">
<em>2-4:</em> After processing ITS information
on the basis of conformance clauses <a href="#its-conformance-2-1" shape="rect">2-1</a> and
- <a href="#its-conformance-2-2" shape="rect">2-2</a>, an application <a href="#rfc-keywords" shape="rect">MAY</a> convert an XML document to NIF, using the algorithm described in <a class="section-ref" href="#conversion-to-nif" shape="rect">Section 5.7: Conversion to NIF</a>.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a> essentially
+ <a href="#its-conformance-2-2" shape="rect">2-2</a>, an application <a href="#rfc-keywords" shape="rect">MAY</a> convert an XML document to NIF, using the
+ algorithm described in <a class="section-ref" href="#conversion-to-nif" shape="rect">Section 5.7: Conversion to NIF</a>.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a> essentially
means that the conversion to NIF is an optional feature of ITS 2.0, and that the
conversion is independent of whether ITS information has been made available via the
global or local selection mechanisms, see conformance clause <a href="#its-conformance-2-1-1" shape="rect">2-1-1</a>.</p></div><p id="its-processing-conformance-claims">Statements related to this conformance type
<a href="#rfc-keywords" shape="rect">MUST</a> list all <a href="#def-datacat" shape="rect">data
categories</a> they implement, and for each <a href="#def-datacat" shape="rect">data
category</a> which type of selection they support, whether they support processing
- of XML. If the implementation provides the conversion to NIF (see
- conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="https://github.com/finnle/ITS-2.0-Testsuite/" shape="rect">ITS 2.0 test
- suite</a>. All tests specify which data category is processed (clause 2-1); they
- are relevant for (clause 2-1-1) global or local selection, or both; they require the
- processing of defaults and precedence of selections (clauses 2-1-2 and 2-1-3); for
- each data category there are tests with linked rules (2-2); and all types of tests are
- given for XML (clause 2-3). In addition, there are test cases for
- conversion to NIF (clause 2-4). Implementors are encouraged to organize their
- documentation in a similar way, so that users of ITS 2.0 easily can understand the
- processing capabilities available.</p></div></div><div class="div2">
+ of XML. If the implementation provides the conversion to NIF (see conformance clause
+ <a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="https://github.com/finnle/ITS-2.0-Testsuite/" shape="rect">ITS 2.0 test suite</a>. All
+ tests specify which data category is processed (clause 2-1); they are relevant for
+ (clause 2-1-1) global or local selection, or both; they require the processing of
+ defaults and precedence of selections (clauses 2-1-2 and 2-1-3); for each data
+ category there are tests with linked rules (2-2); and all types of tests are given for
+ XML (clause 2-3). In addition, there are test cases for conversion to NIF (clause
+ 2-4). Implementors are encouraged to organize their documentation in a similar way, so
+ that users of ITS 2.0 easily can understand the processing capabilities
+ available.</p></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="conformance-product-html-processing-expectations" id="conformance-product-html-processing-expectations" shape="rect"/>4.3 Conformance Type 3: Processing Expectations for ITS Markup in HTML</h3><p>
<em>Description:</em> Processors need to compute the ITS information that pertains
- to a node in a HTML document. The ITS processing expectations define how the
- computation has to be carried out. Correct computation involves support for <a href="#def-selection" shape="rect">selection mechanism</a>, <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
+ to a node in a HTML document. The ITS processing expectations define how the computation
+ has to be carried out. Correct computation involves support for <a href="#def-selection" shape="rect">selection mechanism</a>, <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
characteristics</a>, and <a href="#html5-selection-precedence" shape="rect">precedence</a>.</p><p>
<em>Definitions related to this conformance type:</em> The processing expectations
for ITS markup make use of selection mechanisms defined in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. The individual data categories defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> have <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
@@ -842,7 +852,7 @@
elements</a> for each data category. Each rule element has a <code class="its-attr-markup">selector</code>
attribute and possibly other attributes. The <code class="its-attr-markup">selector</code> attribute contains an
absolute selector as defined in <a class="section-ref" href="#selectors" shape="rect">Section 5.3: Query Language of Selectors</a>.</p></li><li><p><a href="#selection-local" shape="rect">Locally in a document</a>: the selection is
- realized using ITS local attributes, which are attached to an element node, or the <code class="its-elem-markup">span</code> or <code class="its-elem-markup">ruby</code> element. There is no additional <code class="its-attr-markup">selector</code>
+ realized using ITS local attributes, which are attached to an element node, or the<code class="its-elem-markup">span</code> or <code class="its-elem-markup">ruby</code> element. There is no additional <code class="its-attr-markup">selector</code>
attribute. The default selection for each data category defines whether the selection
covers attributes and child elements. See <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p></li></ul><p>The two locations are described in detail below.</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="selection-global" id="selection-global" shape="rect"/>5.2.1 Global, Rule-based Selection</h4><p>Global, rule-based selection is implemented using the <code class="its-elem-markup">rules</code> element. It
@@ -866,13 +876,13 @@
XML document. The precedence of their processing depends on these variations. See also
<a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</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="selection-local" id="selection-local" shape="rect"/>5.2.2 Local Selection in an XML Document</h4><p>Local selection in XML documents is realized with <a href="#local-attributes" shape="rect">ITS
- local attributes</a> or the <code class="its-elem-markup">span</code> element.
- <code class="its-elem-markup">span</code> serves just as a carrier for the local ITS attributes.</p><p>The data category determines what is being selected. The necessary data category
+ local attributes</a> or the <code class="its-elem-markup">span</code> element. <code class="its-elem-markup">span</code> serves just as a
+ carrier for the local ITS attributes.</p><p>The data category determines what is being selected. The necessary data category
specific defaults are 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 class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-local-1" id="EX-selection-local-1" shape="rect"/>Example 15: Defaults for various data categories</div><p>By default the content of all elements in a document is translatable. The attribute
<code>its:translate="no"</code> in the <code>head</code> element means that the
content of this element, including child elements, should not be translated. The
- attribute <code>its:translate="yes"</code> in the <code>title</code> element means that
- the content of this element, should be translated (overriding the
+ attribute <code>its:translate="yes"</code> in the <code>title</code> element means
+ that the content of this element, should be translated (overriding the
<code>its:translate="no"</code> in <code>head</code>). Attribute values of the
selected elements or their children are not affected by local <code class="its-attr-markup">translate</code> attributes. By default they are not translatable.</p><p>The default directionality of a document is left-to-right. The
<code>its:dir="rtl"</code> in the <code>quote</code> element means that the
@@ -891,11 +901,10 @@
<strong class="hl-tag" style="color: #000096"></text></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-selection-local-1.xml" shape="rect">examples/xml/EX-selection-local-1.xml</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code class="its-attr-markup">dir</code> and <code class="its-attr-markup">translate</code> attributes are not listed in the
ITS attributes to be used in HTML. The reason is that these two attributes are
- available in HTML natively, so there is no need to provide them as
- <code>its-</code> attributes. The definition of the two attributes in HTML is
- compatibly, that is it provides the same values and interpretation, as the
- definition for the two data categories <a href="#trans-datacat" shape="rect">Translate</a>
- and <a href="#directionality" shape="rect">Directionality</a>.</p></div></div></div><div class="div2">
+ available in HTML natively, so there is no need to provide them as <code>its-</code>
+ attributes. The definition of the two attributes in HTML is compatibly, that is it
+ provides the same values and interpretation, as the definition for the two data
+ categories <a href="#trans-datacat" shape="rect">Translate</a> and <a href="#directionality" shape="rect">Directionality</a>.</p></div></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="selectors" id="selectors" shape="rect"/>5.3 Query Language of Selectors</h3><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="queryLanguage" id="queryLanguage" shape="rect"/>5.3.1 Choosing Query Language</h4><p>
<a href="#rule-elements" shape="rect">Rule elements</a> have attributes which contain
@@ -929,11 +938,16 @@
</pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-2.xml" shape="rect">examples/xml/EX-selection-global-2.xml</a>]</p></div></div><div class="div4">
<h5><a name="xpath-relative-selector" id="xpath-relative-selector" shape="rect"/>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords" shape="rect">MUST</a> use a <a href="http://www.w3.org/TR/xpath/#NT-RelativeLocationPath" shape="rect">RelativeLocationPath</a> or an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">AbsoluteLocationPath</a> as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
The XPath expression is evaluated relative to the nodes selected by the selector
- attribute.</p><p id="pointer-attributes-list">The following attributes point to existing information:
- <code class="its-attr-markup">allowedCharactersPointer</code>, <code class="its-attr-markup">disambigClassPointer</code>, <code class="its-attr-markup">disambigClassRefPointer</code>, <code class="its-attr-markup">disambigIdentPointer</code>,
- <code class="its-attr-markup">disambigIdentRefPointer</code>, <code class="its-attr-markup">domainPointer</code>, <code class="its-attr-markup">externalResourceRefPointer</code>, <code class="its-attr-markup">langPointer</code>, <code class="its-attr-markup">locNotePointer</code>,
- <code class="its-attr-markup">locNoteRefPointer</code>, <code class="its-attr-markup">locQualityIssuesRefPointer</code>, <code class="its-attr-markup">provenanceRecordsRefPointer</code>, <code class="its-attr-markup">storageEncodingPointer</code>,
- <code class="its-attr-markup">storageSizePointer</code>, <code class="its-attr-markup">targetPointer</code>, <code class="its-attr-markup">termInfoPointer</code>, <code class="its-attr-markup">termInfoRefPointer</code>.</p><p>Context for evaluation of the XPath expression is same as for absolute selector
+ attribute.</p><p id="pointer-attributes-list">The following attributes point to existing
+ information: <code class="its-attr-markup">allowedCharactersPointer</code>, <code class="its-attr-markup">disambigClassPointer</code>,
+ <code class="its-attr-markup">disambigClassRefPointer</code>, <code class="its-attr-markup">disambigIdentPointer</code>,
+ <code class="its-attr-markup">disambigIdentRefPointer</code>, <code class="its-attr-markup">domainPointer</code>,
+ <code class="its-attr-markup">externalResourceRefPointer</code>, <code class="its-attr-markup">langPointer</code>,
+ <code class="its-attr-markup">locNotePointer</code>, <code class="its-attr-markup">locNoteRefPointer</code>,
+ <code class="its-attr-markup">locQualityIssuesRefPointer</code>, <code class="its-attr-markup">provenanceRecordsRefPointer</code>,
+ <code class="its-attr-markup">storageEncodingPointer</code>, <code class="its-attr-markup">storageSizePointer</code>,
+ <code class="its-attr-markup">targetPointer</code>, <code class="its-attr-markup">termInfoPointer</code>,
+ <code class="its-attr-markup">termInfoRefPointer</code>.</p><p>Context for evaluation of the XPath expression is same as for absolute selector
with the following changes:</p><ul><li><p>Nodes selected by the expression in the <code class="its-attr-markup">selector</code> attribute form the
current node list.</p></li><li><p>Context node comes from the current node list.</p></li><li><p>The context position comes from the position of the current node in the current
node list; the first position is 1.</p></li><li><p>The context size comes from the size of the current node list.</p></li></ul></div></div><div class="div3">
@@ -1030,7 +1044,10 @@
<strong class="hl-tag" style="color: #000096"><p></strong>A <strong class="hl-tag" style="color: #000096"><term></strong>Palouse horse<strong class="hl-tag" style="color: #000096"></term></strong> has a spotted coat.<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></myDoc></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-3.xml" shape="rect">examples/xml/EX-link-external-rules-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-link-external-rules-4" id="EX-link-external-rules-4" shape="rect"/>Example 22: External rules file with the <code class="its-elem-markup">rules</code> element as the root element</div><p>Like <a href="#EX-link-external-rules-1" shape="rect">Example 19</a>, these rules can be applied e.g. to <a href="#EX-link-external-rules-2" shape="rect">Example 20</a>. The only difference is that in <a href="#EX-link-external-rules-4" shape="rect">Example 22</a>, the <code class="its-elem-markup">rules</code> element is the root element of the external file.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span cass="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
+</pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-3.xml" shape="rect">examples/xml/EX-link-external-rules-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-link-external-rules-4" id="EX-link-external-rules-4" shape="rect"/>Example 22: External rules file with the <code class="its-elem-markup">rules</code> element as the root element</div><p>Like <a href="#EX-link-external-rules-1" shape="rect">Example 19</a>, these rules can be
+ applied e.g. to <a href="#EX-link-external-rules-2" shape="rect">Example 20</a>. The only
+ difference is that in <a href="#EX-link-external-rules-4" shape="rect">Example 22</a>, the
+ <code class="its-elem-markup">rules</code> element is the root element of the external file.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//header"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//term"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"><its:termRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//term"</span> <span class="hl-attribute" style="color: #F5844C">term</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -1042,7 +1059,9 @@
where the original XLink <code class="its-attr-markup">href</code> attribute is.</p><p>External rules may also have links to other external rules. The linking mechanism is
recursive, the deepest rules being overridden by the top-most rules, if any.</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="selection-precedence" id="selection-precedence" shape="rect"/>5.5 Precedence between Selections</h3><p>The following precedence order is defined for selections of ITS information in various
- positions (the first item in the list has the highest precedence):</p><ol class="depth1"><li><p>Selection via explicit (that is, not inherited) local ITS markup in documents (<a href="#local-attributes" shape="rect">ITS local attributes</a> on a specific element)</p></li><li><p>Global selections in documents (using a
+ positions (the first item in the list has the highest precedence):</p><ol class="depth1"><li><p>Selection via explicit (that is, not inherited) local
+ ITS markup in documents (<a href="#local-attributes" shape="rect">ITS local attributes</a> on
+ a specific element)</p></li><li><p>Global selections in documents (using a
<code class="its-elem-markup">rules</code> element)</p><p>Inside each <code class="its-elem-markup">rules</code> element the precedence order is: </p><ol class="depth2"><li><p>Any rule inside the rules element</p></li><li><p>Any rule linked via the XLink <code class="its-attr-markup">href</code> attribute</p></li></ol><p>
</p><div class="note"><p class="prefix"><b>Note:</b></p><p>ITS does not define precedence related to rules defined or linked based on
non-ITS mechanisms (such as processing instructions for linking rules).</p></div></li><li><p>Selections via defaults for data categories, see <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a></p></li></ol><p>In case of conflicts between global selections via multiple <a href="#selection-global" shape="rect">rules</a> elements, the last rule has higher
@@ -1050,13 +1069,13 @@
all information provided via lower precedence is overriden by the higher precedence.
E.g. defaults are overridden by inherited values, these are overriden by nodes
selected via global rules, which are in turn overridden by local markup.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-precedence-1" id="EX-selection-precedence-1" shape="rect"/>Example 23: Conflicts between selections of ITS information which are resolved using the
- precedence order</div><p>The two elements <code>title</code> and <code>author</code> of this document should be
- treated as separate content when inside a <code>prolog</code> element, but as part of the
- content of their parent element otherwise. In order to make this distinction two
- <code class="its-elem-markup">withinTextRule</code> elements are used:</p><p>The first rule specifies that <code>title</code> and <code>author</code> in general should be
- treated as an element within text. This overrides the default.</p><p>The second rule indicates that when <code>title</code> or <code>author</code> are found in a
- <code>prolog</code> element their content should be treated separately. This is normally
- the default, but the rule is needed to override the first rule.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></strong>
+ precedence order</div><p>The two elements <code>title</code> and <code>author</code> of this document should
+ be treated as separate content when inside a <code>prolog</code> element, but as part
+ of the content of their parent element otherwise. In order to make this distinction
+ two <code class="its-elem-markup">withinTextRule</code> elements are used:</p><p>The first rule specifies that <code>title</code> and <code>author</code> in general
+ should be treated as an element within text. This overrides the default.</p><p>The second rule indicates that when <code>title</code> or <code>author</code> are
+ found in a <code>prolog</code> element their content should be treated separately.
+ This is normally the default, but the rule is needed to override the first rule.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><prolog></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:withinTextRule</strong> <span class="hl-attribute" style="color: #F5844C">withinText</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//title|//author"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -1115,7 +1134,8 @@
example, for a command-line tool: providing the paths of both the XML document to
process and its corresponding external rules file.</p></li></ul></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="conversion-to-nif" id="conversion-to-nif" shape="rect"/>5.7 Conversion to NIF</h3><p>This section defines an algorithm to convert XML or HTML documents (or their DOM
- representations) that contain ITS metadata to the RDF-based format <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF</a>. The conversion results in RDF triples.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP
+ representations) that contain ITS metadata to the RDF-based format <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF</a>. The conversion results in RDF
+ triples.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP
tool and can produce a lot of "<span class="quote">phantom</span>" predicates from excessive
whitespace, which 1) increases the size of the intermediate mapping and 2) extracts
this whitespace as text. This might decrease NLP performance. It is recommended to
@@ -1205,9 +1225,37 @@
applications, creating for example named entity annotations. A non-normative algorithm
to integrate these annotations into the original input document is given in <a class="section-ref" href="#nif-backconversion" shape="rect">Appendix G: Conversion NIF2ITS</a>. The algorithm in that appendix is
non-normative since many choices depend on the actual NLP application.</p></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="its-tool-annotation" id="its-tool-annotation" shape="rect"/>5.8 ITS Tools Annotation</h3><p>In some cases, it may be important for instances of data categories to be associated with information about the processor that generated them. For example, the score of the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category (provided via the <code class="its-attr-markup">mtConfidence</code> attribute) is meaningful only when the consumer of the information also knows what MT engine produced it, because the score provides the relative confidence of translations from the same MT engine but does not provide a score that can be reliably compared between MT engines. The same is true for confidence provided for the <a href="#Disambiguation" shape="rect">Disambiguation</a> data category, providing confidence informaton via the <code class="its-attr-markup">disambigConfidence</code> attribute, or the <a href="#terminology" shape="rect">Terminology</a> data category, providing confidence information via the <code class="its-attr-markup">termConfidence</code> attribute.</p><p>ITS 2.0 provides a mechanism to associate such processor information with the use of individual data categories in a document, independently from data category annotations themselves.</p><p>The attribute <code class="its-attr-markup">toolsRef</code> provides a way to associate all the annotations of a given data category within the element with information about the processor that generated those data category annotations.</p><p>The value of <code class="its-attr-markup">toolsRef</code> is a space-separated list of references where each reference is composed of two parts: a data category identifier and an IRI. These two parts are separated by a character <code>|</code> VERTICAL LINE (U+007C).</p><ul><li><p>The data category identifier <a href="#rfc219" shape="rect">MUST</a> be one of the identifiers specified in the <a href="#datacategories-overview" shape="rect">data category overview table</a>.</p></li><li><p>The IRI indicates information about the processor used to generate the data category annotation. No single means is specified for how this IRI should be used to indicate processor information. Possible mechanisms are: to encode information directly in the IRI, e.g. as parameters; to reference an external resource that provides such information, e.g. an XML file or an RDF declaration; or to reference another part of the document that provides such information.</p></li></ul><p>In HTML documents, the mechanism is implemented with the <code class="its-attr-markup">its-tools-ref</code> attribute.</p><p>The attribute applies to the content of the element where it is declared (including its children elements) and to the attributes of that element.</p><p>On any given node, the information provided by this mechanism is a space-separated list of the accumlated references found it the <code class="its-attr-markup">toolsRef</code> attributes
- declared in the enclosing elements and sorted by data category identifiers. For each data category, the IRI part is the one of the inner-most declarartion.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-tool-annotation-1" id="EX-its-tool-annotation-1" shape="rect"/>Example 26: Accumulation and Overriding of the <code class="its-attr-markup">toolsRef</code> Values</div><p>In this example, the text shows the computed tools reference information for the given node. Note that the references are ordered alphabetically and
- that the IRI values are always the ones of the inner-most declaration.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><doc</strong> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
+<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="its-tool-annotation" id="its-tool-annotation" shape="rect"/>5.8 ITS Tools Annotation</h3><p>In some cases, it may be important for instances of data categories to be associated
+ with information about the processor that generated them. For example, the score of the
+ <a href="#mtconfidence" shape="rect">MT Confidence</a> data category (provided via the
+ <code class="its-attr-markup">mtConfidence</code> attribute) is meaningful only when the consumer of the
+ information also knows what MT engine produced it, because the score provides the
+ relative confidence of translations from the same MT engine but does not provide a score
+ that can be reliably compared between MT engines. The same is true for confidence
+ provided for the <a href="#Disambiguation" shape="rect">Disambiguation</a> data category,
+ providing confidence information via the <code class="its-attr-markup">disambigConfidence</code> attribute, or the
+ <a href="#terminology" shape="rect">Terminology</a> data category, providing confidence
+ information via the <code class="its-attr-markup">termConfidence</code> attribute.</p><p>ITS 2.0 provides a mechanism to associate such processor information with the use of
+ individual data categories in a document, independently from data category annotations
+ themselves.</p><p>The attribute <code class="its-attr-markup">toolsRef</code> provides a way to associate all the annotations of a
+ given data category within the element with information about the processor that
+ generated those data category annotations.</p><p>The value of <code class="its-attr-markup">toolsRef</code> is a space-separated list of references where each
+ reference is composed of two parts: a data category identifier and an IRI. These two
+ parts are separated by a character <code>|</code> VERTICAL LINE (U+007C).</p><ul><li><p>The data category identifier <a href="#rfc2119" shape="rect">MUST</a> be one of the
+ identifiers specified in the <a href="#datacategories-overview" shape="rect">data category
+ overview table</a>.</p></li><li><p>The IRI indicates information about the processor used to generate the data
+ category annotation. No single means is specified for how this IRI should be used to
+ indicate processor information. Possible mechanisms are: to encode information
+ directly in the IRI, e.g. as parameters; to reference an external resource that
+ provides such information, e.g. an XML file or an RDF declaration; or to reference
+ another part of the document that provides such information.</p></li></ul><p>In HTML documents, the mechanism is implemented with the <code class="its-attr-markup">its-tools-ref</code>
+ attribute.</p><p>The attribute applies to the content of the element where it is declared (including its
+ children elements) and to the attributes of that element.</p><p>On any given node, the information provided by this mechanism is a space-separated list
+ of the accumulated references found it the <code class="its-attr-markup">toolsRef</code> attributes declared in
+ the enclosing elements and sorted by data category identifiers. For each data category,
+ the IRI part is the one of the inner-most declarartion.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-tool-annotation-1" id="EX-its-tool-annotation-1" shape="rect"/>Example 26: Accumulation and Overriding of the <code class="its-attr-markup">toolsRef</code> Values</div><p>In this example, the text shows the computed tools reference information for the
+ given node. Note that the references are ordered alphabetically and that the IRI
+ values are always the ones of the inner-most declaration.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><doc</strong> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
<span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"mt-confidence|MT1"</span><strong class="hl-tag" style="color: #000096">
></strong>doc node: "mt-confidence|MT1"
<strong class="hl-tag" style="color: #000096"><group</strong> <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"lq-issue|ABC"</span><strong class="hl-tag" style="color: #000096">
@@ -1220,10 +1268,14 @@
<strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">its:toolsRef</span>=<span class="hl-value" style="color: #993300">"disambiguation|XYZ"</span><strong class="hl-tag" style="color: #000096">
></strong>This p node: "disambiguation|XYZ mt-confidence|MT1"<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></doc></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-its-tool-annotation-1.xml" shape="rect">examples/xml/EX-its-tool-annotation-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-tool-annotation-2" id="EX-its-tool-annotation-2" shape="rect"/>Example 27: Example of ITS Tool Annotation</div><p>The <code class="its-attr-markup">toolsRef</code> attribute is used in this XML document to indicate that information about the processor that generated the <code class="its-attr-markup">mtConfidence</code> values
- for the first two <code>p</code> elements are found in element with <code>id="T1"</code> in the external document tools.xml, while that information for the
- third <code>p</code> element is found in the element with <code>id="T2"</code> in the same document. In addition, <code class="its-attr-markup">toolsRef</code> is used to identify a Web
- resource with information about the QA tool used to generate the <a href="#lqissue" shape="rect">Localization Quality Issue</a> annotation in the document.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><doc</strong> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span>
[1178 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/30 13:09:04 1.286
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/30 14:13:00 1.287
@@ -4794,9 +4794,19 @@
<item>The localization had “Pen Drive” when corporate terminology specified that
“USB Stick” was to be used.</item>
<item>The localization text inconsistently used "Start" and "Begin".</item>
+ <item>A text renders the Hungarian term <emph>recsegőék</emph> as “buzzer bridge” in
+ English to translate (a literal translation), but the term used in English should
+ be “wedge block,” as specified in a terminology list supplied to the
+ translator.</item>
</list></cell>
<cell>S or T</cell>
- <cell/>
+ <cell>This value <ref target="#rfc-keywords">MUST NOT</ref> be used for simple
+ typographical errors or word choice not related to defined terminologies. For example,
+ a mistyping of “pin” as “pen” or the use of “imply” instead of “infer” (mistaking two
+ commonly confused words) would not count as terminology issues and should be
+ categorized as either spelling errors or mistranslations, depending on the nature of
+ the issue. Terminology refers <emph>only</emph> to cases where incorrect choices about
+ terms (either formal or commonly defined in a domain) are involved.</cell>
</row>
<row>
<cell><code>mistranslation</code></cell>
@@ -4897,7 +4907,7 @@
<cell>The text is written in the wrong linguistic register of uses slang or other
language variants inappropriate to the text.</cell>
<cell><list>
- <item>A financia text in U.S. English refers to dollars as "bucks".</item>
+ <item>A financial text in U.S. English refers to dollars as "bucks".</item>
</list></cell>
<cell>S or T</cell>
<cell/>
@@ -4921,9 +4931,15 @@
DD.MM.YYYY.</item>
<item>A text for the Irish market uses American-style foot and inch measurements
instead of centimeters.</item>
+ <item>A text intended for a U.S.-based audience uses U.K. spellings such as “centre”
+ and “colour.”</item>
</list></cell>
<cell>S or T</cell>
- <cell/>
+ <cell>This category should be used for spelling errors only if they relate specifically
+ to locale expectations (e.g., a text consitently uses British instead of U.S.
+ spellings for a text intended for the U.S.). If these errors are not systematic (e.g.,
+ a text uses U.S. spellings but has a single instance of “centre”), they should instead
+ be counted as spelling errors.</cell>
</row>
<row>
<cell><code>style</code></cell>
@@ -5027,10 +5043,15 @@
</row>
<row>
<cell><code>whitespace</code></cell>
- <cell>There is a mismatch in whitespace between source and target content.</cell>
+ <cell>There is a mismatch in whitespace between source and target content or the text
+ violates specific rules related to the use of whitespace..</cell>
<cell><list>
<item>A source segment starts with six space characters but the corresponding target
segment has two non-breaking spaces at the start.</item>
+ <item>The text uses a run of 12 space characters instead of a tab character to align
+ numbers in a table.</item>
+ <item>Two space characters appear after a period even though only a single period
+ should be used.</item>
</list></cell>
<cell>S or T</cell>
<cell/>
@@ -5542,6 +5563,10 @@
made to this document since the <ref target="http://www.w3.org/TR/2012/WD-its20-20121023/"
>ITS 2.0 Working Draft 23 October 2012</ref>.</p>
<list type="ordered">
+ <item>Made changes to <ref target="#lqissue-typevalues">descriptions of allowed
+ values</ref> for <ref target="#lqissue">Localization Quality Issue</ref> (specifically
+ <emph>terminology</emph>, <emph>locale-violation</emph>, and <emph>whitespace</emph>
+ to respond to and clarify points raised by Daniel Naber</item>
<item>Clarified usage of <ref target="#domain">Domain</ref> data category in HTML in
response to <ref
target="https://www.w3.org/International/multilingualweb/lt/track/issues/56"
Received on Friday, 30 November 2012 14:13:09 UTC