- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Sun, 09 Jun 2013 21:47:02 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv19946
Modified Files:
its20-for-editing-sec1-sec2.html
its20-for-editing-sec1-sec2.odd
Log Message:
more sec1 sec2 edits
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/06 09:56:55 1.12
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/09 21:47:02 1.13
@@ -19,23 +19,26 @@
<h2><a name="contents" id="contents" shape="rect"/>Table of Contents</h2><div class="toc"><div class="toc1">1 <a href="#introduction" shape="rect">Introduction</a><div class="toc2">1.1 <a href="#overview" shape="rect">Overview</a></div>
<div class="toc2">1.2 <a href="#general-motiviation-for-ITS2.0" shape="rect">General motivation for going beyond ITS 1.0</a></div>
<div class="toc2">1.3 <a href="#usage-scenarios" shape="rect">Usage Scenarios</a></div>
-<div class="toc2">1.4 <a href="#high-level-differences-between-1.0-and-2.0" shape="rect">High-level differences between ITS 1.0 and ITS 2.0</a><div class="toc3">1.4.1 <a href="#specific-HTML-support" shape="rect">Specific HTML support</a></div>
-<div class="toc3">1.4.2 <a href="#additional-data-categories" shape="rect">Additional data categories</a></div>
-<div class="toc3">1.4.3 <a href="#modified-datacategories" shape="rect">Modified data categories</a></div>
-<div class="toc3">1.4.4 <a href="#additional-mechanisms" shape="rect">Additional or modified mechanisms</a></div>
-<div class="toc3">1.4.5 <a href="#mappings" shape="rect">Mappings</a></div>
-<div class="toc3">1.4.6 <a href="#unicode-normalization" shape="rect">Unicode normalization</a></div>
-<div class="toc3">1.4.7 <a href="#extended-implementation-hints" shape="rect">Extended implementation hints</a></div>
-</div>
+<div class="toc2">1.4 <a href="#high-level-differences-between-1.0-and-2.0" shape="rect">High-level differences between ITS 1.0 and ITS 2.0</a></div>
+<div class="toc2">1.5 <a href="#extended-implementation-hints" shape="rect">Extended implementation hints</a></div>
</div>
<div class="toc1">2 <a href="#basic-concepts" shape="rect">Basic Concepts</a><div class="toc2">2.1 <a href="#basic-concepts-selection" shape="rect">Selection</a><div class="toc3">2.1.1 <a href="#basic-concepts-selection-local" shape="rect">Local Approach</a></div>
<div class="toc3">2.1.2 <a href="#basic-concepts-selection-global" shape="rect">Global Approach</a></div>
</div>
<div class="toc2">2.2 <a href="#basic-concepts-overinher" shape="rect">Overriding, Inheritance and Defaults</a></div>
<div class="toc2">2.3 <a href="#basic-concepts-addingpointing" shape="rect">Adding Information or Pointing to Existing Information</a></div>
-<div class="toc2">2.4 <a href="#mapping-conversion" shape="rect">Mapping and conversion</a></div>
-<div class="toc2">2.5 <a href="#tools-information" shape="rect">ITS Tools Annotation</a></div>
-<div class="toc2">2.6 <a href="#implementing-its20" shape="rect">Implementing ITS 2.0</a></div>
+<div class="toc2">2.4 <a href="#specific-HTML-support" shape="rect">Specific HTML support</a><div class="toc3">2.4.1 <a href="#html5-reference-global-rules" shape="rect">Referencing global rules</a></div>
+<div class="toc3">2.4.2 <a href="#html5-its-local-markup" shape="rect">Specifities of inserting local ITS 2.0 data categories</a></div>
+<div class="toc3">2.4.3 <a href="#html5-existing-markup-versus-its" shape="rect">Relation between HTML markup and ITS 2.0 data categories</a></div>
+<div class="toc3">2.4.4 <a href="#html5-standoff-markup-explanation" shape="rect">Standoff Markup in HTML5</a></div>
+<div class="toc3">2.4.5 <a href="#usage-in-legacy-html" shape="rect">Version of HTML</a></div>
+</div>
+<div class="toc2">2.5 <a href="#traceability" shape="rect">Traceability</a></div>
+<div class="toc2">2.6 <a href="#mapping-conversion" shape="rect">Mapping and conversion</a><div class="toc3">2.6.1 <a href="#mapping-NIF" shape="rect">ITS and RDF/NIF</a></div>
+<div class="toc3">2.6.2 <a href="#mapping-XLIFF" shape="rect">ITS and XLIFF</a></div>
+</div>
+<div class="toc2">2.7 <a href="#datacategories-summary" shape="rect">Summary: ITS 2.0 data categories</a></div>
+<div class="toc2">2.8 <a href="#implementing-its20" shape="rect">Implementing ITS 2.0</a></div>
</div>
<div class="toc1">3 <a href="#notation-terminology" shape="rect">Notation and Terminology</a><div class="toc2">3.1 <a href="#notation" shape="rect">Notation</a></div>
<div class="toc2">3.2 <a href="#def-datacat" shape="rect">Data category</a></div>
@@ -56,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="#d0e2352" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2441" 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="#d0e2597" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2686" 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>
@@ -143,7 +146,9 @@
<div class="toc1">H <a href="#revisionlog" shape="rect">Revision Log</a> (Non-Normative)</div>
<div class="toc1">I <a href="#acknowledgements" shape="rect">Acknowledgements</a> (Non-Normative)</div>
</div><hr/><div class="body"><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="introduction" id="introduction" shape="rect"/>1 Introduction</h2><div class="div2">
+<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="introduction" id="introduction" shape="rect"/>1 Introduction</h2><p>
+ <em>This section is informative</em>
+ </p><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="overview" id="overview" shape="rect"/>1.1 Overview</h3><p>
Content or software that is authored in one language (so-called
@@ -440,92 +445,16 @@
<strong class="hl-tag" style="color: #000096"></rsrc></strong>
<strong class="hl-tag" style="color: #000096"></dialogue></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">examples/xml/EX-motivation-its-2.xml</a>]</p></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><p>The basics of ITS 1.0 fit onto a beer mat:</p><ol class="depth1"><li><p>Provide meta data (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global appraoch</a>) to tie the meta data to specific XML nodes (e.g. all elements named <code>uitext</code>) or put the meta data straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of meta data categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing meta data (e.g terms already marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <a href="http://www.w3.org/International/its/ig/links.html" shape="rect">ITS Interest Group</a> for example compiled a list of additional data categories (see this <a href="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf" shape="rect">related summary</a>). Some of these were then defined in ITS 2.0: <a href="#idvalue" shape="rect">ID Value</a>, local <a href="#elements-within-text" shape="rect">Elements Within Text</a>, <a href="#preservespace" shape="rect">Preserve Space</a>, and <a href="#LocaleFilter" shape="rect">Locale Filte</a>. Others are still discussed as requirements:</p><ol class="depth1"><li><p>“Context” = What specific related information might be helpful?</p></li><li><p>“Automated Language”: Does this content lend iself to automatic processing?</p></li></ol><p>The real-world deployments also helped to understand that for the <a href="http://www.webplatform.org/" shape="rect">Open Web Platform</a> - the ITS 1.0 restriction to XML was an obstacle for quite a number of environments. What was missing was for example the following:</p><ol class="depth1"><li><p>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</p></li><li><p>Easy use of ITS in various Web-exposed Natural Language Processing contexts (e.g. machine translation, cross-language information retrieval, computer-supported linguistic quality assurance)</p></li><li><p>Support for provenance <a title="" href="#prov-overview" shape="rect">[PROV-OVERVIEW]</a>, “information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data scenaris.</p></li></ol><p>ITS 2.0 was created by an alliance of stakeholders who are involved in content for global use. Thus, ITS 2.0 was developed with input from/with a view towards the following:</p><ul><li><p>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in production chains</p></li><li><p>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to faciliate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="" href="#xliff" shape="rect">[XLIFF]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>) that are interested for example in lossless roundtripping of meta data in localization workflows.</p></li></ul><p>One example outcome of work on the requirements is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> mechanism. It addresses the provenance-related requirement b allowing ITS processors to leave a trace: ITS processors can basically say "It is me that generated this bit of information". Another example are the NIF-related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</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="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><p>The basics of ITS 1.0 fit onto a beer mat:</p><ol class="depth1"><li><p>Provide meta data (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global appraoch</a>) to tie the meta data to specific XML nodes (e.g. all elements named <code>uitext</code>) or put the meta data straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of meta data categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing meta data (e.g terms already marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <a href="http://www.w3.org/International/its/ig/links.html" shape="rect">ITS Interest Group</a> for example compiled a list of additional data categories (see this <a href="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf" shape="rect">related summary</a>). Some of these were then defined in ITS 2.0: <a href="#idvalue" shape="rect">ID Value</a>, local <a href="#elements-within-text" shape="rect">Elements Within Text</a>, <a href="#preservespace" shape="rect">Preserve Space</a>, and <a href="#LocaleFilter" shape="rect">Locale Filte</a>. Others are still discussed as requirements:</p><ol class="depth1"><li><p>“Context” = What specific related information might be helpful?</p></li><li><p>“Automated Language”: Does this content lend iself to automatic processing?</p></li></ol><p>The real-world deployments also helped to understand that for the <a href="http://www.webplatform.org/" shape="rect">Open Web Platform</a> - the ITS 1.0 restriction to XML was an obstacle for quite a number of environments. What was missing was for example the following:</p><ol class="depth1"><li><p>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</p></li><li><p>Easy use of ITS in various Web-exposed Natural Language Processing contexts (e.g. machine translation, cross-language information retrieval, computer-supported linguistic quality assurance)</p></li><li><p>Support for provenance <a title="" href="#prov-overview" shape="rect">[PROV-OVERVIEW]</a>, “information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data scenaris.</p></li></ol><p>ITS 2.0 was created by an alliance of stakeholders who are involved in content for global use. Thus, ITS 2.0 was developed with input from/with a view towards the following:</p><ul><li><p>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in production chains</p></li><li><p>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to faciliate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="" href="#xliff" shape="rect">[XLIFF]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>) that are interested for example in lossless roundtripping of meta data in localization workflows.</p></li></ul><p>One example outcome of work on the requirements is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> mechanism. It addresses the provenance-related requirement b allowing ITS processors to leave a trace: ITS processors can basically say "It is me that generated this bit of information". Another example are the <a title="" href="#nif-reference" shape="rect">[NIF]</a> related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</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="usage-scenarios" id="usage-scenarios" shape="rect"/>1.3 Usage Scenarios</h3><p>The ITS 1.0 specification <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a> states in <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">the introduction</a>: “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 multi-lingual production.<p><ul><li><p>Static mono-lingual: This part of the content has the directionality “right-to-left”.</p></li><li><p>Dynamic multi-lingual: This part of the content should be excluded from a possible translation phase.</p></li></ul><p>Although the ITS 1.0 made no assumptions about possible phases in a 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 multi-lingual content production. The model comprises support for multi-lingual content production phases such as:</p><ul><li><p>Internationalization</p></li><li><p>Pre-production (e.g. related to marking terminology)</p></li><li><p>Automated content enrichment (e.g. automatic hyperlinking for entities)</p></li><li><p>Extraction/filtering of translation-relevant content</p></li><li><p>Segmentation</p></li><li><p>Leveraging (e.g. of existing translation-related assets such as translaion memories)</p></li><li><p>Machine Translation (e.g. geared towards a specific domain)</p></li><li><p>Quality assessment or control of source language or target language content</p></li><li><p>Generation of translation kits (e.g. packages based on XLIFF)</p></li><li><p>Post-production</p></li><li><p>Publishing</p></li></ul><p>The document <a href="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/" shape="rect">Metadata for the Multilingual Web - Usage Scenarios and Implementations</a> lists 18 different usage scenarios for ITS 2.0. Most of them are composed of several of the aforementioned phases.</p><p>In a similar vein, ITS 2.0 takes a much more comprehensive view on the actors that may participate in a multi-lingual content production process. ITS 1.0 annotations (e.g. local markup for the <a href="#terminology" shape="rect">Terminology</a> data category) most of the time were conceived as being closely tied to human actors such as content authors or information architects. ITS 2.0 raises nonhuman actors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity idenfiers/disambiguators to the same level. This change amongst others is reflected in the introduction of the ITS 2.0 <a href="#its-tool-annotation" shape="rect">Tool Annotation</a> which allows systems to record that they have processed as certain part of content.</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="high-level-differences-between-1.0-and-2.0" id="high-level-differences-between-1.0-and-2.0" shape="rect"/>1.4 High-level differences between ITS 1.0 and ITS 2.0</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="specific-HTML-support" id="specific-HTML-support" shape="rect"/>1.4.1 Specific HTML support</h4><p>For applying ITS 2.0 data categories to HTML, five aspects must be considered:</p><ol class="depth1"><li><p>referencing global rules</p></li><li><p>specifities of inserting local ITS 2.0 data categories</p></li><li><p>relationship between HTML markup and data categories,</p></li><li><p>standoff markup in HTML5</p></li><li><p>HTML version.</p></li></ol><p>In the following sections these aspects are briefly discussed.</p><div class="div4">
-<h5><a name="html5-reference-global-rules" id="html5-reference-global-rules" shape="rect"/>1.4.1.1 Referencing global rules</h5><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 a link type for referring to external files
- with global rules and an approach to have inline global rules in the HTML <code>script</code> element.
- It is preferred to use external global rules linked via the <code>link</code> element than to have inline global rules in the HTML document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 4: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
- <code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
- the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
-<strong class="hl-tag" style="color: #000096"><html></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"><link</strong> <span class="hl-attribute" style="color: #F5844C">href</span>=<span class="hl-value" style="color: #993300">EX-translateRule-html5-1.xml</span> <span class="hl-attribute" style="color: #F5844C">rel</span>=<span class="hl-value" style="color: #993300">its-rules</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
- Of course there are always exceptions: certain code values should be translated,
- e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-global-1.html" shape="rect">examples/html5/EX-translate-html5-global-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1-rules-file" id="EX-translate-html5-global-1-rules-file" shape="rect"/>Example 5: ITS rules file linked from HTML</div><p>The rules file linked in <a href="#EX-translate-html5-global-1" shape="rect">Example 4</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
- <span class="hl-attribute" style="color: #F5844C">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
-<strong class="hl-tag" style="color: #000096"></its:rules></strong>
-</pre></div><p>[Source file: <a href="examples/html5/EX-translateRule-html5-1.xml" shape="rect">examples/html5/EX-translateRule-html5-1.xml</a>]</p></div></div><div class="div4">
-<h5><a name="html5-its-local-markup" id="html5-its-local-markup" shape="rect"/>1.4.1.2 Specifities of inserting local ITS 2.0 data categories</h5><p>In HTML, an ITS 2.0 local data category is realized with the specific prefix <code>its-*</code>.
- The general mapping of the XML based ITS 2.0 attributes to their HTML <code>its-*</code> counterparts is defined in
- <a class="section-ref" href="#html5-local-attributes" shape="rect">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" shape="rect">Appendix G: 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="div4">
-<h5><a name="html5-existing-markup-versus-its" id="html5-existing-markup-versus-its" shape="rect"/>1.4.1.3 Relation between HTML markup and ITS 2.0 data categories</h5><p>There are four ITS 2.0 data categories, which have direct counterparts
- in HTML markup. For theses data categories, ITS 2.0 defines the following specific
- behaviour:</p><ul><li><p>The <a href="#language-information" shape="rect">Language Information</a> data category has the HTML <code>lang</code>
- attribute counterpart; in XHTML this is the <code>xml:lang</code> attribute. These attributes act as
- local markup for the <a href="#language-information" shape="rect">Language Information</a> data category in HTML and
- take <a href="#selection-precedence" shape="rect">precedence</a> over language information conveyed via a global <code class="its-elem-markup">langRule</code>.</p></li><li><p>The <a href="#idvalue" shape="rect">Id Value</a> data category has the HTML or XHTML <code>id</code> attribute.
- This attribute acts as local markup for the <a href="#idvalue" shape="rect">Id Value</a> data category in HTML and take <a href="#selection-precedence" shape="rect">precedence</a> over
- id information conveyed via a global <code class="its-elem-markup">idValueRule</code>.</p></li><li><p>The <a href="#elements-within-text" shape="rect">Elements within Text</a> data category has a set of HTML
- elements defined as <a href="http://www.w3.org/TR/html51/dom.html#phrasing-content-1" shape="rect">phrasing content</a>. In the absence of an
- <a href="#elements-within-text" shape="rect">Elements within Text</a> local attribute or global rules selecting the
- element in question, these elements are always interpreted as
- <code>withinText="yes"</code> by default, except for the elements <code class="its-elem-markup">iframe</code>, <code class="its-elem-markup">noscript</code>, <code class="its-elem-markup">script</code>
- and <code class="its-elem-markup">textarea</code> which are interpreted as <code>withinText="nested"</code>.</p></li><li><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category has a direct counterpart in
- <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, namely the HTML5
- <code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute" shape="rect">the HTML5 definition</a>. The <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> 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" shape="rect"/>Example 6: The <a href="#language-information" shape="rect">Language Information</a>, <a href="#idvalue" shape="rect">Id Value</a>,
- <a href="#elements-within-text" shape="rect">Elements within Text</a> and <a href="#trans-datacat" shape="rect">Translate</a>
- ITS 2.0 data categories used with
- HTML native markup.</div><p>The <code>html</code> element is interpreted to convey the
- <a href="#language-information" shape="rect">Language Information</a> value "en".
- The <code>p</code> element is interpreted to
- convey the <a href="#idvalue" shape="rect">Id Value</a> of "p1". The elements <code>em</code> and <code>img</code> are interpreted to be <code>withinText="yes"</code>. The <code>p</code> element and its children is set to be non-translatable via an <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>
- <code>translate</code> attribute. Here the <code>alt</code> attribute, normally translatable by default, will also be non-translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
-<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">en</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>HTML native markup expressing three ITS 2.0 data categories<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"p1"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>This is a <strong class="hl-tag" style="color: #000096"><em></strong>motherboard<strong class="hl-tag" style="color: #000096"></em></strong> and image:
- <strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"http://example.com/myimg.png"</span> <span class="hl-attribute" style="color: #F5844C">alt</span>=<span class="hl-value" style="color: #993300">"My image"</span><strong class="hl-tag" style="color: #000096">/></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-its-and-existing-HTML5-markup.html" shape="rect">examples/html5/EX-its-and-existing-HTML5-markup.html</a>]</p></div><p>There are also some HTML markup elements that have similar, but not always identical, roles and behaviour than certain ITS 2.0 data categories.
- For example, the HTML <code>dfn</code> element
- could be used to identify a term in the sense of the <a href="#terminology" shape="rect">Terminology</a> data
- category. However, this is not always the case and it depends on the
- intentions of the content author. To accomodate this situation, users
- of ITS 2.0 are encouraged to specifiy the association of existing HTML
- markup with a dedicated global rules file. For an example rules file see the
- <a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml" shape="rect">XML I18N Best Practices</a> document.</p></div><div class="div4">
-<h5><a name="html5-standoff-markup-explanation" id="html5-standoff-markup-explanation" shape="rect"/>1.4.1.4 Standoff Markup in HTML5</h5><p>The <a href="#provenance" shape="rect">Provenance</a> and the <a href="#lqissue" shape="rect">Localization Quality Issue</a> data categories allow for using standoff markup. In HTML such standoff markup is put into a <code>script</code> element. The constraints for <a href="#provenance-records-in-html5-constraint" shape="rect">Provenance standoff</a> markup in HTML and <a href="#loc-quality-issues-in-html5-constraint" shape="rect">Localization quality issue</a> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <a href="#EX-provenance-html5-local-2" shape="rect">Example 62</a> and <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 77</a>.</p></div><div class="div4">
-<h5><a name="usage-in-legacy-html" id="usage-in-legacy-html" shape="rect"/>1.4.1.5 Version of HTML</h5><p>ITS 2.0 does not define how to use ITS in HTML versions prior version 5. Users are
- encouraged to migrate their content to HTML5 or XHTML. While it is possible to use
- <code>its-*</code> attributes introduced for <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> in older versions of HTML (such
- as 3.2 or 4.01) and pages using these attributes will work without any problems,
- <code>its-*</code> attributes will be marked as invalid in validators.</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="additional-data-categories" id="additional-data-categories" shape="rect"/>1.4.2 Additional data categories</h4><p>The following new data categories have been introduced in ITS 2.0.</p><ul><li><p><a href="#domain" shape="rect">Domain</a>: identify the topic or subject of the annotated content for translation related applications.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotate content with lexical or conceptual information for the purpose of contextual disambiguation.</p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a>: specify that a piece of content is only applicable to certain locales. </p></li><li><p><a href="#provenance" shape="rect">Provenance</a>: communicate the identity of agents that have been involved in the translation of the content or the revision of the ranslated content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate that a reference points to potentially translatable data in a resource outside the document. Examples of such resources are external images and audio or video files.</p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a>: associate a given piece of source content (i.e. the content to be translated) and its corresponding target content (i.e. the source content translated into a given target language).</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>: identify 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>: indicate how whitespace should be handled in content.</p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a>: describe 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>: express an overall measurement of the localization quality of a document or an item in a document.</p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a>: indicate the confidence that MT systems provide about their translation.
- </p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a>: specify the characters that are permitted in a given piece of content.</p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a>: specify the maximum storage size of a given content.</p></li></ul></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="modified-datacategories" id="modified-datacategories" shape="rect"/>1.4.3 Modified data categories</h4><p id="ruby-in-its2">ITS 1.0 provided the <a href="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation" shape="rect">Ruby data category</a>. ITS 2.0 does not provide ruby since at the time of writing, because of the the <a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element" shape="rect">ruby model in HTML5</a> was still under development. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p><p>The <a href="#directionality" shape="rect">Directionality</a> data category reflects directionality markup in <a title="HTML 4.01" href="#html4" shape="rect">[HTML 4.01]</a>. The reason is that enhancements are being discussed in th context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.</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="additional-mechanisms" id="additional-mechanisms" shape="rect"/>1.4.4 Additional or modified mechanisms</h4><p>The following mechanisms from ITS 1.0 have been modified for all data categories.</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">paam</code> element serves this purpose.</p></li></ul><p id="traceability">One mechanism has been added to ITS 2.0: <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a>. It allows to associate processor information with the use of individual data categories in a document, independently from data category annotations themselves. The mechanism is mandatory for the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category. For the <a href="#terminology" shape="rect">Terminology</a> and <a href="#textanalysis" shape="rect">Text Analysis</a> data categories it is mandatory if they provide confidence information, that is always tool related. Nevertheless, <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> can be used for all data categories.</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="mappings" id="mappings" shape="rect"/>1.4.5 Mappings</h4><div class="div4">
-<h5><a name="mapping-NIF" id="mapping-NIF" shape="rect"/>1.4.5.1 ITS and RDF/NIF</h5><p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
- representations) that contain ITS metadata to the RDF-based format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples that represent the textual content of the original document as RDF typed information and the ITS annotation as properties of those nodes defined in an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The backconversion <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div><div class="div4">
-<h5><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>1.4.5.2 ITS and XLIFF</h5><p>The XML Localization Interchange File Format <a title="" href="#xliff" shape="rect">[XLIFF]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.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: 1) the extraction of ITS meta-data from a source language file into XLIFF; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in te resulting target language files. 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="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="unicode-normalization" id="unicode-normalization" shape="rect"/>1.4.6 Unicode normalization</h4><p>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 by <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</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="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.4.7 Extended implementation hints</h4><p>tbd</p></div></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="high-level-differences-between-1.0-and-2.0" id="high-level-differences-between-1.0-and-2.0" shape="rect"/>1.4 High-level differences between ITS 1.0 and ITS 2.0</h3><p>The differences between ITS 1.0 and ITS 2.0 can be summarized as follows.</p><p>
+ <em>Covering <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>: </em>ITS 1.0 provides data categories to be applied to XML content. ITS 2.0 extends the coverage to <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>. Explanatory details about ITS 2.0 and <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> is given in <a class="section-ref" href="#specific-HTML-support" shape="rect">Section 2.4: Specific HTML support</a>.</p><p>
+ <em>Adding data categories</em>: ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 1.0 and ITS 2.0 data categories is given in <a class="section-ref" href="#datacategories-summary" shape="rect">Section 2.7: Summary: ITS 2.0 data categories</a>.</p><p>
+ <em>Modifying data categories</em>:</p><ul><li><p id="ruby-in-its2">ITS 1.0 provided the <a href="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation" shape="rect">Ruby data category</a>. ITS 2.0 does not provide ruby since at the time of writing, because of the the <a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element" shape="rect">ruby model in HTML5</a> was still under development. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p></li><li><p>The <a href="#directionality" shape="rect">Directionality</a> data category reflects directionality markup in <a title="HTML 4.01" href="#html4" shape="rect">[HTML 4.01]</a>. The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancemens are not finalized yet. They will be reflected in a future revision of ITS.</p></li></ul><p>
+ <em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified for all data categories.</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="secion-ref" href="#traceability" shape="rect">Section 2.5: 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 ITS 2.0 and XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">Section 2.6: 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 clarifying that Non-ITS elements and attributes found in ITS elements may be ignored 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 by <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”. The underlying formal definitions are given in the subsequent sections.</p><p>A key concept of ITS is the abstract notion of <a href="#def-datacat" shape="rect">data categories</a>. Data categories define the information that can be conveyed via ITS. An example is the <a href="#trans-datacat" shape="rect">Translate</a> data category. It conveys information about translatability of conent.</p><p>
@@ -544,11 +473,11 @@
markup in elements defined by ITS itself (namely the <code class="its-elem-markup">rules</code> element)</p></li></ul><p>ITS markup can be used with XML documents (e.g. a DocBook article), HTML documents, or schemas (e.g. an
XML Schema document for a proprietary document format).</p><p>The following two examples sketch the distinction between the local and global
approaches, using the <a href="#trans-datacat" shape="rect">Translate</a> data category as one 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.1.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 7</a> shows how a content
+<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.1.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 4</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. Translation tools that are aware of the meaning of this attribute can
- then screen the relevant content from the translation process.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 7: ITS markup on elements in an XML document (local approach) </div><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>
+ then screen the relevant content from the translation process.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 4: ITS markup on elements in an XML document (local approach) </div><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>
@@ -571,7 +500,7 @@
which does not. Tools that process this content for translation will need to implement
the expected inheritance.</p><p id="local-approach-not-applicable-to-attributes">For XML content, the local approach cannot be applied on a particular attribute.
It can be applied for the content of the current element and all its inherited nodes as described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>. For the <a href="#trans-datacat" shape="rect">Translate</a> data category used in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, this is different, see the explanation of the <a href="#translate-in-html5" shape="rect">HTML5 definition of Translate</a>.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"/>2.1.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 8</a> shows a different
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"/>2.1.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 5</a> shows a different
approach to identifying non-translatable content, similar to that used with a
<code>style</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>, but using an
ITS-defined element called <code class="its-elem-markup">rules</code>. It works as follows: A document can contain
@@ -583,7 +512,7 @@
attributes are XPath absolute location paths (or CSS Selectors if <a href="#queryLanguage" shape="rect">queryLanguage</a> is set to "css"). Via the <a href="#its-param" shape="rect">param</a> element
variables can be provided and then be used in the selectors.</p><p>Information for the
handling of namespaces in XPath expressions is taken from namespace declarations
- <a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> at the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 8: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> at the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 5: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><prolog></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>Using ITS<strong class="hl-tag" style="color: #000096"></title></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -616,7 +545,7 @@
<code>p</code> elements in an XML document)</p></li><li><p>ITS markup to pertain to attributes</p></li><li><p>ITS markup to <a href="#associating-its-with-existing-markup" shape="rect"> associate
with existing markup</a> (for example the <code>term</code> element in
DITA)</p></li></ul></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"/>2.2 Overriding, Inheritance and Defaults</h3><p>The power of the ITS selection mechanisms comes at a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a>, and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a>, have to be established.</p><p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 9</a> shows how inheritance
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"/>2.2 Overriding, Inheritance and Defaults</h3><p>The power of the ITS selection mechanisms comes at a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a>, and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a>, have to be established.</p><p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 6</a> shows how inheritance
and overriding work for the <a href="#trans-datacat" shape="rect">Translate</a> data category.
By default elements are translatable. Here, the <code class="its-elem-markup">translateRule</code> element declared
in the header overrides the default for the <code>head</code> element inside
@@ -625,7 +554,7 @@
<code>its:translate="yes"</code>. Note that the global rule is processed first,
regardless of its position inside the document. In the main body of the document, the
default applies, and here it is <code>its:translate="no"</code> that is used to set
- “faux pas” as non-translatable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 9: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #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>
+ “faux pas” as non-translatable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 6: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #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"><head></strong>
<strong class="hl-tag" style="color: #000096"><revision></strong>Sep-10-2006 v5<strong class="hl-tag" style="color: #000096"></revision></strong>
<strong class="hl-tag" style="color: #000096"><author></strong>Ealasaidh McIan<strong class="hl-tag" style="color: #000096"></author></strong>
@@ -644,7 +573,7 @@
<strong class="hl-tag" style="color: #000096"></div></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></text></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-3.xml" shape="rect">examples/xml/EX-basic-concepts-3.xml</a>]</p></div><p>For XML content, <a href="#datacategories-overview" shape="rect">data category specific defaults</a> are provided. These are independent of the actual XML markup vocabulary. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence, that HTML markup is normatively interpreted as ITS 2.0 data category information: See <a class="section-ref" href="#html5-existing-markup-versus-its" shape="rect">Section 1.4.1.3: Relation between HTML markup and ITS 2.0 data categories</a> for more information.</p></div><div class="div2">
+</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-3.xml" shape="rect">examples/xml/EX-basic-concepts-3.xml</a>]</p></div><p>For XML content, <a href="#datacategories-overview" shape="rect">data category specific defaults</a> are provided. These are independent of the actual XML markup vocabulary. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence, that HTML markup is normatively interpreted as ITS 2.0 data category information: See <a class="section-ref" href="#html5-existing-markup-versus-its" shape="rect">Section 2.4.3: Relation between HTML markup and ITS 2.0 data categories</a> for more information.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-addingpointing" id="basic-concepts-addingpointing" shape="rect"/>2.3 Adding Information or Pointing to Existing Information</h3><p>For some data categories, special attributes add or point to information about the
selected nodes. For example, the <a href="#locNote-datacat" shape="rect">Localization Note</a>
data category can add information to selected nodes (using a <code class="its-elem-markup">locNote</code> element),
@@ -653,9 +582,87 @@
data categories allow to point to existing information or to add information.</p><p>The functionalities of adding information and pointing to existing information are
<em>mutually exclusive</em>. That is to say, attributes for pointing and adding
the same information must not 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="mapping-conversion" id="mapping-conversion" shape="rect"/>2.4 Mapping and conversion</h3><p>tbd - here <a class="section-ref" href="#mappings" shape="rect">Section 1.4.5: Mappings</a>.</p></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="tools-information" id="tools-information" shape="rect"/>2.5 ITS Tools Annotation</h3><p>tbd - here partially content of <a class="section-ref" href="#additional-mechanisms" shape="rect">Section 1.4.4: Additional or modified mechanisms</a>.</p></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="implementing-its20" id="implementing-its20" shape="rect"/>2.6 Implementing ITS 2.0</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>, 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 Expectations for ITS Markup</a> tell implementer how to process XML content applying 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-class-html5-its" shape="rect">Section 4.4: Conformance Class for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">Section 4.3: Conformance Type 3: Processing Expectatins for ITS Markup in HTML</a> make clear: what information needs to be made available for given pieces of markup then processing a dedicated ITS 2.0 data category? To allow for flexibility, an implementation can choose whether it wants to process only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in seperate conformances clauses and also in the <a href="@@@@" shape="rect">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only cover above aspect, that is: what information needs to be made available. They do not define how that information actually should be applied. This is due to the fact that there is a huge variety of usage scenarios of ITS 2.0, and a huge variety of tools for working with ITS 2.0. Each of these tools has their own way of using ITS 2.0 data categories. See <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a> for more information.</p><span class=editor-note">[Ed. note: Add link to test suite]</span></div></div><div class="div1">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="specific-HTML-support" id="specific-HTML-support" shape="rect"/>2.4 Specific HTML support</h3><p>For applying ITS 2.0 data categories to HTML, five aspects must be considered:</p><ol class="depth1"><li><p>referencing global rules</p></li><li><p>specifities of inserting local ITS 2.0 data categories</p></li><li><p>relationship between HTML markup and data categories,</p></li><li><p>standoff markup in HTML5</p></li><li><p>HTML version.</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-reference-global-rules" id="html5-reference-global-rules" shape="rect"/>2.4.1 Referencing global rules</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 a link type for referring to external files
+ with global rules and an approach to have inline global rules in the HTML <code>script</code> element.
+ It is preferred to use external global rules linked via the <code>link</code> element than to have inline global rules in the HTML document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 7: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
+ <code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
+ the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"><link</strong> <span class="hl-attribute" style="color: #F5844C">href</span>=<span class="hl-value" style="color: #993300">EX-translateRule-html5-1.xml</span> <span class="hl-attribute" style="color: #F5844C">rel</span>=<span class="hl-value" style="color: #993300">its-rules</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"></head></strong>
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
+ Of course there are always exceptions: certain code values should be translated,
+ e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
+<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-global-1.html" shape="rect">examples/html5/EX-translate-html5-global-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1-rules-file" id="EX-translate-html5-global-1-rules-file" shape="rect"/>Example 8: ITS rules file linked from HTML</div><p>The rules file linked in <a href="#EX-translate-html5-global-1" shape="rect">Example 7</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
+ <span class="hl-attribute" style="color: #F5844C">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
+<strong class="hl-tag" style="color: #000096"></its:rules></strong>
+</pre></div><p>[Source file: <a href="examples/html5/EX-translateRule-html5-1.xml" shape="rect">examples/html5/EX-translateRule-html5-1.xml</a>]</p></div></div><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-its-local-markup" id="html5-its-local-markup" shape="rect"/>2.4.2 Specifities of inserting local ITS 2.0 data categories</h4><p>In HTML, an ITS 2.0 local data category is realized with the specific prefix <code>its-*</code>.
+ The general mapping of the XML based ITS 2.0 attributes to their HTML <code>its-*</code> counterparts is defined in
+ <a class="section-ref" href="#html5-local-attributes" shape="rect">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" shape="rect">Appendix G: 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" 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-existing-markup-versus-its" id="html5-existing-markup-versus-its" shape="rect"/>2.4.3 Relation between HTML markup and ITS 2.0 data categories</h4><p>There are four ITS 2.0 data categories, which have direct counterparts
+ in HTML markup. For theses data categories, ITS 2.0 defines the following specific
+ behaviour:</p><ul><li><p>The <a href="#language-information" shape="rect">Language Information</a> data category has the HTML <code>lang</code>
+ attribute counterpart; in XHTML this is the <code>xml:lang</code> attribute. These attributes act as
+ local markup for the <a href="#language-information" shape="rect">Language Information</a> data category in HTML and
+ take <a href="#selection-precedence" shape="rect">precedence</a> over language information conveyed via a global <code class="its-elem-markup">langRule</code>.</p></li><li><p>The <a href="#idvalue" shape="rect">Id Value</a> data category has the HTML or XHTML <code>id</code> attribute.
+ This attribute acts as local markup for the <a href="#idvalue" shape="rect">Id Value</a> data category in HTML and take <a href="#selection-precedence" shape="rect">precedence</a> over
+ id information conveyed via a global <code class="its-elem-markup">idValueRule</code>.</p></li><li><p>The <a href="#elements-within-text" shape="rect">Elements within Text</a> data category has a set of HTML
+ elements defined as <a href="http://www.w3.org/TR/html51/dom.html#phrasing-content-1" shape="rect">phrasing content</a>. In the absence of an
+ <a href="#elements-within-text" shape="rect">Elements within Text</a> local attribute or global rules selecting the
+ element in question, these elements are always interpreted as
+ <code>withinText="yes"</code> by default, except for the elements <code class="its-elem-markup">iframe</code>, <code class="its-elem-markup">noscript</code>, <code class="its-elem-markup">script</code>
+ and <code class="its-elem-markup">textarea</code> which are interpreted as <code>withinText="nested"</code>.</p></li><li><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category has a direct counterpart in
+ <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, namely the HTML5
+ <code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute" shape="rect">the HTML5 definition</a>. The <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> 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" shape="rect"/>Example 9: The <a href="#language-information" shape="rect">Language Information</a>, <a href="#idvalue" shape="rect">Id Value</a>,
+ <a href="#elements-within-text" shape="rect">Elements within Text</a> and <a href="#trans-datacat" shape="rect">Translate</a>
+ ITS 2.0 data categories used with
+ HTML native markup.</div><p>The <code>html</code> element is interpreted to convey the
+ <a href="#language-information" shape="rect">Language Information</a> value "en".
+ The <code>p</code> element is interpreted to
+ convey the <a href="#idvalue" shape="rect">Id Value</a> of "p1". The elements <code>em</code> and <code>img</code> are interpreted to be <code>withinText="yes"</code>. The <code>p</code> element and its children is set to be non-translatable via an <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>
+ <code>translate</code> attribute. Here the <code>alt</code> attribute, normally translatable by default, will also be non-translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">en</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>HTML native markup expressing three ITS 2.0 data categories<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"></head></strong>
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"p1"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>This is a <strong class="hl-tag" style="color: #000096"><em></strong>motherboard<strong class="hl-tag" style="color: #000096"></em></strong> and image:
+ <strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"http://example.com/myimg.png"</span> <span class="hl-attribute" style="color: #F5844C">alt</span>=<span class="hl-value" style="color: #993300">"My image"</span><strong class="hl-tag" style="color: #000096">/></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
+<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-its-and-existing-HTML5-markup.html" shape="rect">examples/html5/EX-its-and-existing-HTML5-markup.html</a>]</p></div><p>There are also some HTML markup elements that have similar, but not always identical, roles and behaviour than certain ITS 2.0 data categories.
+ For example, the HTML <code>dfn</code> element
+ could be used to identify a term in the sense of the <a href="#terminology" shape="rect">Terminology</a> data
+ category. However, this is not always the case and it depends on the
+ intentions of the content author. To accomodate this situation, users
+ of ITS 2.0 are encouraged to specifiy the association of existing HTML
+ markup with a dedicated global rules file. For an example rules file see the
+ <a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml" shape="rect">XML I18N Best Practices</a> document.</p></div><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-standoff-markup-explanation" id="html5-standoff-markup-explanation" shape="rect"/>2.4.4 Standoff Markup in HTML5</h4><p>The <a href="#provenance" shape="rect">Provenance</a> and the <a href="#lqissue" shape="rect">Localization Quality Issue</a> data categories allow for using standoff markup. In HTML such standoff markup is put into a <code>script</code> element. The constraints for <a href="#provenance-records-in-html5-constraint" shape="rect">Provenance standoff</a> markup in HTML and <a href="#loc-quality-issues-in-html5-constraint" shape="rect">Localization quality issue</a> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <a href="#EX-provenance-html5-local-2" shape="rect">Example 62</a> and <a href="#EX-locQualityIssue-html5-local-2" shape="rct">Example 77</a>.</p></div><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="usage-in-legacy-html" id="usage-in-legacy-html" shape="rect"/>2.4.5 Version of HTML</h4><p>ITS 2.0 does not define how to use ITS in HTML versions prior version 5. Users are
+ encouraged to migrate their content to HTML5 or XHTML. While it is possible to use
+ <code>its-*</code> attributes introduced for <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> in older versions of HTML (such
+ as 3.2 or 4.01) and pages using these attributes will work without any problems,
+ <code>its-*</code> attributes will be marked as invalid in validators.</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="traceability" id="traceability" shape="rect"/>2.5 Traceability</h3><p>The <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism allows to associate processor information with the use of individual data categories in a document, independently from data category annotations themselves. The mechanism associates identifiers for tools and data categories via the <code class="its-attr-markup">annotatorsRef</code> attribute (or <code class="its-attr-markup">annotators-ref</code> in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>) and is mandatory for the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category. For the <a href="#terminology" shape="rect">Terminology</a> and <a href="#textanalysis" shape="rect">Text Analysis</a> data categories it is mandatory if they provide confience information, that is always tool related. Nevertheless, <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> can be used for all data categories. <a href="#EX-its-tool-annotation-2" shape="rect">Example 24</a> demonstrates the usage including several data categories.</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="mapping-conversion" id="mapping-conversion" shape="rect"/>2.6 Mapping and conversion</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="mapping-NIF" id="mapping-NIF" shape="rect"/>2.6.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-based format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples that represent the textual content of the original document as RDF typed information and the ITS annotation as properties of those nodes defined in an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The backconversion <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</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.6.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="" href="#xliff" shape="rect">[XLIFF]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.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: 1) the extraction of ITS meta-data from a sourcelanguage file into XLIFF; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files. 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="datacategories-summary" id="datacategories-summary" shape="rect"/>2.7 Summary: ITS 2.0 data categories</h3><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>: express 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>: communicate notes to localizers about a particular item of content.</p></li><li><p><a href="#terminology" shape="rect">Terminology</a>: mak terms and optionally associate them with information, such as definitions or references to a term data base.</p></li><li><p><a href="#directionality" shape="rect">Directionality</a>: specify the base writing direction of blocks, embeddings and overrides for the Unicode bidirectional algorithm.</p></li><li><p><a href="#language-information" shape="rect">Language Information</a>: express the language of a given piece of content.</p></li><li><p><a href="#elements-within-text" shape="rect">Elements Witin Text:</a> express how content of an element is related to the text flow (constitute its own segment like paragraphs, be part of a segment like emphasis marker etc).</p></li><li><p><a href="#domain" shape="rect">Domain</a>: identify the topic or subject of the annotated content for translation related applications.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotate content with lexical or conceptual information for the purpose of contextual disambiguation.</p></li><li><p><a href="#ocaleFilter" shape="rect">Locale Filter</a>: specify that a piece of content is only applicable to certain locales. </p></li><li><p><a href="#provenance" shape="rect">Provenance</a>: communicate the identity of agents that have been involved in the translation of the content or the revision of the translated content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate that a reference points to potentially translatable data in a resource outside the document. Examples of such resources are external images and audio or video files.</p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a>: associate a given piece of source content (i.e. the content to be translated) and its corresponding target content (i.e. the source content translated into a given target language).</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>: identify 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>: indicate how whitespace should be handled in content.</p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a>: describe 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>: express an overall measurement of the localization quality of a document or an item in a document.</p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a>: indicate the confidence that MT systems provide about their translation.
+ </p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a>: specify the characters that are permitted in a given piece of content.</p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a>: specify the maximum storage size of a given content.</p></li></ul></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 Implementing ITS 2.0</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>, 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 Expectations for ITS Markup</a> tell implementer how to process XML content applying 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-class-html5-its" shape="rect">Section 4.4: Conformance Class for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">Section 4.3: Conformance Type 3: Processing Expectatins for ITS Markup in HTML</a> make clear: what information needs to be made available for given pieces of markup then processing a dedicated ITS 2.0 data category? To allow for flexibility, an implementation can choose whether it wants to process only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in seperate conformances clauses and also in the <a href="@@@@" shape="rect">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only cover above aspect, that is: what information needs to be made available. They do not define how that information actually should be applied. This is due to the fact that there is a huge variety of usage scenarios of ITS 2.0, and a huge variety of tools for working with ITS 2.0. Each of these tools has their own way of using ITS 2.0 data categories. See <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a> for more information.</p><span class=editor-note">[Ed. note: Add link to test suite]</span></div></div><div class="div1">
<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">
@@ -676,7 +683,7 @@
and localization of XML schemas and documents.] The concept of a data
category is independent of its implementation in an XML and HTML environment (e.g. using
an element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "implementation" subsections in
- <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1441" id="d0e1441" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1530" id="d0e1530" 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
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
@@ -762,7 +769,7 @@
used, it <a href="#rfc-keywords" shape="rect">MUST</a> be part of the content model of at
least one element declared in the schema. It <a href="#rfc-keywords" shape="rect">SHOULD</a> be in a content model for meta information, if this is available in
that schema (e.g. the <code>head</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>).</p></li><li><p id="its-conformance-1-3">
- <em>1-4:</em> If the <code class="its-elem-markup">span</code> element is
+ <em>1-3:</em> If the <code class="its-elem-markup">span</code> element is
used, it <a href="#rfc-keywords" shape="rect">SHOULD</a> be declared as an inline
element.</p></li></ul><p id="its-markup-conformance-claims">Full implementations of this conformance type
will implement all markup declarations for ITS. Statements related to this conformance
@@ -882,7 +889,8 @@
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" shape="rect">Section 5.3: Query Language of Selectors</a>.</p></li><li><p><a href="#selection-local" shape="rect">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" shape="rect">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" 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="selection-global" id="selection-global" shape="rect"/>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. It
@@ -941,9 +949,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2352" id="d0e2352" 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="d0e2441" id="d0e2441" 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="d0e2363" id="d0e2363" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+<h5><a name="d0e2452" id="d0e2452" 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
which starts with "<code>/</code>". That is, it must 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>.
@@ -988,14 +996,14 @@
implementations can 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 <code>css</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2574" id="d0e2574" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2663" id="d0e2663" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as 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="d0e2584" id="d0e2584" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2673" id="d0e2673" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Selector is not
evaluated against the complete document tree but only against subtrees rooted at
nodes selected by selector in the <code 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="d0e2597" id="d0e2597" 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="d0e2686" id="d0e2686" 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>identifier of query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating absolute selector to collection of nodes;</p></li><li><p>rules for evaluating relative selector to collection of 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>,
@@ -1394,8 +1402,8 @@
<a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-global-rules" id="html5-global-rules" shape="rect"/>6.2 Global rules</h3><p>Various aspects for global rules in general, external global rules or inline global
rules need to be taken into account. An example of an HTML5 document using global rules
- is <a href="#EX-translate-html5-global-1" shape="rect">Example 4</a>. The corresponding rules
- file is <a href="#EX-translate-html5-global-1-rules-file" shape="rect">Example 5</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>By default XPath 1.0 will be used for selection in global rules. If users prefer
+ is <a href="#EX-translate-html5-global-1" shape="rect">Example 7</a>. The corresponding rules
+ file is <a href="#EX-translate-html5-global-1-rules-file" shape="rect">Example 8</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>By default XPath 1.0 will be used for selection in global rules. If users prefer
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>HTML5 parsing algorithm automatically puts all HTML elements into XHTML namespace
(<code>http://www.w3.org/1999/xhtml</code>). Selectors used in global rules must
@@ -1425,7 +1433,7 @@
inheritance rules are laid out in a dedicated <a href="#datacategories-overview" shape="rect">datacategory overview table</a>, see column "<span class="quote">Inheritance for element
nodes</span>". Selection via inheritance takes precedence over default values, see
below item.</p></li><li><p>Selections via defaults for data categories, see <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p></li></ol><p>In case of conflicts between global selections via multiple <a href="#selection-global" shape="rect">rules</a> elements, the last rule has higher
- precedence.</p><p>The forehand mentioned <a href="#EX-translate-html5-global-1" shape="rect">Example 4</a>
+ precedence.</p><p>The forehand mentioned <a href="#EX-translate-html5-global-1" shape="rect">Example 7</a>
demonstrates the precedence: the <code>code</code> element with the <code class="its-attr-markup">translate</code>
attribute set to yes has precedence over the global rule setting all <code>code</code>
elements as untranslatable.</p></div></div><div class="div1">
@@ -1656,8 +1664,7 @@
communicate notes to localizers about a particular item of content.</p><p>This data category can be used for several purposes, including, but not limited
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
+ 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
[21 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/06 09:56:55 1.14
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/09 21:47:02 1.15
@@ -132,8 +132,7 @@
<div xml:id="introduction">
<head>Introduction</head>
-
-
+<p><emph>This section is informative</emph></p>
<div xml:id="overview">
@@ -482,7 +481,7 @@
- <p>One example outcome of work on the requirements is the <ref target="#its-tool-annotation">ITS Tool Annotation</ref> mechanism. It addresses the provenance-related requirement by allowing ITS processors to leave a trace: ITS processors can basically say "It is me that generated this bit of information". Another example are the NIF-related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</p>
+ <p>One example outcome of work on the requirements is the <ref target="#its-tool-annotation">ITS Tool Annotation</ref> mechanism. It addresses the provenance-related requirement by allowing ITS processors to leave a trace: ITS processors can basically say "It is me that generated this bit of information". Another example are the <ptr target="#nif-reference" type="bibref"/> related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</p>
</div>
<div xml:id="usage-scenarios"><head>Usage Scenarios</head>
@@ -527,7 +526,7 @@
<item>Publishing</item></list>
- <p>The document <ref target="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/">Metadata for the Multilingual Web - Usage Scenarios and Implementations</ref> lists 18 different usage scenarios for ITS 2.0. Most of them are composed of several of the aforementioned phases.</p>
+ <p>The document <ref target="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/">Metadata for the Multilingual Web - Usage Scenarios and Implementations</ref> lists a large variety of usage scenarios for ITS 2.0. Most of them are composed of several of the aforementioned phases.</p>
<p>In a similar vein, ITS 2.0 takes a much more comprehensive view on the actors that may participate in a multi-lingual content production process. ITS 1.0 annotations (e.g. local markup for the <ref target="#terminology">Terminology</ref> data category) most of the time were conceived as being closely tied to human actors such as content authors or information architects. ITS 2.0 raises non-human actors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity idenfiers/disambiguators to the same level. This change amongst others is reflected in the introduction of the ITS 2.0 <ref target="#its-tool-annotation">Tool Annotation</ref> which allows systems to record that they have processed as certain part of content.</p>
@@ -536,104 +535,33 @@
</div>
<div xml:id="high-level-differences-between-1.0-and-2.0"><head>High-level differences between ITS 1.0 and ITS 2.0</head>
- <div xml:id="specific-HTML-support"><head>Specific HTML support</head>
-
- <p>For applying ITS 2.0 data categories to HTML, five aspects must be considered:</p>
- <list type="ordered">
- <item>referencing global rules</item>
- <item>specifities of inserting local ITS 2.0 data categories</item>
- <item>relationship between HTML markup and data categories,</item>
- <item>standoff markup in HTML5</item>
- <item>HTML version.</item>
+
+ <p>The differences between ITS 1.0 and ITS 2.0 can be summarized as follows.</p>
+
+ <p><emph>Covering <ptr type="bibref" target="#html5"/>: </emph>ITS 1.0 provides data categories to be applied to XML content. ITS 2.0 extends the coverage to <ptr target="#html5" type="bibref"/>. Explanatory details about ITS 2.0 and <ptr target="#html5" type="bibref"/> is given in <ptr target="#specific-HTML-support" type="specref"/>.</p>
+ <p><emph>Adding data categories</emph>: ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 1.0 and ITS 2.0 data categories is given in <ptr target="#datacategories-summary" type="specref"/>.</p>
+
+ <p><emph>Modifying data categories</emph>:</p>
+ <list><item> <p xml:id="ruby-in-its2">ITS 1.0 provided the <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation">Ruby data category</ref>. ITS 2.0 does not provide ruby since at the time of writing, because of the the <ref target="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</ref> was still under development. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p></item>
+
+ <item> <p>The <ref target="#directionality">Directionality</ref> data category reflects directionality markup in <ptr target="#html4" type="bibref"/>. The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.</p></item></list>
+ <p><emph>Additional or modified mechanisms:</emph> The following mechanisms from ITS 1.0 have been modified for all data categories.</p>
+
+ <list>
+ <item><p xml:id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <ref target="#basic-concepts-selection-global">global rules</ref>. ITS 2.0 allows for choosing the <ref target="#selectors">query language of selectors</ref>. 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></item>
+ <item><p xml:id="parameters-in-selector">In global rules it is now possible to set <ref target="#its-param">variables for the selectors</ref> (XPath expression). The <gi>param</gi> element serves this purpose.</p></item>
+ <item>ITS 2.0 has a <ref target="#its-tool-annotation">ITS Tools Annotation</ref> mechanism to associate processor information with the use of individual data categories. See <ptr target="#traceability" type="specref"/> for details.</item>
</list>
- <p>In the following sections these aspects are briefly discussed.</p>
- <div xml:id="html5-reference-global-rules"><head>Referencing global rules</head>
- <p>To account for the so-called “<ref target="#basic-concepts-selection-global">global
- approach</ref>” in HTML, this specification (see <ptr target="#html5-global-rules" type="specref"/>) defines a link type for referring to external files
- with global rules and an approach to have inline global rules in the HTML <code>script</code> element.
- It is preferred to use external global rules linked via the <code>link</code> element than to have inline global rules in the HTML document.</p>
- <exemplum xml:id="EX-translate-html5-global-1">
- <head>Using ITS global rules in HTML</head>
- <p>The <code>link</code> element points to the rules file
- <code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
- the ITS specific link relation <code>its-rules</code>.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/html5/EX-translate-html5-global-1.html" type="html5"/>
- </exemplum>
- <exemplum xml:id="EX-translate-html5-global-1-rules-file">
- <head>ITS rules file linked from HTML</head>
- <p>The rules file linked in <ptr target="#EX-translate-html5-global-1" type="exref"
- />.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/html5/EX-translateRule-html5-1.xml"/>
- </exemplum>
- </div>
- <div xml:id="html5-its-local-markup"><head>Specifities of inserting local ITS 2.0 data categories</head>
- <p>In HTML, an ITS 2.0 local data category is realized with the specific prefix <code>its-*</code>.
- The general mapping of the XML based ITS 2.0 attributes to their HTML <code>its-*</code> counterparts is defined in
- <ptr target="#html5-local-attributes" type="specref"/>. An informative table in <ptr target="#list-of-elements-and-attributes" type="specref"/>
- provides an overview of the mapping for all data categories.</p>
- </div>
- <div xml:id="html5-existing-markup-versus-its"><head>Relation between HTML markup and ITS 2.0 data categories</head>
- <p>There are four ITS 2.0 data categories, which have direct counterparts
- in HTML markup. For theses data categories, ITS 2.0 defines the following specific
- behaviour:</p>
- <list type="unordered">
- <item><p>The <ref target="#language-information">Language Information</ref> data category has the HTML <code>lang</code>
- attribute counterpart; in XHTML this is the <code>xml:lang</code> attribute. These attributes act as
- local markup for the <ref target="#language-information">Language Information</ref> data category in HTML and
- take <ref target="#selection-precedence">precedence</ref> over language information conveyed via a global <gi>langRule</gi>.</p></item>
- <item><p>The <ref target="#idvalue">Id Value</ref> data category has the HTML or XHTML <code>id</code> attribute.
- This attribute acts as local markup for the <ref target="#idvalue">Id Value</ref> data category in HTML and take <ref target="#selection-precedence">precedence</ref> over
- id information conveyed via a global <gi>idValueRule</gi>.</p></item>
- <item><p>The <ref target="#elements-within-text">Elements within Text</ref> data category has a set of HTML
- elements defined as <ref target="http://www.w3.org/TR/html51/dom.html#phrasing-content-1">phrasing content</ref>. In the absence of an
- <ref target="#elements-within-text">Elements within Text</ref> local attribute or global rules selecting the
- element in question, these elements are always interpreted as
- <code>withinText="yes"</code> by default, except for the elements <gi>iframe</gi>, <gi>noscript</gi>, <gi>script</gi>
- and <gi>textarea</gi> which are interpreted as <code>withinText="nested"</code>.</p></item>
- <item xml:id="translate-in-html5"><p>The <ref target="#trans-datacat">Translate</ref> data category has a direct counterpart in
- <ptr target="#html5" type="bibref"/>, namely the HTML5
- <code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <ref target="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">the HTML5 definition</ref>. The <ptr target="#html5" type="bibref"/> definition also applies to nodes selected via global rules. That is, a <gi>translateRule</gi> 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 <val>yes</val>.</p></item>
- </list>
- <exemplum xml:id="EX-its-and-existing-HTML5-markup">
- <head>The <ref target="#language-information">Language Information</ref>, <ref target="#idvalue">Id Value</ref>,
- <ref target="#elements-within-text">Elements within Text</ref> and <ref target="#trans-datacat">Translate</ref>
- ITS 2.0 data categories used with
- HTML native markup.</head>
- <p>The <code>html</code> element is interpreted to convey the
- <ref target="#language-information">Language Information</ref> value <val>en</val>.
- The <code>p</code> element is interpreted to
- convey the <ref target="#idvalue">Id Value</ref> of <val>p1</val>. The elements <code>em</code> and <code>img</code> are interpreted to be <code>withinText="yes"</code>. The <code>p</code> element and its children is set to be non-translatable via an <ptr target="#html5" type="bibref"/> <code>translate</code> attribute. Here the <code>alt</code> attribute, normally translatable by default, will also be non-translatable.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/html5/EX-its-and-existing-HTML5-markup.html"/>
- </exemplum>
- <p>There are also some HTML markup elements that have similar, but not always identical, roles and behaviour than certain ITS 2.0 data categories.
- For example, the HTML <code>dfn</code> element
- could be used to identify a term in the sense of the <ref target="#terminology">Terminology</ref> data
- category. However, this is not always the case and it depends on the
- intentions of the content author. To accomodate this situation, users
- of ITS 2.0 are encouraged to specifiy the association of existing HTML
- markup with a dedicated global rules file. For an example rules file see the
- <ref target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml">XML I18N Best Practices</ref> document.</p>
- </div>
- <div xml:id="html5-standoff-markup-explanation"><head>Standoff Markup in HTML5</head>
- <p>The <ref target="#provenance">Provenance</ref> and the <ref target="#lqissue">Localization Quality Issue</ref> data categories allow for using standoff markup. In HTML such standoff markup is put into a <code>script</code> element. The constraints for <ref target="#provenance-records-in-html5-constraint">Provenance standoff</ref> markup in HTML and <ref target="#loc-quality-issues-in-html5-constraint">Localization quality issue</ref> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <ptr target="#EX-provenance-html5-local-2" type="exref"/> and <ptr target="#EX-locQualityIssue-html5-local-2" type="exref"/>.</p></div>
- <div xml:id="usage-in-legacy-html">
- <head>Version of HTML</head>
- <p>ITS 2.0 does not define how to use ITS in HTML versions prior version 5. Users are
- encouraged to migrate their content to HTML5 or XHTML. While it is possible to use
- <code>its-*</code> attributes introduced for <ptr target="#html5" type="bibref"/> in older versions of HTML (such
- as 3.2 or 4.01) and pages using these attributes will work without any problems,
- <code>its-*</code> attributes will be marked as invalid in validators.</p>
- </div>
- </div>
+
+ <p><emph>Mappings:</emph> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <ptr target="#nif-reference" type="bibref"/> and links to guidance about ITS 2.0 and XLIFF. See <ptr target="#mapping-conversion" type="specref"/> for details.</p>
+
+ <p><emph>Changes to the conformance section</emph>: The <ptr target="#conformance" type="specref"/> 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 <ptr type="bibref" target="#nif-reference"/> has been added. For <ptr target="#html5" type="bibref"/>, a dedicated conformance section has been created. Finally, a conformance clause clarifying that Non-ITS elements and attributes found in ITS elements may be ignored has been added.</p>
<!-- http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jan/0018.html
-1. list of additional data categories (that's already in the current draft)
+1. list of additional data categories (that's already in the current draft)
2. modified data categories (e.g. "termConfidence" for term, or the model for Ruby)
@@ -665,106 +593,12 @@
- -->
-
- <div xml:id="additional-data-categories"><head>Additional data categories</head>
- <p>The following new data categories have been introduced in ITS 2.0.</p>
-
- <list type="unordered">
- <item><ref target="#domain">Domain</ref>: identify the topic or subject of the annotated content for translation related applications.</item>
-
-
-
- <item><ref target="#textanalysis">Text Analysis</ref>: annotate content with lexical or conceptual information for the purpose of contextual disambiguation.</item>
-
-
-
- <item><ref target="#LocaleFilter">Locale Filter</ref>: specify that a piece of content is only applicable to certain locales. </item>
-
-
-
- <item><ref target="#provenance">Provenance</ref>: communicate the identity of agents that have been involved in the translation of the content or the revision of the translated content.</item>
-
-
-
- <item><ref target="#externalresource">External Resource</ref>: indicate that a reference points to potentially translatable data in a resource outside the document. Examples of such resources are external images and audio or video files.</item>
-
-
-
- <item><ref target="#target-pointer">Target Pointer</ref>: associate a given piece of source content (i.e. the content to be translated) and its corresponding target content (i.e. the source content translated into a given target language).</item>
-
-
-
- <item><ref target="#idvalue">Id Value</ref>: identify a value that can be used as unique identifier for a given part of the content.
- </item>
-
-
- <item><ref target="#preservespace">Preserve Space</ref>: indicate how whitespace should be handled in content.</item>
-
-
- <item><ref target="#lqissue">Localization Quality Issue</ref>: describe the nature and severity of an error detected during a language-oriented quality assurance (QA) process.</item>
-
-
- <item><ref target="#lqrating">Localization Quality Rating</ref>: express an overall measurement of the localization quality of a document or an item in a document.</item>
-
-
- <item><ref target="#mtconfidence">MT Confidence</ref>: indicate the confidence that MT systems provide about their translation.
- </item>
-
-
- <item> <ref target="#allowedchars">Allowed Characters</ref>: specify the characters that are permitted in a given piece of content.</item>
-
- <item><ref target="#storagesize">Storage Size</ref>: specify the maximum storage size of a given content.</item></list>
- </div>
-
- <div xml:id="modified-datacategories"><head>Modified data categories</head>
-
- <p xml:id="ruby-in-its2">ITS 1.0 provided the <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation">Ruby data category</ref>. ITS 2.0 does not provide ruby since at the time of writing, because of the the <ref target="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</ref> was still under development. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p>
-
- <p>The <ref target="#directionality">Directionality</ref> data category reflects directionality markup in <ptr target="#html4" type="bibref"/>. The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.</p>
-
- </div>
-
- <div xml:id="additional-mechanisms"><head>Additional or modified mechanisms</head>
-
- <p>The following mechanisms from ITS 1.0 have been modified for all data categories.</p>
-
- <list>
- <item><p xml:id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <ref target="#basic-concepts-selection-global">global rules</ref>. ITS 2.0 allows for choosing the <ref target="#selectors">query language of selectors</ref>. 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></item>
- <item><p xml:id="parameters-in-selector">In global rules it is now possible to set <ref target="#its-param">variables for the selectors</ref> (XPath expression). The <gi>param</gi> element serves this purpose.</p></item>
- </list>
-
-
- <p xml:id="traceability">One mechanism has been added to ITS 2.0: <ref target="#its-tool-annotation">ITS Tools Annotation</ref>. It allows to associate processor information with the use of individual data categories in a document, independently from data category annotations themselves. The mechanism is mandatory for the <ref target="#mtconfidence">MT Confidence</ref> data category. For the <ref target="#terminology">Terminology</ref> and <ref target="#textanalysis">Text Analysis</ref> data categories it is mandatory if they provide confidence information, that is always tool related. Nevertheless, <ref target="#its-tool-annotation">ITS Tools Annotation</ref> can be used for all data categories.</p>
-
- </div>
-
-
-
- <div xml:id="mappings"><head>Mappings</head>
-
- <div xml:id="mapping-NIF"><head>ITS and RDF/NIF</head>
- <p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
- representations) that contain ITS metadata to the RDF-based format based on <ptr
- target="#nif-reference" type="bibref"/>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p>
- <p>The conversion <ref target="#conversion-to-nif">ITS 2.0 to NIF</ref> results in RDF triples that represent the textual content of the original document as RDF typed information and the ITS annotation as properties of those nodes defined in an <ref target="http://www.w3.org/2005/11/its/rdf#">ITS RDF vocabulary</ref>.</p>
-
- <p>The backconversion <ref target="#nif-backconversion">NIF to ITS 2.0</ref> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div>
-
- <div xml:id="mapping-XLIFF"><head>ITS and XLIFF</head>
- <p>The XML Localization Interchange File Format <ptr target="#xliff" type="bibref"/> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.0 usage scenarios <ptr target="#mlw-metadata-us-impl" type="bibref"/>. These usage scenarios involve: 1) the extraction of ITS meta-data from a source language file into XLIFF; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files. ITS 2.0 has no normative dependency on XLIFF, however a <ref target="http://www.w3.org/International/its/wiki/XLIFF_Mapping">non-normatie definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</ref> is being defined within the <ref target="http://www.w3.org/International/its/ig/">Internationalization Tag Set Interest Group</ref>.</p>
- </div>
-
- </div>
-
- <div xml:id="unicode-normalization"><head>Unicode normalization</head>
- <p>As a general guidance, implementations of ITS 2.0 should use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided by <ptr target="#charmod-norm" type="bibref"/>.</p>
- </div>
-
- <div xml:id="extended-implementation-hints"><head>Extended implementation hints</head> <p>tbd</p></div>
+ -->
</div>
-
+
+ <div xml:id="extended-implementation-hints"><head>Extended implementation hints</head>
+ <p xml:id="unicode-normalization">As a general guidance, implementations of ITS 2.0 should use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided by <ptr target="#charmod-norm" type="bibref"/>.</p></div>
</div>
<div xml:id="basic-concepts">
<head>Basic Concepts</head>
@@ -962,17 +796,179 @@
the same information must not appear at the same rule element.</p>
</div>
+ <div xml:id="specific-HTML-support"><head>Specific HTML support</head>
+
+ <p>For applying ITS 2.0 data categories to HTML, five aspects must be considered:</p>
+ <list type="ordered">
+ <item>referencing global rules</item>
+ <item>specifities of inserting local ITS 2.0 data categories</item>
+ <item>relationship between HTML markup and data categories,</item>
+ <item>standoff markup in HTML5</item>
+ <item>HTML version.</item>
+ </list>
+ <p>In the following sections these aspects are briefly discussed.</p>
+ <div xml:id="html5-reference-global-rules"><head>Referencing global rules</head>
+ <p>To account for the so-called “<ref target="#basic-concepts-selection-global">global
+ approach</ref>” in HTML, this specification (see <ptr target="#html5-global-rules" type="specref"/>) defines a link type for referring to external files
+ with global rules and an approach to have inline global rules in the HTML <code>script</code> element.
+ It is preferred to use external global rules linked via the <code>link</code> element than to have inline global rules in the HTML document.</p>
+ <exemplum xml:id="EX-translate-html5-global-1">
+ <head>Using ITS global rules in HTML</head>
+ <p>The <code>link</code> element points to the rules file
+ <code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
+ the ITS specific link relation <code>its-rules</code>.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/html5/EX-translate-html5-global-1.html" type="html5"/>
+ </exemplum>
+ <exemplum xml:id="EX-translate-html5-global-1-rules-file">
+ <head>ITS rules file linked from HTML</head>
+ <p>The rules file linked in <ptr target="#EX-translate-html5-global-1" type="exref"
+ />.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/html5/EX-translateRule-html5-1.xml"/>
+ </exemplum>
+ </div>
+ <div xml:id="html5-its-local-markup"><head>Specifities of inserting local ITS 2.0 data categories</head>
+ <p>In HTML, an ITS 2.0 local data category is realized with the specific prefix <code>its-*</code>.
+ The general mapping of the XML based ITS 2.0 attributes to their HTML <code>its-*</code> counterparts is defined in
+ <ptr target="#html5-local-attributes" type="specref"/>. An informative table in <ptr target="#list-of-elements-and-attributes" type="specref"/>
+ provides an overview of the mapping for all data categories.</p>
+ </div>
+ <div xml:id="html5-existing-markup-versus-its"><head>Relation between HTML markup and ITS 2.0 data categories</head>
+ <p>There are four ITS 2.0 data categories, which have direct counterparts
+ in HTML markup. For theses data categories, ITS 2.0 defines the following specific
+ behaviour:</p>
+ <list type="unordered">
+ <item><p>The <ref target="#language-information">Language Information</ref> data category has the HTML <code>lang</code>
+ attribute counterpart; in XHTML this is the <code>xml:lang</code> attribute. These attributes act as
+ local markup for the <ref target="#language-information">Language Information</ref> data category in HTML and
+ take <ref target="#selection-precedence">precedence</ref> over language information conveyed via a global <gi>langRule</gi>.</p></item>
+ <item><p>The <ref target="#idvalue">Id Value</ref> data category has the HTML or XHTML <code>id</code> attribute.
+ This attribute acts as local markup for the <ref target="#idvalue">Id Value</ref> data category in HTML and take <ref target="#selection-precedence">precedence</ref> over
+ id information conveyed via a global <gi>idValueRule</gi>.</p></item>
+ <item><p>The <ref target="#elements-within-text">Elements within Text</ref> data category has a set of HTML
+ elements defined as <ref target="http://www.w3.org/TR/html51/dom.html#phrasing-content-1">phrasing content</ref>. In the absence of an
+ <ref target="#elements-within-text">Elements within Text</ref> local attribute or global rules selecting the
+ element in question, these elements are always interpreted as
+ <code>withinText="yes"</code> by default, except for the elements <gi>iframe</gi>, <gi>noscript</gi>, <gi>script</gi>
+ and <gi>textarea</gi> which are interpreted as <code>withinText="nested"</code>.</p></item>
+ <item xml:id="translate-in-html5"><p>The <ref target="#trans-datacat">Translate</ref> data category has a direct counterpart in
+ <ptr target="#html5" type="bibref"/>, namely the HTML5
+ <code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <ref target="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">the HTML5 definition</ref>. The <ptr target="#html5" type="bibref"/> definition also applies to nodes selected via global rules. That is, a <gi>translateRule</gi> 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 <val>yes</val>.</p></item>
+ </list>
+ <exemplum xml:id="EX-its-and-existing-HTML5-markup">
+ <head>The <ref target="#language-information">Language Information</ref>, <ref target="#idvalue">Id Value</ref>,
+ <ref target="#elements-within-text">Elements within Text</ref> and <ref target="#trans-datacat">Translate</ref>
+ ITS 2.0 data categories used with
+ HTML native markup.</head>
+ <p>The <code>html</code> element is interpreted to convey the
+ <ref target="#language-information">Language Information</ref> value <val>en</val>.
+ The <code>p</code> element is interpreted to
+ convey the <ref target="#idvalue">Id Value</ref> of <val>p1</val>. The elements <code>em</code> and <code>img</code> are interpreted to be <code>withinText="yes"</code>. The <code>p</code> element and its children is set to be non-translatable via an <ptr target="#html5" type="bibref"/> <code>translate</code> attribute. Here the <code>alt</code> attribute, normally translatable by default, will also be non-translatable.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/html5/EX-its-and-existing-HTML5-markup.html"/>
+ </exemplum>
+ <p>There are also some HTML markup elements that have similar, but not always identical, roles and behaviour than certain ITS 2.0 data categories.
+ For example, the HTML <code>dfn</code> element
+ could be used to identify a term in the sense of the <ref target="#terminology">Terminology</ref> data
+ category. However, this is not always the case and it depends on the
+ intentions of the content author. To accomodate this situation, users
+ of ITS 2.0 are encouraged to specifiy the association of existing HTML
+ markup with a dedicated global rules file. For an example rules file see the
+ <ref target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml">XML I18N Best Practices</ref> document.</p>
+ </div>
+ <div xml:id="html5-standoff-markup-explanation"><head>Standoff Markup in HTML5</head>
+ <p>The <ref target="#provenance">Provenance</ref> and the <ref target="#lqissue">Localization Quality Issue</ref> data categories allow for using standoff markup. In HTML such standoff markup is put into a <code>script</code> element. The constraints for <ref target="#provenance-records-in-html5-constraint">Provenance standoff</ref> markup in HTML and <ref target="#loc-quality-issues-in-html5-constraint">Localization quality issue</ref> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <ptr target="#EX-provenance-html5-local-2" type="exref"/> and <ptr target="#EX-locQualityIssue-html5-local-2" type="exref"/>.</p></div>
+ <div xml:id="usage-in-legacy-html">
+ <head>Version of HTML</head>
+ <p>ITS 2.0 does not define how to use ITS in HTML versions prior version 5. Users are
+ encouraged to migrate their content to HTML5 or XHTML. While it is possible to use
+ <code>its-*</code> attributes introduced for <ptr target="#html5" type="bibref"/> in older versions of HTML (such
+ as 3.2 or 4.01) and pages using these attributes will work without any problems,
+ <code>its-*</code> attributes will be marked as invalid in validators.</p>
+ </div>
+ </div>
+
+ <div xml:id="traceability"><head>Traceability</head>
+ <p>The <ref target="#its-tool-annotation">ITS Tools Annotation</ref> mechanism allows to associate processor information with the use of individual data categories in a document, independently from data category annotations themselves. The mechanism associates identifiers for tools and data categories via the <att>annotatorsRef</att> attribute (or <att>annotators-ref</att> in <ptr target="#html5" type="bibref"/>) and is mandatory for the <ref target="#mtconfidence">MT Confidence</ref> data category. For the <ref target="#terminology">Terminology</ref> and <ref target="#textanalysis">Text Analysis</ref> data categories it is mandatory if they provide confidence information, that is always tool related. Nevertheless, <ref target="#its-tool-annotation">ITS Tools Annotation</ref> can be used for all data categories. <ptr target="#EX-its-tool-annotation-2" type="exref"/> demonstrates the usage including several data categories.</p></div>
<div xml:id="mapping-conversion">
<head>Mapping and conversion</head>
- <p>tbd - here <ptr target="#mappings" type="specref"/>.</p>
+
+ <div xml:id="mapping-NIF"><head>ITS and RDF/NIF</head>
+ <p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
+ representations) that contain ITS metadata to the RDF-based format based on <ptr
+ target="#nif-reference" type="bibref"/>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p>
+ <p>The conversion <ref target="#conversion-to-nif">ITS 2.0 to NIF</ref> results in RDF triples that represent the textual content of the original document as RDF typed information and the ITS annotation as properties of those nodes defined in an <ref target="http://www.w3.org/2005/11/its/rdf#">ITS RDF vocabulary</ref>.</p>
+
+ <p>The backconversion <ref target="#nif-backconversion">NIF to ITS 2.0</ref> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div>
+
+ <div xml:id="mapping-XLIFF"><head>ITS and XLIFF</head>
+ <p>The XML Localization Interchange File Format <ptr target="#xliff" type="bibref"/> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.0 usage scenarios <ptr target="#mlw-metadata-us-impl" type="bibref"/>. These usage scenarios involve: 1) the extraction of ITS meta-data from a source language file into XLIFF; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files. ITS 2.0 has no normative dependency on XLIFF, however a <ref target="http://www.w3.org/International/its/wiki/XLIFF_Mapping">non-normative definition f how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</ref> is being defined within the <ref target="http://www.w3.org/International/its/ig/">Internationalization Tag Set Interest Group</ref>.</p>
+ </div>
+
</div>
- <div xml:id="tools-information">
- <head>ITS Tools Annotation</head>
- <p>tbd - here partially content of <ptr target="#additional-mechanisms" type="specref"/>.</p>
+
+ <div xml:id="datacategories-summary"><head>Summary: ITS 2.0 data categories</head>
+
+ <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 <ptr target="#high-level-differences-between-1.0-and-2.0" type="specref"/>.</p>
+
+
+ <list type="unordered">
+ <item><ref target="#trans-datacat">Translate</ref>: express information about whether a selected piece of content should be translated or not.</item>
+ <item><ref target="#locNote-datacat">Localization Note</ref>: communicate notes to localizers about a particular item of content.</item>
+ <item><ref target="#terminology">Terminology</ref>: mark terms and optionally associate them with information, such as definitions or references to a term data base.</item>
+ <item><ref target="#directionality">Directionality</ref>: specify the base writing direction of blocks, embeddings and overrides for the Unicode bidirectional algorithm.</item>
[68 lines skipped]
Received on Sunday, 9 June 2013 21:47:08 UTC