- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Tue, 27 Nov 2012 14:53:17 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv26086
Modified Files:
its20.html its20.odd
Log Message:
Many edits, see http://www.w3.org/2012/11/27-mlw-lt-minutes.html
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/11/27 11:30:11 1.265
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/11/27 14:53:17 1.266
@@ -35,12 +35,12 @@
<div class="toc2">2.3 <a href="#basic-concepts-addingpointing" shape="rect">Adding Information or Pointing to Existing Information</a></div>
</div>
<div class="toc1">3 <a href="#notation-terminology" shape="rect">Notation and Terminology</a><div class="toc2">3.1 <a href="#notation" shape="rect">Notation</a></div>
-<div class="toc2">3.2 <a href="#def-schemalanguage" shape="rect">Schema Language</a></div>
-<div class="toc2">3.3 <a href="#def-datacat" shape="rect">Data category</a></div>
-<div class="toc2">3.4 <a href="#def-selection" shape="rect">Selection</a></div>
-<div class="toc2">3.5 <a href="#def-local-attributes" shape="rect">ITS Local Attributes</a></div>
-<div class="toc2">3.6 <a href="#def-rule-elements" shape="rect">Rule Elements</a></div>
-<div class="toc2">3.7 <a href="#iri-usage" shape="rect">Usage of Internationalized Resource Identifiers in ITS</a></div>
+<div class="toc2">3.2 <a href="#def-datacat" shape="rect">Data category</a></div>
+<div class="toc2">3.3 <a href="#def-selection" shape="rect">Selection</a></div>
+<div class="toc2">3.4 <a href="#def-local-attributes" shape="rect">ITS Local Attributes</a></div>
+<div class="toc2">3.5 <a href="#def-rule-elements" shape="rect">Rule Elements</a></div>
+<div class="toc2">3.6 <a href="#iri-usage" shape="rect">Usage of Internationalized Resource Identifiers in ITS</a></div>
+<div class="toc2">3.7 <a href="#def-html" shape="rect">The Term HTML</a></div>
</div>
<div class="toc1">4 <a href="#conformance" shape="rect">Conformance</a><div class="toc2">4.1 <a href="#conformance-product-schema" shape="rect">Conformance Type 1: ITS Markup Declarations</a></div>
<div class="toc2">4.2 <a href="#conformance-product-processing-expectations" shape="rect">Conformance Type 2: The Processing Expectations for ITS Markup</a></div>
@@ -52,9 +52,9 @@
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors" shape="rect">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage" shape="rect">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2165" shape="rect">XPath 1.0</a></div>
-<div class="toc3">5.3.3 <a href="#d0e2416" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2455" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2085" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.3 <a href="#d0e2291" shape="rect">CSS Selectors</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2330" shape="rect">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param" shape="rect">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules" shape="rect">Link to External Rules</a></div>
@@ -63,75 +63,75 @@
<div class="toc2">5.7 <a href="#conversion-to-nif" shape="rect">Conversion to NIF</a></div>
<div class="toc2">5.8 <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a></div>
</div>
-<div class="toc1">6 <a href="#datacategory-description" shape="rect">Description of Data Categories</a><div class="toc2">6.1 <a href="#datacategories-defaults-etc" shape="rect">Position, Defaults, Inheritance and Overriding of Data Categories</a></div>
-<div class="toc2">6.2 <a href="#trans-datacat" shape="rect">Translate</a><div class="toc3">6.2.1 <a href="#translatability-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.2.2 <a href="#translatability-implementation" shape="rect">Implementation</a></div>
+<div class="toc1">6 <a href="#html5-markup" shape="rect">Using ITS Markup in HTML5</a><div class="toc2">6.1 <a href="#html5-local-attributes" shape="rect">Mapping of Local Data Categories to HTML5</a></div>
+<div class="toc2">6.2 <a href="#html5-external-global-rules" shape="rect">External Rules</a></div>
+<div class="toc2">6.3 <a href="#html5-inline-global-rules" shape="rect">Inline Global Rules in HTML5</a></div>
+<div class="toc2">6.4 <a href="#html5-standoff-markup" shape="rect">Standoff Markup in HTML5</a></div>
+<div class="toc2">6.5 <a href="#html5-selection-precedence" shape="rect">Precedence between Selections</a></div>
</div>
-<div class="toc2">6.3 <a href="#locNote-datacat" shape="rect">Localization Note</a><div class="toc3">6.3.1 <a href="#locNote-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.3.2 <a href="#locNote-implementation" shape="rect">Implementation</a></div>
+<div class="toc1">7 <a href="#xhtml5-markup" shape="rect">Using ITS Markup in XHTML</a></div>
+<div class="toc1">8 <a href="#datacategory-description" shape="rect">Description of Data Categories</a><div class="toc2">8.1 <a href="#datacategories-defaults-etc" shape="rect">Position, Defaults, Inheritance and Overriding of Data Categories</a></div>
+<div class="toc2">8.2 <a href="#trans-datacat" shape="rect">Translate</a><div class="toc3">8.2.1 <a href="#translatability-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.2.2 <a href="#translatability-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.4 <a href="#terminology" shape="rect">Terminology</a><div class="toc3">6.4.1 <a href="#terminology-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.4.2 <a href="#terminology-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.3 <a href="#locNote-datacat" shape="rect">Localization Note</a><div class="toc3">8.3.1 <a href="#locNote-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.3.2 <a href="#locNote-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.5 <a href="#directionality" shape="rect">Directionality</a><div class="toc3">6.5.1 <a href="#directionality-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.5.2 <a href="#directionality-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.4 <a href="#terminology" shape="rect">Terminology</a><div class="toc3">8.4.1 <a href="#terminology-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.4.2 <a href="#terminology-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.6 <a href="#ruby-annotation" shape="rect">Ruby</a><div class="toc3">6.6.1 <a href="#ruby-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.6.2 <a href="#ruby-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.5 <a href="#directionality" shape="rect">Directionality</a><div class="toc3">8.5.1 <a href="#directionality-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.5.2 <a href="#directionality-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.7 <a href="#language-information" shape="rect">Language Information</a><div class="toc3">6.7.1 <a href="#langinfo-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.7.2 <a href="#langinfo-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.6 <a href="#ruby-annotation" shape="rect">Ruby</a><div class="toc3">8.6.1 <a href="#ruby-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.6.2 <a href="#ruby-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.8 <a href="#elements-within-text" shape="rect">Elements Within Text</a><div class="toc3">6.8.1 <a href="#within-text-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.8.2 <a href="#within-text-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.7 <a href="#language-information" shape="rect">Language Information</a><div class="toc3">8.7.1 <a href="#langinfo-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.7.2 <a href="#langinfo-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.9 <a href="#domain" shape="rect">Domain</a><div class="toc3">6.9.1 <a href="#domain-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.9.2 <a href="#domain-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.8 <a href="#elements-within-text" shape="rect">Elements Within Text</a><div class="toc3">8.8.1 <a href="#within-text-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.8.2 <a href="#within-text-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.10 <a href="#Disambiguation" shape="rect">Disambiguation</a><div class="toc3">6.10.1 <a href="#Disambiguation-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.10.2 <a href="#Disambiguation-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.9 <a href="#domain" shape="rect">Domain</a><div class="toc3">8.9.1 <a href="#domain-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.9.2 <a href="#domain-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.11 <a href="#LocaleFilter" shape="rect">Locale Filter</a><div class="toc3">6.11.1 <a href="#LocaleFilter-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.11.2 <a href="#LocaleFilter-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.10 <a href="#Disambiguation" shape="rect">Disambiguation</a><div class="toc3">8.10.1 <a href="#Disambiguation-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.10.2 <a href="#Disambiguation-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.12 <a href="#provenance" shape="rect">Provenance</a><div class="toc3">6.12.1 <a href="#provenance-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.12.2 <a href="#provenance-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.11 <a href="#LocaleFilter" shape="rect">Locale Filter</a><div class="toc3">8.11.1 <a href="#LocaleFilter-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.11.2 <a href="#LocaleFilter-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.13 <a href="#externalresource" shape="rect">External Resource</a><div class="toc3">6.13.1 <a href="#externalresource-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.13.2 <a href="#externalresource-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.12 <a href="#provenance" shape="rect">Provenance</a><div class="toc3">8.12.1 <a href="#provenance-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.12.2 <a href="#provenance-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.14 <a href="#target-pointer" shape="rect">Target Pointer</a><div class="toc3">6.14.1 <a href="#target-pointer-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.14.2 <a href="#target-pointer-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.13 <a href="#externalresource" shape="rect">External Resource</a><div class="toc3">8.13.1 <a href="#externalresource-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.13.2 <a href="#externalresource-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.15 <a href="#idvalue" shape="rect">Id Value</a><div class="toc3">6.15.1 <a href="#idvalue-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.15.2 <a href="#idvalue-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.14 <a href="#target-pointer" shape="rect">Target Pointer</a><div class="toc3">8.14.1 <a href="#target-pointer-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.14.2 <a href="#target-pointer-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.16 <a href="#preservespace" shape="rect">Preserve Space</a><div class="toc3">6.16.1 <a href="#preservespace-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.16.2 <a href="#preservespace-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.15 <a href="#idvalue" shape="rect">Id Value</a><div class="toc3">8.15.1 <a href="#idvalue-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.15.2 <a href="#idvalue-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.17 <a href="#lqissue" shape="rect">Localization Quality Issue</a><div class="toc3">6.17.1 <a href="#lqissue-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.17.2 <a href="#lqissue-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.16 <a href="#preservespace" shape="rect">Preserve Space</a><div class="toc3">8.16.1 <a href="#preservespace-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.16.2 <a href="#preservespace-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.18 <a href="#lqprecis" shape="rect">Localization Quality Précis</a><div class="toc3">6.18.1 <a href="#lqprecis-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.18.2 <a href="#lqprecis-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.17 <a href="#lqissue" shape="rect">Localization Quality Issue</a><div class="toc3">8.17.1 <a href="#lqissue-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.17.2 <a href="#lqissue-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.19 <a href="#mtconfidence" shape="rect">MT Confidence</a><div class="toc3">6.19.1 <a href="#mtconfidence-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.19.2 <a href="#mtconfidence-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.18 <a href="#lqprecis" shape="rect">Localization Quality Précis</a><div class="toc3">8.18.1 <a href="#lqprecis-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.18.2 <a href="#lqprecis-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.20 <a href="#allowedchars" shape="rect">Allowed Characters</a><div class="toc3">6.20.1 <a href="#allowedchars-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.20.2 <a href="#allowedchars-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.19 <a href="#mtconfidence" shape="rect">MT Confidence</a><div class="toc3">8.19.1 <a href="#mtconfidence-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.19.2 <a href="#mtconfidence-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.21 <a href="#storagesize" shape="rect">Storage Size</a><div class="toc3">6.21.1 <a href="#storagesize-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.21.2 <a href="#storagesize-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">8.20 <a href="#allowedchars" shape="rect">Allowed Characters</a><div class="toc3">8.20.1 <a href="#allowedchars-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.20.2 <a href="#allowedchars-implementation" shape="rect">Implementation</a></div>
</div>
+<div class="toc2">8.21 <a href="#storagesize" shape="rect">Storage Size</a><div class="toc3">8.21.1 <a href="#storagesize-definition" shape="rect">Definition</a></div>
+<div class="toc3">8.21.2 <a href="#storagesize-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc1">7 <a href="#html5-markup" shape="rect">Using ITS Markup in HTML5</a><div class="toc2">7.1 <a href="#html5-local-attributes" shape="rect">Mapping of Local Data Categories to HTML5</a></div>
-<div class="toc2">7.2 <a href="#html5-external-global-rules" shape="rect">External Rules</a></div>
-<div class="toc2">7.3 <a href="#html5-inline-global-rules" shape="rect">Inline Global Rules in HTML5</a></div>
-<div class="toc2">7.4 <a href="#html5-standoff-markup" shape="rect">Standoff Markup in HTML5</a></div>
-<div class="toc2">7.5 <a href="#html5-selection-precedence" shape="rect">Precedence between Selections</a></div>
</div>
-<div class="toc1">8 <a href="#xhtml5-markup" shape="rect">Using ITS Markup in XHTML</a></div>
</div>
<h3><a name="appendices" id="appendices" shape="rect"/>Appendices</h3><div class="toc1">A <a href="#normative-references" shape="rect">References</a></div>
<div class="toc1">B <a href="#its-mime-type" shape="rect">Internationalization Tag Set (ITS) MIME Type</a></div>
@@ -244,7 +244,7 @@
these different types of users, and their usage of ITS. In order to support all of
these users, the information about what markup should be supported to enable worldwide
use and effective localization of content is provided in this specification in two
- ways:</p><ul><li><p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a></p></li></ul><div class="div4">
+ ways:</p><ul><li><p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a></p></li></ul><div class="div4">
<h5><a name="schema-dev-new" id="schema-dev-new" shape="rect"/>1.3.1.1Schema developers starting a schema from the ground up</h5><p>This type of user will find proposals for attribute and element names to be
included in their new schema (also called "host vocabulary"). Using the attribute
and element names proposed in the ITS specification may be helpful because it leads
@@ -428,7 +428,7 @@
attributes</a>.</p><span class="editor-note">[Ed. note: Add example of HTML5 with local attributes for illustartion
purposes]</span><p>For the so-called “<a href="#basic-concepts-selection-global" shape="rect">global
approach</a>” in HTML5, this specification defines a link type for referring to files
- with global rules in <a class="section-ref" href="#html5-external-global-rules" shape="rect">Section 7.2: External Rules</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 8: Using ITS global rules in HTML5</div><p>The <code>link</code> element points to the rules file
+ with global rules in <a class="section-ref" href="#html5-external-global-rules" shape="rect">Section 6.2: External Rules</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 8: Using ITS global rules in HTML5</div><p>The <code>link</code> element points to the rules file
<code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
<strong class="hl-tag" style="color: #000096"><html></strong>
@@ -464,9 +464,9 @@
as an abstract notion for information needed for the internationalization and
localization of XML documents and HTML5 documents. This abstraction is helpful in
realizing independence from any one particular implementation (e.g., as an element or
- attribute). (See <a class="section-ref" href="#def-datacat" shape="rect">Section 3.3: Data category</a> for a definition of the
- term data categories, <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> for the
- definition of the various ITS data categories, and subsections in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> for the data category
+ attribute). (See <a class="section-ref" href="#def-datacat" shape="rect">Section 3.2: Data category</a> for a definition of the
+ term data categories, <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> for the
+ definition of the various ITS data categories, and subsections in <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> for the data category
implementations.)</p><p>Powerful <em>selection mechanism:</em> For ITS markup that appears in an XML
instance, the XML nodes to which the ITS-related information pertains must be clearly
defined. Thus, ITS defines <a href="#termdef-selection" shape="rect">selection</a> mechanisms
@@ -495,7 +495,7 @@
<a title="XML Linking Language
 1.1" href="#xlink1" shape="rect">[XLink 1.1]</a>, by providing mostly global attributes for the
