W3C home > Mailing lists > Public > public-multilingualweb-lt-commits@w3.org > October 2012

its20 CVS commit

From: Felix Sasaki via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 18 Oct 2012 12:00:35 +0000
To: public-multilingualweb-lt-commits@w3.org
Message-Id: <E1TOomC-0004Yz-0V@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory hutz:/tmp/cvs-serv17418/TR-version

Modified Files:
	Overview.html 
Log Message:
Updated list of new ITS 2.0 data categories

Index: Overview.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -d -r1.58 -r1.59
--- Overview.html	18 Oct 2012 11:49:22 -0000	1.58
+++ Overview.html	18 Oct 2012 12:00:32 -0000	1.59
@@ -87,9 +87,9 @@
 <div class="toc3">5.2.2 <a href="#selection-local">Local Selection in an XML Document</a></div>
 </div>
 <div class="toc2">5.3 <a href="#selectors">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d3e2103">XPath 1.0</a></div>
-<div class="toc3">5.3.3 <a href="#d3e2283">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d3e2319">Additional query languages</a></div>
+<div class="toc3">5.3.2 <a href="#d3e2140">XPath 1.0</a></div>
+<div class="toc3">5.3.3 <a href="#d3e2320">CSS Selectors</a></div>
+<div class="toc3">5.3.4 <a href="#d3e2356">Additional query languages</a></div>
 <div class="toc3">5.3.5 <a href="#its-param">Variables in selectors</a></div>
 </div>
 <div class="toc2">5.4 <a href="#link-external-rules">Link to External Rules</a></div>
@@ -213,8 +213,8 @@
 								or XML with ITS 2.0 metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the XPath
 								version 1.0. Other versions of XPath or other query languages (e.g.,
 								CSS selectors) can be expressed via a dedicated <a href="#queryLanguage">queryLanguage</a> attribute.</p></li></ul><p>As of the time of this writing, the new data categories included in ITS
-							2.0 are:</p><span class="editor-note">[Ed. note: Below needs to be updated before next publication.]</span><ul><li><p><a href="#domain">Domain</a></p></li><li><p><a href="#Disambiguation">Disambiguation</a></p></li><li><p><a href="#LocaleFilter">Locale Filter</a></p></li><li><p><a href="#translation-agent-provenance">Provenance</a></p></li><li><p><a href="#TextAnalyisAnnotation">Text Analysis
-									Annotation</a></p></li></ul></div></div><div class="div2">
+							2.0 are:</p><span class="editor-note">[Ed. note: Below needs to be updated before each publication before last call.]</span><ul><li><p><a href="#domain">Domain</a></p></li><li><p><a href="#Disambiguation">Disambiguation</a></p></li><li><p><a href="#LocaleFilter">Locale Filter</a></p></li><li><p><a href="#translation-agent-provenance">Translation Agent Provenance</a></p></li><li><p><a href="#TextAnalyisAnnotation">Text Analysis
+								Annotation</a></p></li><li><p><a href="#externalresource">External Resource</a></p></li><li><p><a href="#target-pointer">Target Pointer</a></p></li><li><p><a href="#idvalue">Id Value</a></p></li><li><p><a href="#preservespace">Preserve Space</a></p></li><li><p><a href="#lqissue">Localization Quality Issue</a></p></li><li><p><a href="#lqprecis">Localization Quality Précis</a></p></li><li><p><a href="#mtconfidence">MT Confidence</a></p></li><li><p><a href="#allowedchars">Allowed Characters</a></p></li><li><p><a href="#storagesize">Storage Size</a></p></li></ul></div></div><div class="div2">
 <h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="motivation-its" id="motivation-its"></a>1.2 Motivation for ITS</h3><p>Content or software that is authored in one language (the <span class="new-term">source
 							language</span>) is often made available in additional languages or
 						adapted with regard to other cultural aspects. This is done through a
@@ -237,7 +237,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="d3e298" id="d3e298"></a>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="d3e335" id="d3e335"></a>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>&lt;resources&gt;
@@ -263,7 +263,7 @@
  &lt;/section&gt;
 &lt;/resources&gt;
 
