- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 24 Jun 2013 17:37:36 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory gil:/tmp/cvs-serv2074/TR-version
Modified Files:
Overview.html
Log Message:
various edits, see http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jun/0089.html
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/06/23 17:50:44 1.92
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/06/24 17:37:36 1.93
@@ -32,7 +32,7 @@
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
processing based on the XML Localization Interchange File Format (XLIFF), as well as the
Natural Language Processing Interchange Format (NIF).</p><p>This document was published by the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
- Group</a> as a Proposed Recommendation Working Draft. Comments submitted against the <a href="http://www.w3.org/TR/2013/WD-its20-20130521/">Last Call specification</a> are consolidated in a <a href="http://tinyurl.com/its20-comments-handling">comment tracking document</a> (tbd:update link). All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <a href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</a> and created an <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</a> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
+ Group</a> as a Proposed Recommendation Working Draft. Comments submitted against the <a href="http://www.w3.org/TR/2013/WD-its20-20130521/">second Last Call specification</a> are consolidated in a <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html">comment tracking document</a>. All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <a href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</a> and created an <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</a> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
document to Recommendation status (see <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
maturity levels</a>).</p><p> The W3C Membership and other interested parties are invited to review the document and send comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
WD" in the subject line of your email. The <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/">archives
@@ -82,9 +82,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="#d0e2577">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2576">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2825">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2824">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>
@@ -344,7 +344,7 @@
<a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</a> was still under development. Once these discussions are
settled, the Ruby data category possibly will be reintroduced, in a subsequent
version of ITS.</p></li><li><p>The <a href="#directionality">Directionality</a> data category reflects directionality markup in <a title="HTML 4.01" href="#html4">[HTML 4.01]</a>. The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.</p></li></ul><p>
- <em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0.</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has an <a href="#its-tool-annotation">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="section-ref" href="#traceability">Section 2.6: Traceabilty</a> for details.</p></li></ul><p>
+ <em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0:</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has an <a href="#its-tool-annotation">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="section-ref" href="#traceability">Section 2.6: Traceabilty</a> for details.</p></li></ul><p>
<em>Mappings:</em> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <a title="" href="#nif-reference">[NIF]</a> and links to guidance about how to relate ITS 2.0 to XLIFF. See <a class="section-ref" href="#mapping-conversion">Section 2.7: Mapping and conversion</a> for details.</p><p>
<em>Changes to the conformance section</em>: The <a class="section-ref" href="#conformance">Section 4: Conformance</a> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed, and a conformance clause related to processing <a title="" href="#nif-reference">[NIF]</a> has been added. For <a title="HTML5" href="#html5">[HTML5]</a>, a dedicated conformance section has been created. Finally, a conformance clause related to Non-ITS elements and attributes has been added.</p></div><div class="div2">
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="extended-implementation-hints" id="extended-implementation-hints"></a>1.5 Extended implementation hints</h3><p id="unicode-normalization">As a general guidance, implementations of ITS 2.0 are encouraged to use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</a>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm">[Charmod Norm]</a>.</p></div></div><div class="div1">
@@ -357,7 +357,7 @@
context. The motivation for separating data category definitions from their
implementation is to enable different implementations with the following
characteristics:</p><ul><li><p>For various types of content (XML in general or <a href="#specific-HTML-support">HTML</a>).</p></li><li><p>For a single piece of content, e.g. a <code>p</code> element. This is the so-called <a href="#basic-concepts-selection-local">local approach</a>.</p></li><li><p>For several pieces of content in one document or even a set of documents. This is the
- so-called <a href="#basic-concepts-selection-global">global approach</a>.</p></li><li><p>For a complete markup vocabulary. This is done by adding <a href="#its-schemas">ITS markup declarations</a> to the schema for the vocabulary.</p></li></ul><p>ITS 2.0 provides the following data categories, using most of the existing ITS 1.0 data categories and adding new ones. Modifications of existing ITS 1.0 data categories are summarized in <a class="section-ref" href="#high-level-differences-between-1.0-and-2.0">Section 1.4: High-level differences between ITS 1.0 and ITS 2.0</a>.</p><ul><li><p><a href="#trans-datacat">Translate</a>: expresses information about whether
+ so-called <a href="#basic-concepts-selection-global">global approach</a>.</p></li><li><p>For a complete markup vocabulary. This is done by adding <a href="#its-schemas">ITS markup declarations</a> to the schema for the vocabulary.</p></li></ul><p>ITS 2.0 provides the following data categories:</p><ul><li><p><a href="#trans-datacat">Translate</a>: expresses information about whether
a selected piece of content is intended for translation or not.</p></li><li><p><a href="#locNote-datacat">Localization Note</a>: communicates notes to
localizers about a particular item of content.</p></li><li><p><a href="#terminology">Terminology</a>: marks terms and optionally
associates them with information, such as definitions or references to a term data
@@ -385,14 +385,14 @@
measurement of the localization quality of a document or an item in a document.</p></li><li><p><a href="#mtconfidence">MT Confidence</a>: indicates the confidence that MT
systems provide about their translation. </p></li><li><p><a href="#allowedchars">Allowed Characters</a>: specifies the characters that
are permitted in a given piece of content.</p></li><li><p><a href="#storagesize">Storage Size</a>: specifies the maximum storage size
- of a given piece of content.</p></li></ul></div><div class="div2">
+ of a given piece of content.</p></li></ul><p>Most of the existing ITS 1.0 data categories are included and new ones have been added. Modifications of existing ITS 1.0 data categories are summarized in <a class="section-ref" href="#high-level-differences-between-1.0-and-2.0">Section 1.4: High-level differences between ITS 1.0 and ITS 2.0</a>.</p></div><div class="div2">
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts-selection" id="basic-concepts-selection"></a>2.2 Selection</h3><p>Information (e.g. “translate this”) captured by an ITS data category always
pertains to one or more XML or HTML nodes, primarily element and attribute nodes. In a
sense, the relevant node(s) get “selected”. Selection may be explicit or implicit.
ITS distinguishes two mechanisms for explicit selection: (1) local and (2) global (via
<code class="its-elem-markup">rules</code>). Both local and global approaches can interact with each other, and
with additional ITS dimensions such as inheritance and defaults.</p><p>The mechanisms defined for ITS selection resemble those defined in <a title="Cascading Style Sheets,
 level 2 revision 1 CSS 2.1 Specification" href="#css2-1">[CSS 2.1]</a>. The local approach can be compared to the