implementation of ITS data categories. Avoiding elements for ITS purposes as much as
possible ensures ease of integration into existing markup schemes, see <a href="http://www.w3.org/TR/itsreq/#impact" shape="rect">section 3.14</a> in <a title="Internationalization and
 Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a>. Only for some requirements do additional child
- elements have to be used, see for example <a class="section-ref" href="#ruby-annotation" shape="rect">Section 6.6: Ruby</a>.</p></li><li><p>ITS has no dependency on technologies which are still under
+ elements have to be used, see for example <a class="section-ref" href="#ruby-annotation" shape="rect">Section 8.6: Ruby</a>.</p></li><li><p>ITS has no dependency on technologies which are still under
development.</p></li><li><p>ITS fits with existing work in the W3C architecture (e.g. use of <a title="XML Path Language (XPath)
 Version 1.0" href="#xpath" shape="rect">[XPath 1.0]</a> for the selection mechanism and use of IRI's <a title="Internationalized Resource
 Identifiers (IRIs)" href="#rfc3987" shape="rect">[RFC 3987]</a> as references to relevant external
resources).</p></li></ul></div></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts" id="basic-concepts" shape="rect"/>2 Basic Concepts</h2><p>
@@ -641,25 +641,16 @@
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>The namespace prefix used in this specification for this URI is “its”. It is
recommended that implementations of this specification use this prefix.</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://relaxng.org/ns/structure/1.0</code> for the RELAX NG namespace, here
- used with the prefix “rng”</p></li><li><p><code>http://www.w3.org/1999/xlink</code> for the XLink namespace, here used with
- the prefix “xlink”</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="def-schemalanguage" id="def-schemalanguage" shape="rect"/>3.2 Schema Language</h3><p>
- [<a name="t001" id="t001" title="schema" shape="rect">Definition</a>:
- <span class="new-term">Schema language</span> refers in this specification to an XML-related modeling
- or validation language such as XML Schema or RELAX NG.]
- </p><div class="note"><p class="prefix"><b>Note:</b></p><p>This specification provides schemas in the format of XML Schema and RELAX NG.
- However, these schemas are only non-normative; <a href="#conformance-product-schema" shape="rect">conformance for ITS markup declarations</a>
- defines only mandatory positions of ITS declarations in schemas. This makes it
- possible to use ITS with any schema language that allows for using these
- positions.</p></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="def-datacat" id="def-datacat" shape="rect"/>3.3 Data category</h3><p>
+ 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">
+<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-datacat" id="def-datacat" shape="rect"/>3.2 Data category</h3><p>
[<a name="t002" id="t002" title="data category" shape="rect">Definition</a>: ITS defines <span class="new-term">data category</span>
as an abstract concept for a particular type of information for internationalization
and localization of XML schemas and documents.] The concept of a data
- category is independent of its implementation in an XML environment (e.g. using an
- element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "implementation" subsections in
- <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1205" id="d0e1205" shape="rect"/>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
+ category is independent of its implementation in an XML and HTML environment (e.g. using an
+ element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "implementation" subsections in
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1188" id="d0e1188" shape="rect"/>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
to whether a piece of content should be translated or not.</p><p>The simplest formalization of this prose description on a schema language independent
level is a <code class="its-attr-markup">translate</code> attribute with two possible values:
"yes" and "no". An implementation on a schema language specific
@@ -667,19 +658,16 @@
for example, an XML Schema document or an RELAX NG document. A different
implementation would be a <code class="its-elem-markup">translateRule</code> element that allows for specifying
<a href="#selection-global" shape="rect">global rules</a> about the <a href="#trans-datacat" shape="rect">Translate</a> data category.</p></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="def-selection" id="def-selection" shape="rect"/>3.4 Selection</h3><p>
+<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-selection" id="def-selection" shape="rect"/>3.3 Selection</h3><p>
[<a name="termdef-selection" id="termdef-selection" title="Selection" shape="rect">Definition</a>:
<span class="new-term">selection</span>
- encompasses mechanisms to specify to what parts of an XML document an ITS data
+ encompasses mechanisms to specify to what parts of an XML or HTML document an ITS data
category and its values should be applied to.] Selection is discussed in
detail in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. Selection can be applied
globally, see <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>, and locally, see <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.2: Local Selection in an XML Document</a>. As for global selection, ITS information
can be <a href="#def-adding-pointing" shape="rect">added</a> to the selected nodes, or it can
<a href="#def-adding-pointing" shape="rect">point to existing information</a> which is
- related to selected nodes. </p><p id="selection-and-inclusion-mechanisms">Selection relies on the information that is
- given in the XML Information Set <a title="XML Information Set
 (Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>. ITS
- applications <a href="#rfc-keywords" shape="rect">MAY</a> implement inclusion mechanisms such
- as XInclude or DITA's <a title="OASIS
 Darwin Information Typing Architecture (DITA) Language Specification
 v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> conref.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="note-object-selection">The selection of the ITS data categories applies to
+ related to selected nodes. </p><div class="note"><p class="prefix"><b>Note:</b></p><p id="note-object-selection">The selection of the ITS data categories applies to
textual values contained within element or attribute nodes. In some cases these nodes
form pointers to other resources; a well-known example is the <code>src</code> attribute
on the <code>img</code> element in HTML. The ITS <a href="#trans-datacat" shape="rect">Translate</a> data category applies to the text of the pointer itself, not the
@@ -696,24 +684,22 @@
<strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"instructions.jpg"</span><strong class="hl-tag" style="color: #000096">/></strong>, the truth is not always out there.<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></text></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-notation-terminology-1.xml" shape="rect">examples/xml/EX-notation-terminology-1.xml</a>]</p></div></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="def-local-attributes" id="def-local-attributes" shape="rect"/>3.5 ITS Local Attributes</h3><p>
+<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-local-attributes" id="def-local-attributes" shape="rect"/>3.4 ITS Local Attributes</h3><p>
[<a name="local-attributes" id="local-attributes" title="ITS Local Attributes" shape="rect">Definition</a>:
<span class="new-term">ITS Local
- Attributes</span> are all attributes defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> as a local markup.]
+ Attributes</span> are all attributes defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> as a local markup.]
</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-rule-elements" id="def-rule-elements" shape="rect"/>3.6 Rule Elements</h3><p>
+<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-rule-elements" id="def-rule-elements" shape="rect"/>3.5 Rule Elements</h3><p>
[<a name="rule-elements" id="rule-elements" title="Rule Elements" shape="rect">Definition</a>:
<span class="new-term">Rule Elements</span> are
- all elements defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> as
+ all elements defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> as
elements for global rules.]
</p></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="iri-usage" id="iri-usage" shape="rect"/>3.7 Usage of Internationalized Resource Identifiers in ITS</h3><span class="editor-note">[Ed. note: Below list is not up to date.]</span><p>The attributes <code class="its-attr-markup">href</code>, <code class="its-attr-markup">locNoteRef</code> and <code class="its-attr-markup">termInfoRef</code> which contain resource identifiers <a href="#rfc-keywords" shape="rect">MUST</a> allow the usage of Internationalized Resource
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="iri-usage" id="iri-usage" shape="rect"/>3.6 Usage of Internationalized Resource Identifiers in ITS</h3><p>All attributes that have the type <code>anyURI</code> in the normative RELAX NG schema in <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a>
+ <a href="#rfc-keywords" shape="rect">MUST</a> allow the usage of Internationalized Resource
Identifiers (IRIs, <a title="Internationalized Resource
 Identifiers (IRIs)" href="#rfc3987" shape="rect">[RFC 3987]</a> or its successor) to ease the
- adoption of ITS in international application scenarios.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The ITS schemas in <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a> are not normative.
- Hence this specification defines no validation requirements for IRI values in ITS
- markup. For processing of these values, relying on IRIs imposes no specific
- requirements. The reason is that the processing happens on the info set level <a title="XML Information Set
 (Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>, where no difference between IRIs and URIs
- exists.</p></div></div></div><div class="div1">
+ adoption of ITS in international application scenarios.</p></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="def-html" id="def-html" shape="rect"/>3.7 The Term HTML</h3><p>This specification uses the term <code>HTML</code> to refer to HTML5 or its successor <a title="HTML5 – A vocabulary and associated APIs for
 HTML and XHTML" href="#html5" shape="rect">[HTML5]</a>.</p></div></div><div class="div1">
<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
@@ -753,25 +739,16 @@
type <a href="#rfc-keywords" shape="rect">MUST</a> list all markup declarations they
implement.</p><p>
<em>Examples: </em> Examples of the usage of ITS markup declarations in various
- existing schemas are given in a separate document <a title="Best
 Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p><span class="editor-note">[Ed. note: Below statement about schemas is wrong if the ITS schemas will be normative.]</span><div class="note"><p class="prefix"><b>Note:</b></p><p>Since the ITS markup declarations are schema language independent, each schema
- language can use its own, possibly multiple, mechanisms to implement the conformance
- clauses for ITS markup declarations. For example, an XML DTD can use parameter
- entities to encapsulate the <a href="#local-attributes" shape="rect">ITS local
- attributes</a>, or declare them directly for each element. The appropriate steps to
- integrate ITS into a schema depend on the design of this schema (e.g. whether it
- already has a customization layer that uses parameter entities). The ITS schemas in
- the format of XML Schema and RELAX NG in <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a>
- are only informative examples.</p></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="conformance-product-processing-expectations" id="conformance-product-processing-expectations" shape="rect"/>4.2 Conformance Type 2: The Processing Expectations for ITS Markup</h3><span class="editor-note">[Ed. note: All traces of HTML has to be removed if we will proceed with CT 3 and
- HTML+ITS CC.]</span><p>
+ existing schemas are given in a separate document <a title="Best
 Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="conformance-product-processing-expectations" id="conformance-product-processing-expectations" shape="rect"/>4.2 Conformance Type 2: The Processing Expectations for ITS Markup</h3><p>
<em>Description:</em> Processors need to compute the ITS information that pertains
- to a node in an XML or HTML5 document. The ITS processing expectations define how the
+ to a node in an XML document. The ITS processing expectations define how the
computation has to be carried out. Correct computation involves support for <a href="#def-selection" shape="rect">selection mechanism</a>, <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
characteristics</a>, and <a href="#selection-precedence" shape="rect">precedence</a>. The
markup <a href="#rfc-keywords" shape="rect">MAY</a> be valid against a schema which conforms to
the clauses in <a class="section-ref" href="#conformance-product-schema" shape="rect">Section 4.1: Conformance Type 1: ITS Markup Declarations</a>.</p><p>
<em>Definitions related to this conformance type:</em> The processing expectations
- for ITS markup make use of selection mechanisms defined in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. The individual data categories defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> have <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
+ for ITS markup make use of selection mechanisms defined in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. The individual data categories defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> have <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
characteristics</a>, and allow for using ITS markup in various positions (<a href="#selection-global" shape="rect">global</a> and <a href="#selection-local" shape="rect">local</a>).</p><p>
<em>Who uses this conformance type:</em> Applications that need to process the
nodes captured by a data category for internationalization or localization. Examples of
@@ -793,39 +770,36 @@
definitions for selections defined in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</a>, for the type of selections it processes.</p></li></ul></li><li><p id="its-conformance-2-2">
<em>2-2:</em> If an application claims to
process ITS markup for the global selection mechanism, it <a href="#rfc-keywords" shape="rect">MUST</a> process an XLink <code class="its-attr-markup">href</code> attribute found
- on a <code class="its-elem-markup">rules</code> elements. If he application processes HTML5 documents, it <a href="#rfc-keywords" shape="rect">MUST</a> process an HTML <code>href</code> attribute
- found on an HTML <code>link</code> element. The <code>link</code> element <a href="#rfc-keywords" shape="rect">MUST</a> also have a <code>rel</code> attribute with the
- value <code>its-rules</code>.</p></li><li><p id="its-conformance-2-3">
+ on a <code class="its-elem-markup">rules</code> elements.</p></li><li><p id="its-conformance-2-3">
<em>2-3:</em> If an application claims to
- process ITS markup implementing the conformance clauses 2-1, 2-2 and 2-3, it <a href="#rfc-keywords" shape="rect">MUST</a> process that markup with HTML5 or with XML
+ process ITS markup implementing the conformance clauses 2-1, 2-2 and 2-3, it <a href="#rfc-keywords" shape="rect">MUST</a> process that markup with XML
documents.</p></li><li><p id="its-conformance-2-4">
<em>2-4:</em> After processing ITS information
on the basis of conformance clauses <a href="#its-conformance-2-1" shape="rect">2-1</a> and
- <a href="#its-conformance-2-2" shape="rect">2-2</a>, an application <a href="#rfc-keywords" shape="rect">MAY</a> convert an XML or HTML document (or its DOM
- representation) to NIF, using the algorithm described in <a class="section-ref" href="#conversion-to-nif" shape="rect">Section 5.7: Conversion to NIF</a>.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a> essentially
+ <a href="#its-conformance-2-2" shape="rect">2-2</a>, an application <a href="#rfc-keywords" shape="rect">MAY</a> convert an XML document to NIF, using the algorithm described in <a class="section-ref" href="#conversion-to-nif" shape="rect">Section 5.7: Conversion to NIF</a>.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a> essentially
means that the conversion to NIF is an optional feature of ITS 2.0, and that the
conversion is independent of whether ITS information has been made available via the
global or local selection mechanisms, see conformance clause <a href="#its-conformance-2-1-1" shape="rect">2-1-1</a>.</p></div><p id="its-processing-conformance-claims">Statements related to this conformance type
<a href="#rfc-keywords" shape="rect">MUST</a> list all <a href="#def-datacat" shape="rect">data
categories</a> they implement, and for each <a href="#def-datacat" shape="rect">data
category</a> which type of selection they support, whether they support processing
- of XML and / or HTML5. If the implementation provides the conversion to NIF (see
- conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="http://phaedrus.scss.tcd.ie/its2.0/its-testsuite.html#" shape="rect">ITS 2.0 test
+ of XML. If the implementation provides the conversion to NIF (see
+ conformance clause <a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="https://github.com/finnle/ITS-2.0-Testsuite/" shape="rect">ITS 2.0 test
suite</a>. All tests specify which data category is processed (clause 2-1); they
are relevant for (clause 2-1-1) global or local selection, or both; they require the
processing of defaults and precedence of selections (clauses 2-1-2 and 2-1-3); for
each data category there are tests with linked rules (2-2); and all types of tests are
- given for XML and HTML5 content (clause 2-3). In addition, there are test cases for
+ given for XML (clause 2-3). In addition, there are test cases for
conversion to NIF (clause 2-4). Implementors are encouraged to organize their
documentation in a similar way, so that users of ITS 2.0 easily can understand the
- processing capabilities availably.</p></div><span class="editor-note">[Ed. note: Need to update link to test suite once the test suite is moved.]</span></div><div class="div2">
+ processing capabilities available.</p></div><span class="editor-note">[Ed. note: Need to update link to test suite once the test suite is moved.]</span></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="conformance-product-html-processing-expectations" id="conformance-product-html-processing-expectations" shape="rect"/>4.3 Conformance Type 3: Processing Expectations for ITS Markup in HTML</h3><p>
<em>Description:</em> Processors need to compute the ITS information that pertains
- to a node in a HTML5 document. The ITS processing expectations define how the
+ to a node in a HTML document. The ITS processing expectations define how the
computation has to be carried out. Correct computation involves support for <a href="#def-selection" shape="rect">selection mechanism</a>, <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
characteristics</a>, and <a href="#html5-selection-precedence" shape="rect">precedence</a>.</p><p>
<em>Definitions related to this conformance type:</em> The processing expectations
- for ITS markup make use of selection mechanisms defined in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. The individual data categories defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> have <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
+ for ITS markup make use of selection mechanisms defined in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. The individual data categories defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> have <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding
characteristics</a>, and allow for using ITS markup in various positions (<a href="#html5-local-attributes" shape="rect">local</a>, <a href="#html5-external-global-rules" shape="rect">external global</a> and <a href="#html5-inline-global-rules" shape="rect">inline global</a>).</p><p>
<em>Who uses this conformance type:</em> Applications that need to process the
nodes captured by a data category for internationalization or localization. Examples of
@@ -844,7 +818,7 @@
<em>3-1-2:</em> the <a href="#datacategories-defaults-etc" shape="rect">default selections for the data
category</a>.</p></li><li><p id="its-conformance-3-1-3">
<em>3-1-3:</em> the precedence
- definitions for selections defined in <a class="section-ref" href="#html5-selection-precedence" shape="rect">Section 7.5: Precedence between Selections</a>, for the type of selections it processes.</p></li></ul></li><li><p id="its-conformance-3-2">
+ definitions for selections defined in <a class="section-ref" href="#html5-selection-precedence" shape="rect">Section 6.5: Precedence between Selections</a>, for the type of selections it processes.</p></li></ul></li><li><p id="its-conformance-3-2">
<em>3-2:</em> If an application claims to
process ITS markup for the global selection mechanism, it <a href="#rfc-keywords" shape="rect">MUST</a> process a <code class="its-attr-markup">href</code> attribute found on a
<code>link</code> elements which has a <code>rel</code> attribute with the value
@@ -858,10 +832,10 @@
<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-class-html5-its" id="conformance-class-html5-its" shape="rect"/>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
 HTML and XHTML" href="#html5" shape="rect">[HTML5]</a> with the following
exception:</p><ul><li><p><a href="http://dev.w3.org/html5/spec/single-page.html#global-attributes" shape="rect">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" shape="rect">Section 7.1: Mapping of Local Data Categories to HTML5</a>.</p></li></ul></div></div><div class="div1">
+ attributes for local data categories as defined in <a class="section-ref" href="#html5-local-attributes" shape="rect">Section 6.1: Mapping of Local Data Categories to HTML5</a>.</p></li></ul></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="its-processing" id="its-processing" shape="rect"/>5 Processing of ITS information</h2><p>
<em>This section is normative.</em>
- </p><div class="div2">
+ </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 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="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. If there is no <code class="its-elem-markup">rules</code> element in an XML
@@ -875,9 +849,9 @@
elements</a> for each data category. Each rule element has a <code class="its-attr-markup">selector</code>
attribute and possibly other attributes. The <code class="its-attr-markup">selector</code> attribute contains an
absolute selector as defined in <a class="section-ref" href="#selectors" shape="rect">Section 5.3: Query Language of Selectors</a>.</p></li><li><p><a href="#selection-local" shape="rect">Locally in a document</a>: the selection is
- realized using ITS local attributes, which are attached to an element node, or the<code class="its-elem-markup">span</code> or <code class="its-elem-markup">ruby</code> element. There is no additional <code class="its-attr-markup">selector</code>
+ realized using ITS local attributes, which are attached to an element node, or the <code class="its-elem-markup">span</code> or <code class="its-elem-markup">ruby</code> element. There is no additional <code class="its-attr-markup">selector</code>
attribute. The default selection for each data category defines whether the selection
- covers attributes and child elements. See <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p></li></ul><p>The two locations are described in detail below.</p><div class="div3">
+ covers attributes and child elements. See <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p></li></ul><p>The two locations are described in detail below.</p><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="selection-global" id="selection-global" shape="rect"/>5.2.1 Global, Rule-based Selection</h4><p>Global, rule-based selection is implemented using the <code class="its-elem-markup">rules</code> element. It
contains zero or more <a href="#rule-elements" shape="rect">rule elements</a>. Each <a href="#rule-elements" shape="rect">rule element</a> has a mandatory <code class="its-attr-markup">selector</code>
attribute. This attribute and all other possible attributes on <a href="#rule-elements" shape="rect">rule elements</a> are in the empty namespace and used
@@ -899,12 +873,9 @@
[645 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/27 11:30:11 1.262
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/27 14:53:17 1.263
@@ -815,35 +815,18 @@
<list type="unordered">
<item><code>http://www.w3.org/2001/XMLSchema</code> for the XML Schema namespace, here
used with the prefix “xs”</item>
- <item><code>http://relaxng.org/ns/structure/1.0</code> for the RELAX NG namespace, here
- used with the prefix “rng”</item>
<item><code>http://www.w3.org/1999/xlink</code> for the XLink namespace, here used with
the prefix “xlink”</item>
+ <item><code>http://www.w3.org/1999/xhtml</code> for the HTML namespace, here used with
+ the prefix “h”</item>
</list>
</div>
- <div xml:id="def-schemalanguage">
- <head>Schema Language</head>
- <p>
- <termStruct term="schema" xml:id="t001">
- <term>Schema language</term> refers in this specification to an XML-related modeling
- or validation language such as XML Schema or RELAX NG.</termStruct>
- </p>
-
- <note>
- <p>This specification provides schemas in the format of XML Schema and RELAX NG.
- However, these schemas are only non-normative; <ref
- target="#conformance-product-schema">conformance for ITS markup declarations</ref>
- defines only mandatory positions of ITS declarations in schemas. This makes it
- possible to use ITS with any schema language that allows for using these
- positions.</p>
- </note>
- </div>
<div xml:id="def-datacat">
<head>Data category</head>
<p><termStruct term="data category" xml:id="t002">ITS defines <term>data category</term>
as an abstract concept for a particular type of information for internationalization
and localization of XML schemas and documents.</termStruct> The concept of a data
- category is independent of its implementation in an XML environment (e.g. using an
+ 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>
<list type="unordered">
@@ -874,7 +857,7 @@
<div xml:id="def-selection">
<head>Selection</head>
<p><termStruct xml:id="termdef-selection" term="Selection"><term>selection</term>
- encompasses mechanisms to specify to what parts of an XML document an ITS data
+ encompasses mechanisms to specify to what parts of an XML or HTML document an ITS data
category and its values should be applied to.</termStruct> Selection is discussed in
detail in <ptr type="specref" target="#its-processing"/>. Selection can be applied
globally, see <ptr target="#selection-global" type="specref"/>, and locally, see <ptr
@@ -882,10 +865,6 @@
can be <ref target="#def-adding-pointing">added</ref> to the selected nodes, or it can
<ref target="#def-adding-pointing">point to existing information</ref> which is
related to selected nodes. </p>
- <p xml:id="selection-and-inclusion-mechanisms">Selection relies on the information that is
- given in the XML Information Set <ptr target="#xmlinfoset" type="bibref"/>. ITS
- applications <ref target="#rfc-keywords">MAY</ref> implement inclusion mechanisms such
- as XInclude or DITA's <ptr type="bibref" target="#dita10"/> conref.</p>
<note>
<p xml:id="note-object-selection">The selection of the ITS data categories applies to
textual values contained within element or attribute nodes. In some cases these nodes
@@ -920,18 +899,13 @@
</div>
<div xml:id="iri-usage">
<head>Usage of Internationalized Resource Identifiers in ITS</head>
- <note type="ed">Below list is not up to date.</note>
- <p>The attributes <att>href</att>, <att type="element">locNoteRef</att> and <att
- type="element">termInfoRef</att> which contain resource identifiers <ref
+ <p>All attributes that have the type <code>anyURI</code> in the normative RELAX NG schema in <ptr target="#its-schemas" type="specref"/> <ref
target="#rfc-keywords">MUST</ref> allow the usage of Internationalized Resource
Identifiers (IRIs, <ptr target="#rfc3987" type="bibref"/> or its successor) to ease the
adoption of ITS in international application scenarios.</p>
- <note><p>The ITS schemas in <ptr target="#its-schemas" type="specref"/> are not normative.
- Hence this specification defines no validation requirements for IRI values in ITS
- markup. For processing of these values, relying on IRIs imposes no specific
- requirements. The reason is that the processing happens on the info set level <ptr
- type="bibref" target="#xmlinfoset"/>, where no difference between IRIs and URIs
- exists.</p></note>
+ </div>
+ <div xml:id="def-html"><head>The Term HTML</head>
+ <p>This specification uses the term <code>HTML</code> to refer to HTML5 or its successor <ptr target="#html5" type="bibref"/>.</p>
</div>
</div>
<div xml:id="conformance">
@@ -1013,26 +987,12 @@
<p><emph>Examples: </emph> Examples of the usage of ITS markup declarations in various
existing schemas are given in a separate document <ptr target="#xml-i18n-bp"
type="bibref"/>.</p>
- <note type="ed">Below statement about schemas is wrong if the ITS schemas will be normative.</note>
- <note>
- <p>Since the ITS markup declarations are schema language independent, each schema
- language can use its own, possibly multiple, mechanisms to implement the conformance
- clauses for ITS markup declarations. For example, an XML DTD can use parameter
- entities to encapsulate the <ref target="#local-attributes">ITS local
- attributes</ref>, or declare them directly for each element. The appropriate steps to
- integrate ITS into a schema depend on the design of this schema (e.g. whether it
- already has a customization layer that uses parameter entities). The ITS schemas in
- the format of XML Schema and RELAX NG in <ptr target="#its-schemas" type="specref"/>
- are only informative examples.</p>
- </note>
</div>
<div xml:id="conformance-product-processing-expectations">
<head>Conformance Type 2: The Processing Expectations for ITS Markup</head>
- <note type="ed">All traces of HTML has to be removed if we will proceed with CT 3 and
- HTML+ITS CC.</note>
<p><emph>Description:</emph> Processors need to compute the ITS information that pertains
- to a node in an XML or HTML5 document. The ITS processing expectations define how the
+ to a node in an XML document. The ITS processing expectations define how the
computation has to be carried out. Correct computation involves support for <ref
target="#def-selection">selection mechanism</ref>, <ref
target="#datacategories-defaults-etc">defaults / inheritance / overriding
@@ -1081,20 +1041,15 @@
<item><p xml:id="its-conformance-2-2"><emph>2-2:</emph> If an application claims to
process ITS markup for the global selection mechanism, it <ref
target="#rfc-keywords">MUST</ref> process an XLink <att>href</att> attribute found
- on a <gi>rules</gi> elements. If he application processes HTML5 documents, it <ref
- target="#rfc-keywords">MUST</ref> process an HTML <code>href</code> attribute
- found on an HTML <code>link</code> element. The <code>link</code> element <ref
- target="#rfc-keywords">MUST</ref> also have a <code>rel</code> attribute with the
- value <code>its-rules</code>.</p></item>
+ on a <gi>rules</gi> elements.</p></item>
<item><p xml:id="its-conformance-2-3"><emph>2-3:</emph> If an application claims to
process ITS markup implementing the conformance clauses 2-1, 2-2 and 2-3, it <ref
- target="#rfc-keywords">MUST</ref> process that markup with HTML5 or with XML
+ target="#rfc-keywords">MUST</ref> process that markup with XML
documents.</p></item>
<item><p xml:id="its-conformance-2-4"><emph>2-4:</emph> After processing ITS information
on the basis of conformance clauses <ref target="#its-conformance-2-1">2-1</ref> and
<ref target="#its-conformance-2-2">2-2</ref>, an application <ref
- target="#rfc-keywords">MAY</ref> convert an XML or HTML document (or its DOM
- representation) to NIF, using the algorithm described in <ptr
+ target="#rfc-keywords">MAY</ref> convert an XML document to NIF, using the algorithm described in <ptr
target="#conversion-to-nif" type="specref"/>.</p></item>
</list>
<note><p>The conformance clause <ref target="#its-conformance-2-4">2-4</ref> essentially
@@ -1106,27 +1061,27 @@
<ref target="#rfc-keywords">MUST</ref> list all <ref target="#def-datacat">data
categories</ref> they implement, and for each <ref target="#def-datacat">data
category</ref> which type of selection they support, whether they support processing
- of XML and / or HTML5. If the implementation provides the conversion to NIF (see
+ of XML. If the implementation provides the conversion to NIF (see
conformance clause <ref target="#its-conformance-2-4">2-4</ref>), this <ref
target="#rfc-keywords">MUST</ref> be stated.</p>
<note><p>The above conformance clauses are directly reflected in the <ref
- target="http://phaedrus.scss.tcd.ie/its2.0/its-testsuite.html#">ITS 2.0 test
+ target="https://github.com/finnle/ITS-2.0-Testsuite/">ITS 2.0 test
suite</ref>. All tests specify which data category is processed (clause 2-1); they
are relevant for (clause 2-1-1) global or local selection, or both; they require the
processing of defaults and precedence of selections (clauses 2-1-2 and 2-1-3); for
each data category there are tests with linked rules (2-2); and all types of tests are
- given for XML and HTML5 content (clause 2-3). In addition, there are test cases for
+ given for XML (clause 2-3). In addition, there are test cases for
conversion to NIF (clause 2-4). Implementors are encouraged to organize their
documentation in a similar way, so that users of ITS 2.0 easily can understand the
- processing capabilities availably.</p></note>
+ processing capabilities available.</p></note>
<note type="ed">Need to update link to test suite once the test suite is moved.</note>
</div>
<div xml:id="conformance-product-html-processing-expectations">
<head>Conformance Type 3: Processing Expectations for ITS Markup in HTML</head>
<p><emph>Description:</emph> Processors need to compute the ITS information that pertains
- to a node in a HTML5 document. The ITS processing expectations define how the
+ to a node in a HTML document. The ITS processing expectations define how the
computation has to be carried out. Correct computation involves support for <ref
target="#def-selection">selection mechanism</ref>, <ref
target="#datacategories-defaults-etc">defaults / inheritance / overriding
@@ -1208,6 +1163,9 @@
<emph>This section is normative.</emph>
</p>
+<note><p>Additional definitions about processing of HTML are given in <ptr type="specref" target="#html5-markup"/>.</p></note>
+
+
<div xml:id="its-version-attribute">
<head>Indicating the Version of ITS</head>
<p>The version of the ITS schema defined in this specification is <val>2.0</val>. The
@@ -1232,8 +1190,7 @@
attribute and possibly other attributes. The <att>selector</att> attribute contains an
absolute selector as defined in <ptr target="#selectors" type="specref"/>.</item>
<item><ref target="#selection-local">Locally in a document</ref>: the selection is
- realized using ITS local attributes, which are attached to an element node, or the
- <gi>span</gi> or <gi>ruby</gi> element. There is no additional <att>selector</att>
+ realized using ITS local attributes, which are attached to an element node, or the <gi>span</gi> or <gi>ruby</gi> element. There is no additional <att>selector</att>
attribute. The default selection for each data category defines whether the selection
covers attributes and child elements. See <ptr target="#datacategories-defaults-etc"
type="specref"/>.</item>
@@ -1280,12 +1237,9 @@
<div xml:id="selection-local">
<head>Local Selection in an XML Document</head>
<p>Local selection in XML documents is realized with <ref target="#local-attributes">ITS
- local attributes</ref>, the <gi>ruby</gi> element, or the <gi>span</gi> element.
- <gi>span</gi> serves just as a carrier for the local ITS attributes and a container
- for <gi>ruby</gi>.</p>
- <p>The content model of <gi>span</gi> permits arbitrary nesting of ruby markup, since
- the <gi>rt</gi> element can contain <gi>span</gi>. An application of ruby, however,
- <ref target="#rfc-keywords">MUST</ref> not use such arbitrary nesting.</p>
+ local attributes</ref> or the <gi>span</gi> element.
+ <gi>span</gi> serves just as a carrier for the local ITS attributes.</p>
+
<p>The data category determines what is being selected. The necessary data category
specific defaults are described in <ptr target="#datacategories-defaults-etc"
type="specref"/>.</p>
@@ -1392,8 +1346,9 @@
>AbsoluteLocationPath</ref> as described in <ref target="#xpath">XPath 1.0</ref>.
The XPath expression is evaluated relative to the nodes selected by the selector
attribute.</p>
+ <note type="ed">Need to update below list depending on outcome of quality precis discussions.</note>
<p xml:id="pointer-attributes-list">The following attributes point to existing information:
- <att>allowedCharactersPointer</att>, <att>disambigClassPointer</att>, <att>disambigClassRefPointer</att>, <att>disambigIdentPointer</att>, <att>disambigIdentRefPointer</att>, <att>domainPointer</att>, <att>externalResourceRefPointer</att>, <att>langPointer</att>, <att>locNotePointer</att>, <att>locNoteRefPointer</att>, <att>locQualityIssuesRefPointer</att>, <att>locQualityPrecisProfileRefPointer</att>, <att>locQualityPrecisScorePointer</att>, <att>locQualityPrecisThresholdPointer</att>, <att>locQualityPrecisVotePointer</att>, <att>orgPointer</att>, <att>orgRefPointer</att>, <att>personPointer</att>, <att>personRefPointer</att>, <att>provRefPointer</att>, <att>provenanceRecordsRefPointer</att>, <att>revOrgPointer</att>, <att>revOrgRefPointer</att>, <att>revPersonPointer</att>, <att>revPersonRefPointer</att>, <att>revToolPointer</att>, <att>revToolRefPointer</att>, <att>rpPointer</att>, <att>rtPointer</att>, <att>rubyPointer</att>, <att>storageEncodingPointer</att>, <att>storageSizePointer<att>, <att>targetPointer</att>, <att>termInfoPointer</att>, <att>termInfoRefPointer</att>, <att>toolPointer</att>, <att>toolRefPointer</att>.</p>
+ <att>allowedCharactersPointer</att>, <att>disambigClassPointer</att>, <att>disambigClassRefPointer</att>, <att>disambigIdentPointer</att>, <att>disambigIdentRefPointer</att>, <att>domainPointer</att>, <att>externalResourceRefPointer</att>, <att>langPointer</att>, <att>locNotePointer</att>, <att>locNoteRefPointer</att>, <att>locQualityIssuesRefPointer</att>, <att>locQualityPrecisProfileRefPointer</att>, <att>locQualityPrecisScorePointer</att>, <att>locQualityPrecisThresholdPointer</att>, <att>locQualityPrecisVotePointer</att>, <att>provenanceRecordsRefPointer</att>, <att>storageEncodingPointer</att>, <att>storageSizePointer</att>, <att>targetPointer</att>, <att>termInfoPointer</att>, <att>termInfoRefPointer</att>.</p>
<p>Context for evaluation of the XPath expression is same as for absolute selector
with the following changes:</p>
<list>
@@ -1531,7 +1486,7 @@
<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>
<list type="ordered">
- <item xml:id="precedence-local">Implicit local selection in documents (<ref
+ <item xml:id="precedence-local">Selection via explicit (that is, not inherited) local ITS markup in documents (<ref
target="#local-attributes">ITS local attributes</ref> on a specific element)</item>
<item xml:id="precedence-global-in-doc"><p>Global selections in documents (using a
<gi>rules</gi> element)</p>
@@ -1556,7 +1511,7 @@
target="#xslt10" type="bibref"/>. 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
- selected via global rules, and these are overriden via local markup.</p>
+ selected via global rules, which are in turn overridden by local markup.</p>
</note>
<exemplum xml:id="EX-selection-precedence-1">
<head>Conflicts between selections of ITS information which are resolved using the
@@ -1628,12 +1583,10 @@
</div>
<div xml:id="conversion-to-nif">
<head>Conversion to NIF</head>
+ <note type="ed">This will also need to be marked as feature at risk, only one implementation so far</note>
<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 <ref
- target="http://nlp2rdf.org/nif-1-0">NIF</ref>. The conversion results in RDF triples
- that rely on the ITS 2.0 ontology, see tbd.</p>
- <note type="ed">Add link to ontology once it is done; assure that the examples use the
- correct base URIs for the ontology.</note>
+ target="http://nlp2rdf.org/nif-1-0">NIF</ref>. The conversion results in RDF triples.</p>
<note><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP
tool and can produce a lot of <quote>phantom</quote> predicates from excessive
whitespace, which 1) increases the size of the intermediate mapping and 2) extracts
@@ -1715,13 +1668,11 @@
<mapping x="xpath(/html/body[1]/h2[1]/text()[3])" b="28" e="29" />
<mapping x="xpath(/html/body[1]/h2[1])" b="0" e="29" />
</mappings>]]></eg>
- <note type="ed">Below needs a reference to the ITS ontology, once available.</note>
<list type="unordered">
<item><p xml:id="its2nif-algorithm-step5">STEP 5: Create a context URI and attach the
whole concatenated text of the document as reference.</p></item>
<item><p xml:id="its2nif-algorithm-step6">STEP 6: Now attach any ITS metadata items from
- the XML/HTML/DOM input to respective NIF URIs using the ITS/RDF ontology (TODO
- Name).</p></item>
+ the XML/HTML/DOM input to respective NIF URIs.</p></item>
<item><p xml:id="its2nif-algorithm-step7">STEP 7: Omit all irrelevant URIs (those that
do not carry annotations, they will just bloat the data).</p></item>
</list>
@@ -1799,6 +1750,102 @@
</exemplum>
</div>
</div>
+ <div xml:id="html5-markup">
+ <head>Using ITS Markup in HTML5</head>
+
+ <div xml:id="html5-local-attributes">
+ <head>Mapping of Local Data Categories to HTML5</head>
+ <p>All data categories defined in <ptr target="#datacategory-description" type="specref"/>
+ and having local implementation might be used in HTML with the exception of <ref
+ target="#trans-datacat" type="specref">Translate</ref>, <ref target="#directionality"
+ type="specref">Directionality</ref>, <ref target="#ruby-annotation" type="specref"
+ >Ruby</ref>, and <ref target="#language-information" type="specref">Language
+ Information</ref> data categories.</p>
+ <note>
+ <p>The above mentioned data categories are excluded because HTML has native markup for
+ them.</p>
+ </note>
+ <p>In HTML data categories are implemented as attributes. Name of HTML attribute is
+ derived from the name of attribute defined in the local implementation by using the
+ following rules:<list type="ordered">
+ <item>Attribute name is prefixed with <code>its-</code></item>
+ <item>Each uppercase letter in the attribute name is replaced by <code>-</code>
+ (U+002D) followed by a lowercase variant of the letter.</item>
+ </list></p>
+ <p>Values of attributes which corresponds to data categories with a predefined set of
+ values MUST be matched case-insensitively. </p>
+ <note><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in
+ HTML terminology data category can be stored as <att>its-term</att>,
+ <code>ITS-TERM</code>, <code>its-Term</code> etc. All those attributes are treated as
+ equivalent and will gets normalized upon DOM construction.</p></note>
+ </div>
+
+ <div xml:id="html5-external-global-rules">
+ <head>External Rules</head>
+ <p>Link to external global rules is specified in <att>href</att> attribute of
+ <code>link</code> element, with the link relation <code>its-rules</code>.</p>
+ <note>
+ <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 <att>queryLanguage</att> attribute, see <ptr target="#queryLanguage"
+ type="specref"/>.</p>
+ </note>
+ <note>
+ <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
+ take this into account.</p>
+ </note>
+ <note>
+ <p>Using XPath in global rules linked from HTML5 documents does not create an additional
+ burden to implementers. Parsing HTML5 content produces a DOM tree that can be directly
+ queried using XPath, functionality supported by all major browsers.</p>
+ </note>
+ </div>
+
+ <div xml:id="html5-inline-global-rules">
+ <head>Inline Global Rules in HTML5</head>
+ <p>Inline global rules MUST be specified inside <code>script</code> which has <code>type</code>
+ attribute with the value <code>application/xml</code> or
+ <code>application/its+xml</code>. The <code>script</code> element itself MUST be child of
+ <code>head</code> element. Comments MUST NOT be used inside global rules. Each
+ <code>script</code> element MUST NOT contain more then one <gi>rules</gi> element.</p>
+ <note><p>It is preferred to use external global rules linked using <code>link</code>
+ element.</p></note>
+ </div>
+ <div xml:id="html5-standoff-markup"><head>Standoff Markup in HTML5</head>
+ <p>The constraints for <ref target="#provenance-records-in-html5-constraint">Provenance standoff markup in HTML5</ref> and <ref target="#loc-quality-issues-in-html5-constraint">Localization quality issues markup in HTML5</ref> <ref target="#rfc2119">MUST</ref> be followed.</p>
+ </div>
+ <div xml:id="html5-selection-precedence">
+ <head>Precedence between Selections</head>
+ <p>The following precedence order is defined for selections of ITS information in various
+ positions of HTML document (the first item in the list has the highest precedence):</p>
+ <list type="ordered">
+ <item>Implicit local selection in documents (<ref target="#html5-local-attributes">ITS
+ local attributes</ref> on a specific element)</item>
+ <item><p>Global selections in documents (using mechanism described in <ptr
+ target="#html5-external-global-rules" type="specref"/> or <ptr
+ target="#html5-inline-global-rules" type="specref"/>)</p>
+ <note><p>If identical selections are defined in different rules elements within one
+ document, the selection defined by the last takes precedence.</p></note>
+ </item>
+ <item>Selections via defaults for data categories, see <ptr
+ target="#datacategories-defaults-etc" type="specref"/></item>
+ </list>
+ <p>In case of conflicts between global selections via multiple <ref
+ target="#selection-global">rules</ref> elements, the last rule has higher
+ precedence.</p>
+ </div>
+ </div>
+
+ <div xml:id="xhtml5-markup">
+ <head>Using ITS Markup in XHTML</head>
+ <p>XHTML documents aimed at public consumption by Web browsers SHOULD use syntax for local
+ attributes described in <ptr target="#html5-local-attributes" type="specref"/> and SHOULD
+ NOT use <ref target="#html5-inline-global-rules">inline global rules</ref> in order to
+ adhere to <ref target="http://www.w3.org/TR/html-design-principles/#dom-consistency">DOM
+ Consistency HTML Design Principle</ref>.</p>
+ </div>
+
<div xml:id="datacategory-description">
<head>Description of Data Categories</head>
<p>
@@ -4477,101 +4524,6 @@
</div>
-->
- <div xml:id="html5-markup">
- <head>Using ITS Markup in HTML5</head>
-
- <div xml:id="html5-local-attributes">
- <head>Mapping of Local Data Categories to HTML5</head>
- <p>All data categories defined in <ptr target="#datacategory-description" type="specref"/>
- and having local implementation might be used in HTML with the exception of <ref
- target="#trans-datacat" type="specref">Translate</ref>, <ref target="#directionality"
- type="specref">Directionality</ref>, <ref target="#ruby-annotation" type="specref"
- >Ruby</ref>, and <ref target="#language-information" type="specref">Language
- Information</ref> data categories.</p>
- <note>
- <p>The above mentioned data categories are excluded because HTML has native markup for
- them.</p>
- </note>
- <p>In HTML data categories are implemented as attributes. Name of HTML attribute is
- derived from the name of attribute defined in the local implementation by using the
- following rules:<list type="ordered">
- <item>Attribute name is prefixed with <code>its-</code></item>
- <item>Each uppercase letter in the attribute name is replaced by <code>-</code>
- (U+002D) followed by a lowercase variant of the letter.</item>
- </list></p>
- <p>Values of attributes which corresponds to data categories with a predefined set of
- values MUST be matched case-insensitively. </p>
- <note><p>Case of attribute names is also irrelevant given the nature of HTML syntax. So in
- HTML terminology data category can be stored as <att>its-term</att>,
- <code>ITS-TERM</code>, <code>its-Term</code> etc. All those attributes are treated as
- equivalent and will gets normalized upon DOM construction.</p></note>
- </div>
[78 lines skipped]
Received on Tuesday, 27 November 2012 14:53:30 UTC