- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Sun, 23 Jun 2013 17:24:05 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory gil:/tmp/cvs-serv4049/TR-version
Modified Files:
Overview.html
Log Message:
re-generated implementation report
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/05/22 19:17:52 1.89
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/06/23 17:24:05 1.90
@@ -5,17 +5,17 @@
</style><link rel="stylesheet" href="local.css" type="text/css"/><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css"/></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"/></a></p>
<h1><a name="title" id="title"></a>Internationalization Tag Set (ITS) Version 2.0</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Last Call Working Draft 21 May 2013</h2><dl><dt>This version:</dt><dd>
- <a href="http://www.w3.org/TR/2013/WD-its20-20130521/">
- http://www.w3.org/TR/2013/WD-its20-20130521/</a>
+<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Proposed Recommendation Working Draft 02 July 2013</h2><dl><dt>This version:</dt><dd>
+ <a href="http://www.w3.org/TR/2013/PR-its20-20130702/">
+ http://www.w3.org/TR/2013/PR-its20-20130702/</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/its20/">http://www.w3.org/TR/its20/</a>
- </dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2013/WD-its20-20130411/">
- http://www.w3.org/TR/2013/WD-its20-20130411/</a></dd><dt>Editors:</dt><dd>Shaun McCane, Invited Expert</dd><dd>Dave Lewis, TCD</dd><dd>Christian Lieske, SAP AG</dd><dd>Arle Lommel, DFKI</dd><dd>Jirka Kosek, UEP</dd><dd>Felix Sasaki, DFKI / W3C Fellow</dd><dd>Yves Savourel, ENLASO</dd></dl><p>This document is also available in these non-normative formats: <a href="its20.odd">ODD/XML document</a>, <a href="itstagset20.zip">self-contained zipped archive</a>, and <a href="diffs/diff-wd20130521-wd20130411.html">XHTML Diff markup to previous publication
+ </dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2013/WD-its20-20130521/">
+ http://www.w3.org/TR/2013/WD-its20-20130521/</a></dd><dt>Editors:</dt><dd>Shaun McCane, Invited Expert</dd><dd>Dave Lewis, TCD</dd><dd>Christian Lieske, SAP AG</dd><dd>Arle Lommel, DFKI</dd><dd>Jirka Kosek, UEP</dd><dd>Felix Sasaki, DFKI / W3C Fellow</dd><dd>Yves Savourel, ENLASO</dd></dl><p>This document is also available in these non-normative formats: <a href="its20.odd">ODD/XML document</a>, <a href="itstagset20.zip">self-contained zipped archive</a>, and <a href="diffs/diff-wd20130702-wd20130521.html">XHTML Diff markup to previous publication
2013-04-11</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
-<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>The technology described in this document - the <em>Internationalization Tag Set (ITS)
- 2.0</em> - enhances the foundation to integrate automated processing of human language
- into core Web technologies. ITS 2.0 bears many commonalities with is predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</a> but provides additional
+<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>The technology described in this document – the <em>Internationalization Tag Set (ITS)
+ 2.0</em> – enhances the foundation to integrate automated processing of human language
+ into core Web technologies. ITS 2.0 bears many commonalities with its predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</a> but provides additional
concepts that are designed to foster the automated creation and processing of multilingual
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
processing based on the XML Localization Interchange File Format (XLIFF), as well as the
@@ -32,43 +32,36 @@
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
processing based on the XML Localization Interchange File Format (XLIFF), as well as the
Natural Language Processing Interchange Format (NIF).</p><p>This document was published by the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
- Group</a> as a Last Call Working Draft. The Last Call period ends 11 June 2013. The publication reflects changes made since the previous
- <a href="http://www.w3.org/TR/2012/WD-its20-20121206/">Last Call publication 6 December 2012</a> and the <a href="http://www.w3.org/TR/2013/WD-its20-20130411/">ordinary working draft 11 April 2013</a>. The Working Group expects to advance this
+ Group</a> as a Proposed Recommendation Working Draft. Comments submitted against the <a href="http://www.w3.org/TR/2013/WD-its20-20130521/">Last Call specification</a> are consolidated in a <a href="@@@@">comment tracking document</a> (tbd:update link). All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <a href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</a> and created an <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</a> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
document to Recommendation status (see <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
- maturity levels</a>).</p><p>All <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-1st-last-call.html">last call issues</a> in the normative sections (from <a class="section-ref" href="#notation-terminology">Section 3: Notation and Terminology</a> to
- <a class="section-ref" href="#datacategory-description">Section 8: Description of Data Categories</a> and <a class="section-ref" href="#normative-references">Appendix A: References</a> to
- <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a>) have been resolved. The other, non-normative sections contain only
- explanatory material and will be updated in a later working draft. The Working Group
- encourages feedback until 11 June 2013.</p><p>Substantive changes during the first last call period are: <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/67">a new regular expression definition for allowed characters</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/68">re-formulation of disambiguation data category to "text analysis"</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/90">making directionality normative again</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/91">removal of the ruby section</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/97">aligning ITS 2.0 translate in HTML5 with the HTML5 definition of the attribute</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/118">defining default behaviour for Elements within Text in HTML5</a>.</p><p>Since the <a href="http://htmlpreview.github.io/?https://raw.github.com/innle/ITS-2.0-Testsuite/master/its2.0/testSuiteDashboard.html">ITS 2.0 test suite</a> already has a high coverage for normative features of this specification, the Working Group expects to advance the specification directly to Proposed Recommendation status.</p><p>To give feedback send your comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
+ maturity levels</a>).</p><p> The W3C Membership and other interested parties are invited to review the document and send comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
WD" in the subject line of your email. The <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/">archives
- for this list</a> are publicly available. See also <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues discussed
- within the Working Group</a> and the <a href="#changelog-since-20130411">list of
+ for this list</a> are publicly available. Advisory Committee Representatives should consult their <a href="https://www.w3.org/2002/09/wbs/myQuestionnaires">WBS questionnaires</a>. The deadline for review and comments is 30 July 2013. See also <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues discussed
+ within the Working Group</a> and the <a href="#changelog-since-20130521">list of
changes since the previous publication</a>.</p><p>Publication as a Last Call Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/53116/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p></div><div class="toc">
-<h2><a name="contents" id="contents"></a>Table of Contents</h2><div class="toc"><div class="toc1">1 <a href="#introduction">Introduction</a><div class="toc2">1.1 <a href="#relation-to-its10-and-new-principles">Relation to ITS 1.0 and New Principles</a><div class="toc3">1.1.1 <a href="#relation-to-its10">Relation to ITS 1.0</a></div>
-<div class="toc3">1.1.2 <a href="#ruby-in-its2">Ruby and ITS 2.0</a></div>
-<div class="toc3">1.1.3 <a href="#new-principles">New Principles</a></div>
-</div>
-<div class="toc2">1.2 <a href="#motivation-its">Motivation for ITS</a><div class="toc3">1.2.1 <a href="#motivation-its-issues">Typical Problems</a></div>
-</div>
-<div class="toc2">1.3 <a href="#users-usage">Users and Usages of ITS</a><div class="toc3">1.3.1 <a href="#potential-users">Potential Users of ITS</a></div>
-<div class="toc3">1.3.2 <a href="#ways-to-use-its">Ways to Use ITS</a></div>
+<h2><a name="contents" id="contents"></a>Table of Contents</h2><div class="toc"><div class="toc1">1 <a href="#introduction">Introduction</a><div class="toc2">1.1 <a href="#overview">Overview</a></div>
+<div class="toc2">1.2 <a href="#general-motiviation-for-ITS2.0">General motivation for going beyond ITS 1.0</a></div>
+<div class="toc2">1.3 <a href="#usage-scenarios">Usage Scenarios</a></div>
+<div class="toc2">1.4 <a href="#high-level-differences-between-1.0-and-2.0">High-level differences between ITS 1.0 and ITS 2.0</a></div>
+<div class="toc2">1.5 <a href="#extended-implementation-hints">Extended implementation hints</a></div>
</div>
-<div class="toc2">1.4 <a href="#usage-in-html">Usage in HTML</a><div class="toc3">1.4.1 <a href="#html5-reference-global-rules">Referencing global rules</a></div>
-<div class="toc3">1.4.2 <a href="#html5-its-local-markup">Specifities of inserting local ITS 2.0 data categories</a></div>
-<div class="toc3">1.4.3 <a href="#html5-existing-markup-versus-its">Relation between HTML markup and ITS 2.0 data categories</a></div>
-<div class="toc3">1.4.4 <a href="#html5-standoff-markup-explanation">Standoff Markup in HTML5</a></div>
-<div class="toc3">1.4.5 <a href="#usage-in-legacy-html">Version of HTML</a></div>
+<div class="toc1">2 <a href="#basic-concepts">Basic Concepts</a><div class="toc2">2.1 <a href="#basic-concepts-datacategories">Data Categories</a></div>
+<div class="toc2">2.2 <a href="#basic-concepts-selection">Selection</a><div class="toc3">2.2.1 <a href="#basic-concepts-selection-local">Local Approach</a></div>
+<div class="toc3">2.2.2 <a href="#basic-concepts-selection-global">Global Approach</a></div>
</div>
-<div class="toc2">1.5 <a href="#its-and-xliff">ITS and XLIFF</a></div>
-<div class="toc2">1.6 <a href="#out-of-scope">Out of Scope</a></div>
-<div class="toc2">1.7 <a href="#design-decisions">Important Design Principles</a></div>
-<div class="toc2">1.8 <a href="#its2-and-unicode-normalization">ITS 2.0 and Unicode Normalization</a></div>
+<div class="toc2">2.3 <a href="#basic-concepts-overinher">Overriding, Inheritance and Defaults</a></div>
+<div class="toc2">2.4 <a href="#basic-concepts-addingpointing">Adding Information or Pointing to Existing Information</a></div>
+<div class="toc2">2.5 <a href="#specific-HTML-support">Specific HTML support</a><div class="toc3">2.5.1 <a href="#html5-global-approach">Global approach in HTML5</a></div>
+<div class="toc3">2.5.2 <a href="#html5-its-local-markup">Local approach</a></div>
+<div class="toc3">2.5.3 <a href="#html5-existing-markup-versus-its">HTML markup with ITS 2.0 counterparts</a></div>
+<div class="toc3">2.5.4 <a href="#html5-standoff-markup-explanation">Standoff markup in HTML5</a></div>
+<div class="toc3">2.5.5 <a href="#usage-in-legacy-html">Version of HTML</a></div>
</div>
-<div class="toc1">2 <a href="#basic-concepts">Basic Concepts</a><div class="toc2">2.1 <a href="#basic-concepts-selection">Selection</a><div class="toc3">2.1.1 <a href="#basic-concepts-selection-local">Local Approach</a></div>
-<div class="toc3">2.1.2 <a href="#basic-concepts-selection-global">Global Approach</a></div>
+<div class="toc2">2.6 <a href="#traceability">Traceability</a></div>
+<div class="toc2">2.7 <a href="#mapping-conversion">Mapping and conversion</a><div class="toc3">2.7.1 <a href="#mapping-NIF">ITS and RDF/NIF</a></div>
+<div class="toc3">2.7.2 <a href="#mapping-XLIFF">ITS and XLIFF</a></div>
</div>
-<div class="toc2">2.2 <a href="#basic-concepts-overinher">Overriding and Inheritance</a></div>
-<div class="toc2">2.3 <a href="#basic-concepts-addingpointing">Adding Information or Pointing to Existing Information</a></div>
+<div class="toc2">2.8 <a href="#implementing-its20">ITS 2.0 Implementations and Conformance</a></div>
</div>
<div class="toc1">3 <a href="#notation-terminology">Notation and Terminology</a><div class="toc2">3.1 <a href="#notation">Notation</a></div>
<div class="toc2">3.2 <a href="#def-datacat">Data category</a></div>
@@ -82,16 +75,16 @@
<div class="toc1">4 <a href="#conformance">Conformance</a><div class="toc2">4.1 <a href="#conformance-product-schema">Conformance Type 1: ITS Markup Declarations</a></div>
<div class="toc2">4.2 <a href="#conformance-product-processing-expectations">Conformance Type 2: The Processing Expectations for ITS Markup</a></div>
<div class="toc2">4.3 <a href="#conformance-product-html-processing-expectations">Conformance Type 3: Processing Expectations for ITS Markup in HTML</a></div>
-<div class="toc2">4.4 <a href="#conformance-class-html5-its">Conformance Class for HTML5+ITS documents</a></div>
+<div class="toc2">4.4 <a href="#conformance-product-html5-its">Conformance Type 4: Markup conformance for HTML5+ITS documents</a></div>
</div>
<div class="toc1">5 <a href="#its-processing">Processing of ITS information</a><div class="toc2">5.1 <a href="#its-version-attribute">Indicating the Version of ITS</a></div>
<div class="toc2">5.2 <a href="#datacategory-locations">Locations of Data Categories</a><div class="toc3">5.2.1 <a href="#selection-global">Global, Rule-based Selection</a></div>
<div class="toc3">5.2.2 <a href="#selection-local">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2327">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2577">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2572">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2825">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules">Link to External Rules</a></div>
@@ -106,7 +99,7 @@
<div class="toc2">6.4 <a href="#html5-selection-precedence">Precedence between Selections</a></div>
</div>
<div class="toc1">7 <a href="#xhtml5-markup">Using ITS Markup in XHTML</a></div>
-<div class="toc1">8 <a href="#datacategory-description">Description of Data Categories</a><div class="toc2">8.1 <a href="#datacategories-defaults-etc">Position, Defaults, Inheritance and Overriding of Data Categories</a></div>
+<div class="toc1">8 <a href="#datacategory-description">Description of Data Categories</a><div class="toc2">8.1 <a href="#datacategories-defaults-etc">Position, Defaults, Inheritance, and Overriding of Data Categories</a></div>
<div class="toc2">8.2 <a href="#trans-datacat">Translate</a><div class="toc3">8.2.1 <a href="#translatability-definition">Definition</a></div>
<div class="toc3">8.2.2 <a href="#translatability-implementation">Implementation</a></div>
</div>
@@ -143,7 +136,7 @@
<div class="toc2">8.13 <a href="#target-pointer">Target Pointer</a><div class="toc3">8.13.1 <a href="#target-pointer-definition">Definition</a></div>
<div class="toc3">8.13.2 <a href="#target-pointer-implementation">Implementation</a></div>
</div>
-<div class="toc2">8.14 <a href="#idvalue">Id Value</a><div class="toc3">8.14.1 <a href="#idvalue-definition">Definition</a></div>
+<div class="toc2">8.14 <a href="#idvalue">ID Value</a><div class="toc3">8.14.1 <a href="#idvalue-definition">Definition</a></div>
<div class="toc3">8.14.2 <a href="#idvalue-implementation">Implementation</a></div>
</div>
<div class="toc2">8.15 <a href="#preservespace">Preserve Space</a><div class="toc3">8.15.1 <a href="#preservespace-definition">Definition</a></div>
@@ -178,53 +171,83 @@
</div><hr/><div class="body"><div class="div1">
<h2><a href="#contents"><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"></a>1 Introduction</h2><p>
<em>This section is informative.</em>
- </p><p>ITS 2.0 is a technology to add metadata to Web content, for the benefit of localization,
- language technologies, and internationalization. The ITS 2.0 specification both identifies
- concepts (such as “Translate”) that are important for internationalization and
- localization, and defines implementations of these concepts (termed “ITS data categories”)
- as a set of elements and attributes called the <em>Internationalization Tag Set
- (ITS)</em>. The document provides implementations for HTML, serializations in <a href="http://nlp2rdf.org/nif-1-0">NIF (NLP Interchange Format)</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">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng">[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/">ITS 2.0 Requirements
- document</a>, in <a title="Internationalization and
 Localization Markup Requirements" href="#itsreq">[ITS REQ]</a> and <a title="Requirements for Localizable
 DTD Design" href="#reqlocdtd">[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">[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"><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"></a>1.1 Relation to ITS 1.0 and New Principles</h3><div class="div3">
-<h4><a href="#contents"><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"></a>1.1.1 Relation to ITS 1.0</h4><p>ITS 2.0 has the following relations to ITS 1.0 <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10">[ITS 1.0]</a>:</p><ul><li><p>It adopts and maintains the following principles from ITS 1.0: </p><ul><li><p>It adopts the use of data categories to define discrete units of
- functionality</p></li><li><p>It adopts the separation of data category definition from the mapping of the
- data category to a given content format</p></li><li><p>It adopts the conformance principle of ITS1.0 that an implementation only
- needs to implement one data category to claim conformance to ITS 2.0</p></li></ul></li><li><p>ITS 2.0 supports all ITS 1.0 data category definitions and adds new definitions,
- with the exceptions of <a href="#directionality">Directionality</a> and Ruby.</p></li><li><p>ITS 2.0 adds a number of new data categories not found in ITS 1.0.</p></li><li><p>While ITS 1.0 addressed only XML, ITS 2.0 specifies implementations of data
- categories in <em>both</em> XML <em>and</em> HTML.</p></li></ul></div><div class="div3">
-<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="ruby-in-its2" id="ruby-in-its2"></a>1.1.2 Ruby and ITS 2.0</h4><p>ITS 1.0 provided the <a href="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation">Ruby data category</a>. ITS 2.0 does not provide ruby since at the time of writing, a stable model for ruby was not available. There are ongoing discussions about the <a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</a>. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p></div><div class="div3">
-<h4><a href="#contents"><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"></a>1.1.3 New Principles</h4><p>ITS 2.0 also adds the following principles and features not found in ITS 1.0:</p><ul><li><p>ITS 2.0 data categories are intended to be format neutral, with support for XML,
- HTML, and NIF: a data category implementation only needs to support a single content
- format mapping in order to support a claim of ITS 2.0 conformance.</p></li><li><p>ITS 2.0 provides algorithms to generate NIF out of HTML or XML with ITS 2.0
- metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the <a href="#xpath">XPath version 1.0</a>. Other versions of XPath or other query languages (e.g.,
- CSS Selectors) can be expressed via a dedicated <a href="#queryLanguage">queryLanguage</a> attribute.</p></li></ul><p id="its20-new-data-categories">The new data categories included in ITS 2.0
- are:</p><ul><li><p><a href="#domain">Domain</a></p></li><li><p><a href="#textanalysis">Text Analysis</a></p></li><li><p><a href="#LocaleFilter">Locale Filter</a></p></li><li><p><a href="#provenance">Provenance</a></p></li><li><p><a href="#externalresource">External Resource</a></p></li><li><p><a href="#target-pointer">Target Pointer</a></p></li><li><p><a href="#idvalue">Id Value</a></p></li><li><p><a href="#preservespace">Preserve Space</a></p></li><li><p><a href="#lqissue">Localization Quality Issue</a></p></li><li><p><a href="#lqrating">Localization Quality Rating</a></p></li><li><p><a href="#mtconfidence">MT Confidence</a></p></li><li><p><a href="#allowedchars">Allowed Characters</a></p></li><li><p><a href="#storagesize">Storage Size</a></p></li></ul></div></div><div class="div2">
-<h3><a href="#contents"><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"></a>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">[l10n i18n]</a>.</p><span class="editor-note">[Ed. note: Note: This should refer to the best practice document as well, when
- ready.]</span><p>The increasing usage of XML as a medium for documentation-related content (e.g. <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook#technical">DocBook</a>> and <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita#technical">DITA</a> as formats for writing structured documentation, well suited to computer
- hardware and software manuals) and software-related content (e.g. the eXtensible User
- Interface Language <a title="exTensible User Interface Language" href="#xul">[XUL]</a>) creates challenges and
- opportunities in the domain of XML internationalization and localization.</p><div class="div3">
-<h4><a href="#contents"><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"></a>1.2.1 Typical Problems</h4><p>The following examples sketch one of the issues that currently hinder efficient
- XML-related localization: the lack of a standard, declarative mechanism that
- identifies which parts of an XML document need to be translated. Tools often cannot
- automatically perform this identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1"></a>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><strong class="hl-tag" style="color: #000096"><resources></strong>
+ </p><div class="div2">
+<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="overview" id="overview"></a>1.1 Overview</h3><p>
+
+ Content or software that is authored in one language (so-called
+
+ source
+
+ language) for one locale (e.g. the French-speaking part of
+
+ Canada) is often made available in additional languages or adapted
+
+ with regard to other cultural aspects. A prevailing paradigm for
+
+ multilingual production in many cases encompasses
+
+ three phases: internationalization, translation, and localization (see the <a href="http://www.w3.org/International/questions/qa-i18n/"> W3C's Internationalization Q&A</a>
+
+ for more information related to these concepts).
+
+ </p><p>
+
+ From the viewpoints of feasibility, cost, and efficiency, it is
+
+ important
+
+ that the original material is suitable for
+
+ downstream
+
+ phases such as translation. This
+
+ is
+
+ achieved by
+
+ appropriate design and
+
+ development.
+
+ The corresponding
+
+ phase is
+
+ referred to as
+
+ internationalization.
+
+A proprietary XML vocabulary may be internationalized by defining special markup to specify directionality in mixed direction text.
+
+ </p><p>During the translation phase, the meaning of a source language text is analyzed,
+ and a target language text that is equivalent in meaning is determined. For example
+ national or international laws may regulate linguistic dimensions like mandatory
+ terminology or standard phrases in order to promote or ensure a translation's
+ fidelity.</p><p>Although an agreed-upon definition of the localization phase is missing, this
+ phase is usually seen as encompassing activities such as creating locale-specific
+ content (e.g. adding a link for a country-specific reseller), or modifying functionality
+ (e.g. to establish a fit with country-specific regulations for financial reporting).
+ Sometimes, the insertion of special markup to support a local language or script is also
+ subsumed under the localization phase. For example, people authoring in languages such
+ as Arabic, Hebrew, Persian or Urdu need special markup to specify directionality in
+ mixed direction text. </p><p>The technology described in this document – the <em>Internationalization Tag
+ Set (ITS) 2.0</em> addresses some of the challenges and opportunities related to
+ internationalization, translation, and localization. ITS 2.0 in particular contributes
+ to concepts in the realm of metadata for internationalization, translation, and
+ localization related to core Web technologies such as XML. ITS does for example assist
+ in production scenarios, in which parts of an XML-based document are to be excluded
+ from translation. ITS 2.0 bears many commonalities with its predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</a> but provides
+ additional concepts that are designed to foster enhanced automated processing – e.g.
+ based on language technology such as entity recognition – related to multilingual Web
+ content. </p><p> Like ITS 1.0, ITS 2.0 both identifies concepts (such as “Translate” ),
+ and defines implementations of these concepts (termed “ITS data categories”) as a set of
+ elements and attributes called the <em>Internationalization Tag Set (ITS)</em>. The
+ definitions of ITS elements and attributes are provided in the form of RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng">[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">[XLIFF 1.2]</a> and <a title="XLIFF Version 2.0" href="#xliff2.0">[XLIFF 2.0]</a>), as
+ well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document are not intended for translation.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1"></a>Example 1: Document in which some content has to be left untranslated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that are intended for translation and those that are not to be translated. Explicit metadata is needed to resolve the issue.</p><div class="exampleInner"><pre><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>
@@ -246,358 +269,137 @@
<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">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"></a>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><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>
- <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"></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"></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">examples/xml/EX-motivation-its-2.xml</a>]</p></div></div></div><div class="div2">
-<h3><a href="#contents"><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"></a>1.3 Users and Usages of ITS</h3><div class="div3">
-<h4><a href="#contents"><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"></a>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">Section 8: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="div4">
-<h5><a name="schema-dev-new" id="schema-dev-new"></a>1.3.1.1 Schema developers starting a schema from the ground up</h5><p>This type of user will find proposals for attribute and element names to be
- included in their new schema (also called "host vocabulary"). Using the attribute
- and element names proposed in the ITS specification may be helpful because it leads
- to easier recognition of the concepts represented by both schema users and
- processors. It is perfectly possible, however, for a schema developer to develop his
- own set of attribute and element names. The specification sets out, first and
- foremost, to ensure that the required markup is available, and that the behavior of
- that markup meets established needs.</p></div><div class="div4">
-<h5><a name="schema-dev-existing" id="schema-dev-existing"></a>1.3.1.2 Schema developers working with an existing schema</h5><p>This type of user will be working with schemas such as DocBook, DITA, or perhaps a
- proprietary schema. The ITS Working Group has sought input from experts developing
- widely used formats such as the ones mentioned.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The question "How to use ITS with existing popular markup schemes?" is
- covered in more details (including examples) in a separate document: <a title="Best
 Practices for XML Internationalization" href="#xml-i18n-bp">[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">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"></a>1.3.1.3 Vendors of content-related tools</h5><p>This type of user includes companies which provide tools for authoring, translation
