W3C home > Mailing lists > Public > public-multilingualweb-lt-commits@w3.org > March 2013

CVS WWW/International/multilingualweb/lt/drafts/its20

From: CVS User alommel <cvsmail@w3.org>
Date: Thu, 28 Mar 2013 11:21:59 +0000
Message-Id: <E1ULAu7-00016Y-DF@gil.w3.org>
To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv4243

Modified Files:
	its20.html its20.odd 
Log Message:
added note and references per Action-83

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/03/28 10:26:24	1.359
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/03/28 11:21:59	1.360
@@ -6,20 +6,13 @@
 </style><link rel="stylesheet" href="local.css" type="text/css"/><link rel="stylesheet" type="text/css" href="base.css"/></head><body><div class="head">
 <h1><a name="title" id="title" shape="rect"/>Internationalization Tag Set (ITS) Version 2.0</h1>
 <h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Copy</h2><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a> © 2012 <a href="http://www.w3.org/" shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>, <a href="http://ev.buaa.edu.cn/" shape="rect">Beihang</a>). All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer" shape="rect">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks" shape="rect">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents" shape="rect">document use</a> rules apply.</p</div><hr/><div>
-<h2><a name="abstract" id="abstract" shape="rect"/>Abstract</h2><p>
-			The technology described in this document - the
-			<em>Internationalization Tag Set (ITS) 2.0</em>
-			- enhances the foundation to integrate automated processing of human
-			language into core Web technologies. ITS 2.0 bears many commonalities
-			with is predecessor,
-			<a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a>
-			but provides additional concepts that are designed to foster the
-			automated creation and processing of multilingual Web content. ITS
-			2.0 focuses on HTML, XML-based formats in general, and can leverage
-			processing based on the XML Localization Interchange File Format
-			(XLIFF), as well as the Natural Language Processing Interchange
-			Format (NIF).
-		</p></div><div>
+<h2><a name="abstract" id="abstract" shape="rect"/>Abstract</h2><p> The technology described in this document - the <em>Internationalization Tag Set (ITS)
+          2.0</em> - enhances the foundation to integrate automated processing of human language
+        into core Web technologies. ITS 2.0 bears many commonalities with is predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a> but provides additional
+        concepts that are designed to foster the automated creation and processing of multilingual
+        Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
+        processing based on the XML Localization Interchange File Format (XLIFF), as well as the
+        Natural Language Processing Interchange Format (NIF). </p></div><div>
 <h2><a name="status" shape="rect">Status of this Document</a></h2><p><strong>This document is an editors' copy that has no official
                             standing.</strong> Last modified: <script type="text/javascript" xml:space="preserve">
 document.write(document.lastModified);</script>.</p></div><div class="toc">
@@ -158,8 +151,8 @@
           concepts (such as “Translate”) that are important for internationalization and
           localization, and defines implementations of these concepts (termed “ITS data categories”)
           as a set of elements and attributes called the <em>Internationalization Tag Set
-            (ITS)</em>. The document provides implementations for HTML, serializations in <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF (NLP Interchange Format)</a>, and provides definitions of
-          ITS elements and attributes in the form of XML Schema <a title="XML Schema Part 1:&#xA;                Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.</p><p>This document aims to realize many of the ideas formulated in the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/" shape="rect">ITS 2.0 Requirements
+            (ITS)</em>. The document provides implementations for HTML, serializations in <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF (NLP Interchange Format)</a>, and provides
+          definitions of ITS elements and attributes in the form of XML Schema <a title="XML Schema Part 1:&#xA;                Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.</p><p>This document aims to realize many of the ideas formulated in the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/" shape="rect">ITS 2.0 Requirements
             document</a>, in <a title="Internationalization and&#xA;                Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a> and <a title="Requirements for Localizable&#xA;                DTD Design" href="#reqlocdtd" shape="rect">[Localizable DTDs]</a>.</p><p>Not all requirements listed there are addressed in this document. Those which are not
           addressed here are either covered in <a title="Best&#xA;                Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>
           (potentially in an as yet unwritten best practice document on multilingual Web content),
@@ -174,10 +167,8 @@
 <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
