- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Fri, 06 Sep 2013 20:50:12 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory gil:/tmp/cvs-serv4745/TR-version
Modified Files:
Overview.html
Log Message:
work on status section
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/08/19 12:55:36 1.116
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/09/06 20:50:12 1.117
@@ -5,16 +5,16 @@
</style><link rel="stylesheet" href="local.css" type="text/css"/><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css"/></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"/></a></p>
<h1><a name="title" id="title"></a>Internationalization Tag Set (ITS) Version 2.0</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Last Call Working Draft 20 August 2013</h2><dl><dt>This version:</dt><dd>
- <a href="http://www.w3.org/TR/2013/WD-its20-20130820/">
- http://www.w3.org/TR/2013/WD-its20-20130820/</a>
+<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Proposed Recommendation 17 September 2013</h2><dl><dt>This version:</dt><dd>
+ <a href="http://www.w3.org/TR/2013/PR-its20-20130917/">
+ http://www.w3.org/TR/2013/PR-its20-20130917/</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/its20/">http://www.w3.org/TR/its20/</a>
- </dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2013/WD-its20-20130521/">
- http://www.w3.org/TR/2013/WD-its20-20130521/</a></dd><dt>Editors:</dt><dd>David Filip, University of Limerick</dd><dd>Shaun McCance, Invited Expert</dd><dd>Dave Lewis, TCD</dd><dd>Christian Lieske, SAP AG</dd><dd>Arle Lommel, DFKI</dd><dd>Jirka Kosek, UEP</dd><dd>Felix Sasaki, DFKI / W3C Fellow</dd><dd>Yves Savourel, ENLASO</dd></dl><p>This document is also available in these non-normative formats: <a href="its20.odd">ODD/XML document</a>, <a href="itstagset20.zip">self-contained zipped archive</a>, and <a href="diffs/diff-wd20130820-wd20130521.html">XHTML Diff markup to previous publication
- 2013-05-21</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
-<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>The technology described in this document – the <em>Internationalization Tag Set (ITS)
- 2.0</em> – enhances the foundation to integrate automated processing of human language
+ </dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2013/WD-its20-20130820/">
+ http://www.w3.org/TR/2013/WD-its20-20130820/</a></dd><dt>Editors:</dt><dd>David Filip, University of Limerick</dd><dd>Shaun McCance, Invited Expert</dd><dd>Dave Lewis, TCD</dd><dd>Christian Lieske, SAP AG</dd><dd>Arle Lommel, DFKI</dd><dd>Jirka Kosek, UEP</dd><dd>Felix Sasaki, DFKI / W3C Fellow</dd><dd>Yves Savourel, ENLASO</dd></dl><p>This document is also available in these non-normative formats: <a href="its20.odd">ODD/XML document</a>, <a href="itstagset20.zip">self-contained zipped archive</a>, and <a href="diffs/diff-wd20130917-wd20130820.html">XHTML Diff markup to previous publication
+ 2013-08-20</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>The technology described in this document “<em>Internationalization Tag Set (ITS)
+ 2.0</em>“ enhances the foundation to integrate automated processing of human language
into core Web technologies. ITS 2.0 bears many commonalities with its predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</a> but provides additional
concepts that are designed to foster the automated creation and processing of multilingual
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
@@ -25,13 +25,20 @@
Other documents may supersede this document. A list of current W3C publications and the
latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em>
- </p><p>The technology described in this document – the <em>Internationalization Tag Set (ITS)
- 2.0</em> – enhances the foundation to integrate automated processing of human language
+ </p><p>The technology described in this document “<em>Internationalization Tag Set (ITS)
+ 2.0</em>“ enhances the foundation to integrate automated processing of human language
into core Web technologies. ITS 2.0 bears many commonalities with is predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</a> but provides additional
concepts that are designed to foster the automated creation and processing of multilingual
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
processing based on the XML Localization Interchange File Format (XLIFF), as well as the
- Natural Language Processing Interchange Format (NIF).</p><p>This document was published by the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working Group</a> as a Last Call Working Draft. The Last Call period ends 10 September 2013. The publication reflects changes made since the previous Last Call publication 21 May 2013. The Working Group expects to advance this document to Recommendation status (see <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document maturity levels</a>).</p><p>All <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html">last call issues</a> in the normative sections (from <a href="#notation-terminology">Section 3: Notation and Terminology</a> to <a href="#datacategory-description">Section 8: Description of Data Categories</a> and <a href="#normative-references">Appendix A: References</a> to <a href="#its-schemas">Appendix D: Schemas for ITS</a>) ave been resolved. As announced in the <a href="http://www.w3.org/TR/2013/WD-its20-20130521/#status">previous draft</a>, the other, non-normative sections have been updated with explanatory material. The Working Group encourages feedback until 10 September 2013.</p><p>One substantive change was made that requires a third last call draft: the <a href="#conversion-to-nif">conversion to NIF</a> was categorized as a non-normative feature (this was a <a href="http://www.w3.org/TR/2013/WD-its20-20130521/#conversion-to-nif">normative feature in the previous draft</a>). The working group encourages especially feedback on this change from the RDF community.</p><p>Since the ITS 2.0 test suite already has a high coverage for normative features of this specification, the Working Group expects to advance the specification directly to Proposed Recommendation status.</p><p>To give feedback send your comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Cmment on ITS 2.0 specification WD" in the subject line of your email. The <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/">archives for this list</a> are publicly available. See also <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues discussed within the Working Group</a> and the <a href="#changelog-since-20130521">list of changes</a> since the previous publication.</p><p>Publication as a Last Call Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/53116/status">public list of any patent disclosures</a> made in connection with the deliverabes of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p></div><div class="toc">
+ Natural Language Processing Interchange Format (NIF).</p><p>This document was published by the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
+ Group</a> as a Proposed Recommendation. Comments submitted against the <a href="http://www.w3.org/TR/2013/WD-its20-20130820/">previous Last Call specification</a> are consolidated in a <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-3rd-last-call.html">comment tracking document</a>. All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <a href="https://github.com/w3c/its-2.0-testsuite/">Test Suite</a> and created an <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</a> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
+ document to Recommendation status (see <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
+ maturity levels</a>).</p><p> The W3C Membership and other interested parties are invited to review the document and send comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
+ WD" in the subject line of your email. The <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/">archives
+ for this list</a> are publicly available. Advisory Committee Representatives should consult their <a href="https://www.w3.org/2002/09/wbs/myQuestionnaires">WBS questionnaires</a>. The deadline for review and comments is 15 October 2013. See also <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues discussed
+ within the Working Group</a> and the <a href="#changelog-since-20130820">list of
+ changes since the previous publication</a>.</p><p>Publication as a Proposed Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/53116/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-2004205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><div class="toc"><div class="toc1">1 <a href="#introduction">Introduction</a><div class="toc2">1.1 <a href="#overview">Overview</a></div>
<div class="toc2">1.2 <a href="#general-motiviation-for-ITS2.0">General motivation for going beyond ITS 1.0</a></div>
<div class="toc2">1.3 <a href="#usage-scenarios">Usage Scenarios</a></div>
@@ -75,9 +82,9 @@
<div class="toc3">5.2.2 <a href="#selection-local">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2530">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2515">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2778">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2763">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules">Link to External Rules</a></div>
@@ -158,9 +165,10 @@
<div class="toc1">E <a href="#informative-references">References</a> (Non-Normative)</div>
<div class="toc1">F <a href="#conversion-to-nif">Conversion to NIF</a> (Non-Normative)</div>
<div class="toc1">G <a href="#nif-backconversion">Conversion NIF2ITS</a> (Non-Normative)</div>
-<div class="toc1">H <a href="#list-of-elements-and-attributes">List of ITS 2.0 Global Elements and Local Attributes</a> (Non-Normative)</div>
-<div class="toc1">I <a href="#revisionlog">Revision Log</a> (Non-Normative)</div>
-<div class="toc1">J <a href="#acknowledgements">Acknowledgements</a> (Non-Normative)</div>
+<div class="toc1">H <a href="#localization-quality-guidance">Localization Quality Guidance</a> (Non-Normative)</div>
+<div class="toc1">I <a href="#list-of-elements-and-attributes">List of ITS 2.0 Global Elements and Local Attributes</a> (Non-Normative)</div>
+<div class="toc1">J <a href="#revisionlog">Revision Log</a> (Non-Normative)</div>
+<div class="toc1">K <a href="#acknowledgements">Acknowledgements</a> (Non-Normative)</div>
</div><hr/><div class="body"><div class="div1">
<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="introduction" id="introduction"></a>1 Introduction</h2><p>
<em>This section is informative.</em>
@@ -511,7 +519,7 @@
<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">examples/html5/EX-translate-html5-inline-global-1.html</a>]</p></div></div><div class="div3">
<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-its-local-markup" id="html5-its-local-markup"></a>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
- <a class="section-ref" href="#html5-local-attributes">Section 6.1: Mapping of Local Data Categories to HTML</a>. An informative table in <a class="section-ref" href="#list-of-elements-and-attributes">Appendix H: List of ITS 2.0 Global Elements and Local Attributes</a>
+ <a class="section-ref" href="#html5-local-attributes">Section 6.1: Mapping of Local Data Categories to HTML</a>. An informative table in <a class="section-ref" href="#list-of-elements-and-attributes">Appendix I: List of ITS 2.0 Global Elements and Local Attributes</a>
provides an overview of the mapping for all data categories.</p></div><div class="div3">
<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-existing-markup-versus-its" id="html5-existing-markup-versus-its"></a>2.5.3 HTML markup with ITS 2.0 counterparts</h4><p>There are four ITS 2.0 data categories, which have counterparts in HTML markup. In these cases, native HTML markup provides some information
in terms of ITS 2.0 data categories. For these data categories, ITS 2.0 defines the following:</p><ul><li><p>The <a href="#language-information">Language Information</a> data category has the HTML <code>lang</code>
@@ -520,7 +528,7 @@
take <a href="#selection-precedence">precedence</a> over language information conveyed via a global <code class="its-elem-markup">langRule</code>.</p></li><li><p>The <a href="#idvalue">Id Value</a> data category has the HTML or XHTML <code>id</code> attribute as counterpart.
This HTML attribute acts as local markup for the <a href="#idvalue">Id Value</a> data category in HTML and takes <a href="#selection-precedence">precedence</a> over
identifier information conveyed via a global <code class="its-elem-markup">idValueRule</code>.</p></li><li><p>The <a href="#elements-within-text">Elements within Text</a> data category has a set of HTML
- elements (the so-called <a href="http://www.w3.org/TR/html51/dom.html#phrasing-content-1">phrasing content</a>) as counterpart.
+ elements (the so-called <a href="http://www.w3.org/TR/2013/CR-html5-20130806/dom.html#phrasing-content-1">phrasing content</a>) as counterpart.
In the absence of an
<a href="#elements-within-text">Elements within Text</a> local attribute or global rules selecting the
element in question, most of the phrasing content elements are interpreted as
@@ -528,7 +536,7 @@
and <code class="its-elem-markup">textarea</code> are interpreted as <code>withinText="nested"</code>.</p></li><li><p id="translate-in-html5">The <a href="#trans-datacat">Translate</a> data category has a direct counterpart in
<a title="HTML5" href="#html5">[HTML5]</a>, namely the <a title="HTML5" href="#html5">[HTML5]</a>
<code>translate</code> attribute. ITS 2.0 does not define its own behavior for <a title="HTML5" href="#html5">[HTML5]</a>
- <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">the HTML5 definition</a>. That definition also applies to nodes selected via global rules. That is, a <code class="its-elem-markup">translateRule</code> like <code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-and-existing-HTML5-markup" id="EX-its-and-existing-HTML5-markup"></a>Example 9: The <a href="#language-information">Language Information</a>, <a href="#idvalue">Id Value</a>,
+ <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/2013/CR-html5-20130806/dom.html#the-translate-attribute">the HTML5 definition</a>. That definition also applies to nodes selected via global rules. That is, a <code class="its-elem-markup">translateRule</code> like <code><its:translateRule selector="//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-and-existing-HTML5-markup" id="EX-its-and-existing-HTML5-markup"></a>Example 9: The <a href="#language-information">Language Information</a>, <a href="#idvalue">Id Value</a>,
<a href="#elements-within-text">Elements within Text</a> and <a href="#trans-datacat">Translate</a>
ITS 2.0 data categories expressed by native HTML markup.</div><p>The <code>lang</code> attribute of the <code>html</code> element conveys the
<a href="#language-information">Language Information</a> value "en".
@@ -579,7 +587,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">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">Section 8: Description of Data Categories</a></p></li><li><p>schema language-specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1628" id="d0e1628"></a>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys information as
+ <a class="section-ref" href="#datacategory-description">Section 8: Description of Data Categories</a></p></li><li><p>schema language-specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1613" id="d0e1613"></a>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys information as
to whether a piece of content 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
@@ -775,7 +783,7 @@
elements</a> for each data category. Each rule element has a <code class="its-attr-markup">selector</code>
attribute and possibly other attributes. The <code class="its-attr-markup">selector</code> attribute contains an
absolute selector as defined in <a class="section-ref" href="#selectors">Section 5.3: Query Language of Selectors</a>.</p></li><li><p><a href="#selection-local">Locally in a document</a>: the selection is
- realized using ITS local attributes, which are attached to an element node, or the<code class="its-elem-markup">span</code> element. There is no additional <code class="its-attr-markup">selector</code>
+ realized using ITS local attributes, which are attached to an element node, or the <code class="its-elem-markup">span</code> element. There is no additional <code class="its-attr-markup">selector</code>
attribute. The default selection for each data category defines whether the selection
covers attributes and child elements. See <a class="section-ref" href="#datacategories-defaults-etc">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>.</p></li></ul><p>The two locations are described in detail below.</p><div class="div3">
<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="selection-global" id="selection-global"></a>5.2.1 Global, Rule-based Selection</h4><p>Global, rule-based selection is implemented using the <code class="its-elem-markup">rules</code> element. The
@@ -826,7 +834,7 @@
</pre></div><p>[Source file: <a href="examples/xml/EX-selection-local-1.xml">examples/xml/EX-selection-local-1.xml</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code class="its-attr-markup">dir</code> and <code class="its-attr-markup">translate</code> attributes are not listed in the
ITS attributes to be used in HTML. The reason is that these two attributes are
available in HTML natively, so there is no need to provide them as <code>its-</code>
- attributes. The definition of the two attributes in HTML is compatibly, that is it
+ attributes. The definition of the two attributes in HTML is compatible, that is it
provides the same values and interpretation, as the definition for the two data
categories <a href="#trans-datacat">Translate</a> and <a href="#directionality">Directionality</a>.</p></div></div></div><div class="div2">
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="selectors" id="selectors"></a>5.3 Query Language of Selectors</h3><div class="div3">
@@ -836,9 +844,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</p></div><div class="div3">
-<h4><a href="#contents"><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="d0e2530" id="d0e2530"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<h4><a href="#contents"><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="d0e2515" id="d0e2515"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2541" id="d0e2541"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an XPath expression
+<h5><a name="d0e2526" id="d0e2526"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an XPath expression
that starts with "<code>/</code>". That is, it <a href="#rfc-keywords">MUST</a> be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
AbsoluteLocationPath</a>s as described in <a href="#xpath">XPath 1.0</a>.
@@ -883,14 +891,14 @@
be used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-and-attributes">CSS selectors have no ability to point to
attributes.</p></div><p>CSS Selectors are identified by the value <code>css</code> in the
<code class="its-attr-markup">queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d0e2755" id="d0e2755"></a>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as a
+<h5><a name="d0e2740" id="d0e2740"></a>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors">[Selectors Level 3]</a>. Both simple
selectors and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2765" id="d0e2765"></a>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords">MUST</a> be interpreted as a
+<h5><a name="d0e2750" id="d0e2750"></a>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors">[Selectors Level 3]</a>. A selector is
not evaluated against the complete document tree but only against subtrees rooted at
nodes selected by the selector in the <code class="its-attr-markup">selector</code> attribute.</p></div></div><div class="div3">
-<h4><a href="#contents"><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="d0e2778" id="d0e2778"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional query
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2763" id="d0e2763"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional query
languages. For each additional query language the processor <a href="#rfc-keywords">MUST</a> define:</p><ul><li><p>the identifier of the query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating an absolute selector to a collection of nodes;</p></li><li><p>rules for evaluating a relative selector to a collection of nodes.</p></li></ul><p>Because future versions of this specification are likely to define additional query
languages, the following query language identifiers are reserved: <code>xpath</code>,
<code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
@@ -1079,7 +1087,7 @@
generated those data category annotations.</p><div class="note"><p class="prefix"><b>Note:</b></p><ul><li><p id="annotators-ref-usage-scenarios">Three cases of providing tool
information can be expected:</p><ol class="depth1"><li><p>information about tools used for creating or modifying the textual
content;</p></li><li><p>information about tools that do 1), but also create ITS annotations, see
- <a class="section-ref" href="#list-of-elements-and-attributes">Appendix H: List of ITS 2.0 Global Elements and Local Attributes</a>; </p></li><li><p>information about tools that don’t modify or create content, but just
+ <a class="section-ref" href="#list-of-elements-and-attributes">Appendix I: List of ITS 2.0 Global Elements and Local Attributes</a>; </p></li><li><p>information about tools that don’t modify or create content, but just
create ITS annotations.</p></li></ol><p>
<code class="its-attr-markup">annotatorsRef</code> is only meant to be used when actual ITS
annotation is involved, that is for 2) and 3). To express tool information related
@@ -1413,7 +1421,7 @@
global rules, or locally on an individual element. Handling of inheritance and interaction between elements and attributes is different for XML content versus <a title="HTML5" href="#html5">[HTML5]</a> content.</p><p>For XML: for elements, the data category
information <a href="#def-inheritance">inherits</a> to the textual content of
the element, <em>including</em> child elements, but <em>excluding</em>
- attributes. The default is that elements are translatable and attributes are not.</p><p id="html5-translate-handling">For HTML: The interpretation of the <code class="its-attr-markup">translate</code> attribute is given in <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">HTML5</a>. Nodes in an HTML document selected via a <a href="#translate-global">global rule</a> are also interpreted following <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">HTML5</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>As of writing, the default in <a title="HTML5" href="#html5">[HTML5]</a> is that elements are translatable, and that translatable attributes inherit from the respective elements. There is a pre-defined list of translatable attributes, for example <code>alt</code> or <code>title</code>.</p><p>Since the <a title="HTML5" href="#html5">[HTML5]</a> definition also applies to nodes selected via global rules, a <code class="its-elem-markup">translatRule</code> like
+ attributes. The default is that elements are translatable and attributes are not.</p><p id="html5-translate-handling">For HTML: The interpretation of the <code class="its-attr-markup">translate</code> attribute is given in <a href="http://www.w3.org/TR/2013/CR-html5-20130806/dom.html#the-translate-attribute">HTML5</a>. Nodes in an HTML document selected via a <a href="#translate-global">global rule</a> are also interpreted following <a href="http://www.w3.org/TR/2013/CR-html5-20130806/dom.html#the-translate-attribute">HTML5</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>As of writing, the default in <a title="HTML5" href="#html5">[HTML5]</a> is that elements are translatable, and that translatable attributes inherit from the respective elements. There is a pre-defined list of translatable attributes, for example <code>alt</code> or <code>title</code>.</p><p>Since the <a title="HTML5" href="#html5">[HTML5]</a> definition also applies to nodes selected via global rules, a <code lass="its-elem-markup">translateRule</code> like
<code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></div><p id="translate-global">GLOBAL: The <code class="its-elem-markup">translateRule</code> element contains the
following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors">absolute selector</a> that selects the nodes to which this
rule applies.</p></li><li><p>A required <code class="its-attr-markup">translate</code> attribute with the value
@@ -2618,35 +2626,14 @@
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="lqissue" id="lqissue"></a>8.16 Localization Quality Issue</h3><div class="div3">
<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="lqissue-definition" id="lqissue-definition"></a>8.16.1 Definition</h4><p>The <a href="#lqissue">Localization Quality Issue</a> data category is used to
express information related to localization quality assessment tasks. Such tasks can
- be conducted on the translation of some source text into a target language or on the
- source text itself where its quality may impact on the localization process.</p><p>This data category can be used in a number of ways, including the following example
- scenarios:</p><ul><li><p>An automatic quality checking tool flags a number of potential quality issues
- in an XML or HTML file and marks them up using ITS 2.0 markup. Other tools in the
- workflow then examine this markup and decide whether the file needs to be reviewed
- manually or passed on for further processing without a manual review
- stage.</p></li><li><p>A quality assessment process identifies a number of issues and adds the ITS
- markup to a rendered HTML preview of an XML file along with CSS styling that
- highlights these issues. The resulting HTML file is then sent back to the
- translator to assist his or her revision efforts.</p></li><li><p>A human reviewer working with a web-based tool adds quality markup, including
- comments and suggestions, to a localized text as part of the review process. A
- subsequent process examines this markup to ensure that changes were
- made.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="selecting-issues">What issues are considered in quality
- assessment tasks depends on the nature of the project and tools used. For more
- information on setting translation project specifications and determining quality
- expectations, implementers are encouraged to consult <a title="Translation projects – General guidance" href="#isots11669">[ISO/TS 11669:2002]</a>. Details about translation specifications are available at <a title="Structured Specifications and Translation Parameters" href="#structuredspecs">[Structured Specifications]</a>. While these documents do not directly
- address the definition of quality metrics, they provide useful guidance for
- implementers interested in determining which localization quality issue values
- are best for specific scenarios.</p></div><p>The data category defines five pieces of information:</p><a name="lqissueDefs" id="lqissueDefs"></a><table border="1" width="100%"><thead><tr><td>Information</td><td>Description</td><td>Value</td><td>Notes</td></tr></thead><tbody><tr><td>Type</td><td>A set of broad types of issues into which tool-specific issues can be
- categorized.</td><td>One of the values defined in <a href="#lqissue-typevalues">list of type
+ be conducted on the translation of some source content (such as a text or an image) into a target language or on the
+ source content itself where its quality may impact on the localization process.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Automated or manual quality assessment is one area of quality management for translation and localization. An example of existing quality assessment is in-country review (e.g., as part of a language acceptance test for software). An important part of quality assessment is the list of issue types that are being used. Very often, simple issue categories like "correct/incorrect" or "like/dislike" are inadequate; instead, more specific ones such as "terminology" or "grammar" are more helpful in identifying concrete reasons for quality problems and for obtaining a more objective picture of quality levels.</p><p>Non-normative terminology related to localization quality as used in this section is provided in <a class="section-ref" href="#localization-quality-guidance">Appendix H: Localization Quality Guidance</a>.</p></div><p>This data category can be used in a nmber of ways, including the following example
+ scenarios:</p><ul><li><p>A human reviewer working with a web-based tool adds quality markup manually in a text editor, including comments and suggestions, to localized content as part of the review process. A subsequent process examines this markup to ensure that changes were made.</p></li><li><p>A fully automatic quality checking tool flags a number of potential quality issues in an XML or HTML file and marks them up using ITS 2.0 markup. A human reviewer then uses another tool to examine this markup and decide whether the file needs to receive more extensive review or be passed on for further processing without a further manual review stage.</p></li><li><p>A quality assessment process identifies a number of issues and adds the ITS markup to a rendered HTML preview of an XML file along with CSS styling that highlights these issues. The resulting HTML file is then sent back to the translator to assist his or her revision efforts.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></><p id="selecting-issues">What issues should be considered in quality assessment tasks depends on the nature of the project and tools used. Further guidance is beyond the scope of this specification, but implementers may wish to consult the references cited in <a class="section-ref" href="#localization-quality-guidance">Appendix H: Localization Quality Guidance</a>.</p></div><p>The data category defines five pieces of information:</p><a name="lqissueDefs" id="lqissueDefs"></a><table border="1" width="100%"><thead><tr><td>Information</td><td>Description</td><td>Value</td><td>Notes</td></tr></thead><tbody><tr><td>Type</td><td>A classifier that groups similar issues into categories (for example to differentiate spelling errors from grammar errors).</td><td>One of the values defined in <a href="#lqissue-typevalues">list of type
values</a>.</td><td>ITS 2.0-compliant tools that use these types <a href="#rfc-keywords">MUST</a> map their internal values to these types. If the type of the issue
- is set to <code>uncategorized</code>, a comment <a href="#rfc-keywords">MUST</a> be specified as well.</td></tr><tr><td>Comment</td><td>A human-readable description of the quality issue.</td><td>Text</td><td/></tr><tr><td>Severity</td><td>A decimal value representing the severity of the issue, as defined by the
- model generating the metadata.</td><td>A rational number in the interval 0 to 100 (inclusive). The value follows the
+ is set to <code>uncategorized</code>, a comment <a href="#rfc-keywords">MUST</a> be specified as well.</td></tr><tr><td>Comment</td><td>A human-readable description of a specific instance of a quality issue.</td><td>Text</td><td>Comments can be used to explain an issue or provide guidance in addressing an issue. For example, a note about a Terminology issue might specify what term should be used.</td></tr><tr><td>Severity</td><td>A classifier for the seriousness of an issue. The seriousness depends on the Quality Model that is being applied. The Quality Model should be made explicit via the Profile Reference.</td><td>A rational number in the interval 0 to 100 (inclusive). The value follows the
<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#double">XML
Schema double data type</a> with the constraining facets <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#rf-minInclusive">minInclusive</a> set to 0 and <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#rf-maxInclusive">maxInclusive</a> set to 100. The higher values represent greater
- severity.</td><td>It is up to tools to map the values of this to their own system to this scale.
- If needed, the original value can be passed along using a custom namespace for
- XML, or a <code>data-</code> attribute for HTML.</td></tr><tr><td>Profile Reference</td><td>A reference to a document describing the quality assessment model used for the
- issue.</td><td>An IRI pointing to the reference document.</td><td>The use of resolvable IRI is strongly recommended as it provides a way for
+ severity.</td><td>It is up to tools to map the values allowed by ITS 2.0 to their own system’s scale. If needed, the original value can be passed along using a custom namespace for XML, or a <code>data-</code> attribute for HTML.</td></tr><tr><td>Profile Reference</td><td>A reference to a description of the quality assessment model (or a specific profile (customization/instantiation) of a model, where relevant) used for the issue.</td><td>An IRI pointing to the reference document.</td><td>The use of resolvable IRIs is strongly recommended as it provides a way for
human evaluators to learn more about the quality issues in use.</td></tr><tr><td>Enabled</td><td>A flag indicating whether the issue is enabled or not.</td><td>A value <code>yes</code> or <code>no</code>, with the default value being
<code>yes</code>.</td><td>This flag is used to activate or deactivate issues. There is no prescribed
behavior associated with activated or deactivated issues. One example of usage is
@@ -3165,7 +3152,7 @@
Languages</cite></a>, September 2009. Available at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>.</dd><dt class="label"><a name="html4" id="html4"/>HTML 4.01</dt><dd>Dave Raggett et al. <a href="http://www.w3.org/TR/1999/REC-html401-19991224/"><cite>HTML 4.01</cite></a>. W3C Recommendation 24 December 1999. Available at <a href="http://www.w3.org/TR/1999/REC-html401-19991224/">
http://www.w3.org/TR/1999/REC-html401-19991224/</a>. The latest version of <a href="http://www.w3.org/TR/html401/">HTML 4.01</a> is available at
- http://www.w3.org/TR/html401.</dd><dt class="label"><a name="html5" id="html5"/>HTML5</dt><dd>Robin Berjon et al. <a href="http://www.w3.org/TR/2012/CR-html5-20121217/"><cite>HTML5</cite></a>. W3C Candidate Recommendation 17 December 2012. Available at <a href="http://www.w3.org/TR/2012/CR-html5-20121217/">http://www.w3.org/TR/2012/CR-html5-20121217/</a>.
+ http://www.w3.org/TR/html401.</dd><dt class="label"><a name="html5" id="html5"/>HTML5</dt><dd>Robin Berjon et al. <a href="http://www.w3.org/TR/2013/CR-html5-20130806/"><cite>HTML5</cite></a>. W3C Candidate Recommendation 06 August 2013. Available at <a href="http://www.w3.org/TR/2013/CR-html5-20130806/">http://www.w3.org/TR/2013/CR-html5-20130806/</a>.
The latest version of <a href="http://www.w3.org/TR/html5/">HTML5</a> is available at
http://www.w3.org/TR/html5/.</dd><dt class="label"><a name="ianacharsets" id="ianacharsets"/>IANA Character Sets</dt><dd>
<a href="http://www.iana.org/assignments/character-sets"><cite>Character Sets</cite></a> Available at <a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>.</dd><dt class="label"><a name="qa-framework" id="qa-framework"/>QAFRAMEWORK</dt><dd>Karl Dubost, Lynne Rosental, Dominique
@@ -3248,16 +3235,15 @@
<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="lqissue-typevalues" id="lqissue-typevalues"></a>C Values for the Localization Quality Issue Type</h2><p>
<em>This section is normative.</em>
</p><p>The <code class="its-attr-markup">locQualityIssueType</code> attribute provides a basic level of interoperability
- between different localization quality assurance systems. It offers a list of high-level
- quality issue types common in automatic and human localization quality assessment. Tools
+ between different localization quality assurance tools. It offers a list of high-level
+ quality issue types common in fully automatic and manual localization quality assessment. Tools
can map their internal types to these types in order to exchange information about the
kinds of issues they identify and take appropriate action even if another tool does not
- know the specific issues identified by the generating tool.</p><p>The scope column in the following table identifies whether the issue type applies to the
- source text (“S”), target text (“T”) or both (“S or T”).</p><p>The values listed in the following table are allowed for <code class="its-attr-markup">locQualityIssueType</code>.
+ know the specific issues identified by the generating tool.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Note: The values of locQualityIssueType were derived from an early version of the QTLaunchPad project's Multidimensional Quality Metrics (MQM) framework. MQM is based on a careful analysis of existing translation quality assessment tools and models, such as the LISA QA Model, SAE J2450, and various commercial tools. The values represent common issue types found in those models and are designed to provide interoperability between models. Differences in granularity and in issue types may prevent full interoperability, but using the shared values will maximize interoperability where possible.</p></div><p>The scope column in the following table identifies whether the issue type applies to the
+ source content (“S”), target content (“T”) or both (“S or T”).</p><p>The values listed in the following table are allowed for <code class="its-attr-markup">locQualityIssueType</code>.
Ideally the values a tool implementing the data category produces for the attribute matches one
- of the values provided in this table and are as semantically accurate as possible. Tools are encouraged to
- map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-mappings">The <a href="http://www.w3.org/International/its/ig/">ITS Interest Group</a> maintains an
- <a href="http://www.w3.org/International/its/wiki/Localization_quality_types_mappings">informative mapping</a> 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></div><a name="lqissue-typevalues-table" id="lqissue-typevalues-table"></a><table border="1" width="100%"><thead><tr><td>Value</td><td>Description</td><td>Example</td><td>Scope</td><td>Notes</td></tr></thead><tbody><tr><td>
+ of the values provided in this table and are as semantically accurate as possible. For example, marking the phrase “These man is” as a <code>terminology</code> issue, rather than as a <code>grammar</code> issue would be semantically inaccurate. Tools are encouraged to
+ map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>For tools <em>generating</em> ITS 2.0 Localization Quality Issue markup, if one internal issue type can be categorized as multiple ITS 2.0 issue types, <em>the first applicable one from the following table should be used</em>. The list is ordered with more specific types first. For example, if a terminology database specifies that the term “USB memory stick” should be used instead of “USB pen drive” but the translated content has “Insert a USB pen drive into any available USB port”, <code>terminology</code> would be used instead of <code>mistranslation</code> because <code>terminology</code> occurs earlier in the list and is more specific than a (general) <code>mistranslation</code>. In the case where multiple separate issues must be marked on a single span (e.g., it contains both a <code>mistranslation<code> and a <code>grammar</code> issue), implementers may wish to use standoff annotation, as shown in <a href="#EX-locQualityIssue-local-2">Example 75</a> and <a href="#EX-locQualityIssue-html5-local-2">Example 76</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-mappings">The <a href="http://www.w3.org/International/its/ig/">ITS Interest Group</a> maintains informative <a href="http://www.w3.org/International/its/wiki/Localization_quality_types_mappings">mappings of tool-specific quality issue types and ITS 2.0 localization quality types</a>. The ITS IG Wiki provides information on how to update that list. 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 to implement the ITS 2.0 quality types natively.</p></div><a name="lqissue-typevalues-table" id="lqissue-typevalues-table"></a><table border="1" width="100%"><thead><tr><td>Value</td><td>Desription</td><td>Example</td><td>Scope</td><td>Notes</td></tr></thead><tbody><tr><td>
<code>terminology</code>
</td><td>An incorrect term or a term from the wrong domain was used or terms are used
inconsistently.</td><td>
@@ -3284,7 +3270,7 @@
<code>omission</code>
</td><td>Necessary text has been omitted from the localization or source.</td><td>
<ul><li><p>One or more segments found in the source that have been intended for translation are
- missing in the target.</p></li></ul>
+ missing in the target.</p></li><li><p>After an alignment, a verification tool flags the pairs of aligned segments where the target has no corresponding source because of incorrect segmentation or some alignment issue. In such case the 'omission' type may apply to the source entry.</p></li></ul>
</td><td>S or T</td><td>This value is not to be used for missing whitespace or formatting codes, but
instead has to be reserved for linguistic content.</td></tr><tr><td>
<code>untranslated</code>
@@ -3356,8 +3342,7 @@
<code>characters</code>
</td><td>The text contains characters that are garbled or incorrect or that are not used in
the language in which the content appears.</td><td>
- <ul><li><p>A text ought to have a '•' but instead has a '¥' sign.</p></li><li><p>A text translated into German systematically transforms 'ü', 'ö', and 'ä' to
- 'û', 'ô', and 'â'.</p></li><li><p>A Japanese text has been garbled and appears with Devanagari
+ <ul><li><p>A text ought to have a '•' but instead has a '¥' sign.</p></li><li><p>A German text erroneously uses û, ô, and â instead of the appropriate 'ü', 'ö', and 'ä'.</p></li><li><p>A Japanese text has been garbled and appears with Devanagari
characters.</p></li></ul>
</td><td>S or T</td><td>Characters ought to be used in cases of garbling or systematic use of
inappropriate characters, not for spelling issues where individual characters
@@ -3388,8 +3373,7 @@
</td><td>Numbers are inconsistent between source and target.</td><td>
<ul><li><p>A source text states that an object is 120 cm long, but the target text says
that it is 129 cm. long.</p></li></ul>
- </td><td>S or T</td><td>Some tools may correct for differences in units of measurement to reduce false
- positives.</td></tr><tr><td>
+ </td><td>S or T</td><td>Some tools may correct for differences in units of measurement to reduce false positives (e.g., a tool might adjust for differences in values between inches and centimeters to avoid flagging numbers that seem to be different but are in fact equivalent).</td></tr><tr><td>
<code>markup</code>
</td><td>There is an issue related to markup or a mismatch in markup between source and
target.</td><td>
@@ -3400,8 +3384,8 @@
that defines non-allowable content).</td><td>
<ul><li><p>The tool disallows the regular expression pattern ['"”’][\.,] but the
translated text contains "A leading “expert”, a political hack, claimed
- otherwise."</p></li></ul>
- </td><td>S or T</td><td/></tr><tr><td>
+ otherwise."</p></li><li><p>A tool uses a regular expression to ensure that the content of an element is an IRI and flags what appears to be a malformed IRI.</p></li></ul>
+ </td><td>S or T</td><td>Defining what is or is not an allowable pattern is up to the processing application and is beyond the scope of this specification. Best practice would be to use the Comment attribute to specify the pattern that led to the issue.</td></tr><tr><td>
<code>whitespace</code>
</td><td>There is a mismatch in whitespace between source and target content or the text
violates specific rules related to the use of whitespace.</td><td>
@@ -3422,13 +3406,8 @@
</td><td>S or T</td><td>What constitutes a "significant" difference in length is determined by the model
referred to in the <code class="its-attr-markup">locQualityIssueProfileRef</code>.</td></tr><tr><td>
<code>non-conformance</code>
- </td><td>The content is deemed to have a level of conformance to a reference corpus. The
- <code>non-conformance</code> type reflects the degree to which the text conforms to
- a reference corpus given an algorithm, which combines several classes of error type to
- produce an aggregate rating. Higher values reflect poorer conformance.</td><td>The sentence "The harbour connected which to printer is busy or configared not
- properly." would have poor conformance.</td><td>S or T</td><td>In a system that uses classification techniques the poor conformance is a function
- of the combined incorrect terminology, wrong spelling and bad grammar, or other
- features as determined by the system.</td></tr><tr><td>
+ </td><td>The content is deemed to show poor statistical conformance to a reference corpus. Higher severity values reflect poorer conformance.</td><td>The sentence "The harbour connected which to printer is busy or configared not
+ properly." would have poor conformance.</td><td>S or T</td><td>Non-conformance is determined through the use of multiple statistical measures of similarity to a corpus of known-good content. For example, in a system that uses classification techniques the poor conformance might be a function of combined incorrect terminology, wrong spelling and bad grammar, or other features as determined by the system.</td></tr><tr><td>
<code>uncategorized</code>
</td><td>The issue either has not been categorized or cannot be categorized.</td><td>
<ul><li><p>A new version of a tool returns information on an issue that has not been
@@ -3455,7 +3434,7 @@
while other issues cannot.</p></li><li><p>If a system has an "miscellaneous" or "other" value, it is better to map this to this
value even if the specific instance of the issue might be mapped to another
value.</p></li></ul>
- </td></tr></tbody></table></div><div class="div1">
+ </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>Note: <code>uncategorized</code> is used for issues that have not (yet) been categorized into a more specific value. For example, an automatic process might flag issues for attention but not provide any further detail or categorization: such issues would be listed as <code>uncategorized</code> in ITS 2.0. It may also be used when the exact nature of an issue is unclear and it cannot be categorized as a result (e.g., text is seriously garbled and the cause it unclear). By contrast other is used when the nature of an issue is clear but it cannot be categorized in one of the ITS 2.0 categories (or when a model or tool has its own “other” category). For example, in translation of subtitles there is a “respeaking” error category that does not correspond to any ITS 2.0 category and is highly specific to that environment; respeaking errors would therefore be categorized as <code>other</code> in ITS 2.0.</p><div></div><div class="div1">
<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="its-schemas" id="its-schemas"></a>D Schemas for ITS</h2><p>
<em>This section is normative.</em>
</p><p>The following schemas define ITS elements and attributes and can be used as building
@@ -5604,9 +5583,9 @@
</dd><dt class="label"><a name="nif-reference" id="nif-reference"/>NIF</dt><dd>Hellmann, S. et al. (ed.). <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#">NIF 2.0 Core Ontology</a>, as of August 2013. Available at <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#">http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#</a> under CC-BY 3.0 license maintained by the <a href="http://nlp2rdf.org">NLP2RDF project</a>.</dd><dt class="label"><a name="nvdl" id="nvdl"/>NVDL</dt><dd>Information technology – Document Schema Definition
Languages (DSDL) – Part 4: <cite>Namespace-based Validation Dispatching Language
(NVDL)</cite>. International Organization for Standardization (ISO) ISO/IEC
- 19757-4:2003.</dd><dt class="label"><a name="opendocument" id="opendocument"/>OpenDocument</dt><dd>Michael Brauer et al. <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office"><cite>OASIS Open Document Format for Office Applications (OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">
+ 19757-4:2003.</dd><dt class="label"><a name="opendocument" id="opendocument"/>OpenDocument</dt><dd>Michael Brauer et al. <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office"><cite>OASIS Open Document Format for Office Applications (OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>. The latest
- version of <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">
+ version of <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">
OpenDocument</a> is available at
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="prov-dm" id="prov-dm"/>PROV-DM</dt><dd>Moreau, Luc and Paolo Missier (eds.). <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">Provenance data model</a>.
W3C Recommendation 30 April 2013. Available at <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>.
@@ -5638,7 +5617,7 @@
<a href="http://www.xulplanet.com/"><cite>exTensible User Interface Language</cite></a>. Available at <a href="http://www.xulplanet.com/">
http://www.xulplanet.com/</a>.</dd></dl></div><div class="div1">
<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="conversion-to-nif" id="conversion-to-nif"></a>F Conversion to NIF (Non-Normative)</h2><p>This section provides an informative 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">[NIF]</a>. The conversion results in RDF triples.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP tool. It can
+ representations) that contain ITS metadata to the RDF format based on <a title="" href="#nif-reference">[NIF]</a>. The conversion results in RDF triples.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm creates URIs that in the query part contain the characters "[" and "]", as part of XPath expressions. In the conversion output (see an <a href="examples/nif/EX-nif-conversion-output.ttl">example</a>), The URIs are escaped as "%5B" and "%5D". For readability the URIs shown in this section do not escape these characters.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP tool. It can
produce a lot of "<span class="quote">phantom</span>" predicates from excessive whitespace, which 1)
increases the size of the intermediate mapping and 2) extracts this whitespace as
text, and therefore might decrease NLP performance. It is strongly recommended to
@@ -5657,13 +5636,13 @@
is in XML (the <code>mappings</code> element).</p></li></ul><div class="exampleInner"><div class="exampleOuter"><pre># Turtle example:
@prefix nif: <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#> .
@prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> .
-<http://example.com/exampledoc.html#char=b0,e0>
- nif:wasConvertedFrom <http://example.com/exampledoc.html#xpath(x0)> .
-<http://example.com/exampledoc.html#char=b1,e1>
- nif:wasConvertedFrom <http://example.com/exampledoc.html#xpath(x1)> .
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=b0,e0>
+ nif:wasConvertedFrom <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=x0> .
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=b1,e1>
+ nif:wasConvertedFrom <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=x1> .
# ...
-<http://example.com/exampledoc.html#char=bn,en>
- nif:wasConvertedFrom <http://example.com/exampledoc.html#xpath(xn)> .
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=bn,en>
+ nif:wasConvertedFrom <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=xn> .
<!-- XML Example -->
<mappings>
<mapping x="xpath(x0)" b="b0" e="e0" />
@@ -5682,29 +5661,29 @@
@prefix nif: <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#> .
@prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> .
# "Welcome to "
-<http://example.com/exampledoc.html#char=0,11>
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=0,11>
nif:wasConvertedFrom
- <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text()[1])>.
+ <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=/html/body[1]/h2[1]/text()[1]>.
# "Dublin"
-<http://example.com/exampledoc.html#char=11,17>
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=11,17>
nif:wasConvertedFrom
- <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/span[1]/text()[1])>.
+ <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=/html/body[1]/h2[1]/span[1]/text()[1]>.
# " in "
-<http://example.com/exampledoc.html#char=17,21>
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=17,21>
nif:wasConvertedFrom
- <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text()[2])> .
+ <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=/html/body[1]/h2[1]/text()[2]> .
# "Ireland"
-<http://example.com/exampledoc.html#char=21,28>
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=21,28>
nif:wasConvertedFrom
- <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/b[1]/text()[1])> .
+ <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=/html/body[1]/h2[1]/b[1]/text()[1]> .
# "!"
-<http://example.com/exampledoc.html#char=28,29>
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=28,29>
nif:wasConvertedFrom
- <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text()[3])> .
+ <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=/html/body[1]/h2[1]/text()[3]> .
# "Welcome to Dublin Ireland!"
-<http://example.com/exampledoc.html#char=0,29>
+<http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&char=0,29>
nif:wasConvertedFrom
- <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text())> .
+ <http://example.com/myitsservice?informat=html&intype=url&input=http://example.com/doc.html&xpath=/html/body[1]/h2[1]/text()> .
<!-- XML Example -->
<mappings>
<mapping x="xpath(/html/body[1]/h2[1]/text()[1])" b="0" e="11" />
[145 lines skipped]
Received on Friday, 6 September 2013 20:50:16 UTC