- or other flavors of content-related software solutions. It is important to ensure
- that such tools enable worldwide use and effective localization of content. For
- example, translation tools should prevent content marked up as not for translation
- from being changed or translated. It is hoped that the ITS specification will make
- the job of vendors easier by standardizing the format and processing expectations of
- certain relevant markup items, and allowing them to more effectively identify how
- content should be handled.</p></div><div class="div4">
-<h5><a name="content-producers" id="content-producers"></a>1.3.1.4 Content producers</h5><p>This type of user comprises authors, translators and other types of content author.
- The markup proposed in this specification may be used by them to mark up specific
- bits of content. Aside: The burden of inserting markup can be removed from content
- producers by relating the ITS information to relevant bits of content in a global
- manner (see <a href="#selection-global">global, rule-based approach</a>). This
- global work, however, may fall to information architects, rather than the content
- producers themselves.</p><p id="cms-plain-text-fields">Content producers often work with content management
- systems (CMS). In various CMS, some of the CMS fields only allow to store plain
- text. For these fields, the current ITS 2.0 data categories can only be applied
- globally and not with local attributes. This issue should be addressed in another
- way, apart from the ITS 2.0 standard. One way would be to allow HTML in these fields
- if possible, or using an extra field which allows HTML input and save the plain text
- of this extra field in the plain text field.</p></div><div class="div4">
-<h5><a name="users_machine-translation" id="users_machine-translation"></a>1.3.1.5 Machine Translation Systems</h5><p>This type of service is intended for a broad user community ranging from developers
- and integrators through translation companies and agencies, freelance translators
- and post-editors to ordinary translation consumers and other types of MT employment.
- Data categories are envisaged for supporting and guiding the different automated
- backend processes of this service type, thereby adding substantial value to the
- service results as well as possible subsequent services. These processes include
- basic tasks, like parsing constraints and markup, and compositional tasks, such as
- disambiguation. These tasks consume and generate valuable metadata from and for
- third party users, for example, provenance information and quality scoring, and add
- relevant information for follow-on tasks, processes and services, such as MT
- post-editing, MT training and MT terminological enhancement.</p></div><div class="div4">
-<h5><a name="users_text_analytics" id="users_text_analytics"></a>1.3.1.6 Text Analytics</h5><p>This type of service provides automatically generated metadata for improving
- localization, data integration or knowledge management workflows. This class of
- users comprises of developers and integrators of services that automate language
- technology tasks such as domain classification, named entity recognition and
- disambiguation, term extraction, language identification and others. Text analytics
- services generate data that contextualizes the raw content with more explicit
- information. This can be used to improve the output quality in machine translation
- systems, search result relevance in information retrieval systems, as well as
- management and integration of unstructured data in knowledge management systems.</p></div><div class="div4">
-<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers"></a>1.3.1.7 Localization Workflow Managers</h5><p>These types of users are concerned with localization workflows in which content
- goes through certain steps: preparation for localization, start of the localization
- process by e.g. a conversion into a bitext (aligned parallel text) format like <a title="" href="#xliff">[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">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">Directionality</a> markup for adequate visualization of
- bidirectional text.</p></div></div><div class="div3">
-<h4><a href="#contents"><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"></a>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"></a>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><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>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>To re-compile all the modules of the Zebulon toolkit you need to go in the <strong class="hl-tag" style="color: #000096"><path</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>\Zebulon\Current Source\binary<strong class="hl-tag" style="color: #000096"></path></strong> directory. Then from there, run
- 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">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="EX-ways-to-use-its-2" id="EX-ways-to-use-its-2"></a>Example 4: Use of ITS by information architect</div><p>The <code class="its-elem-markup">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><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>
- <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>
- <strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
[3599 lines skipped]
Received on Sunday, 23 June 2013 17:24:08 UTC