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

CVS WWW/International/multilingualweb/lt/drafts/its20/TR-version

From: CVS User fsasaki <cvsmail@w3.org>
Date: Tue, 09 Apr 2013 20:57:09 +0000
Message-Id: <E1UPfbJ-0007WT-Oo@gil.w3.org>
To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory gil:/tmp/cvs-serv28825/TR-version

Modified Files:
	Overview.html 
Log Message:
status section update

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html	2013/03/22 15:23:59	1.74
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html	2013/04/09 20:57:09	1.75
@@ -5,46 +5,41 @@
 
 </style><link rel="stylesheet" href="local.css" type="text/css"/><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css"/></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"/></a></p>
 <h1><a name="title" id="title"></a>Internationalization Tag Set (ITS) Version 2.0</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Draft 06 December 2012</h2><dl><dt>This version:</dt><dd>
-         <a href="http://www.w3.org/TR/2012/WD-its20-20121206/">
-        http://www.w3.org/TR/2012/WD-its20-20121206/</a>
+<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Draft 11 April 2013</h2><dl><dt>This version:</dt><dd>
+         <a href="http://www.w3.org/TR/2012/WD-its20-20130411/">
+        http://www.w3.org/TR/2012/WD-its20-20130411/</a>
       </dd><dt>Latest version:</dt><dd>
          <a href="http://www.w3.org/TR/its20/">http://www.w3.org/TR/its20/</a>
-      </dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2012/WD-its20-20121023/">
-        http://www.w3.org/TR/2012/WD-its20-20121023/</a></dd><dt>Editors:</dt><dd>Shaun McCane, Invited Expert</dd><dd>Dave Lewis, TCD</dd><dd>Arle Lommel, DFKI</dd><dd>Jirka Kosek, UEP</dd><dd>Felix Sasaki, DFKI / W3C Fellow</dd><dd>Yves Savourel, ENLASO</dd></dl><p>This document is also available in these non-normative formats: <a href="its20.odd">ODD/XML document</a>, <a href="itstagset20.zip">self-contained zipped archive</a>, and <a href="diffs/diff-wd20121206-wd20121023.html">XHTML Diff markup to previous publication 2012-10-23</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2012 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.eio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>). All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
-<h2><a name="abstract" id="abstract"></a>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/">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>
+      </dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2012/WD-its20-20121206/">
+        http://www.w3.org/TR/2012/WD-its20-20121206/</a></dd><dt>Editors:</dt><dd>Shaun McCane, Invited Expert</dd><dd>Dave Lewis, TCD</dd><dd>Christian Lieske, SAP AG</dd><dd>Arle Lommel, DFKI</dd><dd>Jirka Kosek, UEP</dd><dd>Felix Sasaki, DFKI / W3C Fellow</dd><dd>Yves Savourel, ENLASO</dd></dl><p>This document is also available in these non-normative formats: <a href="its20.odd">ODD/XML document</a>, <a href="itstagset20.zip">self-contained zipped archive</a>, and <a href="diffs/diff-wd20130411-wd20121206.html">XHTML Diff markup to previous publication
+        2012-12-06</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>). All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+<h2><a name="abstract" id="abstract"></a>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/">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" id="status"></a>Status of this Document</h2><p>
             <em>This section describes the status of this document at the time of its publication.
           Other documents may supersede this document. A list of current W3C publications and the
           latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
           http://www.w3.org/TR/.</em>