-                metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the <a href="#xpath" shape="rect">XPath version 1.0</a>.
-                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
+                metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the <a href="#xpath" shape="rect">XPath version 1.0</a>. 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="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
@@ -191,8 +182,7 @@
             design and development, and the corresponding process is referred to as
             internationalization. For a detailed explanation of the terms “localization” and
             “internationalization”, see <a title="" href="#geo-i18n-l10n" shape="rect">[l10n i18n]</a>.</p><span class="editor-note">[Ed. note: Note: This should refer to the best practice document as well, when
-            ready.]</span><p>The increasing usage of XML as a medium for documentation-related content (e.g. <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook#technical" shape="rect">DocBook</a>&gt;
-            and <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#technical" shape="rect">DITA</a> as formats for writing structured documentation, well suited to computer
+            ready.]</span><p>The increasing usage of XML as a medium for documentation-related content (e.g. <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook#technical" shape="rect">DocBook</a>&gt; and <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#technical" shape="rect">DITA</a> as formats for writing structured documentation, well suited to computer
             hardware and software manuals) and software-related content (e.g. the eXtensible User
             Interface Language <a title="exTensible User Interface Language" href="#xul" shape="rect">[XUL]</a>) creates challenges and
             opportunities in the domain of XML internationalization and localization.</p><div class="div3">
@@ -311,11 +301,11 @@
                 information. This can be used to improve the output quality in machine translation
                 systems, search result relevance in information retrieval systems, as well as
                 management and integration of unstructured data in knowledge management systems.</p></div><div class="div4">
-<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers" shape="rect"/>1.3.1.7 Localization Workflow Managers</h5><p>These types of users are concerned with localization workflows in which content goes
-                through certain steps: preparation for localization, start of the localization
-                process by e.g. a conversion into a bitext (aligned parallel text) format like <a title="" href="#xliff" shape="rect">[XLIFF]</a>, the actual localization by human translators or machine
-                translation and other adaptations of content, and finally the integration of the
-                localized content into the original format. That format is often based on XML or
+<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers" shape="rect"/>1.3.1.7 Localization Workflow Managers</h5><p>These types of users are concerned with localization workflows in which content
+                goes through certain steps: preparation for localization, start of the localization
+                process by e.g. a conversion into a bitext (aligned parallel text) format like <a title="" href="#xliff" shape="rect">[XLIFF]</a>, the actual localization by human translators or
+                machine translation and other adaptations of content, and finally the integration of
+                the localized content into the original format. That format is often based on XML or
                 HTML; (Web) content management systems are widely used for content creation, and
                 their integration with localization workflows is an important task for the workflow
                 manager. For the integration of content creation and localization, metadata plays a
@@ -513,13 +503,14 @@
          </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 href="xpath" shape="rect">XPath</a>.
-            In a sense, ITS markup “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,&#xA;                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
+            primarily element and attribute nodes, as defined in <a href="xpath" shape="rect">XPath</a>. In
+            a sense, ITS markup “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,&#xA;                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
+            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
               (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
             XML Schema document for a proprietary document format).</p><p>The following two examples sketch the distinction between the local and global
@@ -635,8 +626,8 @@
             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),
             or point to existing information elsewhere in the document (using a
-              <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
+              <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">
 <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>
@@ -645,8 +636,11 @@
 <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="notation" id="notation" shape="rect"/>3.1 Notation</h3><p id="rfc-keywords">The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
             NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are
             to be interpreted as described in <a title="" href="#rfc2119" shape="rect">[RFC 2119]</a>.</p><p>The namespace URI that <a href="#rfc-keywords" shape="rect">MUST</a> be used by
-            implementations of this specification is:</p><div class="exampleInner"><div class="exampleOuter"><pre xml:space="preserve">http://www.w3.org/2005/11/its</pre></div></div><p id="its-namespace-prefix">The namespace prefix used in this specification for XML implementations
-            of ITS for the above URI is "its". It is recommended that XML implementations of this specification use this prefix, unless there is existing dedicated markup in use for a given data category. In HTML there is no namespace prefix: "its-" is used to indicate ITS 2.0 attributes in HTML documents. See <a class="section-ref" href="#html5-local-attributes" shape="rect">Section 6.1: Mapping of Local Data Categories to HTML</a> for details.</p><p>In addition, the following namespaces are used in this document:</p><ul><li><p><code>http://www.w3.org/2001/XMLSchema</code> for the XML Schema namespace, here
+            implementations of this specification is:</p><div class="exampleInner"><div class="exampleOuter"><pre xml:space="preserve">http://www.w3.org/2005/11/its</pre></div></div><p id="its-namespace-prefix">The namespace prefix used in this specification for XML
+            implementations of ITS for the above URI is "its". It is recommended that XML
+            implementations of this specification use this prefix, unless there is existing
+            dedicated markup in use for a given data category. In HTML there is no namespace prefix:
+              "its-" is used to indicate ITS 2.0 attributes in HTML documents. See <a class="section-ref" href="#html5-local-attributes" shape="rect">Section 6.1: Mapping of Local Data Categories to HTML</a> for details.</p><p>In addition, the following namespaces are used in this document:</p><ul><li><p><code>http://www.w3.org/2001/XMLSchema</code> for the XML Schema namespace, here
               used with the prefix “xs”</p></li><li><p><code>http://www.w3.org/1999/xlink</code> for the XLink namespace, here used with
               the prefix “xlink”</p></li><li><p><code>http://www.w3.org/1999/xhtml</code> for the HTML namespace, here used with
               the prefix “h”</p></li></ul></div><div class="div2">
@@ -706,23 +700,22 @@
                <a href="#rfc-keywords" shape="rect">MUST</a> allow the usage of Internationalized Resource
             Identifiers (IRIs, <a title="Internationalized Resource&#xA;                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 in HTML syntax
-              <a title="HTML5" href="#html5" shape="rect">[HTML5]</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="def-css-selector" id="def-css-selector" shape="rect"/>3.8 The Term CSS Selectors</h3><p>This specification uses the term <code>CSS Selectors</code> in the 
-            sense of <code>Selectors</code> as specifies in <a title="Selectors Level 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a> 
-            to prevent confusion with the generic use of the word "selector".
-            <a title="Selectors Level 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</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
+            in HTML syntax <a title="HTML5" href="#html5" shape="rect">[HTML5]</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="def-css-selector" id="def-css-selector" shape="rect"/>3.8 The Term CSS Selectors</h3><p>This specification uses the term <code>CSS Selectors</code> in the sense of
+              <code>Selectors</code> as specifies in <a title="Selectors Level&#xA;                3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>
+            to prevent confusion with the generic use of the word "selector". <a title="Selectors Level&#xA;                3" href="#css3-selectors" shape="rect">[Selectors Level 3]</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
           with <a title="QA Framework:&#xA;                Specification Guidelines" href="#qa-framework" shape="rect">[QAFRAMEWORK]</a>.</p><p>This specification defines three types of conformance: conformance of <a href="#conformance-product-schema" shape="rect">1) ITS markup declarations</a> , conformance of
             <a href="#conformance-product-processing-expectations" shape="rect">2) processing expectations
             for ITS Markup</a> and conformance of <a href="#conformance-product-html-processing-expectations" shape="rect">3) processing expectations
