- From: Jirka Kozek via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 17 Oct 2012 16:31:17 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory hutz:/tmp/cvs-serv21323
Modified Files:
its20.html its20.odd
Log Message:
Removed section about ODD as we do not longer use ODD schema related features
Index: its20.odd
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd,v
retrieving revision 1.189
retrieving revision 1.190
diff -u -d -r1.189 -r1.190
--- its20.odd 17 Oct 2012 15:59:31 -0000 1.189
+++ its20.odd 17 Oct 2012 16:31:15 -0000 1.190
@@ -446,6 +446,7 @@
content should not be translated.</p>
</item>
</list>
+ <note type="ed">Following schema example has to updated once we have final XSD schema for ITS 2.0</note>
<exemplum>
<head>An XSD schema with ITS declaration</head>
<p>The declarations for the <att type="class">translate</att> attribute
@@ -470,6 +471,7 @@
<p>ITS 2.0 adds support for usage in HTML5. In HTML5, ITS local selection is
realized via dedicated, <ref target="#html5-local-attributes">data category
specific attributes</ref>.</p>
+ <note type="ed">Add example of HTML5 with local attributes for illustartion purposes</note>
<p>For the so-called “<ref target="#basic-concepts-selection-global">global
approach</ref>” in HTML5, this specification defines a link type for
referring to files with global rules in <ptr target="#html5-external-global-rules" type="specref"/>.</p>
@@ -583,28 +585,7 @@
target="#xpath" type="bibref"/> for the selection mechanism).</item>
</list>
</div>
- <div xml:id="spec-development">
- <head>Development of this Specification</head>
- <p>This specification has been developed using the ODD (<emph>One Document Does
- it all</emph>) language of the Text Encoding Initiative (<ptr
- target="#tei" type="bibref"/>). This is a literate programming language
- for writing XML schemas, with three characteristics:</p>
- <list type="ordered">
- <item>The element and attribute set is specified using an XML vocabulary
- which includes support for macros (like DTD entities, or schema
- patterns), a hierarchical class system for attributes and elements, and
- creation of modules.</item>
- <item>The content models for elements and attributes are written using
- embedded RELAX NG XML notation.</item>
- <item>Documentation for elements, attributes, value lists etc. is written
- inline, along with examples and other supporting material.</item>
- </list>
- <p>XSLT transformations are provided by the TEI to create documentation into
- HTML, XSL FO or LaTeX forms, and to generate RELAX NG documents and DTD.
- From the RELAX NG documents, James Clark's <ref
- target="http://www.thaiopensource.com/relaxng/trang.html">trang</ref>
- can be used to create XML Schema documents.</p>
- </div>
+
</div>
<div xml:id="basic-concepts">
<head>Basic Concepts</head>
Index: its20.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html,v
retrieving revision 1.191
retrieving revision 1.192
diff -u -d -r1.191 -r1.192
--- its20.html 16 Oct 2012 23:07:51 -0000 1.191
+++ its20.html 17 Oct 2012 16:31:14 -0000 1.192
@@ -28,7 +28,6 @@
</div>
<div class="toc2">1.5 <a href="#out-of-scope" shape="rect">Out of Scope</a></div>
<div class="toc2">1.6 <a href="#design-decisions" shape="rect">Important Design Principles</a></div>
-<div class="toc2">1.7 <a href="#spec-development" shape="rect">Development of this Specification</a></div>
</div>
<div class="toc1">2 <a href="#basic-concepts" shape="rect">Basic Concepts</a><div class="toc2">2.1 <a href="#basic-concepts-selection" shape="rect">Selection</a><div class="toc3">2.1.1 <a href="#basic-concepts-selection-local" shape="rect">Local Approach</a></div>
<div class="toc3">2.1.2 <a href="#basic-concepts-selection-global" shape="rect">Global Approach</a></div>
@@ -54,9 +53,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="#d3e2154" shape="rect">XPath 1.0</a></div>
-<div class="toc3">5.3.3 <a href="#d3e2334" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d3e2370" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.2 <a href="#d3e2132" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.3 <a href="#d3e2312" shape="rect">CSS Selectors</a></div>
+<div class="toc3">5.3.4 <a href="#d3e2348" 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>
@@ -152,8 +151,8 @@
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 HTML5, serializations in <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF</a>, and the schema languages XML
- DTD <a title="Extensible
								Markup Language (XML) 1.0 (Fourth Edition)" href="#xml10spec" shape="rect">[XML 1.0]</a>, XML Schema <a title="XML
								Schema Part 1: Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based
							validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.</p><p>This document aims to realize many of the ideas formulated in the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/" shape="rect">ITS 2.0 Requirements
