- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Sun, 16 Jun 2013 23:18:40 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv4274
Modified Files:
its20.html its20.odd
Log Message:
merged sec1-2 into its20.odd and re-generated its20.html
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/13 21:41:34 1.446
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/16 23:18:39 1.447
@@ -16,31 +16,29 @@
<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: <script type="text/javascript" xml:space="preserve">
document.write(document.lastModified);</script>.</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="#relation-to-its10-and-new-principles" shape="rect">Relation to ITS 1.0 and New Principles</a><div class="toc3">1.1.1 <a href="#relation-to-its10" shape="rect">Relation to ITS 1.0</a></div>
-<div class="toc3">1.1.2 <a href="#ruby-in-its2" shape="rect">Ruby and ITS 2.0</a></div>
-<div class="toc3">1.1.3 <a href="#new-principles" shape="rect">New Principles</a></div>
+<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="toc2">1.2 <a href="#motivation-its" shape="rect">Motivation for ITS</a><div class="toc3">1.2.1 <a href="#motivation-its-issues" shape="rect">Typical Problems</a></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">1.3 <a href="#users-usage" shape="rect">Users and Usages of ITS</a><div class="toc3">1.3.1 <a href="#potential-users" shape="rect">Potential Users of ITS</a></div>
-<div class="toc3">1.3.2 <a href="#ways-to-use-its" shape="rect">Ways to Use ITS</a></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">1.4 <a href="#usage-in-html" shape="rect">Usage in HTML</a><div class="toc3">1.4.1 <a href="#html5-reference-global-rules" shape="rect">Referencing global rules</a></div>
-<div class="toc3">1.4.2 <a href="#html5-its-local-markup" shape="rect">Specifities of inserting local ITS 2.0 data categories</a></div>
-<div class="toc3">1.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">1.4.4 <a href="#html5-standoff-markup-explanation" shape="rect">Standoff Markup in HTML5</a></div>
-<div class="toc3">1.4.5 <a href="#usage-in-legacy-html" shape="rect">Version of HTML</a></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">1.5 <a href="#its-and-xliff" shape="rect">ITS and XLIFF</a></div>
-<div class="toc2">1.6 <a href="#out-of-scope" shape="rect">Out of Scope</a></div>
-<div class="toc2">1.7 <a href="#design-decisions" shape="rect">Important Design Principles</a></div>
-<div class="toc2">1.8 <a href="#its2-and-unicode-normalization" shape="rect">ITS 2.0 and Unicode Normalization</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 and Inheritance</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.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>
@@ -54,16 +52,16 @@
<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-type-html5-its" shape="rect">Conformance Type 4: Markup conformance for HTML5+ITS documents</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="#d0e2426" shape="rect">XPath 1.0</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="#d0e2671" shape="rect">Additional query languages</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>
@@ -149,53 +147,187 @@
<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><p>ITS 2.0 is a technology to add metadata to Web content, for the benefit of localization,
- language technologies, and internationalization. The ITS 2.0 specification both identifies
- concepts (such as “Translate”) that are important for internationalization and
- localization, 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 document provides implementations for HTML, serializations in <a title="" href="#nif-reference" shape="rect">[NIF]</a> (NLP Interchange Format), and provides definitions of ITS elements and attributes in the form of XML Schema <a title="XML Schema Part 1:
 Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.</p><p>This document aims to realize many of the ideas formulated in the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/" shape="rect">ITS 2.0 Requirements
- document</a>, in <a title="Internationalization and
 Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a> and <a title="Requirements for Localizable
 DTD Design" href="#reqlocdtd" shape="rect">[Localizable DTDs]</a>.</p><p>Not all requirements listed there are addressed in this document. Those which are not
- addressed here are either covered in <a title="Best
 Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>