-            for ITS Markup in HTML</a>. Also special <a href="#conformance-class-html5-its" shape="rect">conformance class</a> is defined for using ITS markup in HTML5 documents, HTML5+ITS, which serves
-          as an <em>applicable specification</em> in the sense specified in the
-          <a href="http://www.w3.org/TR/html5/infrastructure.html#extensibility" shape="rect">Extensibility section</a> of
-          <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>. These conformance types and classes
-          complement each other. An implementation of this specification <a href="#rfc2119" shape="rect">MAY</a> use them separately or together.</p><div class="div2">
+            for ITS Markup in HTML</a>. Also special <a href="#conformance-class-html5-its" shape="rect">conformance class</a> is defined for using ITS markup in HTML5 documents, HTML5+ITS,
+          which serves as an <em>applicable specification</em> in the sense specified in the
+            <a href="http://www.w3.org/TR/html5/infrastructure.html#extensibility" shape="rect">Extensibility
+            section</a> of <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>. These conformance types and
+          classes complement each other. An implementation of this specification <a href="#rfc2119" shape="rect">MAY</a> use them separately or together.</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="conformance-product-schema" id="conformance-product-schema" shape="rect"/>4.1 Conformance Type 1: ITS Markup Declarations</h3><p>
                <em>Description:</em> ITS markup declarations encompass all declarations that are
             part of the Internationalization Tag Set. They do not concern the <em>usage</em> of
@@ -853,9 +846,10 @@
          </p><div class="note"><p class="prefix"><b>Note:</b></p><p>Additional definitions about processing of HTML are given in <a class="section-ref" href="#html5-markup" shape="rect">Section 6: Using ITS Markup in HTML</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="its-version-attribute" id="its-version-attribute" shape="rect"/>5.1 Indicating the Version of ITS</h3><p>The version of the ITS schema defined in this specification is "2.0". The
             version is indicated by the ITS <code class="its-attr-markup">version</code> attribute. This attribute is