-</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml">examples/xml/EX-motivation-its-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e313" id="d3e313"></a>Example 2: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text,
+</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml">examples/xml/EX-motivation-its-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e350" id="d3e350"></a>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
@@ -328,7 +328,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="d3e371" id="d3e371"></a>1.3.1.4Content producers</h5><p>This type of user comprises authors, translators and other types of
+<h5><a name="d3e408" id="d3e408"></a>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
@@ -361,7 +361,7 @@
 
 </pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-1.xml">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="d3e423" id="d3e423"></a>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="d3e460" id="d3e460"></a>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>&lt;help xmlns:its="http://www.w3.org/2005/11/its"
  its:version="2.0"&gt;
@@ -378,7 +378,7 @@
  &lt;/body&gt;
 &lt;/help&gt;
 </pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-2.xml">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="d3e448" id="d3e448"></a>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="d3e485" id="d3e485"></a>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">ITS external rule</a>
 								document.</p><div class="exampleInner"><pre>&lt;help xmlns:its="http://www.w3.org/2005/11/its"
  its:version="2.0"&gt;
@@ -394,7 +394,7 @@
   Then from there, run batch file &lt;cmd&gt;Build.bat&lt;/cmd&gt;.&lt;/p&gt;
  &lt;/body&gt;
 &lt;/help&gt;
-</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e469" id="d3e469"></a>Example 6: ITS rule file shared by different documents</div><p>The <code>rules</code> element contains several ITS rules that are common
+</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e506" id="d3e506"></a>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>&lt;its:rules  xmlns:its="http://www.w3.org/2005/11/its" version="2.0"&gt;
@@ -403,7 +403,7 @@
 
 </pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-4.xml">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><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="d3e501" id="d3e501"></a>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="d3e538" id="d3e538"></a>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">Example 3</a>.</p><div class="exampleInner"><pre>&lt;xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:its="http://www.w3.org/2005/11/its"
@@ -717,7 +717,7 @@
 							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">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">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1135" id="d3e1135"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys
+						attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description">Section 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">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1172" id="d3e1172"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys
 							information as to whether a piece of content should be translated or
 							not.</p><p>The simplest formalization of this prose description on a schema language
 							independent level is a <code>translate</code> attribute with
@@ -746,7 +746,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="d3e1218" id="d3e1218"></a>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre>&lt;text&gt;
+							graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1255" id="d3e1255"></a>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre>&lt;text&gt;
  &lt;its:rules version="2.0" 
   xmlns:its="http://www.w3.org/2005/11/its"&gt;
  &lt;its:translateRule translate="yes" selector="//p/img/@src"/&gt;
@@ -1031,9 +1031,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"><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="d3e2103" id="d3e2103"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2140" id="d3e2140"></a>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="d3e2114" id="d3e2114"></a>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an
+<h5><a name="d3e2151" id="d3e2151"></a>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an
 								XPath expression which starts with "<code>/</code>". That is, it
 								must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
 									AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
@@ -1048,17 +1048,17 @@
 										occurs. This includes the implicit declaration of the prefix
 											<code>xml</code> required by the the <a href="#xmlns">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="d3e2174" id="d3e2174"></a>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="d3e2211" id="d3e2211"></a>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>&lt;!-- Definitions for TEI --&gt;
 &lt;its:rules version="2.0"  xmlns:its="http://www.w3.org/2005/11/its"&gt;
  &lt;its:termRule selector="//tei:term" term="yes" xmlns:tei="http://www.tei-c.org/ns/1.0"/&gt;
 &lt;/its:rules&gt;
-</pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2192" id="d3e2192"></a>Example 17: XPath expressions without namespaces</div><p>The <code>term</code> element from DocBook V4.5 is in no
+</pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2229" id="d3e2229"></a>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>&lt;!-- Definitions for DocBook --&gt;
 &lt;its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"&gt;
  &lt;its:termRule selector="//term" term="yes"/&gt;
 &lt;/its:rules&gt;</pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-2.xml">examples/xml/EX-selection-global-2.xml</a>]</p></div></div><div class="div4">
