- From: Felix Sasaki via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 12 Nov 2012 15:04:47 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory hutz:/tmp/cvs-serv19356/TR-version
Modified Files:
Overview.html
Log Message:
Draft regeneration, including life-edit draft
Index: Overview.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -d -r1.64 -r1.65
--- Overview.html 24 Oct 2012 03:26:08 -0000 1.64
+++ Overview.html 12 Nov 2012 15:04:45 -0000 1.65
@@ -87,9 +87,9 @@
<div class="toc3">5.2.2 <a href="#selection-local">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2134">XPath 1.0</a></div>
-<div class="toc3">5.3.3 <a href="#d0e2311">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2347">Additional query languages</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2156">XPath 1.0</a></div>
+<div class="toc3">5.3.3 <a href="#d0e2333">CSS Selectors</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2369">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>
@@ -336,7 +336,8 @@
information architects, rather than the content producers
themselves.</p></div><div class="div4">
<h5><a name="users_machine-translation" id="users_machine-translation"></a>1.3.1.5Machine Translation Systems</h5><p>This type of service is intended for a broad user community ranging from developers and integrators through translation companies and agencies, freelance translators and post-editors to ordinary translation consumers and other types of MT employment. Data categories are envisaged for supporting and guiding the different automated backend processes of this service type, thereby adding substantial value to the service results as well as possible subsequent services. These processes include basic tasks, like parsing constraints and markup, and compositional tasks, such as disambiguation. These tasks consume and generate valuable metadata from and for third party users, for example, provenance information and quality scoring, and add relevant information for follow-on tasks, processes and services, such as MT post-editing, MT training and MT terminological enhancement.</p></div><div class="div4"
-<h5><a name="users_text_analytics" id="users_text_analytics"></a>1.3.1.6Text Analytics</h5><p>These types of users fulfil the role of providing services for automatic generation of metadata for improving localization, data integration or knowledge management workflows. This class of users comprises of developers and integrators of services that automate language technology tasks such as domain classification, named entity recognition and disambiguation, term extraction, language identification and others. Text analytics services generate data that contextualizes the raw content with more explicit information. This can be used to improve the output quality in machine translation systems, search result relevance in information retrieval systems, as well as management and integration of unstructured data in knowledge management systems.</p></div></div><div class="div3">
+<h5><a name="users_text_analytics" id="users_text_analytics"></a>1.3.1.6Text Analytics</h5><p>These types of users fulfil the role of providing services for automatic generation of metadata for improving localization, data integration or knowledge management workflows. This class of users comprises of developers and integrators of services that automate language technology tasks such as domain classification, named entity recognition and disambiguation, term extraction, language identification and others. Text analytics services generate data that contextualizes the raw content with more explicit information. This can be used to improve the output quality in machine translation systems, search result relevance in information retrieval systems, as well as management and integration of unstructured data in knowledge management systems.</p></div><div class="div4">
+<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers"></a>1.3.1.7Localization Workflow Managers</h5><p>This type of users is concerend with localization workflows in which content goes through certain steps: preparation for localization, start of the localization process by e.g. a conversion into a bitext format like <a title="" href="#xliff">[XLIFF]</a>, the actual localization by human translators or machine translation and other adaptations of content, and finally the integration of the localized content into the original format. That format is often based on XML or HTML; (Web) content management systems are widely used for content creation, and their integration with localization workflows is an important task for the workflow manager. For the integration of content creation and localization, metadata plays a crucial role. E.g. an ITS data category like <a href="#trans-datacat">translate</a> can trigger the extraction of localizable text. "<span class="quote">Metaata roundtripping</span>", that is the availibility of metadata both before and after the localization process is crucial for many tasks of the localization workflow manager. An example is metadata based quality control, with checks like "<span class="quote">Have all pieces of content set to <code>translate="no"</code> been left unchanged?</span>". Other pieces of metadata are relevant for proper internationalization during the localization workflow, e.g. the availibility of <a href="#directionality">Directionality</a> markup for adequate visualization of bidirectional text.</p></div></div><div class="div3">
<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="ways-to-use-its" id="ways-to-use-its"></a>1.3.2 Ways to Use ITS</h4><p>The ITS specification proposes several mechanisms for supporting
worldwide use and effective internationalization and localization of
content. We will sketch them below by looking at them from the
@@ -357,7 +358,7 @@
<strong class="hl-tag" style="color: #000096"></help></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-1.xml">examples/xml/EX-ways-to-use-its-1.xml</a>]</p></div><ul><li><p>A content author or information architect uses markup at the top
of the document to identify a particular type of element or
- context in which the content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e458" id="d0e458"></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="d0e480" id="d0e480"></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><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
@@ -373,7 +374,7 @@
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></help></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-2.xml">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="d0e483" id="d0e483"></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="d0e505" id="d0e505"></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><strong class="hl-tag" style="color: #000096"><help</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><head></strong>
@@ -387,7 +388,7 @@
<strong class="hl-tag" style="color: #000096"><cmd></strong>Build.bat<strong class="hl-tag" style="color: #000096"></cmd></strong>.<strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></help></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d0e504" id="d0e504"></a>Example 6: ITS rule file shared by different documents</div><p>The <code>rules</code> element contains several ITS rules that are common
+</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="d0e526" id="d0e526"></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><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>
@@ -395,7 +396,7 @@
<strong class="hl-tag" style="color: #000096"></its:rules></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-4.xml">examples/xml/EX-ways-to-use-its-4.xml</a>]</p></div><ul><li><p>A schema developer integrates ITS markup declarations in his
schema to allow users to indicate that specific parts of the
- content should not be translated.</p></li></ul><span class="editor-note">[Ed. note: Following schema example has to updated once we have final XSD schema for ITS 2.0]</span><div class="exampleOuter"><div class="exampleHeader"><a name="d0e535" id="d0e535"></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><span class="editor-note">[Ed. note: Following schema example has to updated once we have final XSD schema for ITS 2.0]</span><div class="exampleOuter"><div class="exampleHeader"><a name="d0e557" id="d0e557"></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><strong class="hl-tag" style="color: #000096"><xs:schema</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:xs</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2001/XMLSchema"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
@@ -706,7 +707,7 @@
information for internationalization and localization of XML schemas and
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 "implementation" 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="d0e1180" id="d0e1180"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys
+ 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 "implementation" 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="d0e1202" id="d0e1202"></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
@@ -735,7 +736,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="d0e1261" id="d0e1261"></a>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><text></strong>
+ graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1283" id="d0e1283"></a>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span>
<span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//p/img/@src"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -1014,41 +1015,41 @@
<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="selectors" id="selectors"></a>5.3 Query Language of Selectors</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="queryLanguage" id="queryLanguage"></a>5.3.1 Choosing Query Language</h4><p>
<a href="#rule-elements">Rule elements</a> have attributes which
- contain asbolute and relative selectors. Interpretation of these
- selectors depends on the actual query languge. The query language is set
+ contain absolute and relative selectors. Interpretation of these
+ selectors depends on the actual query language. The query language is set
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="d0e2134" id="d0e2134"></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="d0e2156" id="d0e2156"></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="d0e2145" id="d0e2145"></a>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an
+<h5><a name="d0e2167" id="d0e2167"></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">
AbsoluteLocationPath</a>s as described in <a href="#xpath">XPath 1.0</a>. This ensures that the selection is not
relative to a specific location. The resulting nodes <a href="#rfc-keywords">MUST</a> be either element or attribute
- nodes.</p><p>Context for evaluatiation of the XPath expression is as follows:</p><ul><li><p>Context node is set to <a href="http://www.w3.org/TR/xpath/#root-node">Root
+ nodes.</p><p>Context for evaluation of the XPath expression is as follows:</p><ul><li><p>Context node is set to <a href="http://www.w3.org/TR/xpath/#root-node">Root
Node</a>.</p></li><li><p>Both context position and context size are 1.</p></li><li><p>All variables defined by <code>param</code> elements are
bind.</p></li><li><p>All functions defined in the <a href="http://www.w3.org/TR/xpath/#corelib">XPath Core
Function Library</a> are available. It is an error for
an expression to include a call to any other function.</p></li><li><p>The set of namespace declarations are those in scope on the
element which has the attribute in which the expression
occurs. This includes the implicit declaration of the prefix
- <code>xml</code> required by the the <a href="#xmlns">XML Namespaces Recommendation</a>; the
+ <code>xml</code> required by 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="d0e2204" id="d0e2204"></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="d0e2226" id="d0e2226"></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><em class="hl-comment" style="color: silver"><!-- Definitions for TEI --></em>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:termRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//tei:term"</span> <span class="hl-attribute" style="color: #F5844C">term</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:tei</span>=<span class="hl-value" style="color: #993300">"http://www.tei-c.org/ns/1.0"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"></its:rules></strong>
-</pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d0e2222" id="d0e2222"></a>Example 17: XPath expressions without namespaces</div><p>The <code>term</code> element from DocBook V4.5 is in no
+</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="d0e2244" id="d0e2244"></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><em class="hl-comment" style="color: silver"><!-- Definitions for DocBook --></em>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:termRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//term"</span> <span class="hl-attribute" style="color: #F5844C">term</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"></its:rules></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-2.xml">examples/xml/EX-selection-global-2.xml</a>]</p></div></div><div class="div4">
-<h5><a name="d0e2237" id="d0e2237"></a>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords">MUST</a> use a
+<h5><a name="d0e2259" id="d0e2259"></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>,
@@ -1060,21 +1061,21 @@
<code>locQualityIssueCommentPointer</code>,
<code>locQualityIssueSeverityPointer</code>,
<code>locQualityIssueProfileRefPointer</code>.</p><span class="editor-note">[Ed. note: Make sure that previous list of ..Pointer attributes is
- complete once spec is stable.]</span><p>Context for evaluatiation of the XPath expression is same as for
+ complete once spec is stable.]</span><p>Context for evaluation of the XPath expression is same as for
absolute selector with the following changes:</p><ul><li><p>Nodes selected by the expression in the <code>selector</code>
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="d0e2311" id="d0e2311"></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="d0e2333" id="d0e2333"></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="d0e2322" id="d0e2322"></a>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be
+<h5><a name="d0e2344" id="d0e2344"></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="d0e2333" id="d0e2333"></a>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be
+<h5><a name="d0e2355" id="d0e2355"></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="d0e2347" id="d0e2347"></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="d0e2369" id="d0e2369"></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
@@ -1133,7 +1134,7 @@
<strong class="hl-tag" style="color: #000096"></its:rules></strong>
<strong class="hl-tag" style="color: #000096"></myFormatInfo></strong>
-</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="d0e2513" id="d0e2513"></a>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><myDoc></strong>
+</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="d0e2535" id="d0e2535"></a>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><myDoc></strong>
<strong class="hl-tag" style="color: #000096"><header></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:xlink</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xlink"</span> <span class="hl-attribute" style="color: #F5844C">xlink:href</span>=<span class="hl-value" style="color: #993300">"EX-link-external-rules-1.xml"</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -1147,7 +1148,7 @@
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></myDoc></strong>
</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="d0e2525" id="d0e2525"></a>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><myDoc></strong>
+ the following document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e2547" id="d0e2547"></a>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><myDoc></strong>
<strong class="hl-tag" style="color: #000096"><header></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//header"</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>
@@ -1185,7 +1186,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="d0e2611" id="d0e2611"></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="d0e2633" id="d0e2633"></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.
@@ -1327,7 +1328,7 @@
<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="datacategories-defaults-etc" id="datacategories-defaults-etc"></a>6.1 Position, Defaults, Inheritance and Overriding of Data Categories</h3><p>The following table summarizes for each data category which selection,
default value, and inheritance and overriding behavior applies.</p><ul><li><p id="def-default-values">
<em>Default values</em> apply if
- both local or global selection are absent. The default value for the
+ both local and global selection are absent. The default value for the
<a href="#trans-datacat">Translate</a> data category for
example mandates that elements are translatable, and attributes are
not translatable if there is no <code>translateRule</code> element and
@@ -1479,7 +1480,7 @@
<a href="#storagesize">Storage Size</a>
</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td><td>
<code>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="d0e3566" id="d0e3566"></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="d0e3588" id="d0e3588"></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
@@ -1558,9 +1559,10 @@
<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>The <strong class="hl-tag" style="color: #000096"><span</strong> <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>World Wide Web Consortium<strong class="hl-tag" style="color: #000096"></span></strong> is
- making the World Web Web worldwide!<strong class="hl-tag" style="color: #000096"></p></strong>
+ making the World Wide Web worldwide!<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-local-1.html">examples/html5/EX-translate-html5-local-1.html</a>]</p></div></div></div><div class="div2">
+<strong class="hl-tag" style="color: #000096"></html></strong>
+</pre></div><p>[Source file: <a href="examples/html5/EX-translate-html5-local-1.html">examples/html5/EX-translate-html5-local-1.html</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="locNote-datacat" id="locNote-datacat"></a>6.3 Localization Note</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="locNote-definition" id="locNote-definition"></a>6.3.1 Definition</h4><p>The <a href="#locNote-datacat">Localization Note</a> data category
is used to communicate notes to localizers about a particular item of
@@ -1590,10 +1592,10 @@
the value "description" or "alert".</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code>locNote</code> element that contains the note itself
and allows for <a href="#selection-local">local ITS
markup</a>.</p></li><li><p>A <code>locNotePointer</code> attribute that contains a <a href="#selectors">relative selector</a> pointing to
- a node that holds the localization note.</p></li><li><p>A <code>locNoteRef</code> attribute that contains a URI
+ a node that holds the localization note.</p></li><li><p>A <code>locNoteRef</code> attribute that contains a IRI
referring to the location of the localization note.</p></li><li><p>A <code>locNoteRefPointer</code> attribute that contains a
<a href="#selectors">relative selector</a>
- pointing to a node that holds the URI referring to the
+ pointing to a node that holds the IRI referring to the
location of the localization note.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locNote-element-1" id="EX-locNote-element-1"></a>Example 29: The <code>locNote</code> element</div><p>The <code>locNoteRule</code> element associates the content of the
<code>locNote</code> element with the message with the identifier
'DisableInfo' and flags it as important. This would also work if the
@@ -1630,7 +1632,7 @@
<strong class="hl-tag" style="color: #000096"></body></strong>
<strong class="hl-tag" style="color: #000096"></Res></strong></pre></div><p>[Source file: <a href="examples/xml/EX-locNotePointer-attribute-1.xml">examples/xml/EX-locNotePointer-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locNoteRef-attribute-1" id="EX-locNoteRef-attribute-1"></a>Example 31: The <code>locNoteRef</code> attribute</div><p>The <code>locNoteRule</code> element specifies that the message with the
identifier 'NotFound' has a corresponding explanation note in an
- external file. The URI for the exact location of the note is stored
+ external file. The IRI for the exact location of the note is stored
in the <code>locNoteRef</code> attribute.</p><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><myRes></strong>
<strong class="hl-tag" style="color: #000096"><head></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>
@@ -1641,8 +1643,8 @@
<strong class="hl-tag" style="color: #000096"><body></strong>
<strong class="hl-tag" style="color: #000096"><msg</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"NotFound"</span><strong class="hl-tag" style="color: #000096">></strong>Cannot find {0} on {1}.<strong class="hl-tag" style="color: #000096"></msg></strong>
<strong class="hl-tag" style="color: #000096"></body></strong>
-<strong class="hl-tag" style="color: #000096"></myRes></strong></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="d0e3963" id="d0e3963"></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><strong class="hl-tag" style="color: #000096"><dataFile></strong>
+<strong class="hl-tag" style="color: #000096"></myRes></strong></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="d0e3985" id="d0e3985"></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 IRI referring to the location of the note.</p><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><dataFile></strong>
<strong class="hl-tag" style="color: #000096"><prolog></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:locNoteRule</strong> <span class="hl-attribute" style="color: #F5844C">locNoteType</span>=<span class="hl-value" style="color: #993300">"description"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//data"</span>
@@ -1661,10 +1663,11 @@
available for the <a href="#locNote-datacat">Localization Note</a>
data category:</p><ul><li><p>One of the following:</p><ul><li><p>A <code>locNote</code> attribute that contains
the note itself.</p></li><li><p>A <code>locNoteRef</code> attribute that
- contains a URI referring to the location of the localization
+ contains a IRI 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="d0e4024" id="d0e4024"></a>Example 33: The <a href="#locNote-datacat">Localization Note</a> data
+ 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="d0e4046" id="d0e4046"></a>Example 33: The <a href="#locNote-datacat">Localization Note</a> data
category expressed locally</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><msgList</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">xml:space</span>=<span class="hl-value" style="color: #993300">"preserve"</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"><data</strong> <span class="hl-attribute" style="color: #F5844C">name</span>=<span class="hl-value" style="color: #993300">"LISTFILTERS_VARIANT"</span> <span class="hl-attribute" style="color: #F5844C">its:locNote</span>=<span class="hl-value" style="color: #993300">"Keep the leading space!"</span> <span class="hl-attribute" style="color: #F5844C">its:locNoteType</span>=<span class="hl-value" style="color: #993300">"alert"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><value></strong> Variant {0} = {1} ({2})<strong class="hl-tag" style="color: #000096"></value></strong>
@@ -1672,7 +1675,7 @@
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">its:locNote</span>=<span class="hl-value" style="color: #993300">"%1\$s is the original text's date in the format YYYY-MM-DD HH:MM always in GMT"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><value></strong>Translated from English content dated <strong class="hl-tag" style="color: #000096"><span</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"version-info"</span><strong class="hl-tag" style="color: #000096">></strong>%1\$s<strong class="hl-tag" style="color: #000096"></span></strong> GMT.<strong class="hl-tag" style="color: #000096"></value></strong>
<strong class="hl-tag" style="color: #000096"></data></strong>
-<strong class="hl-tag" style="color: #000096"></msgList></strong></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="d0e4037" id="d0e4037"></a>Example 34: The <a href="#locNote-datacat">Localization Note</a> data
+<strong class="hl-tag" style="color: #000096"></msgList></strong></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="d0e4059" id="d0e4059"></a>Example 34: The <a href="#locNote-datacat">Localization Note</a> data
category expressed locally in HTML5</div><div class="exampleInner"><pre><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>
@@ -1703,19 +1706,19 @@
"yes" or "no".</p></li><li><p>None or exactly one of the following:</p><ul><li><p>A <code>termInfoPointer</code> attribute that contains a
<a href="#selectors">relative selector</a>
pointing to a node that holds the terminology
- information.</p></li><li><p>A <code>termInfoRef</code> attribute that contains a URI
+ information.</p></li><li><p>A <code>termInfoRef</code> attribute that contains a IRI
referring to the resource providing information about the
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="d0e4135" id="d0e4135"></a>Example 35: Usage of the <code>termInfoPointer</code> attribute</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><text></strong>
+ pointing to a node that holds the IRI referring to the
+ location of the terminology information.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e4157" id="d0e4157"></a>Example 35: Usage of the <code>termInfoPointer</code> attribute</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:termRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//term"</span> <span class="hl-attribute" style="color: #F5844C">term</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">termInfoPointer</span>=<span class="hl-value" style="color: #993300">"id(@def)"</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"><p></strong>We may define <strong class="hl-tag" style="color: #000096"><term</strong> <span class="hl-attribute" style="color: #F5844C">def</span>=<span class="hl-value" style="color: #993300">"TDPV"</span><strong class="hl-tag" style="color: #000096">></strong>discoursal point of view<strong class="hl-tag" style="color: #000096"></term></strong> as
<strong class="hl-tag" style="color: #000096"><gloss</strong> <span class="hl-attribute" style="color: #F5844C">xml:id</span>=<span class="hl-value" style="color: #993300">"TDPV"</span><strong class="hl-tag" style="color: #000096">></strong>the relationship, expressed through discourse structure, between the
implied author or some other addresser, and the fiction.<strong class="hl-tag" style="color: #000096"></gloss></strong><strong class="hl-tag" style="color: #000096"></p></strong>
-<strong class="hl-tag" style="color: #000096"></text></strong></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="d0e4148" id="d0e4148"></a>Example 36: Usage of the <code>termInfoRef</code> attribute</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><text></strong>
+<strong class="hl-tag" style="color: #000096"></text></strong></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="d0e4170" id="d0e4170"></a>Example 36: Usage of the <code>termInfoRef</code> attribute</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:termRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//term[1]"</span> <span class="hl-attribute" style="color: #F5844C">term</span>=<span class="hl-value" style="color: #993300">"yes"</span>
<span class="hl-attribute" style="color: #F5844C">termInfoRef</span>=<span class="hl-value" style="color: #993300">"#TDPV"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -1725,7 +1728,7 @@
structure, between the implied author or some other addresser,
and the fiction.<strong class="hl-tag" style="color: #000096"></gloss></strong><strong class="hl-tag" style="color: #000096"></p></strong>
<strong class="hl-tag" style="color: #000096"></text></strong>
-</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="d0e4161" id="d0e4161"></a>Example 37: Usage of the <code>termInfoRefPointer</code> attribute</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><text></strong>
+</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="d0e4183" id="d0e4183"></a>Example 37: Usage of the <code>termInfoRefPointer</code> attribute</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:termRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//term"</span> <span class="hl-attribute" style="color: #F5844C">term</span>=<span class="hl-value" style="color: #993300">"yes"</span>
<span class="hl-attribute" style="color: #F5844C">termInfoRefPointer</span>=<span class="hl-value" style="color: #993300">"@target"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -1738,7 +1741,7 @@
</pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-3.xml">examples/xml/EX-terms-selector-3.xml</a>]</p></div><p id="terminology-local">LOCAL: The following local markup is available
for the <a href="#terminology">Terminology</a> data category:</p><ul><li><p>A <code>term</code> attribute with the value
"yes" or "no".</p></li><li><p>An optional <code>termInfoRef</code> attribute that
- contains a URI referring to the resource providing information about
+ contains a IRI referring to the resource providing information about
the term.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-terms-selector-4" id="EX-terms-selector-4"></a>Example 38: The <a href="#terminology">Terminology</a> data category
expressed locally</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><book</strong> <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">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"></head></strong>
@@ -1813,7 +1816,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="d0e4418" id="d0e4418"></a>Example 42: The <a href="#directionality">Directionality</a> data
+ "rlo".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e4440" id="d0e4440"></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><strong class="hl-tag" style="color: #000096"><text</strong> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en"</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"><body></strong>
@@ -1822,7 +1825,7 @@
W3C<strong class="hl-tag" style="color: #000096"></quote></strong>.<strong class="hl-tag" style="color: #000096"></par></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-dir-selector-3.xml">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d0e4439" id="d0e4439"></a>Example 43: The <a href="#directionality">Directionality</a> data
+</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="d0e4461" id="d0e4461"></a>Example 43: The <a href="#directionality">Directionality</a> data
category expressed locally in HTML5</div><div class="exampleInner"><pre><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>
@@ -1959,7 +1962,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="d0e4845" id="d0e4845"></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="d0e4867" id="d0e4867"></a>Example 47: Specifying elements within text with a <code>withinTextRule</code>
element</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:withinTextRule</strong> <span class="hl-attribute" style="color: #F5844C">withinText</span>=<span class="hl-value" style="color: #993300">"yes"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//b | //em | //i"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"></its:rules></strong>
@@ -1992,37 +1995,27 @@
<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="domain-implementation" id="domain-implementation"></a>6.9.2 Implementation</h4><p>The <a href="#domain">Domain</a> data category can be expressed
only with global rules. For elements, the data category information <a href="#def-inheritance">inherits</a> to the textual content of
the element, <em>including</em> child elements and attributes. There
- is no default.</p><p>The information provided by this data category is a comma-separated list of one or more values which is obtained by applying the following algorithm:</p><ol class="depth1"><li><p>Set the initial value of the resulting string as a empty string.</p></li><li><p>Get the list of nodes resulting of the evaluation of the <code>domainPointer</code> attribute.</p></li><li><p>For each node:
- </p><ol class="depth2"><li><p>If the node value contains a COMMA (U+002C):
- </p><ol class="depth3"><li><p>Split the node value into separate strings using the COMMA (U+002C) as separator.</p></li><li><p>For each string:
- </p><ol class="depth4"><li><p>Trim the leading and trailing white spaces of the string.</p></li><li><p>Check if there is a mapping for the string:
- </p><ol class="depth5"><li><p>If one is found:
- </p><ol class="depth1"><li><p>Add the corresponding value to the result string.</p></li></ol><p></p></li><li><p>Otherwise (if no mapping is found):
- </p><ol class="depth1"><li><p>Add the string to the result string.</p></li></ol><p></p></li></ol><p></p></li></ol><p></p></li></ol><p></p></li><li><p>If the node value does not contain a COMMA (U+002C):
- </p><ol class="depth3"><li><p>Trim the leading and trailing white spaces of the string.</p></li><li><p>Check if there is a mapping for the string:
- </p><ol class="depth4"><li><p>If one if found:
- </p><ol class="depth5"><li><p>Add the corresponding value to the result string.</p></li></ol><p></p></li><li><p>Otherwise (if no mapping is found):
- </p><ol class="depth5"><li><p>Add the string to the result string.</p></li></ol><p></p></li></ol><p></p></li></ol><p></p></li></ol><p></p></li><li><p>Return the resulting string.</p></li></ol><p id="domain-global">GLOBAL: The <code>domainRule</code> element contains
+ is no default.</p><p>The information provided by this data category is a comma-separated list of one or more values which is obtained by applying the following algorithm:</p><ul class="slist"><li><p>STEP 1: Set the initial value of the resulting string as a empty string.</p></li><li><p>STEP 2: Get the list of nodes resulting of the evaluation of the <code>domainPointer</code> attribute.</p></li><li><p>STEP 3: For each node:</p><ul class="slist"><li><p>STEP 3-1: If the node value contains a COMMA (U+002C):</p><ul class="slist"><li><p>STEP 3-1-1: Split the node value into separate strings using the COMMA (U+002C) as separator.</p></li><li><p>STEP 3-1-2: For each string:</p><ul class="slist"><li><p>STEP 3-1-2-1: Trim the leading and trailing white spaces of the string.</p></li><li><p>STEP 3-1-2-2: If the first character of the value is an APOSTROPHE (U+0027) or a QUOTATION MARK (U+0022): Remove it.</p></li><li><p>STEP 3-1-2-3: If the last character of the value is an APOSTROPHE (U+0027) or a QUOTATION ARK (U+0022): Remove it.</p></li><li><p>STEP 3-1-2-4: If the value is empty: Go to STEP 3-1-2.</p></li><li><p>STEP 3-1-2-5: Check if there is a mapping for the string (the mapping is case-insensitive):</p><ul class="slist"><li><p>STEP 3-1-2-5-1. If a mapping is found: Add the corresponding value to the result string.</p></li><li><p>STEP 3-1-2-5-2. Else (if no mapping is found): Add the string (in its original cases) to the result string.</p></li></ul></li></ul></li></ul></li><li><p>STEP 3-2: Else (if the node value does not contain a COMMA (U+002C)):</p><ul class="slist"><li><p>STEP 3-2-1: Trim the leading and trailing white spaces of the string.</p></li><li><p>STEP 3-2-2: If the first character of the value is an APOSTROPHE (U+0027) or a QUOTATION MARK (U+0022): Remove it.</p></li><li><p>STEP 3-2-3: If the last character of the value is an APOSTROPHE (U+0027) or a QUOTATION MARK (U+0022): Remove it.</p></li><li><p>STEP 3-2-4: If the value is empty: Go to STEP 3.</p></li><li><p>STEP 3-2-5: Check if there isa mapping for the string (the mapping is case-insensitive):</p><ul class="slist"><li><p>STEP 3-2-5-1: If a mapping is found: Add the corresponding value to the result string.</p></li><li><p>STEP 3-2-5-2: Else (if no mapping is found): Add the string (in its original cases) to the result string.</p></li></ul></li></ul></li></ul></li><li><p>STEP 4: Remove duplicated values from the resulting string.</p></li><li><p>STEP 5: Return the resulting string.</p></li></ul><p id="domain-global">GLOBAL: The <code>domainRule</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>domainPointer</code> attribute that contains a <a href="#selectors">relative selector</a> pointing to a node
that contains the domain information.</p></li><li><p>An optional <code>domainMapping</code> attribute that contains a
comma separated list of mappings between values in the content and
- consumer tool specific values. The left part of the pair is part of
- the source content and unique within the mapping. The right part of
+ consumer tool specific values. The left part of the pair corresponds to
+ the source content and is unique within the mapping and case-insensitive. The right part of
the mapping belongs to the consumer tool. Several left parts can map
to a single right part. The values in the left or the right part of
the mapping may contain spaces; in that case they <a href="#rfc-keywords">MUST</a> be delimited by quotation
- marks, that is pairs of APOSTROPHE (Unicode code point U+0027) or
- QUOTATION MARK (U+0023).</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Although the <code>domainMapping</code> attribute it is optional, its
+ marks, that is pairs of APOSTROPHE (U+0027) or
+ QUOTATION MARK (U+0022).</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>Although the <code>domainMapping</code> attribute it is optional, its
usage is recommended. Many commercial machine translation systems
use their own domain definitions; the <code>domainMapping</code>
attribute will foster interoperability between these definitions and
- metadata items like <code>DC.subject</code> in Web pages or other
+ metadata items like <code>keywords</code> or <code>dcterms.subject</code> in Web pages or other
types of content.</p><p>Values used in the <code>domainMapping</code> attribute are arbitrary
strings. In some consumer systems or existing content, the domain
- may be identified via an URI like
+ may be identified via an IRI like
<code>http://example.com/domains/automotive</code>. The
- <code>domainMapping</code> allows for using URIs too. For the
+ <code>domainMapping</code> allows for using IRIs too. For the
mapping, they are regarded as ordinary string values.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-domain-1" id="EX-domain-1"></a>Example 50: The <code>domainRule</code> element</div><p>The <code>domainRule</code> element expresses that the content of the
HTML <code>body</code> element is in the domain expressed by the
HTML <code>meta</code> element with the <code>name</code> attribute,
@@ -2082,7 +2075,7 @@
“PopulatedPlace” in the conceptual granularity level, or the central area of a particular city, e.g. City of London,
as interpreted in the entity granularity level. Linked data network, such as DBpedia, increasing interlink ontological
and named entity definitions for the same things as authored in different languages, offering a mechanism to
- locate translations from the source language description.</p><p>Two types of disambiguation are needed to identify:</p><span class="editor-note">[Ed. note: The previous sentence needs to be re-worded]</span><ul><li><p>Disambiguation type class, which describes the type class of the underlying concept or entity of the fragment.</p></li><li><p>Disambiguation, which describes the actual underlying external resource that conveys the intended meaning of the fragment.</p></li></ul><p>Text analysis engines, such as named entity recognizers, named entity, concept and word sense disambiguation
+ locate translations from the source language description.</p><p>Two types of disambiguation are possible:</p><ul><li><p>Disambiguation for target type class, which describes the type class of the underlying concept or entity of the fragment.</p></li><li><p>Disambiguation for target identity, which describes the actual underlying external resource that conveys the intended meaning of the fragment.</p></li></ul><p>Text analysis engines, such as named entity recognizers, named entity, concept and word sense disambiguation
components can offer an easy way to create this information. Content management tools can present and visualize
this information or use it to index their content. Machine translations systems may use it for training and translation
when dealing with proper names and edge cases.</p></div><div class="div3">
@@ -2091,21 +2084,22 @@
information applies to the textual content of the element. There is no
inheritance. The entity type follows inheritance rules.</p><span class="editor-note">[Ed. note: The two last sentences above seem contradictory.]</span><p id="disambiguation-global">GLOBAL: The <code>disambiguationRule</code>
element contains the following:</p><ul><li><p>A required <code>selector</code> attribute that contains an <a href="#selectors">absolute selector</a> which selects the
- nodes to which this rule applies.</p></li><li><p>Either:</p><ul><li><p>A <code>disambigSource</code> attribute that contains a string representing the disambiguation
- identifier collection source.</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code>disambigIdent</code> attribute that contains a string that represents the disambiguation
- identifier for the disambiguation target that is valid within the specified disambiguation source.</p></li><li><p>A <code>disambigIdentPointer</code> attribute that contains a <a href="#selectors">relative selector</a>
- pointing to a node that represents a unique identifier for the disambiguation target.</p></li></ul></li></ul></li><li><p>Or:</p><ul><li><p>Exactly one of the following:</p><ul><li><p>A <code>disambigIdentRef</code> attribute that contains an URI that represents a unique identifier
- for the disambiguation target.</p></li><li><p>A <code>disambigIdentRefPointer</code> attribute that contains a <a href="#selectors">relative selector</a>
- pointing to a node that holds a URI that represents a unique identifier for the disambiguation target.</p></li></ul></li></ul></li><li><p>None or exactly one of the following:</p><ul><li><p>A <code>disambigClassPointer</code> attribute that contains a <a href="#selectors">relative selector</a>
- pointing to a node specifying the entity type class behind the selector.</p></li><li><p>A <code>disambigClassRef</code> attribute that contains a URI, specifying the type class of the concept
- or entity behind the selector.</p></li><li><p>A <code>disambigClassRefPointer</code> attribute that contains a <a href="#selectors">relative selector</a>
- pointing to a node that holds a URI that specifies the entity type class behind the selector.</p></li></ul></li><li><p>An optional <code>disambigGranularity</code> attribute that contains a string, specifying the granularity
- level of the disambiguation. The value can be one of the following identifiers:
- <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code>.</p></li></ul><span class="editor-note">[Ed. note: Below will need a test case in the test suite.]</span><span class="editor-note">[Ed. note: Sentence below is awkward]</span><p id="disambiguation-use-cases">When using a disambiguation rule, the user <a href="#rfc2119">MUST</a> use one of the use
- cases for disambiguation: specifying the target type, or specifying the target identity.
- For the latter, the user <a href="#rfc2119">MUST</a> use only one of the two addressing modes:</p><ul><li><p>Using <code>disambigSource</code> and one of <code>disambigIdent</code> or <code>disambigIdentPointer</code> to specify the
+ nodes to which this rule applies.</p></li><li><p>An optional <code>disambigGranularity</code> attribute that contains a string, specifying the granularity
+ level of the disambiguation. The value can be one of the following identifiers:
+ <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code>.</p></li><li><p>At least one of the following:
+ <ul><li><p>To specify the target type class, exactly one of the following:<ul><li><p>A <code>disambigClassPointer</code> attribute that contains a <a href="#selectors">relative selector</a>
+ pointing to a node specifying the entity type class behind the selector.</p></li><li><p>A <code>disambigClassRef</code> attribute that contains a IRI, specifying the type class of the concept
+ or entity behind the selector.</p></li><li><p>A <code>disambigClassRefPointer</code> attribute that contains a <a href="#selectors">relative selector</a>
+ pointing to a node that holds a IRI that specifies the entity type class behind the selector.</p></li></ul></p></li><li><p>To specify the target identity, exactly one of the following:
+ <ul><li><p>When using addressing mode 1:</p><ul><li><p>A <code>disambigSource</code> attribute that contains a string representing the disambiguation
+ identifier collection source.</p></li><li><p>Exactly one of the following:</p><ul><li><p>A <code>disambigIdent</code> attribute that contains a string that represents the disambiguation
+ identifier for the disambiguation target that is valid within the specified disambiguation source.</p></li><li><p>A <code>disambigIdentPointer</code> attribute that contains a <a href="#selectors">relative selector</a>
+ pointing to a node that represents a unique identifier for the disambiguation target.</p></li></ul></li></ul></li><li><p>When using addressing mode 2:</p><ul><li><p>Exactly one of the following:</p><ul><li><p>A <code>disambigIdentRef</code> attribute that contains an IRI that represents a unique identifier
+ for the disambiguation target.</p></li><li><p>A <code>disambigIdentRefPointer</code> attribute that contains a <a href="#selectors">relative selector</a>
+ pointing to a node that holds a IRI that represents a unique identifier for the disambiguation target.</p></li></ul></li></ul></li></ul></p></li></ul></p></li></ul><span class="editor-note">[Ed. note: Below will need a test case in the test suite.]</span><p id="disambiguation-use-cases">When using a disambiguation rule specifying the target identity,
+ the user <a href="#rfc2119">MUST</a> use only one of the two addressing modes:</p><ul><li><p>Using <code>disambigSource</code> and one of <code>disambigIdent</code> or <code>disambigIdentPointer</code> to specify the
collection and the identifier itself.</p></li><li><p>Using one of <code>disambigIdentRef</code> or <code>disambigIdentRefPointer</code> using
- a URI for the disambiguation target.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-global-1" id="EX-disambiguation-global-1"></a>Example 52: Usage of <code>disambigClassRef</code>, <code>disambigGranularity</code>, <code>disambigIdentRef</code>,
+ a IRI for the disambiguation target.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-global-1" id="EX-disambiguation-global-1"></a>Example 52: Usage of <code>disambigClassRef</code>, <code>disambigGranularity</code>, <code>disambigIdentRef</code>,
<code>disambigSource</code> and <code>disambigIdent</code> for both entity and word sense disambiguation.</div><div class="exampleInner"><pre><span class="hl-directive" style="color: maroon"><?xml version="1.0"?></span>
<strong class="hl-tag" style="color: #000096"><text></strong>
<strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">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>
@@ -2125,14 +2119,18 @@
<strong class="hl-tag" style="color: #000096"></text></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-disambiguation-global-1.xml">examples/xml/EX-disambiguation-global-1.xml</a>]</p></div><p id="disambiguation-local">LOCAL: The following local markup is
available for the <a href="#Disambiguation">Disambiguation</a>
- data category:</p><ul><li><p>An optional <code>disambigClassRef</code> attribute that contains a URI, specifying the type class
- of the concept or entity behind the selector.</p></li><li><p>An optional <code>disambigGranularity</code> attribute that contains a string, specifying the
- granularity level of the disambiguation. The value can be one of the following identifiers: <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code></p></li><li><p>Either:</p><ul><li><p>A <code>disambigSource</code> attribute that contains a string representing the
- disambiguation identifier collection source.</p></li><li><p>A <code>disambigIdent</code> attribute that contains a string, representing the
- disambiguation identifier for the disambiguation target that is valid within the specified
- disambiguation source.</p></li></ul></li><li><p>Or:</p><ul><li><p>A <code>disambigIdentRef</code> attribute that contains a URI that represents a unique
- identifier for the disambiguation target.</p></li></ul></li></ul><p>The user <a href="#rfc2119">MUST</a> use only one of the two addressing modes for "target identity" disambiguation:</p><ul><li><p>Using <code>disambigSource</code> and <code>disambigIdent</code> to specify the collection
- and the identifier itself.</p></li><li><p>Using <code>disambigIdentRef</code> using a URI for the disambiguation target</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-html5-local-1" id="EX-disambiguation-html5-local-1"></a>Example 53: Local mixed usage of Usage of <code>disambigClassRef</code>, <code>disambigGranularity</code>,
+ data category:</p><ul><li><p>An optional <code>disambigGranularity</code> attribute that contains a string, specifying the
+ granularity level of the disambiguation. The value can be one of the following identifiers: <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code></p></li><li><p>At least one of the following:
+ <ul><li><p>To specify the target type class:
+ <ul><li><p>A <code>disambigClassRef</code> attribute that contains a IRI, specifying the type class
+ of the concept or entity behind the selector.</p></li></ul></p></li><li><p>To specify the target identity, exactly one of the following:
+ <ul><li><p>When using addressing mode 1:</p><ul><li><p>A <code>disambigSource</code> attribute that contains a string representing the
+ disambiguation identifier collection source.</p></li><li><p>A <code>disambigIdent</code> attribute that contains a string, representing the
+ disambiguation identifier for the disambiguation target that is valid within the specified
+ disambiguation source.</p></li></ul></li><li><p>When using addressing mode 2:</p><ul><li><p>A <code>disambigIdentRef</code> attribute that contains a IRI that represents a unique
+ identifier for the disambiguation target.</p></li></ul></li></ul></p></li></ul></p></li></ul><p>When specifying the target identity,
+ the user <a href="#rfc2119">MUST</a> use only one of the two addressing modes:</p><ul><li><p>Using <code>disambigSource</code> and <code>disambigIdent</code> to specify the collection
+ and the identifier itself.</p></li><li><p>Using <code>disambigIdentRef</code> using a IRI for the disambiguation target</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-html5-local-1" id="EX-disambiguation-html5-local-1"></a>Example 53: Local mixed usage of Usage of <code>disambigClassRef</code>, <code>disambigGranularity</code>,
and <code>disambigIdentRef</code> in HTML.</div><div class="exampleInner"><pre><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>
@@ -2152,7 +2150,7 @@
<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-disambiguation-html5-local-1.html">examples/html5/EX-disambiguation-html5-local-1.html</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>For referring to <code>disambigClassRef</code> values, implementors are encouraged to use an existing
repository of entity types as long as they satisfy their requirements. For example,
- the Named Entity Recognition and Disambiguation ontology (NERD): http://nerd.eurecom.fr/ontology</p><p>Furthermore, valid target types depend on the disambiguation granularity: types of entities are distinct
+ the Named Entity Recognition and Disambiguation ontology <a title="" href="#nerd">[NERD]</a>.</p><p>Furthermore, valid target types depend on the disambiguation granularity: types of entities are distinct
from types of lexical concepts or ontology concepts. While this distinction exists, the specification does not prescribe
a way of automatically inferring a disambiguation level from a target type.</p><p>When serializing the ITS mark-up in HTML5, the preferred way is to serialize in RDFa Lite or Microdata due
to the existing search and crawling infrastructure that is able to consume this kind of data.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-html5-rdfa" id="EX-disambiguation-html5-rdfa"></a>Example 54: Local mixed usage of <code>entityTypeSourceRef</code>, <code>enttiyTypeRef</code>, <code>disambigSourceRef</code>,
@@ -2161,15 +2159,16 @@
<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"><link</strong> <span class="hl-attribute" style="color: #F5844C">href</span>=<span class="hl-value" style="color: #993300">EX-disambiguation-html5-rdfa.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"><title></strong>Entity: Local Test<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> <span class="hl-attribute" style="color: #F5844C">prefix</span>=<span class="hl-value" style="color: #993300">"its: http://www.w3.org/2005/11/its"</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"><span</strong> <span class="hl-attribute" style="color: #F5844C">property</span>=<span class="hl-value" style="color: #993300">name</span> <span class="hl-attribute" style="color: #F5844C">resource</span>=<span class="hl-value" style="color: #993300">http:</span><strong class="hl-tag" style="color: #000096">//</strong>dbpedia.org/resource/Dublin typeof=http:/nerd.eurecom.fr/ontology#Place>Dublin<strong class="hl-tag" style="color: #000096"></span></strong> is
+ <strong class="hl-tag" style="color: #000096"><body></strong>
+ <strong class="hl-tag" style="color: #000096"><p></strong><strong class="hl-tag" style="color: #000096"><span</strong> <span class="hl-attribute" style="color: #F5844C">property</span>=<span class="hl-value" style="color: #993300">http:</span><strong class="hl-tag" style="color: #000096">//</strong>xmlns.com/foaf/0.1/name about=http://dbpedia.org/resource/Dublin typeof=http:/nerd.eurecom.fr/ontology#Place>Dublin<strong class="hl-tag" style="color: #000096"></span></strong> is
the capital of Ireland.<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-disambiguation-html5-rdfa.html">examples/html5/EX-disambiguation-html5-rdfa.html</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-disambiguation-html5-rdfa-companion-document" id="EX-disambiguation-html5-rdfa-companion-document"></a>Example 55: Companion document, having the mapping data for <a href="#EX-disambiguation-html5-rdfa">Example 54</a>.</div><div class="exampleInner"><pre><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:disambiguationRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//*[@typeof]"</span> <span class="hl-attribute" style="color: #F5844C">entityTypeRefPointer</span>=<span class="hl-value" style="color: #993300">"@typeof"</span><strong class="hl-tag" style="color: #000096">/></strong>
- <strong class="hl-tag" style="color: #000096"><its:disambiguationRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//*[@resource]"</span> <span class="hl-attribute" style="color: #F5844C">disambigIdentRefPointer</span>=<span class="hl-value" style="color: #993300">"@resource"</span><strong class="hl-tag" style="color: #000096">/></strong>
+ <strong class="hl-tag" style="color: #000096"><its:disambiguationRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//*[@about]"</span> <span class="hl-attribute" style="color: #F5844C">disambigIdentRefPointer</span>=<span class="hl-value" style="color: #993300">"@about"</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-disambiguation-html5-rdfa.xml">examples/html5/EX-disambiguation-html5-rdfa.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="LocaleFilter" id="LocaleFilter"></a>6.11 Locale Filter</h3><div class="div3">
@@ -2243,7 +2242,7 @@
attributes.</p><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>Exactly one of the following:</p><ul><li><p>A <code>translationProvenanceRecordsRef</code> attribute. Its
- value is a URI pointing to the
+ value is an IRI pointing to the
<code>translationProvenanceRecord</code> element containing the
list of translation provenance records related to the content selected via the <code>selector</code> attribute.</p></li><li><p>A <code>translationProvenanceRecordsRefPointer</code>
attribute that contains a <a href="#selectors">relative selector</a> pointing to a node with
@@ -2368,7 +2367,7 @@
attributes applied to the same span of text because the inner-most one
would override the others). A local <em>standoff markup</em> is
provided to allow such cases.</p><p>The following local markup is available for the <a href="#translation-agent-provenance">Translation Agent Provenance</a> data category:</p><ul><li><p>Either (inline markup): at least one of the following, with the same semantics as the corresponding attributes at the <code>transProvRule</code> element:</p><ul><li><p>Human translation provenance information specified by exactly a <code>transPerson</code> or a <code>transPersonRef</code> attribute.</p></li><li><p>Organizational translation provenance information specified by exactly a <code>transOrg</code> or a <code>transOrgRef</code> attribute.</p></li><li><p>Translation tool provenance related information specified by exactly a <code>transTool</code> or a <code>transToolRef</code> attribute.</p></li><li><p>Human translation revision provenance related information specified by exactly a <code>transRevPerson</code> or a <code>transRevPersonRef</code> attribute.</p></li><li><p>Organizational revision translation reated provenance information specified by exactly a <code>transRevOrg</code> or a <code>transRevOrgRef</code> attribute.</p></li><li><p>Translation tool revision provenance related information specified by exactly a <code>transRevTool</code> or a <code>transRevToolRef</code> attribute.</p></li><li><p>A reference to external, RDF-based provenance description specified by a <code>provRef</code> attribute.</p></li></ul></li><li><p>Or (standoff markup):</p><ul><li><p>A <code>translationProvenanceRecordsRef</code> attribute. Its value
- is a URI pointing to the <code>translationProvenanceRecords</code>
+ is a IRI pointing to the <code>translationProvenanceRecords</code>
element containing the list of provenance information related to this
content.</p></li><li><p>An element <code>translationProvenanceRecords</code> (or <code><span
its-translation-provenance-records></code> in HTML) which
@@ -2525,7 +2524,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 69: The <code>externalResourceRefRule</code> element</div><p>The <code>externalResourceRefRule</code> element expresses that the
+ to a node that provides the IRI of the external resource.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-externalresource-1" id="EX-externalresource-1"></a>Example 69: 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>
@@ -2790,9 +2789,11 @@
system to this scale. If needed, the original value can be
passed along using a custom namespace for XML, or a
<code>data-</code> attribute for HTML.</td></tr><tr><td>Profile Reference</td><td>A reference to a document describing the quality assessment
- model used for the issue.</td><td>A URI pointing to the reference document.</td><td>The use of resolvable URI is strongly recommended as it
- provides a way for human evaluators to learn more about the
- quality issues in use.</td></tr></tbody></table></div><div class="div3">
+ model used for the issue.</td><td>A IRI pointing to the reference document.</td><td>The use of resolvable IRI is strongly recommended as it
+ provides a way for human evaluators to learn more about the
+ quality issues in use.</td></tr><tr><td>Enabled</td><td>A flag indicating whether the issue is enabled or not.</td><td>A value <code>yes</code> or <code>no</code>, with the default value being <code>yes</code>.</td><td>This flag is used to activate or deactivate issues. There is no prescribed behavior associated with activated or deactivated issues.
+ One example of usage is a tool that allows the user to deactivate false positives so they are not displayed again each
+ time the document is re-checked.</td></tr></tbody></table></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="lqissue-implementation" id="lqissue-implementation"></a>6.18.2 Implementation</h4><p>The <a href="#lqissue">Localization Quality Issue</a> data category
can be expressed with global rules, or locally on individual elements.
For elements, the data category information <a href="#def-inheritance">inherits</a> to the textual content of
@@ -2800,7 +2801,7 @@
attributes.</p><p id="lqissue-global">GLOBAL: The <code>locQualityIssueRule</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>Exactly one of the following:</p><ul><li><p>A <code>locQualityIssuesRef</code> attribute. Its
- value is a URI pointing to the
+ value is a IRI pointing to the
<code>locQualityIssues</code> element containing the
list of issues related to this content.</p></li><li><p>A <code>locQualityIssuesRefPointer</code>
attribute that contains a <a href="#selectors">relative selector</a> pointing to a node with
@@ -2826,10 +2827,16 @@
that contains a <a href="#selectors">relative
selector</a> pointing to a node with the exact
same semantics as
- <code>locQualityIssueProfileRef</code>.</p></li></ul></li></ul><span class="editor-note">[Ed. note: Why does below say "do not apply to HMTL as local markup"? There is local markup for direction annotation in XML too.]</span><div class="note"><p class="prefix"><b>Note:</b></p><p>The attributes <code>locQualityIssuesRefPointer</code>,
+ <code>locQualityIssueProfileRef</code>.</p></li></ul></li><li><p>None or exactly one of the following:</p><ul><li><p>A <code>locQualityIssueEnabled</code> attribute that
+ implements the <a href="#lqissueDefs">enabled
+ information</a>.</p></li><li><p>A <code>locQualityIssueEnabledPointer</code> attribute
+ that contains a <a href="#selectors">relative
+ selector</a> pointing to a node with the exact
+ same semantics as <code>locQualityIssueEnabled</code>.</p></li></ul></li></ul><span class="editor-note">[Ed. note: Why does below say "do not apply to HMTL as local markup"? There is local markup for direction annotation in XML too.]</span><div class="note"><p class="prefix"><b>Note:</b></p><p>The attributes <code>locQualityIssuesRefPointer</code>,
<code>locQualityIssueTypePointer</code>,
<code>locQualityIssueCommentPointer</code>,
- <code>locQualityIssueSeverityPointer</code> and
+ <code>locQualityIssueSeverityPointer</code>,
+ <code>locQualityIssueSeverityEnabled</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 78: Annotating an issue in XML with <code>locQualityIssueRule</code>
element</div><p>The <code>locQualityIssueRule</code> element associates the issue
@@ -2891,8 +2898,9 @@
information</a>.</p></li><li><p>A <code>locQualityIssueComment</code> attribute
that implements the <a href="#lqissueDefs">comment information</a>.</p></li></ul></li><li><p>An optional <code>locQualityIssueSeverity</code>
attribute that implements the <a href="#lqissueDefs">severity information</a>.</p></li><li><p>An optional <code>locQualityIssueProfileRef</code>
- attribute that implements the <a href="#lqissueDefs">profile reference information</a>.</p></li></ul></li><li><p>Or (standoff markup):</p><ul><li><p>A <code>locQualityIssuesRef</code> attribute. Its value
- is a URI pointing to the <code>locQualityIssues</code>
+ attribute that implements the <a href="#lqissueDefs">profile reference information</a>.</p></li><li><p>An optional <code>locQualityIssueEnabled</code>
+ attribute that implements the <a href="#lqissueDefs">enabled information</a>.</p></li></ul></li><li><p>Or (standoff markup):</p><ul><li><p>A <code>locQualityIssuesRef</code> attribute. Its value
+ is a IRI pointing to the <code>locQualityIssues</code>
element containing the list of issues related to this
content.</p></li><li><p>An element <code>locQualityIssues</code> (or <code><span
loc-quality-issues></code> in HTML) which
@@ -2907,8 +2915,10 @@
<code>locQualityIssueSeverity</code> attribute that
implements the <a href="#lqissueDefs">severity
information</a>.</p></li><li><p>An optional
- <code>locQualityIssueProfileRef</code> attribute
- that implements the <a href="#lqissueDefs">profile reference information</a>.</p></li></ul></li></ul></li></ul></li></ul><p>Important: When the attributes <code>locQualityIssueType</code>,
+ <code>locQualityIssueProfileRef</code> attribute
+ that implements the <a href="#lqissueDefs">profile reference information</a>.</p></li><li><p>An optional
+ <code>locQualityIssueEnabled</code> attribute
+ that implements the <a href="#lqissueDefs">enabled information</a>.</p></li></ul></li></ul></li></ul></li></ul><p>Important: When the attributes <code>locQualityIssueType</code>,
<code>locQualityIssueComment</code>,
<code>locQualityIssueSeverity</code> and
<code>locQualityIssueProfileRef</code> (or their equivalent
@@ -3077,7 +3087,7 @@
selector</a> pointing to a node with the exact
same semantics as
<code>locQualityPrecisThreshold</code>.</p></li></ul></li><li><p>None or exactly one of the following:</p><ul><li><p>A <code>locQualityPrecisProfileRef</code> attribute. Its
- value is a URI pointing to the reference document
+ value is a IRI pointing to the reference document
describing the quality assessment model used for the
scoring.</p></li><li><p>A <code>locQualityPrecisProfileRefPointer</code>
attribute that contains a <a href="#selectors">relative selector</a> pointing to a node with the
@@ -3145,7 +3155,7 @@
value is a signed integer which indicates the lowest score or
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
+ Its value is a IRI 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 91: 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
@@ -3253,7 +3263,7 @@
<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-mtConfidence-global-2.xml">examples/xml/EX-mtConfidence-global-2.xml</a>]</p></div><p id="mtconfidence-local">LOCAL: the following local markup is
available for the <a href="#mtconfidence">MT Confidence</a> data
- category:</p><ul><li><p>An mtProducer attribute that contains a string identifying the
+ category:</p><span class="editor-note">[Ed. note: Missing the <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Oct/0384.html">local mtconfidencescore attribute</a>.]</span><ul><li><p>An mtProducer attribute that contains a string identifying the
Machine Translation Platform, e.g. “Bing Translator”, “Google
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
@@ -3756,9 +3766,7 @@
value even if the specific instance of the issue might be mapped
to another category.</p></li></ul>
</td></tr></tbody></table></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="informative-references" id="informative-references"></a>C References (Non-Normative)</h2><span class="editor-note">[Ed. note: Need to complete entry for provenance data model.]</span><dl><dt class="label"><a name="prov-dm" id="prov-dm"/>PROV-DM</dt><dd>Editors tbd.
- <a href="http://www.w3.org/TR/prov-dm/">Provenance data model</a>. Details to be completed.
- </dd><dt class="label"><a name="bidiarticle" id="bidiarticle"/>Bidi Article</dt><dd>Richard Ishida. <a href="http://www.w3.org/International/articles/inline-bidi-markup/"><cite>What you need to know about the bidi algorithm and inline
+<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="informative-references" id="informative-references"></a>C References (Non-Normative)</h2><span class="editor-note">[Ed. note: Need to complete entry for provenance data model.]</span><dl><dt class="label"><a name="bidiarticle" id="bidiarticle"/>Bidi Article</dt><dd>Richard Ishida. <a href="http://www.w3.org/International/articles/inline-bidi-markup/"><cite>What you need to know about the bidi algorithm and inline
markup</cite></a>. Article of the <a href="http://www.w3.org/International/">W3C Internationalization
Activity</a>, June 2005.</dd><dt class="label"><a name="checkmate" id="checkmate"/>CheckMate Quality Check</dt><dd>Okapi Project. <a href="http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration"><cite>CheckMate – Quality Check Configuration</cite></a>. Available at
<a href="http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration">http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration</a>.</dd><dt class="label"><a name="css2-1" id="css2-1"/>CSS 2.1</dt><dd> Bert Bos, Tantek Çelik, Ian Hickson Håkon
@@ -3784,14 +3792,18 @@
<a href="http://people.w3.org/rishida/localizable-dtds/"><cite>Requirements for Localizable DTD Design</cite></a>. Working
Draft 7 July 2003. Available at <a href="http://people.w3.org/rishida/localizable-dtds/">http://people.w3.org/rishida/localizable-dtds/</a>. </dd><dt class="label"><a name="css3-selectors" id="css3-selectors"/>CSS Selectors Level 3</dt><dd>Tantek Çelik, Elika J.
Etemad, Daniel Glazman, Ian Hickson, Peter Linss, John Williams <a href="http://www.w3.org/TR/css3-selectors/"><cite>Selectors Level
- 3</cite></a>. W3C Recommendation 29 September 2011. Available at <a href="http://www.w3.org/TR/css3-selectors/">http://www.w3.org/TR/css3-selectors/</a>.</dd><dt class="label"><a name="nvdl" id="nvdl"/>NVDL</dt><dd>Information technology -- Document Schema
+ 3</cite></a>. W3C Recommendation 29 September 2011. Available at <a href="http://www.w3.org/TR/css3-selectors/">http://www.w3.org/TR/css3-selectors/</a>.</dd><dt class="label"><a name="nerd" id="nerd"/>NERD</dt><dd>Named Entity Recognition and Disambiguation ontology (NERD)
+ available at: <a href="http://nerd.eurecom.fr/ontology">http://nerd.eurecom.fr/ontology</a>
+ </dd><dt class="label"><a name="nvdl" id="nvdl"/>NVDL</dt><dd>Information technology -- Document Schema
Definition Languages (DSDL) -- Part 4: <cite>Namespace-based Validation
Dispatching Language (NVDL)</cite>. International Organization for
Standardization (ISO) ISO/IEC 19757-4:2003.</dd><dt class="label"><a name="opendocument" id="opendocument"/>OpenDocument</dt><dd>Michael Brauer et al. <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office"><cite>OASIS Open Document Format for Office Applications
(OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>.
The latest version of <a href=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office"> OpenDocument</a> is available at
- https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="rfc3066" id="rfc3066"/>RFC 3066</dt><dd>Harald Alvestrand. <a href="http://www.ietf.org/rfc/rfc3066.txt"><cite>Tags for the
+ https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="prov-dm" id="prov-dm"/>PROV-DM</dt><dd>Editors tbd.
+ <a href="http://www.w3.org/TR/prov-dm/">Provenance data model</a>. Details to be completed.
+ </dd><dt class="label"><a name="rfc3066" id="rfc3066"/>RFC 3066</dt><dd>Harald Alvestrand. <a href="http://www.ietf.org/rfc/rfc3066.txt"><cite>Tags for the
Identification of Languages</cite></a>. RFC 3066, January 2001.
Available at <a href="http://www.ietf.org/rfc/rfc3066.txt">http://www.ietf.org/rfc/rfc3066.txt</a>.</dd><dt class="label"><a name="ruby-tr" id="ruby-tr"/>Ruby-TR</dt><dd>Marcin Sawicki (until 10 October, 1999),
Michel Suignard, Masayasu Ishikawa (石川 雅康), Martin Dürst, Tex Texin, <a href="http://www.w3.org/TR/ruby/"><cite>Ruby Annotation</cite></a>. W3C Recommendation 31 May 2001. Available at <a href="http://www.w3.org/TR/2001/REC-ruby-20010531/">
@@ -3807,7 +3819,7 @@
Available at <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/">
http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>. The latest version
of <a href="http://www.w3.org/TR/xhtml1/">XHTML 1.0</a> is available
- at http://www.w3.org/TR/xhtml1/.</dd><dt class="label"><a name="xml-i18n-bp" id="xml-i18n-bp"/>XML i18n BP</dt><dd>Yves Savourel, Jirka Kosek, Richard
+ at http://www.w3.org/TR/xhtml1/.</dd><dt class="label"><a name="xliff" id="xliff"/>XLIFF</dt><dd>XLIFF reference - tbd.</dd><dt class="label"><a name="xml-i18n-bp" id="xml-i18n-bp"/>XML i18n BP</dt><dd>Yves Savourel, Jirka Kosek, Richard
Ishida. <a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/"><cite>Best
Practices for XML Internationalization</cite></a>. Available at
<a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/">http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/</a>. The latest
@@ -3841,7 +3853,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="d0e9929" id="d0e9929"></a>Example 105: Testing constraints in ITS markup</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><schema</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://www.ascc.net/xml/schematron"</span><strong class="hl-tag" style="color: #000096">></strong>
+ validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e10049" id="d0e10049"></a>Example 105: Testing constraints in ITS markup</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><schema</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://www.ascc.net/xml/schematron"</span><strong class="hl-tag" style="color: #000096">></strong>
<em class="hl-comment" style="color: silver"><!-- Schematron document to test constraints for global and local ITS markup.
For ITS markup definitions, see http://www.w3.org/TR/its/ . --></em>
<strong class="hl-tag" style="color: #000096"><ns</strong> <span class="hl-attribute" style="color: #F5844C">prefix</span>=<span class="hl-value" style="color: #993300">"its"</span> <span class="hl-attribute" style="color: #F5844C">uri</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -3888,7 +3900,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="d0e9951" id="d0e9951"></a>Example 106: NVDL schema for ITS</div><div class="exampleInner"><pre><span class="hl-directive" style="color: maroon"><?xml version="1.0" encoding="UTF-8"?></span>
+ during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d0e10071" id="d0e10071"></a>Example 106: NVDL schema for ITS</div><div class="exampleInner"><pre><span class="hl-directive" style="color: maroon"><?xml version="1.0" encoding="UTF-8"?></span>
<strong class="hl-tag" style="color: #000096"><rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><namespace</strong> <span class="hl-attribute" style="color: #F5844C">ns</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"><validate</strong> <span class="hl-attribute" style="color: #F5844C">schema</span>=<span class="hl-value" style="color: #993300">"its20-elements.rng"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -3946,7 +3958,7 @@
</html></span></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-20121023">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-20121023/">ITS 2.0 Working Draft
- 23 October 2012</a>.</p><ul><li><p>Clarified usage of <a href="#domain">Domain</a> data category in HTML5 in response to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/56">issue-56</a>.</p></li></ul><p id="changelog-since-20120829">The following log records major changes that
+ 23 October 2012</a>.</p><ul><li><p>Clarified usage of <a href="#domain">Domain</a> data category in HTML5 in response to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/56">issue-56</a>.</p></li><li><p>Added the <a href="#lqissueDefs">enabled information</a> in <a class="section-ref" href="#lqissue">Section 6.18: Localization Quality Issue</a>.</p></li><li><p>Updated the <a href="#Disambiguation">Disambiguation</a> data category.</p></li><li><p>Fine tuned the algorithm to compute the result values of the <a href="#domain">Domain</a> data category.</p></li></ul><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 a first draft of <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
Received on Monday, 12 November 2012 15:04:53 UTC