-         </p><p>This document defines data categories and their implementation as a set of elements and
-        attributes called the <em>Internationalization Tag Set (ITS)</em> 2.0. ITS 2.0 is the
-        successor of <a href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</a>; it is
-        designed to foster the creation of multilingual Web content, focusing on HTML, XML based
-        formats in general, and to leverage localization workflows based on the XML Localization
-        Interchange File Format (XLIFF).</p><p>This document was published by the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
-          Group</a> as a Last Call Working Draft. The Working Group expects to advance this
+         </p><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/">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><p>This document was published by the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
+          Group</a> as an updated working draft. The publication reflects changes made since the 
+        <a href="http://www.w3.org/TR/2012/WD-its20-20121206/">Last Call</a> publication 6 November 2012. The Working Group expects to advance this
         Working Draft to Recommendation status (see <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
-          maturity levels</a>). The Last Call period ends 10 January 2013.</p><p>The normative sections of this document (from <a class="section-ref" href="#notation-terminology">Section 3: Notation and Terminology</a> to
+          maturity levels</a>).</p><p id="open-issues">All <a href="http://tinyurl.com/its20-comments-handling">last call issues</a> in the normative sections (from <a class="section-ref" href="#notation-terminology">Section 3: Notation and Terminology</a> to
           <a class="section-ref" href="#datacategory-description">Section 8: Description of Data Categories</a> and <a class="section-ref" href="#normative-references">Appendix A: References</a> to
-          <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a>) are stable. The other, non-normative sections contain only
-        explanatory material and will be updated in a later working draft. Hence, the Working Group
-        especially encourages feedback on the normative sections. The goal is to move out of last
-        call without any substantive changes to these sections.</p><p>To give feedback send your comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
+          <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a>) have been resolved, with 4 exceptions: @@@@. The other, non-normative sections contain only
+        explanatory material and will be updated in a later working draft. The Working Group
+         encourages feedback until end of April 2013 on the @@@ open issues: @@@@ sections.</p><p>To give feedback send your comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
         WD" in the subject line of your email. The <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/">archives
           for this list</a> are publicly available. See also <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues discussed
           within the Working Group</a> and the <a href="#changelog-since-20121023">list of
@@ -82,6 +77,7 @@
 <div class="toc2">3.5 <a href="#def-rule-elements">Rule Elements</a></div>
 <div class="toc2">3.6 <a href="#iri-usage">Usage of Internationalized Resource Identifiers in ITS</a></div>
 <div class="toc2">3.7 <a href="#def-html">The Term HTML</a></div>
+<div class="toc2">3.8 <a href="#def-css-selector">The Term CSS Selectors</a></div>
 </div>
 <div class="toc1">4 <a href="#conformance">Conformance</a><div class="toc2">4.1 <a href="#conformance-product-schema">Conformance Type 1: ITS Markup Declarations</a></div>
 <div class="toc2">4.2 <a href="#conformance-product-processing-expectations">Conformance Type 2: The Processing Expectations for ITS Markup</a></div>
@@ -93,9 +89,9 @@
 <div class="toc3">5.2.2 <a href="#selection-local">Local Selection in an XML Document</a></div>
 </div>
 <div class="toc2">5.3 <a href="#selectors">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2041">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2065">XPath 1.0</a></div>
 <div class="toc3">5.3.3 <a href="#css-selectors">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2271">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2310">Additional query languages</a></div>
 <div class="toc3">5.3.5 <a href="#its-param">Variables in selectors</a></div>
 </div>
 <div class="toc2">5.4 <a href="#link-external-rules">Link to External Rules</a></div>
@@ -135,8 +131,8 @@
 <div class="toc2">8.9 <a href="#domain">Domain</a><div class="toc3">8.9.1 <a href="#domain-definition">Definition</a></div>
 <div class="toc3">8.9.2 <a href="#domain-implementation">Implementation</a></div>
 </div>
-<div class="toc2">8.10 <a href="#Disambiguation">Disambiguation</a><div class="toc3">8.10.1 <a href="#Disambiguation-definition">Definition</a></div>
-<div class="toc3">8.10.2 <a href="#Disambiguation-implementation">Implementation</a></div>
+<div class="toc2">8.10 <a href="#textanalysis">Text Analysis</a><div class="toc3">8.10.1 <a href="#textanalysis-definition">Definition</a></div>
+<div class="toc3">8.10.2 <a href="#textanalysis-implementation">Implementation</a></div>
 </div>
 <div class="toc2">8.11 <a href="#LocaleFilter">Locale Filter</a><div class="toc3">8.11.1 <a href="#LocaleFilter-definition">Definition</a></div>
 <div class="toc3">8.11.2 <a href="#LocaleFilter-implementation">Implementation</a></div>
@@ -190,15 +186,14 @@
           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">NIF</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">[XML Schema]</a> and