- <code>style</code> attribute in HTML/XHTML, and the global approach is similar to the <code>style</code> element in HTML/XHTML.</p><ul><li><p>The local approach puts ITS markup in the relevant element of the host vocabulary
+ <code>style</code> attribute in HTML/XHTML, and the global approach is similar to the <code>style</code> element in HTML/XHTML:</p><ul><li><p>The local approach puts ITS markup in the relevant element of the host vocabulary
(e.g. the <code>author</code> element in DocBook)</p></li><li><p>The global <a href="#selection-global">rule-based approach</a> puts the ITS
markup in elements defined by ITS itself (namely the <code class="its-elem-markup">rules</code> element)</p></li></ul><p>ITS usually uses XPath in rules for identifying nodes although CSS Selectors and other query languages can in addition be implemented by applications.</p><p>ITS 2.0 can be used with XML documents (e.g. a DocBook article), HTML documents,
document schemas (e.g. an XML Schema document for a proprietary document format), or
@@ -560,7 +560,7 @@
<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="mapping-NIF" id="mapping-NIF"></a>2.7.1 ITS and RDF/NIF</h4><p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
representations) that contain ITS metadata to the RDF format based on <a title="" href="#nif-reference">[NIF]</a>. NIF is an RDF/OWL-based format that aims at interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion from <a href="#conversion-to-nif">ITS 2.0 to NIF</a> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content-related triples and relies on an <a href="http://www.w3.org/2005/11/its/rdf#">ITS RDF vocabulary</a>.</p><p>The back conversion from <a href="#nif-backconversion">NIF to ITS 2.0</a> is defined informatively. One motivation for the back conversion is a roundtrip workflow like: 1) conversion to NIF 2) in NIF representation detection of named entities using NLP tools 3) back conversion to HTML and generation of <a href="#textanalysis">Text Analysis</a> markup. The outcome are HTML documents with liked information, see <a href="#EX-text-analysis-html5-local-1">Example 53</a>.</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="mapping-XLIFF" id="mapping-XLIFF"></a>2.7.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="XLIFF Version 1.2" href="#xliff1.2">[XLIFF 1.2]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localization and translation workflows. <a title="XLIFF Version 2.0" href="#xliff2.0">[XLIFF 2.0]</a> is the successor of <a title="XLIFF Version 1.2" href="#xliff1.2">[XLIFF 1.2]</a> and under development. XLIFF has been widely implemented in various translation management systems, computer aided translation tools and in utilities for extracting translatable content from source documents and merging back the content in the target language..</p><p>The mapping between ITS and XLIFF therefore unpins several important ITS 2.0 usage scenarios <atitle="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl">[MLW US IMPL]</a>. These usage scenarios involve:</p><ul><li><p>the extraction of ITS metadata from a source language file into XLIFF</p></li><li><p>the addition of ITS metadata into an XLIFF file by translation tools</p></li><li><p>the mapping of ITS metadata in an XLIFF file into ITS metadata in the resulting target language files.</p></li></ul><p>ITS 2.0 has no normative dependency on XLIFF, however a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/">Internationalization Tag Set Interest Group</a>.</p></div></div><div class="div2">
-<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="implementing-its20" id="implementing-its20"></a>2.8 ITS 2.0 Implementations and Conformance</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer (see <a class="section-ref" href="#conformance">Section 4: Conformance</a>). The clauses are targeted at different types of implementers.</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> tell implementers how to process XML contet according to ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html5-its">Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> clarify how information needs to be made availble for given pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <a href="@@@@">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually is to be used. This is due to the fact that there is a wide variety of usage scenarios for ITS 2.0, and a wide variety of tools for working with ITS 2.0 is possible. Each of these tools may have its own way of using ITS 2.0 data categories (see <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl">[MLW US IMPL]</a> for more information).</p><span class="editor-note">[Ed. note: Add link to test suite]</span></div></div><div class="div1">
+<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="implementing-its20" id="implementing-its20"></a>2.8 ITS 2.0 Implementations and Conformance</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer (see <a class="section-ref" href="#conformance">Section 4: Conformance</a>). The clauses target different types of implementers:</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> tell implementers how to process XML content accordng to ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html5-its">Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> clarify how information needs to be made available for iven pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <a href="@@@@">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually is to be used. This is due to the fact that there is a wide variety of usage scenarios for ITS 2.0, and a wide variety of tools for working with ITS 2.0 is possible. Each of these tools may have its own way of using ITS 2.0 data categories (see <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl">[MLW US IMPL]</a> for more information).</p></div></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="notation-terminology" id="notation-terminology"></a>3 Notation and Terminology</h2><p>
<em>This section is normative.</em>
</p><div class="div2">
@@ -582,7 +582,7 @@
and localization of XML schemas and documents.] The concept of a data
category is independent of its implementation in an XML and HTML 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 8: 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 8: 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="d0e1611" id="d0e1611"></a>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat">Translate</a> data category conveys information as
+ <a class="section-ref" href="#datacategory-description">Section 8: 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="d0e1610" id="d0e1610"></a>Example 10: 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 is intended for translation or not.</p><p>The simplest formalization of this prose description on a schema language-independent
level is a <code class="its-attr-markup">translate</code> attribute with two possible values:
"yes" and "no". An implementation on a schema language-specific
@@ -722,7 +722,7 @@
categories</a> they implement, and for each <a href="#def-datacat">data
category</a>, which type of selection they support, whether they support processing
of XML. If the implementation provides the conversion to NIF (see conformance clause
- <a href="#its-conformance-2-4">2-4</a>), this <a href="#rfc-keywords">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="http://tbd:update">ITS 2.0 test suite</a>. All
+ <a href="#its-conformance-2-4">2-4</a>), this <a href="#rfc-keywords">MUST</a> be stated.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The above conformance clauses are directly reflected in the <a href="https://github.com/finnle/ITS-2.0-Testsuite/">ITS 2.0 test suite</a>. All
tests specify which data category is processed (clause <a href="#its-conformance-2-1">2-1</a>); they are relevant for
(clause <a href="#its-conformance-2-1-1">2-1-1</a>) global or local selection, or both; they require the processing of
defaults and precedence of selections (clauses <a href="#its-conformance-2-1-2">2-1-2</a> and
@@ -854,9 +854,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">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="d0e2577" id="d0e2577"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<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="d0e2576" id="d0e2576"></a>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2588" id="d0e2588"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an XPath expression
+<h5><a name="d0e2587" id="d0e2587"></a>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords">MUST</a> be an XPath expression
that starts with "<code>/</code>". That is, it <a href="#rfc-keywords">MUST</a> 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>.
@@ -901,14 +901,14 @@
be used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-and-attributes">CSS selectors have no ability to point to
attributes.</p></div><p>CSS Selectors are identified by the value <code>css</code> in the
<code class="its-attr-markup">queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d0e2802" id="d0e2802"></a>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as a
+<h5><a name="d0e2801" id="d0e2801"></a>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" 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="d0e2812" id="d0e2812"></a>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords">MUST</a> be interpreted as a
+<h5><a name="d0e2811" id="d0e2811"></a>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors">[Selectors Level 3]</a>. A selector is
not evaluated against the complete document tree but only against subtrees rooted at
nodes selected by the selector in the <code class="its-attr-markup">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="d0e2825" id="d0e2825"></a>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords">MAY</a> support additional query
+<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="d0e2824" id="d0e2824"></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 the processor <a href="#rfc-keywords">MUST</a> define:</p><ul><li><p>the identifier of the query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating an absolute selector to a collection of nodes;</p></li><li><p>rules for evaluating a relative selector to a collection of nodes.</p></li></ul><p>Because future versions of this specification are likely to define additional query
languages, the following query language identifiers are reserved: <code>xpath</code>,
<code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
@@ -1095,7 +1095,7 @@
<br/>This ontology is not a normative part of the ITS 2.0 specification and is being discussed in the <a href="http://www.w3.org/International/its/wiki/ITS-RDF_mapping">ITS Interest Group</a>.</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-HTML-whitespace-normalization" id="EX-HTML-whitespace-normalization"></a>Example 22: Example (see <a href="examples/html5/EX-HTML-whitespace-normalization.html">source code</a>) of an HTML document with whitespace character normalization as preparation for the conversion to NIF</div><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><html></strong><strong class="hl-tag" style="color: #000096"><body></strong><strong class="hl-tag" style="color: #000096"><h2</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Welcome to <strong class="hl-tag" style=color: #000096"><span</strong>
<span class="hl-attribute" style="color: #F5844C">its-ta-ident-ref</span>=<span class="hl-value" style="color: #993300">"http://dbpedia.org/resource/Dublin"</span> <span class="hl-attribute" style="color: #F5844C">its-within-text</span>=<span class="hl-value" style="color: #993300">"yes"</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>Dublin<strong class="hl-tag" style="color: #000096"></span></strong> in <strong class="hl-tag" style="color: #000096"><b</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">its-within-text</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Ireland<strong class="hl-tag" style="color: #000096"></b></strong>!<strong class="hl-tag" style="color: #000096"></h2></strong><strong class="hl-tag" style="color: #000096"></body></strong><strong class="hl-tag" style="color: #000096"></html></strong></pre></div></div><p id="its2nif-algorithm">The conversion algorithm to generate NIF consists of seven
- steps.</p><ul><li><p id="its2nif-algorithm-step1">STEP 1: Get an ordered list of all text nodes
+ steps:</p><ul><li><p id="its2nif-algorithm-step1">STEP 1: Get an ordered list of all text nodes
of the document.</p></li><li><p id="its2nif-algorithm-step2">STEP 2: Generate an XPath expression for each non-empty text node of all leaf elements and memorize them.</p></li><li><p id="its2nif-algorithm-step3">STEP 3: Get the text for each text node and make a tuple with the corresponding XPath expression (X,T). Since the text nodes have a certain order we
now have a list of ordered tuples ((x0,t0), (x1,t1), ..., (xn,tn)).</p></li><li><p id="its2nif-algorithm-step4">STEP 4 (optional): Serialize as XML or as RDF.
The list with the XPath-to-text mapping can also be kept in memory. Part of a
@@ -1219,7 +1219,7 @@
is to identify the tool most useful in further processes, in this case the MT
engine.</p></li></ul></div><p>The value of <code class="its-attr-markup">annotatorsRef</code> is a space-separated list of references where
each reference is composed of two parts: a data category identifier and an IRI. These
- two parts are separated by a <code>|</code> VERTICAL LINE (U+007C) character.</p><ul><li><p>The data category identifier <a href="#rfc2119">MUST</a> be one of the
+ two parts are separated by a <code>|</code> VERTICAL LINE (U+007C) character:</p><ul><li><p>The data category identifier <a href="#rfc2119">MUST</a> be one of the
identifiers specified in the <a href="#datacategories-overview">data category
overview table</a>.</p></li><li><p>The IRI indicates information about the processor used to generate the data category annotation.
No single means is specified for how this IRI has to be used to indicate processor
@@ -1374,7 +1374,7 @@
</p><div class="div2">
<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="datacategories-defaults-etc" id="datacategories-defaults-etc"></a>8.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 apply. It also provides data category
- identifiers used in <a class="section-ref" href="#its-tool-annotation">Section 5.8: ITS Tools Annotation</a>.</p><p>Foreign elements can be used only inside <code class="its-elem-markup">rules</code>. Foreign attributes can be used on any element defined in ITS.</p><ul><li><p id="def-default-values">
+ identifiers used in <a class="section-ref" href="#its-tool-annotation">Section 5.8: ITS Tools Annotation</a>:</p><ul><li><p id="def-default-values">
<em>Default values</em> apply if 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
@@ -1387,7 +1387,7 @@
translatable.</p></li><li><p id="def-overriding">For ITS data categories with inheritance, the
information conveyed by the data category can be overridden. For example, a local
<code class="its-attr-markup">translate</code> attribute overrides the <a href="#trans-datacat">Translate</a> information conveyed by a global
- <code class="its-elem-markup">translateRule</code>.</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p id="its-information_versus_content">An ITS application is free to decide what
+ <code class="its-elem-markup">translateRule</code>.</p></li></ul><p>Foreign elements can be used only inside <code class="its-elem-markup">rules</code>. Foreign attributes can be used on any element defined in ITS.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="its-information_versus_content">An ITS application is free to decide what
pieces of content it uses. For example:</p><ul><li><p><a href="#terminology">Terminology</a> information is added to a
<code>term</code> element. The information pertains only to the content of the
element, since there is no inheritance for <a href="#terminology">Terminology</a>. Nevertheless an ITS application can make use of the complete
@@ -1539,7 +1539,7 @@
<code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></div><p id="translate-global">GLOBAL: The <code class="its-elem-markup">translateRule</code> element contains the
following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors">absolute selector</a> that selects the nodes to which this
rule applies.</p></li><li><p>A required <code class="its-attr-markup">translate</code> attribute with the value
- "yes" or "no".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-1" id="EX-translate-selector-1"></a>Example 28: The <a href="#trans-datacat">Translate</a> data category expressed
+ "yes" or "no".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-1" id="EX-translate-selector-1"></a>Example 28: The <a href="#trans-datacat">Translate</a> data category expressed
globally</div><p>The <code class="its-elem-markup">translateRule</code> element specifies that the elements <code>code</code>
is not to be translated.</p><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:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//code"</span><strong class="hl-tag" style="color: #000096">/></strong>
@@ -2242,7 +2242,7 @@
each selected node a filter type and a list of extended language ranges conforming to
<a title="Tags for Identifying
 Languages" href="#bcp47">[BCP47]</a>.</p><p>The list is comma-separated and can include the wildcard extended language range
"*". The list can also be empty. Whitespace surrounding language ranges is
- ignored.</p><p>The type can take the values "include" or "exclude".</p><ul><li><p>A single wildcard "*" with a type "include" indicates that
+ ignored.</p><p>The type can take the values "include" or "exclude":</p><ul><li><p>A single wildcard "*" with a type "include" indicates that
the selected content applies to all locales.</p></li><li><p>A single wildcard "*" with a type "exclude" indicates that
the selected content applies to no locale.</p></li><li><p>An empty string with a type "include" indicates that the selected
content applies to no locale.</p></li><li><p>An empty string with a type "exclude" indicates that the selected
@@ -3371,11 +3371,8 @@
source text (“S”), target text (“T”) or both (“S or T”).</p><p>The values listed in the following table are allowed for <code class="its-attr-markup">locQualityIssueType</code>.
Ideally the values a tool implementing the data category produces for the attribute matches one
of the values provided in this table and are as semantically accurate as possible. Tools are encouraged to
- map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-tool-specific-mappings">The <a href="http://www.w3.org/International/its/ig/">ITS Interest Group</a> maintains an
- informative mapping of tools to localization quality issue types. <a href="http://www.w3.org/International/its/wiki/Tool_specific_mappings">The ITS IG
- Wiki</a> provides information on <a href="http://www.w3.org/International/its/wiki/Tool_specific_mappings#Update_of_this_page">how to update that list</a>. The purpose of these mappings is to document how tool internal information
- relates to the ITS 2.0 quality types. To foster interoperability, implementers are strongly encouraged not to rely on these mappings
- and to implement the ITS 2.0 quality types natively.</p></div><a name="lqissue-typevalues-table" id="lqissue-typevalues-table"></a><table border="1" width="100%"><thead><tr><td>Value</td><td>Description</td><td>Example</td><td>Scope</td><td>Notes</td></tr></thead><tbody><tr><td>
+ map their internal values to these types. The value <code>other</code> is reserved strictly for values that cannot be mapped.</p><div class="note"><p class="prefix"><b>Note:</b></p><p id="qa-issue-types-mappings">The <a href="http://www.w3.org/International/its/ig/">ITS Interest Group</a> maintains an
+ <a href="http://www.w3.org/International/its/wiki/Localization_quality_types_mappings">informative mapping</a> between ITS 2.0 quality issue types and other types used to specify quality issues: types produced by quality check tools, defined in other specifications etc. The purpose of these mappings is to document how tool internal information relates to the ITS 2.0 quality types. To foster interoperability, implementers are strongly encouraged not to rely on these mappings and to implement the ITS 2.0 quality types natively.</p></div><a name="lqissue-typevalues-table" id="lqissue-typevalues-table"></a><table border="1" width="100%"><thead><tr><td>Value</td><td>Description</td><td>Example</td><td>Scope</td><td>Notes</td></tr></thead><tbody><tr><td>
<code>terminology</code>
</td><td>An incorrect term or a term from the wrong domain was used or terms are used
inconsistently.</td><td>
@@ -5677,7 +5674,12 @@
At least one attribute must be specified on the provenanceRecord element.<strong class="hl-tag" style="color: #000096"></assert></strong>
<strong class="hl-tag" style="color: #000096"></rule></strong>
<strong class="hl-tag" style="color: #000096"></pattern></strong>
-<strong class="hl-tag" style="color: #000096"></schema></strong></pre></div><p>[Source file: <a href="schemas/its20.sch">schemas/its20.sch</a>]</p></div></div><div class="div1">
+<strong class="hl-tag" style="color: #000096"></schema></strong></pre></div><p>[Source file: <a href="schemas/its20.sch">schemas/its20.sch</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In order to make it easy to integrate ITS markup into schemas based on W3C XML Schema language
+ the following informative schemas are provided:</p><ul><li><p>
+ <a href="schemas/its20.xsd">its20.xsd</a> – base schema for ITS</p></li><li><p>
+ <a href="schemas/its20-types.xsd">its20.xsd</a> – schema defining datatypes used in ITS markup</p></li></ul><p>Please note that W3C XML Schema is less expressive then RELAX NG and some content models are more loose.
+ A document can validate against W3C XML Schema while it is not conforming to ITS specification
+ and it is not valid according to RELAX NG schema.</p></div></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>E References (Non-Normative)</h2><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
@@ -5747,7 +5749,7 @@
itsrdf:taIdentRef <http://dbpedia.org/resource/Ireland> .
<http://dbpedia.org/resource/Ireland>
rdf:type <http:/nerd.eurecom.fr/ontology#Country> .</pre></div></div><p id="nif2its-algorithm">The conversion algorithm to generate ITS out of NIF consists
- of two steps.</p><ul><li><p id="nif2its-algorithm-step1">STEP 1: NIF Web services accept two different types of input. It is possible to either send the extracted text (the object of the <code>nif:isString</code> property) directly or NIF RDF to the NLP tool, i.e. the text is sent as a <code>nif:Context</code> node and included as <code>nif:isString</code>. Either way, the output of the Web service will be a NIF representation.
+ of two steps:</p><ul><li><p id="nif2its-algorithm-step1">STEP 1: NIF Web services accept two different types of input. It is possible to either send the extracted text (the object of the <code>nif:isString</code> property) directly or NIF RDF to the NLP tool, i.e. the text is sent as a <code>nif:Context</code> node and included as <code>nif:isString</code>. Either way, the output of the Web service will be a NIF representation.
</p><p>Accepting text will be the minimal requirement of a NIF web service. Ideally, you would be able to send the <code>nif:Context</code> node with the isString as RDF directly, which has the advantage, that all other annotations can be used by the NLP tool:</p><div class="exampleInner"><div class="exampleOuter"><pre><strong class="hl-tag" style="color: #000096"><http:</strong>//example.com/exampledoc.html#char=0,29>
rdf:type nif:RFC5147String ;
rdf:type nif:Context ;
@@ -5955,15 +5957,15 @@
<code class="its-attr-markup">lineBreakType</code>?</td><td>
<code class="its-attr-markup">its-storage-size</code>, <code class="its-attr-markup">its-storage-encoding</code>?,
<code class="its-attr-markup">lits-line-break-type</code>?</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="revisionlog" id="revisionlog"></a>H Revision Log (Non-Normative)</h2><p id="changelog-since-20130521">The following log records major changes that have been made to this document since the <a href="http://www.w3.org/TR/2013/WD-its20-20130521/">ITS 2.0 Working Draft 21 May 2013</a>.</p><ol class="depth1"><li><p>Updated all text of the <a href="#html5-withintext-handling">HTML5 defaults for Element Within Text</a> and added example.
+<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-20130521">The following log records major changes that have been made to this document since the <a href="http://www.w3.org/TR/2013/WD-its20-20130521/">ITS 2.0 Working Draft 21 May 2013</a>:</p><ol class="depth1"><li><p>Added informative W3C XML Schema.</p></li><li><p>Updated all text of the <a href="#html5-withintext-handling">HTML5 defaults for Element Within Text</a> and added example.
See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/118">issue-118</a>
- and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/532">action-532</a>.</p></li><li><p>Added a paragraph about mime type submission to <a class="section-ref" href="#its-mime-type">Appendix B: Internationalization Tag Set (ITS) MIME Type</a>, see step 3 (first bullet point) at <a href="http://www.w3.org/2002/06/registering-mediatype#Planned">Register an Internet Media Type for a W3C Spec</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/251">action-251</a>.</p></li><li><p>Removed company names from various examples, see <a href="http://www.w3.org/Search/Mail/Public/search?type-index=public-multilingualweb-lt-commits&index-type=t&keywords=action-502&search=Search">CVS commits</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/502">action-502</a>.</p></li><li><p>Reformatting of various examples, see <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-commits/2013May/0066.htm">CVS commit mail</a> and further CVS commit mails with the same send time.</p></li><li><p>Edits related to <a title="" href="#nif-reference">[NIF]</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/125">issue-125</a>.</p></li><li><p>Edit related to <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/527">action-527</a>: put the sentence about foreign elements / attributes also in <a class="section-ref" href="#datacategories-defaults-etc">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>.</p></li><li><p>Copy editing of spec, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/422">action-422</a>.</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/126">issue-126</a> (Minor issue with quality types listing).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/127">issue-127</a> (Clarifyig HTML5 translate and global rules).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/128">issue-128</a> (Various editorial edits + conformance section fixes).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/129">issue-129</a> (sec1-2 editing (non-normative sec)).</p></li><li><p>Fixes about <a title="" href="#rfc2119">[RFC 2119]</a> statements, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/540">action-540</a>.</p></li><li><p>Various checks: spelling (using U.S. English), style, and grammar.</p></li></ol><p id="changelog-since-20130411">The following log records major changes that have been made to this document since the <a href="http://www.w3.org/TR/2013/WD-its20-20130411/">ITS 2.0 Working Draft 11 April 2013</a>.</p><ol class="depth1"><li><p>Added a reference to the <a href="http://www.w3.org/2005/11/its/rdf#">ITS RDF Ontology</a> and an <a href="#its-rdf-ontoogy-status">explanatory note</a> about its status to <a class="section-ref" href="#conversion-to-nif">Section 5.7: Conversion to NIF</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/514">action-514</a>.</p></li><li><p>Updated <a class="section-ref" href="#conversion-to-nif">Section 5.7: Conversion to NIF</a> to reflect <a href="http://www.w3.org/2013/05/08-mlw-lt-minutes#item04">MLW-LT May 2013 f2f discussion</a>: <code>nif:occursIn</code> has changed to <code>nif:sourceUrl</code>, and <code>nif:convertedFrom</code> replaces <code>itsrdf:xpath2nif</code>. See <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/517">action-517</a>.</p></li><li><p>Added <a href="#local-approach-not-applicable-to-attributes">a note</a> to <a class="section-ref" href="#basic-concepts-selection-local">Section 2.2.1: Local Approach</a> expressing that local selection does not apply to attributes,
- see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/98">issue-98</a>.</p></li><li><p>Added a <a href="#qa-issue-types-tool-specific-mappings">clarification</a> about the role of mappings from tools to quality issue types,
+ and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/532">action-532</a>.</p></li><li><p>Added a paragraph about mime type submission to <a class="section-ref" href="#its-mime-type">Appendix B: Internationalization Tag Set (ITS) MIME Type</a>, see step 3 (first bullet point) at <a href="http://www.w3.org/2002/06/registering-mediatype#Planned">Register an Internet Media Type for a W3C Spec</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/251">action-251</a>.</p></li><li><p>Removed company names from various examples, see <a href="http://www.w3.org/Search/Mail/Public/search?type-index=public-multilingualweb-lt-commits&index-type=t&keywords=action-502&search=Search">CVS commits</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/502">action-502</a>.</p></li><li><p>Reformatting of various examples, see <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-commits/2013May/0066.htm">CVS commit mail</a> and further CVS commit mails with the same send time.</p></li><li><p>Edits related to <a title="" href="#nif-reference">[NIF]</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/125">issue-125</a>.</p></li><li><p>Edit related to <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/527">action-527</a>: put the sentence about foreign elements / attributes also in <a class="section-ref" href="#datacategories-defaults-etc">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>.</p></li><li><p>Copy editing of spec, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/422">action-422</a>.</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/126">issue-126</a> (Minor issue with quality types listing).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/127">issue-127</a> (Clarifyig HTML5 translate and global rules).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/128">issue-128</a> (Various editorial edits + conformance section fixes).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/129">issue-129</a> (sec1-2 editing (non-normative sec)).</p></li><li><p>Fixes about <a title="" href="#rfc2119">[RFC 2119]</a> statements, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/540">action-540</a>.</p></li><li><p>Various checks: spelling (using U.S. English), style, grammar, use of ":" etc.</p></li><li><p>Added a non-normative XML Schema for ITS 2.0 to <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/546">action-546</a>.</p></li><li><p>Updated link to quality issue type mappings in <a class="section-ref" href="#lqissue-typevalues">Appendix C: Vlues for the Localization Quality Issue Type</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/543">action-543</a>.</p></li></ol><p id="changelog-since-20130411">The following log records major changes that have been made to this document since the <a href="http://www.w3.org/TR/2013/WD-its20-20130411/">ITS 2.0 Working Draft 11 April 2013</a>:</p><ol class="depth1"><li><p>Added a reference to the <a href="http://www.w3.org/2005/11/its/rdf#">ITS RDF Ontology</a> and an <a href="#its-rdf-ontology-status">explanatory note</a> about its status to <a class="section-ref" href="#conversion-to-nif">Section 5.7: Conversion to NIF</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/514">action-514</a>.</p></li><li><p>Updated <a class="section-ref" href="#conversion-to-nif">Section 5.7: Conversion to NIF</a> to reflect <a href="http://www.w3.org/2013/05/08-mlw-lt-minutes#item04">MLW-LT May 2013 f2f discussion</a>: <code>nif:occursIn</code> has changed o <code>nif:sourceUrl</code>, and <code>nif:convertedFrom</code> replaces <code>itsrdf:xpath2nif</code>. See <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/517">action-517</a>.</p></li><li><p>Added <a href="#local-approach-not-applicable-to-attributes">a note</a> to <a class="section-ref" href="#basic-concepts-selection-local">Section 2.2.1: Local Approach</a> expressing that local selection does not apply to attributes,
+ see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/98">issue-98</a>.</p></li><li><p>Added a <a href="#qa-issue-types-mappings">clarification</a> about the role of mappings from tools to quality issue types,
see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/493">action-493</a>.</p></li><li><p>Updated the definition of the regular expression to use in the <a class="section-ref" href="#allowedchars">Section 8.19: Allowed Characters</a> data category,
see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/67">issue-67</a>.</p></li><li><p>Updated explanation of usage in <a title="HTML5" href="#html5">[HTML5]</a> to reflect discussion on <a title="HTML5" href="#html5">[HTML5]</a> defaults, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/89">issue-89</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/97">issue-97</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/118">issue-118</a>.</p></li><li><p>Clarified <a href="#provenance-records-in-html5-constraint">provenance</a> and
<a href="#loc-quality-issues-in-html5-constraint">localization quality issue</a> standoff
constraints for HTML5, see related <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013May/0032.html">mail thread</a>.</p></li><li><p>Edits related to HTML defaults for <a href="#elements-within-text">Elements Within Text</a> and <a href="#language-information">Language Information</a>, see <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013May/0010.html">mail thread</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/118">issue-118</a>.</p></li><li><p>Added section about ITS 2.0 and XLIFF.</p></li><li><p>Added a <a href="#text-analyis-serializations">note on serializations</a> of the <a href="#textanalysis">Text Analysis</a> data category.</p></li><li><p>Added <a href="#its-conformance-2-5">conformance clause 2-5</a> about non ITS elements and attributes and a <a href="#foreign-elements">related paragraph</a> to <a class="section-ref" href="#its-schemas">Appendix D: Schemas for ITS</a>, see <a href="https://www.w3.or/International/multilingualweb/lt/track/actions/527">action-527</a>.</p></li><li><p>Made <code class="its-attr-markup">annotatorsRef</code> only needed for <a href="#terminology">Terminology</a>, <a href="#textanalysis">Text Analysis</a> and <a href="#mtconfidence">MT Confidence</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/71">issue-71</a>.</p></li></ol><p id="changelog-since-20121206">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-20121206/">ITS 2.0 Working Draft 6 December 2012</a>.</p><ol class="depth1"><li><p>Changed usage of <code>quote</code> element in example <a href="#EX-dir-html5-local-1">Example 45</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/88">issue-88</a></p></li><li><p>Added optional version attribute to standoff elements, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/122">issue-122</a>.</p></li><li><p>Fixed <a href="#EX-its-tool-annotation-1">Example 23</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/58">issue-58</a>.</p></li><li><p>Clarified text in <a class="section-ref" href="#basic-concepts-addingpointing">Section 2.4: Adding Information or Pointing to Existing Information</a> and
+ made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121206/">ITS 2.0 Working Draft 6 December 2012</a>:</p><ol class="depth1"><li><p>Changed usage of <code>quote</code> element in example <a href="#EX-dir-html5-local-1">Example 45</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/88">issue-88</a></p></li><li><p>Added optional version attribute to standoff elements, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/122">issue-122</a>.</p></li><li><p>Fixed <a href="#EX-its-tool-annotation-1">Example 23</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/58">issue-58</a>.</p></li><li><p>Clarified text in <a class="section-ref" href="#basic-concepts-addingpointing">Section 2.4: Adding Information or Pointing to Existing Information</a> and
<a class="section-ref" href="#selection-global">Section 5.2.1: Global, Rule-based Selection</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/59">issue-59</a>.</p></li><li><p>Clarified the definition of <code>uncategorized</code> in <a class="section-ref" href="#lqissue-typevalues">Appendix C: Values for the Localization Quality Issue Type</a>, and (see <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2012Dec/0031.html">related mail</a>) used "<span class="quote">value</span>" consistently instead of
"<span class="quote">category</span>" to refer to the value types. See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/60">issue-60</a>.</p></li><li><p>Clarified definition of <a href="#lqissue-global">Localization Quality
Issue</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/62">issue-62</a>.</p></li><li><p>Removed <code>disambigClassPointer</code> attribute, see <a class="section-ref" href="#textanalysis-implementation">Section 8.9.2: Implementation</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/64">issue-64</a>.</p></li><li><p>Clarified that <code class="its-attr-markup">provenanceRecordsRefPointer</code> cannot be used in HTML, see
@@ -5983,7 +5985,7 @@
11669 and Structure specifications. See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/83">issue-83</a>.</p></li><li><p>Renamed Disambiguation data category to Text Analysis. Removed <code>disambigGranularity</code> attribute. All other attributes of Disambiguation were renamed to have the prefix "ta". Rewrote <a href="#textanalysis">defining section</a>. See for all changes <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/68">issue-68</a>.</p></li><li><p>Added non-normative reference to ITS 1.0 <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10">[ITS 1.0]</a>.</p></li><li><p>Updated <a class="section-ref" href="#conversion-to-nif">Section 5.7: Conversion to NIF</a> and <a class="section-ref" href="#nif-backconversion">Appendix F: Conversion NIF2ITS</a> with new NIF URI (see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/460">action-460</a>), fragment identifiers (see <a href="https://wwww3.org/International/multilingualweb/lt/track/actions/458">action-458</a>) and ITS ontology predicates. Changes to be confirmed, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/481">action-481</a>. See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/73">issue-73</a>.</p></li><li><p>Updated <a class="section-ref" href="#storagesize">Section 8.20: Storage Size</a> to clarify the usage of the encoding and the line break type.
See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/106">issue-106</a>
and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/107">issue-107</a>.</p></li><li><p>Removed note in <a class="section-ref" href="#basic-concepts-selection-global">Section 2.2.2: Global Approach</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/117">issue-117</a>.</p></li></ol><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><ol class="depth1"><li><p>Clarified usage of <a href="#domain">Domain</a> data category in HTML in
+ 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><ol class="depth1"><li><p>Clarified usage of <a href="#domain">Domain</a> data category in HTML 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 8.16: Localization Quality Issue</a>.</p></li><li><p>Updated the Disambiguation 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><li><p>Fix on <a href="#EX-locQualityIssue-html5-local-2">Example 77</a>:
<code>id</code> attribute of <code>script</code> element now the same as of containing
XML.</p></li><li><p>NIF example fix - see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/284">action-284</a>.</p></li><li><p>Added a note to mark CSS selectors as feature at risk, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/272">action-272</a>.</p></li><li><p>Defined in <a class="section-ref" href="#xpath-relative-selector">Section 5.3.2.2: Relative selector</a> that an XPath
@@ -6012,23 +6014,23 @@
<em>whitespace</em> to respond to and clarify <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Nov/0208.html">points raised by Daniel Naber</a>.</p></li><li><p>Added <a class="section-ref" href="#list-of-elements-and-attributes">Appendix G: List of ITS 2.0 Global Elements and Local Attributes</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/321">action-321</a>.</p></li><li><p>Renaming attribute for <a class="section-ref" href="#its-tool-annotation">Section 5.8: ITS Tools Annotation</a>. See <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Dec/0006.html">change description</a>.</p></li><li><p>Changes related to <code class="its-attr-markup">annotatorsRef</code>, see <a href="http://www.w3.org/2012/12/03-mlw-lt-minutes.html#item08">Working Group call
2012-12-03</a> discussion.</p></li><li><p>Changes related to <code>disambigGranularity</code> attribute, see <a href="http://www.w3.org/2012/12/03-mlw-lt-minutes.html#item04">Working Group call
2012-12-03</a> discussion and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/359">action-359</a>.</p></li></ol><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="#provenance">Section 8.11: Provenance</a></p></li><li><p>Added <a class="section-ref" href="#html5-markup">Section 6: Using ITS Markup in HTML</a>.</p></li><li><p>Removed inline markup declarations.</p></li><li><p>Addition of a <code class="its-attr-markup">locQualityRatingVote</code> attribute and a
+ 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="#provenance">Section 8.11: Provenance</a></p></li><li><p>Added <a class="section-ref" href="#html5-markup">Section 6: Using ITS Markup in HTML</a>.</p></li><li><p>Removed inline markup declarations.</p></li><li><p>Addition of a <code class="its-attr-markup">locQualityRatingVote</code> attribute and a
<code class="its-attr-markup">locQualityRatingVotePointer</code> attribute to <a class="section-ref" href="#lqrating">Section 8.17: Localization Quality Rating</a>.</p></li><li><p>A <a href="#its-information_versus_content">clarification</a> of ITS data
- category information and processing of content in <a class="section-ref" href="#datacategories-defaults-etc">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>.</p></li><li><p>Added <a class="section-ref" href="#allowedchars">Section 8.19: Allowed Characters</a>.</p></li><li><p>Added <a class="section-ref" href="#storagesize">Section 8.20: Storage Size</a>.</p></li><li><p>Added <a class="section-ref" href="#mtconfidence">Section 8.18: MT Confidence</a>.</p></li><li><p>Added <a href="#qa-issue-types-tool-specific-mappings">a note</a> about
+ category information and processing of content in <a class="section-ref" href="#datacategories-defaults-etc">Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories</a>.</p></li><li><p>Added <a class="section-ref" href="#allowedchars">Section 8.19: Allowed Characters</a>.</p></li><li><p>Added <a class="section-ref" href="#storagesize">Section 8.20: Storage Size</a>.</p></li><li><p>Added <a class="section-ref" href="#mtconfidence">Section 8.18: MT Confidence</a>.</p></li><li><p>Added <a href="#qa-issue-types-mappings">a note</a> about
informative mappings of <a href="#lqissue-typevalues">Values for the Localization
Quality Issue Type</a> to the <a href="http://www.w3.org/International/its/wiki/Tool_specific_mappings">ITS IG
wiki</a>.</p></li><li><p>Added a <a href="#its-conformance-2-3">conformance clause</a> about HTML versus
XML processing.</p></li><li><p>Added links to XML and HTML examples to the <a href="#datacategories-overview">data category overview table</a>.</p></li><li><p>Added new kind of user to the introduction.</p></li><li><p>Added the algorithm to obtain the value of the <a href="#domain">Domain</a>
data category.</p></li><li><p>Updated the <a href="#allowedchars">Allowed Characters</a> data category for
the empty string case and the way to define "allow any characters"..</p></li><li><p>Added sections related to NIF conversion (<a class="section-ref" href="#conversion-to-nif">Section 5.7: Conversion to NIF</a> and <a class="section-ref" href="#nif-backconversion">Appendix F: Conversion NIF2ITS</a>) and a related conformance clause <a href="#its-conformance-2-4">2-4</a>.</p></li></ol><p id="changelog-since-20120731">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-20120731/">ITS 2.0 Working Draft 31 July 2012</a>.</p><ol class="depth1"><li><p>Added Disambiguation data category.</p></li><li><p>Added <a class="section-ref" href="#preservespace">Section 8.15: Preserve Space</a>.</p></li><li><p>Added <a class="section-ref" href="#idvalue">Section 8.14: ID Value</a>.</p></li><li><p>Added support for different query language and reworked whole XPath and CSS
+ made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20120731/">ITS 2.0 Working Draft 31 July 2012</a>:</p><ol class="depth1"><li><p>Added Disambiguation data category.</p></li><li><p>Added <a class="section-ref" href="#preservespace">Section 8.15: Preserve Space</a>.</p></li><li><p>Added <a class="section-ref" href="#idvalue">Section 8.14: ID Value</a>.</p></li><li><p>Added support for different query language and reworked whole XPath and CSS
Selectors integration.</p></li><li><p>Added examples to <a class="section-ref" href="#externalresource">Section 8.12: External Resource</a>.</p></li><li><p>Simplified <a class="section-ref" href="#LocaleFilter">Section 8.10: Locale Filter</a>.</p></li><li><p>Added a note about HTML and the attributes <code class="its-attr-markup">dir</code> and <code class="its-attr-markup">translate</code>
to <a class="section-ref" href="#selection-local">Section 5.2.2: Local Selection in an XML Document</a>.</p></li><li><p>Added definition of <code class="its-elem-markup">param</code> element to <a class="section-ref" href="#selection-global">Section 5.2.1: Global, Rule-based Selection</a>.</p></li><li><p>Added <a class="section-ref" href="#target-pointer">Section 8.13: Target Pointer</a>.</p></li><li><p>Original Ruby markup model changed to HTML5 Ruby model.</p></li><li><p>Updated references.</p></li><li><p>Added <a class="section-ref" href="#preservespace">Section 8.15: Preserve Space</a>.</p></li><li><p>Added <a class="section-ref" href="#lqissue">Section 8.16: Localization Quality Issue</a> and the related <a class="section-ref" href="#lqissue-typevalues">Appendix C: Values for the Localization Quality Issue Type</a>.</p></li><li><p>Added <a class="section-ref" href="#lqrating">Section 8.17: Localization Quality Rating</a>.</p></li><li><p>Added a placeholder <a class="section-ref" hre="#mtconfidence">Section 8.18: MT Confidence</a>.</p></li></ol><p id="changelog-since-20120626">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-20120626/">ITS 2.0 Working Draft 26 June 2012</a>.</p><ol class="depth1"><li><p>Various editorial changes (non-normative references update, style & grammar
+ made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20120626/">ITS 2.0 Working Draft 26 June 2012</a>:</p><ol class="depth1"><li><p>Various editorial changes (non-normative references update, style & grammar
fixes).</p></li><li><p>Made clarifications about what is out of scope of ITS 2.0 and about design decisions.</p></li><li><p>Added explanatory note on precedence and overriding in <a class="section-ref" href="#selection-precedence">Section 5.5: Precedence between Selections</a>.</p></li><li><p>Reordered some components in <a class="section-ref" href="#introduction">Section 1: Introduction</a>.</p></li><li><p>Restructured description of relation to ITS 1.0 and new principles in <a class="section-ref" href="#introduction">Section 1: Introduction</a>.</p></li><li><p>Added <a class="section-ref" href="#queryLanguage">Section 5.3.1: Choosing Query Language</a> as a stub.</p></li><li><p>Added <a class="section-ref" href="#LocaleFilter">Section 8.10: Locale Filter</a>.</p></li><li><p>Added <a class="section-ref" href="#domain">Section 8.8: Domain</a>.</p></li><li><p>Added <a class="section-ref" href="#usage-in-legacy-html">Section 2.5.5: Version of HTML</a>.</p></li><li><p>Added local markup in a class="section-ref" href="#elements-within-text">Section 8.7: Elements Within Text</a>.</p></li><li><p>Added <a class="section-ref" href="#externalresource">Section 8.12: External Resource</a>.</p></li><li><p>Updated examples to use the <code class="its-attr-markup">version</code> attribute with the value
<code>2.0</code>.</p></li></ol><p id="changelog-since-20070403">The following log records major changes that have been
made to this document between the <a href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0 Recommendation</a> and
- this document.</p><ol class="depth1"><li><p>Clarified <a href="#introduction">introduction</a> to cover ITS 2.0</p></li><li><p>Added a subsection on the relation to ITS 1.0 to the introduction.</p></li><li><p>Created HTML based declarations for various data categories, see e.g., HTML
+ this document:</p><ol class="depth1"><li><p>Clarified <a href="#introduction">introduction</a> to cover ITS 2.0</p></li><li><p>Added a subsection on the relation to ITS 1.0 to the introduction.</p></li><li><p>Created HTML based declarations for various data categories, see e.g., HTML
declarations for the Terminology data category and the summary for local data categories
in <a class="section-ref" href="#selection-local">Section 5.2.2: Local Selection in an XML Document</a></p></li><li><p>Created examples for these declarations, see e.g., <a href="#EX-term-local-html-1">Example 41</a></p></li><li><p>Added placeholders for new data categories to <a class="section-ref" href="#datacategory-description">Section 8: Description of Data Categories</a></p></li><li><p>Added a placeholder section <a class="section-ref" href="#conversion-to-nif">Section 5.7: Conversion to NIF</a></p></li></ol></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="acknowledgements" id="acknowledgements"></a>I Acknowledgements (Non-Normative)</h2><p>This document has been developed with contributions by the
Received on Monday, 24 June 2013 17:37:40 UTC