-            mandatory for the <code class="its-elem-markup">rules</code> element, where it <a href="#rfc-keywords" shape="rect">MUST</a> be in no namespace.</p><p>If there is no <code class="its-elem-markup">rules</code> element in an XML document, a prefixed ITS <code class="its-attr-markup">version</code> attribute (e.g. <code>its:version</code>)
-              <a href="#rfc-keywords" shape="rect">MUST</a> be provided on the element where the ITS markup is used, or on one of its ancestors.
-            There <a href="#rfc-keywords" shape="rect">MUST NOT</a> be two different versions of ITS in the same document.</p><p>External, linked rules can have different versions than internal rules.</p></div><div class="div2">
+            mandatory for the <code class="its-elem-markup">rules</code> element, where it <a href="#rfc-keywords" shape="rect">MUST</a> be in no namespace.</p><p>If there is no <code class="its-elem-markup">rules</code> element in an XML document, a prefixed ITS
+              <code class="its-attr-markup">version</code> attribute (e.g. <code>its:version</code>) <a href="#rfc-keywords" shape="rect">MUST</a> be provided on the element where the ITS markup is
+            used, or on one of its ancestors. There <a href="#rfc-keywords" shape="rect">MUST NOT</a> be
+            two different versions of ITS in the same document.</p><p>External, linked rules can have different versions than internal 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="datacategory-locations" id="datacategory-locations" shape="rect"/>5.2 Locations of Data Categories</h3><p>ITS data categories can appear in two places:</p><ul><li><p><a href="#selection-global" shape="rect">Global rules</a>: the selection is realized
               within a <code class="its-elem-markup">rules</code> element. It contains <a href="#rule-elements" shape="rect">rule
                 elements</a> for each data category. Each rule element has a <code class="its-attr-markup">selector</code>
@@ -875,9 +869,12 @@
               existing information in the document. For example, the <a href="#locNote-datacat" shape="rect">Localization Note</a> data category can be used for adding notes to selected
               nodes, or for pointing to existing notes in the document. For the former purpose, a
                 <code class="its-elem-markup">locNote</code> element can be used. For the latter purpose, a
-                <code class="its-attr-markup">locNotePointer</code> attribute can be used.</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: markup for pointing and adding the same information <a href="#rfc-keywords" shape="rect">MUST NOT</a> appear in the same rule element.</p><p>Global rules can appear in the XML document they will be applied to, or in a separate
+                <code class="its-attr-markup">locNotePointer</code> attribute can be used.</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: markup for pointing and adding the same
+              information <a href="#rfc-keywords" shape="rect">MUST NOT</a> appear in the same rule
+              element.</p><p>Global rules can appear in the XML document they will be applied to, or in a separate
               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
@@ -944,11 +941,11 @@
 <h5><a name="xpath-relative-selector" id="xpath-relative-selector" shape="rect"/>5.3.2.2 Relative 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">disambigClassRefPointer</code>, <code class="its-attr-markup">disambigIdentPointer</code>,
-                <code class="its-attr-markup">disambigIdentRefPointer</code>, <code class="its-attr-markup">disambigSourcePointer</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>,
+                information: <code class="its-attr-markup">allowedCharactersPointer</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">disambigSourcePointer</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>,
@@ -956,27 +953,26 @@
                 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">
-<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="css-selectors" id="css-selectors" shape="rect"/>5.3.3 CSS Selectors</h4><div class="note"><p class="prefix"><b>Note:</b></p><p>The term <code>CSS Selectors</code> is used throughout the specification in the 
-              sense of <code>Selectors</code> as specified in <a title="Selectors Level 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a> 
-              to prevent confusion with the generic use of the word "selector". 
-              See <a href="#css-selectors" shape="rect">The term CSS Selector</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-implementations">The working group will not provide a
-              CSS Selectors based implementation; nevertheless there are several existing libraries,
-              which can translate CSS Selectors to XPath, so that XPath selectors based 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>
+<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="css-selectors" id="css-selectors" shape="rect"/>5.3.3 CSS Selectors</h4><div class="note"><p class="prefix"><b>Note:</b></p><p>The term <code>CSS Selectors</code> is used throughout the specification in the
+                sense of <code>Selectors</code> as specified in <a title="Selectors Level&#xA;                3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a> to prevent confusion with the generic use of the word "selector".
+                See <a href="#css-selectors" shape="rect">The term CSS Selector</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-implementations">The working group will not provide a CSS
+                Selectors based implementation; nevertheless there are several existing libraries,
+                which can translate CSS Selectors to XPath, so that XPath selectors based
+                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="d0e2298" id="d0e2298" 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">
+                as defined in <a title="Selectors Level&#xA;                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="d0e2308" id="d0e2308" 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
+                as defined in <a title="Selectors Level&#xA;                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="d0e2321" id="d0e2321" 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>, <code>xquery3</code>, <code>xslt2</code>,
-              <code>xslt3</code>.</p></div><div class="div3">
+              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>,
+                <code>xquery3</code>, <code>xslt2</code>, <code>xslt3</code>.</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="its-param" id="its-param" shape="rect"/>5.3.5 Variables in selectors</h4><p id="parameter-for-rules">A <code class="its-elem-markup">param</code> element (or several ones) can be placed
               as the first child element(s) of the <code class="its-elem-markup">rules</code> element to define the default
               values of variables used in the various selectors used in the rules.</p><p>Implementation <a href="#rfc2119" shape="rect">MUST</a> support the <code class="its-elem-markup">param</code> element
