- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Tue, 18 Jun 2013 21:29:15 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv8036
Modified Files:
its20.html its20.odd
Log Message:
new example 2, see http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jun/0058.html and http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jun/0064.html
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/17 11:09:44 1.462
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/18 21:29:14 1.463
@@ -59,9 +59,9 @@
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors" shape="rect">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage" shape="rect">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2603" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2606" shape="rect">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2848" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2851" 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>
@@ -211,7 +211,7 @@
mixed direction text. </p><p>The technology described in this document – the <em>Internationalization Tag
Set (ITS) 2.0</em> addresses some of the challenges and opportunities related to
internationalization, translation, and localization. ITS 2.0 in particular contributes
- to concepts in the realm of meta data for internationalization, translation, and
+ 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 should not be
translated. ITS 2.0 bears many commonalities with its predecessor, <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0</a> but provides
@@ -224,50 +224,62 @@
ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between
ITS markup and the various HTML flavors. Furthermore, ITS 2.0 suggests when and how to
leverage processing based on the XML Localization Interchange File Format (<a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>), as
- well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document must not be translated.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content must not be translated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that should be translated and those that must not be translated. Explicit meta data is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
- <strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><arguments></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></arguments></strong>
- <strong class="hl-tag" style="color: #000096"><variables></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Corporate Policy<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></variables></strong>
- <strong class="hl-tag" style="color: #000096"><keyvalue_pairs></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Page<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>ABC Corporation - Policy Repository<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Footer_Last<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>Pages<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>bgColor<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>NavajoWhite<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>title<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"><string></strong>List of Available Policies<strong class="hl-tag" style="color: #000096"></string></strong>
- <strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
- <strong class="hl-tag" style="color: #000096"></section></strong>
-<strong class="hl-tag" style="color: #000096"></resources></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml" shape="rect">examples/xml/EX-motivation-its-1.xml</a>]</p></div><p>ITS proposes several mechanisms which differ amongst others in terms of the usage scenario/user types for which the mechanism is most suitable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-2" id="EX-motivation-its-2" shape="rect"/>Example 2: Document that uses two different ITS mechanisms to indicate that some parts must not be translated.</div><p>ITS provides two mechanisms to explicitly associate meta data with one or more pieces of content (e.g. XML nodes): a <a href="#basic-concepts-selection-global" shape="rect">global</a>, rule-based approach as well as a <a href="#basic-concepts-selection-local" shape="rect">local</a>, attribute-based approached). Here, for instance, a rule first specifies that no <code>data</code> element must be translated; later, an attribute <a href="#basic-concepts-overinher" shape="rect">overwrites/a> this rule for two of the <code>data</code> elements of type "text".</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><dialogue</strong> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-gb"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//data"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">/></strong>
- <strong class="hl-tag" style="color: #000096"></its:rules></strong>
- 
- <strong class="hl-tag" style="color: #000096"><rsrc</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"123"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"456"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"image"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span><strong class="hl-tag" style="color: #000096">></strong>images/cancel.gif<strong class="hl-tag" style="color: #000096"></data></strong>
- <strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">></strong>12,20<strong class="hl-tag" style="color: #000096"></data></strong>
- <strong class="hl-tag" style="color: #000096"></component></strong>
- <strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"789"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"caption"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Cancel<strong class="hl-tag" style="color: #000096"></data></strong>
- <strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">></strong>60,40<strong class="hl-tag" style="color: #000096"></data></strong>
- <strong class="hl-tag" style="color: #000096"></component></strong>
- <strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"792"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"string"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Number of files: <strong class="hl-tag" style="color: #000096"></data></strong>
- <strong class="hl-tag" style="color: #000096"></component></strong>
- <strong class="hl-tag" style="color: #000096"></rsrc></strong>
-<strong class="hl-tag" style="color: #000096"></dialogue></strong>
+ well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document must not be translated.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content must not be translated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that should be translated and those that must not be translated. Explicit metadata is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
+ <strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><arguments></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></arguments></strong>
+ <strong class="hl-tag" style="color: #000096"><variables></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Corporate Policy<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></variables></strong>
+ <strong class="hl-tag" style="color: #000096"><keyvalue_pairs></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Page<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>ABC Corporation - Policy Repository<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Footer_Last<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Pages<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>bgColor<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>NavajoWhite<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>title<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>List of Available Policies<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
+ <strong class="hl-tag" style="color: #000096"></section></strong>
+<strong class="hl-tag" style="color: #000096"></resources></strong>
+</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml" shape="rect">examples/xml/EX-motivation-its-1.xml</a>]</p></div><p>ITS proposes several mechanisms which differ amongst others in terms of the usage scenario/user types for which the mechanism is most suitable.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-2" id="EX-motivation-its-2" shape="rect"/>Example 2: Document that uses two different ITS mechanisms to indicate that some parts must not be translated.</div><p>ITS provides two mechanisms to explicitly associate metadata with one
+ or more pieces of content (e.g. XML nodes): a <a href="#basic-concepts-selection-global" shape="rect">global</a>, rule-based
+ approach as well as a <a href="#basic-concepts-selection-local" shape="rect">local</a>, attribute-based approached. Here, for
+ instance, a <code class="its-elem-markup">translateRule</code> first specifies that only every second element inside
+ <code>keyvalue_pairs</code> must be translated; later, an ITS <code class="its-attr-markup">translate</code> attribute specifics that
+ one of these elements must not be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources</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"><its:rules</strong> <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">"//arguments"</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:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//keyvalue_pairs/string[(position() mod 2)=1]"</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"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><arguments></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>childlist<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></arguments></strong>
+ <strong class="hl-tag" style="color: #000096"><variables></strong>
+ <strong class="hl-tag" style="color: #000096"><string</strong> <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>POLICY<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Corporate Policy<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></variables></strong>
+ <strong class="hl-tag" style="color: #000096"><keyvalue_pairs></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Page<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>ABC Corporation - Policy Repository<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Footer_Last<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>Pages<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>bgColor<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string</strong> <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>NavajoWhite<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>title<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"><string></strong>List of Available Policies<strong class="hl-tag" style="color: #000096"></string></strong>
+ <strong class="hl-tag" style="color: #000096"></keyvalue_pairs></strong>
+ <strong class="hl-tag" style="color: #000096"></section></strong>
+<strong class="hl-tag" style="color: #000096"></resources></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">examples/xml/EX-motivation-its-2.xml</a>]</p></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><p>The basics of ITS 1.0 are simple:</p><ol class="depth1"><li><p>Provide meta data (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global appraoch</a>) to associate meta data with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the meta data straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of meta data categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing meta data (e.g. ters already marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to
- identify additional meta data categories for internationalization-related processes. The
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><p>The basics of ITS 1.0 are simple:</p><ol class="depth1"><li><p>Provide metadata (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global appraoch</a>) to associate metadata with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the metadata straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of metadata categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing metadata (e.g. terms aleady marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to
+ identify additional metadata categories for internationalization-related processes. The
<a href="http://www.w3.org/International/its/ig/" shape="rect">ITS Interest Group</a> for
example compiled a list of additional data categories (see this <a href="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf" shape="rect">related summary</a>). Some of these were then defined in ITS 2.0: <a href="#idvalue" shape="rect">ID Value</a>, local <a href="#elements-within-text" shape="rect">Elements
Within Text</a>, <a href="#preservespace" shape="rect">Preserve Space</a>, and <a href="#LocaleFilter" shape="rect">Locale Filter</a>. Others are still discussed as requirements
@@ -275,24 +287,24 @@
to XML was an obstacle for quite a number of environments. What was missing was, for
example, the following:</p><ol class="depth1"><li><p>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</p></li><li><p>Easy use of ITS in various Web-exposed (multilingual) Natural Language Processing contexts</p></li><li><p>Computer-supported linguistic quality assurance</p></li><li><p>Content Management and translation platforms</p></li><li><p>Cross-language scenarios</p></li><li><p>Content enrichment</p></li><li><p>Support for W3C provenance <a title="" href="#prov-dm" shape="rect">[PROV-DM]</a>, “information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data
scenarios</p></li></ol><p>ITS 2.0 was created by an alliance of stakeholders who are involved in content for global use. Thus, ITS 2.0 was developed with input from/with a view towards the following:</p><ul><li><p>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in multilingual production chains</p></li><li><p>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to facilitate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a>, <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>)
- that are interested for example in information sharing, and lossless round tripping of
- meta data in localization workflows</p></li></ul><p>One example outcome of the resulting synergies is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> mechanism. It addresses the
+ that are interested for example in information sharing, and lossless roundtrip of
+ metadata in localization workflows</p></li></ul><p>One example outcome of the resulting synergies is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> mechanism. It addresses the
provenance-related requirement by allowing ITS processors to leave a trace: ITS
processors can basically say “It is me that generated this bit of
information”. Another example are the <a title="" href="#nif-reference" shape="rect">[NIF]</a> related details of ITS 2.0 which help to couple Natural Language
Processing with concepts of the Semantic Web.</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="usage-scenarios" id="usage-scenarios" shape="rect"/>1.3 Usage Scenarios</h3><p>The <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a>
- <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “ITS is a technology to easily create XML which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multi-lingual production.</p><ul><li><p>Static mono-lingual (for example, the area of content authors): This part of the
- content has the directionality “right-to-left”.</p></li><li><p>Dynamic multi-lingual: (for example, the area of machine translation systems): This
+ <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “ITS is a technology to easily create XML which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multilingual production.</p><ul><li><p>Static mono-lingual (for example, the area of content authors): This part of the
+ content has the directionality “right-to-left”.</p></li><li><p>Dynamic multilingual: (for example, the area of machine translation systems): This
part of the content must not be translated.</p></li></ul><p>Although ITS 1.0 made no assumptions about possible phases in a multilingual production
process chain, it was slanted towards a simple three phase
“write→internationalize→translate” model. Even a birds-eye-view at ITS 2.0 shows
- that ITS 2.0 explicitly targets a much more comprehensive model for multi-lingual
- content production. The model comprises support for multi-lingual content production
+ that ITS 2.0 explicitly targets a much more comprehensive model for multilingual
+ content production. The model comprises support for multilingual content production
phases such as:</p><ul><li><p>Internationalization</p></li><li><p>Pre-production (e.g. related to marking terminology)</p></li><li><p>Automated content enrichment (e.g. automatic hyperlinking for entities)</p></li><li><p>Extraction/filtering of translation-relevant content</p></li><li><p>Segmentation</p></li><li><p>Leveraging (e.g. of existing translation-related assets such as translation memories)</p></li><li><p>Machine Translation (e.g. geared towards a specific domain)</p></li><li><p>Quality assessment or control of source language or target language content</p></li><li><p>Generation of translation kits (e.g. packages based on XLIFF)</p></li><li><p>Post-production</p></li><li><p>Publishing</p></li></ul><p>The document <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a> lists a large variety
of usage scenarios for ITS 2.0. Most of them are composed from the aforementioned
phases.</p><p>In a similar vein, ITS 2.0 takes a much more comprehensive view on the actors that may
- participate in a multi-lingual content production process. ITS 1.0 annotations (e.g.
+ participate in a multilingual content production process. ITS 1.0 annotations (e.g.
local markup for the <a href="#terminology" shape="rect">Terminology</a> data category) most of
the time were conceived as being closely tied to human actors such as content authors or
information architects. ITS 2.0 raises non-human actors such as word processors/editors,
@@ -364,39 +376,39 @@
data models in RDF.</p><p>The following two examples provide more details about the distinction between the local
and global approach, using the <a href="#trans-datacat" shape="rect">Translate</a> data
category as an example.</p><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"/>2.2.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 3</a> shows how a content author may use the ITS <code class="its-attr-markup">translate</code> attribute to indicate that all content inside the <code>author</code> element should be protected from translation (i.e. must not be translated). Translation tools that are aware of the meaning of the attribute can protect the relevant content from being translated (possibly still allowing translators to see the protected content as context information).</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 3: ITS markup on elements in an XML document (local approach) </iv><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
- <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
- <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"5.0"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><info></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>An example article<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"><author</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><personname></strong>
- <strong class="hl-tag" style="color: #000096"><firstname></strong>John<strong class="hl-tag" style="color: #000096"></firstname></strong>
- <strong class="hl-tag" style="color: #000096"><surname></strong>Doe<strong class="hl-tag" style="color: #000096"></surname></strong>
- <strong class="hl-tag" style="color: #000096"></personname></strong>
- <strong class="hl-tag" style="color: #000096"><affiliation></strong>
- <strong class="hl-tag" style="color: #000096"><address></strong><strong class="hl-tag" style="color: #000096"><email></strong>foo@example.com<strong class="hl-tag" style="color: #000096"></email></strong><strong class="hl-tag" style="color: #000096"></address></strong>
- <strong class="hl-tag" style="color: #000096"></affiliation></strong>
- <strong class="hl-tag" style="color: #000096"></author></strong>
- <strong class="hl-tag" style="color: #000096"></info></strong>
- <strong class="hl-tag" style="color: #000096"><para></strong>This is a short article.<strong class="hl-tag" style="color: #000096"></para></strong>
-<strong class="hl-tag" style="color: #000096"></article></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="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"/>2.2.1 Local Approach</h4><p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 3</a> shows how a content author may use the ITS <code class="its-attr-markup">translate</code> attribute to indicate that all content inside the <code>author</code> element should be protected from translation (i.e. must not be translated). Translation tools that are aware of the meaning of the attribute can protect the relevant content from being translated (possibly still allowing translators to see the protected content as context information).</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1" shape="rect"/>Example 3: ITS markup on elements in an XML document (local approach) </iv><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><article</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://docbook.org/ns /docbook"</span>
+ <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
+ <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"5.0"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><info></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>An example article<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"><author</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><personname></strong>
+ <strong class="hl-tag" style="color: #000096"><firstname></strong>John<strong class="hl-tag" style="color: #000096"></firstname></strong>
+ <strong class="hl-tag" style="color: #000096"><surname></strong>Doe<strong class="hl-tag" style="color: #000096"></surname></strong>
+ <strong class="hl-tag" style="color: #000096"></personname></strong>
+ <strong class="hl-tag" style="color: #000096"><affiliation></strong>
+ <strong class="hl-tag" style="color: #000096"><address></strong><strong class="hl-tag" style="color: #000096"><email></strong>foo@example.com<strong class="hl-tag" style="color: #000096"></email></strong><strong class="hl-tag" style="color: #000096"></address></strong>
+ <strong class="hl-tag" style="color: #000096"></affiliation></strong>
+ <strong class="hl-tag" style="color: #000096"></author></strong>
+ <strong class="hl-tag" style="color: #000096"></info></strong>
+ <strong class="hl-tag" style="color: #000096"><para></strong>This is a short article.<strong class="hl-tag" style="color: #000096"></para></strong>
+<strong class="hl-tag" style="color: #000096"></article></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-1.xml" shape="rect">examples/xml/EX-basic-concepts-1.xml</a>]</p></div><p>For the local approach (and <a href="#EX-basic-concepts-1" shape="rect">Example 3</a>) to work for a whole markup vocabulary, a schema developer would need to add the <code class="its-attr-markup">translate</code> attribute to the schema as a common attribute or on all the relevant element definitions. The example indicates that <a href="#basic-concepts-overinher" shape="rect">inheritance</a> plays a part in identifying which content does have to be translated and which does not: Although only the <code>author</code> element is marked as “do not translate”, its descendants (<code>personname</code>, <code>firstname</code>, <code>surname</code>) are considered to be implicitly marked as well. Tools that process this content for translation need to implement the expected inheritance.</p><p id="local-approach-not-applicable-to-attributes">For XML content, the local pproach cannot be applied to a particular attribute. If ITS needs to be applied to a particular attribute, the global approach has to be used. The local approach applies to content of the current element and all its inherited nodes as described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 8.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>. For the <a href="#trans-datacat" shape="rect">Translate</a> data category used in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, this is different, see the explanation of the <a href="#translate-in-html5" shape="rect">HTML5 definition of Translate</a>.</p></div><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"/>2.2.2 Global Approach</h4><p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 4</a> shows a different approach to identifying non-translatable content, similar to that used with a <code>style</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>, but using an ITS-defined element called <code class="its-elem-markup">rules</code>. It works as follows: A document can contain a <code class="its-elem-markup">rules</code> element (placed where it does not impact the structure of the document, e.g., in a “head” section, or even outside of the document itself). The <code class="its-elem-markup">rules</code> elemnt contains one or more ITS children/rule elements (for example <code class="its-elem-markup">translateRule</code>). Each of these children elements contains a <code class="its-attr-markup">selector</code> attribute. As its name suggests, this attribute selects the node or nodes to which the corresponding ITS information pertains. The values of ITS <code class="its-attr-markup">selector</code> attributes are XPath absolute location paths (or CSS Selectors if queryLanguage is set to "css"). Via the <code class="its-elem-markup">param</code> element variables can be provided and used in selectors.
</p><p>Information for the handling of namespaces in XPath expressions is taken from namespace declarations
- <a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> in the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 4: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><prolog></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>Using ITS<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
- <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">"//n:term"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:n</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</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"></prolog></strong>
- <strong class="hl-tag" style="color: #000096"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>ITS defines <strong class="hl-tag" style="color: #000096"><term></strong>data category<strong class="hl-tag" style="color: #000096"></term></strong> as an abstract concept for a particular type of
- information for internationalization and localization of XML schemas and documents.<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"></myTopic></strong>
-
+ <a title="Namespaces in XML
 (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> in the current rule element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2" shape="rect"/>Example 4: ITS global markup in an XML document (rule-based approach) </div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><myTopic</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"topic01"</span> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-us"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><prolog></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>Using ITS<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <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">"//n:term"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:n</span>=<span class="hl-value" style="color: #993300">"http://mynsuri.example.com"</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"></prolog></strong>
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong>ITS defines <strong class="hl-tag" style="color: #000096"><term></strong>data category<strong class="hl-tag" style="color: #000096"></term></strong> as an abstract concept for a particular type of
+ information for internationalization and localization of XML schemas and documents.<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"></myTopic></strong>
+
</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-2.xml" shape="rect">examples/xml/EX-basic-concepts-2.xml</a>]</p></div><p>For the global approach (and <a href="#EX-basic-concepts-2" shape="rect">Example 4</a>) to work, a schema developer may need to add a <code class="its-elem-markup">rules</code> element and associated markup to the schema. In some cases, global rules may be sufficient and other ITS markup (such as an <code class="its-attr-markup">translate</code> attribute on the elements and attributes) may not be needed in the schema. However, it is likely that authors may need the local approach from time to time to override the general rule.</p><p>For specification of the <a href="#trans-datacat" shape="rect">Translate</a> data category information, the contents of the <code class="its-elem-markup">translateRule</code> element would normally be designed by an information architect familiar with the document format and familiar with, or working with someone familiar with, the nees of localization/translation.</p><p>The global, rule-based approach has the following benefits:</p><ul><li><p>Content authors do not have to concern themselves with creating additional
markup or verifying that the markup was applied correctly. ITS data categories are
associated with sets of nodes (for example all <code>p</code> elements in an XML
@@ -406,25 +418,25 @@
<code>term</code> element in DITA)</p></li></ul><p>The commonality in both examples above is the markup <code>translate='no'</code>.
This piece of ITS markup can be interpreted as follows:</p><ul><li><p>it pertains to the <a href="#trans-datacat" shape="rect">Translate</a> data category </p></li><li><p>the attribute <code class="its-attr-markup">translate</code> holds a value of "no"</p></li></ul></div></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"/>2.3 Overriding, Inheritance and Defaults</h3><p>The power of the ITS selection mechanisms comes at a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a> and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a> have to be established.</p><p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 5</a> shows how inheritance
- and overriding work for the <a href="#trans-datacat" shape="rect">Translate</a> data category:</p><ul><li><p>The ITS default is that all elements are translatable.</p></li><li><p>The <code class="its-elem-markup">translateRule</code> element declared in the header overrides the default for the <code>head</code> element inside text and for all its children.</p></li><li><p>Because the <code>title</code> element is actually translatable, the global rule needs to be overridden by a local <code>its:translate="yes"</code>.</p></li><li><p>In the body of the document the default applies, and <code>its:translate="no"</code> is used to set "faux pas" as non-translatable.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 5: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F544C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><revision></strong>Sep-10-2006 v5<strong class="hl-tag" style="color: #000096"></revision></strong>
- <strong class="hl-tag" style="color: #000096"><author></strong>Ealasaidh McIan<strong class="hl-tag" style="color: #000096"></author></strong>
- <strong class="hl-tag" style="color: #000096"><contact></strong>ealasaidh@hogw.ac.uk<strong class="hl-tag" style="color: #000096"></contact></strong>
- <strong class="hl-tag" style="color: #000096"><title</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>The Origins of Modern Novel<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">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">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"/text/head"</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>
- <strong class="hl-tag" style="color: #000096"><div</strong> <span class="hl-attribute" style="color: #F5844C">xml:id</span>=<span class="hl-value" style="color: #993300">"intro"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>Introduction<strong class="hl-tag" style="color: #000096"></head></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>It would certainly be quite a <strong class="hl-tag" style="color: #000096"><span</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>faux pas<strong class="hl-tag" style="color: #000096"></span></strong> to start a
- dissertation on the origin of modern novel without mentioning the <strong class="hl-tag" style="color: #000096"><tl></strong>Epic of
- Gilgamesh<strong class="hl-tag" style="color: #000096"></tl></strong>...<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></div></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></text></strong>
+ and overriding work for the <a href="#trans-datacat" shape="rect">Translate</a> data category:</p><ul><li><p>The ITS default is that all elements are translatable.</p></li><li><p>The <code class="its-elem-markup">translateRule</code> element declared in the header overrides the default for the <code>head</code> element inside text and for all its children.</p></li><li><p>Because the <code>title</code> element is actually translatable, the global rule needs to be overridden by a local <code>its:translate="yes"</code>.</p></li><li><p>In the body of the document the default applies, and <code>its:translate="no"</code> is used to set "faux pas" as non-translatable.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3" shape="rect"/>Example 5: Overriding and Inheritance</div><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F544C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><revision></strong>Sep-10-2006 v5<strong class="hl-tag" style="color: #000096"></revision></strong>
+ <strong class="hl-tag" style="color: #000096"><author></strong>Ealasaidh McIan<strong class="hl-tag" style="color: #000096"></author></strong>
+ <strong class="hl-tag" style="color: #000096"><contact></strong>ealasaidh@hogw.ac.uk<strong class="hl-tag" style="color: #000096"></contact></strong>
+ <strong class="hl-tag" style="color: #000096"><title</strong> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>The Origins of Modern Novel<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">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">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"/text/head"</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>
+ <strong class="hl-tag" style="color: #000096"><div</strong> <span class="hl-attribute" style="color: #F5844C">xml:id</span>=<span class="hl-value" style="color: #993300">"intro"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>Introduction<strong class="hl-tag" style="color: #000096"></head></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong>It would certainly be quite a <strong class="hl-tag" style="color: #000096"><span</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>faux pas<strong class="hl-tag" style="color: #000096"></span></strong> to start a
+ dissertation on the origin of modern novel without mentioning the <strong class="hl-tag" style="color: #000096"><tl></strong>Epic of
+ Gilgamesh<strong class="hl-tag" style="color: #000096"></tl></strong>...<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></div></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
+<strong class="hl-tag" style="color: #000096"></text></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-basic-concepts-3.xml" shape="rect">examples/xml/EX-basic-concepts-3.xml</a>]</p></div><p>For XML content, <a href="#datacategories-overview" shape="rect">data category specific defaults</a> are provided. These are independent of the actual XML markup vocabulary. Example for the <a href="#trans-datacat" shape="rect">Translate</a> data category: <code>translate="yes"</code> for elements, and <code>translate="no"</code> for attributes.</p><p>For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, several HTML5 elements and attributes map exactly to ITS 2.0 data categories. Hence, that HTML markup is normatively interpreted as ITS 2.0 data category information (see <a class="section-ref" href="#html5-existing-markup-versus-its" shape="rect">Section 2.5.3: HTML markup with ITS 2.0 counterparts</a> for more information).</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-addingpointing" id="basic-concepts-addingpointing" shape="rect"/>2.4 Adding Information or Pointing to Existing Information</h3><p>Data categories can add information or point to information for the selected nodes. For example, the <a href="#locNote-datacat" shape="rect">Localization Note</a>
data category can add information to selected nodes (using a <code class="its-elem-markup">locNote</code> element),
@@ -442,47 +454,47 @@
The advantage is in being able to reuse the same rules file for many documents and also inline rules require secondary parsing
of the <code>script</code> element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 6: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
<code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
- the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
-<strong class="hl-tag" style="color: #000096"><html></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"><link</strong> <span class="hl-attribute" style="color: #F5844C">href</span>=<span class="hl-value" style="color: #993300">EX-translateRule-html5-1.xml</span> <span class="hl-attribute" style="color: #F5844C">rel</span>=<span class="hl-value" style="color: #993300">its-rules</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"><body></strong>
- <strong class="hl-tag" style="color: #000096"><p></strong>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
- Of course there are always exceptions: certain code values should be translated,
- e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-global-1.html" shape="rect">examples/html5/EX-translate-html5-global-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1-rules-file" id="EX-translate-html5-global-1-rules-file" shape="rect"/>Example 7: ITS rules file linked from HTML</div><p>The rules file linked in <a href="#EX-translate-html5-global-1" shape="rect">Example 6</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
- <span class="hl-attribute" style="color: #F5844C">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
-<strong class="hl-tag" style="color: #000096"></its:rules></strong>
+ the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"><link</strong> <span class="hl-attribute" style="color: #F5844C">href</span>=<span class="hl-value" style="color: #993300">EX-translateRule-html5-1.xml</span> <span class="hl-attribute" style="color: #F5844C">rel</span>=<span class="hl-value" style="color: #993300">its-rules</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"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
+ Of course there are always exceptions: certain code values should be translated,
+ e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
+<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-global-1.html" shape="rect">examples/html5/EX-translate-html5-global-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1-rules-file" id="EX-translate-html5-global-1-rules-file" shape="rect"/>Example 7: ITS rules file linked from HTML</div><p>The rules file linked in <a href="#EX-translate-html5-global-1" shape="rect">Example 6</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
+ <span class="hl-attribute" style="color: #F5844C">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
+<strong class="hl-tag" style="color: #000096"></its:rules></strong>
</pre></div><p>[Source file: <a href="examples/html5/EX-translateRule-html5-1.xml" shape="rect">examples/html5/EX-translateRule-html5-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-inline-global-1" id="EX-translate-html5-inline-global-1" shape="rect"/>Example 8: Using ITS inline global rules in HTML</div><p>The <code>script</code> element contains the same rules as the external rules file
- <code>EX-translateRule-html5-1.xml</code> in <a href="#EX-translate-html5-global-1-rules-file" shape="rect">the above example</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
-<strong class="hl-tag" style="color: #000096"><html></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
- <strong class="hl-tag" style="color: #000096"><script</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">application/its+xml</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">ru1</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
- <span class="hl-attribute" style="color: #F5844C">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
- <strong class="hl-tag" style="color: #000096"></its:rules></strong>
- <strong class="hl-tag" style="color: #000096"></script></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>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
- Of course there are always exceptions: certain code values should be translated,
- e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
+ <code>EX-translateRule-html5-1.xml</code> in <a href="#EX-translate-html5-global-1-rules-file" shape="rect">the above example</a>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>Translate flag global rules example<strong class="hl-tag" style="color: #000096"></title></strong>
+ <strong class="hl-tag" style="color: #000096"><script</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">application/its+xml</span> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">ru1</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
+ <span class="hl-attribute" style="color: #F5844C">xmlns:h</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xhtml"</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//h:code"</span><strong class="hl-tag" style="color: #000096">/></strong>
+ <strong class="hl-tag" style="color: #000096"></its:rules></strong>
+ <strong class="hl-tag" style="color: #000096"></script></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>This sentence should be translated, but code names like the <strong class="hl-tag" style="color: #000096"><code></strong>span<strong class="hl-tag" style="color: #000096"></code></strong> element should not be translated.
+ Of course there are always exceptions: certain code values should be translated,
+ e.g. to a value in your language like <strong class="hl-tag" style="color: #000096"><code</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">yes</span><strong class="hl-tag" style="color: #000096">></strong>warning<strong class="hl-tag" style="color: #000096"></code></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-inline-global-1.html" shape="rect">examples/html5/EX-translate-html5-inline-global-1.html</a>]</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="html5-its-local-markup" id="html5-its-local-markup" shape="rect"/>2.5.2 Local approach</h4><p>In HTML, an ITS 2.0 local data category is realized with the prefix <code>its-</code>.
The general mapping of the XML based ITS 2.0 attributes to their HTML counterparts is defined in
<a class="section-ref" href="#html5-local-attributes" shape="rect">Section 6.1: Mapping of Local Data Categories to HTML</a>. An informative table in <a class="section-ref" href="#list-of-elements-and-attributes" shape="rect">Appendix G: List of ITS 2.0 Global Elements and Local Attributes</a>
provides an overview of the mapping for all data categories.</p></div><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-existing-markup-versus-its" id="html5-existing-markup-versus-its" shape="rect"/>2.5.3 HTML markup with ITS 2.0 counterparts</h4><p>There are four ITS 2.0 data categories, which have counterparts in HTML markup. In these cases, native HTML markup provides some information
- in termms of ITS 2.0 data categories. For these data categories, ITS 2.0 defines the following:</p><ul><li><p>The <a href="#language-information" shape="rect">Language Information</a> data category has the HTML <code>lang</code>
+ in terms of ITS 2.0 data categories. For these data categories, ITS 2.0 defines the following:</p><ul><li><p>The <a href="#language-information" shape="rect">Language Information</a> data category has the HTML <code>lang</code>
attribute as a counterpart. In XHTML the counterpart is the <code>xml:lang</code> attribute. These HTML attributes act as
local markup for the <a href="#language-information" shape="rect">Language Information</a> data category in HTML and
take <a href="#selection-precedence" shape="rect">precedence</a> over language information conveyed via a global <code class="its-elem-markup">langRule</code>.</p></li><li><p>The <a href="#idvalue" shape="rect">Id Value</a> data category has the HTML or XHTML <code>id</code> attribute as counterpart.
@@ -502,16 +514,16 @@
<a href="#language-information" shape="rect">Language Information</a> value "en".
The <code>id</code> attribute of the <code>p</code> element conveys the <a href="#idvalue" shape="rect">Id Value</a>
"p1". The elements <code>em</code> and <code>img</code> are interpreted to be <code>withinText="yes"</code>. The <code>p</code> element and its children are set to be non-translatable via an <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>
- <code>translate</code> attribute. Via inheritance, the <code>alt</code> attribute, normally translatable by default, also is non-translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
-<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">en</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><head></strong>
- <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><title></strong>HTML native markup expressing three ITS 2.0 data categories<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> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"p1"</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>This is a <strong class="hl-tag" style="color: #000096"><em></strong>motherboard<strong class="hl-tag" style="color: #000096"></em></strong> and image: 
- <strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"http://example.com/myimg.png"</span> <span class="hl-attribute" style="color: #F5844C">alt</span>=<span class="hl-value" style="color: #993300">"My image"</span><strong class="hl-tag" style="color: #000096">/></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
- <strong class="hl-tag" style="color: #000096"></body></strong>
+ <code>translate</code> attribute. Via inheritance, the <code>alt</code> attribute, normally translatable by default, also is non-translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
+<strong class="hl-tag" style="color: #000096"><html</strong> <span class="hl-attribute" style="color: #F5844C">lang</span>=<span class="hl-value" style="color: #993300">en</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><head></strong>
+ <strong class="hl-tag" style="color: #000096"><meta</strong> <span class="hl-attribute" style="color: #F5844C">charset</span>=<span class="hl-value" style="color: #993300">utf-8</span><strong class="hl-tag" style="color: #000096">></strong>
+ <strong class="hl-tag" style="color: #000096"><title></strong>HTML native markup expressing three ITS 2.0 data categories<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> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"p1"</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>This is a <strong class="hl-tag" style="color: #000096"><em></strong>motherboard<strong class="hl-tag" style="color: #000096"></em></strong> and image:
+ <strong class="hl-tag" style="color: #000096"><img</strong> <span class="hl-attribute" style="color: #F5844C">src</span>=<span class="hl-value" style="color: #993300">"http://example.com/myimg.png"</span> <span class="hl-attribute" style="color: #F5844C">alt</span>=<span class="hl-value" style="color: #993300">"My image"</span><strong class="hl-tag" style="color: #000096">/></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
+ <strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></html></strong></pre></div><p>[Source file: <a href="examples/html5/EX-its-and-existing-HTML5-markup.html" shape="rect">examples/html5/EX-its-and-existing-HTML5-markup.html</a>]</p></div><p>There are also some HTML markup elements that have or can have similar, but not necessarily identical, roles and behaviors as certain ITS 2.0 data categories. For example, the HTML <code>dfn</code> element could be used to identify a term in the sense of the <a href="#terminology" shape="rect">Terminology</a> data category. However, this is not always the case and it depends on the intentions of the HTML content author. To accommodate this situation, users of ITS 2.0 are encouraged to specify the semantics of existing HTML markup in an ITS 2.0 context with a dedicated global rules file. For example, a rule can be used to define that the HTML <code>dfn</code> has the semantics of ITS <code>term="yes"</code>. For additional examples see the <a href="http://www.w3.org/TR2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml" shape="rect">XML I18N Best Practices</a> document.</p></div><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="html5-standoff-markup-explanation" id="html5-standoff-markup-explanation" shape="rect"/>2.5.4 Standoff markup in HTML5</h4><p>The <a href="#provenance" shape="rect">Provenance</a> and the <a href="#lqissue" shape="rect">Localization Quality Issue</a> data categories allow for using so-called standoff markup, see the XML <a href="#EX-provenance-global-1" shape="rect">Example 59</a>. In HTML such standoff markup is placed into a <code>script</code> element. If this is done, the constraints for <a href="#provenance-records-in-html5-constraint" shape="rect">Provenance standoff</a> markup in HTML and <a href="#loc-quality-issues-in-html5-constraint" shape="rect">Localization quality issue</a> markup in HTML need to be taken into account. Examples of standoff markup in HTML for the two data categories are <a href="#EX-proveance-html5-local-2" shape="rect">Example 62</a> and <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 77</a>.</p></div><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="usage-in-legacy-html" id="usage-in-legacy-html" shape="rect"/>2.5.5 Version of HTML</h4><p>ITS 2.0 does not define how to use ITS in HTML versions prior to version 5. Users are
@@ -519,12 +531,12 @@
<code>its-*</code> attributes introduced for <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> in older versions of HTML (such
as 3.2 or 4.01) and pages using these attributes will work without any problems,
<code>its-*</code> attributes will be marked as invalid by validators.</p></div></div><div class="div2">
-<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="traceability" id="traceability" shape="rect"/>2.6 Traceability</h3><p>The <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism allows associating processor information with individual data categories in a document, independently from data category annotations themselves (e.g. the Entity Type related to Text Analysis). The mechanism associates identifiers for tools with data categories via the <code class="its-attr-markup">annotatorsRef</code> attribute (or <a href="" shape="rect">annotators-ref</a> in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>) and is mandatory for the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category. For the <a href="#terminology" shape="rect">Terminology</a> and <a href="#textanalysis" shape="rect">Text Analysis</a> data categories the ITS Tols Annotation is mandatory if the data categories provide confidence information. Nevertheless, <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> can be used for all data categories. <a href="#EX-its-tool-annotation-2" shape="rect">Example 24</a> demonstrates the usage in the context of several data categories.
+<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="traceability" id="traceability" shape="rect"/>2.6 Traceability</h3><p>The <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism allows processor information to be associated with individual data categories in a document, independently from data category annotations themselves (e.g. the Entity Type related to Text Analysis). The mechanism associates identifiers for tools with data categories via the <code class="its-attr-markup">annotatorsRef</code> attribute (or <a href="" shape="rect">annotators-ref</a> in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>) and is mandatory for the <a href="#mtconfidence" shape="rect">MT Confidence</a> data category. For the <a href="#terminology" shape="rect">Terminology</a> and <a href="#textanalysis" shape="rect">Text Analysis</a> data categories the TS Tools Annotation is mandatory if the data categories provide confidence information. Nevertheless, <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> can be used for all data categories. <a href="#EX-its-tool-annotation-2" shape="rect">Example 24</a> demonstrates the usage in the context of several data categories.
</p></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-conversion" id="mapping-conversion" shape="rect"/>2.7 Mapping and conversion</h3><div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-NIF" id="mapping-NIF" shape="rect"/>2.7.1 ITS and RDF/NIF</h4><p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
- representations) that contain ITS metadata to the RDF-based format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims at interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content related triples and relies on an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The back conversion from <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively. One motivation for the back conversion is a round tripping work flow like: 1) conversion to NIF 2) in NIF representation detection of named entities using NLP tools 3) back conversion to HTML and generation of <a href="#textanalysis" shape"rect">Text Analysis</a> markup. The outcome are HTML documents with linked information, see <a href="#EX-text-analysis-html5-local-1" shape="rect">Example 53</a>.</p></div><div class="div3">
-<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>2.7.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localization and translation workflows. <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> is the successor of <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and under development. XLIFF has been widely implemented in various translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents.</p><p>The mapping between ITS and XLIFF therefore unpins several important ITS 2.0 usagescenarios <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a>. These usage scenarios involve:</p><ul><li><p>the extraction of ITS meta-data from a source language file into XLIFF</p></li><li><p>the addition of ITS meta-data into an XLIFF file by translation tools</p></li><li><p>the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files.</p></li></ul><p>ITS 2.0 has no normative dependency on XLIFF, however a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping" shape="rect">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/" shape="rect">Internationalization Tag Set Interest Group</a>.</p></div></div><div class="div2">
+ representations) that contain ITS metadata to the RDF format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims at interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion from <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content-related triples and relies on an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The back conversion from <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively. One motivation for the back conversion is a roundtrip workflow like: 1) conversion to NIF 2) in NIF representation detection of named entities using NLP tools 3) back conversion to HTML and generation of <a href="#textanalysis" shape="rect"Text Analysis</a> markup. The outcome are HTML documents with linked information, see <a href="#EX-text-analysis-html5-local-1" shape="rect">Example 53</a>.</p></div><div class="div3">
+<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>2.7.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localization and translation workflows. <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> is the successor of <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and under development. XLIFF has been widely implemented in various translation management systems, computer aided translation tools and in utilities for extracting translatable content from source documents and merging back the content in the target language..</p><p>The mapping between ITS and XLIFFtherefore unpins several important ITS 2.0 usage scenarios <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a>. These usage scenarios involve:</p><ul><li><p>the extraction of ITS metadata from a source language file into XLIFF</p></li><li><p>the addition of ITS metadata into an XLIFF file by translation tools</p></li><li><p>the mapping of ITS metadata in an XLIFF file into ITS metadata in the resulting target language files.</p></li></ul><p>ITS 2.0 has no normative dependency on XLIFF, however a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping" shape="rect">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/" shape="rect">Internationalization Tag Set Interest Group</a>.</p></div></div><div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="implementing-its20" id="implementing-its20" shape="rect"/>2.8 ITS 2.0 Implementations and Conformance</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer (see <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a>). The clauses are targeted at different types of implementers.</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema" shape="rect">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectationsfor ITS Markup</a> tell implementers how to process XML content according to ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html5-its" shape="rect">Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations" shap="rect">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> clarify how information needs to be made available for given pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <a href="@@@@" shape="rect">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually should be used. This is due to the fact that there is a wide variety of usage scenarios for ITS 2.0, and a wide variety of tools for working with ITS 2.0 is possible. Each of these tools may have its own way of using ITS 2.0 data categories (see <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW U IMPL]</a> for more information).</p><span class="editor-note">[Ed. note: Add link to test suite]</span></div></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="notation-terminology" id="notation-terminology" shape="rect"/>3 Notation and Terminology</h2><p>
[6611 lines skipped]
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 11:48:50 1.469
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/18 21:29:15 1.470
@@ -241,7 +241,12 @@
<exemplum xml:id="EX-motivation-its-2">
<head>Document that uses two different ITS mechanisms to indicate that some parts must not be translated.</head>
- <p>ITS provides two mechanisms to explicitly associate metadata with one or more pieces of content (e.g. XML nodes): a <ref target="#basic-concepts-selection-global">global</ref>, rule-based approach as well as a <ref target="#basic-concepts-selection-local">local</ref>, attribute-based approached). Here, for instance, a rule first specifies that no <code>data</code> element must be translated; later, an attribute <ref target="#basic-concepts-overinher">overwrites</ref> this rule for two of the <code>data</code> elements of type <val>text</val>.</p>
+ <p>ITS provides two mechanisms to explicitly associate metadata with one
+ or more pieces of content (e.g. XML nodes): a <ref target="#basic-concepts-selection-global">global</ref>, rule-based
+ approach as well as a <ref target="#basic-concepts-selection-local">local</ref>, attribute-based approached. Here, for
+ instance, a <gi>translateRule</gi> first specifies that only every second element inside
+ <code>keyvalue_pairs</code> must be translated; later, an ITS <att>translate</att> attribute specifics that
+ one of these elements must not be translated.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-motivation-its-2.xml"/>
</exemplum>
Received on Tuesday, 18 June 2013 21:29:20 UTC