- From: Felix Sasaki via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 06 Oct 2012 04:27:56 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory hutz:/tmp/cvs-serv13713/TR-version
Modified Files:
Overview.html
Log Message:
Added text anlaytics section from http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Oct/0065.html
Index: Overview.html
===================================================================
RCS file: /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -d -r1.53 -r1.54
--- Overview.html 4 Oct 2012 16:25:40 -0000 1.53
+++ Overview.html 6 Oct 2012 04:27:54 -0000 1.54
@@ -91,9 +91,9 @@
<div class="toc3">5.2.3 <a href="#selection-local">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d3e2411">XPath 1.0</a></div>
-<div class="toc3">5.3.3 <a href="#d3e2591">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d3e2627">Additional query languages</a></div>
+<div class="toc3">5.3.2 <a href="#d3e2416">XPath 1.0</a></div>
+<div class="toc3">5.3.3 <a href="#d3e2596">CSS Selectors</a></div>
+<div class="toc3">5.3.4 <a href="#d3e2632">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>
@@ -350,7 +350,8 @@
approach</a>). This global work, however, may fall to
information architects, rather than the content producers
themselves.</p></div><div class="div4">
-<h5><a name="users_machine-translation" id="users_machine-translation"></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><div class=div3">
+<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">
<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
@@ -375,7 +376,7 @@
</body>
</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-1.xml">examples/xml/EX-ways-to-use-its-1.xml</a>]</p></div><ul><li><p>A content author or information architect uses markup at the top
of the document to identify a particular type of element or
- context in which the content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e444" id="d3e444"></a>Example 4: Use of ITS by information architect</div><p>The <a class="itsmarkup" href="#translateRule">translateRule</a> 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="d3e449" id="d3e449"></a>Example 4: Use of ITS by information architect</div><p>The <a class="itsmarkup" href="#translateRule">translateRule</a> element is used in the header of the
document to indicate that none of the <code>path</code> or <code>cmd</code>
elements should be translated.</p><div class="exampleInner"><pre>
<help
@@ -393,7 +394,7 @@
Then from there, run batch file <cmd>Build.bat</cmd>.</p>
</body>
</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-2.xml">examples/xml/EX-ways-to-use-its-2.xml</a>]</p></div><ul><li><p>A processor may insert markup at the top of the document which
- links to ITS information outside of the document.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e469" id="d3e469"></a>Example 5: Use of ITS by processor</div><p>A <a class="itsmarkup" href="#rules">rules</a> 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="d3e474" id="d3e474"></a>Example 5: Use of ITS by processor</div><p>A <a class="itsmarkup" href="#rules">rules</a> element is inserted in the header of the document.
It has a XLink <a class="itsmarkup" href="#rules.attributes">href</a> attribute used to link to an <a href="#link-external-rules">ITS external rule</a>
document.</p><div class="exampleInner"><pre>
<help
@@ -409,7 +410,7 @@
<path>\Zebulon\Current Source\binary</path> directory.
Then from there, run batch file <cmd>Build.bat</cmd>.</p>
</body>
-</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e490" id="d3e490"></a>Example 6: ITS rule file shared by different documents</div><p>The <a class="itsmarkup" href="#rules">rules</a> element contains several ITS rules that are common
+</help></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-3.xml">examples/xml/EX-ways-to-use-its-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e495" id="d3e495"></a>Example 6: ITS rule file shared by different documents</div><p>The <a class="itsmarkup" href="#rules">rules</a> element contains several ITS rules that are common
to different documents. One of them is a <a class="itsmarkup" href="#translateRule">translateRule</a>
element that indicates that no <code>path</code> or <code>cmd</code> element
should be translated.</p><div class="exampleInner"><pre>
@@ -418,7 +419,7 @@
<its:translateRule selector="//path | //cmd" translate="no"/>
</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-ways-to-use-its-4.xml">examples/xml/EX-ways-to-use-its-4.xml</a>]</p></div><ul><li><p>A schema developer integrates ITS markup declarations in his
schema to allow users to indicate that specific parts of the
- content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e518" id="d3e518"></a>Example 7: An XSD schema with ITS declaration</div><p>The declarations for the <a class="itsmarkup" href="#att.local.no-ns.attribute.translate">translate</a> attribute
+ content should not be translated.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e523" id="d3e523"></a>Example 7: An XSD schema with ITS declaration</div><p>The declarations for the <a class="itsmarkup" href="#att.local.no-ns.attribute.translate">translate</a> attribute
is added to a group of common attributes <code>commonAtts</code>.
This allows to use the <a class="itsmarkup" href="#att.local.no-ns.attribute.translate">translate</a> attribute
within the documents like in <a href="#EX-ways-to-use-its-1">Example 3</a>.</p><div class="exampleInner"><pre>
@@ -762,7 +763,7 @@
documents.] The concept of a data category is independent of
its implementation in an XML environment (e.g. using an element or
attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description">Section 6: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "markup
- declarations" subsections in <a class="section-ref" href="#datacategory-description">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix E: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1182" id="d3e1182"></a>Example 13: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys
+ declarations" subsections in <a class="section-ref" href="#datacategory-description">Section 6: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas">Appendix E: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1187" id="d3e1187"></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 <a class="itsmarkup" href="#att.local.no-ns.attribute.translate">translate</a> attribute with
@@ -791,7 +792,7 @@
points. Thus in the following example, the translation information
specified via the <a class="itsmarkup" href="#translateRule">translateRule</a> 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="d3e1265" id="d3e1265"></a>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre>
+ graphic and change the words therein.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e1270" id="d3e1270"></a>Example 14: Selecting the text of a pointer to an external object</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1115,9 +1116,9 @@
by <a class="itsmarkup" href="#rules.attributes">queryLanguage</a> attribute on <a class="itsmarkup" href="#rules">rules</a> 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="d3e2411" id="d3e2411"></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="d3e2416" id="d3e2416"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in
<a class="itsmarkup" href="#rules.attributes">queryLanguage</a> attribute.</p><div class="div4">
-<h5><a name="d3e2422" id="d3e2422"></a>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an
+<h5><a name="d3e2427" id="d3e2427"></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">
@@ -1132,7 +1133,7 @@
occurs. This includes the implicit declaration of the prefix
<code>xml</code> required by the the <a href="#xmlns">XML Namespaces Recommendation</a>; the
default namespace (as declared by <code>xmlns</code>) is not
- part of this set.</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2482" id="d3e2482"></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="d3e2487" id="d3e2487"></a>Example 16: XPath expressions with namespaces</div><p>The <code>term</code> element from the TEI is in a namespace
<code>http://www.tei-c.org/ns/1.0</code>. </p><div class="exampleInner"><pre>
<!-- Definitions for TEI -->
@@ -1140,7 +1141,7 @@
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:tei="http://www.tei-c.org/ns/1.0" version="2.0">
<its:termRule selector="//tei:term" term="yes"/>
-</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2500" id="d3e2500"></a>Example 17: XPath expressions without namespaces</div><p>The <code>term</code> element from DocBook V4.5 is in no
+</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-1.xml">examples/xml/EX-selection-global-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2505" id="d3e2505"></a>Example 17: XPath expressions without namespaces</div><p>The <code>term</code> element from DocBook V4.5 is in no
namespace.</p><div class="exampleInner"><pre>
<!-- Definitions for DocBook -->
@@ -1148,7 +1149,7 @@
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
<its:termRule selector="//term" term="yes"/>
</its:rules></pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-2.xml">examples/xml/EX-selection-global-2.xml</a>]</p></div></div><div class="div4">
-<h5><a name="d3e2515" id="d3e2515"></a>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords">MUST</a> use a
+<h5><a name="d3e2520" id="d3e2520"></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: <a class="itsmarkup" href="#locNoteRule.attributes">locNotePointer</a>,
@@ -1165,16 +1166,16 @@
attribute form the current node list.</p></li><li><p>Context node comes from the current node list.</p></li><li><p>The context position comes from the position of the current
node in the current node list; the first position is 1.</p></li><li><p>The context size comes from the size of the current node
list.</p></li></ul></div></div><div class="div3">
-<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d3e2591" id="d3e2591"></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="d3e2596" id="d3e2596"></a>5.3.3 CSS Selectors</h4><p>CSS Selectors are identified by <code>css</code> value in
<a class="itsmarkup" href="#rules.attributes">queryLanguage</a> attribute.</p><div class="div4">
-<h5><a name="d3e2602" id="d3e2602"></a>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords">MUST</a> be
+<h5><a name="d3e2607" id="d3e2607"></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="d3e2613" id="d3e2613"></a>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords">MUST</a> be
+<h5><a name="d3e2618" id="d3e2618"></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 <a class="itsmarkup" href="#att.selector.attribute.selector">selector</a> 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="d3e2627" id="d3e2627"></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="d3e2632" id="d3e2632"></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
<a class="itsmarkup" href="#rules.attributes">queryLanguage</a>;</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
@@ -1234,7 +1235,7 @@
<its:termRule selector="//term" term="yes"/>
<its:withinTextRule withinText="yes" selector="//term | //b"/>
</its:rules>
-</myFormatInfo></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-1.xml">examples/xml/EX-link-external-rules-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2794" id="d3e2794"></a>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre>
+</myFormatInfo></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-1.xml">examples/xml/EX-link-external-rules-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2799" id="d3e2799"></a>Example 20: Document with a link to EX-link-external-rules-1.xml</div><div class="exampleInner"><pre>
<myDoc
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xlink="http://www.w3.org/1999/xlink" >
@@ -1249,7 +1250,7 @@
<p>A <term>Palouse horse</term> has a spotted coat.</p>
</body>
</myDoc></pre></div><p>[Source file: <a href="examples/xml/EX-link-external-rules-2.xml">examples/xml/EX-link-external-rules-2.xml</a>]</p></div><p>The result of processing the two documents above is the same as processing
- the following document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2806" id="d3e2806"></a>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre>
+ the following document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e2811" id="d3e2811"></a>Example 21: Document with identical rules as in the case of included rules</div><div class="exampleInner"><pre>
<myDoc
xmlns:its="http://www.w3.org/2005/11/its" >
<header>
@@ -1289,7 +1290,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="d3e2898" id="d3e2898"></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="d3e2903" id="d3e2903"></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.
@@ -1521,7 +1522,7 @@
<a href="#storagesize">Storage Size</a>
</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td><td>
<code>its:storageEncoding="UTF-8"</code>
- </td><td>None</td><td>tbd</td><td>tbd</td></tr></tbody></table><div class="exampleOuter"><div class="exampleHeader"><a name="d3e3764" id="d3e3764"></a>Example 24: 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="d3e3769" id="d3e3769"></a>Example 24: 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 <a class="itsmarkup" href="#locNote">locNote</a> is not translatable
@@ -1717,7 +1718,7 @@
<body>
<msg id="NotFound">Cannot find {0} on {1}.</msg>
</body>
-</myRes></pre></div><p>[Source file: <a href="examples/xml/EX-locNoteRef-attribute-1.xml">examples/xml/EX-locNoteRef-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4255" id="d3e4255"></a>Example 31: The <a class="itsmarkup" href="#locNoteRule.attributes">locNoteRefPointer</a> attribute</div><p>The <a class="itsmarkup" href="#locNoteRule.attributes">locNoteRefPointer</a> attribute contains a <a href="#selectors">relative selector</a> pointing to a node
+</myRes></pre></div><p>[Source file: <a href="examples/xml/EX-locNoteRef-attribute-1.xml">examples/xml/EX-locNoteRef-attribute-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4260" id="d3e4260"></a>Example 31: The <a class="itsmarkup" href="#locNoteRule.attributes">locNoteRefPointer</a> attribute</div><p>The <a class="itsmarkup" href="#locNoteRule.attributes">locNoteRefPointer</a> attribute contains a <a href="#selectors">relative selector</a> pointing to a node
that holds the URI referring to the location of the note.</p><div class="exampleInner"><pre>
<dataFile
xmlns:its="http://www.w3.org/2005/11/its" >
@@ -1741,7 +1742,7 @@
contains a URI referring to the location of the localization
note.</p></li></ul></li><li><p>An optional <a class="itsmarkup" href="#att.local.no-ns.attribute.locNoteType">locNoteType</a> attribute with the
value "description" or "alert". If the <a class="itsmarkup" href="#att.local.no-ns.attribute.locNoteType">locNoteType</a> 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="d3e4317" id="d3e4317"></a>Example 32: The <a href="#locNote-datacat">Localization Note</a> data
+ type of localization note will be assumed to be"description". </p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4322" id="d3e4322"></a>Example 32: The <a href="#locNote-datacat">Localization Note</a> data
category expressed locally</div><div class="exampleInner"><pre>
<msgList
xmlns:its="http://www.w3.org/2005/11/its" xml:space="preserve"
@@ -1755,7 +1756,7 @@
its:locNote="%1\$s is the original text's date in the format YYYY-MM-DD HH:MM always in GMT">
<value>Translated from English content dated <span id="version-info">%1\$s</span> GMT.</value>
</data>
-</msgList></pre></div><p>[Source file: <a href="examples/xml/EX-locNote-selector-2.xml">examples/xml/EX-locNote-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4330" id="d3e4330"></a>Example 33: The <a href="#locNote-datacat">Localization Note</a> data
+</msgList></pre></div><p>[Source file: <a href="examples/xml/EX-locNote-selector-2.xml">examples/xml/EX-locNote-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4335" id="d3e4335"></a>Example 33: The <a href="#locNote-datacat">Localization Note</a> data
category expressed locally in HTML5</div><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
<head>
@@ -1815,7 +1816,7 @@
term.</p></li><li><p>A <a class="itsmarkup" href="#termRule.attributes">termInfoRefPointer</a> 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="d3e4569" id="d3e4569"></a>Example 34: Usage of the <a class="itsmarkup" href="#termRule.attributes">termInfoPointer</a> attribute</div><div class="exampleInner"><pre>
+ location of the terminology information.</p></li></ul></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4574" id="d3e4574"></a>Example 34: Usage of the <a class="itsmarkup" href="#termRule.attributes">termInfoPointer</a> attribute</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1826,7 +1827,7 @@
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-1.xml">examples/xml/EX-terms-selector-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4582" id="d3e4582"></a>Example 35: Usage of the <a class="itsmarkup" href="#att.local.no-ns.attribute.termInfoRef">termInfoRef</a> attribute</div><div class="exampleInner"><pre>
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-1.xml">examples/xml/EX-terms-selector-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4587" id="d3e4587"></a>Example 35: Usage of the <a class="itsmarkup" href="#att.local.no-ns.attribute.termInfoRef">termInfoRef</a> attribute</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1837,7 +1838,7 @@
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-2.xml">examples/xml/EX-terms-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4595" id="d3e4595"></a>Example 36: Usage of the <a class="itsmarkup" href="#termRule.attributes">termInfoRefPointer</a> attribute</div><div class="exampleInner"><pre>
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-terms-selector-2.xml">examples/xml/EX-terms-selector-2.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4600" id="d3e4600"></a>Example 36: Usage of the <a class="itsmarkup" href="#termRule.attributes">termInfoRefPointer</a> attribute</div><div class="exampleInner"><pre>
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="2.0">
@@ -1942,7 +1943,7 @@
available for the <a href="#directionality">Directionality</a>
data category:</p><ul><li><p>A <a class="itsmarkup" href="#att.local.no-ns.attribute.dir">dir</a> attribute with the value
"ltr", "rtl", "lro" or
- "rlo".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4943" id="d3e4943"></a>Example 41: The <a href="#directionality">Directionality</a> data
+ "rlo".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4948" id="d3e4948"></a>Example 41: The <a href="#directionality">Directionality</a> data
category expressed locally</div><p>On the first <code>quote</code> element, the <code>its:dir="rtl"</code>
attribute indicates a right-to-left content.</p><div class="exampleInner"><pre>
<text
@@ -1953,7 +1954,7 @@
its:dir="rtl"><span dir="rtl">نشاط التدويل، W3C</span></quote>
means <quote>Internationalization Activity, W3C</quote>.</par>
</body>
-</text></pre></div><p>[Source file: <a href="examples/xml/EX-dir-selector-3.xml">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4967" id="d3e4967"></a>Example 42: The <a href="#directionality">Directionality</a> data
+</text></pre></div><p>[Source file: <a href="examples/xml/EX-dir-selector-3.xml">examples/xml/EX-dir-selector-3.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="d3e4972" id="d3e4972"></a>Example 42: The <a href="#directionality">Directionality</a> data
category expressed locally in HTML5</div><div class="exampleInner"><pre><!DOCTYPE html>
<html lang=en>
<head>
@@ -2120,7 +2121,7 @@
within text.</p><p id="withintext-global">GLOBAL: The <a class="itsmarkup" href="#withinTextRule">withinTextRule</a> element
contains the following:</p><ul><li><p>A required <a class="itsmarkup" href="#att.selector.attribute.selector">selector</a> 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 <a class="itsmarkup" href="#att.local.no-ns.attribute.withinText">withinText</a> attribute with the value
- "yes", "no" or "nested".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e5651" id="d3e5651"></a>Example 46: Specifying elements within text with a <a class="itsmarkup" href="#withinTextRule">withinTextRule</a>
+ "yes", "no" or "nested".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d3e5656" id="d3e5656"></a>Example 46: Specifying elements within text with a <a class="itsmarkup" href="#withinTextRule">withinTextRule</a>
element</div><div class="exampleInner"><pre>
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
@@ -4388,7 +4389,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="d3e11123" id="d3e11123"></a>Example 94: Testing constraints in ITS markup</div><div class="exampleInner"><pre>
+ validating some of these constraints.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e11128" id="d3e11128"></a>Example 94: Testing constraints in ITS markup</div><div class="exampleInner"><pre>
<sch:schema
xmlns:sch="http://www.ascc.net/xml/schematron" >
<!-- Schematron document to test constraints for global and local ITS markup.
@@ -4456,7 +4457,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="d3e11145" id="d3e11145"></a>Example 95: NVDL schema for ITS</div><div class="exampleInner"><pre><rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0">
+ during validation against this NVDL document/schema.</p><div class="exampleOuter"><div class="exampleHeader"><a name="d3e11150" id="d3e11150"></a>Example 95: NVDL schema for ITS</div><div class="exampleInner"><pre><rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0">
<namespace ns="http://www.w3.org/2005/11/its"> <validate
schema="its-elements.rng"/> </namespace> <namespace
ns="http://www.w3.org/2005/11/its" match="attributes"> <validate
Received on Saturday, 6 October 2012 04:27:58 UTC