- (potentially in an as yet unwritten best practice document on multilingual Web content),
- or may be addressed in a future version of this specification.</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="relation-to-its10-and-new-principles" id="relation-to-its10-and-new-principles" shape="rect"/>1.1 Relation to ITS 1.0 and New Principles</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="relation-to-its10" id="relation-to-its10" shape="rect"/>1.1.1 Relation to ITS 1.0</h4><p>ITS 2.0 has the following relations to ITS 1.0 <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a>:</p><ul><li><p>It adopts and maintains the following principles from ITS 1.0: </p><ul><li><p>It adopts the use of data categories to define discrete units of
- functionality</p></li><li><p>It adopts the separation of data category definition from the mapping of the
- data category to a given content format</p></li><li><p>It adopts the conformance principle of ITS1.0 that an implementation only
- needs to implement one data category to claim conformance to ITS 2.0</p></li></ul></li><li><p>ITS 2.0 supports all ITS 1.0 data category definitions and adds new definitions,
- with the exceptions of <a href="#directionality" shape="rect">Directionality</a> and Ruby.</p></li><li><p>ITS 2.0 adds a number of new data categories not found in ITS 1.0.</p></li><li><p>While ITS 1.0 addressed only XML, ITS 2.0 specifies implementations of data
- categories in <em>both</em> XML <em>and</em> HTML.</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="ruby-in-its2" id="ruby-in-its2" shape="rect"/>1.1.2 Ruby and ITS 2.0</h4><p>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, a stable model for ruby was not available. There are ongoing discussions about the <a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element" shape="rect">ruby model in HTML5</a>. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</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="new-principles" id="new-principles" shape="rect"/>1.1.3 New Principles</h4><p>ITS 2.0 also adds the following principles and features not found in ITS 1.0:</p><ul><li><p>ITS 2.0 data categories are intended to be format neutral, with support for XML,
- HTML, and NIF: a data category implementation only needs to support a single content
- format mapping in order to support a claim of ITS 2.0 conformance.</p></li><li><p>ITS 2.0 provides algorithms to generate NIF out of HTML or XML with ITS 2.0
- metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the <a href="#xpath" shape="rect">XPath version 1.0</a>. Other versions of XPath or other query languages (e.g.,
- CSS Selectors) can be expressed via a dedicated <a href="#queryLanguage" shape="rect">queryLanguage</a> attribute.</p></li></ul><p id="its20-new-data-categories">The new data categories included in ITS 2.0
- are:</p><ul><li><p><a href="#domain" shape="rect">Domain</a></p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a></p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a></p></li><li><p><a href="#provenance" shape="rect">Provenance</a></p></li><li><p><a href="#externalresource" shape="rect">External Resource</a></p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a></p></li><li><p><a href="#idvalue" shape="rect">ID Value</a></p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a></p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a></p></li><li><p><a href="#lqrating" shape="rect">Localization Quality Rating</a></p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a></p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a></p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a></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="motivation-its" id="motivation-its" shape="rect"/>1.2 Motivation for ITS</h3><p>Content or software that is authored in one language (the <span class="new-term">source language</span>)
- is often made available in additional languages or adapted with regard to other cultural
- aspects. This is done through a process called <span class="new-term">localization</span>, where the
- original material is translated and adapted to the target audience.</p><p>In addition, document formats expressed by schemas may be used by people in different
- parts of the world, and these people may need special markup to support the local
- language or script. 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>From the viewpoints of feasibility, cost, and efficiency, it is important that the
- original material should be suitable for localization. This is achieved by appropriate
- design and development, and the corresponding process is referred to as
- internationalization. For a detailed explanation of the terms “localization” and
- “internationalization”, see <a title="" href="#geo-i18n-l10n" shape="rect">[l10n i18n]</a>.</p><span class="editor-note">[Ed. note: Note: This should refer to the best practice document as well, when
- ready.]</span><p>The increasing usage of XML as a medium for documentation-related content (e.g. <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook#technical" shape="rect">DocBook</a>> and <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#technical" shape="rect">DITA</a> as formats for writing structured documentation, well suited to computer
- hardware and software manuals) and software-related content (e.g. the eXtensible User
- Interface Language <a title="exTensible User Interface Language" href="#xul" shape="rect">[XUL]</a>) creates challenges and
- opportunities in the domain of XML internationalization and localization.</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="motivation-its-issues" id="motivation-its-issues" shape="rect"/>1.2.1 Typical Problems</h4><p>The following examples sketch one of the issues that currently hinder efficient
- XML-related localization: the lack of a standard, declarative mechanism that
- identifies which parts of an XML document need to be translated. Tools often cannot
- automatically perform this identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those <code>string</code>
- elements that are translatable and those that are not. Only the addition of an
- explicit flag could resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
+ <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 betwee those <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>
@@ -217,10 +349,7 @@
<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><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-2" id="EX-motivation-its-2" shape="rect"/>Example 2: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text, the conditions
- may be quite complex and not directly indicated with a simple flag. Here, for
- instance, only the text in the nodes matching the expression
- <code>//component[@type!='image']/data[@type='text']</code> is translatable.</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>
+</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/a> 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>
@@ -239,339 +368,29 @@
<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><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="users-usage" id="users-usage" shape="rect"/>1.3 Users and Usages of ITS</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="potential-users" id="potential-users" shape="rect"/>1.3.1 Potential Users of ITS</h4><p>The ITS specification aims to provide different types of users with information about
- what markup should be supported to enable worldwide use and effective
- internationalization and localization of content. The following paragraphs sketch
- these different types of users, and their usage of ITS. In order to support all of
- these users, the information about what markup should be supported to enable worldwide
- use and effective localization of content is provided in this specification in two
- ways:</p><ul><li><p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="div4">
-<h5><a name="schema-dev-new" id="schema-dev-new" shape="rect"/>1.3.1.1 Schema developers starting a schema from the ground up</h5><p>This type of user will find proposals for attribute and element names to be
- included in their new schema (also called "host vocabulary"). Using the attribute
- and element names proposed in the ITS specification may be helpful because it leads
- to easier recognition of the concepts represented by both schema users and
- processors. It is perfectly possible, however, for a schema developer to develop his
- own set of attribute and element names. The specification sets out, first and
- foremost, to ensure that the required markup is available, and that the behavior of
- that markup meets established needs.</p></div><div class="div4">
-<h5><a name="schema-dev-existing" id="schema-dev-existing" shape="rect"/>1.3.1.2 Schema developers working with an existing schema</h5><p>This type of user will be working with schemas such as DocBook, DITA, or perhaps a
- proprietary schema. The ITS Working Group has sought input from experts developing
- widely used formats such as the ones mentioned.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The question "How to use ITS with existing popular markup schemes?" is
- covered in more details (including examples) in a separate document: <a title="Best
 Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p></div><p>Developers working on existing schemas should check whether their schemas support
