- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Fri, 21 Jun 2013 16:54:47 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv10928
Modified Files:
its20.html
Added Files:
its20-before-rfc2199-check.html
Log Message:
added HTML before rfc 2119 check
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/18 21:29:14 1.463
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/21 16:54:47 1.464
@@ -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="#d0e2606" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2612" 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="#d0e2851" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2860" 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>
@@ -173,7 +173,7 @@
important
- that the original material should be suitable for
+ that the original material is suitable for
downstream
@@ -213,8 +213,8 @@
internationalization, translation, and localization. ITS 2.0 in particular contributes
to concepts in the realm of metadata for internationalization, translation, and
localization related to core Web technologies such as XML. ITS does for example assist
- in production scenarios in which parts of an XML-based document should not be
- translated. ITS 2.0 bears many commonalities with its predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a> but provides
+ in production scenarios, in which parts of an XML-based document are to be excluded
+ from translation. ITS 2.0 bears many commonalities with its predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a> but provides
additional concepts that are designed to foster enhanced automated processing – e.g.
based on language technology such as entity recognition – related to multilingual Web
content. </p><p> Like ITS 1.0, ITS 2.0 both identifies concepts (such as “Translate” ),
@@ -224,7 +224,7 @@
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 must not be translated.</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 must not be translated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that should be translated and those that must not 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>
+ 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>
@@ -246,12 +246,12 @@
<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 amongst 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 must not be translated.</div><p>ITS provides two mechanisms to explicitly associate metadata with one
+</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 amongst 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> must be translated; later, an ITS <code class="its-attr-markup">translate</code> attribute specifics that
- one of these elements must not 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>
+ <code>keyvalue_pairs</code> is intnded 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>
@@ -296,7 +296,7 @@
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="usage-scenarios" id="usage-scenarios" shape="rect"/>1.3 Usage Scenarios</h3><p>The <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a>
<a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “ITS is a technology to easily create XML which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multilingual production.</p><ul><li><p>Static mono-lingual (for example, the area of content authors): This part of the
content has the directionality “right-to-left”.</p></li><li><p>Dynamic multilingual: (for example, the area of machine translation systems): This
- part of the content must not be translated.</p></li></ul><p>Although ITS 1.0 made no assumptions about possible phases in a multilingual production
+ part of the content has to be left untranslated.</p></li></ul><p>Although ITS 1.0 made no assumptions about possible phases in a multilingual production
process chain, it was slanted towards a simple three phase
“write→internationalize→translate” model. Even a birds-eye-view at ITS 2.0 shows
that ITS 2.0 explicitly targets a much more comprehensive model for multilingual
@@ -324,7 +324,7 @@
<em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0.</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global" shape="rect">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors" shape="rect">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param" shape="rect">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has a <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="sectio-ref" href="#traceability" shape="rect">Section 2.6: Traceability</a> for details.</p></li></ul><p>
<em>Mappings:</em> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <a title="" href="#nif-reference" shape="rect">[NIF]</a> and links to guidance about how to relate ITS 2.0 to XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">Section 2.7: Mapping and conversion</a> for details.</p><p>
<em>Changes to the conformance section</em>: The <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed, and a conformance clause related to processing <a title="" href="#nif-reference" shape="rect">[NIF]</a> has been added. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, a dedicated conformance section has been created. Finally, a conformance clause related to Non-ITS elements and attributes has been added.</p></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.5 Extended implementation hints</h3><p id="unicode-normalization">As a general guidance, implementations of ITS 2.0 should use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</a>.</p></div></div><div class="div1">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.5 Extended implementation hints</h3><p id="unicode-normalization">As a general guidance, implementations of ITS 2.0 <a href="#rfc-keywords" shape="rect">SHOULD</a> use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</a>.</p></div></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts" id="basic-concepts" shape="rect"/>2 Basic Concepts</h2><p>
<em>This section is informative.</em>
</p><p>The purpose of this section is to provide basic knowledge about how ITS 2.0 works. Detailed knowledge (including formal definitions) is given in the subsequent sections.</p><div class="div2">
@@ -335,7 +335,7 @@
implementation is to enable different implementations with the following
characteristics:</p><ul><li><p>For various types of content (XML in general or <a href="#specific-HTML-support" shape="rect">HTML</a>).</p></li><li><p>For a single piece of content, e.g. a <code>p</code> element. This is the so-called <a href="#basic-concepts-selection-local" shape="rect">local approach</a>.</p></li><li><p>For several pieces of content in one document or even a set of documents. This is the
so-called <a href="#basic-concepts-selection-global" shape="rect">global approach</a>.</p></li><li><p>For a complete markup vocabulary. This is done by adding <a href="#its-schemas" shape="rect">ITS markup declarations</a> to the schema for the vocabulary.</p></li></ul><p>ITS 2.0 provides the following data categories, using most of the existing ITS 1.0 data categories and adding new ones. 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><ul><li><p><a href="#trans-datacat" shape="rect">Translate</a>: expresses information about whether
- a selected piece of content should be translated or not.</p></li><li><p><a href="#locNote-datacat" shape="rect">Localization Note</a>: communicates notes to
+ a selected piece of content is intended for translation or not.</p></li><li><p><a href="#locNote-datacat" shape="rect">Localization Note</a>: communicates notes to
localizers about a particular item of content.</p></li><li><p><a href="#terminology" shape="rect">Terminology</a>: marks terms and optionally
associates them with information, such as definitions or references to a term data
base.</p></li><li><p><a href="#directionality" shape="rect">Directionality</a>: specifies the base writing
@@ -355,7 +355,7 @@
corresponding target content (i.e. the source content translated into a given target
language). This is relevant for formats that hold the same content in different
languages inside a single document.</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>: identifies a value that can be used as
- unique identifier for a given part of the content. </p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a>: indicates how whitespace should
+ unique identifier for a given part of the content. </p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a>: indicates how whitespace is to
be handled in content.</p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a>: describes the nature and
severity of an error detected during a language-oriented quality assurance (QA)
process.</p></li><li><p><a href="#lqrating" shape="rect">Localization Quality Rating</a>: expresses an overall
@@ -376,7 +376,7 @@
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 may use the ITS <code class="its-attr-markup">translate</code> attribute to indicate that all content inside the <code>author</code> element should be protected from translation (i.e. must not be translated). 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>
+<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>
@@ -445,7 +445,7 @@
data categories allow the addition of information and which allow to point to existing
information.</p><p>Adding information and pointing to existing information are <em>mutually
exclusive</em>; attributes for adding information and attributes for pointing to the
- same information must not appear at the same rule element.</p></div><div class="div2">
+ same information <a href="#rfc-keywords" shape="rect">MUST NOT</a> appear at the same rule element.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="specific-HTML-support" id="specific-HTML-support" shape="rect"/>2.5 Specific HTML support</h3><p>For applying ITS 2.0 data categories to HTML, five aspects are of importance:</p><ol class="depth1"><li><p>Global approach in HTML5</p></li><li><p>Local Approach</p></li><li><p>HTML markup with ITS 2.0 counterparts</p></li><li><p>Standoff markup in HTML5</p></li><li><p>Version of HTML</p></li></ol><p>In the following sections these aspects are briefly discussed.</p><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-global-approach" id="html5-global-approach" shape="rect"/>2.5.1 Global approach in HTML5</h4><p>To account for the so-called <a href="#basic-concepts-selection-global" shape="rect">global
approach</a> in HTML, this specification (see <a class="section-ref" href="#html5-global-rules" shape="rect">Section 6.2: Global rules</a>) defines: </p><ul><li><p>A link type for referring to external files with global rules from a <code>link</code>
@@ -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 are targeted at 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 Expectationsfor ITS Markup</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" shap="rect">Section 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 should 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 U 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 are targeted at 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 Expectationsfor ITS Markup</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" shap="rect">Section 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 USIMPL]</a> for more information).</p><span class="editor-note">[Ed. note: Add link to test suite]</span></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,8 +559,8 @@
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="d0e1640" id="d0e1640" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
- to whether a piece of content should be translated or not.</p><p>The simplest formalization of this prose description on a schema language-independent
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language-specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1646" id="d0e1646" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
+ 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
level would be the declaration of the <code class="its-attr-markup">translate</code> attribute in,
@@ -570,7 +570,7 @@
[<a name="termdef-selection" id="termdef-selection" title="Selection" shape="rect">Definition</a>:
<span class="new-term">selection</span>
encompasses mechanisms to specify to what parts of an XML or HTML document an ITS data
- category and its values should be applied to.] Selection is discussed in
+ category and its values apply.] Selection is discussed in
detail in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. Selection can be applied
globally, see <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>, and locally, see <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.2: Local Selection in an XML Document</a>. As for global selection, ITS information
can be <a href="#def-adding-pointing" shape="rect">added</a> to the selected nodes, or it can
@@ -799,9 +799,9 @@
carrier for the local ITS attributes.</p><p>The data category determines what is being selected. The necessary data category
specific defaults are described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-local-1" id="EX-selection-local-1" shape="rect"/>Example 12: Defaults for various data categories</div><p>By default the content of all elements in a document is translatable. The attribute
<code>its:translate="no"</code> in the <code>head</code> element means that the
- content of this element, including child elements, should not be translated. The
+ content of this element, including child elements, is not intended for translation. The
attribute <code>its:translate="yes"</code> in the <code>title</code> element means
- that the content of this element, should be translated (overriding the
+ that the content of this element, is to be translated (overriding the
<code>its:translate="no"</code> in <code>head</code>). Attribute values of the
selected elements or their children are not affected by local <code class="its-attr-markup">translate</code> attributes. By default they are not translatable.</p><p>The default directionality of a document is left-to-right. The
<code>its:dir="rtl"</code> in the <code>quote</code> element means that the
@@ -831,10 +831,10 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2606" id="d0e2606" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2612" id="d0e2612" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2617" id="d0e2617" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
- that starts with "<code>/</code>". That is, it must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
+<h5><a name="d0e2623" id="d0e2623" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+ that starts with "<code>/</code>". That is, it <a href="#rfc-keywords" shape="rect">MUST</a> be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a>s as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
This ensures that the selection is not relative to a specific location. The
@@ -878,14 +878,14 @@
be used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-and-attributes">CSS selectors have no ability to point to
attributes.</p></div><p>CSS Selectors are identified by the value <code>css</code> in the
<code class="its-attr-markup">queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d0e2828" id="d0e2828" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2837" id="d0e2837" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Both simple
selectors and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2838" id="d0e2838" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2847" id="d0e2847" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. A selector is
not evaluated against the complete document tree but only against subtrees rooted at
nodes selected by the selector in the <code class="its-attr-markup">selector</code> attribute.</p></div></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2851" id="d0e2851" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2860" id="d0e2860" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
languages. For each additional query language the processor <a href="#rfc-keywords" shape="rect">MUST</a> define:</p><ul><li><p>the identifier of the query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating an absolute selector to a collection of nodes;</p></li><li><p>rules for evaluating a relative selector to a collection of nodes.</p></li></ul><p>Because future versions of this specification are likely to define additional query
languages, the following query language identifiers are reserved: <code>xpath</code>,
<code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
@@ -918,7 +918,7 @@
<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="link-external-rules" id="link-external-rules" shape="rect"/>5.4 Link to External Rules</h3><p>One way to associate a document with a set of external ITS rules is to use the optional
XLink <a title="XML Linking Language
 1.1" href="#xlink1" shape="rect">[XLink 1.1]</a>
<code class="its-attr-markup">href</code> attribute in the
- <code class="its-elem-markup">rules</code> element. The referenced document must be a valid XML document
+ <code class="its-elem-markup">rules</code> element. The referenced document <a href="#rfc-keywords" shape="rect">MUST</a> be a valid XML document
containing at most one <code class="its-elem-markup">rules</code> element. That <code class="its-elem-markup">rules</code> element can be the
root element or be located anywhere within the document tree (for example, the document
could be an XML Schema).</p><p>The rules contained in the referenced document <a href="#rfc-keywords" shape="rect">MUST</a>
@@ -996,12 +996,11 @@
all information provided via lower precedence is overriden by the higher precedence.
E.g. defaults are overridden by inherited values and these are overriden by nodes
selected via global rules, which are in turn overridden by local markup.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-precedence-1" id="EX-selection-precedence-1" shape="rect"/>Example 20: Conflicts between selections of ITS information resolved using the precedence
- order</div><p>The two elements <code>title</code> and <code>author</code> of this document should
- be treated as separate content when inside a <code>prolog</code> element, but in other
+ order</div><p>The two elements <code>title</code> and <code>author</code> of this document are intended as separate content when inside a <code>prolog</code> element, but in other
contexts as part of the content of their parent element. In order to make this
distinction two <code class="its-elem-markup">withinTextRule</code> elements are used:</p><p>The first rule specifies that <code>title</code> and <code>author</code> in general
- should be treated as an element within text. This overrides the default.</p><p>The second rule indicates that when <code>title</code> or <code>author</code> are
- found in a <code>prolog</code> element their content should be treated separately.
+ are to be treated as an element within text. This overrides the default.</p><p>The second rule indicates that when <code>title</code> or <code>author</code> are
+ found in a <code>prolog</code> element their content is to be treated separately.
This is normally the default, but the rule is needed to override the first rule.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><prolog></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>
@@ -1188,19 +1187,19 @@
<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
only to the creation or modification of textual content and independent of ITS
- data categories, that is case 1), one should use the tool or <code class="its-attr-markup">toolRef</code>
+ data categories, that is case 1), the tool or <code class="its-attr-markup">toolRef</code>
attribute provided by the <a href="#provenance" shape="rect">Provenance</a> data
- category.</p></li><li><p>An example of case 2) is an MT engine that modifies content and creates ITS
+ category is to be used.</p></li><li><p>An example of case 2) is an MT engine that modifies content and creates ITS
<a href="#mtconfidence" shape="rect">MT Confidence</a> annotations. Here the situation
may occur that several tools are involved in creating MT Confidence annotations:
the MT engine and the tool inserting the markup. The annotatorsRef attribute
- should identify the tool most useful in further processes, in this case the MT
+ is to identify the tool most useful in further processes, in this case the MT
engine.</p></li></ul></div><p>The value of <code class="its-attr-markup">annotatorsRef</code> is a space-separated list of references where
each reference is composed of two parts: a data category identifier and an IRI. These
two parts are separated by a <code>|</code> VERTICAL LINE (U+007C) character.</p><ul><li><p>The data category identifier <a href="#rfc2119" shape="rect">MUST</a> be one of the
identifiers specified in the <a href="#datacategories-overview" shape="rect">data category
overview table</a>.</p></li><li><p>The IRI indicates information about the processor used to generate the data category annotation.
- No single means is specified for how this IRI should be used to indicate processor
+ No single means is specified for how this IRI has to be used to indicate processor
information. Possible mechanisms are: to encode information directly in the IRI,
e.g., as parameters; to reference an external resource that provides such
information, e.g. an XML file or an RDF declaration; or to reference another part of
@@ -1295,7 +1294,7 @@
easier selection mechanism, they can switch query language to CSS selectors by using
the <code class="its-attr-markup">queryLanguage</code> attribute, see <a class="section-ref" href="#queryLanguage" shape="rect">Section 5.3.1: Choosing Query Language</a>.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The HTML5 parsing algorithm automatically puts all HTML elements into the XHTML
namespace (<code>http://www.w3.org/1999/xhtml</code>). Selectors used in global rules
- must take this into account.</p></div><p id="html5-external-global-rules">Linking to external global rules is specified in
+ <a href="#rfc-keywords" shape="rect">MUST</a> take this into account.</p></div><p id="html5-external-global-rules">Linking to external global rules is specified in
the <code class="its-attr-markup">href</code> attribute of <code>link</code> elements, with the link relation
<code>its-rules</code>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Using XPath in global rules linked from HTML documents does not create an additional
burden to implementers. Parsing HTML content produces a DOM tree that can be directly
@@ -1506,7 +1505,7 @@
textual content.</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="trans-datacat" id="trans-datacat" shape="rect"/>8.2 Translate</h3><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="translatability-definition" id="translatability-definition" shape="rect"/>8.2.1 Definition</h4><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category expresses information
- about whether the content of an element or attribute should be translated or not. The
+ about whether the content of an element or attribute is intended for translation or not. The
values of this data category are "yes" (translatable) or "no" (not
translatable).</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="translatability-implementation" id="translatability-implementation" shape="rect"/>8.2.2 Implementation</h4><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category can be expressed with
@@ -1519,7 +1518,7 @@
rule applies.</p></li><li><p>A required <code class="its-attr-markup">translate</code> attribute with the value
"yes" or "no".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-1" id="EX-translate-selector-1" shape="rect"/>Example 28: The <a href="#trans-datacat" shape="rect">Translate</a> data category expressed
globally</div><p>The <code class="its-elem-markup">translateRule</code> element specifies that the elements <code>code</code>
- must not be translated.</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><strong class="hl-tag" style="color: #000096">></strong>
+ is not to be translated.</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><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">"//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/xml/EX-translate-selector-1.xml" shape="rect">examples/xml/EX-translate-selector-1.xml</a>]</p></div><p id="translate-local">LOCAL: The following local markup is available for the <a href="#trans-datacat" shape="rect">Translate</a> data category:</p><ul><li><p>A <code class="its-attr-markup">translate</code> attribute with the value "yes" or
@@ -1529,15 +1528,15 @@
data category settings of attributes using local markup. This limitation is
consistent with the advised practice of not using translatable attributes. If
attributes need to be translatable, then
- this must be declared globally. Note that this restriciption does not apply to <a href="#html5-translate-handling" shape="rect">HTML5</a>.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-2" id="EX-translate-selector-2" shape="rect"/>Example 29: The <a href="#trans-datacat" shape="rect">Translate</a> data category expressed
+ this has to be declared globally. Note that this restriciption does not apply to <a href="#html5-translate-handling" shape="rect">HTML5</a>.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-2" id="EX-translate-selector-2" shape="rect"/>Example 29: The <a href="#trans-datacat" shape="rect">Translate</a> data category expressed
locally</div><p>The local <code>its:translate="no"</code> specifies that the content of
- <code>panelmsg</code> must not be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><messages</strong> <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">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>
+ <code>panelmsg</code> is not to be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><messages</strong> <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">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"><msg</strong> <span class="hl-attribute" style="color: #F5844C">num</span>=<span class="hl-value" style="color: #993300">"123"</span><strong class="hl-tag" style="color: #000096">></strong>Click Resume Button on Status Display or <strong class="hl-tag" style="color: #000096"><panelmsg</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>CONTINUE<strong class="hl-tag" style="color: #000096"></panelmsg></strong> Button on printer panel<strong class="hl-tag" style="color: #000096"></msg></strong>
<strong class="hl-tag" style="color: #000096"></messages></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-translate-selector-2.xml" shape="rect">examples/xml/EX-translate-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5" id="EX-translate-html5" shape="rect"/>Example 30: The <a href="#trans-datacat" shape="rect">Translate</a> data category expressed locally
in HTML</div><p>The local <code>translate="no"</code> attribute specifies that the content of
- <code>span</code> must not be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+ <code>span</code> is not to be translated.</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>
@@ -1555,7 +1554,7 @@
to:</p><ul><li><p>Tell the translator how to translate parts of the content</p></li><li><p>Expand on the meaning or contextual usage of a specific element, such as what a
variable refers to or how a string will be used in the user interface</p></li><li><p>Clarify ambiguity and show relationships between items sufficiently to allow
correct translation (e.g., in many languages it is impossible to translate the word"<span class="quote">enabled</span>" in isolation without knowing the gender, number, and case
- of the thing it refers to.)</p></li><li><p>Indicate why a piece of text is emphasized (important, sarcastic, etc.)</p></li></ul><p>Two types of informative notes are needed:</p><ul><li><p>An alert contains information that the translator must read before translating a
+ of the thing it refers to.)</p></li><li><p>Indicate why a piece of text is emphasized (important, sarcastic, etc.)</p></li></ul><p>Two types of informative notes are needed:</p><ul><li><p>An alert contains information that the translator has to read before translating a
piece of text. Example: an instruction to the translator to leave parts of the text
in the source language.</p></li><li><p>A description provides useful background information that the translator will
refer to only if they wish. Example: a clarification of ambiguity in the source
@@ -1568,8 +1567,7 @@
content of the element, <em>including</em> child elements, but
<em>excluding</em> attributes.</p><p id="localizationnote-global">GLOBAL: The <code class="its-elem-markup">locNoteRule</code> element contains
the following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors" shape="rect">absolute selector</a> that selects the nodes to which this
- rule applies.</p></li><li><p>A required <code class="its-attr-markup">locNoteType</code> attribute with the value
- "description" or "alert".</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code class="its-elem-markup">locNote</code> element that contains the note itself and allows for <a href="#selection-local" shape="rect">local ITS markup</a>.</p></li><li><p>A <code class="its-attr-markup">locNotePointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a> pointing to a node that holds the
+ rule applies.</p></li><li><p>A required <code class="its-attr-markup">locNoteType</code> attribute with the value"description" or "alert".</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code class="its-elem-markup">locNote</code> element that contains the note itself and allows for <a href="#selection-local" shape="rect">local ITS markup</a>.</p></li><li><p>A <code class="its-attr-markup">locNotePointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a> pointing to a node that holds the
localization note.</p></li><li><p>A <code class="its-attr-markup">locNoteRef</code> attribute that contains an IRI referring to the
location of the localization note.</p></li><li><p>A <code class="its-attr-markup">locNoteRefPointer</code> attribute that contains a <a href="#selectors" shape="rect">relative selector</a> pointing to a node that holds the
IRI referring to the location of the localization note.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locNote-element-1" id="EX-locNote-element-1" shape="rect"/>Example 31: The <code class="its-elem-markup">locNote</code> element</div><p>The <code class="its-elem-markup">locNoteRule</code> element associates the content of the <code class="its-elem-markup">locNote</code>
@@ -1928,8 +1926,8 @@
<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="domain-definition" id="domain-definition" shape="rect"/>8.8.1 Definition</h4><p>The <a href="#domain" shape="rect">Domain</a> data category is used to identify the topic or
subject of content. Such information allows for more relevant linguistic choices
during various processes.</p><p>Examples of usage include:</p><ul><li><p>Allowing machine translation systems to select the most appropriate engine and
- rules to translate the content.</p></li><li><p>Providing a general indication of what terminology collection should be used by
- a translator.</p></li></ul><p>This data category addresses various challenges:</p><ul><li><p>Often domain-related information already exist in the document (e.g., keywords
+ rules to translate the content.</p></li><li><p>Providing a general indication of what terminology collection is most suitable for use by
+ translators.</p></li></ul><p>This data category addresses various challenges:</p><ul><li><p>Often domain-related information already exist in the document (e.g., keywords
in the HTML <code>meta</code> element). The <a href="#domain" shape="rect">Domain</a> data
category provides a mechanism to point to this information.</p></li><li><p>There are many flat or structured lists of domain related values, keywords, key
phrases, classification codes, ontologies, etc. The <a href="#domain" shape="rect">Domain</a> data category does not propose its own given list. Instead it
@@ -2006,10 +2004,10 @@
"dcterms.subject" can be used. The usage of both "keywords" and
"dcterms.subject" is shown in example <a href="#EX-domain-2" shape="rect">Example 52</a>.</p><p>In the area of machine translation (e.g., machine translation systems or systems
harvesting content for machine translation training), there is no agreed upon set of
- value sets for domain. Nevertheless it is recommended to use a small set of values
+ value sets for domain. Nevertheless, it is recommended to use a small set of values
both in source content and within consumer tools, to foster interoperability. If
larger value sets are needed (e.g., detailed terms in the law or medical domain),
- mappings to the smaller value set needed for interoperability should be provided. An
+ mappings to the smaller value set needed for interoperability is to be provided. An
example would be a <code class="its-attr-markup">domainMapping</code> attribute for generalizing the law
domain: <code>domainMapping="'criminal law' law, 'property law' law, 'contract law'
law"</code>. </p><p>It is possible to have more than one domain associated with a piece of content. For
@@ -2078,8 +2076,7 @@
of London')</p></li></ul></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="text-analysis-unique-annotation"> A given document fragment can only be annotated
once. When support for multiple annotations is necessary (e.g., when all three of
the annotations in the extended example above need to be accommodated) NIF 2.0, <a href="http://www.tei-c.org/release/doc/tei-p5-doc/en/html/NH.html#NHSO" shape="rect">TEI
- Stand-off Markup</a>, or other so-called stand-off annotation mechanisms should
- be considered.</p><p>Some external resources such as DBpedia also provide information for some ontological concepts and named entity definitions in multiple languages, and this facilitates translation even more because a possible link traversal would allow a direct access to foreign language labels for named entities.</p></div></div><div class="div3">
+ Stand-off Markup</a>, or other so-called stand-off annotation mechanisms is better suitable.</p><p>Some external resources such as DBpedia also provide information for some ontological concepts and named entity definitions in multiple languages, and this facilitates translation even more because a possible link traversal would allow a direct access to foreign language labels for named entities.</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="textanalysis-implementation" id="textanalysis-implementation" shape="rect"/>8.9.2 Implementation</h4><p>
The
<a href="#textanalysis" shape="rect">Text Analysis</a>
@@ -2393,7 +2390,7 @@
implements the <a href="#provenanceDefs" shape="rect">tool-related revision
provenance information</a>.</p></li><li><p>A <code class="its-attr-markup">provRef</code> attribute that implements the <a href="#provenanceDefs" shape="rect">reference to external provenance
descriptions</a>.</p></li></ul></li></ul></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="provenanceRecord-order">The order of <code class="its-elem-markup">provenanceRecord</code> elements
- within a <code class="its-elem-markup">provenanceRecords</code> element should reflect the order with which
+ within a <code class="its-elem-markup">provenanceRecords</code> element <a href="#rfc-keywords" shape="rect">SHOULD</a> reflect the order with which
they were added to the document, with the most recently added one listed
first.</p></div><p>When the attributes <code class="its-attr-markup">person</code>, <code class="its-attr-markup">personRef</code>, <code class="its-attr-markup">org</code>,
<code class="its-attr-markup">orgRef</code>, <code class="its-attr-markup">tool</code>, <code class="its-attr-markup">toolRef</code>, <code class="its-attr-markup">revPerson</code>,
@@ -2573,7 +2570,7 @@
only with global rules. There is no inheritance. There is no default.</p><p id="targetpointer-global">GLOBAL: The <code class="its-elem-markup">targetPointerRule</code> element contains
the following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors" shape="rect">absolute selector</a> that selects the nodes to which this
rule applies.</p></li><li><p>A required <code class="its-attr-markup">targetPointer</code> attribute. It contains a <a href="#selectors" shape="rect">relative selector</a> that points to the node for the target
- content corresponding to the selected source node.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The source node and the target node may be of different types, but the target node must be able
+ content corresponding to the selected source node.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The source node and the target node may be of different types, but the target node <a href="#rfc-keywords" shape="rect">MUST</a> be able
to contain the same content as the source node (e.g., an attribute node cannot be
the target node of a source node that is an element with children).</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-target-pointer-global-1" id="EX-target-pointer-global-1" shape="rect"/>Example 66: Defining the target location of a source content with the
<code class="its-elem-markup">targetPointerRule</code> element</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><file></strong>
@@ -2671,7 +2668,7 @@
<strong class="hl-tag" style="color: #000096"></file></strong></pre></div><p>[Source file: <a href="examples/xml/EX-idvalue-attribute-1.xml" shape="rect">examples/xml/EX-idvalue-attribute-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="preservespace" id="preservespace" shape="rect"/>8.15 Preserve Space</h3><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="preservespace-definition" id="preservespace-definition" shape="rect"/>8.15.1 Definition</h4><p>The <a href="#preservespace" shape="rect">Preserve Space</a> data category indicates how
- whitespace should be handled in content. The possible values for this data category
+ whitespace is to be handled in content. The possible values for this data category
are "default" and "preserve" and carry the same meaning as the corresponding values of
the <a href="http://www.w3.org/TR/2008/REC-xml-20081126/#sec-white-space" shape="rect">xml:space</a> attribute. The default value is "default". The Preserve Space data
category does not apply to HTML documents in HTML syntax.</p></div><div class="div3">
@@ -2688,7 +2685,7 @@
rule applies.</p></li><li><p>A required <code class="its-attr-markup">space</code> attribute with the value "default" or
"preserve".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-preservespace-global-1" id="EX-preservespace-global-1" shape="rect"/>Example 70: The <a href="#preservespace" shape="rect">Preserve Space</a> data category expressed
globally</div><p>The <code class="its-elem-markup">preserveSpaceRule</code> element specifies that whitespace in all verse
- elements must be treated literally.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><book></strong>
+ elements <a href="#rfc-keywords" shape="rect">MUST</a> be treated literally.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><book></strong>
<strong class="hl-tag" style="color: #000096"><info></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:preserveSpaceRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//verse"</span> <span class="hl-attribute" style="color: #F5844C">space</span>=<span class="hl-value" style="color: #993300">"preserve"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -2704,7 +2701,7 @@
</pre></div><p>[Source file: <a href="examples/xml/EX-preservespace-global-1.xml" shape="rect">examples/xml/EX-preservespace-global-1.xml</a>]</p></div><p id="preservespace-local">LOCAL: The <code>xml:space</code> attribute, as defined
in section 2.10 of <a title="Extensible Markup Language
 (XML) 1.0 (Fifth Edition)" href="#xml10spec" shape="rect">[XML 1.0]</a>, maps exactly to the <a href="#preservespace" shape="rect">Preserve Space</a> data category.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-preservespace-local-1" id="EX-preservespace-local-1" shape="rect"/>Example 71: The <a href="#preservespace" shape="rect">Preserve Space</a> data category expressed
locally</div><p>The standard <code>xml:space</code> attribute specifies that the whitespace in the
- verse element must be treated literally.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><book></strong>
+ verse element <a href="#rfc-keywords" shape="rect">MUST</a> be treated literally.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><book></strong>
<strong class="hl-tag" style="color: #000096"><verse</strong> <span class="hl-attribute" style="color: #F5844C">xml:space</span>=<span class="hl-value" style="color: #993300">"preserve"</span><strong class="hl-tag" style="color: #000096">></strong>
'Twas brillig, and the slithy toves
Did gyre and gimble in the wabe;
@@ -2728,13 +2725,13 @@
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 should be considered in quality
+ 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" shape="rect">[ISO/TS 11669:2002]</a>. Details about translation specifications are available at <a title="Structured Specifications and Translation Parameters" href="#structuredspecs" shape="rect">[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
- should be used for specific scenarios.</p></div><p>The data category defines five pieces of information:</p><a name="lqissueDefs" id="lqissueDefs" shape="rect"/><table border="1" width="100%"><thead><tr><td rowspan="1" colspan="1">Information</td><td rowspan="1" colspan="1">Description</td><td rowspan="1" colspan="1">Value</td><td rowspan="1" colspan="1">Notes</td></tr></thead><tbody><tr><td rowspan="1" colspan="1">Type</td><td rowspan="1" colspan="1">A set of broad types of issues into which tool-specific issues can be
+ are best for specific scenarios.</p></div><p>The data category defines five pieces of information:</p><a name="lqissueDefs" id="lqissueDefs" shape="rect"/><table border="1" width="100%"><thead><tr><td rowspan="1" colspan="1">Information</td><td rowspan="1" colspan="1">Description</td><td rowspan="1" colspan="1">Value</td><td rowspan="1" colspan="1">Notes</td></tr></thead><tbody><tr><td rowspan="1" colspan="1">Type</td><td rowspan="1" colspan="1">A set of broad types of issues into which tool-specific issues can be
categorized.</td><td rowspan="1" colspan="1">One of the values defined in <a href="#lqissue-typevalues" shape="rect">list of type
values</a>.</td><td rowspan="1" colspan="1">ITS 2.0-compliant tools that use these types <a href="#rfc-keywords" shape="rect">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" shape="rect">MUST</a> be specified as well.</td></tr><tr><td rowspan="1" colspan="1">Comment</td><td rowspan="1" colspan="1">A human-readable description of the quality issue.</td><td rowspan="1" colspan="1">Text</td><td rowspan="1" colspan="1"/></tr><tr><td rowspan="1" colspan="1">Severity</td><td rowspan="1" colspan="1">A decimal value representing the severity of the issue, as defined by the
@@ -2835,7 +2832,7 @@
information</a>.</p></li><li><p>An optional <code class="its-attr-markup">locQualityIssueEnabled</code> attribute that
implements the <a href="#lqissueDefs" shape="rect">enabled
information</a>.</p></li></ul></li></ul></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="locQualityIssue-order">The order of <code class="its-elem-markup">locQualityIssue</code>
- elements within a <code class="its-elem-markup">locQualityIssues</code> element should reflect the order
[191 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-before-rfc2199-check.html 2013/06/21 16:54:48 NONE
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-before-rfc2199-check.html 2013/06/21 16:54:48 1.1
[6218 lines skipped]
Received on Friday, 21 June 2013 16:54:51 UTC