@@ -1065,14 +1061,19 @@
 </pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-4.xml" shape="rect">examples/xml/EX-link-external-rules-4.xml</a>]</p></div><p>Applications processing global ITS markup <a href="#rfc-keywords" shape="rect">MUST</a>
             recognize the XLink <code class="its-attr-markup">href</code> attribute in the <code class="its-elem-markup">rules</code> element; they <a href="#rfc-keywords" shape="rect">MUST</a> load the corresponding referenced document and
             process its rules element before processing the content of the <code class="its-elem-markup">rules</code> element
-            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 (see <a href="#EX-link-external-rules-2" shape="rect">Example 20</a>). The linking mechanism is recursive in a depth-first approach, and subsequently after the processing the rules MUST be read top-down (see <a href="#EX-link-external-rules-3" shape="rect">Example 21</a>).</p></div><div class="div2">
+            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 (see <a href="#EX-link-external-rules-2" shape="rect">Example 20</a>). The linking mechanism is recursive
+            in a depth-first approach, and subsequently after the processing the rules MUST be read
+            top-down (see <a href="#EX-link-external-rules-3" shape="rect">Example 21</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="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
                   <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>Selection via inherited values. This applies only to element nodes. The inheritance rules are laid out in a dedicated <a href="#datacategories-overview" shape="rect">datacategory overview table</a>, see column "<span class="quote">Inheritance for element nodes</span>". Selection via inheritance takes precedence over default values, see below item.</p></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
+                  non-ITS mechanisms (such as processing instructions for linking rules).</p></div></li><li><p>Selection via inherited values. This applies only
+              to element nodes. The inheritance rules are laid out in a dedicated <a href="#datacategories-overview" shape="rect">datacategory overview table</a>, see column
+                "<span class="quote">Inheritance for element nodes</span>". Selection via inheritance takes
+              precedence over default values, see below item.</p></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
             precedence.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The precedence order fulfills the same purpose as the built-in template rules of <a title="XSL Transformations (XSLT)&#xA;                Version 1.0" href="#xslt10" shape="rect">[XSLT 1.0]</a>. Override semantics are always complete, that is
               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
@@ -1142,8 +1143,7 @@
               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 based on <a title="" href="#NIF" 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 based on <a title="" href="#NIF" 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
@@ -1245,12 +1245,26 @@
               <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">annotatorsRef</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><div class="note"><p class="prefix"><b>Note:</b></p><ul><li><p id="annotators-ref-usage-scenarios">Three cases of providing tool information can be expected:</p><ol class="depth1"><li><p>information about tools used for creating or modifying the textual content;</p></li><li><p>information about tools that do 1), but also create ITS annotations, see <a class="section-ref" href="#list-of-elements-and-attributes" shape="rect">Appendix G: List of ITS 2.0 Global Elements and Local Attributes</a>; </p></li><li><p>information about tools that don’t modify or create content, but just create ITS annotations.</p></li></ol><p>
-                        <code class="its-attr-markup">annotatorsRef</code> is only meant to be used when actual ITS annotation is involved, that is for 2) and 3). To express tool information related only to the creation or modification of textual content and independent of ITS data categories, that is case 1), one should use the tool or <code class="its-attr-markup">toolRef</code> attribute provided by the <a href="#provenance" shape="rect">Provenance</a> data category.</p></li><li><p>An example of case 2) is an MT engine that modifies content and creates ITS <a href="#mtconfidence" shape="rect">MT Confidence</a> annotations. Here the situation may occur that several tools are involved in creating MT Confidence annotations: the MT engine and the tool inserting the markup. The annotatorsRef attribute should identify the tool most useful in further processes, in this case the MT engine.</p></li></ul></div><p>The value of <code class="its-attr-markup">annotatorsRef</code> is a space-separated list of referencs 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
+            themselves.</p><p>The attribute <code class="its-attr-markup">annotatorsRef</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><div class="note"><p class="prefix"><b>Note:</b></p><ul><li><p id="annotators-ref-usage-scenarios">Three cases of providing tool
+                  information can be expected:</p><ol class="depth1"><li><p>information about tools used for creating or modifying the textual
+                      content;</p></li><li><p>information about tools that do 1), but also create ITS annotations, see
+                        <a class="section-ref" href="#list-of-elements-and-attributes" shape="rect">Appendix G: List of ITS 2.0 Global Elements and Local Attributes</a>; </p></li><li><p>information about tools that don’t modify or create content, but just
+                      create ITS annotations.</p></li></ol><p>
+                        <code class="its-attr-markup">annotatorsRef</code> is only meant to be used when actual ITS
+                  annotation is involved, that is for 2) and 3). To express tool information related
+                  only to the creation or modification of textual content and independent of ITS
+                  data categories, that is case 1), one should use the tool or <code class="its-attr-markup">toolRef</code>
+                  attribute provided by the <a href="#provenance" shape="rect">Provenance</a> data
+                  category.</p></li><li><p>An example of case 2) is an MT engine that modifies content and creates ITS
+                    <a href="#mtconfidence" shape="rect">MT Confidence</a> annotations. Here the situation
+                  may occur that several tools are involved in creating MT Confidence annotations:
+                  the MT engine and the tool inserting the markup. The annotatorsRef attribute
+                  should identify the tool most useful in further processes, in this case the MT
+                  engine.</p></li></ul></div><p>The value of <code class="its-attr-markup">annotatorsRef</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
@@ -1260,9 +1274,9 @@
                 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-annotators-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 in the <code class="its-attr-markup">annotatorsRef</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 declaration.</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">annotatorsRef</code> Values</div><p>In this example, the text shows the computed tools reference information for the