-<h5><a name="d3e2207" id="d3e2207"></a>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords">MUST</a> use a
+<h5><a name="d3e2244" id="d3e2244"></a>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords">MUST</a> use a
 									<a href="http://www.w3.org/TR/xpath/#NT-RelativeLocationPath">RelativeLocationPath</a> as described in <a href="#xpath">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 +1075,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"><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="d3e2283" id="d3e2283"></a>5.3.3 CSS Selectors</h4><p>CSS Selectors are identified by <code>css</code> value in
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2320" id="d3e2320"></a>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="d3e2294" id="d3e2294"></a>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be
+<h5><a name="d3e2331" id="d3e2331"></a>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be
 								interpreted as selector as defined in <a href="#css3-selectors">Selectors Level 3</a>. Both simple selectors and groups of
 								selectors can be used.</p></div><div class="div4">
-<h5><a name="d3e2305" id="d3e2305"></a>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be
+<h5><a name="d3e2342" id="d3e2342"></a>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be
 								interpreted as selector as defined in <a href="#css3-selectors">Selectors Level 3</a>. Selector is not 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"><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="d3e2319" id="d3e2319"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2356" id="d3e2356"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional
 							query languages. For each additional query language processor <a href="#rfc-keywords">MUST</a> define:</p><ul><li><p>identifier of query language used in
 								<code>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
@@ -1140,7 +1140,7 @@
   &lt;its:termRule selector="//term" term="yes"/&gt;
   &lt;its:withinTextRule withinText="yes" selector="//term | //b"/&gt;
  &lt;/its:rules&gt;
-&lt;/myFormatInfo&gt;</pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-1.xml">examples/xml/EX-link-external-rules-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2486" id="d3e2486"></a>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre>&lt;myDoc&gt;
+&lt;/myFormatInfo&gt;</pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-1.xml">examples/xml/EX-link-external-rules-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2523" id="d3e2523"></a>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre>&lt;myDoc&gt;
  &lt;header&gt;
   &lt;its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"
    xmlns:xlink="http://www.w3.org/1999/xlink"
@@ -1154,7 +1154,7 @@
   &lt;p&gt;A &lt;term&gt;Palouse horse&lt;/term&gt; has a spotted coat.&lt;/p&gt;
  &lt;/body&gt;
 &lt;/myDoc&gt;</pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-2.xml">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="d3e2498" id="d3e2498"></a>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre>&lt;myDoc&gt;
+						the following document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2535" id="d3e2535"></a>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre>&lt;myDoc&gt;
  &lt;header&gt;
   &lt;its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"&gt;
    &lt;its:translateRule selector="//header" translate="no"/&gt;
@@ -1191,7 +1191,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&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;Transformations (XSLT) Version 1.0" href="#xslt10">[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="d3e2585" id="d3e2585"></a>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="d3e2622" id="d3e2622"></a>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.
@@ -1486,7 +1486,7 @@
                         <a href="#storagesize">Storage Size</a>
                      </td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td><td>
                         <code>storageEncoding="UTF-8"</code>
-                     </td><td>None</td><td>tbd</td><td>tbd</td></tr></tbody></table><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3547" id="d3e3547"></a>Example 25: Defaults, inheritance and overriding behavior of data
+                     </td><td>None</td><td>tbd</td><td>tbd</td></tr></tbody></table><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3584" id="d3e3584"></a>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">Translate</a> data category in elements is "yes". The
 							content of <code>revision</code> and <code>locNote</code> is not translatable
@@ -1547,7 +1547,7 @@
 &lt;/its:rules&gt;
 </pre></div><p>[Source file: <a href="examples/xml/EX-translate-selector-1.xml">examples/xml/EX-translate-selector-1.xml</a>]</p></div><p id="translate-local">LOCAL: The following local markup is available
 							for the <a href="#trans-datacat">Translate</a> data category:</p><ul><li><p>A <code>translate</code> attribute with the value
-			"yes" or "no".</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>It is not possible to override the <a href="#trans-datacat">Translate</a> data category settings of attributes using
+									"yes" or "no".</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>It is not possible to override the <a href="#trans-datacat">Translate</a> data category settings of attributes using
 								local markup. This limitation is consistent with the advised
 								practice of not using translatable attributes. If attributes need to
 								be translatable (e.g., an HTML <code>alt</code> attribute), then