-          RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng">[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/">ITS 2.0 Requirements
+            (ITS)</em>. The document provides implementations for HTML, serializations in <a href="http://nlp2rdf.org/nif-1-0">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">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng">[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/">ITS 2.0 Requirements
             document</a>, in <a title="Internationalization and&#xA;                Localization Markup Requirements" href="#itsreq">[ITS REQ]</a> and <a title="Requirements for Localizable&#xA;                DTD Design" href="#reqlocdtd">[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">[XML i18n BP]</a>
           (potentially in an as yet unwritten best practice document on multilingual Web content),
           or may be addressed in a future version of this specification.</p><div class="div2">
 <h3><a href="#contents"><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="relation-to-its10-and-new-principles" id="relation-to-its10-and-new-principles"></a>1.1 Relation to ITS 1.0 and New Principles</h3><div class="div3">
-<h4><a href="#contents"><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="relation-to-its10" id="relation-to-its10"></a>1.1.1 Relation to ITS 1.0</h4><p>ITS 2.0 has the following relations to ITS 1.0:</p><ul><li><p>It adopts and maintains the following principles from ITS 1.0: </p><ul><li><p>It adopts the use of data categories to define discrete units of
+<h4><a href="#contents"><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="relation-to-its10" id="relation-to-its10"></a>1.1.1 Relation to ITS 1.0</h4><p>ITS 2.0 has the following relations to ITS 1.0 <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10">[ITS 1.0]</a>:</p><ul><li><p>It adopts and maintains the following principles from ITS 1.0: </p><ul><li><p>It adopts the use of data categories to define discrete units of
                     functionality</p></li><li><p>It adopts the separation of data category definition from the mapping of the
                     data category to a given content format</p></li><li><p>It adopts the conformance principle of ITS1.0 that an implementation only
                     needs to implement one data category to claim conformance to ITS 2.0</p></li></ul></li><li><p>ITS 2.0 supports all ITS 1.0 data category definitions and adds new definitions,
@@ -207,11 +202,9 @@
 <h4><a href="#contents"><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"></a>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 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">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">Domain</a></p></li><li><p><a href="#Disambiguation">Disambiguation</a></p></li><li><p><a href="#LocaleFilter">Locale Filter</a></p></li><li><p><a href="#provenance">Provenance</a></p></li><li><p><a href="#externalresource">External Resource</a></p></li><li><p><a href="#target-pointer">Target Pointer</a></p></li><li><p><a href="#idvalue">Id Value</a></p></li><li><p><a href="#preservespace">Preserve Space</a></p></li><li><p><a href="#lqissue">Localization Quality Issue</a></p></li><li><p><a href="#lqrating">Localization Quality Rating</a></p></li><li><p><a href="#mtconfidence">MT Confidence</a></p></li><li><p><a href="#allowedchars">Allowed Characters</a></p></li><li><p><a href="#storagesize">Storage Size</a></p></li></ul></div></div><div class="div2">
+                metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the <a href="#xpath">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">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">Domain</a></p></li><li><p><a href="#textanalysis">Text Analysis</a></p></li><li><p><a href="#LocaleFilter">Locale Filter</a></p></li><li><p><a href="#provenance">Provenance</a></p></li><li><p><a href="#externalresource">External Resource</a></p></li><li><p><a href="#target-pointer">Target Pointer</a></p></li><li><p><a href="#idvalue">Id Value</a></p></li><li><p><a href="#preservespace">Preserve Space</a></p></li><li><p><a href="#lqissue">Localization Quality Issue</a></p></li><li><p><a href="#lqrating">Localization Quality Rating</a></p></li><li><p><a href="#mtconfidence">MT Confidence</a></p></li><li><p><a href="#allowedchars">Allowed Characters</a></p></li><li><p><a href="#storagesize">Storage Size</a></p></li></ul></div></div><div class="div2">
 <h3><a href="#contents"><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"></a>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
@@ -224,8 +217,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">[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. DocBook
-            and DITA 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">DocBook</a>&gt; and <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#technical">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">[XUL]</a>) creates challenges and
             opportunities in the domain of XML internationalization and localization.</p><div class="div3">
@@ -335,21 +327,20 @@
                 third party users, for example, provenance information and quality scoring, and add
                 relevant information for follow-on tasks, processes and services, such as MT
                 post-editing, MT training and MT terminological enhancement.</p></div><div class="div4">
-<h5><a name="users_text_analytics" id="users_text_analytics"></a>1.3.1.6 Text Analytics</h5><p>These types of users fulfil the role of providing services for automatic generation
-                of metadata for improving localization, data integration or knowledge management
-                workflows. This class of users comprises of developers and integrators of services
-                that automate language technology tasks such as domain classification, named entity
-                recognition and disambiguation, term extraction, language identification and others.
-                Text analytics services generate data that contextualizes the raw content with more
-                explicit 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"></a>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 format like <a title="" href="#xliff">[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_text_analytics" id="users_text_analytics"></a>1.3.1.6 Text Analytics</h5><p>This type of service provides automatically generated metadata for improving
+                localization, data integration or knowledge management workflows. This class of
+                users comprises of developers and integrators of services that automate language
+                technology tasks such as domain classification, named entity recognition and
+                disambiguation, term extraction, language identification and others. Text analytics
+                services generate data that contextualizes the raw content with more explicit
+                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"></a>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">[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
@@ -491,7 +482,7 @@
 <strong class="hl-tag" style="color: #000096">&lt;/its:rules&gt;</strong>
 </pre></div><p>[Source file: <a href="examples/html5/EX-translateRule-html5-1.xml">examples/html5/EX-translateRule-html5-1.xml</a>]</p></div><div class="div3">
 <h4><a href="#contents"><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-legacy-html" id="usage-in-legacy-html"></a>1.4.1 Support for legacy HTML content</h4><p>ITS 2.0 does not define how to use ITS in HTML versions prior version 5. Users are
-              encouraged to migrate their content to HTML or XHTML. While it is possible to use
+              encouraged to migrate their content to HTML5 or XHTML. While it is possible to use
                 <code>its-*</code> attributes introduced for HTML5 in older versions of HTML (such
               as 3.2 or 4.01) and pages using these attributes will work without any problems,
                 <code>its-*</code> attributes will be marked as invalid in validators.</p></div></div><div class="div2">
@@ -546,14 +537,15 @@
             <em>This section is informative.</em>
          </p><div class="div2">
 <h3><a href="#contents"><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"></a>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). 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">[CSS 2.1]</a>. The local approach can be compared to the
+              <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">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">[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 and other query languages can be used if supported by
-            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">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
@@ -594,16 +586,9 @@
               example <code class="its-elem-markup">translateRule</code>). Each of these specific elements contains a
                 <code class="its-attr-markup">selector</code> attribute. As its name suggests, this attribute selects the node
               or nodes to which a corresponding ITS information pertains. The values of ITS selector
-              attributes are XPath absolute location paths (or CSS selectors if <a href="#queryLanguage">queryLanguage</a> is set to "css"). Information for the
+              attributes are XPath absolute location paths (or CSS Selectors if <a href="#queryLanguage">queryLanguage</a> is set to "css"). Information for the
               handling of namespaces in these path expressions is taken from namespace declarations
-                <a title="Namespaces in XML&#xA;                (Second Edition)" href="#xmlns">[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">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"></a>Example 11: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096">&lt;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">&gt;</strong>
+                <a title="Namespaces in XML&#xA;                (Second Edition)" href="#xmlns">[XML Names]</a> at the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2"></a>Example 11: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096">&lt;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">&gt;</strong>
   <strong class="hl-tag" style="color: #000096">&lt;prolog&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;title&gt;</strong>Using ITS<strong class="hl-tag" style="color: #000096">&lt;/title&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;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">&gt;</strong>
@@ -669,8 +654,8 @@
             selected nodes. For example, the <a href="#locNote-datacat">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">data category overview table</a>, in <a class="section-ref" href="#datacategories-defaults-etc">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">data category overview table</a>, in <a class="section-ref" href="#datacategories-defaults-etc">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"><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"></a>3 Notation and Terminology</h2><p>
@@ -679,8 +664,11 @@
 <h3><a href="#contents"><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"></a>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">[RFC 2119]</a>.</p><p>The namespace URI that <a href="#rfc-keywords">MUST</a> be used by
-            implementations of this specification is:</p><div class="exampleInner"><div class="exampleOuter"><pre>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">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>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">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">
@@ -690,7 +678,7 @@
               and localization of XML schemas and documents.] The concept of a data
             category is independent of its implementation in an XML and HTML environment (e.g. using
             an element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description">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">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1164" id="d0e1164"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys information as
+                <a class="section-ref" href="#datacategory-description">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1143" id="d0e1143"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys information as
               to whether a piece of content should be translated or not.</p><p>The simplest formalization of this prose description on a schema language independent
               level is a <code class="its-attr-markup">translate</code> attribute with two possible values:
                 "yes" and "no". An implementation on a schema language specific
@@ -741,16 +729,21 @@
             Identifiers (IRIs, <a title="Internationalized Resource&#xA;                Identifiers (IRIs)" href="#rfc3987">[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"><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"></a>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&#xA;                HTML and XHTML" href="#html5">[HTML5]</a>.</p></div></div><div class="div1">
+            in HTML syntax <a title="HTML5" href="#html5">[HTML5]</a>.</p></div><div class="div2">
+<h3><a href="#contents"><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"></a>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">[Selectors Level 3]</a>
+            to prevent confusion with the generic use of the word "selector". <a title="Selectors Level&#xA;                3" href="#css3-selectors">[Selectors Level 3]</a>.</p></div></div><div class="div1">
 <h2><a href="#contents"><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"></a>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">[QAFRAMEWORK]</a>.</p><p>This specification defines three types of conformance: conformance of <a href="#conformance-product-schema">1) ITS markup declarations</a> , conformance of
             <a href="#conformance-product-processing-expectations">2) processing expectations
             for ITS Markup</a> and conformance of <a href="#conformance-product-html-processing-expectations">3) processing expectations
-            for ITS Markup in HTML</a>. Also special <a href="#conformance-class-html5-its">conformance class</a> is defined for using ITS markup in HTML5 document which servers
-          as an applicable specification for HTML5+ITS. These conformance types and classes
-          complement each other. An implementation of this specification <a href="#rfc2119">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">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">Extensibility
+            section</a> of <a title="HTML5" href="#html5">[HTML5]</a>. These conformance types and
+          classes complement each other. An implementation of this specification <a href="#rfc2119">MAY</a> use them separately or together.</p><div class="div2">
 <h3><a href="#contents"><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"></a>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
@@ -873,7 +866,7 @@
               categories</a> they implement, and for each <a href="#def-datacat">data
               category</a> which type of selection they support.</p></div><div class="div2">
 <h3><a href="#contents"><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-class-html5-its" id="conformance-class-html5-its"></a>4.4 Conformance Class for HTML5+ITS documents</h3><p>Conforming HTML5+ITS documents are those that comply with all the conformance criteria
-            for documents as defined in <a title="HTML5 – A vocabulary and associated APIs for&#xA;                HTML and XHTML" href="#html5">[HTML5]</a> with the following
+            for documents as defined in <a title="HTML5" href="#html5">[HTML5]</a> with the following
             exception:</p><ul><li><p><a href="http://dev.w3.org/html5/spec/single-page.html#global-attributes">Global attributes</a> which can be used on all HTML elements are extended by
               attributes for local data categories as defined in <a class="section-ref" href="#html5-local-attributes">Section 6.1: Mapping of Local Data Categories to HTML</a>.</p></li></ul></div></div><div class="div1">
 <h2><a href="#contents"><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-processing" id="its-processing"></a>5 Processing of ITS information</h2><p>
@@ -881,9 +874,13 @@
          </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">Section 6: Using ITS Markup in HTML</a>.</p></div><div class="div2">
 <h3><a href="#contents"><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"></a>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">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">MUST</a> be provided on the element where the ITS markup is used, or on one of its ancestors.
-            There <a href="#rfc-keywords">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">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">MUST</a> be provided on the element where the ITS markup is
+            used, or on one of its ancestors.</p><p>If there is no <code class="its-elem-markup">rules</code> element and there are elements with standoff ITS markup
+            in an XML document, an ITS
+            <code class="its-attr-markup">version</code> attribute <a href="#rfc-keywords">MUST</a> be provided on element with standoff ITS markup or a prefixed ITS
+            <code class="its-attr-markup">version</code> attribute (e.g. <code>its:version</code>) <a href="#rfc-keywords">MUST</a> be provided on one of its ancestors.</p><p>There <a href="#rfc-keywords">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"><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"></a>5.2 Locations of Data Categories</h3><p>ITS data categories can appear in two places:</p><ul><li><p><a href="#selection-global">Global rules</a>: the selection is realized
               within a <code class="its-elem-markup">rules</code> element. It contains <a href="#rule-elements">rule
                 elements</a> for each data category. Each rule element has a <code class="its-attr-markup">selector</code>
@@ -903,9 +900,12 @@
               existing information in the document. For example, the <a href="#locNote-datacat">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">data category overview table</a>, in <a class="section-ref" href="#datacategories-defaults-etc">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">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">data category overview table</a>, in
+                <a class="section-ref" href="#datacategories-defaults-etc">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">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">Section 5.5: Precedence between Selections</a>.</p></div><div class="div3">
 <h4><a href="#contents"><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"></a>5.2.2 Local Selection in an XML Document</h4><p>Local selection in XML documents is realized with <a href="#local-attributes">ITS
@@ -945,9 +945,9 @@
               actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
               on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
               used as a default query language.</p></div><div class="div3">
-<h4><a href="#contents"><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="d0e2041" id="d0e2041"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<h4><a href="#contents"><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="d0e2065" id="d0e2065"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
               attribute.</p><div class="div4">
-<h5><a name="d0e2052" id="d0e2052"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an XPath expression
+<h5><a name="d0e2076" id="d0e2076"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an XPath expression
                 which starts with "<code>/</code>". That is, it must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
                   AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
                   AbsoluteLocationPath</a>s as described in <a href="#xpath">XPath 1.0</a>.
@@ -972,11 +972,11 @@
 <h5><a name="xpath-relative-selector" id="xpath-relative-selector"></a>5.3.2.2 Relative selector</h5><p>The relative selector <a href="#rfc-keywords">MUST</a> use a <a href="http://www.w3.org/TR/xpath/#NT-RelativeLocationPath">RelativeLocationPath</a> or an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">AbsoluteLocationPath</a> as described in <a href="#xpath">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">taClassRefPointer</code>, <code class="its-attr-markup">taIdentPointer</code>,
+                  <code class="its-attr-markup">taIdentRefPointer</code>, <code class="its-attr-markup">taSourcePointer</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>,
@@ -984,28 +984,33 @@
                 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"><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"></a>5.3.3 CSS Selectors</h4><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><p>CSS Selectors are identified by <code>css</code> value in <code class="its-attr-markup">queryLanguage</code>
+<h4><a href="#contents"><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"></a>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">[Selectors Level 3]</a> to prevent confusion with the generic use of the word "selector".
+                See <a href="#css-selectors">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="d0e2246" id="d0e2246"></a>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as selector
-                as defined in <a href="#css3-selectors">Selectors Level 3</a>. Both simple
-                selectors and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2257" id="d0e2257"></a>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be interpreted as selector
-                as defined in <a href="#css3-selectors">Selectors Level 3</a>. Selector is not
+<h5><a name="d0e2287" id="d0e2287"></a>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as selector
+                as defined in <a title="Selectors Level&#xA;                3" href="#css3-selectors">[Selectors Level 3]</a>. Both simple selectors
+                and groups of selectors can be used.</p></div><div class="div4">
+<h5><a name="d0e2297" id="d0e2297"></a>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be interpreted as selector
+                as defined in <a title="Selectors Level&#xA;                3" href="#css3-selectors">[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"><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="d0e2271" id="d0e2271"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional query
-              languages. For each additional query language processor <a href="#rfc-keywords">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>Future versions of this specification <a href="#rfc-keywords">MAY</a> 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"><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="d0e2310" id="d0e2310"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional query
+              languages. For each additional query language the processor <a href="#rfc-keywords">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

[2310 lines skipped]
Received on Tuesday, 9 April 2013 20:57:13 UTC

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