- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Fri, 21 Jun 2013 17:38:26 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv14123
Modified Files:
its20.html its20.odd
Log Message:
https://www.w3.org/International/multilingualweb/lt/track/actions/540 done, sending mail to get feedback from group now
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/21 16:54:47 1.464
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/21 17:38:26 1.465
@@ -59,9 +59,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="#d0e2612" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2606" shape="rect">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2860" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2854" 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>
@@ -250,7 +250,7 @@
or more pieces of content (e.g. XML nodes): a <a href="#basic-concepts-selection-global" shape="rect">global</a>, rule-based
approach as well as a <a href="#basic-concepts-selection-local" shape="rect">local</a>, attribute-based approached. Here, for
instance, a <code class="its-elem-markup">translateRule</code> first specifies that only every second element inside
- <code>keyvalue_pairs</code> is intnded for translation; later, an ITS <code class="its-attr-markup">translate</code> attribute specifies that
+ <code>keyvalue_pairs</code> is intended for translation; later, an ITS <code class="its-attr-markup">translate</code> attribute specifies that
one of these elements is not to be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//arguments"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -324,7 +324,7 @@
<em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0.</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global" shape="rect">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors" shape="rect">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param" shape="rect">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has a <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="sectio-ref" href="#traceability" shape="rect">Section 2.6: Traceability</a> for details.</p></li></ul><p>
<em>Mappings:</em> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <a title="" href="#nif-reference" shape="rect">[NIF]</a> and links to guidance about how to relate ITS 2.0 to XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">Section 2.7: Mapping and conversion</a> for details.</p><p>
<em>Changes to the conformance section</em>: The <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed, and a conformance clause related to processing <a title="" href="#nif-reference" shape="rect">[NIF]</a> has been added. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, a dedicated conformance section has been created. Finally, a conformance clause related to Non-ITS elements and attributes has been added.</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="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.5 Extended implementation hints</h3><p id="unicode-normalization">As a general guidance, implementations of ITS 2.0 <a href="#rfc-keywords" shape="rect">SHOULD</a> use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</a>.</p></div></div><div class="div1">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.5 Extended implementation hints</h3><p id="unicode-normalization">As a general guidance, implementations of ITS 2.0 are encouraged to use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</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="basic-concepts" id="basic-concepts" shape="rect"/>2 Basic Concepts</h2><p>
<em>This section is informative.</em>
</p><p>The purpose of this section is to provide basic knowledge about how ITS 2.0 works. Detailed knowledge (including formal definitions) is given in the subsequent sections.</p><div class="div2">
@@ -445,7 +445,7 @@
data categories allow the addition of information and which allow to point to existing
information.</p><p>Adding information and pointing to existing information are <em>mutually
exclusive</em>; attributes for adding information and attributes for pointing to the
- same information <a href="#rfc-keywords" shape="rect">MUST NOT</a> appear at the same rule element.</p></div><div class="div2">
+ same information are not allowed to appear at the same rule element.</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="specific-HTML-support" id="specific-HTML-support" shape="rect"/>2.5 Specific HTML support</h3><p>For applying ITS 2.0 data categories to HTML, five aspects are of importance:</p><ol class="depth1"><li><p>Global approach in HTML5</p></li><li><p>Local Approach</p></li><li><p>HTML markup with ITS 2.0 counterparts</p></li><li><p>Standoff markup in HTML5</p></li><li><p>Version of HTML</p></li></ol><p>In the following sections these aspects are briefly discussed.</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="html5-global-approach" id="html5-global-approach" shape="rect"/>2.5.1 Global approach in HTML5</h4><p>To account for the so-called <a href="#basic-concepts-selection-global" shape="rect">global
approach</a> in HTML, this specification (see <a class="section-ref" href="#html5-global-rules" shape="rect">Section 6.2: Global rules</a>) defines: </p><ul><li><p>A link type for referring to external files with global rules from a <code>link</code>
@@ -559,7 +559,7 @@
and localization of XML schemas and documents.] The concept of a data
category is independent of its implementation in an XML and HTML environment (e.g.,
using an element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" 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 D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1646" id="d0e1646" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
+ <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 D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1640" id="d0e1640" shape="rect"/>Example 10: 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 is intended for translation 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
@@ -831,9 +831,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</p></div><div class="div3">
-<h4><a href="#contents" 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="d0e2612" id="d0e2612" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<h4><a href="#contents" 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="d0e2606" id="d0e2606" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2623" id="d0e2623" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+<h5><a name="d0e2617" id="d0e2617" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
that starts with "<code>/</code>". That is, it <a href="#rfc-keywords" shape="rect">MUST</a> 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">
AbsoluteLocationPath</a>s as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
@@ -878,14 +878,14 @@
be used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-and-attributes">CSS selectors have no ability to point to
attributes.</p></div><p>CSS Selectors are identified by the value <code>css</code> in the
<code class="its-attr-markup">queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d0e2837" id="d0e2837" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2831" id="d0e2831" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Both simple
selectors and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2847" id="d0e2847" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2841" id="d0e2841" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. A selector is
not evaluated against the complete document tree but only against subtrees rooted at
nodes selected by the selector in the <code class="its-attr-markup">selector</code> attribute.</p></div></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2860" id="d0e2860" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
+<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="d0e2854" id="d0e2854" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
languages. For each additional query language the processor <a href="#rfc-keywords" shape="rect">MUST</a> define:</p><ul><li><p>the identifier of the query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating an absolute selector to a collection of nodes;</p></li><li><p>rules for evaluating a relative selector to a collection of nodes.</p></li></ul><p>Because future versions of this specification are likely to define additional query
languages, the following query language identifiers are reserved: <code>xpath</code>,
<code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
@@ -1294,7 +1294,7 @@
easier selection mechanism, they can switch query language to CSS selectors by using
the <code class="its-attr-markup">queryLanguage</code> attribute, see <a class="section-ref" href="#queryLanguage" shape="rect">Section 5.3.1: Choosing Query Language</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The HTML5 parsing algorithm automatically puts all HTML elements into the XHTML
namespace (<code>http://www.w3.org/1999/xhtml</code>). Selectors used in global rules
- <a href="#rfc-keywords" shape="rect">MUST</a> take this into account.</p></div><p id="html5-external-global-rules">Linking to external global rules is specified in
+ need to take this into account.</p></div><p id="html5-external-global-rules">Linking to external global rules is specified in
the <code class="its-attr-markup">href</code> attribute of <code>link</code> elements, with the link relation
<code>its-rules</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Using XPath in global rules linked from HTML documents does not create an additional
burden to implementers. Parsing HTML content produces a DOM tree that can be directly
@@ -1567,7 +1567,8 @@
content of the element, <em>including</em> child elements, but
<em>excluding</em> attributes.</p><p id="localizationnote-global">GLOBAL: The <code class="its-elem-markup">locNoteRule</code> element contains
the following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors" shape="rect">absolute selector</a> that selects the nodes to which this
- rule applies.</p></li><li><p>A required <code class="its-attr-markup">locNoteType</code> attribute with the value"description" or "alert".</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code class="its-elem-markup">locNote</code> element that contains the note itself and allows for <a href="#selection-local" shape="rect">local ITS markup</a>.</p></li><li><p>A <code class="its-attr-markup">locNotePointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a> pointing to a node that holds the
+ rule applies.</p></li><li><p>A required <code class="its-attr-markup">locNoteType</code> attribute with the value
+ "description" or "alert".</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code class="its-elem-markup">locNote</code> element that contains the note itself and allows for <a href="#selection-local" shape="rect">local ITS markup</a>.</p></li><li><p>A <code class="its-attr-markup">locNotePointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a> pointing to a node that holds the
localization note.</p></li><li><p>A <code class="its-attr-markup">locNoteRef</code> attribute that contains an IRI referring to the
location of the localization note.</p></li><li><p>A <code class="its-attr-markup">locNoteRefPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a> pointing to a node that holds the
IRI referring to the location of the localization note.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locNote-element-1" id="EX-locNote-element-1" shape="rect"/>Example 31: The <code class="its-elem-markup">locNote</code> element</div><p>The <code class="its-elem-markup">locNoteRule</code> element associates the content of the <code class="its-elem-markup">locNote</code>
@@ -2389,8 +2390,8 @@
information</a>.</p></li><li><p>A <code class="its-attr-markup">revTool</code> or <code class="its-attr-markup">revToolRef</code> attribute that
implements the <a href="#provenanceDefs" shape="rect">tool-related revision
provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">provRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">reference to external provenance
- descriptions</a>.</p></li></ul></li></ul></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="provenanceRecord-order">The order of <code class="its-elem-markup">provenanceRecord</code> elements
- within a <code class="its-elem-markup">provenanceRecords</code> element <a href="#rfc-keywords" shape="rect">SHOULD</a> reflect the order with which
+ descriptions</a>.</p></li></ul></li></ul></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="provenanceRecord-order">Ideally the order of <code class="its-elem-markup">provenanceRecord</code> elements
+ within a <code class="its-elem-markup">provenanceRecords</code> element reflects the order with which
they were added to the document, with the most recently added one listed
first.</p></div><p>When the attributes <code class="its-attr-markup">person</code>, <code class="its-attr-markup">personRef</code>, <code class="its-attr-markup">org</code>,
<code class="its-attr-markup">orgRef</code>, <code class="its-attr-markup">tool</code>, <code class="its-attr-markup">toolRef</code>, <code class="its-attr-markup">revPerson</code>,
@@ -2570,7 +2571,7 @@
only with global rules. There is no inheritance. There is no default.</p><p id="targetpointer-global">GLOBAL: The <code class="its-elem-markup">targetPointerRule</code> element contains
the following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors" shape="rect">absolute selector</a> that selects the nodes to which this
rule applies.</p></li><li><p>A required <code class="its-attr-markup">targetPointer</code> attribute. It contains a <a href="#selectors" shape="rect">relative selector</a> that points to the node for the target
- content corresponding to the selected source node.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The source node and the target node may be of different types, but the target node <a href="#rfc-keywords" shape="rect">MUST</a> be able
+ content corresponding to the selected source node.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The source node and the target node may be of different types, but the target node has
to contain the same content as the source node (e.g., an attribute node cannot be
the target node of a source node that is an element with children).</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-target-pointer-global-1" id="EX-target-pointer-global-1" shape="rect"/>Example 66: Defining the target location of a source content with the
<code class="its-elem-markup">targetPointerRule</code> element</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><file></strong>
@@ -2685,7 +2686,7 @@
rule applies.</p></li><li><p>A required <code class="its-attr-markup">space</code> attribute with the value "default" or
"preserve".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-preservespace-global-1" id="EX-preservespace-global-1" shape="rect"/>Example 70: The <a href="#preservespace" shape="rect">Preserve Space</a> data category expressed
globally</div><p>The <code class="its-elem-markup">preserveSpaceRule</code> element specifies that whitespace in all verse
- elements <a href="#rfc-keywords" shape="rect">MUST</a> be treated literally.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><book></strong>
+ elements are to be treated literally.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><book></strong>
<strong class="hl-tag" style="color: #000096"><info></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:preserveSpaceRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//verse"</span> <span class="hl-attribute" style="color: #F5844C">space</span>=<span class="hl-value" style="color: #993300">"preserve"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -2701,7 +2702,7 @@
</pre></div><p>[Source file: <a href="examples/xml/EX-preservespace-global-1.xml" shape="rect">examples/xml/EX-preservespace-global-1.xml</a>]</p></div><p id="preservespace-local">LOCAL: The <code>xml:space</code> attribute, as defined
in section 2.10 of <a title="Extensible Markup Language
 (XML) 1.0 (Fifth Edition)" href="#xml10spec" shape="rect">[XML 1.0]</a>, maps exactly to the <a href="#preservespace" shape="rect">Preserve Space</a> data category.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-preservespace-local-1" id="EX-preservespace-local-1" shape="rect"/>Example 71: The <a href="#preservespace" shape="rect">Preserve Space</a> data category expressed
locally</div><p>The standard <code>xml:space</code> attribute specifies that the whitespace in the
- verse element <a href="#rfc-keywords" shape="rect">MUST</a> be treated literally.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><book></strong>
+ verse element are to be treated literally.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><book></strong>
<strong class="hl-tag" style="color: #000096"><verse</strong> <span class="hl-attribute" style="color: #F5844C">xml:space</span>=<span class="hl-value" style="color: #993300">"preserve"</span><strong class="hl-tag" style="color: #000096">></strong>
'Twas brillig, and the slithy toves
Did gyre and gimble in the wabe;
@@ -2831,8 +2832,8 @@
implements the <a href="#lqissueDefs" shape="rect">profile reference
information</a>.</p></li><li><p>An optional <code class="its-attr-markup">locQualityIssueEnabled</code> attribute that
implements the <a href="#lqissueDefs" shape="rect">enabled
- information</a>.</p></li></ul></li></ul></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="locQualityIssue-order">The order of <code class="its-elem-markup">locQualityIssue</code>
- elements within a <code class="its-elem-markup">locQualityIssues</code> element <a href="#rfc-keywords" shape="rect">SHOULD</a> reflect the order
+ information</a>.</p></li></ul></li></ul></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="locQualityIssue-order">Ideally the order of <code class="its-elem-markup">locQualityIssue</code>
+ elements within a <code class="its-elem-markup">locQualityIssues</code> element reflects the order
with which they were added to the document, with the most recently added one
listed first.</p></div><p>When the attributes <code class="its-attr-markup">locQualityIssueType</code>,
<code class="its-attr-markup">locQualityIssueComment</code>, <code class="its-attr-markup">locQualityIssueSeverity</code>,
@@ -3142,8 +3143,7 @@
<a href="#allowedchars" shape="rect">Allowed Characters</a> data category:</p><ul><li><p>A <code class="its-attr-markup">allowedCharacters</code> attribute that contains the regular expression
indicating the allowed characters.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-local-1" id="EX-allowedCharacters-local-1" shape="rect"/>Example 86: The <a href="#allowedchars" shape="rect">Allowed Characters</a> data category expressed
locally in XML</div><p>The local <code class="its-attr-markup">allowedCharacters</code> attribute specifies that the translated
- content of element <code>panelmsg</code>
- <a href="#rfc-keywords" shape="rect">MUST</a> contain only Unicode characters
+ content of element <code>panelmsg</code> is only allowed to contain Unicode characters
between U+0020 and U+00FE.</p><div class="exampleInner"><pre xml:space="preserve"><span class="hl-directive" style="color: maroon"><?xml version="1.0"?></span>
<strong class="hl-tag" style="color: #000096"><messages</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><msg</strong> <span class="hl-attribute" style="color: #F5844C">num</span>=<span class="hl-value" style="color: #993300">"123"</span><strong class="hl-tag" style="color: #000096">></strong>Click the <strong class="hl-tag" style="color: #000096"><panelmsg</strong> <span class="hl-attribute" style="color: #F5844C">its:allowedCharacters</span>=<span class="hl-value" style="color: #993300">"[&#x0020;-&#x00FE;]"</span><strong class="hl-tag" style="color: #000096">
@@ -3315,17 +3315,7 @@
media type as specified in IETF RFC 3023.</p><p>
<em>Encoding considerations:</em> Identical to those of "application/xml" as
described in IETF RFC 3023, section 3.2, as applied to an ITS document.</p><p>
- <em>Security considerations:</em> An ITS 1.0 or ITS 2.0 document can cause arbitrary
- URIs or IRIs to be dereferenced, via the <code>xlink:href</code> attribute at the <code><its:rules></code> element.
- Therefore, the security issues of [RFC3987] Section 8 is to be considered. In addition,
- the contents of resources identified by file: URIs can in some cases be accessed,
- processed and returned as results. An implementation of ITS global rules requires the
- support of XPath 1.0 or its successor. Hence, processing of global rules might encompass
- dereferencing of URIs or IRIs during computation of XPath expressions. Arbitrary recursion
- is possible, as is arbitrarily large memory usage, and implementations may place limits on
- CPU and memory usage, as well as restricting access to system-defined functions. ITS 1.0
- and ITS 2.0 permit extensions. Hence it is possible that application/its+xml may describe
- content that has security implications beyond those described here.</p><p>
+ <em>Security considerations:</em> An ITS 1.0 or ITS 2.0 document may cause arbitrary URIs or IRIs to be dereferenced, via the @xlink:href attribute at the its:rules element. Therefore, the security issues of <a title="Internationalized Resource
 Identifiers (IRIs)" href="#rfc3987" shape="rect">[RFC 3987]</a> Section 8 should be considered. In addition, the contents of resources identified by file: URIs can in some cases be accessed, processed and returned as results. An implementation of ITS global rules requires the support of XPath 1.0 or its successor. Hence, processing of global rules might encompass dereferencing of URIs or IRIs during computation of XPath expressions. Arbitrary recursion is possible, as is arbitrarily large memory usage, and implementations may place limits on CPU and memory usage, as well as restricting access to system-defined functions. ITS 1.0 and ITS 2.0 permit extensions. Hence it is possible that application/its+xml may describe content that has ecurity implications beyond those described here.</p><p>
<em>Interoperability considerations:</em> There are no known interoperability
issues.</p><p>
<em>Published specification:</em>
@@ -3357,11 +3347,9 @@
kinds of issues they identify and take appropriate action even if another tool does not
know the specific issues identified by the generating tool.</p><p>The scope column in the following table identifies whether the issue type applies to the
source text (“S”), target text (“T”) or both (“S or T”).</p><p>The values listed in the following table are allowed for <code class="its-attr-markup">locQualityIssueType</code>.
- The values a tool implementing the data category produces for the attribute <a href="#rfc-keywords" shape="rect">MUST</a> match one
- of the values provided in this table and be as semantically accurate as possible. If a tool can map
- its internal values to these types it <a href="#rfc-keywords" shape="rect">MUST</a> do so and <a href="#rfc-keywords" shape="rect">MUST NOT</a> use the value
- <code>other</code>, which is reserved strictly for values that cannot be mapped to these
- values.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-tool-specific-mappings">The <a href="http://www.w3.org/International/its/ig/" shape="rect">ITS Interest Group</a> maintains an
+ Ideally the values a tool implementing the data category produces for the attribute matches one
+ of the values provided in this table and are as semantically accurate as possible. Tools are encouraged to
+ map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-tool-specific-mappings">The <a href="http://www.w3.org/International/its/ig/" shape="rect">ITS Interest Group</a> maintains an
informative mappings of tools to localization quality issue types. <a href="http://www.w3.org/International/its/wiki/Tool_specific_mappings" shape="rect">The ITS IG
Wiki</a> provides information on <a href="http://www.w3.org/International/its/wiki/Tool_specific_mappings#Update_of_this_page" shape="rect">how to update that list</a>. The purpose of these mappings is to document how tool internal information
relates to the ITS 2.0 quality types. To foster interoperability, implementers are strongly encouraged not to rely on these mappings
@@ -3558,10 +3546,10 @@
<code>other</code>
</td><td rowspan="1" colspan="1">Any issue that cannot be assigned to any values listed above.</td><td rowspan="1" colspan="1"/><td rowspan="1" colspan="1">S or T</td><td rowspan="1" colspan="1">
<ul><li><p>This value allows for the inclusion of any issues not included in the
- previously listed values. This value <a href="#rfc-keywords" shape="rect">MUST NOT</a> be used for any tool- or
+ previously listed values. It is encouraged not to use this value for any tool- or
model-specific issues that can be mapped to the values listed above.</p></li><li><p>In addition, this value is not synonymous with <code>uncategorized</code> in
that <code>uncategorized</code> issues may be assigned to another precise value,
- while other issues cannot.</p></li><li><p>If a system has an "miscellaneous" or "other" value, it <a href="#rfc-keywords" shape="rect">MUST</a> be mapped to this
+ while other issues cannot.</p></li><li><p>If a system has an "miscellaneous" or "other" value, it is better to map this to this
value even if the specific instance of the issue might be mapped to another
value.</p></li></ul>
</td></tr></tbody></table></div><div class="div1">
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/21 16:30:24 1.471
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/21 17:38:26 1.472
@@ -245,7 +245,7 @@
or more pieces of content (e.g. XML nodes): a <ref target="#basic-concepts-selection-global">global</ref>, rule-based
approach as well as a <ref target="#basic-concepts-selection-local">local</ref>, attribute-based approached. Here, for
instance, a <gi>translateRule</gi> first specifies that only every second element inside
- <code>keyvalue_pairs</code> is intnded for translation; later, an ITS <att>translate</att> attribute specifies that
+ <code>keyvalue_pairs</code> is intended for translation; later, an ITS <att>translate</att> attribute specifies that
one of these elements is not to be translated.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-motivation-its-2.xml"/>
@@ -430,7 +430,7 @@
</div>
<div xml:id="extended-implementation-hints"><head>Extended implementation hints</head>
- <p xml:id="unicode-normalization">As a general guidance, implementations of ITS 2.0 <ref target="#rfc-keywords">SHOULD</ref> use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <ptr target="#charmod-norm" type="bibref"/>.</p></div>
+ <p xml:id="unicode-normalization">As a general guidance, implementations of ITS 2.0 are encouraged to use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <ptr target="#charmod-norm" type="bibref"/>.</p></div>
</div>
<div xml:id="basic-concepts">
<head>Basic Concepts</head>
@@ -664,7 +664,7 @@
information.</p>
<p>Adding information and pointing to existing information are <emph>mutually
exclusive</emph>; attributes for adding information and attributes for pointing to the
- same information <ref target="#rfc-keywords">MUST NOT</ref> appear at the same rule element.</p>
+ same information are not allowed to appear at the same rule element.</p>
</div>
<div xml:id="specific-HTML-support"><head>Specific HTML support</head>
@@ -1947,7 +1947,7 @@
<note>
<p>The HTML5 parsing algorithm automatically puts all HTML elements into the XHTML
namespace (<code>http://www.w3.org/1999/xhtml</code>). Selectors used in global rules
- <ref target="#rfc-keywords">MUST</ref> take this into account.</p>
+ need to take this into account.</p>
</note>
<p xml:id="html5-external-global-rules">Linking to external global rules is specified in
the <att>href</att> attribute of <code>link</code> elements, with the link relation
@@ -3772,8 +3772,8 @@
</item>
</list>
<note>
- <p xml:id="provenanceRecord-order">The order of <gi>provenanceRecord</gi> elements
- within a <gi>provenanceRecords</gi> element <ref target="#rfc-keywords">SHOULD</ref> reflect the order with which
+ <p xml:id="provenanceRecord-order">Ideally the order of <gi>provenanceRecord</gi> elements
+ within a <gi>provenanceRecords</gi> element reflects the order with which
they were added to the document, with the most recently added one listed
first.</p>
</note>
@@ -3931,7 +3931,7 @@
target="#selectors">relative selector</ref> that points to the node for the target
content corresponding to the selected source node.</item>
</list>
- <note><p>The source node and the target node may be of different types, but the target node <ref target="#rfc-keywords">MUST</ref> be able
+ <note><p>The source node and the target node may be of different types, but the target node has
to contain the same content as the source node (e.g., an attribute node cannot be
the target node of a source node that is an element with children).</p></note>
<exemplum xml:id="EX-target-pointer-global-1">
@@ -4072,7 +4072,7 @@
<head>The <ref target="#preservespace">Preserve Space</ref> data category expressed
globally</head>
<p>The <gi>preserveSpaceRule</gi> element specifies that whitespace in all verse
- elements <ref target="#rfc-keywords">MUST</ref> be treated literally.</p>
+ elements are to be treated literally.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-preservespace-global-1.xml"/>
</exemplum>
@@ -4084,7 +4084,7 @@
<head>The <ref target="#preservespace">Preserve Space</ref> data category expressed
locally</head>
<p>The standard <code>xml:space</code> attribute specifies that the whitespace in the
- verse element <ref target="#rfc-keywords">MUST</ref> be treated literally.</p>
+ verse element are to be treated literally.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-preservespace-local-1.xml"/>
</exemplum>
@@ -4318,8 +4318,8 @@
</list>
</item>
</list>
- <note><p xml:id="locQualityIssue-order">The order of <gi>locQualityIssue</gi>
- elements within a <gi>locQualityIssues</gi> element <ref target="#rfc-keywords">SHOULD</ref> reflect the order
+ <note><p xml:id="locQualityIssue-order">Ideally the order of <gi>locQualityIssue</gi>
+ elements within a <gi>locQualityIssues</gi> element reflects the order
with which they were added to the document, with the most recently added one
listed first.</p></note>
<p>When the attributes <att>locQualityIssueType</att>,
@@ -4677,7 +4677,7 @@
<head>The <ref target="#allowedchars">Allowed Characters</ref> data category expressed
locally in XML</head>
<p>The local <att>allowedCharacters</att> attribute specifies that the translated
- content of element <code>panelmsg</code> <ref target="#rfc-keywords">MUST</ref> contain only Unicode characters
+ content of element <code>panelmsg</code> is only allowed to contain Unicode characters
between U+0020 and U+00FE.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-allowedCharacters-local-1.xml"/>
@@ -5005,17 +5005,7 @@
media type as specified in IETF RFC 3023.</p>
<p><emph>Encoding considerations:</emph> Identical to those of "application/xml" as
described in IETF RFC 3023, section 3.2, as applied to an ITS document.</p>
- <p><emph>Security considerations:</emph> An ITS 1.0 or ITS 2.0 document can cause arbitrary
- URIs or IRIs to be dereferenced, via the <code>xlink:href</code> attribute at the <code><its:rules></code> element.
- Therefore, the security issues of [RFC3987] Section 8 is to be considered. In addition,
- the contents of resources identified by file: URIs can in some cases be accessed,
- processed and returned as results. An implementation of ITS global rules requires the
- support of XPath 1.0 or its successor. Hence, processing of global rules might encompass
- dereferencing of URIs or IRIs during computation of XPath expressions. Arbitrary recursion
- is possible, as is arbitrarily large memory usage, and implementations may place limits on
- CPU and memory usage, as well as restricting access to system-defined functions. ITS 1.0
- and ITS 2.0 permit extensions. Hence it is possible that application/its+xml may describe
- content that has security implications beyond those described here.</p>
+ <p><emph>Security considerations:</emph> An ITS 1.0 or ITS 2.0 document may cause arbitrary URIs or IRIs to be dereferenced, via the @xlink:href attribute at the its:rules element. Therefore, the security issues of <ptr target="#rfc3987" type="bibref"/> Section 8 should be considered. In addition, the contents of resources identified by file: URIs can in some cases be accessed, processed and returned as results. An implementation of ITS global rules requires the support of XPath 1.0 or its successor. Hence, processing of global rules might encompass dereferencing of URIs or IRIs during computation of XPath expressions. Arbitrary recursion is possible, as is arbitrarily large memory usage, and implementations may place limits on CPU and memory usage, as well as restricting access to system-defined functions. ITS 1.0 and ITS 2.0 permit extensions. Hence it is possible that application/its+xml may describe content that has security implications beyond those described here.</p>
<p><emph>Interoperability considerations:</emph> There are no known interoperability
issues.</p>
<p><emph>Published specification:</emph>
@@ -5066,11 +5056,9 @@
<p>The scope column in the following table identifies whether the issue type applies to the
source text (“S”), target text (“T”) or both (“S or T”).</p>
<p>The values listed in the following table are allowed for <att>locQualityIssueType</att>.
- The values a tool implementing the data category produces for the attribute <ref target="#rfc-keywords">MUST</ref> match one
- of the values provided in this table and be as semantically accurate as possible. If a tool can map
- its internal values to these types it <ref target="#rfc-keywords">MUST</ref> do so and <ref target="#rfc-keywords">MUST NOT</ref> use the value
- <code>other</code>, which is reserved strictly for values that cannot be mapped to these
- values.</p>
+ Ideally the values a tool implementing the data category produces for the attribute matches one
+ of the values provided in this table and are as semantically accurate as possible. Tools are encouraged to
+ map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p>
<note>
<p xml:id="qa-issue-types-tool-specific-mappings">The <ref
target="http://www.w3.org/International/its/ig/">ITS Interest Group</ref> maintains an
@@ -5486,12 +5474,12 @@
<cell>
<list type="unordered">
<item>This value allows for the inclusion of any issues not included in the
- previously listed values. This value <ref target="#rfc-keywords">MUST NOT</ref> be used for any tool- or
+ previously listed values. It is encouraged not to use this value for any tool- or
model-specific issues that can be mapped to the values listed above.</item>
<item>In addition, this value is not synonymous with <code>uncategorized</code> in
that <code>uncategorized</code> issues may be assigned to another precise value,
while other issues cannot.</item>
- <item>If a system has an "miscellaneous" or "other" value, it <ref target="#rfc-keywords">MUST</ref> be mapped to this
+ <item>If a system has an "miscellaneous" or "other" value, it is better to map this to this
value even if the specific instance of the issue might be mapped to another
value.</item>
</list>
Received on Friday, 21 June 2013 17:38:29 UTC