+ document provides implementations for HTML5, serializations in <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF</a>, and provides definitions
+ of ITS elements and attributes in the form of XML Schema <a title="XML
								Schema Part 1: Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based
							validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.</p><p>This document aims to realize many of the ideas formulated in the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/" shape="rect">ITS 2.0 Requirements
document</a>, in <a title="Internationalization and Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a> and <a title="Requirements for Localizable DTD Design" href="#reqlocdtd" shape="rect">[Localizable DTDs]</a>.</p><p>Not all requirements listed there are addressed in this document. Those which are
not addressed here are either covered in <a title="Best
								Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a> (potentially in an as yet unwritten best practice
document on multilingual Web content), or may be addressed in a future version
@@ -204,7 +203,7 @@
efficient XML-related localization: the lack of a standard, declarative
mechanism that identifies which parts of an XML document need to be
translated. Tools often cannot automatically perform this
- identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e323" id="d3e323" shape="rect"/>Example 1: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those
+ identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e321" id="d3e321" shape="rect"/>Example 1: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those
<code>string</code> elements that are translatable and those that
are not. Only the addition of an explicit flag could resolve the
issue.</p><div class="exampleInner"><pre xml:space="preserve">
@@ -229,7 +228,7 @@
<string>List of Available Policies</string>
</keyvalue_pairs>
</section>
-</resources></pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml" shape="rect">examples/xml/EX-motivation-its-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e338" id="d3e338" shape="rect"/>Example 2: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text,
+</resources></pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml" shape="rect">examples/xml/EX-motivation-its-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e336" id="d3e336" shape="rect"/>Example 2: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text,
the conditions may be quite complex and not directly indicated with
a simple flag. Here, for instance, only the text in the nodes
matching the expression
@@ -293,7 +292,7 @@
standardizing the format and processing expectations of certain
relevant markup items, and allowing them to more effectively
identify how content should be handled.</p></div><div class="div4">
-<h5><a name="d3e396" id="d3e396" shape="rect"/>1.3.1.4Content producers</h5><p>This type of user comprises authors, translators and other types of
+<h5><a name="d3e394" id="d3e394" shape="rect"/>1.3.1.4Content producers</h5><p>This type of user comprises authors, translators and other types of
content author. The markup proposed in this specification may be
used by them to mark up specific bits of content. Aside: The burden
of inserting markup can be removed from content producers by
@@ -328,7 +327,7 @@
</body>
</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-1.xml" shape="rect">examples/xml/EX-ways-to-use-its-1.xml</a>]</p></div><ul><li><p>A content author or information architect uses markup at the top
of the document to identify a particular type of element or
- context in which the content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e448" id="d3e448" shape="rect"/>Example 4: Use of ITS by information architect</div><p>The <code>translateRule</code> element is used in the header of the
+ context in which the content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e446" id="d3e446" shape="rect"/>Example 4: Use of ITS by information architect</div><p>The <code>translateRule</code> element is used in the header of the
document to indicate that none of the <code>path</code> or <code>cmd</code>
elements should be translated.</p><div class="exampleInner"><pre xml:space="preserve">
<help
@@ -346,7 +345,7 @@
Then from there, run batch file <cmd>Build.bat</cmd>.</p>
</body>
</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-2.xml" shape="rect">examples/xml/EX-ways-to-use-its-2.xml</a>]</p></div><ul><li><p>A processor may insert markup at the top of the document which
- links to ITS information outside of the document.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e473" id="d3e473" shape="rect"/>Example 5: Use of ITS by processor</div><p>A <code>rules</code> element is inserted in the header of the document.
+ links to ITS information outside of the document.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e471" id="d3e471" shape="rect"/>Example 5: Use of ITS by processor</div><p>A <code>rules</code> element is inserted in the header of the document.
It has a XLink <code>href</code> attribute used to link to an <a href="#link-external-rules" shape="rect">ITS external rule</a>
document.</p><div class="exampleInner"><pre xml:space="preserve">
<help
@@ -362,7 +361,7 @@
<path>\Zebulon\Current Source\binary</path> directory.
Then from there, run batch file <cmd>Build.bat</cmd>.</p>
</body>
-</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml" shape="rect">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e494" id="d3e494" shape="rect"/>Example 6: ITS rule file shared by different documents</div><p>The <code>rules</code> element contains several ITS rules that are common
+</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml" shape="rect">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e492" id="d3e492" shape="rect"/>Example 6: ITS rule file shared by different documents</div><p>The <code>rules</code> element contains several ITS rules that are common
to different documents. One of them is a <code>translateRule</code>
element that indicates that no <code>path</code> or <code>cmd</code> element
should be translated.</p><div class="exampleInner"><pre xml:space="preserve">
@@ -371,7 +370,7 @@
<its:translateRule selector="//path | //cmd" translate="no"/>
</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-4.xml" shape="rect">examples/xml/EX-ways-to-use-its-4.xml</a>]</p></div><ul><li><p>A schema developer integrates ITS markup declarations in his
schema to allow users to indicate that specific parts of the
- content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e522" id="d3e522" shape="rect"/>Example 7: An XSD schema with ITS declaration</div><p>The declarations for the <code>translate</code> attribute
+ content should not be translated.</p></li></ul><span class="editor-note">[Ed. note: Following schema example has to updated once we have final XSD schema for ITS 2.0]</span><div class="exampleOuter"><div class="exampleHeader"><a name="d3e524" id="d3e524" shape="rect"/>Example 7: An XSD schema with ITS declaration</div><p>The declarations for the <code>translate</code> attribute
is added to a group of common attributes <code>commonAtts</code>.
This allows to use the <code>translate</code> attribute
within the documents like in <a href="#EX-ways-to-use-its-1" shape="rect">Example 3</a>.</p><div class="exampleInner"><pre xml:space="preserve">
@@ -430,7 +429,7 @@
or in a particular context would be colored red.</p></div></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="usage-in-html5" id="usage-in-html5" shape="rect"/>1.4 Usage in HTML5</h3><p>ITS 2.0 adds support for usage in HTML5. In HTML5, ITS local selection is
realized via dedicated, <a href="#html5-local-attributes" shape="rect">data category
- specific attributes</a>.</p><p>For the so-called “<a href="#basic-concepts-selection-global" shape="rect">global
+ specific 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
<code>EX-translateRule-html5-1.xml</code> The <code>rel</code>
@@ -504,18 +503,7 @@
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
- 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).</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="spec-development" id="spec-development" shape="rect"/>1.7 Development of this Specification</h3><p>This specification has been developed using the ODD (<em>One Document Does
- it all</em>) language of the Text Encoding Initiative (<a title="Text Encoding
								Initiative Guidelines development version (P5)" href="#tei" shape="rect">[TEI]</a>). This is a literate programming language
- for writing XML schemas, with three characteristics:</p><ol class="depth1"><li><p>The element and attribute set is specified using an XML vocabulary
- which includes support for macros (like DTD entities, or schema
- patterns), a hierarchical class system for attributes and elements, and
- creation of modules.</p></li><li><p>The content models for elements and attributes are written using
- embedded RELAX NG XML notation.</p></li><li><p>Documentation for elements, attributes, value lists etc. is written
- inline, along with examples and other supporting material.</p></li></ol><p>XSLT transformations are provided by the TEI to create documentation into
- HTML, XSL FO or LaTeX forms, and to generate RELAX NG documents and DTD.
- From the RELAX NG documents, James Clark's <a href="http://www.thaiopensource.com/relaxng/trang.html" shape="rect">trang</a>
- can be used to create XML Schema documents.</p></div></div><div class="div1">
+ 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).</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>
<em>This section is informative.</em>
</p><div class="div2">
@@ -705,7 +693,7 @@
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 "markup
- declarations" 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 D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1180" id="d3e1180" shape="rect"/>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys
+ declarations" 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 D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1158" id="d3e1158" 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>translate</code> attribute with
@@ -734,7 +722,7 @@
points. Thus in the following example, the translation information
specified via the <code>translateRule</code> element applies to the filename
"instructions.jpg", and is not an instruction to open the
- graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1263" id="d3e1263" shape="rect"/>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre xml:space="preserve">
+ graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1241" id="d3e1241" shape="rect"/>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1025,9 +1013,9 @@
by <code>queryLanguage</code> attribute on <code>rules</code> element. If
<code>queryLanguge</code> is not specified XPath 1.0 is used as a
default query language.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2154" id="d3e2154" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in
+<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="d3e2132" id="d3e2132" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in
<code>queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d3e2165" id="d3e2165" shape="rect"/>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an
+<h5><a name="d3e2143" id="d3e2143" shape="rect"/>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an
XPath expression which starts with "<code>/</code>". That is, it
must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
@@ -1042,7 +1030,7 @@
occurs. This includes the implicit declaration of the prefix
<code>xml</code> required by the the <a href="#xmlns" shape="rect">XML Namespaces Recommendation</a>; the
default namespace (as declared by <code>xmlns</code>) is not
- part of this set.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2225" id="d3e2225" shape="rect"/>Example 16: XPath expressions with namespaces</div><p>The <code>term</code> element from the TEI is in a namespace
+ part of this set.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2203" id="d3e2203" shape="rect"/>Example 16: XPath expressions with namespaces</div><p>The <code>term</code> element from the TEI is in a namespace
<code>http://www.tei-c.org/ns/1.0</code>. </p><div class="exampleInner"><pre xml:space="preserve">
<!-- Definitions for TEI -->
@@ -1050,7 +1038,7 @@
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:tei="http://www.tei-c.org/ns/1.0" version="2.0">
<its:termRule selector="//tei:term" term="yes"/>
-</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml" shape="rect">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2243" id="d3e2243" shape="rect"/>Example 17: XPath expressions without namespaces</div><p>The <code>term</code> element from DocBook V4.5 is in no
+</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml" shape="rect">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2221" id="d3e2221" shape="rect"/>Example 17: XPath expressions without namespaces</div><p>The <code>term</code> element from DocBook V4.5 is in no
namespace.</p><div class="exampleInner"><pre xml:space="preserve">
<!-- Definitions for DocBook -->
@@ -1058,7 +1046,7 @@
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
<its:termRule selector="//term" term="yes"/>
</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-2.xml" shape="rect">examples/xml/EX-selection-global-2.xml</a>]</p></div></div><div class="div4">
-<h5><a name="d3e2258" id="d3e2258" shape="rect"/>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords" shape="rect">MUST</a> use a
+<h5><a name="d3e2236" id="d3e2236" shape="rect"/>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords" shape="rect">MUST</a> use a
<a href="http://www.w3.org/TR/xpath/#NT-RelativeLocationPath" shape="rect">RelativeLocationPath</a> as described in <a href="#xpath" shape="rect">XPath 1.0</a>. The XPath expression is evaluated relative to
the nodes selected by the selector attribute. The following
attributes point to existing information: <code>locNotePointer</code>,
@@ -1075,16 +1063,16 @@
attribute form the current node list.</p></li><li><p>Context node comes from the current node list.</p></li><li><p>The context position comes from the position of the current
node in the current node list; the first position is 1.</p></li><li><p>The context size comes from the size of the current node
list.</p></li></ul></div></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2334" id="d3e2334" shape="rect"/>5.3.3 CSS Selectors</h4><p>CSS Selectors are identified by <code>css</code> value in
+<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="d3e2312" id="d3e2312" shape="rect"/>5.3.3 CSS Selectors</h4><p>CSS Selectors are identified by <code>css</code> value in
<code>queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d3e2345" id="d3e2345" shape="rect"/>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be
+<h5><a name="d3e2323" id="d3e2323" shape="rect"/>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be
interpreted as selector as defined in <a href="#css3-selectors" shape="rect">Selectors Level 3</a>. Both simple selectors and groups of
selectors can be used.</p></div><div class="div4">
-<h5><a name="d3e2356" id="d3e2356" shape="rect"/>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be
+<h5><a name="d3e2334" id="d3e2334" shape="rect"/>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be
interpreted as selector as defined in <a href="#css3-selectors" shape="rect">Selectors Level 3</a>. Selector is not evaluated against the
complete document tree but only against subtrees rooted at nodes
selected by selector in the <code>selector</code> attribute.</p></div></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2370" id="d3e2370" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional
+<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="d3e2348" id="d3e2348" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional
query languages. For each additional query language processor <a href="#rfc-keywords" shape="rect">MUST</a> define:</p><ul><li><p>identifier of query language used in
<code>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
@@ -1144,7 +1132,7 @@
<its:termRule selector="//term" term="yes"/>
<its:withinTextRule withinText="yes" selector="//term | //b"/>
</its:rules>
-</myFormatInfo></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-1.xml" shape="rect">examples/xml/EX-link-external-rules-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2537" id="d3e2537" shape="rect"/>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre xml:space="preserve">
+</myFormatInfo></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-1.xml" shape="rect">examples/xml/EX-link-external-rules-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2515" id="d3e2515" shape="rect"/>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre xml:space="preserve">
<myDoc
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xlink="http://www.w3.org/1999/xlink" >
@@ -1159,7 +1147,7 @@
<p>A <term>Palouse horse</term> has a spotted coat.</p>
</body>
</myDoc></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-2.xml" shape="rect">examples/xml/EX-link-external-rules-2.xml</a>]</p></div><p>The result of processing the two documents above is the same as processing
- the following document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2549" id="d3e2549" shape="rect"/>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre xml:space="preserve">
+ the following document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2527" id="d3e2527" shape="rect"/>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre xml:space="preserve">
<myDoc
xmlns:its="http://www.w3.org/2005/11/its" >
<header>
@@ -1198,7 +1186,7 @@
higher precedence.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The precedence order fulfills the same purpose as the built-in template
rules of <a title="XSL
								Transformations (XSLT) Version 1.0" href="#xslt10" shape="rect">[XSLT 1.0]</a>. Override semantics are
