- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Tue, 18 Jun 2013 21:05:45 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv5693
Added Files:
its20-before-dublinJune13-f2f.html
Removed Files:
its20-for-editing-sec1-sec2.html
its20-for-editing-sec1-sec2.odd
Log Message:
removing unused files, adding temporary its20 HTML file that is the version before the f2f editing session
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-before-dublinJune13-f2f.html 2013/06/18 21:05:45 NONE
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-before-dublinJune13-f2f.html 2013/06/18 21:05:45 1.1
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/><title>Internationalization Tag Set (ITS) Version 2.0 -- (Editors' copy)</title><style type="text/css" xml:space="preserve">
</style><link rel="stylesheet" href="local.css" type="text/css"/><link rel="stylesheet" type="text/css" href="base.css"/></head><body><div class="head">
<h1><a name="title" id="title" shape="rect"/>Internationalization Tag Set (ITS) Version 2.0</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Copy</h2><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a> © 2013 <a href="http://www.w3.org/" shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>, <a href="http://ev.buaa.edu.cn/" shape="rect">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer" shape="rect">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks" shape="rect">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents" shape="rect">document use</a> rules apply.</p>/div><hr/><div>
<h2><a name="abstract" id="abstract" shape="rect"/>Abstract</h2><p>The technology described in this document - the <em>Internationalization Tag Set (ITS)
2.0</em> - enhances the foundation to integrate automated processing of human language
into core Web technologies. ITS 2.0 bears many commonalities with is predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a> but provides additional
concepts that are designed to foster the automated creation and processing of multilingual
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
processing based on the XML Localization Interchange File Format (XLIFF), as well as the
Natural Language Processing Interchange Format (NIF).</p></div><div>
<h2><a name="status" shape="rect">Status of this Document</a></h2><p><strong>This document is an editors' copy that has no official
standing.</strong> Last modified: 06/17/2013 01:18:39.</p></div><div class="toc">
<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>
<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-datacategories" shape="rect">Data Categories</a></div>
<div class="toc2">2.2 <a href="#basic-concepts-selection" shape="rect">Selection</a><div class="toc3">2.2.1 <a href="#basic-concepts-selection-local" shape="rect">Local Approach</a></div>
<div class="toc3">2.2.2 <a href="#basic-concepts-selection-global" shape="rect">Global Approach</a></div>
</div>
<div class="toc2">2.3 <a href="#basic-concepts-overinher" shape="rect">Overriding, Inheritance and Defaults</a></div>
<div class="toc2">2.4 <a href="#basic-concepts-addingpointing" shape="rect">Adding Information or Pointing to Existing Information</a></div>
<div class="toc2">2.5 <a href="#specific-HTML-support" shape="rect">Specific HTML support</a><div class="toc3">2.5.1 <a href="#html5-global-approach" shape="rect">Global approach in HTML5</a></div>
<div class="toc3">2.5.2 <a href="#html5-its-local-markup" shape="rect">Local approach</a></div>
<div class="toc3">2.5.3 <a href="#html5-existing-markup-versus-its" shape="rect">HTML markup with ITS 2.0 counterparts</a></div>
<div class="toc3">2.5.4 <a href="#html5-standoff-markup-explanation" shape="rect">Standoff Markup in HTML5</a></div>
<div class="toc3">2.5.5 <a href="#usage-in-legacy-html" shape="rect">Version of HTML</a></div>
</div>
<div class="toc2">2.6 <a href="#traceability" shape="rect">Traceability</a></div>
<div class="toc2">2.7 <a href="#mapping-conversion" shape="rect">Mapping and conversion</a><div class="toc3">2.7.1 <a href="#mapping-NIF" shape="rect">ITS and RDF/NIF</a></div>
<div class="toc3">2.7.2 <a href="#mapping-XLIFF" shape="rect">ITS and XLIFF</a></div>
</div>
<div class="toc2">2.8 <a href="#implementing-its20" shape="rect">ITS 2.0 Implementations and Conformance</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>
<div class="toc2">3.3 <a href="#def-selection" shape="rect">Selection</a></div>
<div class="toc2">3.4 <a href="#def-local-attributes" shape="rect">ITS Local Attributes</a></div>
<div class="toc2">3.5 <a href="#def-rule-elements" shape="rect">Rule Elements</a></div>
<div class="toc2">3.6 <a href="#iri-usage" shape="rect">Usage of Internationalized Resource Identifiers in ITS</a></div>
<div class="toc2">3.7 <a href="#def-html" shape="rect">The Term HTML</a></div>
<div class="toc2">3.8 <a href="#def-css-selector" shape="rect">The Term CSS Selectors</a></div>
</div>
<div class="toc1">4 <a href="#conformance" shape="rect">Conformance</a><div class="toc2">4.1 <a href="#conformance-product-schema" shape="rect">Conformance Type 1: ITS Markup Declarations</a></div>
<div class="toc2">4.2 <a href="#conformance-product-processing-expectations" shape="rect">Conformance Type 2: The Processing Expectations for ITS Markup</a></div>
<div class="toc2">4.3 <a href="#conformance-product-html-processing-expectations" shape="rect">Conformance Type 3: Processing Expectations for ITS Markup in HTML</a></div>
<div class="toc2">4.4 <a href="#conformance-product-html5-its" shape="rect">Conformance Type 4: Markup conformance for HTML5+ITS documents</a></div>
</div>
<div class="toc1">5 <a href="#its-processing" shape="rect">Processing of ITS information</a><div class="toc2">5.1 <a href="#its-version-attribute" shape="rect">Indicating the Version of ITS</a></div>
<div class="toc2">5.2 <a href="#datacategory-locations" shape="rect">Locations of Data Categories</a><div class="toc3">5.2.1 <a href="#selection-global" shape="rect">Global, Rule-based Selection</a></div>
<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="#d0e2582" shape="rect">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors" shape="rect">CSS Selectors</a></div>
<div class="toc3">5.3.4 <a href="#d0e2827" shape="rect">Additional query languages</a></div>
<div class="toc3">5.3.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>
<div class="toc2">5.5 <a href="#selection-precedence" shape="rect">Precedence between Selections</a></div>
<div class="toc2">5.6 <a href="#associating-its-with-existing-markup" shape="rect">Associating ITS Data Categories with Existing Markup</a></div>
<div class="toc2">5.7 <a href="#conversion-to-nif" shape="rect">Conversion to NIF</a></div>
<div class="toc2">5.8 <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a></div>
</div>
<div class="toc1">6 <a href="#html5-markup" shape="rect">Using ITS Markup in HTML</a><div class="toc2">6.1 <a href="#html5-local-attributes" shape="rect">Mapping of Local Data Categories to HTML</a></div>
<div class="toc2">6.2 <a href="#html5-global-rules" shape="rect">Global rules</a></div>
<div class="toc2">6.3 <a href="#html5-standoff-markup" shape="rect">Standoff Markup in HTML</a></div>
<div class="toc2">6.4 <a href="#html5-selection-precedence" shape="rect">Precedence between Selections</a></div>
</div>
<div class="toc1">7 <a href="#xhtml5-markup" shape="rect">Using ITS Markup in XHTML</a></div>
<div class="toc1">8 <a href="#datacategory-description" shape="rect">Description of Data Categories</a><div class="toc2">8.1 <a href="#datacategories-defaults-etc" shape="rect">Position, Defaults, Inheritance and Overriding of Data Categories</a></div>
<div class="toc2">8.2 <a href="#trans-datacat" shape="rect">Translate</a><div class="toc3">8.2.1 <a href="#translatability-definition" shape="rect">Definition</a></div>
<div class="toc3">8.2.2 <a href="#translatability-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.3 <a href="#locNote-datacat" shape="rect">Localization Note</a><div class="toc3">8.3.1 <a href="#locNote-definition" shape="rect">Definition</a></div>
<div class="toc3">8.3.2 <a href="#locNote-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.4 <a href="#terminology" shape="rect">Terminology</a><div class="toc3">8.4.1 <a href="#terminology-definition" shape="rect">Definition</a></div>
<div class="toc3">8.4.2 <a href="#terminology-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.5 <a href="#directionality" shape="rect">Directionality</a><div class="toc3">8.5.1 <a href="#directionality-definition" shape="rect">Definition</a></div>
<div class="toc3">8.5.2 <a href="#directionality-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.6 <a href="#language-information" shape="rect">Language Information</a><div class="toc3">8.6.1 <a href="#langinfo-definition" shape="rect">Definition</a></div>
<div class="toc3">8.6.2 <a href="#langinfo-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.7 <a href="#elements-within-text" shape="rect">Elements Within Text</a><div class="toc3">8.7.1 <a href="#within-text-definition" shape="rect">Definition</a></div>
<div class="toc3">8.7.2 <a href="#within-text-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.8 <a href="#domain" shape="rect">Domain</a><div class="toc3">8.8.1 <a href="#domain-definition" shape="rect">Definition</a></div>
<div class="toc3">8.8.2 <a href="#domain-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.9 <a href="#textanalysis" shape="rect">Text Analysis</a><div class="toc3">8.9.1 <a href="#textanalysis-definition" shape="rect">Definition</a></div>
<div class="toc3">8.9.2 <a href="#textanalysis-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.10 <a href="#LocaleFilter" shape="rect">Locale Filter</a><div class="toc3">8.10.1 <a href="#LocaleFilter-definition" shape="rect">Definition</a></div>
<div class="toc3">8.10.2 <a href="#LocaleFilter-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.11 <a href="#provenance" shape="rect">Provenance</a><div class="toc3">8.11.1 <a href="#provenance-definition" shape="rect">Definition</a></div>
<div class="toc3">8.11.2 <a href="#provenance-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.12 <a href="#externalresource" shape="rect">External Resource</a><div class="toc3">8.12.1 <a href="#externalresource-definition" shape="rect">Definition</a></div>
<div class="toc3">8.12.2 <a href="#externalresource-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.13 <a href="#target-pointer" shape="rect">Target Pointer</a><div class="toc3">8.13.1 <a href="#target-pointer-definition" shape="rect">Definition</a></div>
<div class="toc3">8.13.2 <a href="#target-pointer-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.14 <a href="#idvalue" shape="rect">ID Value</a><div class="toc3">8.14.1 <a href="#idvalue-definition" shape="rect">Definition</a></div>
<div class="toc3">8.14.2 <a href="#idvalue-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.15 <a href="#preservespace" shape="rect">Preserve Space</a><div class="toc3">8.15.1 <a href="#preservespace-definition" shape="rect">Definition</a></div>
<div class="toc3">8.15.2 <a href="#preservespace-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.16 <a href="#lqissue" shape="rect">Localization Quality Issue</a><div class="toc3">8.16.1 <a href="#lqissue-definition" shape="rect">Definition</a></div>
<div class="toc3">8.16.2 <a href="#lqissue-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.17 <a href="#lqrating" shape="rect">Localization Quality Rating</a><div class="toc3">8.17.1 <a href="#lqrating-definition" shape="rect">Definition</a></div>
<div class="toc3">8.17.2 <a href="#lqrating-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.18 <a href="#mtconfidence" shape="rect">MT Confidence</a><div class="toc3">8.18.1 <a href="#mtconfidence-definition" shape="rect">Definition</a></div>
<div class="toc3">8.18.2 <a href="#mtconfidence-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.19 <a href="#allowedchars" shape="rect">Allowed Characters</a><div class="toc3">8.19.1 <a href="#allowedchars-definition" shape="rect">Definition</a></div>
<div class="toc3">8.19.2 <a href="#allowedchars-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">8.20 <a href="#storagesize" shape="rect">Storage Size</a><div class="toc3">8.20.1 <a href="#storagesize-definition" shape="rect">Definition</a></div>
<div class="toc3">8.20.2 <a href="#storagesize-implementation" shape="rect">Implementation</a></div>
</div>
</div>
</div>
<h3><a name="appendices" id="appendices" shape="rect"/>Appendices</h3><div class="toc1">A <a href="#normative-references" shape="rect">References</a></div>
<div class="toc1">B <a href="#its-mime-type" shape="rect">Internationalization Tag Set (ITS) MIME Type</a></div>
<div class="toc1">C <a href="#lqissue-typevalues" shape="rect">Values for the Localization Quality Issue Type</a></div>
<div class="toc1">D <a href="#its-schemas" shape="rect">Schemas for ITS</a></div>
<div class="toc1">E <a href="#informative-references" shape="rect">References</a> (Non-Normative)</div>
<div class="toc1">F <a href="#nif-backconversion" shape="rect">Conversion NIF2ITS</a> (Non-Normative)</div>
<div class="toc1">G <a href="#list-of-elements-and-attributes" shape="rect">List of ITS 2.0 Global Elements and Local Attributes</a> (Non-Normative)</div>
<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><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
original
language) for one locale (e.g. the French-speaking part of
Canada) is often made available in additional languages or adapted
with regard to other cultural aspects. A prevailing paradigm for
the
corresponding approach to multilingual production in many cases encompasses
three phases: internationalization, translation, and localization (see the <a href="http://www.w3.org/International/questions/qa-i18n/" shape="rect"> W3C's Internationalization Q&A</a>
for more information related to these concepts).
</p><p>
From the viewpoints of feasibility, cost, and efficiency, it is
important
that the original material should be suitable for
downstream
phases such as translation. This
is
achieved by
appropriate design and
development.
The corresponding
phase is
referred to as
internationalization.
A proprietary XML vocabulary may for example may be internationalized by defining special markup to specify directionality in mixed direction text.
</p><p>During the translation phase, the meaning of a source language
text
is
analyzed, and a target language text that is equivalent in
meaning
is
determined. In order to promote or ensure a translation's
fidelity,
national or international laws may for example regulate
linguistic
dimensions like mandatory terminology or standard
phrases.
</p><p>
Although an agreed-upon definition of the localization phase is
missing,
this phase is usually seen as encompassing activities such as
creating locale-specific content (e.g. adding a link for a
country-specific reseller), or modifying functionality (e.g. to
establish a fit with country-specific regulations for financial
reporting).
Sometimes, the insertion of special markup to support a
local language
or script is also subsumed under the localization phase.
For
example, people authoring in languages such as Arabic, Hebrew,
Persian or Urdu need special markup to specify directionality in
mixed
direction text.
</p><p>
The technology described in this document - the
<em>Internationalization Tag Set (ITS)
2.0</em>
addresses some of the challenges and opportunities related to
internationalization,
translation, and localization. ITS 2.0 in
particular contributes to concepts in the realm of meta data for
internationalization,
translation, and localization related to core Web
technologies such as XML. ITS does for example assist in production scenarios in which parts of an
XML-based document should not be translated. ITS 2.0 bears many
commonalities with is
predecessor,
<a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a>
but provides additional
concepts that are designed to foster enhanced
automated processing - e.g. based on language technology such as
entity recognition - related to multilingual
Web content.
</p><p>
Like ITS 1.0, ITS 2.0
both identifies
concepts (such as
“Translate”
), and
defines implementations of these concepts (termed “ITS data
categories”)
as a set of elements and attributes called the
<em>Internationalization Tag Set
(ITS)</em>
. The
definitions of ITS elements and attributes are provided in the
form of RELAX NG
<a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>
(normative).
Since one major step from ITS 1.0 to ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between ITS markup and the various HTML flavors. Furthermore, ITS 2.0 suggests when and how to leverage processing based on the XML Localization Interchange File Format (<a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>), as well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document must not be translated.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content must not be translated</div><p>In this document it is difficult to distinguish between hose <code>string</code> elements that should be translated and those that must not be translated. Explicit meta data is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
<strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><arguments></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"></arguments></strong>
<strong class="hl-tag" style="color: #000096"><variables></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>Corporate Policy<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"></variables></strong>
<strong class="hl-tag" style="color: #000096"><keyvalue_pairs></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>Page<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>ABC Corporation - Policy Repository<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>Footer_Last<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>Pages<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>bgColor<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>NavajoWhite<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>title<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>List of Available Policies<strong class="hl-tag" style="color: #000096"></string></strong>
<strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
<strong class="hl-tag" style="color: #000096"></section></strong>
<strong class="hl-tag" style="color: #000096"></resources></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml" shape="rect">examples/xml/EX-motivation-its-1.xml</a>]</p></div><p>ITS proposes several mechanisms which differ amongst others in terms of the usage scenario/user types for which the mechanism is most suitable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-2" id="EX-motivation-its-2" shape="rect"/>Example 2: Document that uses two different ITS mechanisms to indicate that some parts must not be translated.</div><p>ITS provides two mechanisms to explicitly associate meta data with one or more pieces of content (e.g. XML nodes): a <a href="#basic-concepts-selection-global" shape="rect">global</a>, rule-based approach as well as a <a href="#basic-concepts-selection-local" shape="rect">local</a>, attribute-based approached). Here, for instance, a rule first specifies that no <code>data</code> element must be translated; later, an attribute <a href="#basic-concepts-overinher" shape="rect">overwrites</> this rule for two of the <code>data</code> elements of type "text".</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><dialogue</strong> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-gb"</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><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//data"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"></its:rules></strong>
<strong class="hl-tag" style="color: #000096"><rsrc</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"123"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"456"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"image"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span><strong class="hl-tag" style="color: #000096">></strong>images/cancel.gif<strong class="hl-tag" style="color: #000096"></data></strong>
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">></strong>12,20<strong class="hl-tag" style="color: #000096"></data></strong>
<strong class="hl-tag" style="color: #000096"></component></strong>
<strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"789"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"caption"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Cancel<strong class="hl-tag" style="color: #000096"></data></strong>
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">></strong>60,40<strong class="hl-tag" style="color: #000096"></data></strong>
<strong class="hl-tag" style="color: #000096"></component></strong>
<strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"792"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"string"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Number of files: <strong class="hl-tag" style="color: #000096"></data></strong>
<strong class="hl-tag" style="color: #000096"></component></strong>
<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 are simple:</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 associate meta data with 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. term already marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <a href="http://www.w3.org/International/its/ig/" 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 for possible future versions of ITS:</p><ol class="depth1"><li><p>“Context” = What specific related information might be helpful?</p></li><li><p>“Automated Languae” = Does this content lend itself 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 (multilingual) Natural Language Processing contexts</p></li><li><p>Computer-supported linguistic quality assurance</p></li><li><p>Content Management and translation platforms</p></li><li><p>Cross-language scenarios</p></li><li><p>Content enrichment</p></li><li><p>Support for W3C provenance <a title="" href="#prov-dm" shape="rect">[PROV-DM]</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, rliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data scenarios.</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 multilingual 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 facilitate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a>, <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>) that are interested for example in information sharing, and ossless round tripping of meta data in localization workflows.</p></li></ul><p>One example outcome of the resulting synergies is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> 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 <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 <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a>
<a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “ITS is a technology to easily create XML which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multi-lingual production.</p><ul><li><p>Static mono-lingual (the area for example of content authors): This part of the content has the directionality “right-to-left”.</p></li><li><p>Dynamic multi-lingual: (the area for example of machine translation systems): This part of the content must not be translated.</p></li></ul><p>Although ITS 1.0 made no assumptions about possible phases in a multilingual production 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 translation 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><>The document <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a> 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 <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 non-human actors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity identifiers/disambiguators to the same level. This change amongst others is reflected by the ITS 2.0 <a href="#its-tool-annotation" shape="rect">Tool Annotation</a> which allows systems to record thatthey 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><p>The differences between ITS 1.0 and ITS 2.0 can be summarized as follows.</p><p>
<em>Coverage of <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>: </em>ITS 1.0 can 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> are given in <a class="section-ref" href="#specific-HTML-support" shape="rect">Section 2.5: Specific HTML support</a>.</p><p>
<em>Addition of data categories</em>: ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 2.0 data categories are given in <a class="section-ref" href="#basic-concepts-datacategories" shape="rect">Section 2.1: Data Categories</a>.</p><p>
<em>Modification of 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, the Ruby data category possibly will be re-introduced, in a subsequent version of ITS.</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, tese enhancements 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 or added to ITS 2.0.</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global" shape="rect">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors" shape="rect">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param" shape="rect">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has a <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="sectionref" href="#traceability" shape="rect">Section 2.6: Traceability</a> for details.</p></li></ul><p>
<em>Mappings:</em> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <a title="" href="#nif-reference" shape="rect">[NIF]</a> and links to guidance about how to relate ITS 2.0 to XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">Section 2.7: Mapping and conversion</a> for details.</p><p>
<em>Changes to the conformance section</em>: The <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed, and a conformance clause related to processing <a title="" href="#nif-reference" shape="rect">[NIF]</a> has been added. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, a dedicated conformance section has been created. Finally, a conformance clause related to Non-ITS elements and attributes has been added.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.5 Extended implementation hints</h3><p id="unicode-normalization">As a general guidance, implementations of ITS 2.0 should use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</a>.</p></div></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts" id="basic-concepts" shape="rect"/>2 Basic Concepts</h2><p>
<em>This section is informative.</em>
</p><p>The purpose of this section is to provide basic knowledge about how ITS 2.0 “works”. Detailed knowledge (including formal definitions) is given in the subsequent sections.</p><div class="div2">
<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-datacategories" id="basic-concepts-datacategories" shape="rect"/>2.1 Data Categories</h3><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 content.</p><p>
<a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> defines data categories. It also describes their implementation, that is: ways to use them for example in an XML context. The motivation for separating data category definitions from their implementation is that only this way the reality can be reflected since data categories can be implemented</p><ul><li><p>In various types of content (XML in general or <a href="#specific-HTML-support" shape="rect">HTML</a>).</p></li><li><p>For a single piece of content, e.g. a <code>p</code> element. This is the so-called <a href="#basic-concepts-selection-local" shape="rect">local approach</a>.</p></li><li><p>for several pieces of content in one document or even a set of documents. This is the so-called <a href="#basic-concepts-selection-global" shape="rect">global approach</a>.</p></li><li><p>For a complete markup vocabulary. This is done by adding <a href="#its-schemas" shape="rect">ITS markp declarations</a> to the schema for the vocabulary.</p></li></ul><p>ITS 2.0 provides the following data categories, using most of the existing ITS 1.0 data categories and adding new ones. Modifications of existing ITS 1.0 data categories are summarized in <a class="section-ref" href="#high-level-differences-between-1.0-and-2.0" shape="rect">Section 1.4: High-level differences between ITS 1.0 and ITS 2.0</a>.</p><ul><li><p><a href="#trans-datacat" shape="rect">Translate</a>: 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>: mark 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, embddings 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 (e.g. 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 hav been involved processing content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate reference points in a resource outside the document that need to be considered during localization or translation. 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 the markup node of a given source content (i.e. the content to be translated) and the markup node of its corresponding target content (i.e. the source content translated into a given target language). This is relevant for formats that hold the same content in different languages inside a single document.</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>: 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="basic-concepts-selection" id="basic-concepts-selection" shape="rect"/>2.2 Selection</h3><p>Information (e.g. “translate this”) captured by an ITS data category always pertains to one or more XML or HTML nodes, primarily element and attribute nodes. In a sense, the relevant node(s) get “selected”. Selection may be explicit or implicit. ITS distinguishes two mechanisms for explicit selection: (1) local approach, and (2) global approach (via <code class="its-elem-markup">rules</code>). Both local and global approach can interact with each other, and with additional ITS dimensions such as inheritance and defaults.</p><p>The mechanisms defined for ITS selection resemble those defined in <a title="Cascading Style Sheets,
 level 2 revision 1 CSS 2.1 Specification" href="#css2-1" shape="rect">[CSS 2.]</a>. The local approach can be compared to the
<code>style</code> attribute in HTML/XHTML, and the global approach is similar to the <code>style</code> element in HTML/XHTML.</p><ul><li><p>the local approach puts ITS markup in the relevant element of the host vocabulary (e.g. the <code>author</code> element in DocBook)</p></li><li><p>the global, <a href="#selection-global" shape="rect">rule-based approach</a> puts the ITS
markup in elements defined by ITS itself (namely the <code class="its-elem-markup">rules</code> element)</p></li></ul><p>ITS usually uses XPath in rules for identifying nodes although CSS Selectors and other query languages can in addition be implemented by applications.</p><p>ITS 2.0 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 provide more details about the distinction between the local and global approach, using the <a href="#trans-datacat" shape="rect">Translate</a> data category as example.</p><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"/>2.2.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 3</a> shows how a content author may use the ITS <code class="its-attr-markup">translate</code> attribute to indicate that all content inside the <code>author</code> element should be protected from translation (i.e. must not be translated). Translation tools that are aware of the meaning of the attribute can protect the relevant content from being translated (possibly still allowing translators to see the protected content as context information).</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 3: ITS markup on elements in an XML document (local approach) </di><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
<span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
<span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"5.0"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><info></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>An example article<strong class="hl-tag" style="color: #000096"></title></strong>
<strong class="hl-tag" style="color: #000096"><author</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><personname></strong>
<strong class="hl-tag" style="color: #000096"><firstname></strong>John<strong class="hl-tag" style="color: #000096"></firstname></strong>
<strong class="hl-tag" style="color: #000096"><surname></strong>Doe<strong class="hl-tag" style="color: #000096"></surname></strong>
[5618 lines skipped]
Received on Tuesday, 18 June 2013 21:05:48 UTC