- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Tue, 20 Nov 2012 12:41:56 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv24755
Modified Files:
its20-before-online-spec-editing-call.html its20.html
its20.odd
Log Message:
updated before life editing doc
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-before-online-spec-editing-call.html 2012/11/13 15:24:48 1.2
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-before-online-spec-editing-call.html 2012/11/20 12:41:56 1.3
@@ -6,14 +6,13 @@
</style><link rel="stylesheet" href="local.css" type="text/css"/><link rel="stylesheet" type="text/css" href="base.css"/></head><body><div class="head">
<h1><a name="title" id="title" shape="rect"/>Internationalization Tag Set (ITS) Version 2.0</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Copy</h2><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a> © 2012 <a href="http://www.w3.org/" shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer" shape="rect">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks" shape="rect">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents" shape="rect">document use</a> rules apply.</p></div><hr/><div>
-<h2><a name="abstract" id="abstract" shape="rect"/>Abstract</h2><p>This document defines data categories and their implementation as a set of elements
- and attributes called the <em>Internationalization Tag Set (ITS)</em> 2.0. ITS
- 2.0 is the successor of <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS
- 1.0</a>; it is designed to foster the creation of multilingual Web content,
- focusing on HTML5, XML based formats in general, and to leverage localization
- workflows based on the XML Localization Interchange File Format (XLIFF). In addition
- to using ITS 2.0 for HTML5 and XML content, an algorithm to convert that content to NIF is
- provided.</p></div><div>
+<h2><a name="abstract" id="abstract" shape="rect"/>Abstract</h2><p>This document defines data categories and their implementation as a set of elements and
+ attributes called the <em>Internationalization Tag Set (ITS)</em> 2.0. ITS 2.0 is the
+ successor of <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a>; it is
+ designed to foster the creation of multilingual Web content, focusing on HTML5, XML based
+ formats in general, and to leverage localization workflows based on the XML Localization
+ Interchange File Format (XLIFF). In addition to using ITS 2.0 for HTML5 and XML content, an
+ algorithm to convert that content to NIF is provided.</p></div><div>
<h2><a name="status" shape="rect">Status of this Document</a></h2><p><strong>This document is an editors' copy that has no official
standing.</strong></p></div><div class="toc">
<h2><a name="contents" id="contents" shape="rect"/>Table of Contents</h2><div class="toc"><div class="toc1">1 <a href="#introduction" shape="rect">Introduction</a><div class="toc2">1.1 <a href="#relation-to-its10-and-new-principles" shape="rect">Relation to ITS 1.0 and New Principles</a><div class="toc3">1.1.1 <a href="#relation-to-its10" shape="rect">Relation to ITS 1.0</a></div>
@@ -53,15 +52,16 @@
<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="#d0e2162" shape="rect">XPath 1.0</a></div>
-<div class="toc3">5.3.3 <a href="#d0e2342" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2381" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2161" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.3 <a href="#d0e2341" shape="rect">CSS Selectors</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2380" shape="rect">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param" shape="rect">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules" shape="rect">Link to External Rules</a></div>
<div class="toc2">5.5 <a href="#selection-precedence" shape="rect">Precedence between Selections</a></div>
<div class="toc2">5.6 <a href="#associating-its-with-existing-markup" shape="rect">Associating ITS Data Categories with Existing Markup</a></div>
<div class="toc2">5.7 <a href="#conversion-to-nif" shape="rect">Conversion to NIF</a></div>
+<div class="toc2">5.8 <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a></div>
</div>
<div class="toc1">6 <a href="#datacategory-description" shape="rect">Description of Data Categories</a><div class="toc2">6.1 <a href="#datacategories-defaults-etc" shape="rect">Position, Defaults, Inheritance and Overriding of Data Categories</a></div>
<div class="toc2">6.2 <a href="#trans-datacat" shape="rect">Translate</a><div class="toc3">6.2.1 <a href="#translatability-definition" shape="rect">Definition</a></div>
@@ -94,8 +94,8 @@
<div class="toc2">6.11 <a href="#LocaleFilter" shape="rect">Locale Filter</a><div class="toc3">6.11.1 <a href="#LocaleFilter-definition" shape="rect">Definition</a></div>
<div class="toc3">6.11.2 <a href="#LocaleFilter-implementation" shape="rect">Implementation</a></div>
</div>
-<div class="toc2">6.12 <a href="#translation-agent-provenance" shape="rect">Translation Agent Provenance</a><div class="toc3">6.12.1 <a href="#translation-agent-provenance-definition" shape="rect">Definition</a></div>
-<div class="toc3">6.12.2 <a href="#translation-agent-provenance-implementation" shape="rect">Implementation</a></div>
+<div class="toc2">6.12 <a href="#provenance" shape="rect">Provenance</a><div class="toc3">6.12.1 <a href="#provenance-definition" shape="rect">Definition</a></div>
+<div class="toc3">6.12.2 <a href="#provenance-implementation" shape="rect">Implementation</a></div>
</div>
<div class="toc2">6.13 <a href="#TextAnalyisAnnotation" shape="rect">TextAnalyisAnnotation</a></div>
<div class="toc2">6.14 <a href="#externalresource" shape="rect">External Resource</a><div class="toc3">6.14.1 <a href="#externalresource-definition" shape="rect">Definition</a></div>
@@ -146,68 +146,56 @@
</div><hr/><div class="body"><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="introduction" id="introduction" shape="rect"/>1 Introduction</h2><p>
<em>This section is informative.</em>
- </p><p>ITS 2.0 is a technology to add metadata to Web content, for the benefit of
- localization, language technologies, and internationalization. The ITS 2.0
- specification both identifies concepts (such as “Translate”) that are
- important for internationalization and localization, and defines implementations
- of these concepts (termed “ITS data categories”) as a set of elements and
- attributes called the <em>Internationalization Tag Set (ITS)</em>. The
- document provides implementations for HTML5, serializations in <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF</a>, and provides definitions
- of ITS elements and attributes in the form of XML Schema <a title="XML
								Schema Part 1: Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based
							validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.</p><p>This document aims to realize many of the ideas formulated in the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/" shape="rect">ITS 2.0 Requirements
