- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Tue, 11 Jun 2013 05:31:54 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv2768
Modified Files:
its20-for-editing-sec1-sec2.html
its20-for-editing-sec1-sec2.odd
Log Message:
more sec1-2 edits
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/10 03:51:56 1.15
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/11 05:31:53 1.16
@@ -59,9 +59,9 @@
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors" shape="rect">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage" shape="rect">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2440" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2451" 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="#d0e2685" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2696" 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>
@@ -163,13 +163,9 @@
the
- corresponding approach to production in many cases encompasses
+ corresponding approach to multilingual production in many cases encompasses
- three
-
- phases: internationalize, translate,
-
- and localize (see the <a href="http://www.w3.org/International/questions/qa-i18n/" shape="rect"> W3C's Internationalization Q&A</a>
+ 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).
@@ -201,15 +197,7 @@
internationalization.
- For
-
- example, people authoring in languages such as Arabic, Hebrew,
-
- Persian or Urdu need special markup to specify directionality in
-
- mixed
-
- direction text.
+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
@@ -231,7 +219,7 @@
linguistic
- dimensions such as mandatory terminology or standard
+ dimensions like mandatory terminology or standard
phrases.
@@ -241,7 +229,7 @@
missing,
- this phase is usually seen as encompassing activites such as
+this phase is usually seen as encompassing activities such as
creating locale-specific content (e.g. adding a link for a
@@ -287,7 +275,7 @@
translation, and localization related to core Web
- technologies. ITS does for example assist in usage scenarios in which parts of an
+ 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
@@ -307,104 +295,39 @@
Web content.
- </p><p>ITS proposes several mechanisms which differ
-
- amongst others in terms of the usage scenario/user types for which the
-
- mechanism is most suitable. For the purpose of
-
- illustration, here is an example how ITS can indicate that certain parts of
-
- content should not be translated.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-ways-to-use-its-0" id="EX-ways-to-use-its-0" shape="rect"/>Example 1: Use of ITS to indicate that parts of an XML-based document - maybe to be transformed into HTML by a Web Content Management System (WCMS) -
-
- should or should not be translated</div><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></div><span class="editor-note">[Ed. note: Need to provide example:
- <egXML xmlns="http://www.tei-c.org/ns/Examples" target="examples/xml/EX-ways-to-use-its-0.xml" />]</span><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 XML Schema
-
- <a title="XML Schema Part 1:
 Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a>
-
- (non-normative)
-
- and 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 regulates the relationship between ITS markup and
-
- the
-
- various HTML flavours.
-
- Furthermore, ITS 2.0
-
- suggests when and how to leverage
-
- processing based on the XML Localization
-
- Interchange File Format
-
- (XLIFF), as
-
- well as the
-
- Natural Language
-
- Processing Interchange
-
- Format
-
- <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF (NLP Interchange Format)</a>
-
- .
-
- </p><span class="editor-note">[Ed. note: We need to have the example <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">EX-motivation-its-2.xml</a> here since it was part of resolving <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/100" shape="rect">issue-100</a>.]</span><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 2: 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>
+ </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 serious 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 with partially translatable content</div><p>In this document it is difficult to distinguish between those code>string</code> elements that should be translated and those that must not be translated. Explicit 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>
@@ -426,35 +349,37 @@
<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 3: 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><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>
+
<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><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"><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><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"><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 fit onto a beer mat:</p><ol class="depth1"><li><p>Provide meta data (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global appraoch</a>) to tie the meta data to specific XML nodes (e.g. all elements named <code>uitext</code>) or put the meta data straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of meta data categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing meta data (e.g terms already marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <a href="http://www.w3.org/International/its/ig/links.html" shape="rect">ITS Interest Group</a> for example compiled a list of additional data categories (see this <a href="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf" shape="rect">related summary</a>). Some of these were then defined in ITS 2.0: <a href="#idvalue" shape="rect">ID Value</a>, local <a href="#elements-within-text" shape="rect">Elements Within Text</a>, <a href="#preservespace" shape="rect">Preserve Space</a>, and <a href="#LocaleFilter" shape="rect">Locale Filte</a>. Others are still discussed as requirements:</p><ol class="depth1"><li><p>“Context” = What specific related information might be helpful?</p></li><li><p>“Automated Language”: Does this content lend iself to automatic processing?</p></li></ol><p>The real-world deployments also helped to understand that for the <a href="http://www.webplatform.org/" shape="rect">Open Web Platform</a> - the ITS 1.0 restriction to XML was an obstacle for quite a number of environments. What was missing was for example the following:</p><ol class="depth1"><li><p>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</p></li><li><p>Easy use of ITS in various Web-exposed Natural Language Processing contexts (e.g. machine translation, cross-language information retrieval, computer-supported linguistic quality assurance)</p></li><li><p>Support for provenance <a title="" href="#prov-overview" shape="rect">[PROV-OVERVIEW]</a>, “information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data scenaris.</p></li></ol><p>ITS 2.0 was created by an alliance of stakeholders who are involved in content for global use. Thus, ITS 2.0 was developed with input from/with a view towards the following:</p><ul><li><p>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in production chains</p></li><li><p>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to faciliate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="" href="#xliff" shape="rect">[XLIFF]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>) that are interested for example in lossless roundtripping of meta data in localization workflows.</p></li></ul><p>One example outcome of work on the requirements is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> mechanism. It addresses the provenance-related requirement b allowing ITS processors to leave a trace: ITS processors can basically say "It is me that generated this bit of information". Another example are the <a title="" href="#nif-reference" shape="rect">[NIF]</a> related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</p></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="usage-scenarios" id="usage-scenarios" shape="rect"/>1.3 Usage Scenarios</h3><p>The ITS 1.0 specification <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a> states in <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">the introduction</a>: “ITS is a technology to easily create XML which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multi-lingual production.<p><ul><li><p>Static mono-lingual: This part of the content has the directionality “right-to-left”.</p></li><li><p>Dynamic multi-lingual: This part of the content should be excluded from a possible translation phase.</p></li></ul><p>Although the ITS 1.0 made no assumptions about possible phases in a production process chain, it was slanted towards a simple three phase “write->internationalize->translate” model. Even a birds-eye-view at ITS 2.0 shows that ITS 2.0 explicitly targets a much more comprehensive model for multi-lingual content production. The model comprises support for multi-lingual content production phases such as:</p><ul><li><p>Internationalization</p></li><li><p>Pre-production (e.g. related to marking terminology)</p></li><li><p>Automated content enrichment (e.g. automatic hyperlinking for entities)</p></li><li><p>Extraction/filtering of translation-relevant content</p></li><li><p>Segmentation</p></li><li><p>Leveraging (e.g. of existing translation-related assets such as translaion memories)</p></li><li><p>Machine Translation (e.g. geared towards a specific domain)</p></li><li><p>Quality assessment or control of source language or target language content</p></li><li><p>Generation of translation kits (e.g. packages based on XLIFF)</p></li><li><p>Post-production</p></li><li><p>Publishing</p></li></ul><p>The document <a 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 acors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity idenfiers/disambiguators to the same level. This change amongst others is reflected in the introduction of the ITS 2.0 <a href="#its-tool-annotation" shape="rect">Tool Annotation</a> which allows systems to record that they have processed as certain part of content.</p></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="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><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. terms already marked up wth 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/links.html" shape="rect">ITS Interest Group</a> for example compiled a list of additional data categories (see this <a href="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf" shape="rect">related summary</a>). Some of these were then defined in ITS 2.0: <a href="#idvalue" shape="rect">ID Value</a>, local <a href="#elements-within-text" shape="rect">Elements Within Text</a>, <a href="#preservespace" shape="rect">Preserve Space</a>, and <a href="#LocaleFilter" shape="rect">Locale Filte</a>. Others are still discussed as requirements 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 Language” = Doe 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-overview" shape="rect">[PROV-OVERVIEW]</a>, “information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, eliability 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, andlossless 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 chai, 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>p>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 tha they have processed as certain part of content.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="high-level-differences-between-1.0-and-2.0" id="high-level-differences-between-1.0-and-2.0" shape="rect"/>1.4 High-level differences between ITS 1.0 and ITS 2.0</h3><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 provides data categories to be applied to XML content. ITS 2.0 extends the coverage to <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>. Explanatory details about ITS 2.0 and <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> is given in <a class="section-ref" href="#specific-HTML-support" shape="rect">Section 2.4: Specific HTML support</a>.</p><p>
+ <em>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.4: 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="#datacategories-summary" shape="rect">Section 2.7: Summary: ITS 2.0 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, in a subsequent version of ITS, the ruby data category may be re-introduced.</p></li><li><p>The <a href="#directionality" shape="rect">Directionality</a> data category reflects directionality markup in <a title="HTML 4.01" href="#html4" shape="rect">[HTML 4.01]</a>. The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhacements are not finalized yet. They will be reflected in a future revision of ITS.</p></li></ul><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, hese 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="sectio-ref" href="#traceability" shape="rect">Section 2.5: Traceability</a> for details.</p></li></ul><p>
- <em>Mappings:</em> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <a title="" href="#nif-reference" shape="rect">[NIF]</a> and links to guidance about ITS 2.0 and XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">Section 2.6: Mapping and conversion</a> for details.</p><p>
+ <em>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.6: Mapping and conversion</a> for details.</p><p>
<em>Changes to the conformance section</em>: The <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed, and a conformance clause related to processing <a title="" href="#nif-reference" shape="rect">[NIF]</a> has been added. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, a dedicated conformance section has been created. Finally, a conformance clause 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 by <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</a>.</p></div></div><div class="div1">
+<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”. The underlying formal definitions are given in the subsequent sections.</p><p>A key concept of ITS is the abstract notion of <a href="#def-datacat" shape="rect">data categories</a>. Data categories define the information that can be conveyed via ITS. An example is the <a href="#trans-datacat" shape="rect">Translate</a> data category. It conveys information about translatability of conent.</p><p>
@@ -473,11 +398,11 @@
markup in elements defined by ITS itself (namely the <code class="its-elem-markup">rules</code> element)</p></li></ul><p>ITS markup can be used with XML documents (e.g. a DocBook article), HTML documents, or schemas (e.g. an
XML Schema document for a proprietary document format).</p><p>The following two examples sketch the distinction between the local and global
approaches, using the <a href="#trans-datacat" shape="rect">Translate</a> data category as one example.</p><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"/>2.1.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 4</a> shows how a content
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"/>2.1.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 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. Translation tools that are aware of the meaning of this attribute can
- then screen the relevant content from the translation process.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 4: ITS markup on elements in an XML document (local approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
+ then screen the relevant content from the translation process.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 3: ITS markup on elements in an XML document (local approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
<span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
<span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"5.0"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><info></strong>
@@ -500,7 +425,7 @@
which does not. Tools that process this content for translation will need to implement
the expected inheritance.</p><p id="local-approach-not-applicable-to-attributes">For XML content, the local approach cannot be applied on a particular attribute.
It can be applied for the content of the current element and all its inherited nodes as described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>. For the <a href="#trans-datacat" shape="rect">Translate</a> data category used in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, this is different, see the explanation of the <a href="#translate-in-html5" shape="rect">HTML5 definition of Translate</a>.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"/>2.1.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 5</a> shows a different
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"/>2.1.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 4</a> shows a different
approach to identifying non-translatable content, similar to that used with a
<code>style</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>, but using an
ITS-defined element called <code class="its-elem-markup">rules</code>. It works as follows: A document can contain
@@ -512,7 +437,7 @@
attributes are XPath absolute location paths (or CSS Selectors if <a href="#queryLanguage" shape="rect">queryLanguage</a> is set to "css"). Via the <a href="#its-param" shape="rect">param</a> element
variables can be provided and then be used in the selectors.</p><p>Information for the
handling of namespaces in XPath expressions is taken from namespace declarations
- <a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> at the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 5: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> at the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 4: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><prolog></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>Using ITS<strong class="hl-tag" style="color: #000096"></title></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -545,7 +470,7 @@
<code>p</code> elements in an XML document)</p></li><li><p>ITS markup to pertain to attributes</p></li><li><p>ITS markup to <a href="#associating-its-with-existing-markup" shape="rect"> associate
with existing markup</a> (for example the <code>term</code> element in
DITA)</p></li></ul></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"/>2.2 Overriding, Inheritance and Defaults</h3><p>The power of the ITS selection mechanisms comes at a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a>, and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a>, have to be established.</p><p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 6</a> shows how inheritance
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"/>2.2 Overriding, Inheritance and Defaults</h3><p>The power of the ITS selection mechanisms comes at a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a>, and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a>, have to be established.</p><p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 5</a> shows how inheritance
and overriding work for the <a href="#trans-datacat" shape="rect">Translate</a> data category.
By default elements are translatable. Here, the <code class="its-elem-markup">translateRule</code> element declared
in the header overrides the default for the <code>head</code> element inside
@@ -554,7 +479,7 @@
<code>its:translate="yes"</code>. Note that the global rule is processed first,
regardless of its position inside the document. In the main body of the document, the
default applies, and here it is <code>its:translate="no"</code> that is used to set
- “faux pas” as non-translatable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 6: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
+ “faux pas” as non-translatable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 5: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><revision></strong>Sep-10-2006 v5<strong class="hl-tag" style="color: #000096"></revision></strong>
<strong class="hl-tag" style="color: #000096"><author></strong>Ealasaidh McIan<strong class="hl-tag" style="color: #000096"></author></strong>
@@ -586,7 +511,7 @@
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-reference-global-rules" id="html5-reference-global-rules" shape="rect"/>2.4.1 Referencing global rules</h4><p>To account for the so-called “<a href="#basic-concepts-selection-global" shape="rect">global
approach</a>” in HTML, this specification (see <a class="section-ref" href="#html5-global-rules" shape="rect">Section 6.2: Global rules</a>) defines a link type for referring to external files
with global rules and an approach to have inline global rules in the HTML <code>script</code> element.
- It is preferred to use external global rules linked via the <code>link</code> element than to have inline global rules in the HTML document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 7: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
+ It is preferred to use external global rules linked via the <code>link</code> element than to have inline global rules in the HTML document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 6: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
<code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
<strong class="hl-tag" style="color: #000096"><html></strong>
@@ -600,7 +525,7 @@
Of course there are always exceptions: certain code values should be translated,
e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-global-1.html" shape="rect">examples/html5/EX-translate-html5-global-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1-rules-file" id="EX-translate-html5-global-1-rules-file" shape="rect"/>Example 8: ITS rules file linked from HTML</div><p>The rules file linked in <a href="#EX-translate-html5-global-1" shape="rect">Example 7</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
+<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-global-1.html" shape="rect">examples/html5/EX-translate-html5-global-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1-rules-file" id="EX-translate-html5-global-1-rules-file" shape="rect"/>Example 7: ITS rules file linked from HTML</div><p>The rules file linked in <a href="#EX-translate-html5-global-1" shape="rect">Example 6</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
<span class="hl-attribute" style="color: #F5844C">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"></its:rules></strong>
@@ -623,7 +548,7 @@
<code>withinText="yes"</code> by default, except for the elements <code class="its-elem-markup">iframe</code>, <code class="its-elem-markup">noscript</code>, <code class="its-elem-markup">script</code>
and <code class="its-elem-markup">textarea</code> which are interpreted as <code>withinText="nested"</code>.</p></li><li><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category has a direct counterpart in
<a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, namely the HTML5
- <code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute" shape="rect">the HTML5 definition</a>. The <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> definition also applies to nodes selected via global rules. That is, a <code class="its-elem-markup">translateRule</code> like <code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-and-existing-HTML5-markup" id="EX-its-and-existing-HTML5-markup" shape="rect"/>Example 9: The <a href="#language-information" shape="rect">Language Information</a>, <a href="#idvalue" shape="rect">Id Value</a>,
+ <code>translate</code> attribute. ITS 2.0 does not define its own behaviour for HTML5 <code>translate</code>, but just refers to <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute" shape="rect">the HTML5 definition</a>. The <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> definition also applies to nodes selected via global rules. That is, a <code class="its-elem-markup">translateRule</code> like <code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-its-and-existing-HTML5-markup" id="EX-its-and-existing-HTML5-markup" shape="rect"/>Example 8: The <a href="#language-information" shape="rect">Language Information</a>, <a href="#idvalue" shape="rect">Id Value</a>,
<a href="#elements-within-text" shape="rect">Elements within Text</a> and <a href="#trans-datacat" shape="rect">Translate</a>
ITS 2.0 data categories used with
HTML native markup.</div><p>The <code>html</code> element is interpreted to convey the
@@ -648,17 +573,17 @@
of ITS 2.0 are encouraged to specifiy the association of existing HTML
markup with a dedicated global rules file. For an example rules file see the
<a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml" shape="rect">XML I18N Best Practices</a> document.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-standoff-markup-explanation" id="html5-standoff-markup-explanation" shape="rect"/>2.4.4 Standoff Markup in HTML5</h4><p>The <a href="#provenance" shape="rect">Provenance</a> and the <a href="#lqissue" shape="rect">Localization Quality Issue</a> data categories allow for using standoff markup. In HTML such standoff markup is put into a <code>script</code> element. The constraints for <a href="#provenance-records-in-html5-constraint" shape="rect">Provenance standoff</a> markup in HTML and <a href="#loc-quality-issues-in-html5-constraint" shape="rect">Localization quality issue</a> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <a href="#EX-provenance-html5-local-2" shape="rect">Example 62</a> and <a href="#EX-locQualityIssue-html5-local-2" shape="rct">Example 77</a>.</p></div><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-standoff-markup-explanation" id="html5-standoff-markup-explanation" shape="rect"/>2.4.4 Standoff Markup in HTML5</h4><p>The <a href="#provenance" shape="rect">Provenance</a> and the <a href="#lqissue" shape="rect">Localization Quality Issue</a> data categories allow for using standoff markup. In HTML such standoff markup is put into a <code>script</code> element. The constraints for <a href="#provenance-records-in-html5-constraint" shape="rect">Provenance standoff</a> markup in HTML and <a href="#loc-quality-issues-in-html5-constraint" shape="rect">Localization quality issue</a> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <a href="#EX-provenance-html5-local-2" shape="rect">Example 61</a> and <a href="#EX-locQualityIssue-html5-local-2" shape="rct">Example 76</a>.</p></div><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="usage-in-legacy-html" id="usage-in-legacy-html" shape="rect"/>2.4.5 Version of HTML</h4><p>ITS 2.0 does not define how to use ITS in HTML versions prior version 5. Users are
encouraged to migrate their content to HTML5 or XHTML. While it is possible to use
<code>its-*</code> attributes introduced for <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> in older versions of HTML (such
as 3.2 or 4.01) and pages using these attributes will work without any problems,
<code>its-*</code> attributes will be marked as invalid in validators.</p></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="traceability" id="traceability" shape="rect"/>2.5 Traceability</h3><p>The <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism allows to associate processor information with the use of individual data categories in a document, independently from data category annotations themselves. The mechanism associates identifiers for tools and data categories via the <code class="its-attr-markup">annotatorsRef</code> attribute (or <code class="its-attr-markup">annotators-ref</code> in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>) and is mandatory for the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category. For the <a href="#terminology" shape="rect">Terminology</a> and <a href="#textanalysis" shape="rect">Text Analysis</a> data categories it is mandatory if they provide confience information, that is always tool related. Nevertheless, <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> can be used for all data categories. <a href="#EX-its-tool-annotation-2" shape="rect">Example 24</a> demonstrates the usage including several data categories.</p></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="traceability" id="traceability" shape="rect"/>2.5 Traceability</h3><p>The <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism allows to associate processor information with the use of individual data categories in a document, independently from data category annotations themselves. The mechanism associates identifiers for tools and data categories via the <code class="its-attr-markup">annotatorsRef</code> attribute (or <code class="its-attr-markup">annotators-ref</code> in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>) and is mandatory for the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category. For the <a href="#terminology" shape="rect">Terminology</a> and <a href="#textanalysis" shape="rect">Text Analysis</a> data categories it is mandatory if they provide confience information, that is always tool related. Nevertheless, <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> can be used for all data categories. <a href="#EX-its-tool-annotation-2" shape="rect">Example 23</a> demonstrates the usage including several data categories.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-conversion" id="mapping-conversion" shape="rect"/>2.6 Mapping and conversion</h3><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-NIF" id="mapping-NIF" shape="rect"/>2.6.1 ITS and RDF/NIF</h4><p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
representations) that contain ITS metadata to the RDF-based format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples that represent the textual content of the original document as RDF typed information and the ITS annotation as properties of those nodes defined in an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The backconversion <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>2.6.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="" href="#xliff" shape="rect">[XLIFF]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.0 usage scenarios <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a>. These usage scenarios involve: 1) the extraction of ITS meta-data from a sourcelanguage file into XLIFF; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files. ITS 2.0 has no normative dependency on XLIFF, however a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping" shape="rect">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/" shape="rect">Internationalization Tag Set Interest Group</a>.</p></div></div><div class="div2">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>2.6.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> is the successor of <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and under development. <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS andXLIFF therefore unpins several important ITS 2.0 usage scenarios <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a>. These usage scenarios involve: 1) the extraction of ITS meta-data from a source language file into XLIFF; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files. ITS 2.0 has no normative dependency on XLIFF, however a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping" shape="rect">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/" shape="rect">Internationalization Tag Set Interest Group</a>.</p></div></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="datacategories-summary" id="datacategories-summary" shape="rect"/>2.7 Summary: ITS 2.0 data categories</h3><p>ITS 2.0 provides the following data categories, using most of the existing ITS 1.0 data categories and adding new ones. Modifications of existing ITS 1.0 data categories are summarized in <a class="section-ref" href="#high-level-differences-between-1.0-and-2.0" shape="rect">Section 1.4: High-level differences between ITS 1.0 and ITS 2.0</a>.</p><ul><li><p><a href="#trans-datacat" shape="rect">Translate</a>: express information about whether a selected piece of content should be translated or not.</p></li><li><p><a href="#locNote-datacat" shape="rect">Localization Note</a>: communicate notes to localizers about a particular item of content.</p></li><li><p><a href="#terminology" shape="rect">Terminology</a>: mak terms and optionally associate them with information, such as definitions or references to a term data base.</p></li><li><p><a href="#directionality" shape="rect">Directionality</a>: specify the base writing direction of blocks, embeddings and overrides for the Unicode bidirectional algorithm.</p></li><li><p><a href="#language-information" shape="rect">Language Information</a>: express the language of a given piece of content.</p></li><li><p><a href="#elements-within-text" shape="rect">Elements Witin Text:</a> express how content of an element is related to the text flow (constitute its own segment like paragraphs, be part of a segment like emphasis marker etc).</p></li><li><p><a href="#domain" shape="rect">Domain</a>: identify the topic or subject of the annotated content for translation related applications.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotate content with lexical or conceptual information for the purpose of contextual disambiguation.</p></li><li><p><a href="#ocaleFilter" shape="rect">Locale Filter</a>: specify that a piece of content is only applicable to certain locales. </p></li><li><p><a href="#provenance" shape="rect">Provenance</a>: communicate the identity of agents that have been involved in the translation of the content or the revision of the translated content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate that a reference points to potentially translatable data in a resource outside the document. Examples of such resources are external images and audio or video files.</p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a>: associate a given piece of source content (i.e. the content to be translated) and its corresponding target content (i.e. the source content translated into a given target language).</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>: identify a value that can be used as unique identifier for a given part of the content.
</p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a>: indicate how whitespace should be handled in content.</p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a>: describe the nature and severity of an error detected during a language-oriented quality assurance (QA) process.</p></li><li><p><a href="#lqrating" shape="rect">Localization Quality Rating</a>: express an overall measurement of the localization quality of a document or an item in a document.</p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a>: indicate the confidence that MT systems provide about their translation.
</p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a>: specify the characters that are permitted in a given piece of content.</p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a>: specify the maximum storage size of a given content.</p></li></ul></div><div class="div2">
@@ -683,7 +608,7 @@
and localization of XML schemas and documents.] The concept of a data
category is independent of its implementation in an XML and HTML environment (e.g. using
an element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "implementation" subsections in
- <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1529" id="d0e1529" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1540" id="d0e1540" shape="rect"/>Example 9: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
to whether a piece of content should be translated or not.</p><p>The simplest formalization of this prose description on a schema language independent
level is a <code class="its-attr-markup">translate</code> attribute with two possible values:
"yes" and "no". An implementation on a schema language specific
@@ -707,7 +632,7 @@
pointer itself, not the object to which it points. Thus in the following example, the
translation information specified via the <code class="its-elem-markup">translateRule</code> element applies to
the filename "instructions.jpg", and is not an instruction to open the
- graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-notation-terminology-1" id="EX-notation-terminology-1" shape="rect"/>Example 11: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></strong>
+ graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-notation-terminology-1" id="EX-notation-terminology-1" shape="rect"/>Example 10: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span>
<span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//p/img/@src"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -914,7 +839,7 @@
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="selection-local" id="selection-local" shape="rect"/>5.2.2 Local Selection in an XML Document</h4><p>Local selection in XML documents is realized with <a href="#local-attributes" shape="rect">ITS
local attributes</a> or the <code class="its-elem-markup">span</code> element. <code class="its-elem-markup">span</code> serves just as a
carrier for the local ITS attributes.</p><p>The data category determines what is being selected. The necessary data category
- specific defaults are described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-local-1" id="EX-selection-local-1" shape="rect"/>Example 12: Defaults for various data categories</div><p>By default the content of all elements in a document is translatable. The attribute
+ specific defaults are described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-selection-local-1" id="EX-selection-local-1" shape="rect"/>Example 11: Defaults for various data categories</div><p>By default the content of all elements in a document is translatable. The attribute
<code>its:translate="no"</code> in the <code>head</code> element means that the
content of this element, including child elements, should not be translated. The
attribute <code>its:translate="yes"</code> in the <code>title</code> element means
@@ -948,9 +873,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2440" id="d0e2440" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2451" id="d0e2451" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2451" id="d0e2451" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+<h5><a name="d0e2462" id="d0e2462" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
which starts with "<code>/</code>". That is, it must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a>s as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
[973 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/10 03:51:56 1.17
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/11 05:31:53 1.18
@@ -154,13 +154,9 @@
the
- corresponding approach to production in many cases encompasses
+ corresponding approach to multilingual production in many cases encompasses
- three
-
- phases: internationalize, translate,
-
- and localize (see the <ref target="http://www.w3.org/International/questions/qa-i18n/"> W3C's Internationalization Q&A</ref>
+ three phases: internationalization, translation, and localization (see the <ref target="http://www.w3.org/International/questions/qa-i18n/"> W3C's Internationalization Q&A</ref>
for more information related to these concepts).
@@ -194,15 +190,7 @@
internationalization.
- For
-
- example, people authoring in languages such as Arabic, Hebrew,
-
- Persian or Urdu need special markup to specify directionality in
-
- mixed
-
- direction text.
+A proprietary XML vocabulary may for example may be internationalized by defining special markup to specify directionality in mixed direction text.
</p>
@@ -226,7 +214,7 @@
linguistic
- dimensions such as mandatory terminology or standard
+ dimensions like mandatory terminology or standard
phrases.
@@ -238,7 +226,7 @@
missing,
- this phase is usually seen as encompassing activites such as
+this phase is usually seen as encompassing activities such as
creating locale-specific content (e.g. adding a link for a
@@ -286,7 +274,7 @@
translation, and localization related to core Web
- technologies. ITS does for example assist in usage scenarios in which parts of an
+ 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
@@ -307,130 +295,52 @@
Web content.
</p>
+ <p>
+
+ Like ITS 1.0, ITS 2.0
+
+ both identifies
+
+ concepts (such as
+
+ <q>Translate</q>
+
+ ), 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
+
+ definitions of ITS elements and attributes are provided in the
+
+ form of RELAX NG
+
+ <ptr target="#relaxng" type="bibref" />
+
+ (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 (<ptr target="#xliff1.2" type="bibref"/> and <ptr target="#xliff2.0" type="bibref"/>), as well as the Natural Language Processing Interchange Format <ptr target="#nif-reference" type="bibref"/>.</p>
+ <p>For the purpose of an introductory illustration, here is a serious of examples related to the question, how ITS can indicate that certain parts of a document must not be translated.</p>
- <p>ITS proposes several mechanisms which differ
-
- amongst others in terms of the usage scenario/user types for which the
-
- mechanism is most suitable. For the purpose of
-
- illustration, here is an example how ITS can indicate that certain parts of
-
- content should not be translated.</p>
-
- <exemplum xml:id="EX-ways-to-use-its-0">
-
- <head>Use of ITS to indicate that parts of an XML-based document - maybe to be transformed into HTML by a Web Content Management System (WCMS) -
-
- should or should not be translated</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>
-
- </exemplum>
-
- <note type="ed">Need to provide example: <![CDATA[
- <egXML xmlns="http://www.tei-c.org/ns/Examples" target="examples/xml/EX-ways-to-use-its-0.xml" />]]></note>
- <p>
-
- Like ITS 1.0, ITS 2.0
-
- both identifies
-
- concepts (such as
-
- <q>Translate</q>
-
- ), 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
-
- definitions of ITS elements and attributes are provided in the
-
- form of XML Schema
-
- <ptr target="#xmlschema1" type="bibref" />
-
- (non-normative)
-
- and RELAX NG
-
- <ptr target="#relaxng" type="bibref" />
-
- (normative).
-
- Since one major step from ITS 1.0 to ITS 2.0 relates to coverage for
-
- HTML, ITS 2.0 also regulates the relationship between ITS markup and
-
- the
-
- various HTML flavours.
-
- Furthermore, ITS 2.0
-
- suggests when and how to leverage
-
- processing based on the XML Localization
-
- Interchange File Format
-
- (XLIFF), as
-
- well as the
-
- Natural Language
-
- Processing Interchange
-
- Format
-
- <ref target="http://nlp2rdf.org/nif-1-0">NIF (NLP Interchange Format)</ref>
-
- .
-
- </p>
-
- <note type="ed">We need to have the example <ref target="examples/xml/EX-motivation-its-2.xml">EX-motivation-its-2.xml</ref> here since it was part of resolving <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/100">issue-100</ref>.</note>
<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>
+ <p>In this document it is difficult to distinguish between those <code>string</code> elements that should be translated and those that must not be translated. Explicit meta data is needed to resolve the issue.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-motivation-its-1.xml"/>
</exemplum>
+ <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>
+
<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>
+ <head>Document that uses two different ITS mechanisms to indicate that some parts must not be translated.</head>
+ <p>ITS provides two mechanisms to explicitly associate meta data with one or more pieces of content (e.g. XML nodes): a <ref target="#basic-concepts-selection-global">global</ref>, rule-based approach as well as a <ref target="#basic-concepts-selection-local">local</ref>, attribute-based approached). Here, for instance, a rule first specifies that no <code>data</code> element must be translated; later, an attribute <ref target="#basic-concepts-overinher">overwrites</ref> this rule for two of the <code>data</code> elements of type <val>text</val>.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-motivation-its-2.xml"/>
</exemplum>
@@ -438,14 +348,14 @@
<div xml:id="general-motiviation-for-ITS2.0"><head>General motivation for going beyond ITS 1.0</head>
- <p>The basics of ITS 1.0 fit onto a beer mat:</p>
+ <p>The basics of ITS 1.0 are simple:</p>
<list type="ordered">
<item>Provide meta data (e.g. <q>Do not translate</q>) to assist internationalization-related processes</item>
- <item>Use XPath (so-called <ref target="#selection-global">global appraoch</ref>) to tie the meta data to specific XML nodes (e.g. all elements named <code>uitext</code>) or put the meta data straight onto the XML nodes themselves (so-called <ref target="#def-local-attributes">local approach</ref>)</item>
+ <item><ref target="#selection-global">global appraoch</ref> 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 <ref target="#def-local-attributes">local approach</ref>)</item>
<item>Work with a well-defined set of meta data categories or values (e.g. only the values <val>yes</val> and <val>no</val> for certain data categories)</item>
@@ -453,56 +363,62 @@
- <p>This conciseness made real-world deployment easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <ref target="http://www.w3.org/International/its/ig/links.html">ITS Interest Group</ref> for example compiled a list of additional data categories (see this <ref target="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf">related summary</ref>). Some of these were then defined in ITS 2.0: <ref target="#idvalue">ID Value</ref>, local <ref target="#elements-within-text">Elements Within Text</ref>, <ref target="#preservespace">Preserve Space</ref>, and <ref target="#LocaleFilter">Locale Filte</ref>. Others are still discussed as requirements:</p>
+ <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 <ref target="http://www.w3.org/International/its/ig/links.html">ITS Interest Group</ref> for example compiled a list of additional data categories (see this <ref target="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf">related summary</ref>). Some of these were then defined in ITS 2.0: <ref target="#idvalue">ID Value</ref>, local <ref target="#elements-within-text">Elements Within Text</ref>, <ref target="#preservespace">Preserve Space</ref>, and <ref target="#LocaleFilter">Locale Filte</ref>. Others are still discussed as requirements for possible future versions of ITS:</p>
<list type="ordered">
<item><q>Context</q> = What specific related information might be helpful?</item>
-<item><q>Automated Language</q>: Does this content lend itself to automatic processing?</item></list>
+<item><q>Automated Language</q> = Does this content lend itself to automatic processing?</item></list>
<p>The real-world deployments also helped to understand that for the <ref target="http://www.webplatform.org/">Open Web Platform</ref> - 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>
<list type="ordered"><item>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</item>
- <item>Easy use of ITS in various Web-exposed Natural Language Processing contexts (e.g. machine translation, cross-language information retrieval, computer-supported linguistic quality assurance)</item>
+ <item>Easy use of ITS in various Web-exposed (multilingual) Natural Language Processing contexts</item>
+
+ <item>Computer-supported linguistic quality assurance</item>
+ <item>Content Management and translation platforms</item>
+ <item>Cross-language scenarios</item>
+ <item>Content enrichment</item>
+
- <item>Support for provenance <ptr target="#prov-overview" type="bibref"/>, <q>information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness</q></item>
+ <item>Support for W3C provenance <ptr target="#prov-overview" type="bibref"/>, <q>information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness</q></item>
<item>Provisions for extended deployment in Semantic Web/Linked Open Data scenarios.</item></list>
<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>
<list type="unordered">
- <item>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in production chains</item>
+ <item>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in multilingual production chains</item>
- <item>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to faciliate human translation</item>
+ <item>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</item>
- <item>Open standards endeavours (e.g. related to <ptr target="#xliff" type="bibref"/> and <ptr target="#nif-reference" type="bibref"/>) that are interested for example in lossless roundtripping of meta data in localization workflows.</item></list>
+ <item>Open standards endeavours (e.g. related to <ptr target="#xliff1.2" type="bibref"/>, <ptr target="#xliff2.0" type="bibref"/> and <ptr target="#nif-reference" type="bibref"/>) that are interested for example in information sharing, and lossless round tripping of meta data in localization workflows.</item></list>
- <p>One example outcome of work on the requirements is the <ref target="#its-tool-annotation">ITS Tool Annotation</ref> mechanism. It addresses the provenance-related requirement by allowing ITS processors to leave a trace: ITS processors can basically say "It is me that generated this bit of information". Another example are the <ptr target="#nif-reference" type="bibref"/> related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</p>
+ <p>One example outcome of the resulting synergies is the <ref target="#its-tool-annotation">ITS Tool Annotation</ref> mechanism. It addresses the provenance-related requirement by allowing ITS processors to leave a trace: ITS processors can basically say "It is me that generated this bit of information". Another example are the <ptr target="#nif-reference" type="bibref"/> related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</p>
</div>
<div xml:id="usage-scenarios"><head>Usage Scenarios</head>
- <p>The ITS 1.0 specification <ptr target="#its10" type="bibref"/> states in <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#introduction">the introduction</ref>: <q>ITS is a technology to easily create XML which is internationalized and can be localized effectively</q>. In order to make this tangible, ITS 1.0 provided examples for <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage">users and usages</ref>. 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>
+ <p>The <ptr target="#its10" type="bibref"/> <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#introduction">introduction</ref> states: <q>ITS is a technology to easily create XML which is internationalized and can be localized effectively</q>. In order to make this tangible, ITS 1.0 provided examples for <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage">users and usages</ref>. 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>
<list type="unordered">
- <item>Static mono-lingual: This part of the content has the directionality <q>right-to-left</q>.</item>
+ <item>Static mono-lingual (the area for example of content authors): This part of the content has the directionality <q>right-to-left</q>.</item>
- <item>Dynamic multi-lingual: This part of the content should be excluded from a possible translation phase.</item>
+ <item>Dynamic multi-lingual: (the area for example of machine translation systems): This part of the content must not be translated.</item>
</list>
- <p>Although the ITS 1.0 made no assumptions about possible phases in a production process chain, it was slanted towards a simple three phase <q>write->internationalize->translate</q> 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>
+ <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 <q>write->internationalize->translate</q> 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>
<list type="unordered">
<item>Internationalization</item>
@@ -529,7 +445,7 @@
<p>The document <ptr target="#mlw-metadata-us-impl" type="bibref"/> lists a large variety of usage scenarios for ITS 2.0. Most of them are composed of several of the aforementioned phases.</p>
- <p>In a similar vein, ITS 2.0 takes a much more comprehensive view on the actors that may participate in a multi-lingual content production process. ITS 1.0 annotations (e.g. local markup for the <ref target="#terminology">Terminology</ref> data category) most of the time were conceived as being closely tied to human actors such as content authors or information architects. ITS 2.0 raises non-human actors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity idenfiers/disambiguators to the same level. This change amongst others is reflected in the introduction of the ITS 2.0 <ref target="#its-tool-annotation">Tool Annotation</ref> which allows systems to record that they have processed as certain part of content.</p>
+ <p>In a similar vein, ITS 2.0 takes a much more comprehensive view on the actors that may participate in a multi-lingual content production process. ITS 1.0 annotations (e.g. local markup for the <ref target="#terminology">Terminology</ref> data category) most of the time were conceived as being closely tied to human actors such as content authors or information architects. ITS 2.0 raises non-human actors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity identifiers/disambiguators to the same level. This change amongst others is reflected by the ITS 2.0 <ref target="#its-tool-annotation">Tool Annotation</ref> which allows systems to record that they have processed as certain part of content.</p>
</div>
@@ -538,11 +454,11 @@
<p>The differences between ITS 1.0 and ITS 2.0 can be summarized as follows.</p>
- <p><emph>Coverage of <ptr type="bibref" target="#html5"/>: </emph>ITS 1.0 provides data categories to be applied to XML content. ITS 2.0 extends the coverage to <ptr target="#html5" type="bibref"/>. Explanatory details about ITS 2.0 and <ptr target="#html5" type="bibref"/> is given in <ptr target="#specific-HTML-support" type="specref"/>.</p>
+ <p><emph>Coverage of <ptr type="bibref" target="#html5"/>: </emph>ITS 1.0 can be applied to XML content. ITS 2.0 extends the coverage to <ptr target="#html5" type="bibref"/>. Explanatory details about ITS 2.0 and <ptr target="#html5" type="bibref"/> are given in <ptr target="#specific-HTML-support" type="specref"/>.</p>
<p><emph>Addition of data categories</emph>: ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 2.0 data categories are given in <ptr target="#datacategories-summary" type="specref"/>.</p>
<p><emph>Modification of data categories</emph>:</p>
- <list><item> <p xml:id="ruby-in-its2">ITS 1.0 provided the <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation">Ruby data category</ref>. ITS 2.0 does not provide ruby since at the time of writing, because of the the <ref target="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</ref> was still under development. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p></item>
+ <list><item> <p xml:id="ruby-in-its2">ITS 1.0 provided the <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation">Ruby data category</ref>. ITS 2.0 does not provide ruby since at the time of writing, because of the the <ref target="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</ref> was still under development. Once these discussions are settled, the Ruby data category possibly will be re-introduced, in a subsequent version of ITS.</p></item>
<item> <p>The <ref target="#directionality">Directionality</ref> data category reflects directionality markup in <ptr target="#html4" type="bibref"/>. The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.</p></item></list>
<p><emph>Additional or modified mechanisms:</emph> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0.</p>
@@ -553,52 +469,14 @@
<item>ITS 2.0 has a <ref target="#its-tool-annotation">ITS Tools Annotation</ref> mechanism to associate processor information with the use of individual data categories. See <ptr target="#traceability" type="specref"/> for details.</item>
</list>
- <p><emph>Mappings:</emph> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <ptr target="#nif-reference" type="bibref"/> and links to guidance about ITS 2.0 and XLIFF. See <ptr target="#mapping-conversion" type="specref"/> for details.</p>
+ <p><emph>Mappings:</emph> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <ptr target="#nif-reference" type="bibref"/> and links to guidance about how to relate ITS 2.0 to XLIFF. See <ptr target="#mapping-conversion" type="specref"/> for details.</p>
<p><emph>Changes to the conformance section</emph>: The <ptr target="#conformance" type="specref"/> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed, and a conformance clause related to processing <ptr type="bibref" target="#nif-reference"/> has been added. For <ptr target="#html5" type="bibref"/>, a dedicated conformance section has been created. Finally, a conformance clause related to Non-ITS elements and attributes has been added.</p>
-
- <!-- http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jan/0018.html
-
-
-
-1. list of additional data categories (that's already in the current draft)
-
-2. modified data categories (e.g. "termConfidence" for term, or the model for Ruby)
-
-3. query language on rules element
-
-4. parameters/variables in selectors
-
-5. modified selectors (absolute and relative)
-
-6. toolsRef to record which tools generated data category related information
-
-7. changes to conformance section (e.g. clause for processing ITS with HTML)
-
-8. conversion to NIF
-
-9. more "implementation hints" (e.g. RDFa Lite)
-
-
-
-Furthermore, the section could mention some additional background:
-
-
-
-10. (implicit) clustering of data categories (as in http://www.w3.org/TR/2012/WD-its2req-20120524/#Descriptions_of_proposed_metadata_categories)
-
-11. liasons and coordination (e.g. attention to Unicode registered extensions "u" and "t")
-
-12. focus on real-world use cases (thus for example no "...confidence" for all data categories, since that would hardly be needed)
-
-
-
- -->
</div>
<div xml:id="extended-implementation-hints"><head>Extended implementation hints</head>
- <p xml:id="unicode-normalization">As a general guidance, implementations of ITS 2.0 should use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided by <ptr target="#charmod-norm" type="bibref"/>.</p></div>
+ <p xml:id="unicode-normalization">As a general guidance, implementations of ITS 2.0 should use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <ptr target="#charmod-norm" type="bibref"/>.</p></div>
</div>
[22 lines skipped]
Received on Tuesday, 11 June 2013 05:32:00 UTC