+            of the accumulated references found in the <code class="its-attr-markup">annotatorsRef</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 declaration.</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">annotatorsRef</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">&lt;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:annotatorsRef</span>=<span class="hl-value" style="color: #993300">"mt-confidence|MT1"</span><strong class="hl-tag" style="color: #000096">
@@ -1283,9 +1297,8 @@
               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">annotatorsRef</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">&lt;doc</strong> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span>
+              document. In addition, <code class="its-attr-markup">annotatorsRef</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">&lt;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">its:annotatorsRef</span>=<span class="hl-value" style="color: #993300">"mt-confidence|file:///tools.xml#T1 lq-issue|http://www.qalsp-ex.com/qatools/transcheckv1.3"</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">&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;p</strong> <span class="hl-attribute" style="color: #F5844C">its:mtConfidence</span>=<span class="hl-value" style="color: #993300">"0.78"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>Text translated with tool T1<strong class="hl-tag" style="color: #000096">&lt;/p&gt;</strong>
@@ -1295,12 +1308,12 @@
     <strong class="hl-tag" style="color: #000096">&lt;p</strong> <span class="hl-attribute" style="color: #F5844C">its:mtConfidence</span>=<span class="hl-value" style="color: #993300">"0.34"</span> <span class="hl-attribute" style="color: #F5844C">its:annotatorsRef</span>=<span class="hl-value" style="color: #993300">"mt-confidence|file:///tools.xml#T2"</span><strong class="hl-tag" style="color: #000096">&gt;</strong> Text translated
         with tool T2<strong class="hl-tag" style="color: #000096">&lt;/p&gt;</strong>
 <strong class="hl-tag" style="color: #000096">&lt;/doc&gt;</strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-its-tool-annotation-2.xml" shape="rect">examples/xml/EX-its-tool-annotation-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-tool-annotation-html5-1" id="EX-its-tool-annotation-html5-1" shape="rect"/>Example 28: Example of ITS Tool Annotation</div><p>The <code class="its-attr-markup">its-annotators-ref</code> attributes are used in this HTML document to indicate
