- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 24 Jun 2013 17:37:36 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv2074
Modified Files:
build.xml its20.html its20.odd
Added Files:
disposition-of-comments-2nd-last-call.html
Log Message:
various edits, see http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jun/0089.html
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/build.xml 2013/06/23 17:50:43 1.21
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/build.xml 2013/06/24 17:37:35 1.22
@@ -238,12 +238,6 @@
<target name="generate-tr-version" depends="validateOdd, odd2xmlspec, makeXmlspecValid, xmlspec2TrHtml">
<echo>GENERATION TR VERSION - DONE</echo>
</target>
-
- <!-- Below target is temporary for editing sec 1 and sec 2, with its20-for-editing-sec1-sec2.odd as the ODD file. -->
-
- <target name="generate-sec1-2" depends="validateOdd-sec1-sec2, odd2xmlspec-sec1-sec2, makeXmlspecValid, xmlspec2Html, copy2Edcopy-sec1-sec2">
- <echo>GENERATION SEC1 - SEC2 VERSION - DONE</echo>
- </target>
<target name="main" depends="generate-ed-copy"/>
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/24 14:11:00 1.468
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/24 17:37:35 1.469
@@ -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="#d0e2579" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2576" 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="#d0e2827" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2824" 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>
@@ -224,59 +224,59 @@
ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between
ITS markup and the various HTML flavors. Furthermore, ITS 2.0 suggests when and how to
leverage processing based on the XML Localization Interchange File Format (<a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>), as
- well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document are not intended for translation.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content has to be left untranslated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that are intended for translation and those that are not to be translated. Explicit metadata is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
- <strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><arguments></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></arguments></strong>
- <strong class="hl-tag" style="color: #000096"><variables></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Corporate Policy<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></variables></strong>
- <strong class="hl-tag" style="color: #000096"><keyvalue_pairs></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Page<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>ABC Corporation - Policy Repository<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Footer_Last<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Pages<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>bgColor<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>NavajoWhite<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>title<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>List of Available Policies<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
- <strong class="hl-tag" style="color: #000096"></section></strong>
-<strong class="hl-tag" style="color: #000096"></resources></strong>
+ well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document are not intended for translation.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content has to be left untranslated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that are intended for translation and those that are not to be translated. Explicit metadata is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
+ <strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><arguments></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></arguments></strong>
+ <strong class="hl-tag" style="color: #000096"><variables></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Corporate Policy<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></variables></strong>
+ <strong class="hl-tag" style="color: #000096"><keyvalue_pairs></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Page<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>ABC Corporation - Policy Repository<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Footer_Last<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Pages<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>bgColor<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>NavajoWhite<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>title<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>List of Available Policies<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
+ <strong class="hl-tag" style="color: #000096"></section></strong>
+<strong class="hl-tag" style="color: #000096"></resources></strong>
</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><p>ITS proposes several mechanisms, which differ among others in terms of the usage scenario/user types for which the mechanism is most suitable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-2" id="EX-motivation-its-2" shape="rect"/>Example 2: Document that uses two different ITS mechanisms to indicate that some parts have to be left untranslated.</div><p>ITS provides two mechanisms to explicitly associate metadata with one
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 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>
- <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">"//keyvalue_pairs/string[(position() mod 2)=1]"</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>
- <strong class="hl-tag" style="color: #000096"></its:rules></strong>
- <strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><arguments></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></arguments></strong>
- <strong class="hl-tag" style="color: #000096"><variables></strong>
- <strong class="hl-tag" style="color: #000096"><string</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Corporate Policy<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></variables></strong>
- <strong class="hl-tag" style="color: #000096"><keyvalue_pairs></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Page<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>ABC Corporation - Policy Repository<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Footer_Last<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Pages<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>bgColor<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">'no'</span><strong class="hl-tag" style="color: #000096">></strong>NavajoWhite<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>title<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>List of Available Policies<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
- <strong class="hl-tag" style="color: #000096"></section></strong>
-<strong class="hl-tag" style="color: #000096"></resources></strong>
+ 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>
+ <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">"//keyvalue_pairs/string[(position() mod 2)=1]"</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>
+ <strong class="hl-tag" style="color: #000096"></its:rules></strong>
+ <strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><arguments></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></arguments></strong>
+ <strong class="hl-tag" style="color: #000096"><variables></strong>
+ <strong class="hl-tag" style="color: #000096"><string</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Corporate Policy<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></variables></strong>
+ <strong class="hl-tag" style="color: #000096"><keyvalue_pairs></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Page<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>ABC Corporation - Policy Repository<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Footer_Last<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Pages<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>bgColor<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">'no'</span><strong class="hl-tag" style="color: #000096">></strong>NavajoWhite<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>title<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>List of Available Policies<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
+ <strong class="hl-tag" style="color: #000096"></section></strong>
+<strong class="hl-tag" style="color: #000096"></resources></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">examples/xml/EX-motivation-its-2.xml</a>]</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="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><p>The basics of ITS 1.0 are simple:</p><ol class="depth1"><li><p>Provide metadata (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global approach</a>) to associate metadata with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the metadata straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of metadata categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing metadata (e.g. terms aleady marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to
identify additional metadata categories for internationalization-related processes. The
@@ -362,7 +362,7 @@
measurement of the localization quality of a document or an item in a document.</p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a>: indicates the confidence that MT
systems provide about their translation. </p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a>: specifies the characters that
are permitted in a given piece of content.</p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a>: specifies the maximum storage size
- of a given piece of content.</p></li></ul><p>Most of the existing ITS 1.0 data categories are included new ones have been added. Modifications of existing ITS 1.0 data categories are summarized in <a class="section-ref" href="#high-level-differences-between-1.0-and-2.0" shape="rect">Section 1.4: High-level differences between ITS 1.0 and ITS 2.0</a>.</p></div><div class="div2">
+ of a given piece of content.</p></li></ul><p>Most of the existing ITS 1.0 data categories are included and new ones have been added. Modifications of existing ITS 1.0 data categories are summarized in <a class="section-ref" href="#high-level-differences-between-1.0-and-2.0" shape="rect">Section 1.4: High-level differences between ITS 1.0 and ITS 2.0</a>.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection" id="basic-concepts-selection" shape="rect"/>2.2 Selection</h3><p>Information (e.g. “translate this”) captured by an ITS data category always
pertains to one or more XML or HTML nodes, primarily element and attribute nodes. In a
sense, the relevant node(s) get “selected”. Selection may be explicit or implicit.
@@ -376,39 +376,39 @@
data models in RDF.</p><p>The following two examples provide more details about the distinction between the local
and global approach, using the <a href="#trans-datacat" shape="rect">Translate</a> data
category as an example.</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="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"/>2.2.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 3</a> shows how a content author can use the ITS <code class="its-attr-markup">translate</code> attribute to indicate that all content inside the <code>author</code> element is not intended for translation (i.e. has to be left untranslated). Translation tools that are aware of the meaning of the attribute can protect the relevant content from being translated (possibly still allowing translators to see the protected content as context information).</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 3: ITS markup on elements in an XML document (local approach) </iv><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
- <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> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"5.0"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><info></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>An example article<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"><author</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><personname></strong>
- <strong class="hl-tag" style="color: #000096"><firstname></strong>John<strong class="hl-tag" style="color: #000096"></firstname></strong>
- <strong class="hl-tag" style="color: #000096"><surname></strong>Doe<strong class="hl-tag" style="color: #000096"></surname></strong>
- <strong class="hl-tag" style="color: #000096"></personname></strong>
- <strong class="hl-tag" style="color: #000096"><affiliation></strong>
- <strong class="hl-tag" style="color: #000096"><address></strong><strong class="hl-tag" style="color: #000096"><email></strong>foo@example.com<strong class="hl-tag" style="color: #000096"></email></strong><strong class="hl-tag" style="color: #000096"></address></strong>
- <strong class="hl-tag" style="color: #000096"></affiliation></strong>
- <strong class="hl-tag" style="color: #000096"></author></strong>
- <strong class="hl-tag" style="color: #000096"></info></strong>
- <strong class="hl-tag" style="color: #000096"><para></strong>This is a short article.<strong class="hl-tag" style="color: #000096"></para></strong>
-<strong class="hl-tag" style="color: #000096"></article></strong>
+<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="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"/>2.2.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 3</a> shows how a content author can use the ITS <code class="its-attr-markup">translate</code> attribute to indicate that all content inside the <code>author</code> element is not intended for translation (i.e. has to be left untranslated). Translation tools that are aware of the meaning of the attribute can protect the relevant content from being translated (possibly still allowing translators to see the protected content as context information).</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 3: ITS markup on elements in an XML document (local approach) </iv><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
+ <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> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"5.0"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><info></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>An example article<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"><author</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><personname></strong>
+ <strong class="hl-tag" style="color: #000096"><firstname></strong>John<strong class="hl-tag" style="color: #000096"></firstname></strong>
+ <strong class="hl-tag" style="color: #000096"><surname></strong>Doe<strong class="hl-tag" style="color: #000096"></surname></strong>
+ <strong class="hl-tag" style="color: #000096"></personname></strong>
+ <strong class="hl-tag" style="color: #000096"><affiliation></strong>
+ <strong class="hl-tag" style="color: #000096"><address></strong><strong class="hl-tag" style="color: #000096"><email></strong>foo@example.com<strong class="hl-tag" style="color: #000096"></email></strong><strong class="hl-tag" style="color: #000096"></address></strong>
+ <strong class="hl-tag" style="color: #000096"></affiliation></strong>
+ <strong class="hl-tag" style="color: #000096"></author></strong>
+ <strong class="hl-tag" style="color: #000096"></info></strong>
+ <strong class="hl-tag" style="color: #000096"><para></strong>This is a short article.<strong class="hl-tag" style="color: #000096"></para></strong>
+<strong class="hl-tag" style="color: #000096"></article></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-1.xml" shape="rect">examples/xml/EX-basic-concepts-1.xml</a>]</p></div><p>For the local approach (and <a href="#EX-basic-concepts-1" shape="rect">Example 3</a>) to work for a whole markup vocabulary, a schema developer would need to add the <code class="its-attr-markup">translate</code> attribute to the schema as a common attribute or on all the relevant element definitions. The example indicates that <a href="#basic-concepts-overinher" shape="rect">inheritance</a> plays a part in identifying which content does have to be translated and which does not: Although only the <code>author</code> element is marked as “do not translate”, its descendants (<code>personname</code>, <code>firstname</code>, <code>surname</code>) are considered to be implicitly marked as well. Tools that process this content for translation need to implement the expected inheritance.</p><p id="local-approach-not-applicable-to-attributes">For XML content, the local pproach cannot be applied to a particular attribute. If ITS needs to be applied to a particular attribute, the global approach has to be used. The local approach applies to content of the current element and all its inherited nodes as described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>. For the <a href="#trans-datacat" shape="rect">Translate</a> data category used in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, this is different, see the explanation of the <a href="#translate-in-html5" shape="rect">HTML5 definition of Translate</a>.</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="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"/>2.2.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 4</a> shows a different approach to identifying non-translatable content, similar to that used with a <code>style</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>, but using an ITS-defined element called <code class="its-elem-markup">rules</code>. It works as follows: A document can contain a <code class="its-elem-markup">rules</code> element (placed where it does not impact the structure of the document, e.g., in a “head” section, or even outside of the document itself). The <code class="its-elem-markup">rules</code> elemnt contains one or more ITS children/rule elements (for example <code class="its-elem-markup">translateRule</code>). Each of these children elements contains a <code class="its-attr-markup">selector</code> attribute. As its name suggests, this attribute selects the node or nodes to which the corresponding ITS information pertains. The values of ITS <code class="its-attr-markup">selector</code> attributes are XPath absolute location paths (or CSS Selectors if queryLanguage is set to "css"). Via the <code class="its-elem-markup">param</code> element variables can be provided and used in selectors.
</p><p>Information for the handling of namespaces in XPath expressions is taken from namespace declarations
- <a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> in the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 4: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><prolog></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>Using ITS<strong class="hl-tag" style="color: #000096"></title></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:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//n:term"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:n</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span><strong class="hl-tag" style="color: #000096">/></strong>
- <strong class="hl-tag" style="color: #000096"></its:rules></strong>
- <strong class="hl-tag" style="color: #000096"></prolog></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>ITS defines <strong class="hl-tag" style="color: #000096"><term></strong>data category<strong class="hl-tag" style="color: #000096"></term></strong> as an abstract concept for a particular type of
- information for internationalization and localization of XML schemas and documents.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></myTopic></strong>
-
+ <a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> in the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 4: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><prolog></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>Using ITS<strong class="hl-tag" style="color: #000096"></title></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:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//n:term"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:n</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span><strong class="hl-tag" style="color: #000096">/></strong>
+ <strong class="hl-tag" style="color: #000096"></its:rules></strong>
+ <strong class="hl-tag" style="color: #000096"></prolog></strong>
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong>ITS defines <strong class="hl-tag" style="color: #000096"><term></strong>data category<strong class="hl-tag" style="color: #000096"></term></strong> as an abstract concept for a particular type of
+ information for internationalization and localization of XML schemas and documents.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
+<strong class="hl-tag" style="color: #000096"></myTopic></strong>
+
</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-2.xml" shape="rect">examples/xml/EX-basic-concepts-2.xml</a>]</p></div><p>For the global approach (and <a href="#EX-basic-concepts-2" shape="rect">Example 4</a>) to work, a schema developer may need to add a <code class="its-elem-markup">rules</code> element and associated markup to the schema. In some cases, global rules may be sufficient and other ITS markup (such as an <code class="its-attr-markup">translate</code> attribute on the elements and attributes) may not be needed in the schema. However, it is likely that authors may need the local approach from time to time to override the general rule.</p><p>For specification of the <a href="#trans-datacat" shape="rect">Translate</a> data category information, the contents of the <code class="its-elem-markup">translateRule</code> element would normally be designed by an information architect familiar with the document format and familiar with, or working with someone familiar with, the nees of localization/translation.</p><p>The global, rule-based approach has the following benefits:</p><ul><li><p>Content authors do not have to concern themselves with creating additional
markup or verifying that the markup was applied correctly. ITS data categories are
associated with sets of nodes (for example all <code>p</code> elements in an XML
@@ -418,25 +418,25 @@
<code>term</code> element in DITA)</p></li></ul><p>The commonality in both examples above is the markup <code>translate='no'</code>.
This piece of ITS markup can be interpreted as follows:</p><ul><li><p>it pertains to the <a href="#trans-datacat" shape="rect">Translate</a> data category </p></li><li><p>the attribute <code class="its-attr-markup">translate</code> holds a value of "no"</p></li></ul></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="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"/>2.3 Overriding, Inheritance and Defaults</h3><p>The power of the ITS selection mechanisms comes at a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a> and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a> have to be established.</p><p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 5</a> shows how inheritance
- and overriding work for the <a href="#trans-datacat" shape="rect">Translate</a> data category:</p><ul><li><p>The ITS default is that all elements are translatable.</p></li><li><p>The <code class="its-elem-markup">translateRule</code> element declared in the header overrides the default for the <code>head</code> element inside text and for all its children.</p></li><li><p>Because the <code>title</code> element is actually translatable, the global rule needs to be overridden by a local <code>its:translate="yes"</code>.</p></li><li><p>In the body of the document the default applies, and <code>its:translate="no"</code> is used to set "faux pas" as non-translatable.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 5: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F544C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><revision></strong>Sep-10-2006 v5<strong class="hl-tag" style="color: #000096"></revision></strong>
- <strong class="hl-tag" style="color: #000096"><author></strong>Ealasaidh McIan<strong class="hl-tag" style="color: #000096"></author></strong>
- <strong class="hl-tag" style="color: #000096"><contact></strong>ealasaidh@hogw.ac.uk<strong class="hl-tag" style="color: #000096"></contact></strong>
- <strong class="hl-tag" style="color: #000096"><title</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>The Origins of Modern Novel<strong class="hl-tag" style="color: #000096"></title></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">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"/text/head"</span><strong class="hl-tag" style="color: #000096">/></strong>
- <strong class="hl-tag" style="color: #000096"></its:rules></strong>
- <strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><div</strong> <span class="hl-attribute" style="color: #F5844C">xml:id</span>=<span class="hl-value" style="color: #993300">"intro"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>Introduction<strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>It would certainly be quite a <strong class="hl-tag" style="color: #000096"><span</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>faux pas<strong class="hl-tag" style="color: #000096"></span></strong> to start a
- dissertation on the origin of modern novel without mentioning the <strong class="hl-tag" style="color: #000096"><tl></strong>Epic of
- Gilgamesh<strong class="hl-tag" style="color: #000096"></tl></strong>...<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></div></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></text></strong>
+ and overriding work for the <a href="#trans-datacat" shape="rect">Translate</a> data category:</p><ul><li><p>The ITS default is that all elements are translatable.</p></li><li><p>The <code class="its-elem-markup">translateRule</code> element declared in the header overrides the default for the <code>head</code> element inside text and for all its children.</p></li><li><p>Because the <code>title</code> element is actually translatable, the global rule needs to be overridden by a local <code>its:translate="yes"</code>.</p></li><li><p>In the body of the document the default applies, and <code>its:translate="no"</code> is used to set "faux pas" as non-translatable.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 5: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F544C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><revision></strong>Sep-10-2006 v5<strong class="hl-tag" style="color: #000096"></revision></strong>
+ <strong class="hl-tag" style="color: #000096"><author></strong>Ealasaidh McIan<strong class="hl-tag" style="color: #000096"></author></strong>
+ <strong class="hl-tag" style="color: #000096"><contact></strong>ealasaidh@hogw.ac.uk<strong class="hl-tag" style="color: #000096"></contact></strong>
+ <strong class="hl-tag" style="color: #000096"><title</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>The Origins of Modern Novel<strong class="hl-tag" style="color: #000096"></title></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">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"/text/head"</span><strong class="hl-tag" style="color: #000096">/></strong>
+ <strong class="hl-tag" style="color: #000096"></its:rules></strong>
+ <strong class="hl-tag" style="color: #000096"></head></strong>
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><div</strong> <span class="hl-attribute" style="color: #F5844C">xml:id</span>=<span class="hl-value" style="color: #993300">"intro"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>Introduction<strong class="hl-tag" style="color: #000096"></head></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong>It would certainly be quite a <strong class="hl-tag" style="color: #000096"><span</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>faux pas<strong class="hl-tag" style="color: #000096"></span></strong> to start a
+ dissertation on the origin of modern novel without mentioning the <strong class="hl-tag" style="color: #000096"><tl></strong>Epic of
+ Gilgamesh<strong class="hl-tag" style="color: #000096"></tl></strong>...<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></div></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
+<strong class="hl-tag" style="color: #000096"></text></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-3.xml" shape="rect">examples/xml/EX-basic-concepts-3.xml</a>]</p></div><p>For XML content, <a href="#datacategories-overview" shape="rect">data category specific defaults</a> are provided. These are independent of the actual XML markup vocabulary. Example for the <a href="#trans-datacat" shape="rect">Translate</a> data category: <code>translate="yes"</code> for elements, and <code>translate="no"</code> for attributes.</p><p>For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence that HTML markup is normatively interpreted as ITS 2.0 data category information (see <a class="section-ref" href="#html5-existing-markup-versus-its" shape="rect">Section 2.5.3: HTML markup with ITS 2.0 counterparts</a> for more information).</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="basic-concepts-addingpointing" id="basic-concepts-addingpointing" shape="rect"/>2.4 Adding Information or Pointing to Existing Information</h3><p>Data categories can add information or point to information for the selected nodes. For example, the <a href="#locNote-datacat" shape="rect">Localization Note</a>
data category can add information to selected nodes (using a <code class="its-elem-markup">locNote</code> element),
@@ -454,40 +454,40 @@
The advantage is in being able to reuse the same rules file for many documents and also inline rules require secondary parsing
of the <code>script</code> element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 6: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
<code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
- the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
-<strong class="hl-tag" style="color: #000096"><html></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"><link</strong> <span class="hl-attribute" style="color: #F5844C">href</span>=<span class="hl-value" style="color: #993300">EX-translateRule-html5-1.xml</span> <span class="hl-attribute" style="color: #F5844C">rel</span>=<span class="hl-value" style="color: #993300">its-rules</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
- Of course there are always exceptions: certain code values should be translated,
- e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-global-1.html" shape="rect">examples/html5/EX-translate-html5-global-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1-rules-file" id="EX-translate-html5-global-1-rules-file" shape="rect"/>Example 7: ITS rules file linked from HTML</div><p>The rules file linked in <a href="#EX-translate-html5-global-1" shape="rect">Example 6</a>.</p><div class="exampleInner"><pre xml:space="preserve"><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> <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">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</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">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
-<strong class="hl-tag" style="color: #000096"></its:rules></strong>
+ the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"><link</strong> <span class="hl-attribute" style="color: #F5844C">href</span>=<span class="hl-value" style="color: #993300">EX-translateRule-html5-1.xml</span> <span class="hl-attribute" style="color: #F5844C">rel</span>=<span class="hl-value" style="color: #993300">its-rules</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"></head></strong>
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
+ Of course there are always exceptions: certain code values should be translated,
+ e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
+<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-global-1.html" shape="rect">examples/html5/EX-translate-html5-global-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1-rules-file" id="EX-translate-html5-global-1-rules-file" shape="rect"/>Example 7: ITS rules file linked from HTML</div><p>The rules file linked in <a href="#EX-translate-html5-global-1" shape="rect">Example 6</a>.</p><div class="exampleInner"><pre xml:space="preserve"><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> <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">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</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">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
+<strong class="hl-tag" style="color: #000096"></its:rules></strong>
</pre></div><p>[Source file: <a href="examples/html5/EX-translateRule-html5-1.xml" shape="rect">examples/html5/EX-translateRule-html5-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-inline-global-1" id="EX-translate-html5-inline-global-1" shape="rect"/>Example 8: Using ITS inline global rules in HTML</div><p>The <code>script</code> element contains the same rules as the external rules file
- <code>EX-translateRule-html5-1.xml</code> in <a href="#EX-translate-html5-global-1-rules-file" shape="rect">the above example</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
-<strong class="hl-tag" style="color: #000096"><html></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"><script</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">application/its+xml</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">ru1</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> <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">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</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">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
- <strong class="hl-tag" style="color: #000096"></its:rules></strong>
- <strong class="hl-tag" style="color: #000096"></script></strong>
- <strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
- Of course there are always exceptions: certain code values should be translated,
- e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
+ <code>EX-translateRule-html5-1.xml</code> in <a href="#EX-translate-html5-global-1-rules-file" shape="rect">the above example</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"><script</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">application/its+xml</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">ru1</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> <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">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</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">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
+ <strong class="hl-tag" style="color: #000096"></its:rules></strong>
+ <strong class="hl-tag" style="color: #000096"></script></strong>
+ <strong class="hl-tag" style="color: #000096"></head></strong>
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
+ Of course there are always exceptions: certain code values should be translated,
+ e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-inline-global-1.html" shape="rect">examples/html5/EX-translate-html5-inline-global-1.html</a>]</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="html5-its-local-markup" id="html5-its-local-markup" shape="rect"/>2.5.2 Local approach</h4><p>In HTML, an ITS 2.0 local data category is realized with the prefix <code>its-</code>.
The general mapping of the XML based ITS 2.0 attributes to their HTML counterparts is defined in
@@ -514,16 +514,16 @@
<a href="#language-information" shape="rect">Language Information</a> value "en".
The <code>id</code> attribute of the <code>p</code> element conveys the <a href="#idvalue" shape="rect">Id Value</a>
"p1". The elements <code>em</code> and <code>img</code> are interpreted to be <code>withinText="yes"</code>. The <code>p</code> element and its children are set to be non-translatable via an <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>
- <code>translate</code> attribute. Via inheritance, the <code>alt</code> attribute, normally translatable by default, also is non-translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
-<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">en</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>HTML native markup expressing three ITS 2.0 data categories<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"p1"</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>This is a <strong class="hl-tag" style="color: #000096"><em></strong>motherboard<strong class="hl-tag" style="color: #000096"></em></strong> and image: 
- <strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"http://example.com/myimg.png"</span> <span class="hl-attribute" style="color: #F5844C">alt</span>=<span class="hl-value" style="color: #993300">"My image"</span><strong class="hl-tag" style="color: #000096">/></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
+ <code>translate</code> attribute. Via inheritance, the <code>alt</code> attribute, normally translatable by default, also is non-translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">en</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>HTML native markup expressing three ITS 2.0 data categories<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"></head></strong>
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"p1"</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>This is a <strong class="hl-tag" style="color: #000096"><em></strong>motherboard<strong class="hl-tag" style="color: #000096"></em></strong> and image:
+ <strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"http://example.com/myimg.png"</span> <span class="hl-attribute" style="color: #F5844C">alt</span>=<span class="hl-value" style="color: #993300">"My image"</span><strong class="hl-tag" style="color: #000096">/></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-its-and-existing-HTML5-markup.html" shape="rect">examples/html5/EX-its-and-existing-HTML5-markup.html</a>]</p></div><p>There are also some HTML markup elements that have or can have similar, but not necessarily identical, roles and behaviors as certain ITS 2.0 data categories. For example, the HTML <code>dfn</code> element could be used to identify a term in the sense of the <a href="#terminology" shape="rect">Terminology</a> data category. However, this is not always the case and it depends on the intentions of the HTML content author. To accommodate this situation, users of ITS 2.0 are encouraged to specify the semantics of existing HTML markup in an ITS 2.0 context with a dedicated global rules file. For example, a rule can be used to define that the HTML <code>dfn</code> has the semantics of ITS <code>term="yes"</code>. For additional examples, see the <a href="http://www.w3.org/T/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml" shape="rect">XML I18N Best Practices</a> document.</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="html5-standoff-markup-explanation" id="html5-standoff-markup-explanation" shape="rect"/>2.5.4 Standoff markup in HTML5</h4><p>The <a href="#provenance" shape="rect">Provenance</a> and the <a href="#lqissue" shape="rect">Localization Quality Issue</a> data categories allow for using so-called standoff markup, see the XML <a href="#EX-provenance-global-1" shape="rect">Example 59</a>. In HTML such standoff markup is placed into a <code>script</code> element. If this is done, the constraints for <a href="#provenance-records-in-html5-constraint" shape="rect">Provenance standoff</a> markup in HTML and <a href="#loc-quality-issues-in-html5-constraint" shape="rect">Localization quality issue</a> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <a href="#EX-proveance-html5-local-2" shape="rect">Example 62</a> and <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 77</a>.</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="usage-in-legacy-html" id="usage-in-legacy-html" shape="rect"/>2.5.5 Version of HTML</h4><p>ITS 2.0 does not define how to use ITS in HTML versions prior to version 5. Users are
@@ -537,7 +537,7 @@
<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="mapping-NIF" id="mapping-NIF" shape="rect"/>2.7.1 ITS and RDF/NIF</h4><p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
representations) that contain ITS metadata to the RDF format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims at interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion from <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content-related triples and relies on an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The back conversion from <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively. One motivation for the back conversion is a roundtrip workflow like: 1) conversion to NIF 2) in NIF representation detection of named entities using NLP tools 3) back conversion to HTML and generation of <a href="#textanalysis" shape="rect"Text Analysis</a> markup. The outcome are HTML documents with linked information, see <a href="#EX-text-analysis-html5-local-1" shape="rect">Example 53</a>.</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="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>2.7.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localization and translation workflows. <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> is the successor of <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and under development. XLIFF has been widely implemented in various translation management systems, computer aided translation tools and in utilities for extracting translatable content from source documents and merging back the content in the target language..</p><p>The mapping between ITS and XLIFFtherefore unpins several important ITS 2.0 usage scenarios <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a>. These usage scenarios involve:</p><ul><li><p>the extraction of ITS metadata from a source language file into XLIFF</p></li><li><p>the addition of ITS metadata into an XLIFF file by translation tools</p></li><li><p>the mapping of ITS metadata in an XLIFF file into ITS metadata in the resulting target language files.</p></li></ul><p>ITS 2.0 has no normative dependency on XLIFF, however a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping" shape="rect">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/" shape="rect">Internationalization Tag Set Interest Group</a>.</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="implementing-its20" id="implementing-its20" shape="rect"/>2.8 ITS 2.0 Implementations and Conformance</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer (see <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a>). The clauses target different types of implementers:</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema" shape="rect">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS arkup</a> tell implementers how to process XML content according to ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html5-its" shape="rect">Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">ection 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> clarify how information needs to be made available for given pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <a href="@@@@" shape="rect">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually is to be used. This is due to the fact that there is a wide variety of usage scenarios for ITS 2.0, and a wide variety of tools for working with ITS 2.0 is possible. Each of these tools may have its own way of using ITS 2.0 data categories (see <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a for more information).</p><span class="editor-note">[Ed. note: Add link to test suite]</span></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="implementing-its20" id="implementing-its20" shape="rect"/>2.8 ITS 2.0 Implementations and Conformance</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer (see <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a>). The clauses target different types of implementers:</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema" shape="rect">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS arkup</a> tell implementers how to process XML content according to ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html5-its" shape="rect">Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">ection 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> clarify how information needs to be made available for given pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <a href="@@@@" shape="rect">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually is to be used. This is due to the fact that there is a wide variety of usage scenarios for ITS 2.0, and a wide variety of tools for working with ITS 2.0 is possible. Each of these tools may have its own way of using ITS 2.0 data categories (see <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a for more information).</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="notation-terminology" id="notation-terminology" shape="rect"/>3 Notation and Terminology</h2><p>
<em>This section is normative.</em>
</p><div class="div2">
@@ -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="d0e1613" id="d0e1613" 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="d0e1610" id="d0e1610" 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
@@ -582,15 +582,15 @@
pointer itself, not the object to which it points. Thus in the following example, the
translation information specified via the <code class="its-elem-markup">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="EX-notation-terminology-1" id="EX-notation-terminology-1" shape="rect"/>Example 11: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></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> 
- <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><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">translate</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//p/img/@src"</span><strong class="hl-tag" style="color: #000096">/></strong>
- <strong class="hl-tag" style="color: #000096"></its:rules></strong>
- ...
- <strong class="hl-tag" style="color: #000096"><p</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><strong class="hl-tag" style="color: #000096">></strong>As you can see in
- <strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"instructions.jpg"</span><strong class="hl-tag" style="color: #000096">/></strong>, the truth is not always out there.<strong class="hl-tag" style="color: #000096"></p></strong>
-<strong class="hl-tag" style="color: #000096"></text></strong>
+ graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-notation-terminology-1" id="EX-notation-terminology-1" shape="rect"/>Example 11: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></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>
+ <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><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">translate</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//p/img/@src"</span><strong class="hl-tag" style="color: #000096">/></strong>
+ <strong class="hl-tag" style="color: #000096"></its:rules></strong>
+ ...
+ <strong class="hl-tag" style="color: #000096"><p</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><strong class="hl-tag" style="color: #000096">></strong>As you can see in
+ <strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"instructions.jpg"</span><strong class="hl-tag" style="color: #000096">/></strong>, the truth is not always out there.<strong class="hl-tag" style="color: #000096"></p></strong>
+<strong class="hl-tag" style="color: #000096"></text></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-notation-terminology-1.xml" shape="rect">examples/xml/EX-notation-terminology-1.xml</a>]</p></div></div></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="def-local-attributes" id="def-local-attributes" shape="rect"/>3.4 ITS Local Attributes</h3><p>
[<a name="local-attributes" id="local-attributes" title="ITS Local Attributes" shape="rect">Definition</a>:
@@ -699,7 +699,7 @@
categories</a> they implement, and for each <a href="#def-datacat" shape="rect">data
category</a>, which type of selection they support, whether they support processing
of XML. If the implementation provides the conversion to NIF (see conformance clause
- <a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="http://tbd:update" shape="rect">ITS 2.0 test suite</a>. All
+ <a href="#its-conformance-2-4" shape="rect">2-4</a>), this <a href="#rfc-keywords" shape="rect">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="https://github.com/finnle/ITS-2.0-Testsuite/" shape="rect">ITS 2.0 test suite</a>. All
tests specify which data category is processed (clause <a href="#its-conformance-2-1" shape="rect">2-1</a>); they are relevant for
(clause <a href="#its-conformance-2-1-1" shape="rect">2-1-1</a>) global or local selection, or both; they require the processing of
defaults and precedence of selections (clauses <a href="#its-conformance-2-1-2" shape="rect">2-1-2</a> and
@@ -807,17 +807,17 @@
[6568 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/24 14:11:01 1.479
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/24 17:37:36 1.480
@@ -90,7 +90,7 @@
Natural Language Processing Interchange Format (NIF).</p>
<p>This document was published by the <loc
href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
- Group</loc> as a Proposed Recommendation Working Draft. Comments submitted against the <loc href="http://www.w3.org/TR/2013/WD-its20-20130521/">Last Call specification</loc> are consolidated in a <loc href="http://tinyurl.com/its20-comments-handling">comment tracking document</loc> (tbd:update link). All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <loc href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</loc> and created an <loc href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</loc> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
+ Group</loc> as a Proposed Recommendation Working Draft. Comments submitted against the <loc href="http://www.w3.org/TR/2013/WD-its20-20130521/">second Last Call specification</loc> are consolidated in a <loc href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html">comment tracking document</loc>. All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <loc href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</loc> and created an <loc href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</loc> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
document to Recommendation status (see <loc
href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
maturity levels</loc>).</p>
@@ -529,7 +529,7 @@
<item><ref target="#storagesize">Storage Size</ref>: specifies the maximum storage size
of a given piece of content.</item></list>
- <p>Most of the existing ITS 1.0 data categories are included new ones have been added. Modifications of existing ITS 1.0 data categories are summarized in <ptr target="#high-level-differences-between-1.0-and-2.0" type="specref"/>.</p>
+ <p>Most of the existing ITS 1.0 data categories are included and new ones have been added. Modifications of existing ITS 1.0 data categories are summarized in <ptr target="#high-level-differences-between-1.0-and-2.0" type="specref"/>.</p>
</div>
<div xml:id="basic-concepts-selection">
@@ -797,7 +797,6 @@
</list>
<p>The conformance clauses in <ptr target="#conformance-product-processing-expectations" type="specref"/> and <ptr type="specref" target="#conformance-product-html-processing-expectations"/> clarify how information needs to be made available for given pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <ref target="@@@@">ITS 2.0 test suite</ref>.</p>
<p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually is to be used. This is due to the fact that there is a wide variety of usage scenarios for ITS 2.0, and a wide variety of tools for working with ITS 2.0 is possible. Each of these tools may have its own way of using ITS 2.0 data categories (see <ptr type="bibref" target="#mlw-metadata-us-impl"/> for more information).</p>
- <note type="ed">Add link to test suite</note>
</div>
</div>
@@ -1082,7 +1081,7 @@
>MUST</ref> be stated.</p>
<note><p>The above conformance clauses are directly reflected in the <ref
- target="http://tbd:update">ITS 2.0 test suite</ref>. All
+ target="https://github.com/finnle/ITS-2.0-Testsuite/">ITS 2.0 test suite</ref>. All
tests specify which data category is processed (clause <ref target="#its-conformance-2-1">2-1</ref>); they are relevant for
(clause <ref target="#its-conformance-2-1-1">2-1-1</ref>) global or local selection, or both; they require the processing of
defaults and precedence of selections (clauses <ref target="#its-conformance-2-1-2">2-1-2</ref> and
@@ -5052,15 +5051,9 @@
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
+ <p xml:id="qa-issue-types-mappings">The <ref
target="http://www.w3.org/International/its/ig/">ITS Interest Group</ref> maintains an
- informative mapping of tools to localization quality issue types. <ref
- target="http://www.w3.org/International/its/wiki/Tool_specific_mappings">The ITS IG
- Wiki</ref> provides information on <ref
- target="http://www.w3.org/International/its/wiki/Tool_specific_mappings#Update_of_this_page"
- >how to update that list</ref>. 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
- and to implement the ITS 2.0 quality types natively.</p>
+ <ref target="http://www.w3.org/International/its/wiki/Localization_quality_types_mappings">informative mapping</ref> between ITS 2.0 quality issue types and other types used to specify quality issues: types produced by quality check tools, defined in other specifications etc. 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 and to implement the ITS 2.0 quality types natively.</p>
</note>
<table border="1" xml:id="lqissue-typevalues-table" width="100%">
<row role="head">
@@ -5994,7 +5987,9 @@
<item>Edits related to <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/128">issue-128</ref> (Various editorial edits + conformance section fixes).</item>
<item>Edits related to <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/129">issue-129</ref> (sec1-2 editing (non-normative sec)).</item>
<item>Fixes about <ptr target="#rfc2119" type="bibref"/> statements, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/actions/540">action-540</ref>.</item>
- <item>Various checks: spelling (using U.S. English), style, and grammar.</item>
+ <item>Various checks: spelling (using U.S. English), style, grammar, use of ":" etc.</item>
+ <item>Added a non-normative XML Schema for ITS 2.0 to <ptr target="#its-schemas" type="specref"/>, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/actions/546">action-546</ref>.</item>
+ <item>Updated link to quality issue type mappings in <ptr target="#lqissue-typevalues" type="specref"/>, see <ref target="https://www.w3.org/International/multilingualweb/lt/track/actions/543">action-543</ref>.</item>
</list>
<p xml:id="changelog-since-20130411">The following log records major changes that have been made to this document since the <ref target="http://www.w3.org/TR/2013/WD-its20-20130411/">ITS 2.0 Working Draft 11 April 2013</ref>:</p>
<list type="ordered">
@@ -6002,7 +5997,7 @@
<item>Updated <ptr target="#conversion-to-nif" type="specref"/> to reflect <ref target="http://www.w3.org/2013/05/08-mlw-lt-minutes#item04">MLW-LT May 2013 f2f discussion</ref>: <code>nif:occursIn</code> has changed to <code>nif:sourceUrl</code>, and <code>nif:convertedFrom</code> replaces <code>itsrdf:xpath2nif</code>. See <ref target="https://www.w3.org/International/multilingualweb/lt/track/actions/517">action-517</ref>.</item>
<item>Added <ref target="#local-approach-not-applicable-to-attributes">a note</ref> to <ptr target="#basic-concepts-selection-local" type="specref"/> expressing that local selection does not apply to attributes,
see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/98">issue-98</ref>.</item>
- <item>Added a <ref target="#qa-issue-types-tool-specific-mappings">clarification</ref> about the role of mappings from tools to quality issue types,
+ <item>Added a <ref target="#qa-issue-types-mappings">clarification</ref> about the role of mappings from tools to quality issue types,
see <ref target="https://www.w3.org/International/multilingualweb/lt/track/actions/493">action-493</ref>.</item>
<item>Updated the definition of the regular expression to use in the <ptr type="specref" target="#allowedchars"/> data category,
see <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/67">issue-67</ref>.</item>
@@ -6348,7 +6343,7 @@
<item>Added <ptr type="specref" target="#allowedchars"/>.</item>
<item>Added <ptr type="specref" target="#storagesize"/>.</item>
<item>Added <ptr type="specref" target="#mtconfidence"/>.</item>
- <item>Added <ref target="#qa-issue-types-tool-specific-mappings">a note</ref> about
+ <item>Added <ref target="#qa-issue-types-mappings">a note</ref> about
informative mappings of <ref target="#lqissue-typevalues">Values for the Localization
Quality Issue Type</ref> to the <ref
target="http://www.w3.org/International/its/wiki/Tool_specific_mappings">ITS IG
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html 2013/06/24 17:37:36 NONE
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html 2013/06/24 17:37:36 1.1
<?xml version="1.0" encoding="utf-8"?><!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>ITS 2.0 Disposition of Second Last Call Comments</title><style type="text/css"> table.overview tr {background: #ddd;} *.description {
border-width:1px; border-style:solid; border-color:blue; padding:2.5em;
text-align:justify; width: 100%; } table.issues-table {empty-cells: show;}
*.unknown {color: red;} *.duplicate { color: grey; text-decoration: line-through}</style></head>
<body>
<div class="head">
<h1>ITS 2.0 Disposition of Second Last Call Comments</h1>
<h2>Version: 2013-06-24</h2>
</div>
<h2>Abstract</h2>
<p>This document outlines the way in which the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working Group</a> addressed the comments submitted
during the <a href="http://www.w3.org/TR/2012/WD-its20-20121206/">ITS 2.0 Second Last Call</a> period,
starting 2013-05-21 and ending 2013-06-11. The document also includes comments received after 2013-06-11, but not comments received after 2013-05-24.
</p>
<p>Please send detailed comments on this document to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>.
</p>
<p>This document is based on an auto-generated with an <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/tools/xslt/disco-for-its20.xsl">XSLT stylesheet</a> based on the <a href="http://www.w3.org/2006/07/SWD/RDFa/disco">DisCo</a> tool, using <a href="http://www.w3.org/International/multilingualweb/lt/wiki/Comments_Handling#Tracker_handling">pre-defined keywords in tracker</a>.
</p>
<h2>Summary</h2>
<p>Total number of comments: 5.</p>
<p>Duplicates: 0.</p>
<table width="100%" class="overview">
<tr>
<td>-</td>
<td align="center">Reviewer satisfied</td>
<td align="center">Reviewer not satisfied</td>
<td align="center">No reply from reviewer</td>
<td align="center">No resolution yet</td>
</tr>
<tr>
<td>WG accepted comment</td>
<td align="center">4</td>
<td align="center">0</td>
<td align="center">1</td>
<td rowspan="2" align="center">0</td>
</tr>
<tr>
<td>WG rejected comment</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
</tr>
</table>
<h2>Issues list</h2>
<ul>
<li id="accepted-issues">Accepted issues: <a href="#issue-125">issue-125</a> <a href="#issue-126">issue-126</a> <a href="#issue-127">issue-127</a> <a href="#issue-128">issue-128</a> <a href="#issue-129">issue-129</a>
</li>
<li id="rejected-issues">Rejected issues: </li>
<li id="duplicates-issues">Duplicates: </li>
<li id="unresolved-issues">Unresolved issues: </li>
<li id="no-response-on-accepted-issues">No reponse from reviewer yet on accepted issues: <a href="#issue-129">issue-129</a>
</li>
<li id="no-response-on-rejected-issues">No reponse from reviewer yet on rejected issues: </li>
<li id="substantive-changes">Substantive changes: </li>
</ul>
<table cellpadding="5" border="2" class="issues-table" width="100%">
<tr>
<th>Issue</th>
<th>First recorded</th>
<th>Resolution<br />("accepted" or "rejected")
</th>
<th>Commenter feedback<br />("satisfied" or "unsatisfied")
</th>
<th>Change type<br />("editorial" or "substantive" or "none")
</th>
<th>Decision details</th>
</tr>
<tr>
<td><a href="https://www.w3.org/International/multilingualweb/lt/track/issues/125"
id="issue-125">issue-125</a>: NIF comments
</td>
<td>2013-05-26</td>
<td>accepted</td>
<td>satisfied
(<a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jun/0038.html">mail</a>)
</td>
<td>editorial</td>
<td> clarifying the NIF conversion with help from Sebastian Hellmann (main NIF developer)</td>
</tr>
<tr>
<td><a href="https://www.w3.org/International/multilingualweb/lt/track/issues/126"
id="issue-126">issue-126</a>: Minor issue with quality types listing
</td>
<td>2013-05-26</td>
<td>accepted</td>
<td>satisfied
(<a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013May/0253.html">mail</a>)
</td>
<td>editorial</td>
<td> editorial edit of quality types description</td>
</tr>
<tr>
<td><a href="https://www.w3.org/International/multilingualweb/lt/track/issues/127"
id="issue-127">issue-127</a>: Clarifying HTML5 transalte and global rules
</td>
<td>2013-06-03</td>
<td>accepted</td>
<td>satisfied
(<a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jun/0003.html">mail</a>)
</td>
<td>editorial</td>
<td> setting the right links to HTML5 "translate" definition</td>
</tr>
<tr>
<td><a href="https://www.w3.org/International/multilingualweb/lt/track/issues/128"
id="issue-128">issue-128</a>: Various editorial edits + conformance section fixes
</td>
<td>2013-06-13</td>
<td>accepted</td>
<td>satisfied
(<a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jun/0036.html">mail</a>)
</td>
<td>editorial</td>
<td> grammar etc. fixes for conformance clauses and other editorial edits</td>
</tr>
<tr>
<td><a href="https://www.w3.org/International/multilingualweb/lt/track/issues/129"
id="issue-129">issue-129</a>: sec1-2 editing (non-normative sec)
</td>
<td>2013-06-13</td>
<td>accepted</td>
<td><span class="unknown">unknown</span></td>
<td>editorial</td>
<td> re-writing the informative sections 1-2, as announced in the status section of the last call draft http://www.w3.org/TR/2013/WD-its20-20130521/#status</td>
</tr>
</table>
</body>
</html>
Received on Monday, 24 June 2013 17:37:41 UTC