@@ -1655,7 +1655,7 @@
  &lt;body&gt;
   &lt;msg id="NotFound"&gt;Cannot find {0} on {1}.&lt;/msg&gt;
  &lt;/body&gt;
-&lt;/myRes&gt;</pre></div><p>[Source file: <a href="examples/xml/EX-locNoteRef-attribute-1.xml">examples/xml/EX-locNoteRef-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3945" id="d3e3945"></a>Example 32: The <code>locNoteRefPointer</code> attribute</div><p>The <code>locNoteRefPointer</code> attribute contains a <a href="#selectors">relative selector</a> pointing to a node
+&lt;/myRes&gt;</pre></div><p>[Source file: <a href="examples/xml/EX-locNoteRef-attribute-1.xml">examples/xml/EX-locNoteRef-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3982" id="d3e3982"></a>Example 32: The <code>locNoteRefPointer</code> attribute</div><p>The <code>locNoteRefPointer</code> attribute contains a <a href="#selectors">relative selector</a> pointing to a node
 								that holds the URI referring to the location of the note.</p><div class="exampleInner"><pre>&lt;dataFile&gt;
  &lt;prolog&gt;
   &lt;its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0"&gt;
@@ -1679,7 +1679,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="d3e4006" id="d3e4006"></a>Example 33: The <a href="#locNote-datacat">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="d3e4043" id="d3e4043"></a>Example 33: The <a href="#locNote-datacat">Localization Note</a> data
 								category expressed locally</div><div class="exampleInner"><pre>&lt;msgList xmlns:its="http://www.w3.org/2005/11/its"
  xml:space="preserve" its:version="2.0"&gt;
  &lt;data name="LISTFILTERS_VARIANT"
@@ -1690,7 +1690,7 @@
   &lt;value&gt;Translated from English content dated &lt;span id="version-info"&gt;%1\$s&lt;/span&gt; GMT.&lt;/value&gt;
  &lt;/data&gt;
 &lt;/msgList&gt;
-</pre></div><p>[Source file: <a href="examples/xml/EX-locNote-selector-2.xml">examples/xml/EX-locNote-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4020" id="d3e4020"></a>Example 34: The <a href="#locNote-datacat">Localization Note</a> data
+</pre></div><p>[Source file: <a href="examples/xml/EX-locNote-selector-2.xml">examples/xml/EX-locNote-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4057" id="d3e4057"></a>Example 34: The <a href="#locNote-datacat">Localization Note</a> data
 								category expressed locally in HTML5</div><div class="exampleInner"><pre>&lt;!DOCTYPE html&gt;
 &lt;html lang=en&gt;
   &lt;head&gt;
@@ -1726,7 +1726,7 @@
 										term.</p></li><li><p>A <code>termInfoRefPointer</code> attribute that contains a
 											<a href="#selectors">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="d3e4118" id="d3e4118"></a>Example 35: Usage of the <code>termInfoPointer</code> attribute</div><div class="exampleInner"><pre>&lt;text&gt;
+										location of the terminology information.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4155" id="d3e4155"></a>Example 35: Usage of the <code>termInfoPointer</code> attribute</div><div class="exampleInner"><pre>&lt;text&gt;
  &lt;its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"&gt;
    &lt;its:termRule selector="//term" term="yes"
     termInfoPointer="id(@def)"/&gt;
@@ -1736,7 +1736,7 @@
 structure, between the implied author or some other addresser,
 and the fiction.&lt;/gloss&gt;&lt;/p&gt;
 &lt;/text&gt;
-</pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-1.xml">examples/xml/EX-terms-selector-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4131" id="d3e4131"></a>Example 36: Usage of the <code>termInfoRef</code> attribute</div><div class="exampleInner"><pre>&lt;text&gt;
+</pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-1.xml">examples/xml/EX-terms-selector-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4168" id="d3e4168"></a>Example 36: Usage of the <code>termInfoRef</code> attribute</div><div class="exampleInner"><pre>&lt;text&gt;
  &lt;its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"&gt;
    &lt;its:termRule selector="//term[1]" term="yes"
     termInfoRef="#TDPV"/&gt;
@@ -1746,7 +1746,7 @@
 structure, between the implied author or some other addresser,
 and the fiction.&lt;/gloss&gt;&lt;/p&gt;
 &lt;/text&gt;
-</pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-2.xml">examples/xml/EX-terms-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4144" id="d3e4144"></a>Example 37: Usage of the <code>termInfoRefPointer</code> attribute</div><div class="exampleInner"><pre>&lt;text&gt;
+</pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-2.xml">examples/xml/EX-terms-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4181" id="d3e4181"></a>Example 37: Usage of the <code>termInfoRefPointer</code> attribute</div><div class="exampleInner"><pre>&lt;text&gt;
  &lt;its:rules version="2.0"  xmlns:its="http://www.w3.org/2005/11/its"&gt;
    &lt;its:termRule selector="//term" term="yes"
     termInfoRefPointer="@target"/&gt;
@@ -1832,7 +1832,7 @@
 							available for the <a href="#directionality">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="d3e4401" id="d3e4401"></a>Example 42: The <a href="#directionality">Directionality</a> data
+								"rlo".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4438" id="d3e4438"></a>Example 42: The <a href="#directionality">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>&lt;text xml:lang="en" xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0"&gt;
  &lt;body&gt;
@@ -1841,7 +1841,7 @@
    means &lt;quote&gt;Internationalization Activity, W3C&lt;/quote&gt;.&lt;/par&gt;
  &lt;/body&gt;
 &lt;/text&gt;
-</pre></div><p>[Source file: <a href="examples/xml/EX-dir-selector-3.xml">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4422" id="d3e4422"></a>Example 43: The <a href="#directionality">Directionality</a> data
+</pre></div><p>[Source file: <a href="examples/xml/EX-dir-selector-3.xml">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4459" id="d3e4459"></a>Example 43: The <a href="#directionality">Directionality</a> data
 								category expressed locally in HTML5</div><div class="exampleInner"><pre>&lt;!DOCTYPE html&gt;
 &lt;html lang=en&gt;
   &lt;head&gt;
@@ -1973,7 +1973,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">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="d3e4831" id="d3e4831"></a>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="d3e4868" id="d3e4868"></a>Example 47: Specifying elements within text with a <code>withinTextRule</code>
 								element</div><div class="exampleInner"><pre>&lt;its:rules version="2.0"  xmlns:its="http://www.w3.org/2005/11/its"&gt;
  &lt;its:withinTextRule withinText="yes" selector="//b | //em | //i"/&gt;
 &lt;/its:rules&gt;</pre></div><p>[Source file: <a href="examples/xml/EX-within-text-implementation-1.xml">examples/xml/EX-within-text-implementation-1.xml</a>]</p></div><p id="withintext-local">LOCAL: The following local markup is available
@@ -3904,7 +3904,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&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;-- Schematron" href="#schematron">[Schematron]</a> document allows for
-					validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9892" id="d3e9892"></a>Example 105: Testing constraints in ITS markup</div><div class="exampleInner"><pre>&lt;schema xmlns="http://www.ascc.net/xml/schematron"&gt;
+					validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9929" id="d3e9929"></a>Example 105: Testing constraints in ITS markup</div><div class="exampleInner"><pre>&lt;schema xmlns="http://www.ascc.net/xml/schematron"&gt;
 &lt;!-- Schematron document to test constraints for global and local ITS markup.
  For ITS markup definitions, see http://www.w3.org/TR/its/ . --&gt;
  &lt;ns prefix="its" uri="http://www.w3.org/2005/11/its"/&gt;
@@ -3955,7 +3955,7 @@
          </p><p>The following <a title="Namespace-based Validation&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;&#x9;Dispatching Language (NVDL)" href="#nvdl">[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="d3e9914" id="d3e9914"></a>Example 106: NVDL schema for ITS</div><div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+					during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9951" id="d3e9951"></a>Example 106: NVDL schema for ITS</div><div class="exampleInner"><pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
 &lt;rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"&gt;
   &lt;namespace ns="http://www.w3.org/2005/11/its"&gt;
     &lt;validate schema="its20-elements.rng"/&gt;   
Received on Thursday, 18 October 2012 12:00:42 UTC

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