- the markup proposed in this specification, and, where appropriate, add the markup
- proposed here to their schema.</p><p>In some cases, an existing schema may already contain markup equivalent to that
- recommended in ITS. In this case it is not necessary to add duplicate markup since
- ITS provides mechanisms for associating ITS markup with markup in the host
- vocabulary which serves a similar purpose (see <a class="section-ref" href="#associating-its-with-existing-markup" shape="rect">Section 5.6: Associating ITS Data Categories with Existing Markup</a>). The developer
- should, however, check that the behavior associated with the markup in their own
- schema is fully compatible with the expectations described in this
- specification.</p></div><div class="div4">
-<h5><a name="content-tool-vendor" id="content-tool-vendor" shape="rect"/>1.3.1.3 Vendors of content-related tools</h5><p>This type of user includes companies which provide tools for authoring, translation
- or other flavors of content-related software solutions. It is important to ensure
- that such tools enable worldwide use and effective localization of content. For
- example, translation tools should prevent content marked up as not for translation
- from being changed or translated. It is hoped that the ITS specification will make
- the job of vendors easier by standardizing the format and processing expectations of
- certain relevant markup items, and allowing them to more effectively identify how
- content should be handled.</p></div><div class="div4">
-<h5><a name="content-producers" id="content-producers" shape="rect"/>1.3.1.4 Content producers</h5><p>This type of user comprises authors, translators and other types of content author.
- The markup proposed in this specification may be used by them to mark up specific
- bits of content. Aside: The burden of inserting markup can be removed from content
- producers by relating the ITS information to relevant bits of content in a global
- manner (see <a href="#selection-global" shape="rect">global, rule-based approach</a>). This
- global work, however, may fall to information architects, rather than the content
- producers themselves.</p><p id="cms-plain-text-fields">Content producers often work with content management
- systems (CMS). In various CMS, some of the CMS fields only allow to store plain
- text. For these fields, the current ITS 2.0 data categories can only be applied
- globally and not with local attributes. This issue should be addressed in another
- way, apart from the ITS 2.0 standard. One way would be to allow HTML in these fields
- if possible, or using an extra field which allows HTML input and save the plain text
- of this extra field in the plain text field.</p></div><div class="div4">
-<h5><a name="users_machine-translation" id="users_machine-translation" shape="rect"/>1.3.1.5 Machine Translation Systems</h5><p>This type of service is intended for a broad user community ranging from developers
- and integrators through translation companies and agencies, freelance translators
- and post-editors to ordinary translation consumers and other types of MT employment.
- Data categories are envisaged for supporting and guiding the different automated
- backend processes of this service type, thereby adding substantial value to the
- service results as well as possible subsequent services. These processes include
- basic tasks, like parsing constraints and markup, and compositional tasks, such as
- disambiguation. These tasks consume and generate valuable metadata from and for
- third party users, for example, provenance information and quality scoring, and add
- relevant information for follow-on tasks, processes and services, such as MT
- post-editing, MT training and MT terminological enhancement.</p></div><div class="div4">
-<h5><a name="users_text_analytics" id="users_text_analytics" shape="rect"/>1.3.1.6 Text Analytics</h5><p>This type of service provides automatically generated metadata for improving
- localization, data integration or knowledge management workflows. This class of
- users comprises of developers and integrators of services that automate language
- technology tasks such as domain classification, named entity recognition and
- disambiguation, term extraction, language identification and others. Text analytics
- services generate data that contextualizes the raw content with more explicit
- information. This can be used to improve the output quality in machine translation
- systems, search result relevance in information retrieval systems, as well as
- management and integration of unstructured data in knowledge management systems.</p></div><div class="div4">
-<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers" shape="rect"/>1.3.1.7 Localization Workflow Managers</h5><p>These types of users are concerned with localization workflows in which content
- goes through certain steps: preparation for localization, start of the localization
- process by e.g. a conversion into a bitext (aligned parallel text) format like <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> or <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>, the actual localization by human translators or
- machine translation and other adaptations of content, and finally the integration of
- the localized content into the original format. That format is often based on XML or
- HTML; (Web) content management systems are widely used for content creation, and
[1493 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/13 21:41:34 1.447
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/16 23:18:40 1.448
@@ -129,618 +129,481 @@
</header>
<text>
<body>
- <div xml:id="introduction">
- <head>Introduction</head>
+ <div xml:id="introduction">
- <p>
- <emph>This section is informative.</emph>
- </p>
- <p>ITS 2.0 is a technology to add metadata to Web content, for the benefit of localization,
- language technologies, and internationalization. The ITS 2.0 specification both identifies
- concepts (such as <q>Translate</q>) that are important for internationalization and
- localization, and defines implementations of these concepts (termed “ITS data categories”)
- as a set of elements and attributes called the <emph>Internationalization Tag Set
- (ITS)</emph>. The document provides implementations for HTML, serializations in <ptr target="#nif-reference" type="bibref"/> (NLP Interchange Format), and provides definitions of ITS elements and attributes in the form of XML Schema <ptr
- target="#xmlschema1" type="bibref"/> and RELAX NG <ptr target="#relaxng" type="bibref"
- />.</p>
-
- <p>This document aims to realize many of the ideas formulated in the <ref
- target="http://www.w3.org/TR/2012/WD-its2req-20120524/">ITS 2.0 Requirements
- document</ref>, in <ptr target="#itsreq" type="bibref"/> and <ptr target="#reqlocdtd"
- type="bibref"/>.</p>
- <p>Not all requirements listed there are addressed in this document. Those which are not
- addressed here are either covered in <ptr type="bibref" target="#xml-i18n-bp"/>
- (potentially in an as yet unwritten best practice document on multilingual Web content),
- or may be addressed in a future version of this specification.</p>
-
- <div xml:id="relation-to-its10-and-new-principles">
- <head>Relation to ITS 1.0 and New Principles</head>
- <div xml:id="relation-to-its10">
- <head>Relation to ITS 1.0</head>
- <p>ITS 2.0 has the following relations to ITS 1.0 <ptr target="#its10" type="bibref"/>:</p>
- <list type="unorderd">
- <item><p>It adopts and maintains the following principles from ITS 1.0: </p><list
- type="unorderd">
- <item>It adopts the use of data categories to define discrete units of
- functionality</item>
- <item>It adopts the separation of data category definition from the mapping of the
- data category to a given content format</item>
- <item>It adopts the conformance principle of ITS1.0 that an implementation only
- needs to implement one data category to claim conformance to ITS 2.0</item>
- </list>
- </item>
- <item>ITS 2.0 supports all ITS 1.0 data category definitions and adds new definitions,
- with the exceptions of <ref target="#directionality">Directionality</ref> and Ruby.</item>
- <item>ITS 2.0 adds a number of new data categories not found in ITS 1.0.</item>
- <item>While ITS 1.0 addressed only XML, ITS 2.0 specifies implementations of data
- categories in <emph>both</emph> XML <emph>and</emph> HTML.</item>
- </list>
- </div>
- <div xml:id="ruby-in-its2">
- <head>Ruby and ITS 2.0</head>
- <p>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, a stable model for ruby was not available. There are ongoing discussions about the <ref target="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</ref>. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p>
- </div>
- <div xml:id="new-principles">
- <head>New Principles</head>
- <p>ITS 2.0 also adds the following principles and features not found in ITS 1.0:</p>
- <list type="unorderd">
- <item>ITS 2.0 data categories are intended to be format neutral, with support for XML,
- HTML, and NIF: a data category implementation only needs to support a single content
- format mapping in order to support a claim of ITS 2.0 conformance.</item>
- <item>ITS 2.0 provides algorithms to generate NIF out of HTML or XML with ITS 2.0
- metadata.</item>
- <item>A global implementation of ITS 2.0 requires at least the <ref target="#xpath"
- >XPath version 1.0</ref>. Other versions of XPath or other query languages (e.g.,
- CSS Selectors) can be expressed via a dedicated <ref target="#queryLanguage"
- >queryLanguage</ref> attribute.</item>
- </list>
- <p xml:id="its20-new-data-categories">The new data categories included in ITS 2.0
- are:</p>
- <list type="unorderd">
- <item><ref target="#domain">Domain</ref></item>
- <item><ref target="#textanalysis">Text Analysis</ref></item>
- <item><ref target="#LocaleFilter">Locale Filter</ref></item>
- <item><ref target="#provenance">Provenance</ref></item>
- <item><ref target="#externalresource">External Resource</ref></item>
- <item><ref target="#target-pointer">Target Pointer</ref></item>
- <item><ref target="#idvalue">ID Value</ref></item>
- <item><ref target="#preservespace">Preserve Space</ref></item>
- <item><ref target="#lqissue">Localization Quality Issue</ref></item>
- <item><ref target="#lqrating">Localization Quality Rating</ref></item>
- <item><ref target="#mtconfidence">MT Confidence</ref></item>
- <item><ref target="#allowedchars">Allowed Characters</ref></item>
- <item><ref target="#storagesize">Storage Size</ref></item>
- </list>
- </div>
- </div>
-
- <div xml:id="motivation-its">
- <head>Motivation for ITS</head>
- <p>Content or software that is authored in one language (the <term>source language</term>)
- is often made available in additional languages or adapted with regard to other cultural
- aspects. This is done through a process called <term>localization</term>, where the
- original material is translated and adapted to the target audience.</p>
- <p>In addition, document formats expressed by schemas may be used by people in different
- parts of the world, and these people may need special markup to support the local
- language or script. 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>From the viewpoints of feasibility, cost, and efficiency, it is important that the
- original material should be suitable for localization. This is achieved by appropriate
- design and development, and the corresponding process is referred to as
- internationalization. For a detailed explanation of the terms “localization” and
- “internationalization”, see <ptr target="#geo-i18n-l10n" type="bibref"/>.</p>
- <note type="ed">Note: This should refer to the best practice document as well, when
- ready.</note>
- <p>The increasing usage of XML as a medium for documentation-related content (e.g. <ref
- target="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook#technical"
- >DocBook</ref>> and <ref
- target="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#technical"
- >DITA</ref> as formats for writing structured documentation, well suited to computer
- hardware and software manuals) and software-related content (e.g. the eXtensible User
- Interface Language <ptr target="#xul" type="bibref"/>) creates challenges and
- opportunities in the domain of XML internationalization and localization.</p>
-
- <div xml:id="motivation-its-issues">
- <head>Typical Problems</head>
-
- <p>The following examples sketch one of the issues that currently hinder efficient
- XML-related localization: the lack of a standard, declarative mechanism that
- identifies which parts of an XML document need to be translated. Tools often cannot
- automatically perform this identification.</p>
- <exemplum xml:id="EX-motivation-its-1">
- <head>Document with partially translatable content</head>
- <p>In this document it is difficult to distinguish between those <code>string</code>
- elements that are translatable and those that are not. Only the addition of an
- explicit flag could resolve the issue.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-motivation-its-1.xml"/>
- </exemplum>
- <exemplum xml:id="EX-motivation-its-2">
- <head>Document with partially translatable content</head>
- <p>Even when metadata are available to identify non-translatable text, the conditions
- may be quite complex and not directly indicated with a simple flag. Here, for
- instance, only the text in the nodes matching the expression
- <code>//component[@type!='image']/data[@type='text']</code> is translatable.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-motivation-its-2.xml"/>
- </exemplum>
- </div>
- </div>
- <div xml:id="users-usage">
- <head>Users and Usages of ITS</head>
- <div xml:id="potential-users">
- <head>Potential Users of ITS</head>
- <p>The ITS specification aims to provide different types of users with information about
- what markup should be supported to enable worldwide use and effective
- internationalization and localization of content. The following paragraphs sketch
- these different types of users, and their usage of ITS. In order to support all of
- these users, the information about what markup should be supported to enable worldwide
- use and effective localization of content is provided in this specification in two
- ways:</p>
- <list>
- <item>abstractly in the data category descriptions: <ptr
- target="#datacategory-description" type="specref"/>
- </item>
- <item>concretely in the ITS schemas: <ptr target="#its-schemas" type="specref"/>
- </item>
- </list>
- <div xml:id="schema-dev-new">
- <head>Schema developers starting a schema from the ground up</head>
- <p>This type of user will find proposals for attribute and element names to be
- included in their new schema (also called "host vocabulary"). Using the attribute
- and element names proposed in the ITS specification may be helpful because it leads
- to easier recognition of the concepts represented by both schema users and
- processors. It is perfectly possible, however, for a schema developer to develop his
- own set of attribute and element names. The specification sets out, first and
- foremost, to ensure that the required markup is available, and that the behavior of
- that markup meets established needs.</p>
- </div>
- <div xml:id="schema-dev-existing">
- <head>Schema developers working with an existing schema</head>
- <p>This type of user will be working with schemas such as DocBook, DITA, or perhaps a
- proprietary schema. The ITS Working Group has sought input from experts developing
- widely used formats such as the ones mentioned.</p>
- <note><p>The question "How to use ITS with existing popular markup schemes?" is
- covered in more details (including examples) in a separate document: <ptr
- target="#xml-i18n-bp" type="bibref"/>.</p></note>
- <p>Developers working on existing schemas should check whether their schemas support
- the markup proposed in this specification, and, where appropriate, add the markup
- proposed here to their schema.</p>
- <p>In some cases, an existing schema may already contain markup equivalent to that
- recommended in ITS. In this case it is not necessary to add duplicate markup since
- ITS provides mechanisms for associating ITS markup with markup in the host
- vocabulary which serves a similar purpose (see <ptr
- target="#associating-its-with-existing-markup" type="specref"/>). The developer
- should, however, check that the behavior associated with the markup in their own
- schema is fully compatible with the expectations described in this
- specification.</p>
- </div>
- <div xml:id="content-tool-vendor">
- <head>Vendors of content-related tools</head>
- <p>This type of user includes companies which provide tools for authoring, translation
- or other flavors of content-related software solutions. It is important to ensure
- that such tools enable worldwide use and effective localization of content. For
- example, translation tools should prevent content marked up as not for translation
- from being changed or translated. It is hoped that the ITS specification will make
- the job of vendors easier by standardizing the format and processing expectations of
- certain relevant markup items, and allowing them to more effectively identify how
- content should be handled.</p>
- </div>
- <div xml:id="content-producers">
- <head>Content producers</head>
- <p>This type of user comprises authors, translators and other types of content author.
- The markup proposed in this specification may be used by them to mark up specific
- bits of content. Aside: The burden of inserting markup can be removed from content
- producers by relating the ITS information to relevant bits of content in a global
- manner (see <ref target="#selection-global">global, rule-based approach</ref>). This
- global work, however, may fall to information architects, rather than the content
- producers themselves.</p>
- <p xml:id="cms-plain-text-fields">Content producers often work with content management
- systems (CMS). In various CMS, some of the CMS fields only allow to store plain
- text. For these fields, the current ITS 2.0 data categories can only be applied
- globally and not with local attributes. This issue should be addressed in another
- way, apart from the ITS 2.0 standard. One way would be to allow HTML in these fields
- if possible, or using an extra field which allows HTML input and save the plain text
- of this extra field in the plain text field.</p>
- </div>
- <div xml:id="users_machine-translation">
- <head>Machine Translation Systems</head>
- <p>This type of service is intended for a broad user community ranging from developers
- and integrators through translation companies and agencies, freelance translators
- and post-editors to ordinary translation consumers and other types of MT employment.
- Data categories are envisaged for supporting and guiding the different automated
- backend processes of this service type, thereby adding substantial value to the
- service results as well as possible subsequent services. These processes include
- basic tasks, like parsing constraints and markup, and compositional tasks, such as
- disambiguation. These tasks consume and generate valuable metadata from and for
- third party users, for example, provenance information and quality scoring, and add
- relevant information for follow-on tasks, processes and services, such as MT
- post-editing, MT training and MT terminological enhancement.</p>
- </div>
- <div xml:id="users_text_analytics">
- <head>Text Analytics</head>
- <p>This type of service provides automatically generated metadata for improving
- localization, data integration or knowledge management workflows. This class of
- users comprises of developers and integrators of services that automate language
- technology tasks such as domain classification, named entity recognition and
- disambiguation, term extraction, language identification and others. Text analytics
- services generate data that contextualizes the raw content with more explicit
- information. This can be used to improve the output quality in machine translation
- systems, search result relevance in information retrieval systems, as well as
- management and integration of unstructured data in knowledge management systems.</p>
- </div>
- <div xml:id="users_localization_workflow_managers">
- <head>Localization Workflow Managers</head>
- <p>These types of users are concerned with localization workflows in which content
- goes through certain steps: preparation for localization, start of the localization
- process by e.g. a conversion into a bitext (aligned parallel text) format like <ptr
- target="#xliff1.2" type="bibref"/> or <ptr target="#xliff2.0" type="bibref"/>, the actual localization by human translators or
- machine translation and other adaptations of content, and finally the integration of
- the localized content into the original format. That format is often based on XML or
- HTML; (Web) content management systems are widely used for content creation, and
- their integration with localization workflows is an important task for the workflow
- manager. For the integration of content creation and localization, metadata plays a
- crucial role. E.g. an ITS data category like <ref target="#trans-datacat"
- >translate</ref> can trigger the extraction of localizable text. <quote>Metadata
- roundtripping</quote>, that is the availibility of metadata both before and after
- the localization process is crucial for many tasks of the localization workflow
- manager. An example is metadata based quality control, with checks like <quote>Have
- all pieces of content set to <code>translate="no"</code> been left
- unchanged?</quote>. Other pieces of metadata are relevant for proper
- internationalization during the localization workflow, e.g. the availibility of <ref
- target="#directionality">Directionality</ref> markup for adequate visualization of
- bidirectional text.</p>
- </div>
- </div>
- <div xml:id="ways-to-use-its">
- <head>Ways to Use ITS</head>
- <p>The ITS specification proposes several mechanisms for supporting worldwide use and
- effective internationalization and localization of content. We will sketch them below
- by looking at them from the perspectives of certain user types. For the purpose of
- illustration, we will demonstrate how ITS can indicate that certain parts of content
- should or should not be translated.</p>
- <list>
- <item>
- <p>A content author uses an attribute on a particular element to say that the text
- in the element should not be translated.</p>
- </item>
- </list>
- <exemplum xml:id="EX-ways-to-use-its-1">
- <head>Use of ITS by content author</head>
- <p>The <code>its:translate="no"</code> attributes indicate that the <code>path</code>
- and the <code>cmd</code> elements should not be translated.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-ways-to-use-its-1.xml"/>
- </exemplum>
- <list>
- <item>
- <p>A content author or information architect uses markup at the top of the document
- to identify a particular type of element or context in which the content should
- not be translated.</p>
- </item>
- </list>
- <exemplum xml:id="EX-ways-to-use-its-2">
- <head>Use of ITS by information architect</head>
- <p>The <gi>translateRule</gi> element is used in the header of the document to
- indicate that none of the <code>path</code> or <code>cmd</code> elements should be
- translated.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-ways-to-use-its-2.xml"/>
- </exemplum>
- <list>
- <item>
- <p>A processor may insert markup at the top of the document which links to ITS
- information outside of the document.</p>
- </item>
- </list>
- <exemplum xml:id="EX-ways-to-use-its-3">
- <head>Use of ITS by processor</head>
- <p>A <gi>rules</gi> element is inserted in the header of the document. It has a XLink
- <att>href</att> attribute used to link to an <ref target="#link-external-rules"
- >ITS external rule</ref> document.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-ways-to-use-its-3.xml"/>
- </exemplum>
- <exemplum xml:id="EX-ways-to-use-its-4">
- <head>ITS rule file shared by different documents</head>
- <p>The <gi>rules</gi> element contains several ITS rules that are common to different
- documents. One of them is a <gi>translateRule</gi> element that indicates that no
- <code>path</code> or <code>cmd</code> element should be translated.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-ways-to-use-its-4.xml"/>
- </exemplum>
- <list>
- <item>
- <p>A schema developer integrates ITS markup declarations in his schema to allow
- users to indicate that specific parts of the content should not be translated.</p>
- </item>
- </list>
- <note type="ed">Following schema example has to updated once we have final XSD schema
- for ITS 2.0</note>
- <exemplum xml:id="EX-ways-to-use-its-5">
- <head>An XSD schema with ITS declaration</head>
- <p>The declarations for the <att type="class">translate</att> attribute is added to a
- group of common attributes <code>commonAtts</code>. This allows to use the <att
- type="class">translate</att> attribute within the documents like in <ptr
- target="#EX-ways-to-use-its-1" type="exref"/>.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-ways-to-use-its-5.xsd"/>
- </exemplum>
- <p>The first two approaches above can be likened to the use of CSS in <ptr
- target="#xhtml10" type="bibref"/>. Using a <code>style</code> attribute, an XHTML
- content author may assign a color to a particular paragraph. That author could also
- have used the <code>style</code> element at the top of the page to say that all
- paragraphs of a particular class or in a particular context would be colored red.</p>
- </div>
- </div>
+ <head>Introduction</head>
+<p><emph>This section is informative</emph></p>
- <div xml:id="usage-in-html">
- <head>Usage in HTML</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>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
[1000 lines skipped]
Received on Sunday, 16 June 2013 23:18:43 UTC