- From: Felix Sasaki via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 14 Oct 2012 19:09:53 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory hutz:/tmp/cvs-serv28107/TR-version
Modified Files:
Overview.html
Log Message:
Fix: ed note was on wrong place
Index: Overview.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -d -r1.55 -r1.56
--- Overview.html 13 Oct 2012 08:29:56 -0000 1.55
+++ Overview.html 14 Oct 2012 19:09:51 -0000 1.56
@@ -93,9 +93,9 @@
<div class="toc3">5.2.3 <a href="#selection-local">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d3e2010">XPath 1.0</a></div>
-<div class="toc3">5.3.3 <a href="#d3e2190">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d3e2226">Additional query languages</a></div>
+<div class="toc3">5.3.2 <a href="#d3e2013">XPath 1.0</a></div>
+<div class="toc3">5.3.3 <a href="#d3e2193">CSS Selectors</a></div>
+<div class="toc3">5.3.4 <a href="#d3e2229">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules">Link to External Rules</a></div>
@@ -134,7 +134,9 @@
<div class="toc2">6.11 <a href="#LocaleFilter">Locale Filter</a><div class="toc3">6.11.1 <a href="#LocaleFilter-definition">Definition</a></div>
<div class="toc3">6.11.2 <a href="#LocaleFilter-implementation">Implementation</a></div>
</div>
-<div class="toc2">6.12 <a href="#Provenance">Provenance</a></div>
+<div class="toc2">6.12 <a href="#translation-agent-provenance">Translation Agent Provenance</a><div class="toc3">6.12.1 <a href="#translation-agent-provenance-definition">Definition</a></div>
+<div class="toc3">6.12.2 <a href="#translation-agent-provenance-implementation">Implementation</a></div>
+</div>
<div class="toc2">6.13 <a href="#TextAnalyisAnnotation">TextAnalyisAnnotation</a></div>
<div class="toc2">6.14 <a href="#externalresource">External Resource</a><div class="toc3">6.14.1 <a href="#externalresource-definition">Definition</a></div>
<div class="toc3">6.14.2 <a href="#externalresource-implementation">Implementation</a></div>
@@ -165,7 +167,7 @@
</div>
</div>
<div class="toc1">7 <a href="#html5-markup">Using ITS Markup in HTML5</a><div class="toc2">7.1 <a href="#html5-local-attributes">Mapping of Local Data Categories to HTML5</a></div>
-<div class="toc2">7.2 <a href="#d3e7734">Inline Global Rules in HTML5</a></div>
+<div class="toc2">7.2 <a href="#d3e7960">Inline Global Rules in HTML5</a></div>
</div>
<div class="toc1">8 <a href="#xhtml5-markup">Using ITS Markup in XHTML</a></div>
</div>
@@ -215,7 +217,7 @@
or XML with ITS 2.0 metadata.</p></li><li><p>A global implementation of ITS 2.0 requires at least the XPath
version 1.0. Other versions of XPath or other query languages (e.g.,
CSS selectors) can be expressed via a dedicated <a href="#queryLanguage">queryLanguage</a> attribute.</p></li></ul><p>As of the time of this writing, the new data categories included in ITS
- 2.0 are:</p><ul><li><p><a href="#domain">Domain</a></p></li><li><p><a href="#Disambiguation">Disambiguation</a></p></li><li><p><a href="#LocaleFilter">Locale Filter</a></p></li><li><p><a href="#Provenance">Provenance</a></p></li><li><p><a href="#TextAnalyisAnnotation">Text Analysis
+ 2.0 are:</p><span class="editor-note">[Ed. note: Below needs to be updated before next publication.]</span><ul><li><p><a href="#domain">Domain</a></p></li><li><p><a href="#Disambiguation">Disambiguation</a></p></li><li><p><a href="#LocaleFilter">Locale Filter</a></p></li><li><p><a href="#translation-agent-provenance">Provenance</a></p></li><li><p><a href="#TextAnalyisAnnotation">Text Analysis
Annotation</a></p></li></ul></div></div><div class="div2">
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="motivation-its" id="motivation-its"></a>1.2 Motivation for ITS</h3><p>Content or software that is authored in one language (the <span class="new-term">source
language</span>) is often made available in additional languages or
@@ -239,7 +241,7 @@
efficient XML-related localization: the lack of a standard, declarative
mechanism that identifies which parts of an XML document need to be
translated. Tools often cannot automatically perform this
- identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e320" id="d3e320"></a>Example 1: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those
+ identification.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e323" id="d3e323"></a>Example 1: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those
<code>string</code> elements that are translatable and those that
are not. Only the addition of an explicit flag could resolve the
issue.</p><div class="exampleInner"><pre>
@@ -264,7 +266,7 @@
<string>List of Available Policies</string>
</keyvalue_pairs>
</section>
-</resources></pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml">examples/xml/EX-motivation-its-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e335" id="d3e335"></a>Example 2: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text,
+</resources></pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml">examples/xml/EX-motivation-its-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e338" id="d3e338"></a>Example 2: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text,
the conditions may be quite complex and not directly indicated with
a simple flag. Here, for instance, only the text in the nodes
matching the expression
@@ -328,7 +330,7 @@
standardizing the format and processing expectations of certain
relevant markup items, and allowing them to more effectively
identify how content should be handled.</p></div><div class="div4">
-<h5><a name="d3e393" id="d3e393"></a>1.3.1.4Content producers</h5><p>This type of user comprises authors, translators and other types of
+<h5><a name="d3e396" id="d3e396"></a>1.3.1.4Content producers</h5><p>This type of user comprises authors, translators and other types of
content author. The markup proposed in this specification may be
used by them to mark up specific bits of content. Aside: The burden
of inserting markup can be removed from content producers by
@@ -363,7 +365,7 @@
</body>
</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-1.xml">examples/xml/EX-ways-to-use-its-1.xml</a>]</p></div><ul><li><p>A content author or information architect uses markup at the top
of the document to identify a particular type of element or
- context in which the content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e445" id="d3e445"></a>Example 4: Use of ITS by information architect</div><p>The <code>translateRule</code> element is used in the header of the
+ context in which the content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e448" id="d3e448"></a>Example 4: Use of ITS by information architect</div><p>The <code>translateRule</code> element is used in the header of the
document to indicate that none of the <code>path</code> or <code>cmd</code>
elements should be translated.</p><div class="exampleInner"><pre>
<help
@@ -381,7 +383,7 @@
Then from there, run batch file <cmd>Build.bat</cmd>.</p>
</body>
</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-2.xml">examples/xml/EX-ways-to-use-its-2.xml</a>]</p></div><ul><li><p>A processor may insert markup at the top of the document which
- links to ITS information outside of the document.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e470" id="d3e470"></a>Example 5: Use of ITS by processor</div><p>A <code>rules</code> element is inserted in the header of the document.
+ links to ITS information outside of the document.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e473" id="d3e473"></a>Example 5: Use of ITS by processor</div><p>A <code>rules</code> element is inserted in the header of the document.
It has a XLink <code>href</code> attribute used to link to an <a href="#link-external-rules">ITS external rule</a>
document.</p><div class="exampleInner"><pre>
<help
@@ -397,7 +399,7 @@
<path>\Zebulon\Current Source\binary</path> directory.
Then from there, run batch file <cmd>Build.bat</cmd>.</p>
</body>
-</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e491" id="d3e491"></a>Example 6: ITS rule file shared by different documents</div><p>The <code>rules</code> element contains several ITS rules that are common
+</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e494" id="d3e494"></a>Example 6: ITS rule file shared by different documents</div><p>The <code>rules</code> element contains several ITS rules that are common
to different documents. One of them is a <code>translateRule</code>
element that indicates that no <code>path</code> or <code>cmd</code> element
should be translated.</p><div class="exampleInner"><pre>
@@ -406,7 +408,7 @@
<its:translateRule selector="//path | //cmd" translate="no"/>
</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-4.xml">examples/xml/EX-ways-to-use-its-4.xml</a>]</p></div><ul><li><p>A schema developer integrates ITS markup declarations in his
schema to allow users to indicate that specific parts of the
- content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e519" id="d3e519"></a>Example 7: An XSD schema with ITS declaration</div><p>The declarations for the <code>translate</code> attribute
+ content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e522" id="d3e522"></a>Example 7: An XSD schema with ITS declaration</div><p>The declarations for the <code>translate</code> attribute
is added to a group of common attributes <code>commonAtts</code>.
This allows to use the <code>translate</code> attribute
within the documents like in <a href="#EX-ways-to-use-its-1">Example 3</a>.</p><div class="exampleInner"><pre>
@@ -741,7 +743,7 @@
documents.] The concept of a data category is independent of
its implementation in an XML environment (e.g. using an element or
attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description">Section 6: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "markup
- declarations" subsections in <a class="section-ref" href="#datacategory-description">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1177" id="d3e1177"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys
+ declarations" subsections in <a class="section-ref" href="#datacategory-description">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1180" id="d3e1180"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys
information as to whether a piece of content should be translated or
not.</p><p>The simplest formalization of this prose description on a schema language
independent level is a <code>translate</code> attribute with
@@ -770,7 +772,7 @@
points. Thus in the following example, the translation information
specified via the <code>translateRule</code> element applies to the filename
"instructions.jpg", and is not an instruction to open the
- graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1260" id="d3e1260"></a>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre>
+ graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1263" id="d3e1263"></a>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1020,9 +1022,9 @@
by <code>queryLanguage</code> attribute on <code>rules</code> element. If
<code>queryLanguge</code> is not specified XPath 1.0 is used as a
default query language.</p></div><div class="div3">
-<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2010" id="d3e2010"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2013" id="d3e2013"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in
<code>queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d3e2021" id="d3e2021"></a>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an
+<h5><a name="d3e2024" id="d3e2024"></a>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an
XPath expression which starts with "<code>/</code>". That is, it
must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath">
@@ -1037,7 +1039,7 @@
occurs. This includes the implicit declaration of the prefix
<code>xml</code> required by the the <a href="#xmlns">XML Namespaces Recommendation</a>; the
default namespace (as declared by <code>xmlns</code>) is not
- part of this set.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2081" id="d3e2081"></a>Example 16: XPath expressions with namespaces</div><p>The <code>term</code> element from the TEI is in a namespace
+ part of this set.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2084" id="d3e2084"></a>Example 16: XPath expressions with namespaces</div><p>The <code>term</code> element from the TEI is in a namespace
<code>http://www.tei-c.org/ns/1.0</code>. </p><div class="exampleInner"><pre>
<!-- Definitions for TEI -->
@@ -1045,7 +1047,7 @@
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:tei="http://www.tei-c.org/ns/1.0" version="2.0">
<its:termRule selector="//tei:term" term="yes"/>
-</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2099" id="d3e2099"></a>Example 17: XPath expressions without namespaces</div><p>The <code>term</code> element from DocBook V4.5 is in no
+</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2102" id="d3e2102"></a>Example 17: XPath expressions without namespaces</div><p>The <code>term</code> element from DocBook V4.5 is in no
namespace.</p><div class="exampleInner"><pre>
<!-- Definitions for DocBook -->
@@ -1053,7 +1055,7 @@
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
<its:termRule selector="//term" term="yes"/>
</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-2.xml">examples/xml/EX-selection-global-2.xml</a>]</p></div></div><div class="div4">
-<h5><a name="d3e2114" id="d3e2114"></a>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords">MUST</a> use a
+<h5><a name="d3e2117" id="d3e2117"></a>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords">MUST</a> use a
<a href="http://www.w3.org/TR/xpath/#NT-RelativeLocationPath">RelativeLocationPath</a> as described in <a href="#xpath">XPath 1.0</a>. The XPath expression is evaluated relative to
the nodes selected by the selector attribute. The following
attributes point to existing information: <code>locNotePointer</code>,
@@ -1070,16 +1072,16 @@
attribute form the current node list.</p></li><li><p>Context node comes from the current node list.</p></li><li><p>The context position comes from the position of the current
node in the current node list; the first position is 1.</p></li><li><p>The context size comes from the size of the current node
list.</p></li></ul></div></div><div class="div3">
-<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2190" id="d3e2190"></a>5.3.3 CSS Selectors</h4><p>CSS Selectors are identified by <code>css</code> value in
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2193" id="d3e2193"></a>5.3.3 CSS Selectors</h4><p>CSS Selectors are identified by <code>css</code> value in
<code>queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d3e2201" id="d3e2201"></a>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be
+<h5><a name="d3e2204" id="d3e2204"></a>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be
interpreted as selector as defined in <a href="#css3-selectors">Selectors Level 3</a>. Both simple selectors and groups of
selectors can be used.</p></div><div class="div4">
-<h5><a name="d3e2212" id="d3e2212"></a>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be
+<h5><a name="d3e2215" id="d3e2215"></a>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be
interpreted as selector as defined in <a href="#css3-selectors">Selectors Level 3</a>. Selector is not evaluated against the
complete document tree but only against subtrees rooted at nodes
selected by selector in the <code>selector</code> attribute.</p></div></div><div class="div3">
-<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2226" id="d3e2226"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2229" id="d3e2229"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional
query languages. For each additional query language processor <a href="#rfc-keywords">MUST</a> define:</p><ul><li><p>identifier of query language used in
<code>queryLanguage</code>;</p></li><li><p>rules for evaluating absolute selector to collection of
nodes;</p></li><li><p>rules for evaluating relative selector to collection of
@@ -1139,7 +1141,7 @@
<its:termRule selector="//term" term="yes"/>
<its:withinTextRule withinText="yes" selector="//term | //b"/>
</its:rules>
-</myFormatInfo></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-1.xml">examples/xml/EX-link-external-rules-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2393" id="d3e2393"></a>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre>
+</myFormatInfo></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-1.xml">examples/xml/EX-link-external-rules-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2396" id="d3e2396"></a>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre>
<myDoc
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xlink="http://www.w3.org/1999/xlink" >
@@ -1154,7 +1156,7 @@
<p>A <term>Palouse horse</term> has a spotted coat.</p>
</body>
</myDoc></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-2.xml">examples/xml/EX-link-external-rules-2.xml</a>]</p></div><p>The result of processing the two documents above is the same as processing
- the following document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2405" id="d3e2405"></a>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre>
+ the following document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2408" id="d3e2408"></a>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre>
<myDoc
xmlns:its="http://www.w3.org/2005/11/its" >
<header>
@@ -1194,7 +1196,7 @@
higher precedence.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The precedence order fulfills the same purpose as the built-in template
rules of <a title="XSL
								Transformations (XSLT) Version 1.0" href="#xslt10">[XSLT 1.0]</a>. Override semantics are
always complete, that is all information that is specified in one rule
- element is overridden by the next one.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2497" id="d3e2497"></a>Example 22: Conflicts between selections of ITS information which are resolved
+ element is overridden by the next one.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2500" id="d3e2500"></a>Example 22: Conflicts between selections of ITS information which are resolved
using the precedence order</div><p>The two elements <code>title</code> and <code>author</code> of this document
should be treated as separate content when inside a <code>prolog</code>
element, but as part of the content of their parent element otherwise.
@@ -1368,13 +1370,13 @@
<code>p</code> element. It cannot be used to identify nested
elements or attributes.</p></li><li><p>Using <a href="#target-pointer">target pointer</a>, selected
<code>source</code> element have the ITS information that their
- translation is available in a <code>target</code> element; see <a href="#EX-target-pointer-global-1">Example 62</a>. This
+ translation is available in a <code>target</code> element; see <a href="#EX-target-pointer-global-1">Example 64</a>. This
information does not inherit to child elements of <code>target
pointer</code>. E.g., the translation of a <code>span</code>
element nested in <code>source</code> is not available in a specific
<code>target</code> element. Nevertheless, an application is
free to use the complete content of <code>source</code>, including
- <code>span</code>, and e.g. present it to a translator.</p></li></ul></div><a name="datacategories-overview" id="datacategories-overview"></a><table border="1" width="100%"><thead><tr><td>Data category</td><td>Local Usage</td><td>Global, rule-based selection</td><td>Global adding of information</td><td>Global pointing to existing information</td><td>Default Values</td><td>Inheritance for elements nodes</td><td>XML examples</td><td>HTML5 examples</td></tr></thead><tbody><tr><td>
+ <code>span</code>, and e.g. present it to a translator.</p></li></ul></div><span class="editor-note">[Ed. note: The links to examples (last column) are currently pointing to the old location of the test suite; these need to be updated to the github location.]</span><a name="datacategories-overview" id="datacategories-overview"></a><table border="1" width="100%"><thead><tr><td>Data category</td><td>Local Usage</td><td>Global, rule-based selection</td><td>Global adding of information</td><td>Global pointing to existing information</td><td>Default Values</td><td>Inheritance for elements nodes</td><td>XML examples</td><td>HTML5 examples</td></tr></thead><tbody><tr><td>
<a href="#trans-datacat">Translate</a>
</td><td>Yes</td><td>Yes</td><td>Yes</td><td>No</td><td>
<code>translate="yes"</code> for elements, and
@@ -1489,7 +1491,7 @@
<a href="#storagesize">Storage Size</a>
</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td><td>
<code>its:storageEncoding="UTF-8"</code>
- </td><td>None</td><td>tbd</td><td>tbd</td></tr></tbody></table><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3431" id="d3e3431"></a>Example 25: Defaults, inheritance and overriding behavior of data
+ </td><td>None</td><td>tbd</td><td>tbd</td></tr></tbody></table><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3437" id="d3e3437"></a>Example 25: Defaults, inheritance and overriding behavior of data
categories</div><p>In this example, the content of all the <code>data</code> elements is
translatable because the default for the <a href="#trans-datacat">Translate</a> data category in elements is "yes". The
content of <code>revision</code> and <code>locNote</code> is not translatable
@@ -1667,7 +1669,7 @@
<body>
<msg id="NotFound">Cannot find {0} on {1}.</msg>
</body>
-</myRes></pre></div><p>[Source file: <a href="examples/xml/EX-locNoteRef-attribute-1.xml">examples/xml/EX-locNoteRef-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3829" id="d3e3829"></a>Example 32: The <code>locNoteRefPointer</code> attribute</div><p>The <code>locNoteRefPointer</code> attribute contains a <a href="#selectors">relative selector</a> pointing to a node
+</myRes></pre></div><p>[Source file: <a href="examples/xml/EX-locNoteRef-attribute-1.xml">examples/xml/EX-locNoteRef-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3835" id="d3e3835"></a>Example 32: The <code>locNoteRefPointer</code> attribute</div><p>The <code>locNoteRefPointer</code> attribute contains a <a href="#selectors">relative selector</a> pointing to a node
that holds the URI referring to the location of the note.</p><div class="exampleInner"><pre>
<dataFile
xmlns:its="http://www.w3.org/2005/11/its" >
@@ -1691,8 +1693,7 @@
contains a URI referring to the location of the localization
note.</p></li></ul></li><li><p>An optional <code>locNoteType</code> attribute with the
value "description" or "alert". If the <code>locNoteType</code> attribute is not present, the
- type of localization note will be assumed to be
- "description". </p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3890" id="d3e3890"></a>Example 33: The <a href="#locNote-datacat">Localization Note</a> data
+ type of localization note will be assumed to be"description". </p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3896" id="d3e3896"></a>Example 33: The <a href="#locNote-datacat">Localization Note</a> data
category expressed locally</div><div class="exampleInner"><pre>
<msgList
xmlns:its="http://www.w3.org/2005/11/its" xml:space="preserve"
@@ -1706,7 +1707,7 @@
its:locNote="%1\$s is the original text's date in the format YYYY-MM-DD HH:MM always in GMT">
<value>Translated from English content dated <span id="version-info">%1\$s</span> GMT.</value>
</data>
-</msgList></pre></div><p>[Source file: <a href="examples/xml/EX-locNote-selector-2.xml">examples/xml/EX-locNote-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3904" id="d3e3904"></a>Example 34: The <a href="#locNote-datacat">Localization Note</a> data
+</msgList></pre></div><p>[Source file: <a href="examples/xml/EX-locNote-selector-2.xml">examples/xml/EX-locNote-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3910" id="d3e3910"></a>Example 34: The <a href="#locNote-datacat">Localization Note</a> data
category expressed locally in HTML5</div><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
<head>
@@ -1742,7 +1743,7 @@
term.</p></li><li><p>A <code>termInfoRefPointer</code> attribute that contains a
<a href="#selectors">relative selector</a>
pointing to a node that holds the URI referring to the
- location of the terminology information.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4002" id="d3e4002"></a>Example 35: Usage of the <code>termInfoPointer</code> attribute</div><div class="exampleInner"><pre>
+ location of the terminology information.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4008" id="d3e4008"></a>Example 35: Usage of the <code>termInfoPointer</code> attribute</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1753,7 +1754,7 @@
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-1.xml">examples/xml/EX-terms-selector-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4015" id="d3e4015"></a>Example 36: Usage of the <code>termInfoRef</code> attribute</div><div class="exampleInner"><pre>
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-1.xml">examples/xml/EX-terms-selector-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4021" id="d3e4021"></a>Example 36: Usage of the <code>termInfoRef</code> attribute</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1764,7 +1765,7 @@
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-2.xml">examples/xml/EX-terms-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4028" id="d3e4028"></a>Example 37: Usage of the <code>termInfoRefPointer</code> attribute</div><div class="exampleInner"><pre>
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-2.xml">examples/xml/EX-terms-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4034" id="d3e4034"></a>Example 37: Usage of the <code>termInfoRefPointer</code> attribute</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1855,7 +1856,7 @@
available for the <a href="#directionality">Directionality</a>
data category:</p><ul><li><p>A <code>dir</code> attribute with the value
"ltr", "rtl", "lro" or
- "rlo".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4288" id="d3e4288"></a>Example 42: The <a href="#directionality">Directionality</a> data
+ "rlo".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4294" id="d3e4294"></a>Example 42: The <a href="#directionality">Directionality</a> data
category expressed locally</div><p>On the first <code>quote</code> element, the <code>its:dir="rtl"</code>
attribute indicates a right-to-left content.</p><div class="exampleInner"><pre>
<text
@@ -1866,7 +1867,7 @@
its:dir="rtl"><span dir="rtl">نشاط التدويل، W3C</span></quote>
means <quote>Internationalization Activity, W3C</quote>.</par>
</body>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-dir-selector-3.xml">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4312" id="d3e4312"></a>Example 43: The <a href="#directionality">Directionality</a> data
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-dir-selector-3.xml">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4318" id="d3e4318"></a>Example 43: The <a href="#directionality">Directionality</a> data
category expressed locally in HTML5</div><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
<head>
@@ -2006,7 +2007,7 @@
within text.</p><p id="withintext-global">GLOBAL: The <code>withinTextRule</code> element
contains the following:</p><ul><li><p>A required <code>selector</code> attribute. It contains an <a href="#selectors">absolute selector</a> which selects the
nodes to which this rule applies.</p></li><li><p>A required <code>withinText</code> attribute with the value
- "yes", "no" or "nested".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4721" id="d3e4721"></a>Example 47: Specifying elements within text with a <code>withinTextRule</code>
+ "yes", "no" or "nested".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4727" id="d3e4727"></a>Example 47: Specifying elements within text with a <code>withinTextRule</code>
element</div><div class="exampleInner"><pre>
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
@@ -2347,9 +2348,47 @@
</legalnotice>
</info>
</book></pre></div><p>[Source file: <a href="examples/xml/EX-locale-filter-attribute-1.xml">examples/xml/EX-locale-filter-attribute-1.xml</a>]</p></div></div></div><div class="div2">
-<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="Provenance" id="Provenance"></a>6.12 Provenance</h3><p>The Provenance data category will be defined in an updated version of this
- document. For details of the proposed data category, see the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/#Provenance">ITS
- 2.0 Requirements document</a>.</p></div><div class="div2">
+<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="translation-agent-provenance" id="translation-agent-provenance"></a>6.12 Translation Agent Provenance</h3><div class="div3">
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="translation-agent-provenance-definition" id="translation-agent-provenance-definition"></a>6.12.1 Definition</h4><span class="editor-note">[Ed. note: Early draft of this data category; additional data categories for provenance might be added, or below definition might be changed. The definition of this data category is not yet reflected in the data category overview table in <a class="section-ref" href="#datacategories-defaults-etc">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.]</span><p>The <a href="#translation-agent-provenance">Translation Provenance Agent</a> data category is used to communicate the identity of agents that have been involved in the translation of the content.
+ This allows translation consumers, such as post-editors or translation quality reviewers, to assess how the performance of these agents may impact the quality of the translation.
+ Translation agents can be identified as a person, a piece of software or an organization that has been involved in providing a translation that resulted in the selected content. </p><p>This data category only offers information on the identity of translation agents. If provenance information is needed that includes temporal information about processes or requires agents that support a wider range of activities, then the Standoff Provenance data category should be used.</p><p>Translation tools, such as machine translation agents or CAT tools, may offer an easy way to create this information. Translation tools can then present this information to post-editors or translation process managers. Web applications may to present such information to consumers of translated documents.</p></div><div class="div3">
+<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="translation-agent-provenance-implementation" id="translation-agent-provenance-implementation"></a>6.12.2 Implementation</h4><p>
+ The Translation Agent Provenance data category can be expressed with global rules, or locally on an individual element. For elements, the data category information <a href="#def-inheritance">inherits</a> to the textual content of the element, including child elements and attributes.
+ </p><span class="editor-note">[Ed. note: No agreement yet on whether such usage of global rules, that is for identifiyng just one or a small set of elements, is something to recommend. See also <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/51">issue-51</a>.]</span><p id="translation-agent-provenance-global">GLOBAL : The <code>transProvRule</code> element contains the following:</p><ul><li><p>A required <code>selector</code> attribute. It contains an <a href="#selectors">absolute selector</a> which selects the
+ nodes to which this rule applies.</p></li><li><p>At least one of the following:</p><ul><li><p>Human translation provenance information specified by exactly one of the following:
+ <ul><li><p>A <code>transPerson</code> attribute that contains a string identifying a human translation agent.</p></li><li><p>A <code>transPersonRef</code> attribute that contains an IRI referring to a resource that identifies a human translation agent.</p></li><li><p>A <code>transPersonPointer</code> attribute that contains a relative selector pointing to a node with the exact same semantics as <code>transPerson</code>.</p></li><li><p>A <code>transPersonRefPointer</code> attribute that contains a relative selector pointing to a node with the exact same semantics as <code>transPersonRef</code>.</p></li></ul>
+ </p></li><li><p>Organizational translation provenance information specified by exactly of the following:
+ <ul><li><p>A <code>transOrg</code> attribute that contains a string identifying an organization acting as a translation agent.</p></li><li><p>A <code>transOrgRef</code> attribute that contains an IRI referring to a resource that identifies an organization acting as a translation agent.</p></li><li><p>A <code>transOrgPointer</code> attribute that contains a relative selector pointing to a node with the exact same semantics as transOrg.</p></li><li><p>A <code>transOrgRefPointer</code> attribute that contains a relative selector pointing to a node with the exact same semantics as transOrgRef.</p></li></ul>
+ </p></li><li><p>Translation tool provenance related information specified by exactly one of the following:</p><ul><li><p>A <code>transTool</code> attribute that contains a string identifying a software tool that was used in translating the selected content.</p></li><li><p>A <code>transToolRef</code> attribute that contains an IRI referring to a resource that identifies a software tool that was used in the translation.</p></li><li><p>A <code>transToolPointer</code> attribute that contains a relative selector pointing to a node with the exact same semantics as transTool.</p></li><li><p>A <code>transToolRefPointer</code> attribute that contains a relative selector pointing to a node with the exact same semantics as transToolRef.</p></li></ul></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translation-agent-provenance-xml-global-1" id="EX-translation-agent-provenance-xml-global-1"></a>Example 59: The <a href="#translation-agent-provenance">Transltion Agent Provenance</a> data category used globally.</div><p>In this example the provenance of the <code>par</code> (which is machine translated) and the <code>legalnotice</code> (which is human translated) elements are different. Hence the provenance information is recorded in different global translation provenance rules. </p><div class="exampleInner"><pre>
+<text
+ xmlns:its="http://www.w3.org/2005/11/its" >
+ <dc:creator>John Doe</dc:creator>
+ <its:rules version="2.0">
+ <its:transProvRule selector="/text/body/par[1]" transToolRef="http://www.onlinemtex.com/2012/7/25/wsdl/" transOrg="acme-CAT-v2.3"/>
+ <its:transProvRule selector="/text/body/legalnotice" transPersonPointer="/text/dc:creator" transOrgRef="http://www.legaltrans-ex.com/"/>
+ </its:rules>
+ <title>Translation Revision Provenance Agent: Global Test in XML</title>
+ <body>
+ <par> This paragraph was translated from the machine.</par>
+ <legalnotice postediting-by="http://www.vistatec.com/">This text
+ was translated directly by a person.</legalnotice>
+ </body>
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-translation-agent-provenance-xml-global-1.xml">examples/xml/EX-translation-agent-provenance-xml-global-1.xml</a>]</p></div><p id="translation-agent-provenance-local">LOCAL: The <code>transProvRule</code> element contains the following:</p><ul><li><p>Human translation provenance information specified by a <code>transPerson</code> OR a <code>transPersonRef</code> attribute.</p></li><li><p>Organisational translation provenance information specified by a <code>transOrg</code> OR a <code>transOrfRef</code> attribute.</p></li><li><p>Translation tool provenance information specified by a <code>transTool</code> OR a <code>transToolRef</code> attribute.</p></li></ul><p>The semantics of the six local attributes for the <a href="#translation-agent-provenance">Translation Agent Provenance</a> data categories are identical to their <a href="#translation-agent-provenance-global">global counterparts</a> with the same name.</p><div class="exampleOuter"><di class="exampleHeader"><a name="EX-translation-agent-provenance-xml-local-1" id="EX-translation-agent-provenance-xml-local-1"></a>Example 60: The <a href="#translation-agent-provenance">Translation Agent Provenance</a> data category used locally.</div><p>The example is identical to <a href="#EX-translation-agent-provenance-xml-global-1">Example 59</a>, that is, it conveys the same ITS <a href="#translation-agent-provenance">Translation Agent Provenance</a>, but now locally.</p><div class="exampleInner"><pre>
+<text
+ xmlns:its="http://www.w3.org/2005/11/its"
+ its:version="2.0">
+ <dc:creator>John Doe</dc:creator>
+ <title>Translation Revision Provenance Agent: Global Test in XML</title>
+ <body>
+ <par
+ its:transToolRef="http://www.onlinemtex.com/2012/7/25/wsdl/"
+ its:transOrg="acme-CAT-v2.3"> This paragraph was translated from the machine.</par>
+ <legalnotice postediting-by="http://www.vistatec.com/"
+ its:transPerson="John Doe"
+ its:transOrgRef="http://www.legaltrans-ex.com/">This text was translated directly by a
+ person.</legalnotice>
+ </body>
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-translation-agent-provenance-xml-local-1.xml">examples/xml/EX-translation-agent-provenance-xml-local-1.xml</a>]</p></div></div></div><div class="div2">
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="TextAnalyisAnnotation" id="TextAnalyisAnnotation"></a>6.13 TextAnalyisAnnotation</h3><p>The TextAnalyisAnnotation data category will be defined in an updated version
of this document. For details of the proposed data category, see the <a href="http://www.w3.org/TR/2012/WD-its2req-20120524/#textAnalysisAnnotation">ITS 2.0 Requirements document</a>.</p></div><div class="div2">
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="externalresource" id="externalresource"></a>6.14 External Resource</h3><div class="div3">
@@ -2363,7 +2402,7 @@
<code>externalResourceRefRule</code> element contains the following:</p><ul><li><p>A required <code>selector</code> attribute. It contains an <a href="#selectors">absolute selector</a> which selects the
nodes to which this rule applies.</p></li><li><p>A required <code>externalResourceRefPointer</code> attribute that
contains a <a href="#selectors">relative selector</a> pointing
- to a node that provides the URI of the external resource.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-externalresource-1" id="EX-externalresource-1"></a>Example 59: The <code>externalResourceRefRule</code> element</div><p>The <code>externalResourceRefRule</code> element expresses that the
+ to a node that provides the URI of the external resource.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-externalresource-1" id="EX-externalresource-1"></a>Example 61: The <code>externalResourceRefRule</code> element</div><p>The <code>externalResourceRefRule</code> element expresses that the
<code>imagedata</code>, <code>audiodata</code> and
<code>videodata</code> elements contain references to external
resources. These references are expressed via a <code>fileref</code>
@@ -2392,7 +2431,7 @@
</warning>
</textobject>
</mediaobject>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-externalresource-1.xml">examples/xml/EX-externalresource-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-externalresource-2" id="EX-externalresource-2"></a>Example 60: Two <code>externalResourceRefRule</code> elements used for external
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-externalresource-1.xml">examples/xml/EX-externalresource-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-externalresource-2" id="EX-externalresource-2"></a>Example 62: Two <code>externalResourceRefRule</code> elements used for external
resources associated with HTML5 <code>video</code> elements</div><p>The two <code>externalResourceRefRule</code> elements select the
<code>src</code> and the <code>poster</code> attributes at HTML5
<code>video</code> elements. These attributes identify different
@@ -2400,12 +2439,12 @@
these resources. For this reason, the
<code>externalResourceRefPointer</code> attributes point to the
value of <code>src</code> and <code>poster</code> respectively. The
- underlying HTML5 document is given in <a href="#EX-externalresource-html5-1">Example 61</a>.</p><div class="exampleInner"><pre>
+ underlying HTML5 document is given in <a href="#EX-externalresource-html5-1">Example 63</a>.</p><div class="exampleInner"><pre>
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
<its:externalResourceRefRule selector="//html:video/@src" externalResourceRefPointer="."/>
<its:externalResourceRefRule selector="//html:video/@poster" externalResourceRefPointer="."/>
-</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-externalresource-2.xml">examples/xml/EX-externalresource-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-externalresource-html5-1" id="EX-externalresource-html5-1"></a>Example 61: An HTML5 document that can be used for <a href="#EX-externalresource-2">Example 60</a>.</div><div class="exampleInner"><pre><!DOCTYPE html>
+</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-externalresource-2.xml">examples/xml/EX-externalresource-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-externalresource-html5-1" id="EX-externalresource-html5-1"></a>Example 63: An HTML5 document that can be used for <a href="#EX-externalresource-2">Example 62</a>.</div><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
<head>
<meta charset=utf-8>
@@ -2448,7 +2487,7 @@
node.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The source node and the target node may be of different types, but
the target node must be able to contain the same content of the
source node (e.g. an attribute node cannot be the target node of a
- source node that is an element with children).</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-target-pointer-global-1" id="EX-target-pointer-global-1"></a>Example 62: Defining the target location of a source content with the
+ source node that is an element with children).</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-target-pointer-global-1" id="EX-target-pointer-global-1"></a>Example 64: Defining the target location of a source content with the
<code>targetPointerRule</code> element</div><div class="exampleInner"><pre>
<file
xmlns:its="http://www.w3.org/2005/11/its" >
@@ -2481,7 +2520,7 @@
only provides for rules to be expressed at a global level.
Locally, users are able to use <code>xml:id</code> (which is
defined by XML) or an attribute specific to the format in
- question (as in <a href="#EX-idvalue-attribute-1">Example 65</a>).</p></li><li><p>Applying the <a href="#idvalue">Id Value</a> data
+ question (as in <a href="#EX-idvalue-attribute-1">Example 67</a>).</p></li><li><p>Applying the <a href="#idvalue">Id Value</a> data
category to <code>xml:id</code> attributes using global rules
is not necessary, since <code>xml:id</code> is the recommended
way to specify an identifier in XML.</p></li></ul></div></div><div class="div3">
@@ -2496,7 +2535,7 @@
within the document. If the attribute <code>xml:id</code> is present
for the selected node, the value of the <code>xml:id</code>
attribute <a href="#rfc2119">MUST</a> take precedence over the
- <code>idValue</code> value.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-idvalue-element-1" id="EX-idvalue-element-1"></a>Example 63: Pointing to an ID value with the <code>idValueRule</code>
+ <code>idValue</code> value.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-idvalue-element-1" id="EX-idvalue-element-1"></a>Example 65: Pointing to an ID value with the <code>idValueRule</code>
element</div><p>The <code>idValueRule</code> element indicates that the unique identifier
for each <code><text></code> element is the value of the
attribute <code>name</code> of its parent element.</p><div class="exampleInner"><pre>
@@ -2517,7 +2556,7 @@
<pos>2, 1</pos>
<trig>cancelAll</trig>
</entry>
-</resources></pre></div><p>[Source file: <a href="examples/xml/EX-idvalue-element-1.xml">examples/xml/EX-idvalue-element-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-idvalue-element-2" id="EX-idvalue-element-2"></a>Example 64: Constructing ID values using the <code>idValueRule</code>
+</resources></pre></div><p>[Source file: <a href="examples/xml/EX-idvalue-element-1.xml">examples/xml/EX-idvalue-element-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-idvalue-element-2" id="EX-idvalue-element-2"></a>Example 66: Constructing ID values using the <code>idValueRule</code>
element.</div><p>The <code>idValue</code> attribute allows to build composite values
based on different attributes, element or event hard-coded text. Any
of the String functions offered by XPath can be used. In the
@@ -2542,7 +2581,7 @@
<desc>The module cannot find the default settings file.
You need to re-initialize the system.</desc>
</msg>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-idvalue-element-2.xml">examples/xml/EX-idvalue-element-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-idvalue-attribute-1" id="EX-idvalue-attribute-1"></a>Example 65: Using <code>xml:id</code> and <code>idValueRule</code>
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-idvalue-element-2.xml">examples/xml/EX-idvalue-element-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-idvalue-attribute-1" id="EX-idvalue-attribute-1"></a>Example 67: Using <code>xml:id</code> and <code>idValueRule</code>
</div><p>When an <code>xml:id</code> attribute is present for a node selected by
an <code>idValueRule</code> element, the value of <code>xml:id</code>
takes precedence over the value defined by the <code>idValueRule</code>
@@ -2573,7 +2612,7 @@
documents parsed as text/html.</p></div><p id="preservespace-global">GLOBAL: The <code>preserveSpaceRule</code>
element contains the following:</p><ul><li><p>A required <code>selector</code> attribute. It contains an <a href="#selectors">absolute selector</a> which selects the
nodes to which this rule applies.</p></li><li><p>A required <code>space</code> attribute with the value "default" or
- "preserve".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-perservespace-global-1" id="EX-perservespace-global-1"></a>Example 66: The <a href="#preservespace">Preserve Space</a> data
+ "preserve".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-perservespace-global-1" id="EX-perservespace-global-1"></a>Example 68: The <a href="#preservespace">Preserve Space</a> data
category expressed globally</div><p>The <code>preserveSpaceRule</code> element specifies that whitespace in
all verse elements must be treated literally.</p><div class="exampleInner"><pre>
<book
@@ -2593,7 +2632,7 @@
</book></pre></div><p>[Source file: <a href="examples/xml/EX-preservespace-global-1.xml">examples/xml/EX-preservespace-global-1.xml</a>]</p></div><p id="preservespace-local">LOCAL: The <code>xml:space</code> attribute,
as defined in section 2.10 of <a title="Extensible
								Markup Language (XML) 1.0 (Fourth Edition)" href="#xml10spec">[XML 1.0]</a>,
maps exactly to the <a href="#preservespace">Preserve Space</a>
- data category.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-perservespace-local-1" id="EX-perservespace-local-1"></a>Example 67: The <a href="#preservespace">Preserve Space</a> data
+ data category.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-perservespace-local-1" id="EX-perservespace-local-1"></a>Example 69: The <a href="#preservespace">Preserve Space</a> data
category expressed locally</div><p>The standard <code>xml:space</code> attribute specifies that the
whitespace in the verse element must be treated literally.</p><div class="exampleInner"><pre>
<book
@@ -2675,7 +2714,7 @@
<code>locQualityIssueCommentPointer</code>,
<code>locQualityIssueSeverityPointer</code> and
<code>locQualityIssueProfileRefPointer</code> do not apply to HTML
- as local markup is provided for direct annotation in HTML.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-global-1" id="EX-locQualityIssue-global-1"></a>Example 68: Annotating an issue in XML with <code>locQualityIssueRule</code>
+ as local markup is provided for direct annotation in HTML.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-global-1" id="EX-locQualityIssue-global-1"></a>Example 70: Annotating an issue in XML with <code>locQualityIssueRule</code>
element</div><p>The <code>locQualityIssueRule</code> element associates the issue
information with a selected span of content.</p><div class="exampleInner"><pre>
<doc
@@ -2691,7 +2730,7 @@
</header>
<para>
<span id="q1">this</span> is an example</para>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-global-1.xml">examples/xml/EX-locQualityIssue-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-global-2" id="EX-locQualityIssue-global-2"></a>Example 69: Using <code>locQualityIssueRule</code> to map equivalent markup</div><p>The <code>locQualityIssueRule</code> element defines what constructs are
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-global-1.xml">examples/xml/EX-locQualityIssue-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-global-2" id="EX-locQualityIssue-global-2"></a>Example 71: Using <code>locQualityIssueRule</code> to map equivalent markup</div><p>The <code>locQualityIssueRule</code> element defines what constructs are
equivalent to the native ITS markup for the different pieces of
information of the data category.</p><div class="exampleInner"><pre>
<doc
@@ -2712,9 +2751,9 @@
note="Sentence without capitalization"
value="50"
profile="http://example.org/qaModel/v13">this</issue> is an example</para>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-global-2.xml">examples/xml/EX-locQualityIssue-global-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-global" id="EX-locQualityIssue-html5-global"></a>Example 70: Annotating an issue in HTML5 with <code>locQualityIssueRule</code>
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-global-2.xml">examples/xml/EX-locQualityIssue-global-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-global" id="EX-locQualityIssue-html5-global"></a>Example 72: Annotating an issue in HTML5 with <code>locQualityIssueRule</code>
element</div><p>The <code>locQualityIssueRule</code> element resides in a separate file
- (<a href="#EX-locQualityIssueRule-html5-global">Example 71</a>) that associates the issue information with a selected span of
+ (<a href="#EX-locQualityIssueRule-html5-global">Example 73</a>) that associates the issue information with a selected span of
content in the HTML document.</p><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
<head>
@@ -2726,7 +2765,7 @@
<p>
<span id=q1>this</span> is an example.</p>
</body>
- </html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssue-html5-global.html">examples/html5/EX-locQualityIssue-html5-global.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssueRule-html5-global" id="EX-locQualityIssueRule-html5-global"></a>Example 71: External rule document associated with an HTML5 document</div><p>This document is used in <a href="#EX-locQualityIssue-html5-global">Example 70</a>:</p><div class="exampleInner"><pre>
+ </html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssue-html5-global.html">examples/html5/EX-locQualityIssue-html5-global.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssueRule-html5-global" id="EX-locQualityIssueRule-html5-global"></a>Example 73: External rule document associated with an HTML5 document</div><p>This document is used in <a href="#EX-locQualityIssue-html5-global">Example 72</a>:</p><div class="exampleInner"><pre>
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
<its:locQualityIssueRule
@@ -2770,7 +2809,7 @@
carry pertains to the content of the element that refers to the standoff
annotation, not to the content of the element <code>locQualityIssue</code>
(or <code><span loc-quality-issue></code>in HTML) where they are
- declared.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-1" id="EX-locQualityIssue-local-1"></a>Example 72: Annotating an issue in XML with local inline markup</div><p>The attributes <code>locQualityIssueType</code>,
+ declared.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-1" id="EX-locQualityIssue-local-1"></a>Example 74: Annotating an issue in XML with local inline markup</div><p>The attributes <code>locQualityIssueType</code>,
<code>locQualityIssueComment</code> and
<code>locQualityIssueSeverity</code> are used to associate the
issue information directly with a selected span of content.</p><div class="exampleInner"><pre>
@@ -2782,7 +2821,7 @@
its:locQualityIssueType="typographical"
its:locQualityIssueComment="Sentence without capitalization"
its:locQualityIssueSeverity="50">this</span> is an example</para>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-1.xml">examples/xml/EX-locQualityIssue-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-local-1" id="EX-locQualityIssue-html5-local-1"></a>Example 73: Annotating an issue in HTML with local inline markup</div><p>In this example several spans of content are associated with a
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-1.xml">examples/xml/EX-locQualityIssue-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-local-1" id="EX-locQualityIssue-html5-local-1"></a>Example 75: Annotating an issue in HTML with local inline markup</div><p>In this example several spans of content are associated with a
quality issue.</p><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
<head>
@@ -2817,7 +2856,7 @@
its-loc-quality-issue-type=spelling>qulaity</span> with his instrument, a standard that would not only satisfy listeners but that
would overcome all the flaws of traditional instruments.</p>
</body>
- </html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssue-html5-local-1.html">examples/html5/EX-locQualityIssue-html5-local-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-2" id="EX-locQualityIssue-local-2"></a>Example 74: Annotating an issue in XML with local standoff markup</div><p>The following example shows a document using local standoff markup to
+ </html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityIssue-html5-local-1.html">examples/html5/EX-locQualityIssue-html5-local-1.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-2" id="EX-locQualityIssue-local-2"></a>Example 76: Annotating an issue in XML with local standoff markup</div><p>The following example shows a document using local standoff markup to
encode several issues. The <code>mrk</code> element delimits the
content to markup and holds a <code>locQualityIssuesRef</code>
attribute that points to the <code>locQualityIssues</code> element where
@@ -2840,7 +2879,7 @@
</trans-unit>
</body>
</file>
-</xliff></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-2.xml">examples/xml/EX-locQualityIssue-local-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-3" id="EX-locQualityIssue-local-3"></a>Example 75: Annotating an issue in XML with local standoff markup and a global
+</xliff></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-2.xml">examples/xml/EX-locQualityIssue-local-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-local-3" id="EX-locQualityIssue-local-3"></a>Example 77: Annotating an issue in XML with local standoff markup and a global
rule</div><p>The following example shows a document using local standoff markup to
encode several issues. But because, in this case, the
<code>mrk</code> element does not allow attributes from another
@@ -2870,7 +2909,7 @@
</its:locQualityIssues>
</unit>
</file>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-3.xml">examples/xml/EX-locQualityIssue-local-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-local-2" id="EX-locQualityIssue-html5-local-2"></a>Example 76: Annotating an issue in HTML with local standoff markup</div><p>The following example shows a document using local standoff markup to
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityIssue-local-3.xml">examples/xml/EX-locQualityIssue-local-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityIssue-html5-local-2" id="EX-locQualityIssue-html5-local-2"></a>Example 78: Annotating an issue in HTML with local standoff markup</div><p>The following example shows a document using local standoff markup to
encode several issues. The <code>span</code> element delimits the
content to markup and holds a <code>loc-quality-issues-ref</code>
attribute that points to a special <code>span</code> element where
@@ -2941,7 +2980,7 @@
<code>locQualityPrecisProfileRef</code>.</p></li></ul></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>The attributes <code>locQualityPrecisScorePointer</code>,
<code>locQualityPrecisThresholdPointer</code>, and
<code>locQualityPrecisProfileRefPointer</code> do not apply to
- HTML as local markup is provided for direct annotation in HTML.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-global-1" id="EX-locQualityPrecis-global-1"></a>Example 77: The <a href="#lqprecis">Localization Quality Précis</a> data
+ HTML as local markup is provided for direct annotation in HTML.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-global-1" id="EX-locQualityPrecis-global-1"></a>Example 79: The <a href="#lqprecis">Localization Quality Précis</a> data
category expressed globally in XML</div><p>The following example shows how to use the
<code>locQualityPrecisRule</code> element to specify the score,
threshold and profile for a document.</p><div class="exampleInner"><pre>
@@ -2957,7 +2996,7 @@
</its:rules>
</header>
<para>This is an example</para>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityPrecis-global-1.xml">examples/xml/EX-locQualityPrecis-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-global-2" id="EX-locQualityPrecis-global-2"></a>Example 78: Using pointers to map the <a href="#lqprecis">Localization
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityPrecis-global-1.xml">examples/xml/EX-locQualityPrecis-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-global-2" id="EX-locQualityPrecis-global-2"></a>Example 80: Using pointers to map the <a href="#lqprecis">Localization
Quality Précis</a> data category in XML</div><p>The following example shows how the
<code>locQualityPrecisVotePointer</code>,
<code>locQualityPrecisThresholdPointer</code> and
@@ -2976,7 +3015,7 @@
</its:rules>
</header>
<para>This is not popular</para>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityPrecis-global-2.xml">examples/xml/EX-locQualityPrecis-global-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-html5-global" id="EX-locQualityPrecis-html5-global"></a>Example 79: The <a href="#lqprecis">Localization Quality Précis</a> data
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityPrecis-global-2.xml">examples/xml/EX-locQualityPrecis-global-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-html5-global" id="EX-locQualityPrecis-html5-global"></a>Example 81: The <a href="#lqprecis">Localization Quality Précis</a> data
category expressed globally in HTML</div><p>The following example shows how to use the
<code>locQualityPrecisRule</code> element to specify the score,
threshold and profile for an HTML document.</p><div class="exampleInner"><pre><!DOCTYPE html>
@@ -2989,7 +3028,7 @@
<body>
<p>This is an example.</p>
</body>
- </html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityPrecis-html5-global.html">examples/html5/EX-locQualityPrecis-html5-global.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecisRule-html5-global" id="EX-locQualityPrecisRule-html5-global"></a>Example 80: External rule document associated with an HTML5 document</div><p>This document is used in <a href="#EX-locQualityPrecis-html5-global">Example 79</a>:</p><div class="exampleInner"><pre>
+ </html></pre></div><p>[Source file: <a href="examples/html5/EX-locQualityPrecis-html5-global.html">examples/html5/EX-locQualityPrecis-html5-global.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecisRule-html5-global" id="EX-locQualityPrecisRule-html5-global"></a>Example 82: External rule document associated with an HTML5 document</div><p>This document is used in <a href="#EX-locQualityPrecis-html5-global">Example 81</a>:</p><div class="exampleInner"><pre>
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
<its:locQualityPrecisRule
@@ -3008,7 +3047,7 @@
vote that constitutes a passing score or a passing vote in the
profile used.</p></li><li><p>An optional <code>locQualityPrecisProfileRef</code> attribute.
Its value is a URI pointing to the reference document describing
- the quality assessment model used for the scoring.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-local-1" id="EX-locQualityPrecis-local-1"></a>Example 81: The <a href="#lqprecis">Localization Quality Précis</a> data
+ the quality assessment model used for the scoring.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-local-1" id="EX-locQualityPrecis-local-1"></a>Example 83: The <a href="#lqprecis">Localization Quality Précis</a> data
category expressed locally in XML</div><p>The <code>locQualityPrecisScore</code>,
<code>locQualityPrecisThreshold</code> and
<code>locQualityPrecisProfileRef</code> are used to score the
@@ -3024,7 +3063,7 @@
the window, he uncovered an ambuscade, in the person of his aunt; and when she
saw the state his clothes were in her resolution to turn his Saturday holiday
into captivity at hard labor became adamantine in its firmness.</para>
-</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityPrecis-local-1.xml">examples/xml/EX-locQualityPrecis-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-html5-local" id="EX-locQualityPrecis-html5-local"></a>Example 82: The <a href="#lqprecis">Localization Quality Précis</a> data
+</doc></pre></div><p>[Source file: <a href="examples/xml/EX-locQualityPrecis-local-1.xml">examples/xml/EX-locQualityPrecis-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locQualityPrecis-html5-local" id="EX-locQualityPrecis-html5-local"></a>Example 84: The <a href="#lqprecis">Localization Quality Précis</a> data
category expressed locally in HTML</div><p>The <code>its-loc-quality-precis-score</code>,
<code>its-loc-quality-precis-threshold</code> and
<code>its-loc-quality-precis-profile-ref</code> are used to score
@@ -3083,7 +3122,7 @@
engine</p></li><li><p>A Domain as per the <a class="section-ref" href="#domain">Section 6.9: Domain</a>
</p></li><li><p>A privately structured string, eg.
<code>Domain:IT-Pair:IT-JA</code>,
- <code>IT-JA:Medical</code>, etc.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-mtConfidence-global-1" id="EX-mtConfidence-global-1"></a>Example 83: Global usage of <code>mtConfidenceRule</code>, <code>mtProducer</code>,
+ <code>IT-JA:Medical</code>, etc.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-mtConfidence-global-1" id="EX-mtConfidence-global-1"></a>Example 85: Global usage of <code>mtConfidenceRule</code>, <code>mtProducer</code>,
and <code>mtEngine</code> (specified by BCP 47 t-extension) along with
local usage of <code>mtConfidenceScore</code>
</div><div class="exampleInner"><pre>
@@ -3100,7 +3139,7 @@
its:mtConfidenceScore="0.8982">Dublin is the capital city of Ireland.</span>
</p>
</body>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-mtConfidence-global-1.xml">examples/xml/EX-mtConfidence-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-mtConfidence-global-2" id="EX-mtConfidence-global-2"></a>Example 84: Global usage of <code>mtConfidenceRule</code>, <code>mtProducer</code>,
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-mtConfidence-global-1.xml">examples/xml/EX-mtConfidence-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-mtConfidence-global-2" id="EX-mtConfidence-global-2"></a>Example 86: Global usage of <code>mtConfidenceRule</code>, <code>mtProducer</code>,
and <code>mtEngine</code> (specified with a sample privately
structured string) along with local usage of
<code>mtConfidenceScore</code>
@@ -3125,7 +3164,7 @@
Translate”, “DCU Matrex”, “vanilla Moses” etc.</p></li><li><p>An mtEngine attribute that contains a string uniquely
identifying a specific MT engine on a platform given in
mtProducer. Some examples of values are given for the <a href="#mtconfidence-global">global definition of MT
- Confidence</a>.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-mtConfidence-local-1" id="EX-mtConfidence-local-1"></a>Example 85: The <a href="#mtconfidence">MT Confidence</a> data category
+ Confidence</a>.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-mtConfidence-local-1" id="EX-mtConfidence-local-1"></a>Example 87: The <a href="#mtconfidence">MT Confidence</a> data category
expressed locally</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
@@ -3137,7 +3176,7 @@
its:mtConfidenceScore="0.8982">Dublin is the capital city of Ireland.</span>
</p>
</body>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-mtConfidence-local-1.xml">examples/xml/EX-mtConfidence-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-mtConfidence-html5-local-1" id="EX-mtConfidence-html5-local-1"></a>Example 86: The <a href="#mtconfidence">MT Confidence</a> data category
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-mtConfidence-local-1.xml">examples/xml/EX-mtConfidence-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-mtConfidence-html5-local-1" id="EX-mtConfidence-html5-local-1"></a>Example 88: The <a href="#mtconfidence">MT Confidence</a> data category
expressed locally in HTML5</div><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
<head>
@@ -3183,7 +3222,7 @@
contains a <a href="#selectors">relative
selector</a> pointing to a node with the exact
same semantics as
- <code>allowedCharacters</code>.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-global-1" id="EX-allowedCharacters-global-1"></a>Example 87: The <a href="#allowedchars">Allowed Characters</a> data
+ <code>allowedCharacters</code>.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-global-1" id="EX-allowedCharacters-global-1"></a>Example 89: The <a href="#allowedchars">Allowed Characters</a> data
category expressed globally in XML</div><p>The <code>allowedCharactersRule</code> element states that the translated
content of elements <code>content</code> must not contain the characters
<code>*</code> and <code>+</code>.</p><div class="exampleInner"><pre>
@@ -3199,7 +3238,7 @@
sed diam nonumy eirmod tempor invidunt ut labore et dolore magna
aliquyam erat, sed diam voluptua.</content>
</body>
-</myRes></pre></div><p>[Source file: <a href="examples/xml/EX-allowedCharacters-global-1.xml">examples/xml/EX-allowedCharacters-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-global-2" id="EX-allowedCharacters-global-2"></a>Example 88: Mapping the <a href="#allowedchars">Allowed Characters</a>
+</myRes></pre></div><p>[Source file: <a href="examples/xml/EX-allowedCharacters-global-1.xml">examples/xml/EX-allowedCharacters-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-global-2" id="EX-allowedCharacters-global-2"></a>Example 90: Mapping the <a href="#allowedchars">Allowed Characters</a>
data category in XML</div><p>The attribute <code>allowedCharactersPointer</code> is used to map the
data category to the non-ITS attribute <code>set</code> in this
document. The attribute has the same semantics as
@@ -3215,7 +3254,7 @@
</res></pre></div><p>[Source file: <a href="examples/xml/EX-allowedCharacters-global-2.xml">examples/xml/EX-allowedCharacters-global-2.xml</a>]</p></div><p id="allowedchars-local">LOCAL: the following local markup is
available for the <a href="#allowedchars">Allowed Characters</a>
data category:</p><ul><li><p>A <code>allowedCharacters</code> attribute that contains the
- regular expression indicating the allowed characters.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-local-1" id="EX-allowedCharacters-local-1"></a>Example 89: The <a href="#allowedchars">Allowed Characters</a> data
+ regular expression indicating the allowed characters.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-local-1" id="EX-allowedCharacters-local-1"></a>Example 91: The <a href="#allowedchars">Allowed Characters</a> data
category expressed locally in XML</div><p>The local <code>allowedCharacters</code> attribute specifies that the
translated content of element <code>panelmsg</code> must contain only
Unicode characters between U+0020 and U+00FE.</p><div class="exampleInner"><pre>
@@ -3226,7 +3265,7 @@
<panelmsg
its:allowedCharacters="[ -þ]">CONTINUE</panelmsg> Button
on the printer panel</msg>
-</messages></pre></div><p>[Source file: <a href="examples/xml/EX-allowedCharacters-local-1.xml">examples/xml/EX-allowedCharacters-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-html5-local-1" id="EX-allowedCharacters-html5-local-1"></a>Example 90: The <a href="#allowedchars">Allowed Characters</a> data
+</messages></pre></div><p>[Source file: <a href="examples/xml/EX-allowedCharacters-local-1.xml">examples/xml/EX-allowedCharacters-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-allowedCharacters-html5-local-1" id="EX-allowedCharacters-html5-local-1"></a>Example 92: The <a href="#allowedchars">Allowed Characters</a> data
category expressed locally in HTML</div><p>The local <code>its-allowed-characters</code> attribute specifies that
the translated content of element <code>code</code> must not contain the
characters other than 'a' to 'z' in any case and the characters
@@ -3273,7 +3312,7 @@
<code>lf</code> for LINE FEED (U+000A), <code>crlf</code>
for CARRIAGE RETURN (U+000D) followed by LINE FEED (U+000A), or
<code>nel</code> for NEXT LINE (U+0085). The default value
- is <code>lf</code>.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-storageSize-global-1" id="EX-storageSize-global-1"></a>Example 91: The <a href="#storagesize">Storage Size</a> data category
+ is <code>lf</code>.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-storageSize-global-1" id="EX-storageSize-global-1"></a>Example 93: The <a href="#storagesize">Storage Size</a> data category
expressed globally in XML</div><p>The <code>storageSizeRule</code> element is used to specify that, when
encoded in ISO-8859-1, the content of the <code>country</code> element
must not be more than 25 bytes. The name "Papouasie-Nouvelle-Guinée"
@@ -3288,7 +3327,7 @@
<country id="123">Papouasie-Nouvelle-Guinée</country>
<country id="139">République Dominicaine</country>
</data>
-</db></pre></div><p>[Source file: <a href="examples/xml/EX-storageSize-global-1.xml">examples/xml/EX-storageSize-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-storageSize-global-2" id="EX-storageSize-global-2"></a>Example 92: Mapping the <a href="#storagesize">Storage Size</a> data
+</db></pre></div><p>[Source file: <a href="examples/xml/EX-storageSize-global-1.xml">examples/xml/EX-storageSize-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-storageSize-global-2" id="EX-storageSize-global-2"></a>Example 94: Mapping the <a href="#storagesize">Storage Size</a> data
category in XML</div><p>The <code>storageSizePointer</code> attribute is used to map the non-ITS
attribute <code>max</code> to the same functionality as
<code>storageSize</code>. There is no character set encoding
@@ -3318,7 +3357,7 @@
<code>lf</code> for LINE FEED (U+000A), <code>crlf</code>
for CARRIAGE RETURN (U+000D) followed by LINE FEED (U+000A), or
<code>nel</code> for NEXT LINE (U+0085). The default value
- is <code>lf</code>.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-storageSize-local-1" id="EX-storageSize-local-1"></a>Example 93: The <a href="#storagesize">Storage Size</a> data category
+ is <code>lf</code>.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-storageSize-local-1" id="EX-storageSize-local-1"></a>Example 95: The <a href="#storagesize">Storage Size</a> data category
expressed locally in XML</div><p>The <code>storageSize</code> attribute allows to specify different the
maximum storage sizes throughout the document.</p><div class="exampleInner"><pre>
<messages
@@ -3333,7 +3372,7 @@
<var num="panelB5_Cancel"
its:storageSize="12"
its:storageEncoding="UTF-16">CANCEL</var>
-</messages></pre></div><p>[Source file: <a href="examples/xml/EX-storageSize-local-1.xml">examples/xml/EX-storageSize-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-storageSize-html5-local-1" id="EX-storageSize-html5-local-1"></a>Example 94: The <a href="#storagesize">Storage Size</a> data category
+</messages></pre></div><p>[Source file: <a href="examples/xml/EX-storageSize-local-1.xml">examples/xml/EX-storageSize-local-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-storageSize-html5-local-1" id="EX-storageSize-html5-local-1"></a>Example 96: The <a href="#storagesize">Storage Size</a> data category
expressed locally in HTML</div><p>The <code>its-storage-size</code> is used here to specify the maximum
number of bytes the two editable strings can have in UTF-8.</p><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
@@ -3360,7 +3399,7 @@
terminology data category can be stored as <code>its-term</code>, <code>ITS-TERM</code>,
<code>its-Term</code> etc. All those attributes are treated as equivalent and will
gets normalized upon DOM construction.</p></div></div><div class="div2">
-<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e7734" id="d3e7734"></a>7.2 Inline Global Rules in HTML5</h3><p>Inline global rules MUST be specified inside <code>script</code> which has <code>type</code>
+<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e7960" id="d3e7960"></a>7.2 Inline Global Rules in HTML5</h3><p>Inline global rules MUST be specified inside <code>script</code> which has <code>type</code>
attribute with the value <code>application/xml</code> or <code>application/its+xml</code>.
The <code>script</code> element itself MUST be child of <code>head</code> element. Comments MUST
NOT be used inside global rules. Each <code>script</code> element MUST NOT contain more then
@@ -3701,7 +3740,7 @@
<em>This section is informative.</em>
</p><p>Several constraints of ITS markup cannot be validated with ITS schemas. The
following <a title="Rule-based validation
							-- Schematron" href="#schematron">[Schematron]</a> document allows for
- validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8757" id="d3e8757"></a>Example 95: Testing constraints in ITS markup</div><div class="exampleInner"><pre>
+ validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8983" id="d3e8983"></a>Example 97: Testing constraints in ITS markup</div><div class="exampleInner"><pre>
<sch:schema
xmlns:sch="http://www.ascc.net/xml/schematron" >
<!-- Schematron document to test constraints for global and local ITS markup.
@@ -3769,7 +3808,7 @@
</p><p>The following <a title="Namespace-based Validation
							Dispatching Language (NVDL)" href="#nvdl">[NVDL]</a> document allows validation of
ITS markup which has been added to a host vocabulary. Only ITS elements and
attributes are checked. Elements and attributes of host language are ignored
- during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e8779" id="d3e8779"></a>Example 96: NVDL schema for ITS</div><div class="exampleInner"><pre>
+ during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e9005" id="d3e9005"></a>Example 98: NVDL schema for ITS</div><div class="exampleInner"><pre>
<nvdl:rules
xmlns:nvdl="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0" >
<nvdl:namespace ns="http://www.w3.org/2005/11/its">
@@ -3828,8 +3867,7 @@
</html></pre></div></div><p>Case 3: The NLP annotation created in NIF starts in one region and ends in another. Solution: No straight mapping is possible; a mapping can be created if both regions have the same parent.</p></div><div class="div1">
<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="revisionlog" id="revisionlog"></a>H Revision Log (Non-Normative)</h2><p id="changelog-since-20120829">The following log records major changes that
have been made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20120829/">ITS 2.0 Working Draft
- 29 August 2012</a>.</p><ol class="depth1"><li><p>Added separate section about HTML5 implementation of ITS.</p></li><li><p>Removed inline markup declarations</p></li><li><p>Added informative appendix mapping <code>locQualityIssueType</code> values
- to tool-specific issue types</p></li><li><p>Addition of a <code>locQualityPrecisVote</code> attribute and a
+ 29 August 2012</a>.</p><ol class="depth1"><li><p>Added <a class="section-ref" href="#translation-agent-provenance">Section 6.12: Translation Agent Provenance</a></p></li><li><p>Added <a class="section-ref" href="#html5-markup">Section 7: Using ITS Markup in HTML5</a>.</p></li><li><p>Removed inline markup declarations.</p></li><li><p>Addition of a <code>locQualityPrecisVote</code> attribute and a
<code>locQualityPrecisVotePointer</code> attribute to <a class="section-ref" href="#lqprecis">Section 6.19: Localization Quality Précis</a>.</p></li><li><p>A <a href="#its-information_versus_content">clarification</a> of ITS
data category information and processing of content in <a class="section-ref" href="#datacategories-defaults-etc">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.</p></li><li><p>Added <a class="section-ref" href="#allowedchars">Section 6.21: Allowed Characters</a>.</p></li><li><p>Added <a class="section-ref" href="#storagesize">Section 6.22: Storage Size</a>.</p></li><li><p>Added <a class="section-ref" href="#mtconfidence">Section 6.20: MT Confidence</a>.</p></li><li><p>Added <a href="#qa-issue-types-tool-specific-mappings">a note</a>
about informative mappings of <a href="#lqissue-typevalues">Values for
Received on Sunday, 14 October 2012 19:09:58 UTC