- document</a>, in <a title="Internationalization and Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a> and <a title="Requirements for Localizable DTD Design" href="#reqlocdtd" shape="rect">[Localizable DTDs]</a>.</p><p>Not all requirements listed there are addressed in this document. Those which are
- not addressed here are either covered in <a title="Best
								Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a> (potentially in an as yet unwritten best practice
- document on multilingual Web content), or may be addressed in a future version
- of this specification.</p><div class="div2">
+ </p><p>ITS 2.0 is a technology to add metadata to Web content, for the benefit of localization,
+ language technologies, and internationalization. The ITS 2.0 specification both identifies
+ concepts (such as “Translate”) that are important for internationalization and
+ localization, and defines implementations of these concepts (termed “ITS data categories”)
+ as a set of elements and attributes called the <em>Internationalization Tag Set
+ (ITS)</em>. The document provides implementations for HTML5, serializations in <a href="http://nlp2rdf.org/nif-1-0" shape="rect">NIF</a>, and provides definitions of ITS elements
+ and attributes in the form of XML Schema <a title="XML Schema Part 1:
 Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and
+ RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.</p><p>This document aims to realize many of the ideas formulated in the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/" shape="rect">ITS 2.0 Requirements
+ document</a>, in <a title="Internationalization and
 Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a> and <a title="Requirements for Localizable
 DTD Design" href="#reqlocdtd" shape="rect">[Localizable DTDs]</a>.</p><p>Not all requirements listed there are addressed in this document. Those which are not
+ addressed here are either covered in <a title="Best
 Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>