-              that the <a href="#mtconfidence" shape="rect">MT Confidence</a> annotation on the first two
-                <code>span</code> elements come from one MT (French to English) engine, while the
-              annotation on the third comes from another (Italian to English) engine. Both
-                <code class="its-attr-markup">its-annotators-ref</code> attributes refer to a Web resource for information about
-              the engine generating the <a href="#mtconfidence" shape="rect">MT Confidence</a>
+</pre></div><p>[Source file: <a href="examples/xml/EX-its-tool-annotation-2.xml" shape="rect">examples/xml/EX-its-tool-annotation-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-tool-annotation-html5-1" id="EX-its-tool-annotation-html5-1" shape="rect"/>Example 28: Example of ITS Tool Annotation</div><p>The <code class="its-attr-markup">its-annotators-ref</code> attributes are used in this HTML document to
+              indicate that the <a href="#mtconfidence" shape="rect">MT Confidence</a> annotation on the
+              first two <code>span</code> elements come from one MT (French to English) engine,
+              while the annotation on the third comes from another (Italian to English) engine. Both
+                <code class="its-attr-markup">its-annotators-ref</code> attributes refer to a Web resource for information
+              about the engine generating the <a href="#mtconfidence" shape="rect">MT Confidence</a>
               annotation.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096">&lt;html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">en</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;head&gt;</strong>
         <strong class="hl-tag" style="color: #000096">&lt;meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
@@ -1318,8 +1331,8 @@
     <strong class="hl-tag" style="color: #000096">&lt;/body&gt;</strong>
 <strong class="hl-tag" style="color: #000096">&lt;/html&gt;</strong>
 </pre></div><p>[Source file: <a href="examples/html5/EX-its-tool-annotation-html5-1.html" shape="rect">examples/html5/EX-its-tool-annotation-html5-1.html</a>]</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="html5-markup" id="html5-markup" shape="rect"/>6 Using ITS Markup in HTML</h2><div class="note"><p class="prefix"><b>Note:</b></p><p>Please note that the term <code>HTML</code> refers to HTML5 or its successor in HTML syntax
-          <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></div><div class="div2">
+<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="html5-markup" id="html5-markup" shape="rect"/>6 Using ITS Markup in HTML</h2><div class="note"><p class="prefix"><b>Note:</b></p><p>Please note that the term <code>HTML</code> refers to HTML5 or its successor in
+            HTML syntax <a title="HTML5" href="#html5" shape="rect">[HTML5]</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="html5-local-attributes" id="html5-local-attributes" shape="rect"/>6.1 Mapping of Local Data Categories to HTML</h3><p>All data categories defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a>
             and having local implementation might be used in HTML with the exception of <a href="#trans-datacat" shape="rect">Translate</a>, <a href="#directionality" shape="rect">Directionality</a>, <a href="#ruby-annotation" shape="rect">Ruby</a>, and <a href="#language-information" shape="rect">Language
               Information</a> data categories.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above mentioned data categories are excluded because HTML has native markup for
@@ -1328,15 +1341,20 @@
             following rules:</p><ol class="depth1"><li><p>Attribute name is prefixed with <code>its-</code></p></li><li><p>Each uppercase letter in the attribute name is replaced by <code>-</code>
                 (U+002D) followed by a lowercase variant of the letter.</p></li></ol><p>
             </p><p>
-               <a href="#EX-within-text-local-1" shape="rect">Example 53</a> demonstrates the <a href="#elements-within-text" shape="rect">Elements Within Text</a> data category with the local XML attribute <code class="its-attr-markup">withinText</code>. <a href="#EX-within-text-local-html5-1" shape="rect">Example 54</a> demonstrates the counterpart in HTML, that is the local attribute <code class="its-attr-markup">its-within-text</code>.</p><p>Values of attributes which corresponds to data categories with a predefined set of
+               <a href="#EX-within-text-local-1" shape="rect">Example 53</a> demonstrates the <a href="#elements-within-text" shape="rect">Elements Within Text</a> data category with the local
+            XML attribute <code class="its-attr-markup">withinText</code>. <a href="#EX-within-text-local-html5-1" shape="rect">Example 54</a> demonstrates the counterpart in HTML, that is
+            the local attribute <code class="its-attr-markup">its-within-text</code>.</p><p>Values of attributes which corresponds to data categories with a predefined set of
             values <a href="#rfc2119" shape="rect">MUST</a> be matched ASCII-case-insensitively. </p><div class="note"><p class="prefix"><b>Note:</b></p><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in
               HTML terminology data category can be stored as <code class="its-attr-markup">its-term</code>,
                 <code>ITS-TERM</code>, <code>its-Term</code> etc. All those attributes are treated
-              as equivalent and will get normalized upon DOM construction.</p></div><p>Values of attributes which corresponds to data categories which use <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double" shape="rect">XML Schema
-            double data type</a>
-               <a href="#rfc2119" shape="rect">MUST</a> be also valid floating-point numbers as defined in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></div><div class="div2">
+              as equivalent and will get normalized upon DOM construction.</p></div><p>Values of attributes which corresponds to data categories which use <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double" shape="rect">XML Schema double
+              data type</a>
+               <a href="#rfc2119" shape="rect">MUST</a> be also valid floating-point numbers as defined in
+              <a title="HTML5" href="#html5" shape="rect">[HTML5]</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="html5-global-rules" id="html5-global-rules" shape="rect"/>6.2 Global rules</h3><p>Various aspects for global rules in general, external global rules or inline global
-            rules need to be taken into account. An example of an HTML5 document using global rules is <a href="#EX-translate-html5-global-1" shape="rect">Example 8</a>. The corresponding rules file is <a href="#EX-translate-html5-global-1-rules-file" shape="rect">Example 9</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>By default XPath 1.0 will be used for selection in global rules. If users prefer
+            rules need to be taken into account. An example of an HTML5 document using global rules
+            is <a href="#EX-translate-html5-global-1" shape="rect">Example 8</a>. The corresponding rules
+            file is <a href="#EX-translate-html5-global-1-rules-file" shape="rect">Example 9</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>By default XPath 1.0 will be used for selection in global rules. If users prefer
               easier selection mechanism, they can switch query language to CSS selectors by using
               the <code class="its-attr-markup">queryLanguage</code> attribute, see <a class="section-ref" href="#queryLanguage" shape="rect">Section 5.3.1: Choosing Query Language</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>HTML5 parsing algorithm automatically puts all HTML elements into XHTML namespace
                 (<code>http://www.w3.org/1999/xhtml</code>). Selectors used in global rules must
@@ -1349,17 +1367,29 @@
             element itself <a href="#rfc2119" shape="rect">SHOULD</a> be child of <code>head</code>
             element. Comments <a href="#rfc2119" shape="rect">MUST NOT</a> be used inside global rules.
             Each <code>script</code> element <a href="#rfc2119" shape="rect">MUST NOT</a> contain more than
-            one <code class="its-elem-markup">rules</code> element.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="note-html-rules-location">It is preferred to use external global rules linked using the <code>link</code> element than to have global rules embedded in the document.</p></div></div><div class="div2">

[690 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/03/28 10:36:26	1.354
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/03/28 11:21:59	1.355
@@ -4032,6 +4032,15 @@
                   subsequent process examines this markup to ensure that changes were
                 made.</p></item>
             </list>
+            <note><p xml:id="selecting-issues">What issues should be considered in quality
+                assessment tasks depends on the nature of the project and tools used. For more
+                information on setting translation project specifications and determining quality
+                expectations, implementers are encouraged to consult <ptr target="#isots11669"
+                  type="bibref"/>. Details about translation specifications are available at <ptr
+                  target="#structuredspecs" type="bibref"/>. While these documents do not directly
+                address the definition of quality metrics, they provide useful guidance for
+                implementers interested in determining which localization quality issue values
+                should be used for specific scenarios.</p></note>
             <p>The data category defines five pieces of information:</p>
             <table border="1" xml:id="lqissueDefs">
               <row role="head">
@@ -5015,8 +5024,8 @@
             <cell>
               <list>
                 <item>The source segment reads "The Professor said to Smith that he would hear from
-                  his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek,
-                  hogy he would hear from his lawyer."</item>
+                  his lawyer" but the Hungarian localization reads "A professzor azt mondta
+                  Smithnek, hogy he would hear from his lawyer."</item>
               </list>
             </cell>
             <cell>T</cell>
@@ -5317,8 +5326,8 @@
               <list>
                 <item>A new version of a tool returns information on an issue that has not been
                   previously checked and that is not yet classified.</item>
-                <item>A text is defective in ways that defy categorization, such as the appearance of
-                  nonsense garbled text of unknown origin (e.g., a translation shows an
+                <item>A text is defective in ways that defy categorization, such as the appearance
+                  of nonsense garbled text of unknown origin (e.g., a translation shows an
                   unintelligible result and/or appears unrelated to the source material).</item>
               </list>
             </cell>
@@ -5473,6 +5482,9 @@
           <bibl xml:id="iso30042" n="ISO 30042">(International Organization for Standardization).
               <title>TermBase eXchange (TBX)</title>. [Geneva]: International Organization for
             Standardization, 2008.</bibl>
+          <bibl xml:id="isots11669" n="ISO/TS 11669:2002">(International Organization for
+            Standardization). <title>Translation projects – General guidance</title>. [Geneva]:
+            International Organization for Standardization, 2012.</bibl>
           <bibl xml:id="itsreq" n="ITS REQ">Yves Savourel. <title>
               <ref target="http://www.w3.org/TR/2006/WD-itsreq-20060518/">Internationalization and
                 Localization Markup Requirements</ref>
@@ -5535,6 +5547,9 @@
             Definition Languages (DSDL) -- Part 3: <title>Rule-based validation --
               Schematron</title>. International Organization for Standardization (ISO) ISO/IEC
             19757-3:2003.</bibl>
+          <bibl xml:id="structuredspecs" n="Structured Specifications">(BYU Translation Research
+            Group). <title>Structured Specifications and Translation Parameters</title>. Available
+            at <ref target="http://www.ttt.org/specs">http://www.ttt.org/specs</ref>.</bibl>
           <bibl xml:id="tei" n="TEI">Lou Burnard and Syd Bauman (eds). <title>
               <ref target="http://www.tei-c.org/Guidelines/P5/">Text Encoding Initiative Guidelines
                 development version (P5)</ref>
@@ -5979,6 +5994,10 @@
               Type values</ref> to properly use RFC2119 values. See <ref
               target="https://www.w3.org/International/multilingualweb/lt/track/issues/124"
               >issue-124</ref>.</item>
+          <item>Updated <ref target="#lqissue">Localization Quality Issue</ref> to reference ISO/TS
+            11669 and Structure specifications. See <ref
+              target="https://www.w3.org/International/multilingualweb/lt/track/issues/83"
+              >issue-83</ref>.</item>
         </list>
         <p xml:id="changelog-since-20121023">The following log records major changes that have been
           made to this document since the <ref target="http://www.w3.org/TR/2012/WD-its20-20121023/"
Received on Thursday, 28 March 2013 11:22:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:40 UTC