always complete, that is all information that is specified in one rule
- element is overridden by the next one.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2636" id="d3e2636" shape="rect"/>Example 22: Conflicts between selections of ITS information which are resolved
+ element is overridden by the next one.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2614" id="d3e2614" shape="rect"/>Example 22: Conflicts between selections of ITS information which are resolved
using the precedence order</div><p>The two elements <code>title</code> and <code>author</code> of this document
should be treated as separate content when inside a <code>prolog</code>
element, but as part of the content of their parent element otherwise.
@@ -1493,7 +1481,7 @@
<a href="#storagesize" shape="rect">Storage Size</a>
</td><td rowspan="1" colspan="1">Yes</td><td rowspan="1" colspan="1">Yes</td><td rowspan="1" colspan="1">Yes</td><td rowspan="1" colspan="1">Yes</td><td rowspan="1" colspan="1">
<code>its:storageEncoding="UTF-8"</code>
- </td><td rowspan="1" colspan="1">None</td><td rowspan="1" colspan="1">tbd</td><td rowspan="1" colspan="1">tbd</td></tr></tbody></table><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3573" id="d3e3573" shape="rect"/>Example 25: Defaults, inheritance and overriding behavior of data
+ </td><td rowspan="1" colspan="1">None</td><td rowspan="1" colspan="1">tbd</td><td rowspan="1" colspan="1">tbd</td></tr></tbody></table><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3551" id="d3e3551" shape="rect"/>Example 25: Defaults, inheritance and overriding behavior of data
categories</div><p>In this example, the content of all the <code>data</code> elements is
translatable because the default for the <a href="#trans-datacat" shape="rect">Translate</a> data category in elements is "yes". The
content of <code>revision</code> and <code>locNote</code> is not translatable
@@ -1671,7 +1659,7 @@
<body>
<msg id="NotFound">Cannot find {0} on {1}.</msg>
</body>
-</myRes></pre></div><p>[Source file: <a href="examples/xml/EX-locNoteRef-attribute-1.xml" shape="rect">examples/xml/EX-locNoteRef-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3971" id="d3e3971" shape="rect"/>Example 32: The <code>locNoteRefPointer</code> attribute</div><p>The <code>locNoteRefPointer</code> attribute contains a <a href="#selectors" shape="rect">relative selector</a> pointing to a node
+</myRes></pre></div><p>[Source file: <a href="examples/xml/EX-locNoteRef-attribute-1.xml" shape="rect">examples/xml/EX-locNoteRef-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3949" id="d3e3949" shape="rect"/>Example 32: The <code>locNoteRefPointer</code> attribute</div><p>The <code>locNoteRefPointer</code> attribute contains a <a href="#selectors" shape="rect">relative selector</a> pointing to a node
that holds the URI referring to the location of the note.</p><div class="exampleInner"><pre xml:space="preserve">
<dataFile
xmlns:its="http://www.w3.org/2005/11/its" >
@@ -1695,7 +1683,7 @@
contains a URI referring to the location of the localization
note.</p></li></ul></li><li><p>An optional <code>locNoteType</code> attribute with the
value "description" or "alert". If the <code>locNoteType</code> attribute is not present, the
- type of localization note will be assumed to be"description". </p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4032" id="d3e4032" shape="rect"/>Example 33: The <a href="#locNote-datacat" shape="rect">Localization Note</a> data
+ type of localization note will be assumed to be"description". </p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4010" id="d3e4010" shape="rect"/>Example 33: The <a href="#locNote-datacat" shape="rect">Localization Note</a> data
category expressed locally</div><div class="exampleInner"><pre xml:space="preserve">
<msgList
xmlns:its="http://www.w3.org/2005/11/its" xml:space="preserve"
@@ -1709,7 +1697,7 @@
its:locNote="%1\$s is the original text's date in the format YYYY-MM-DD HH:MM always in GMT">
<value>Translated from English content dated <span id="version-info">%1\$s</span> GMT.</value>
</data>
-</msgList></pre></div><p>[Source file: <a href="examples/xml/EX-locNote-selector-2.xml" shape="rect">examples/xml/EX-locNote-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4046" id="d3e4046" shape="rect"/>Example 34: The <a href="#locNote-datacat" shape="rect">Localization Note</a> data
+</msgList></pre></div><p>[Source file: <a href="examples/xml/EX-locNote-selector-2.xml" shape="rect">examples/xml/EX-locNote-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4024" id="d3e4024" shape="rect"/>Example 34: The <a href="#locNote-datacat" shape="rect">Localization Note</a> data
category expressed locally in HTML5</div><div class="exampleInner"><pre xml:space="preserve"><!DOCTYPE html>
<html lang=en>
<head>
@@ -1745,7 +1733,7 @@
term.</p></li><li><p>A <code>termInfoRefPointer</code> attribute that contains a
<a href="#selectors" shape="rect">relative selector</a>
pointing to a node that holds the URI referring to the
- location of the terminology information.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4144" id="d3e4144" shape="rect"/>Example 35: Usage of the <code>termInfoPointer</code> attribute</div><div class="exampleInner"><pre xml:space="preserve">
+ location of the terminology information.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4122" id="d3e4122" shape="rect"/>Example 35: Usage of the <code>termInfoPointer</code> attribute</div><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1756,7 +1744,7 @@
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-1.xml" shape="rect">examples/xml/EX-terms-selector-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4157" id="d3e4157" shape="rect"/>Example 36: Usage of the <code>termInfoRef</code> attribute</div><div class="exampleInner"><pre xml:space="preserve">
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-1.xml" shape="rect">examples/xml/EX-terms-selector-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4135" id="d3e4135" shape="rect"/>Example 36: Usage of the <code>termInfoRef</code> attribute</div><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1767,7 +1755,7 @@
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-2.xml" shape="rect">examples/xml/EX-terms-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4170" id="d3e4170" shape="rect"/>Example 37: Usage of the <code>termInfoRefPointer</code> attribute</div><div class="exampleInner"><pre xml:space="preserve">
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-2.xml" shape="rect">examples/xml/EX-terms-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4148" id="d3e4148" shape="rect"/>Example 37: Usage of the <code>termInfoRefPointer</code> attribute</div><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1858,7 +1846,7 @@
available for the <a href="#directionality" shape="rect">Directionality</a>
data category:</p><ul><li><p>A <code>dir</code> attribute with the value
"ltr", "rtl", "lro" or
- "rlo".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4430" id="d3e4430" shape="rect"/>Example 42: The <a href="#directionality" shape="rect">Directionality</a> data
+ "rlo".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4408" id="d3e4408" shape="rect"/>Example 42: The <a href="#directionality" shape="rect">Directionality</a> data
category expressed locally</div><p>On the first <code>quote</code> element, the <code>its:dir="rtl"</code>
attribute indicates a right-to-left content.</p><div class="exampleInner"><pre xml:space="preserve">
<text
@@ -1869,7 +1857,7 @@
its:dir="rtl"><span dir="rtl">نشاط التدويل، W3C</span></quote>
means <quote>Internationalization Activity, W3C</quote>.</par>
</body>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-dir-selector-3.xml" shape="rect">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4454" id="d3e4454" shape="rect"/>Example 43: The <a href="#directionality" shape="rect">Directionality</a> data
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-dir-selector-3.xml" shape="rect">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4432" id="d3e4432" shape="rect"/>Example 43: The <a href="#directionality" shape="rect">Directionality</a> data
category expressed locally in HTML5</div><div class="exampleInner"><pre xml:space="preserve"><!DOCTYPE html>
<html lang=en>
<head>
@@ -2009,7 +1997,7 @@
within text.</p><p id="withintext-global">GLOBAL: The <code>withinTextRule</code> element
contains the following:</p><ul><li><p>A required <code>selector</code> attribute. It contains an <a href="#selectors" shape="rect">absolute selector</a> which selects the
nodes to which this rule applies.</p></li><li><p>A required <code>withinText</code> attribute with the value
- "yes", "no" or "nested".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4863" id="d3e4863" shape="rect"/>Example 47: Specifying elements within text with a <code>withinTextRule</code>
+ "yes", "no" or "nested".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4841" id="d3e4841" shape="rect"/>Example 47: Specifying elements within text with a <code>withinTextRule</code>
element</div><div class="exampleInner"><pre xml:space="preserve">
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
@@ -3701,7 +3689,7 @@
<em>This section is informative.</em>
</p><p>Several constraints of ITS markup cannot be validated with ITS schemas. The
following <a title="Rule-based validation
							-- Schematron" href="#schematron" shape="rect">[Schematron]</a> document allows for
- validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9222" id="d3e9222" shape="rect"/>Example 97: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve">
+ validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9200" id="d3e9200" shape="rect"/>Example 97: Testing constraints in ITS markup</div><div class="exampleInner"><pre xml:space="preserve">
<sch:schema
xmlns:sch="http://www.ascc.net/xml/schematron" >
<!-- Schematron document to test constraints for global and local ITS markup.
@@ -3769,7 +3757,7 @@
</p><p>The following <a title="Namespace-based Validation
							Dispatching Language (NVDL)" href="#nvdl" shape="rect">[NVDL]</a> document allows validation of
ITS markup which has been added to a host vocabulary. Only ITS elements and
attributes are checked. Elements and attributes of host language are ignored
- during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9244" id="d3e9244" shape="rect"/>Example 98: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve">
+ during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9222" id="d3e9222" shape="rect"/>Example 98: NVDL schema for ITS</div><div class="exampleInner"><pre xml:space="preserve">
<nvdl:rules
xmlns:nvdl="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0" >
<nvdl:namespace ns="http://www.w3.org/2005/11/its">
Received on Wednesday, 17 October 2012 16:31:23 UTC