+ (potentially in an as yet unwritten best practice document on multilingual Web content),
+ or may be addressed in a future version of this specification.</p><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="relation-to-its10-and-new-principles" id="relation-to-its10-and-new-principles" shape="rect"/>1.1 Relation to ITS 1.0 and New Principles</h3><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="relation-to-its10" id="relation-to-its10" shape="rect"/>1.1.1 Relation to ITS 1.0</h4><p>ITS 2.0 has the following relations to ITS 1.0:</p><ul><li><p>It adopts and maintains the following principles from ITS 1.0:
- </p><ul><li><p>It adopts the use of data categories to define discrete
- units of functionality</p></li><li><p>It adopts the separation of data category definition from
- the mapping of the data category to a given content
- format</p></li><li><p>It adopts the conformance principle of ITS1.0 that an
- implementation only needs to implement one data category to
- claim conformance to ITS 2.0</p></li></ul></li><li><p>ITS 2.0 supports all ITS 1.0 data category definitions and adds
- new definitions, with the exceptions of <a href="#directionality" shape="rect">Directionality</a> and <a href="#ruby-annotation" shape="rect">Ruby</a>.</p></li><li><p>ITS 2.0 adds a number of new data categories not found in ITS
- 1.0.</p></li><li><p>While ITS 1.0 addressed only XML, ITS 2.0 specifies
- implementations of data categories in <em>both</em> XML
- <em>and</em> HTML5.</p></li><li><p>Where ITS 1.0 data categories are implemented in XML, the
- implementation must be conformant with the ITS 1.0 approach to XML
- to claim conformance to ITS 2.0.</p></li></ul></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="new-principles" id="new-principles" shape="rect"/>1.1.2 New Principles</h4><p>ITS 2.0 also adds the following principles and features not found in ITS
- 1.0:</p><ul><li><p>ITS 2.0 data categories are intended to be format neutral, with
- support for XML, HTML5, and NIF: a data category
- implementation only needs to support a single content format mapping
- in order to support a claim of ITS 2.0 conformance.</p></li><li><p>ITS 2.0 provides algorithms to generate NIF out of HTML5
- or XML with ITS 2.0 metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the XPath
- version 1.0. Other versions of XPath or other query languages (e.g.,
- CSS selectors) can be expressed via a dedicated <a href="#queryLanguage" shape="rect">queryLanguage</a> attribute.</p></li></ul><p>As of the time of this writing, the new data categories included in ITS
- 2.0 are:</p><span class="editor-note">[Ed. note: Below needs to be updated before each publication before last call.]</span><ul><li><p><a href="#domain" shape="rect">Domain</a></p></li><li><p><a href="#Disambiguation" shape="rect">Disambiguation</a></p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a></p></li><li><p><a href="#translation-agent-provenance" shape="rect">Translation Agent Provenance</a></p></li><li><p><a href="#TextAnalyisAnnotation" shape="rect">Text Analysis
- Annotation</a></p></li><li><p><a href="#externalresource" shape="rect">External Resource</a></p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a></p></li><li><p><a href="#idvalue" shape="rect">Id Value</a></p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a></p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a></p></li><li><p><a href="#lqprecis" shape="rect">Localization Quality Précis</a></p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a></p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a></p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a></p></li></ul></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="motivation-its" id="motivation-its" shape="rect"/>1.2 Motivation for ITS</h3><p>Content or software that is authored in one language (the <span class="new-term">source
- language</span>) is often made available in additional languages or
- adapted with regard to other cultural aspects. This is done through a
- process called <span class="new-term">localization</span>, where the original material is
- translated and adapted to the target audience.</p><p>In addition, document formats expressed by schemas may be used by people in
- different parts of the world, and these people may need special markup to
- support the local language or script. For example, people authoring in
- languages such as Arabic, Hebrew, Persian, or Urdu need special markup to
- specify directionality in mixed direction text.</p><p>From the viewpoints of feasibility, cost, and efficiency, it is important
- that the original material should be suitable for localization. This is
- achieved by appropriate design and development, and the corresponding
- process is referred to as internationalization. For a detailed explanation
- of the terms “localization” and “internationalization”, see <a title="" href="#geo-i18n-l10n" shape="rect">[l10n i18n]</a>.</p><span class="editor-note">[Ed. note: Note: This should refer to the best practice document as well,
- when ready.]</span><p>The increasing usage of XML as a medium for documentation-related content
- (e.g. DocBook and DITA as formats for writing structured documentation, well
- suited to computer hardware and software manuals) and software-related
- content (e.g. the eXtensible User Interface Language <a title="exTensible User Interface
								Language" href="#xul" shape="rect">[XUL]</a>) creates challenges and opportunities in the domain of
- XML internationalization and localization.</p><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="motivation-its-issues" id="motivation-its-issues" shape="rect"/>1.2.1 Typical Problems</h4><p>The following examples sketch one of the issues that currently hinder
- efficient XML-related localization: the lack of a standard, declarative
- mechanism that identifies which parts of an XML document need to be
- translated. Tools often cannot automatically perform this
- identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e339" id="d0e339" shape="rect"/>Example 1: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those
- <code>string</code> elements that are translatable and those that
- are not. Only the addition of an explicit flag could resolve the
- issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="relation-to-its10" id="relation-to-its10" shape="rect"/>1.1.1 Relation to ITS 1.0</h4><p>ITS 2.0 has the following relations to ITS 1.0:</p><ul><li><p>It adopts and maintains the following principles from ITS 1.0: </p><ul><li><p>It adopts the use of data categories to define discrete units of
+ functionality</p></li><li><p>It adopts the separation of data category definition from the mapping of the
+ data category to a given content format</p></li><li><p>It adopts the conformance principle of ITS1.0 that an implementation only
+ needs to implement one data category to claim conformance to ITS 2.0</p></li></ul></li><li><p>ITS 2.0 supports all ITS 1.0 data category definitions and adds new definitions,
+ with the exceptions of <a href="#directionality" shape="rect">Directionality</a> and <a href="#ruby-annotation" shape="rect">Ruby</a>.</p></li><li><p>ITS 2.0 adds a number of new data categories not found in ITS 1.0.</p></li><li><p>While ITS 1.0 addressed only XML, ITS 2.0 specifies implementations of data
+ categories in <em>both</em> XML <em>and</em> HTML5.</p></li></ul></div><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="new-principles" id="new-principles" shape="rect"/>1.1.2 New Principles</h4><p>ITS 2.0 also adds the following principles and features not found in ITS 1.0:</p><ul><li><p>ITS 2.0 data categories are intended to be format neutral, with support for XML,
+ HTML5, and NIF: a data category implementation only needs to support a single
+ content format mapping in order to support a claim of ITS 2.0 conformance.</p></li><li><p>ITS 2.0 provides algorithms to generate NIF out of HTML5 or XML with ITS 2.0
+ metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the XPath version 1.0.
+ Other versions of XPath or other query languages (e.g., CSS selectors) can be
+ expressed via a dedicated <a href="#queryLanguage" shape="rect">queryLanguage</a>
+ attribute.</p></li></ul><p>As of the time of this writing, the new data categories included in ITS 2.0 are:</p><span class="editor-note">[Ed. note: Below needs to be updated before each publication before last
+ call.]</span><ul><li><p><a href="#domain" shape="rect">Domain</a></p></li><li><p><a href="#Disambiguation" shape="rect">Disambiguation</a></p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a></p></li><li><p><a href="#provenance" shape="rect">Provenance</a></p></li><li><p><a href="#TextAnalyisAnnotation" shape="rect">Text Analysis Annotation</a></p></li><li><p><a href="#externalresource" shape="rect">External Resource</a></p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a></p></li><li><p><a href="#idvalue" shape="rect">Id Value</a></p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a></p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a></p></li><li><p><a href="#lqprecis" shape="rect">Localization Quality Précis</a></p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a></p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a></p></li><li><p><a href="#storagesize" shape="rect">Storae Size</a></p></li></ul></div></div><div class="div2">
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="motivation-its" id="motivation-its" shape="rect"/>1.2 Motivation for ITS</h3><p>Content or software that is authored in one language (the <span class="new-term">source language</span>)
+ is often made available in additional languages or adapted with regard to other cultural
+ aspects. This is done through a process called <span class="new-term">localization</span>, where the
+ original material is translated and adapted to the target audience.</p><p>In addition, document formats expressed by schemas may be used by people in different
+ parts of the world, and these people may need special markup to support the local
+ language or script. For example, people authoring in languages such as Arabic, Hebrew,
+ Persian, or Urdu need special markup to specify directionality in mixed direction
+ text.</p><p>From the viewpoints of feasibility, cost, and efficiency, it is important that the
+ original material should be suitable for localization. This is achieved by appropriate
+ design and development, and the corresponding process is referred to as
+ internationalization. For a detailed explanation of the terms “localization” and
+ “internationalization”, see <a title="" href="#geo-i18n-l10n" shape="rect">[l10n i18n]</a>.</p><span class="editor-note">[Ed. note: Note: This should refer to the best practice document as well, when
+ ready.]</span><p>The increasing usage of XML as a medium for documentation-related content (e.g. DocBook
+ and DITA as formats for writing structured documentation, well suited to computer
+ hardware and software manuals) and software-related content (e.g. the eXtensible User
+ Interface Language <a title="exTensible User Interface Language" href="#xul" shape="rect">[XUL]</a>) creates challenges and
+ opportunities in the domain of XML internationalization and localization.</p><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="motivation-its-issues" id="motivation-its-issues" shape="rect"/>1.2.1 Typical Problems</h4><p>The following examples sketch one of the issues that currently hinder efficient
+ XML-related localization: the lack of a standard, declarative mechanism that
+ identifies which parts of an XML document need to be translated. Tools often cannot
+ automatically perform this identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e336" id="d0e336" shape="rect"/>Example 1: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those <code>string</code>
+ elements that are translatable and those that are not. Only the addition of an
+ explicit flag could resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
<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>
@@ -229,12 +217,10 @@
<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="d0e354" id="d0e354" shape="rect"/>Example 2: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text,
- the conditions may be quite complex and not directly indicated with
- a simple flag. Here, for instance, only the text in the nodes
- matching the expression
- <code>//component[@type!='image']/data[@type='text']</code> is
- translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><dialogue</strong> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-gb"</span><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><div class="exampleOuter"><div class="exampleHeader"><a name="d0e351" id="d0e351" shape="rect"/>Example 2: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text, the conditions
+ may be quite complex and not directly indicated with a simple flag. Here, for
+ instance, only the text in the nodes matching the expression
+ <code>//component[@type!='image']/data[@type='text']</code> is translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><dialogue</strong> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-gb"</span><strong class="hl-tag" style="color: #000096">></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>
@@ -251,69 +237,92 @@
<strong class="hl-tag" style="color: #000096"></dialogue></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">examples/xml/EX-motivation-its-2.xml</a>]</p></div></div></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="users-usage" id="users-usage" shape="rect"/>1.3 Users and Usages of ITS</h3><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="potential-users" id="potential-users" shape="rect"/>1.3.1 Potential Users of ITS</h4><p>The ITS specification aims to provide different types of users with
- information about what markup should be supported to enable worldwide
- use and effective internationalization and localization of content. The
- following paragraphs sketch these different types of users, and their
- usage of ITS. In order to support all of these users, the information
- about what markup should be supported to enable worldwide use and
- effective localization of content is provided in this specification in
- two ways:</p><ul><li><p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a></p></li></ul><div class="div4">
-<h5><a name="schema-dev-new" id="schema-dev-new" shape="rect"/>1.3.1.1Schema developers starting a schema from the ground up</h5><p>This type of user will find proposals for attribute and element names
- to be included in their new schema (also called "host vocabulary").
- Using the attribute and element names proposed in the ITS
- specification may be helpful because it leads to easier recognition
- of the concepts represented by both schema users and processors. It
- is perfectly possible, however, for a schema developer to develop
- his own set of attribute and element names. The specification sets
- out, first and foremost, to ensure that the required markup is
- available, and that the behavior of that markup meets established
- needs.</p></div><div class="div4">
-<h5><a name="schema-dev-existing" id="schema-dev-existing" shape="rect"/>1.3.1.2Schema developers working with an existing schema</h5><p>This type of user will be working with schemas such as DocBook, DITA,
- or perhaps a proprietary schema. The ITS Working Group has sought
- input from experts developing widely used formats such as the ones
- mentioned.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The question "How to use ITS with existing popular markup
- schemes?" is covered in more details (including examples) in a
- separate document: <a title="Best
								Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p></div><p>Developers working on existing schemas should check whether their
- schemas support the markup proposed in this specification, and,
- where appropriate, add the markup proposed here to their schema.</p><p>In some cases, an existing schema may already contain markup
- equivalent to that recommended in ITS. In this case it is not
- necessary to add duplicate markup since ITS provides mechanisms for
- associating ITS markup with markup in the host vocabulary which
- serves a similar purpose (see <a class="section-ref" href="#associating-its-with-existing-markup" shape="rect">Section 5.6: Associating ITS Data Categories with Existing Markup</a>). The developer should, however, check that the behavior
- associated with the markup in their own schema is fully compatible
- with the expectations described in this specification.</p></div><div class="div4">
-<h5><a name="content-tool-vendor" id="content-tool-vendor" shape="rect"/>1.3.1.3Vendors of content-related tools</h5><p>This type of user includes companies which provide tools for
- authoring, translation or other flavors of content-related software
- solutions. It is important to ensure that such tools enable
- worldwide use and effective localization of content. For example,
- translation tools should prevent content marked up as not for
- translation from being changed or translated. It is hoped that the
- ITS specification will make the job of vendors easier by
- standardizing the format and processing expectations of certain
- relevant markup items, and allowing them to more effectively
- identify how content should be handled.</p></div><div class="div4">
-<h5><a name="d0e412" id="d0e412" shape="rect"/>1.3.1.4Content producers</h5><p>This type of user comprises authors, translators and other types of
- content author. The markup proposed in this specification may be
- used by them to mark up specific bits of content. Aside: The burden
- of inserting markup can be removed from content producers by
- relating the ITS information to relevant bits of content in a global
- manner (see <a href="#selection-global" shape="rect">global, rule-based
- approach</a>). This global work, however, may fall to
- information architects, rather than the content producers
- themselves.</p></div><div class="div4">
-<h5><a name="users_machine-translation" id="users_machine-translation" shape="rect"/>1.3.1.5Machine Translation Systems</h5><p>This type of service is intended for a broad user community ranging from developers and integrators through translation companies and agencies, freelance translators and post-editors to ordinary translation consumers and other types of MT employment. Data categories are envisaged for supporting and guiding the different automated backend processes of this service type, thereby adding substantial value to the service results as well as possible subsequent services. These processes include basic tasks, like parsing constraints and markup, and compositional tasks, such as disambiguation. These tasks consume and generate valuable metadata from and for third party users, for example, provenance information and quality scoring, and add relevant information for follow-on tasks, processes and services, such as MT post-editing, MT training and MT terminological enhancement.</p></div><div clss="div4">
-<h5><a name="users_text_analytics" id="users_text_analytics" shape="rect"/>1.3.1.6Text Analytics</h5><p>These types of users fulfil the role of providing services for automatic generation of metadata for improving localization, data integration or knowledge management workflows. This class of users comprises of developers and integrators of services that automate language technology tasks such as domain classification, named entity recognition and disambiguation, term extraction, language identification and others. Text analytics services generate data that contextualizes the raw content with more explicit information. This can be used to improve the output quality in machine translation systems, search result relevance in information retrieval systems, as well as management and integration of unstructured data in knowledge management systems.</p></div><div class="div4">
-<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers" shape="rect"/>1.3.1.7Localization Workflow Managers</h5><p>This type of users is concerend with localization workflows in which content goes through certain steps: preparation for localization, start of the localization process by e.g. a conversion into a bitext format like <a title="" href="#xliff" shape="rect">[XLIFF]</a>, the actual localization by human translators or machine translation and other adaptations of content, and finally the integration of the localized content into the original format. That format is often based on XML or HTML; (Web) content management systems are widely used for content creation, and their integration with localization workflows is an important task for the workflow manager. For the integration of content creation and localization, metadata plays a crucial role. E.g. an ITS data category like <a href="#trans-datacat" shape="rect">translate</a> can trigger the extraction of localizble text. "<span class="quote">Metadata roundtripping</span>", that is the availibility of metadata both before and after the localization process is crucial for many tasks of the localization workflow manager. An example is metadata based quality control, with checks like "<span class="quote">Have all pieces of content set to <code>translate="no"</code> been left unchanged?</span>". Other pieces of metadata are relevant for proper internationalization during the localization workflow, e.g. the availibility of <a href="#directionality" shape="rect">Directionality</a> markup for adequate visualization of bidirectional text.</p></div></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="ways-to-use-its" id="ways-to-use-its" shape="rect"/>1.3.2 Ways to Use ITS</h4><p>The ITS specification proposes several mechanisms for supporting
- worldwide use and effective internationalization and localization of
- content. We will sketch them below by looking at them from the
- perspectives of certain user types. For the purpose of illustration, we
- will demonstrate how ITS can indicate that certain parts of content
- should or should not be translated.</p><ul><li><p>A content author uses an attribute on a particular element to say
- that the text in the element should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-ways-to-use-its-1" id="EX-ways-to-use-its-1" shape="rect"/>Example 3: Use of ITS by content author</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 class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="potential-users" id="potential-users" shape="rect"/>1.3.1 Potential Users of ITS</h4><p>The ITS specification aims to provide different types of users with information about
+ what markup should be supported to enable worldwide use and effective
+ internationalization and localization of content. The following paragraphs sketch
+ these different types of users, and their usage of ITS. In order to support all of
+ these users, the information about what markup should be supported to enable worldwide
+ use and effective localization of content is provided in this specification in two
+ ways:</p><ul><li><p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix E: Schemas for ITS</a></p></li></ul><div class="div4">
+<h5><a name="schema-dev-new" id="schema-dev-new" shape="rect"/>1.3.1.1Schema developers starting a schema from the ground up</h5><p>This type of user will find proposals for attribute and element names to be
+ included in their new schema (also called "host vocabulary"). Using the attribute
+ and element names proposed in the ITS specification may be helpful because it leads
+ to easier recognition of the concepts represented by both schema users and
+ processors. It is perfectly possible, however, for a schema developer to develop his
+ own set of attribute and element names. The specification sets out, first and
+ foremost, to ensure that the required markup is available, and that the behavior of
+ that markup meets established needs.</p></div><div class="div4">
+<h5><a name="schema-dev-existing" id="schema-dev-existing" shape="rect"/>1.3.1.2Schema developers working with an existing schema</h5><p>This type of user will be working with schemas such as DocBook, DITA, or perhaps a
+ proprietary schema. The ITS Working Group has sought input from experts developing
+ widely used formats such as the ones mentioned.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The question "How to use ITS with existing popular markup schemes?" is
+ covered in more details (including examples) in a separate document: <a title="Best
 Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p></div><p>Developers working on existing schemas should check whether their schemas support
+ the markup proposed in this specification, and, where appropriate, add the markup
+ proposed here to their schema.</p><p>In some cases, an existing schema may already contain markup equivalent to that
+ recommended in ITS. In this case it is not necessary to add duplicate markup since
+ ITS provides mechanisms for associating ITS markup with markup in the host
+ vocabulary which serves a similar purpose (see <a class="section-ref" href="#associating-its-with-existing-markup" shape="rect">Section 5.6: Associating ITS Data Categories with Existing Markup</a>). The developer
+ should, however, check that the behavior associated with the markup in their own
+ schema is fully compatible with the expectations described in this
+ specification.</p></div><div class="div4">
+<h5><a name="content-tool-vendor" id="content-tool-vendor" shape="rect"/>1.3.1.3Vendors of content-related tools</h5><p>This type of user includes companies which provide tools for authoring, translation
+ or other flavors of content-related software solutions. It is important to ensure
+ that such tools enable worldwide use and effective localization of content. For
+ example, translation tools should prevent content marked up as not for translation
+ from being changed or translated. It is hoped that the ITS specification will make
+ the job of vendors easier by standardizing the format and processing expectations of
+ certain relevant markup items, and allowing them to more effectively identify how
+ content should be handled.</p></div><div class="div4">
+<h5><a name="d0e409" id="d0e409" shape="rect"/>1.3.1.4Content producers</h5><p>This type of user comprises authors, translators and other types of content author.
+ The markup proposed in this specification may be used by them to mark up specific
+ bits of content. Aside: The burden of inserting markup can be removed from content
+ producers by relating the ITS information to relevant bits of content in a global
+ manner (see <a href="#selection-global" shape="rect">global, rule-based approach</a>). This
+ global work, however, may fall to information architects, rather than the content
+ producers themselves.</p></div><div class="div4">
+<h5><a name="users_machine-translation" id="users_machine-translation" shape="rect"/>1.3.1.5Machine Translation Systems</h5><p>This type of service is intended for a broad user community ranging from developers
+ and integrators through translation companies and agencies, freelance translators
+ and post-editors to ordinary translation consumers and other types of MT employment.
+ Data categories are envisaged for supporting and guiding the different automated
+ backend processes of this service type, thereby adding substantial value to the
+ service results as well as possible subsequent services. These processes include
+ basic tasks, like parsing constraints and markup, and compositional tasks, such as
+ disambiguation. These tasks consume and generate valuable metadata from and for
+ third party users, for example, provenance information and quality scoring, and add
+ relevant information for follow-on tasks, processes and services, such as MT
+ post-editing, MT training and MT terminological enhancement.</p></div><div class="div4">
+<h5><a name="users_text_analytics" id="users_text_analytics" shape="rect"/>1.3.1.6Text Analytics</h5><p>These types of users fulfil the role of providing services for automatic generation
+ of metadata for improving localization, data integration or knowledge management
+ workflows. This class of users comprises of developers and integrators of services
+ that automate language technology tasks such as domain classification, named entity
+ recognition and disambiguation, term extraction, language identification and others.
+ Text analytics services generate data that contextualizes the raw content with more
+ explicit information. This can be used to improve the output quality in machine
+ translation systems, search result relevance in information retrieval systems, as
+ well as management and integration of unstructured data in knowledge management
+ systems.</p></div><div class="div4">
+<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers" shape="rect"/>1.3.1.7Localization Workflow Managers</h5><p>This type of users is concerend with localization workflows in which content goes
+ through certain steps: preparation for localization, start of the localization
+ process by e.g. a conversion into a bitext format like <a title="" href="#xliff" shape="rect">[XLIFF]</a>, the actual localization by human translators or machine
+ translation and other adaptations of content, and finally the integration of the
+ localized content into the original format. That format is often based on XML or
+ HTML; (Web) content management systems are widely used for content creation, and
+ their integration with localization workflows is an important task for the workflow
+ manager. For the integration of content creation and localization, metadata plays a
+ crucial role. E.g. an ITS data category like <a href="#trans-datacat" shape="rect">translate</a> can trigger the extraction of localizable text. "<span class="quote">Metadata
+ roundtripping</span>", that is the availibility of metadata both before and after
+ the localization process is crucial for many tasks of the localization workflow
+ manager. An example is metadata based quality control, with checks like "<span class="quote">Have
+ all pieces of content set to <code>translate="no"</code> been left
+ unchanged?</span>". Other pieces of metadata are relevant for proper
+ internationalization during the localization workflow, e.g. the availibility of <a href="#directionality" shape="rect">Directionality</a> markup for adequate visualization of
+ bidirectional text.</p></div></div><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="ways-to-use-its" id="ways-to-use-its" shape="rect"/>1.3.2 Ways to Use ITS</h4><p>The ITS specification proposes several mechanisms for supporting worldwide use and
+ effective internationalization and localization of content. We will sketch them below
+ by looking at them from the perspectives of certain user types. For the purpose of
+ illustration, we will demonstrate how ITS can indicate that certain parts of content
+ should or should not be translated.</p><ul><li><p>A content author uses an attribute on a particular element to say that the text
+ in the element should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-ways-to-use-its-1" id="EX-ways-to-use-its-1" shape="rect"/>Example 3: Use of ITS by content author</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 class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>Building the Zebulon Toolkit<strong class="hl-tag" style="color: #000096"></title></strong>
<strong class="hl-tag" style="color: #000096"></head></strong>
@@ -323,11 +332,11 @@
batch file <strong class="hl-tag" style="color: #000096"><cmd</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>Build.bat<strong class="hl-tag" style="color: #000096"></cmd></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"></help></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-1.xml" shape="rect">examples/xml/EX-ways-to-use-its-1.xml</a>]</p></div><ul><li><p>A content author or information architect uses markup at the top
- of the document to identify a particular type of element or
- context in which the content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e486" id="d0e486" shape="rect"/>Example 4: Use of ITS by information architect</div><p>The <code>translateRule</code> element is used in the header of the
- document to indicate that none of the <code>path</code> or <code>cmd</code>
- elements should be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
+</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-1.xml" shape="rect">examples/xml/EX-ways-to-use-its-1.xml</a>]</p></div><ul><li><p>A content author or information architect uses markup at the top of the document
+ to identify a particular type of element or context in which the content should
+ not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e483" id="d0e483" shape="rect"/>Example 4: Use of ITS by information architect</div><p>The <code>translateRule</code> element is used in the header of the document to
+ indicate that none of the <code>path</code> or <code>cmd</code> elements should be
+ translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>Building the Zebulon Toolkit<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>
@@ -340,10 +349,9 @@
<strong class="hl-tag" style="color: #000096"><cmd></strong>Build.bat<strong class="hl-tag" style="color: #000096"></cmd></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"></help></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-2.xml" shape="rect">examples/xml/EX-ways-to-use-its-2.xml</a>]</p></div><ul><li><p>A processor may insert markup at the top of the document which
- links to ITS information outside of the document.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e511" id="d0e511" shape="rect"/>Example 5: Use of ITS by processor</div><p>A <code>rules</code> element is inserted in the header of the document.
- It has a XLink <code>href</code> attribute used to link to an <a href="#link-external-rules" shape="rect">ITS external rule</a>
- document.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
+</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-2.xml" shape="rect">examples/xml/EX-ways-to-use-its-2.xml</a>]</p></div><ul><li><p>A processor may insert markup at the top of the document which links to ITS
+ information outside of the document.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e508" id="d0e508" shape="rect"/>Example 5: Use of ITS by processor</div><p>A <code>rules</code> element is inserted in the header of the document. It has a XLink
+ <code>href</code> attribute used to link to an <a href="#link-external-rules" shape="rect">ITS external rule</a> document.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
<strong class="hl-tag" style="color: #000096"><title></strong>Building the Zebulon Toolkit<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>
@@ -355,18 +363,15 @@
<strong class="hl-tag" style="color: #000096"><cmd></strong>Build.bat<strong class="hl-tag" style="color: #000096"></cmd></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"></help></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml" shape="rect">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d0e532" id="d0e532" shape="rect"/>Example 6: ITS rule file shared by different documents</div><p>The <code>rules</code> element contains several ITS rules that are common
- to different documents. One of them is a <code>translateRule</code>
- element that indicates that no <code>path</code> or <code>cmd</code> element
- should be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">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>
+</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml" shape="rect">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d0e529" id="d0e529" shape="rect"/>Example 6: ITS rule file shared by different documents</div><p>The <code>rules</code> element contains several ITS rules that are common to different
+ documents. One of them is a <code>translateRule</code> element that indicates that no
+ <code>path</code> or <code>cmd</code> element should be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">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">"//path | //cmd"</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>
-</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-4.xml" shape="rect">examples/xml/EX-ways-to-use-its-4.xml</a>]</p></div><ul><li><p>A schema developer integrates ITS markup declarations in his
- schema to allow users to indicate that specific parts of the
- content should not be translated.</p></li></ul><span class="editor-note">[Ed. note: Following schema example has to updated once we have final XSD schema for ITS 2.0]</span><div class="exampleOuter"><div class="exampleHeader"><a name="d0e563" id="d0e563" shape="rect"/>Example 7: An XSD schema with ITS declaration</div><p>The declarations for the <code>translate</code> attribute
- is added to a group of common attributes <code>commonAtts</code>.
- This allows to use the <code>translate</code> attribute
- within the documents like in <a href="#EX-ways-to-use-its-1" shape="rect">Example 3</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><xs:schema</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:xs</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2001/XMLSchema"</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>
+</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-4.xml" shape="rect">examples/xml/EX-ways-to-use-its-4.xml</a>]</p></div><ul><li><p>A schema developer integrates ITS markup declarations in his schema to allow
+ users to indicate that specific parts of the content should not be translated.</p></li></ul><span class="editor-note">[Ed. note: Following schema example has to updated once we have final XSD schema
+ for ITS 2.0]</span><div class="exampleOuter"><div class="exampleHeader"><a name="d0e560" id="d0e560" shape="rect"/>Example 7: An XSD schema with ITS declaration</div><p>The declarations for the <code>translate</code> attribute is added to a
+ group of common attributes <code>commonAtts</code>. This allows to use the <code>translate</code> attribute within the documents like in <a href="#EX-ways-to-use-its-1" shape="rect">Example 3</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><xs:schema</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:xs</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2001/XMLSchema"</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>
[5061 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/11/20 12:37:44 1.238
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2012/11/20 12:41:56 1.239
@@ -3940,7 +3940,7 @@
<code>id</code> attribute of <code>script</code> element now the same as of containing
XML.</p></li><li><p>NIF example fix - see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/284" shape="rect">action-284</a>.</p></li><li><p>Added <a href="#css-selectors-feature-at-risk" shape="rect">a note</a> to mark CSS
selectors as feature at risk, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/272" shape="rect">action-272</a>.</p></li><li><p>Defined in <a class="section-ref" href="#xpath-relative-selector" shape="rect">Section 5.3.2.2: Relative selector</a> that an XPath
- based relative selector can also be an absolute location path - see the<code>domainPointer</code> attribute in <a href="#EX-domain-2" shape="rect">Example 53</a> and
+ based relative selector can also be an absolute location path - see the <code>domainPointer</code> attribute in <a href="#EX-domain-2" shape="rect">Example 53</a> and
<a href="https://www.w3.org/International/multilingualweb/lt/track/actions/282" shape="rect">action-282</a>.</p></li><li><p>Defined <a href="#directionality" shape="rect">Directionality</a> and <a href="#ruby-annotation" shape="rect">Ruby</a> as non-normative features. See <a class="section-ref" href="#relation-to-its10" shape="rect">Section 1.1.1: Relation to ITS 1.0</a>, <a href="#directionality-non-normative-explanation" shape="rect">note on directionality</a>, <a href="#ruby-non-normative-explanation" shape="rect">note on ruby</a>, and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/250" shape="rect">action-250</a>.</p></li><li><p>Update on <a href="#Disambiguation" shape="rect">Disambiguation</a> example <a href="#EX-disambiguation-html5-rdfa-companion-document" shape="rect">Example 56</a>. See <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/266" shape="rect">action-266</a> (<a href="http://www.w3.org/2012/11/01-mlw-lt-irc#T10-53-44"shape="rect">related discussion</a>).</p></li><li><p>Made a simplification of <a href="#disambiguation-global" shape="rect">Disambiguation used
global</a>. See <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/267" shape="rect">action-267</a>.</p></li><li><p>Added <a class="section-ref" href="#its-mime-type" shape="rect">Appendix B: Internationalization Tag Set (ITS) MIME Type</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/251" shape="rect">action-251</a>.</p></li><li><p>Added <a class="section-ref" href="#mtconfidence" shape="rect">Section 6.20: MT Confidence</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/287" shape="rect">action-287</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/288" shape="rect">action-288</a>.</p></li><li><p>Added <a class="section-ref" href="#its-tool-annotation" shape="rect">Section 5.8: ITS Tools Annotation</a> see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/301" shape="rect">action-301</a>.</p></li><li><p>Added confidence score attributes to < href="#Disambiguation" shape="rect">Disambiguation</a> and <a href="#mtconfidence" shape="rect">MTConfidence</a> data categories - see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/298" shape="rect">action-298</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/299" shape="rect">action-299</a>.</p></li><li><p>Updated <a class="section-ref" href="#provenance" shape="rect">Section 6.12: Provenance</a> - now called "<span class="quote">Provenance</span>" instead of "<span class="quote">Translation Agent Provenance</span>" - see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/300" shape="rect">action-300</a>.</p></li></ol><p id="changelog-since-20120829">The following log records major changes that have been
made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20120829/" shape="rect">ITS 2.0 Working Draft 29 August 2012</a>.</p><ol class="depth1"><li><p>Added a first draft of <a class="section-ref" href="#provenance" shape="rect">Section 6.12: Provenance</a></p></li><li><p>Added <a class="section-ref" href="#html5-markup" shape="rect">Section 7: Using ITS Markup in HTML5</a>.</p></li><li><p>Removed inline markup declarations.</p></li><li><p>Addition of a <code>locQualityPrecisVote</code> attribute and a
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/20 12:37:44 1.236
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/20 12:41:56 1.237
@@ -5761,8 +5761,7 @@
target="https://www.w3.org/International/multilingualweb/lt/track/actions/272"
>action-272</ref>.</item>
<item>Defined in <ptr target="#xpath-relative-selector" type="specref"/> that an XPath
- based relative selector can also be an absolute location path - see the
- <att>domainPointer</att> attribute in <ptr target="#EX-domain-2" type="exref"/> and
+ based relative selector can also be an absolute location path - see the <att>domainPointer</att> attribute in <ptr target="#EX-domain-2" type="exref"/> and
<ref target="https://www.w3.org/International/multilingualweb/lt/track/actions/282"
>action-282</ref>.</item>
<item>Defined <ref target="#directionality">Directionality</ref> and <ref
Received on Tuesday, 20 November 2012 12:42:08 UTC