CVS WWW/International/multilingualweb/lt/drafts/its20 from CVS User fsasaki on 2013-10-21 (public-multilingualweb-lt-commits@w3.org from October 2013)

From: CVS User fsasaki <cvsmail@w3.org>
Date: Mon, 21 Oct 2013 20:11:09 +0000
To: public-multilingualweb-lt-commits@w3.org
Message-Id: <E1VYLoj-0007rl-H3@gil.w3.org>
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv30237

Modified Files:
	its20.html 
Log Message:
re-generated HTML

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/10/14 07:50:58	1.504
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/10/21 20:11:08	1.505
@@ -225,7 +225,7 @@
             ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between
             ITS markup and the various HTML flavors. Furthermore, ITS 2.0 suggests when and how to
             leverage processing based on the XML Localization Interchange File Format (<a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a>), as
-            well as the Natural Language Processing Interchange Format <a title="" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document are not intended for translation.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content has to be left untranslated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that are intended for translation and those that are not to be translated. Explicit metadata is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096">&lt;resources&gt;</strong>
+            well as the Natural Language Processing Interchange Format <a title="NIF 2.0 Core Ontology" href="#nif-reference" shape="rect">[NIF]</a>.</p><p>For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document are not intended for translation.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 1: Document in which some content has to be left untranslated</div><p>In this document it is difficult to distinguish between those <code>string</code> elements that are intended for translation and those that are not to be translated. Explicit metadata is needed to resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096">&lt;resources&gt;</strong>
   <strong class="hl-tag" style="color: #000096">&lt;section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;arguments&gt;</strong>
       <strong class="hl-tag" style="color: #000096">&lt;string&gt;</strong>page<strong class="hl-tag" style="color: #000096">&lt;/string&gt;</strong>
@@ -286,13 +286,13 @@
               Within Text</a>, <a href="#preservespace" shape="rect">Preserve Space</a>, and <a href="#LocaleFilter" shape="rect">Locale Filter</a>. Others are still discussed as requirements
             for possible future versions of ITS:</p><ol class="depth1"><li><p>“Context” = What specific related information might be helpful?</p></li><li><p>“Automated Language” = Does this content lend itself to automatic processing?</p></li></ol><p>The real-world deployments also helped to understand that for the <a href="http://www.webplatform.org/" shape="rect">Open Web Platform</a> – the ITS 1.0 restriction
             to XML was an obstacle for quite a number of environments. What was missing was, for
-            example, the following:</p><ol class="depth1"><li><p>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</p></li><li><p>Easy use of ITS in various Web-exposed (multilingual) Natural Language Processing contexts</p></li><li><p>Computer-supported linguistic quality assurance</p></li><li><p>Content Management  and translation platforms</p></li><li><p>Cross-language scenarios</p></li><li><p>Content enrichment</p></li><li><p>Support for W3C provenance <a title="" href="#prov-dm" shape="rect">[PROV-DM]</a>, “information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data
-              scenarios</p></li></ol><p>ITS 2.0 was created by an alliance of stakeholders who are involved in content for global use. Thus, ITS 2.0 was developed with input from/with a view towards the following:</p><ul><li><p>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in multilingual production chains</p></li><li><p>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to facilitate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a>, <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>)
+            example, the following:</p><ol class="depth1"><li><p>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</p></li><li><p>Easy use of ITS in various Web-exposed (multilingual) Natural Language Processing contexts</p></li><li><p>Computer-supported linguistic quality assurance</p></li><li><p>Content Management  and translation platforms</p></li><li><p>Cross-language scenarios</p></li><li><p>Content enrichment</p></li><li><p>Support for W3C provenance <a title="Provenance data model" href="#prov-dm" shape="rect">[PROV-DM]</a>, “information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data
+              scenarios</p></li></ol><p>ITS 2.0 was created by an alliance of stakeholders who are involved in content for global use. Thus, ITS 2.0 was developed with input from/with a view towards the following:</p><ul><li><p>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in multilingual production chains</p></li><li><p>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to facilitate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a>, <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> and <a title="NIF 2.0 Core Ontology" href="#nif-reference" shape="rect">[NIF]</a>)
               that are interested for example in information sharing, and lossless roundtrip of
               metadata in localization workflows</p></li></ul><p>One example outcome of the resulting synergies is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> mechanism. It addresses the
             provenance-related requirement by allowing ITS processors to leave a trace: ITS
             processors can basically say “It is me that generated this bit of
-              information”. Another example are the <a title="" href="#nif-reference" shape="rect">[NIF]</a> related details of ITS 2.0, which provide a non-normative approach to couple Natural Language
+              information”. Another example are the <a title="NIF 2.0 Core Ontology" href="#nif-reference" shape="rect">[NIF]</a> related details of ITS 2.0, which provide a non-normative approach to couple Natural Language
             Processing with concepts of the Semantic Web.</p></div><div class="div2">
 <h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="usage-scenarios" id="usage-scenarios" shape="rect"/>1.3 Usage Scenarios</h3><p>The <a title="&#x2028;Internationalization Tag Set (ITS) Version 1.0&#x2028;" href="#its10" shape="rect">[ITS 1.0]</a>
                <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “ITS is a technology to easily create XML, which is internationalized and can be localized effectively”.  In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multilingual production.</p><ul><li><p>Static mono-lingual (for example, the area of content authors): This part of the
@@ -323,7 +323,7 @@
                 settled, the Ruby data category possibly will be reintroduced, in a subsequent
                 version of ITS.</p></li><li><p>The <a href="#directionality" shape="rect">Directionality</a> data category reflects directionality markup in <a title="HTML 4.01" href="#html4" shape="rect">[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" shape="rect">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors" shape="rect">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" shape="rect">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" shape="rect">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="sectin-ref" href="#traceability" shape="rect">Section 2.6: Traceability</a> for details.</p></li></ul><p>
-               <em>Mappings:</em> ITS 2.0 provides a non-normative algorithm to convert ITS 2.0 information into <a title="" href="#nif-reference" shape="rect">[NIF]</a> and links to guidance about how to relate ITS 2.0 to XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">Section 2.7: Mapping and conversion</a> for details.</p><p>
+               <em>Mappings:</em> ITS 2.0 provides a non-normative algorithm to convert ITS 2.0 information into <a title="NIF 2.0 Core Ontology" href="#nif-reference" shape="rect">[NIF]</a> and links to guidance about how to relate ITS 2.0 to XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">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" shape="rect">Section 4: Conformance</a> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed. For <a title="HTML5" href="#html5" shape="rect">[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" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>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" shape="rect">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" shape="rect">[Charmod Norm]</a>.</p></div></div><div class="div1">
 <h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts" id="basic-concepts" shape="rect"/>2 Basic Concepts</h2><p>
@@ -540,7 +540,7 @@
           </p></div><div class="div2">
 <h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-conversion" id="mapping-conversion" shape="rect"/>2.7 Mapping and conversion</h3><div class="div3">
 <h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-NIF" id="mapping-NIF" shape="rect"/>2.7.1 ITS and RDF/NIF</h4><p>ITS 2.0 provides a non-normative 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" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims at interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion from <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content-related triples and relies on an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The back conversion from <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively as well. 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" shap="rect">Text Analysis</a> markup. The outcome are HTML documents with linked information, see <a href="#EX-text-analysis-html5-local-1" shape="rect">Example 52</a>.</p></div><div class="div3">
+        representations) that contain ITS metadata to the RDF format based on <a title="NIF 2.0 Core Ontology" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims at interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion from <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content-related triples and relies on an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The back conversion from <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively as well. One motivation for the back conversion is a roundtrip workflow like: 1) conversion to NIF 2) in NIF representation detection of named entities using NLP tools 3) back conversion to HTML and generation of <a href"#textanalysis" shape="rect">Text Analysis</a> markup. The outcome are HTML documents with linked information, see <a href="#EX-text-analysis-html5-local-1" shape="rect">Example 52</a>.</p></div><div class="div3">
 <h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>2.7.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localization and translation workflows. <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> is the successor of <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a> and under development. XLIFF has been widely implemented in various translation management systems, computer aided translation tools and in utilities for extracting translatable content from source documents and merging back the content in the target language.</p><p>The mapping between ITS and XLIFF herefore underpins several important ITS 2.0 usage scenarios <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a>. These usage scenarios involve:</p><ul><li><p>the extraction of ITS metadata from a source language file into XLIFF</p></li><li><p>the addition of ITS metadata into an XLIFF file by translation tools</p></li><li><p>the mapping of ITS metadata in an XLIFF file into ITS metadata in the resulting target language files.</p></li></ul><p>ITS 2.0 has no normative dependency on XLIFF, however a  <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping" shape="rect">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/" shape="rect">Internationalization Tag Set Interest Group</a>.</p></div></div><div class="div2">
 <h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="implementing-its20" id="implementing-its20" shape="rect"/>2.8 ITS 2.0 Implementations and Conformance</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer (see <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a>). The clauses target different types of implementers:</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema" shape="rect">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS arkup</a> tell implementers how to process XML content according to ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html5-its" shape="rect">Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations" shape="rect">ection 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> clarify how information needs to be made available for given pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <a href="https://github.com/w3c/its-2.0-testsuite/" shape="rect">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually 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-u-impl" shape="rect">[MLW US IMPL]</a> for more information).</p></div></div><div class="div1">
 <h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="notation-terminology" id="notation-terminology" shape="rect"/>3 Notation and Terminology</h2><p>
@@ -548,7 +548,7 @@
          </p><div class="div2">
 <h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="notation" id="notation" shape="rect"/>3.1 Notation</h3><p id="rfc-keywords">The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
             NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are
-            to be interpreted as described in <a title="" href="#rfc2119" shape="rect">[RFC 2119]</a>.</p><p>The namespace URI that <a href="#rfc-keywords" shape="rect">MUST</a> be used by
+            to be interpreted as described in <a title="Key Words for use in RFCs to Indicate&#xA;              Requirement Levels" href="#rfc2119" shape="rect">[RFC 2119]</a>.</p><p>The namespace URI that <a href="#rfc-keywords" shape="rect">MUST</a> be used by
             implementations of this specification is:</p><div class="exampleInner"><div class="exampleOuter"><pre xml:space="preserve">http://www.w3.org/2005/11/its</pre></div></div><p id="its-namespace-prefix">The namespace prefix used in this specification for XML
             implementations of ITS for the above URI is <code>its</code>. It is recommended that XML
             implementations of this specification use this prefix, unless there is existing
@@ -1954,7 +1954,7 @@
 				fragment, and thereby contributing to its correct translation. The
 				web resource may as well provide information on appropriate synonyms
 				and example usage. This is for example the case if the web resource
-				is WordNet <a title="" href="#wordnet" shape="rect">[WordNet]</a>. In the case of a <a href="#textAnalysis-info-pieces" shape="rect">concept class</a>, the external resource
+				is WordNet <a title="WordNet" href="#wordnet" shape="rect">[WordNet]</a>. In the case of a <a href="#textAnalysis-info-pieces" shape="rect">concept class</a>, the external resource
 				may provide a formalized conceptual definition arranged in a
 				hierarchical framework of related concepts. In the case of a named
 				entity, the external resource may provide a full-fledged description
@@ -2066,7 +2066,7 @@
   <strong class="hl-tag" style="color: #000096">&lt;/body&gt;</strong>
 <strong class="hl-tag" style="color: #000096">&lt;/html&gt;</strong></pre></div><p>[Source file: <a href="examples/html5/EX-text-analysis-html5-local-1.html" shape="rect">examples/html5/EX-text-analysis-html5-local-1.html</a>]</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p> For expressing <a href="#textAnalysis-info-pieces" shape="rect">Entity type / concept class </a>
                 information, implementers are encouraged to use an existing repository of entity
-                types such as the Named Entity Recognition and Disambiguation <a title="" href="#nerd" shape="rect">[NERD]</a> ontology. Of course this requires that the repository satisfies the
+                types such as the Named Entity Recognition and Disambiguation <a title="Named Entity Recognition and Disambiguation ontology (NERD)" href="#nerd" shape="rect">[NERD]</a> ontology. Of course this requires that the repository satisfies the
                 constraints imposed by the text analysis data category (e.g., use of IRIs).</p><p>
 				Various target types can be expressed via
 				<a href="#textAnalysis-info-pieces" shape="rect">Entity type / concept class</a>: types of entities, types of lexical concepts, or ontology
@@ -2196,7 +2196,7 @@
               a wider range of activities, the data category offers a mechanism to refer to external
               provenance information.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The specification does not define the format of external provenance information, but it is
                 recommended that an open provenance or change-logging format be used, e.g. the W3C
-                provenance data model <a title="" href="#prov-dm" shape="rect">[PROV-DM]</a>.</p></div><p>Translation or translation revision tools, such as machine translation engines or
+                provenance data model <a title="Provenance data model" href="#prov-dm" shape="rect">[PROV-DM]</a>.</p></div><p>Translation or translation revision tools, such as machine translation engines or
               computer assisted translation tools, may offer an easy way to create this information.
               Translation tools can then present this information to post-editors or translation
               workflow managers. Web applications may to present such information to consumers of
@@ -3140,8 +3140,8 @@
               http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/</a>. The latest version of <a href="http://www.w3.org/TR/qaframe-spec/" shape="rect">QAFRAMEWORK</a> is available at
             http://www.w3.org/TR/qaframe-spec/.</dd><dt class="label"><a name="relaxng" id="relaxng" shape="rect"/>RELAX NG</dt><dd>Information technology – Document Schema Definition
             Language (DSDL) – Part 2: <cite>Regular-grammar-based validation – RELAX NG</cite>.
-            International Organization for Standardization (ISO) ISO/IEC 19757-2:2003.</dd><dt class="label"><a name="rfc2119" id="rfc2119" shape="rect"/>RFC 2119</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect">Key Words for use in RFCs to Indicate
-              Requirement Levels</a>. IETF RFC 2119, March 1997. Available at <a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect">
+            International Organization for Standardization (ISO) ISO/IEC 19757-2:2003.</dd><dt class="label"><a name="rfc2119" id="rfc2119" shape="rect"/>RFC 2119</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect"><cite>Key Words for use in RFCs to Indicate
+              Requirement Levels</cite></a>. IETF RFC 2119, March 1997. Available at <a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect">
               http://www.ietf.org/rfc/rfc2119.txt</a>. </dd><dt class="label"><a name="rfc3987" id="rfc3987" shape="rect"/>RFC 3987</dt><dd>Martin Dürst, Michel Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt" shape="rect"><cite>Internationalized Resource
                 Identifiers (IRIs)</cite></a>. RFC 3987, January 2005. See <a href="http://www.ietf.org/rfc/rfc3987.txt" shape="rect">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="css3-selectors" id="css3-selectors" shape="rect"/>Selectors Level 3</dt><dd>Tantek Çelik, Elika J. Etemad, Daniel
             Glazman, Ian Hickson, Peter Linss, John Williams <a href="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/" shape="rect"><cite>Selectors Level
@@ -3413,10 +3413,10 @@
                   while other issues cannot.</p></li><li><p>If a system has an "miscellaneous" or "other" value, it is better to map this to this
                   value even if the specific instance of the issue might be mapped to another
                   value.</p></li></ul>
-                  </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>Note: <code>uncategorized</code> is used for issues that have not (yet) been categorized into a more specific value. For example, an automatic process might flag issues for attention but not provide any further detail or categorization: such issues would be listed as <code>uncategorized</code> in ITS 2.0. It may also be used when the exact nature of an issue is unclear and it cannot be categorized as a result (e.g., text is seriously garbled and the cause it unclear). By contrast other is used when the nature of an issue is clear but it cannot be categorized in one of the ITS 2.0 categories (or when a model or tool has its own “other” category). For example, in translation of subtitles there is a “respeaking” error category that does not correspond to any ITS 2.0 category and is highly specific to that environment; respeaking errors would therefore be categorized as <code>other</code> in ITS 2.0.</p><div></div><div class="div1">
+                  </td></tr></tbody></table><div class="note"><p class="prefix"><b>Note:</b></p><p>The value <code>uncategorized</code> is used for issues that have not (yet) been categorized into a more specific value. For example, an automatic process might flag issues for attention but not provide any further detail or categorization: such issues would be listed as <code>uncategorized</code> in ITS 2.0. It may also be used when the exact nature of an issue is unclear and it cannot be categorized as a result (e.g., text is seriously garbled and the cause it unclear). By contrast other is used when the nature of an issue is clear but it cannot be categorized in one of the ITS 2.0 categories (or when a model or tool has its own “other” category). For example, in translation of subtitles there is a “respeaking” error category that does not correspond to any ITS 2.0 category and is highly specific to that environment; respeaking errors would therefore be categorized as <code>other</code> in ITS 2.0.<p></div></div><div class="div1">
 <h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="its-schemas" id="its-schemas" shape="rect"/>D Schemas for ITS</h2><p>
-            <em>This section is normative.</em>
-         </p><p>The following schemas define ITS elements and attributes and can be used as building
+            <em>This section is informative.</em>
+         </p><div class="note"><p class="prefix"><b>Note:</b></p><p>The schemas are only informative and may be updated any time. An updated version of the schemas can be found in the <a href="https://github.com/w3c/its-2.0-testsuite/tree/master/its2.0/schema" shape="rect">ITS 2.0 test suite</a>.</p></div><p>The following schemas define ITS elements and attributes and can be used as building
           blocks when you want to integrate ITS markup into your own XML vocabulary. You can see
           examples of such integration in <a href="http://www.w3.org/TR/xml-i18n-bp/" shape="rect">Best
             Practices for XML Internationalization</a>.</p><p id="foreign-elements">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><p>The following four schemas are provided:</p><p>
@@ -5530,13 +5530,14 @@
               Activity</a>, June 2005.</dd><dt class="label"><a name="charmod-norm" id="charmod-norm" shape="rect"/>Charmod Norm</dt><dd>Yergeau, François, Martin J. Dürst, Richard Ishida, Addison Phillips, Misha Wolf, Tex Texin. <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/" shape="rect"><cite>Character Model for the World Wide Web 1.0: Normalization</cite></a>. W3C Working Draft 1 May 2012. Available at <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/" shape="rect">http://www.w3.org/TR/2012/WD-charmod-norm-20120501/</a>. The latest version of <a href="http://www.w3.org/TR/charmod-norm/" shape="rect">Charmod Norm</a> is available at http://www.w3.org/TR/charmod-norm/ .</dd><dt class="label"><a name="checkmate" id="checkmate" shape="rect"/>CheckMate Quality Check</dt><dd>Okapi Project. <a href="http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration" shape="rect"><cite>CheckMate – Quality Check Configuration</cite></a>. Available at <a href="ttp://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration" shape="rect">http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration</a>.</dd><dt class="label"><a name="css2-1" id="css2-1" shape="rect"/>CSS 2.1</dt><dd> Bert Bos, Tantek Çelik, Ian Hickson Håkon Wium Lie. <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/" shape="rect"><cite>Cascading Style Sheets,
                 level 2 revision 1 CSS 2.1 Specification</cite></a>. W3C Recommendation 7 June 2011. Available at <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/" shape="rect">
               http://www.w3.org/TR/2011/REC-CSS2-20110607/</a>. The latest version of <a href="http://www.w3.org/TR/CSS21/" shape="rect">CSS2</a> is available at
-            http://www.w3.org/TR/CSS21/.</dd><dt class="label"><a name="dbpedia" id="dbpedia" shape="rect"/>DBpedia</dt><dd>DBpedia available at: <a href="http://dbpedia.org/OnlineAccess" shape="rect">http://dbpedia.org/OnlineAccess</a>.</dd><dt class="label"><a name="dita10" id="dita10" shape="rect"/>DITA 1.0</dt><dd>Michael Priestley, JoAnn Hackos, et. al., editors.
+            http://www.w3.org/TR/CSS21/.</dd><dt class="label"><a name="dbpedia" id="dbpedia" shape="rect"/>DBpedia</dt><dd>
+               <cite>DBpedia</cite>. Available at: <a href="http://dbpedia.org/OnlineAccess" shape="rect">http://dbpedia.org/OnlineAccess</a>.</dd><dt class="label"><a name="dita10" id="dita10" shape="rect"/>DITA 1.0</dt><dd>Michael Priestley, JoAnn Hackos, et. al., editors.
                 <a href="https://www.oasis-open.org/committees/download.php/15316/dita10.zip" shape="rect"><cite>OASIS
                 Darwin Information Typing Architecture (DITA) Language Specification
               v1.0</cite></a>. OASIS Standard 9 May 2005. Available at <a href="https://www.oasis-open.org/committees/download.php/15316/dita10.zip" shape="rect">
               https://www.oasis-open.org/committees/download.php/15316/dita10.zip</a>.</dd><dt class="label"><a name="docbook" id="docbook" shape="rect"/>DocBook</dt><dd>Norman Walsh and Leonard Muellner. <a href="http://www.docbook.org/" shape="rect"><cite>DocBook: The Definitive Guide</cite></a>. Available at <a href="http://www.docbook.org/" shape="rect">
-              http://www.docbook.org/</a>.</dd><dt class="label"><a name="geo-i18n-l10n" id="geo-i18n-l10n" shape="rect"/>l10n i18n</dt><dd>Richard Ishida, Susan Miller. <a href="http://www.w3.org/International/questions/qa-i18n" shape="rect">Localization vs.
-              Internationalization</a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization Activity</a>,
+              http://www.docbook.org/</a>.</dd><dt class="label"><a name="geo-i18n-l10n" id="geo-i18n-l10n" shape="rect"/>l10n i18n</dt><dd>Richard Ishida, Susan Miller. <a href="http://www.w3.org/International/questions/qa-i18n" shape="rect"><cite>Localization vs.
+              Internationalization</cite></a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization Activity</a>,
             January 2006.</dd><dt class="label"><a name="iso30042" id="iso30042" shape="rect"/>ISO 30042</dt><dd>(International Organization for Standardization).
               <cite>TermBase eXchange (TBX)</cite>. [Geneva]: International Organization for
             Standardization, 2008.</dd><dt class="label"><a name="isots11669" id="isots11669" shape="rect"/>ISO/TS 11669:2002</dt><dd>(International Organization for
@@ -5546,16 +5547,17 @@
                 Localization Markup Requirements</cite></a>. W3C Working Draft 18 May 2006. Available at <a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/" shape="rect">
               http://www.w3.org/TR/2006/WD-itsreq-20060518/</a>. The latest version of <a href="http://www.w3.org/TR/itsreq/" shape="rect">ITS REQ</a> is available at
             http://www.w3.org/TR/itsreq/.</dd><dt class="label"><a name="reqlocdtd" id="reqlocdtd" shape="rect"/>Localizable DTDs</dt><dd>Richard Ishida, Yves Savourel <a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect"><cite>Requirements for Localizable
-                DTD Design</cite></a>. Working Draft 7 July 2003. Available at <a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect">http://people.w3.org/rishida/localizable-dtds/</a>. </dd><dt class="label"><a name="microdata" id="microdata" shape="rect"/>Microdata</dt><dd>Ian Hickson <a href="http://www.w3.org/TR/microdata/" shape="rect"><cite>HTML Microdata</cite></a>. W3C Working Draft 25 October 2012. Available at <a href="http://www.w3.org/TR/2012/WD-microdata-20121025/" shape="rect">http://www.w3.org/TR/2012/WD-microdata-20121025/</a>. </dd><dt class="label"><a name="mlw-metadata-us-impl" id="mlw-metadata-us-impl" shape="rect"/>MLW US IMPL</dt><dd>Christian Lieske (ed.). <a href="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/" shape="rect"><cite>Metadata for the Multilingual Web - Usage Scenarios and Implementations </cite></a>. W3C Working Draft 7 March 2013. Available at <a href="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/" shape="rect">http://www.w3.or/TR/2013/WD-mlw-metadata-us-impl-20130307/</a>. The latest version of <a href="http://www.w3.org/TR/mlw-metadata-us-impl/" shape="rect">MLW Metadata US IMPL</a> is available at http://www.w3.org/TR/mlw-metadata-us-impl/ .</dd><dt class="label"><a name="nerd" id="nerd" shape="rect"/>NERD</dt><dd>Named Entity Recognition and Disambiguation ontology (NERD)
+                DTD Design</cite></a>. Working Draft 7 July 2003. Available at <a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect">http://people.w3.org/rishida/localizable-dtds/</a>. </dd><dt class="label"><a name="microdata" id="microdata" shape="rect"/>Microdata</dt><dd>Ian Hickson <a href="http://www.w3.org/TR/microdata/" shape="rect"><cite>HTML Microdata</cite></a>. W3C Working Draft 25 October 2012. Available at <a href="http://www.w3.org/TR/2012/WD-microdata-20121025/" shape="rect">http://www.w3.org/TR/2012/WD-microdata-20121025/</a>. </dd><dt class="label"><a name="mlw-metadata-us-impl" id="mlw-metadata-us-impl" shape="rect"/>MLW US IMPL</dt><dd>Christian Lieske (ed.). <a href="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/" shape="rect"><cite>Metadata for the Multilingual Web - Usage Scenarios and Implementations </cite></a>. W3C Working Draft 7 March 2013. Available at <a href="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/" shape="rect">http://www.w3.or/TR/2013/WD-mlw-metadata-us-impl-20130307/</a>. The latest version of <a href="http://www.w3.org/TR/mlw-metadata-us-impl/" shape="rect">MLW Metadata US IMPL</a> is available at http://www.w3.org/TR/mlw-metadata-us-impl/ .</dd><dt class="label"><a name="mqm" id="mqm" shape="rect"/>Multidimensional Quality Metrics</dt><dd>Lommel, Arle. <cite>Useful Quality Metrics (for Humans, Not Researchers)</cite>. Presentation at the Workshop on UserCentric Machine Translation &amp; Evaluation, <a href="http://www.mtsummit2013.info/workshops.asp" shape="rect">MT Summit 2013</a>.</dd><dt class="label"><a name="nerd" id="nerd" shape="rect"/>NERD</dt><dd>
+               <cite>Named Entity Recognition and Disambiguation ontology (NERD)</cite>.
             available at: <a href="http://nerd.eurecom.fr/ontology" shape="rect">http://nerd.eurecom.fr/ontology</a>
-            </dd><dt class="label"><a name="nif-reference" id="nif-reference" shape="rect"/>NIF</dt><dd>Hellmann, S. et al. (ed.). <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#" shape="rect">NIF 2.0 Core Ontology</a>, as of August 2013. Available at <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#" shape="rect">http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#</a> under CC-BY 3.0  license maintained by the <a href="http://nlp2rdf.org" shape="rect">NLP2RDF project</a>.</dd><dt class="label"><a name="nvdl" id="nvdl" shape="rect"/>NVDL</dt><dd>Information technology – Document Schema Definition
+            </dd><dt class="label"><a name="nif-reference" id="nif-reference" shape="rect"/>NIF</dt><dd>Hellmann, S. et al. (ed.). <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#" shape="rect"><cite>NIF 2.0 Core Ontology</cite></a>, as of August 2013. Available at <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#" shape="rect">http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#</a> under CC-BY 3.0  license maintained by the <a href="http://nlp2rdf.org" shape="rect">NLP2RDF project</a>.</dd><dt class="label"><a name="nvdl" id="nvdl" shape="rect"/>NVDL</dt><dd>Information technology – Document Schema Definition
             Languages (DSDL) – Part 4: <cite>Namespace-based Validation Dispatching Language
               (NVDL)</cite>. International Organization for Standardization (ISO) ISO/IEC
             19757-4:2003.</dd><dt class="label"><a name="opendocument" id="opendocument" shape="rect"/>OpenDocument</dt><dd>Michael Brauer et al. <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect"><cite>OASIS Open Document Format for Office Applications (OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
               https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>. The latest
             version of <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
               OpenDocument</a> is available at
-            https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="prov-dm" id="prov-dm" shape="rect"/>PROV-DM</dt><dd>Moreau, Luc and Paolo Missier (eds.). <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/" shape="rect">Provenance data model</a>. 
+            https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.</dd><dt class="label"><a name="prov-dm" id="prov-dm" shape="rect"/>PROV-DM</dt><dd>Moreau, Luc and Paolo Missier (eds.). <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/" shape="rect"><cite>Provenance data model</cite></a>. 
             W3C Recommendation 30 April 2013. Available at <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/" shape="rect">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>.
             The latest version of <a href="http://www.w3.org/TR/prov-dm/" shape="rect">The PROV Data Model</a>
             is available at http://www.w3.org/TR/prov-dm/.
@@ -5566,7 +5568,8 @@
             Group). <cite>Structured Specifications and Translation Parameters</cite>. Available
             at <a href="http://www.ttt.org/specs/" shape="rect">http://www.ttt.org/specs</a>.</dd><dt class="label"><a name="tei" id="tei" shape="rect"/>TEI</dt><dd>Lou Burnard and Syd Bauman (eds.) <a href="http://www.tei-c.org/Guidelines/P5/" shape="rect"><cite>Text Encoding Initiative Guidelines
                 development version (P5)</cite></a>. TEI Consortium, Charlottesville, Virginia, USA, Text Encoding
-            Initiative.</dd><dt class="label"><a name="wordnet" id="wordnet" shape="rect"/>WordNet</dt><dd>Princeton University "About WordNet." WordNet.
+            Initiative.</dd><dt class="label"><a name="wordnet" id="wordnet" shape="rect"/>WordNet</dt><dd>
+               <cite>WordNet</cite>.
             Princeton University. 2010, available at: <a href="http://wordnet.princeton.edu" shape="rect">http://wordnet.princeton.edu</a>.</dd><dt class="label"><a name="xhtml10" id="xhtml10" shape="rect"/>XHTML 1.0</dt><dd>Steven Pemberton et al. <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect"><cite>XHTML™ 1.0 The Extensible
                 HyperText Markup Language (Second Edition)</cite></a>. W3C Recommendation 26 January 2000, revised 1 August 2002. Available at <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect">
               http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>. The latest version of <a href="http://www.w3.org/TR/xhtml1/" shape="rect">XHTML 1.0</a> is available at
@@ -5586,7 +5589,7 @@
 <h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="conversion-to-nif" id="conversion-to-nif" shape="rect"/>F Conversion to NIF</h2><p>
             <em>This section is informative.</em>
          </p><p>This section provides an informative 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" shape="rect">[NIF]</a>. The conversion results in RDF triples.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm creates URIs that in the query part contain the characters "[" and "]", as part of XPath expressions. In the conversion output (see an <a href="examples/nif/EX-nif-conversion-output.ttl" shape="rect">example</a>), The URIs are escaped as "%5B" and "%5D". For readability the URIs shown in this section do not escape these characters.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP tool. It can
+          representations) that contain ITS metadata to the RDF format based on <a title="NIF 2.0 Core Ontology" href="#nif-reference" shape="rect">[NIF]</a>. The conversion results in RDF triples.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm creates URIs that in the query part contain the characters "[" and "]", as part of XPath expressions. In the conversion output (see an <a href="examples/nif/EX-nif-conversion-output.ttl" shape="rect">example</a>), The URIs are escaped as "%5B" and "%5D". For readability the URIs shown in this section do not escape these characters.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP tool. It can
           produce a lot of "<span class="quote">phantom</span>" predicates from excessive whitespace, which 1)
           increases the size of the intermediate mapping and 2) extracts this whitespace as
           text, and therefore might decrease NLP performance. It is strongly recommended to
@@ -5774,7 +5777,7 @@
           the same parent.</p></div><div class="div1">
 <h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="localization-quality-guidance" id="localization-quality-guidance" shape="rect"/>H Localization Quality Guidance</h2><p>
             <em>This section is informative.</em>
-         </p><p>The <a href="#lqissue" shape="rect">Localization Quality Issue</a> data category description uses the following terms as defined below for the purposes of this document.</p><ul><li><p><em>Quality assessment</em>. The task of evaluating the quality of translated content to determine its quality and to assign a value to it. Localization quality assessment is commonly conducted by identifying, categorizing, and counting issues in the translated content.</p></li><li><p><em>Issue</em>. A quality issue is a potential error detected in content. Issues may be detected automatically (e.g., by using a grammar checker or translation-specific tool) or manually, by human checking of content. Issues may or may not be errors (e.g., an apparent mistranslation may be deliberate and appropriate in some contexts) and should be confirmed by review.</p></li><li><p><em>Metric</em>. A metric is a formal system used in quality assessment tasks to identify issues, evaluate them, and determine quality. Metrics provie specific reference points for categorizing issues (as opposed to subjective assessment of quality, which does not use a metric) and may include weights for issues.</p></li><li><p><em>Model</em>. A model is the underlying description of the system that underlies a metric. (For example, some models may allow variable weights to be assigned to different issue types, in which case the specific metric used for a task will have these weights defined, even though the underlying model does not.)</p></li><li><p><em>Profile</em>. A quality profile is the adaptation of a model to specific requirements. It specifies specific conditions for using a model. It may include instructions and other guidelines that are not included in the actual metric used. If a model allows for no customization, it has a single profile that is identical to the model; if it allows customization, each customization is a distinct profile.</p></li><li><p><em>Review</em>. The task of examining a text to identify any issues that occur in it. Revew may be tied to the task of fixing any issues, a task generally referred to as revision.</p></li><li><p><em>Specifications</em>. Specifications (sometimes called a translation brief) are a description of the various expectations and requirements for a translation task. These may include statements about the type of translation expected, guidance on terminology to be used, information about audience, and so forth. Translation specifications are described in detail in ISO/TS-11669.</p></li><li><p><em>Tool</em>. As used here, a tool is software that generates localization quality markup. Tools may be fully automatic (e.g., a tool that identifies potential issues with terminology and grammar and marks them without human intervention) or may required human input (e.g., a system that allows users to highlight spans of text and mark them with appropriate issues).</p></li></ul><p>For more information on setting translation project specifications and determining quality expectations, implementers are encouraged toconsult the ISO standard definition of translation project specifications included in <a title="Translation projects – General guidance" href="#isots11669" shape="rect">[ISO/TS 11669:2002]</a>. Details about translation specifications are available at <a title="Structured Specifications and Translation Parameters" href="#structuredspecs" shape="rect">[Structured Specifications]</a>. While these documents do not directly address the definition of quality metrics, they provide useful guidance for implementers interested in determining which localization quality issue values should be used for specific scenarios.</p><p>The issue types defined in Localization Quality Issue were derived from the QTLaunchPad project’s Multidimensional Quality Metrics (MQM) framework. Additional guidance on this project may be found at [Multidimensional Quality Metrics].</p><p>The topic of localization quality is rapidly evolving and ITS 2.0 represents the first step in standardizing this area and will serve for basic interopeability needs. For situations requiring additional expressive capability or categories, further custom markup may be required.</p></div><div class="div1">
+         </p><p>The <a href="#lqissue" shape="rect">Localization Quality Issue</a> data category description uses the following terms as defined below for the purposes of this document.</p><ul><li><p><em>Quality assessment</em>. The task of evaluating the quality of translated content to determine its quality and to assign a value to it. Localization quality assessment is commonly conducted by identifying, categorizing, and counting issues in the translated content.</p></li><li><p><em>Issue</em>. A quality issue is a potential error detected in content. Issues may be detected automatically (e.g., by using a grammar checker or translation-specific tool) or manually, by human checking of content. Issues may or may not be errors (e.g., an apparent mistranslation may be deliberate and appropriate in some contexts) and should be confirmed by review.</p></li><li><p><em>Metric</em>. A metric is a formal system used in quality assessment tasks to identify issues, evaluate them, and determine quality. Metrics provie specific reference points for categorizing issues (as opposed to subjective assessment of quality, which does not use a metric) and may include weights for issues.</p></li><li><p><em>Model</em>. A model is the underlying description of the system that underlies a metric. (For example, some models may allow variable weights to be assigned to different issue types, in which case the specific metric used for a task will have these weights defined, even though the underlying model does not.)</p></li><li><p><em>Profile</em>. A quality profile is the adaptation of a model to specific requirements. It specifies specific conditions for using a model. It may include instructions and other guidelines that are not included in the actual metric used. If a model allows for no customization, it has a single profile that is identical to the model; if it allows customization, each customization is a distinct profile.</p></li><li><p><em>Review</em>. The task of examining a text to identify any issues that occur in it. Revew may be tied to the task of fixing any issues, a task generally referred to as revision.</p></li><li><p><em>Specifications</em>. Specifications (sometimes called a translation brief) are a description of the various expectations and requirements for a translation task. These may include statements about the type of translation expected, guidance on terminology to be used, information about audience, and so forth. Translation specifications are described in detail in ISO/TS-11669.</p></li><li><p><em>Tool</em>. As used here, a tool is software that generates localization quality markup. Tools may be fully automatic (e.g., a tool that identifies potential issues with terminology and grammar and marks them without human intervention) or may required human input (e.g., a system that allows users to highlight spans of text and mark them with appropriate issues).</p></li></ul><p>For more information on setting translation project specifications and determining quality expectations, implementers are encouraged toconsult the ISO standard definition of translation project specifications included in <a title="Translation projects – General guidance" href="#isots11669" shape="rect">[ISO/TS 11669:2002]</a>. Details about translation specifications are available at <a title="Structured Specifications and Translation Parameters" href="#structuredspecs" shape="rect">[Structured Specifications]</a>. While these documents do not directly address the definition of quality metrics, they provide useful guidance for implementers interested in determining which localization quality issue values should be used for specific scenarios.</p><p>The issue types defined in Localization Quality Issue were derived from the QTLaunchPad project’s Multidimensional Quality Metrics (MQM) framework. Additional guidance on this project may be found at <a title="Useful Quality Metrics (for Humans, Not Researchers)" href="#mqm" shape="rect">[Multidimensional Quality Metrics]</a>.</p><p>The topic of localization quality is rapidly evolving and IS 2.0 represents the first step in standardizing this area and will serve for basic interoperability needs. For situations requiring additional expressive capability or categories, further custom markup may be required.</p></div><div class="div1">
 <h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="list-of-elements-and-attributes" id="list-of-elements-and-attributes" shape="rect"/>I List of ITS 2.0 Global Elements and Local Attributes</h2><p>
             <em>This section is informative.</em>
          </p><p>The following table lists global ITS 2.0 elements inside <code class="its-elem-markup">rules</code> element and local
@@ -5939,7 +5942,7 @@
             <em>This section is informative.</em>
          </p><p id="changelog-since-20130820">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-20130820/" shape="rect">ITS 2.0 Working Draft 20 August 2013</a>:</p><ol class="depth1"><li><p>Updated reference to HTML5, see related <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Sep/0004.html" shape="rect">mail thread</a>.</p></li><li><p>Edits in <a class="section-ref" href="#lqissue" shape="rect">Section 8.16: Localization Quality Issue</a> and <a class="section-ref" href="#lqissue-typevalues" shape="rect">Appendix C: Values for the Localization Quality Issue Type</a> (plus a new informative <a class="section-ref" href="#localization-quality-guidance" shape="rect">Appendix H: Localization Quality Guidance</a>) to clarify the <a href="#lqissue" shape="rect">Localization Quality Issue</a> data category, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/132" shape="rect">isue-132</a>.</p></li><li><p>Edits in <a class="section-ref" href="#conversion-to-nif" shape="rect">Appendix F: Conversion to NIF</a> and <a class="section-ref" href="#nif-backconversion" shape="rect">Appendix G: Conversion NIF2ITS</a> to resolve <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/131" shape="rect">issue-131</a>.</p></li></ol><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/" shape="rect">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" shape="rect">HTML5 defaults for Element Within Text</a> and added example.
             See <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/118" shape="rect">issue-118</a>
-            and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/532" shape="rect">action-532</a>.</p></li><li><p>Added a paragraph about mime type submission to <a class="section-ref" href="#its-mime-type" shape="rect">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" shape="rect">Register an Internet Media Type for a W3C Spec</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/251" shape="rect">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&amp;index-type=t&amp;keywords=action-502&amp;search=Search" shape="rect">CVS commits</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/502" shape="rect">action-502</a>.</p></li><li><p>Reformatting of various examples, see <a href="http://lsts.w3.org/Archives/Public/public-multilingualweb-lt-commits/2013May/0066.html" shape="rect">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" shape="rect">[NIF]</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/125" shape="rect">issue-125</a>.</p></li><li><p>Edit related to <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/527" shape="rect">action-527</a>: put the sentence about foreign elements / attributes also in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">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" shape="rect">action-422</a>.</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/126" shape="rect">issue-126</a> (Minor ssue with quality types listing).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/127" shape="rect">issue-127</a> (Clarifying HTML5 translate and global rules).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/128" shape="rect">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" shape="rect">issue-129</a> (sec1-2 editing (non-normative sec)).</p></li><li><p>Fixes about <a title="" href="#rfc2119" shape="rect">[RFC 2119]</a> statements, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/540" shape="rect">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" shape="rect">Appendix D: chemas for ITS</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/546" shape="rect">action-546</a>.</p></li><li><p>Updated link to quality issue type mappings in <a class="section-ref" href="#lqissue-typevalues" shape="rect">Appendix C: Values for the Localization Quality Issue Type</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/543" shape="rect">action-543</a>.</p></li><li><p>Clarify conflicts of <code class="its-elem-markup">param</code> elements with the same name in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</a> and <a class="section-ref" href="#html5-selection-precedence" shape="rect">Section 6.4: Precedence between Selections</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/130" shape="rect">issue-130</a>.</p></li><li><p>Updated editors list.</p></li><li><p>Implemented <a href="http://lists.w3.org/Archives/Public/public-i18n-its-ig/013Jul/0041.html" shape="rect">editorial edits</a> in <a class="section-ref" href="#idvalue" shape="rect">Section 8.14: ID Value</a> and <a class="section-ref" href="#locNote-datacat" shape="rect">Section 8.3: Localization Note</a>.</p></li><li><p>Implemented <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jul/0056.html" shape="rect">clarification</a> about <code class="its-attr-markup">annotatorsRef</code> attribute in <a class="section-ref" href="#its-tool-annotation" shape="rect">Section 5.7: ITS Tools Annotation</a>.</p></li><li><p>Implemented a <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jul/0037.html" shape="rect">clarification</a> in <a class="section-ref" href="#mtconfidence-definition" shape="rect">Section 8.18.1: Definition</a> and added <a href="#mt-confidence-score-generation-tools" shape="rect">a note</a> that <a href="#mtconfidence" shape="rect">MT Confidence</a> information can be produced both by MT systems and other tool.</p></li><li><p>Changed the <a href="#conversion-to-nif" shape="rect">conversion to NIF</a> to be a non-normative feature.</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/" shape="rect">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#" shape="rect">ITS RDF Ontology</a> and an <a href="#its-rdf-ontology-status" shape="rect">explanatory note</a> about its status to <a class="section-ref" href="#conversion-to-nif" shape="rect">Appendix F: Conversion to NIF</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/514" shape="rect">action-514</a>.</p></li><li><p>Updated <a class="section-ref" href="#conversion-to-nif" shape="rect">Appendix F: Conversion to NIF</a> to reflect <a href="http://www.w3.org/2013/05/08-mlw-lt-minutes#item04" shape="rect">MLW-LT May 013 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" shape="rect">action-517</a>.</p></li><li><p>Added <a href="#local-approach-not-applicable-to-attributes" shape="rect">a note</a> to <a class="section-ref" href="#basic-concepts-selection-local" shape="rect">Section 2.2.1: Local Approach</a> expressing that local selection does not apply to attributes,
+            and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/532" shape="rect">action-532</a>.</p></li><li><p>Added a paragraph about mime type submission to <a class="section-ref" href="#its-mime-type" shape="rect">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" shape="rect">Register an Internet Media Type for a W3C Spec</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/251" shape="rect">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&amp;index-type=t&amp;keywords=action-502&amp;search=Search" shape="rect">CVS commits</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/502" shape="rect">action-502</a>.</p></li><li><p>Reformatting of various examples, see <a href="http://lsts.w3.org/Archives/Public/public-multilingualweb-lt-commits/2013May/0066.html" shape="rect">CVS commit mail</a> and further CVS commit mails with the same send time.</p></li><li><p>Edits related to <a title="NIF 2.0 Core Ontology" href="#nif-reference" shape="rect">[NIF]</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/125" shape="rect">issue-125</a>.</p></li><li><p>Edit related to <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/527" shape="rect">action-527</a>: put the sentence about foreign elements / attributes also in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">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" shape="rect">action-422</a>.</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/126" shape="rect">ssue-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" shape="rect">issue-127</a> (Clarifying HTML5 translate and global rules).</p></li><li><p>Edits related to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/128" shape="rect">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" shape="rect">issue-129</a> (sec1-2 editing (non-normative sec)).</p></li><li><p>Fixes about <a title="Key Words for use in RFCs to Indicate&#xA;              Requirement Levels" href="#rfc2119" shape="rect">[RFC 2119]</a> statements, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/540" shape="rect">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 ML Schema for ITS 2.0 to <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/546" shape="rect">action-546</a>.</p></li><li><p>Updated link to quality issue type mappings in <a class="section-ref" href="#lqissue-typevalues" shape="rect">Appendix C: Values for the Localization Quality Issue Type</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/543" shape="rect">action-543</a>.</p></li><li><p>Clarify conflicts of <code class="its-elem-markup">param</code> elements with the same name in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</a> and <a class="section-ref" href="#html5-selection-precedence" shape="rect">Section 6.4: Precedence between Selections</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/130" shape="rect">issue-130</a>.</p></li><li><p>Updated editors lit.</p></li><li><p>Implemented <a href="http://lists.w3.org/Archives/Public/public-i18n-its-ig/2013Jul/0041.html" shape="rect">editorial edits</a> in <a class="section-ref" href="#idvalue" shape="rect">Section 8.14: ID Value</a> and <a class="section-ref" href="#locNote-datacat" shape="rect">Section 8.3: Localization Note</a>.</p></li><li><p>Implemented <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jul/0056.html" shape="rect">clarification</a> about <code class="its-attr-markup">annotatorsRef</code> attribute in <a class="section-ref" href="#its-tool-annotation" shape="rect">Section 5.7: ITS Tools Annotation</a>.</p></li><li><p>Implemented a <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Jul/0037.html" shape="rect">clarification</a> in <a class="section-ref" href="#mtconfidence-definition" shape="rect">Section 8.18.1: Definition</a> and added <a href="#mt-confidence-score-generation-tools" shape="rect">a note</a> that <a href="#mtconfidenc" shape="rect">MT Confidence</a> information can be produced both by MT systems and other tools.</p></li><li><p>Changed the <a href="#conversion-to-nif" shape="rect">conversion to NIF</a> to be a non-normative feature.</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/" shape="rect">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#" shape="rect">ITS RDF Ontology</a> and an <a href="#its-rdf-ontology-status" shape="rect">explanatory note</a> about its status to <a class="section-ref" href="#conversion-to-nif" shape="rect">Appendix F: Conversion to NIF</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/actions/514" shape="rect">action-514</a>.</p></li><li><p>Updated <a class="section-ref" href="#conversion-to-nif" shape="rect">Appendix F: Conversion to NIF</a> t reflect <a href="http://www.w3.org/2013/05/08-mlw-lt-minutes#item04" shape="rect">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" shape="rect">action-517</a>.</p></li><li><p>Added <a href="#local-approach-not-applicable-to-attributes" shape="rect">a note</a> to <a class="section-ref" href="#basic-concepts-selection-local" shape="rect">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" shape="rect">issue-98</a>.</p></li><li><p>Added a <a href="#qa-issue-types-mappings" shape="rect">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" shape="rect">action-493</a>.</p></li><li><p>Updated the definition of the regular expression to use in the <a class="section-ref" href="#allowedchars" shape="rect">Section 8.19: Allowed Characters</a> data category,
             see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/67" shape="rect">issue-67</a>.</p></li><li><p>Updated explanation of usage in <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> to reflect discussion on <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> defaults, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/89" shape="rect">issue-89</a>, <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/97" shape="rect">issue-97</a> and <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/118" shape="rect">issue-118</a>.</p></li><li><p>Clarified <a href="#provenance-records-in-html5-constraint" shape="rect">provenance</a> and 
@@ -6015,4 +6018,4 @@
             in <a class="section-ref" href="#selection-local" shape="rect">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" shape="rect">Example 40</a></p></li><li><p>Added placeholders for new data categories to <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>Added a placeholder section <a class="section-ref" href="#conversion-to-nif" shape="rect">Appendix F: Conversion to NIF</a></p></li></ol></div><div class="div1">
 <h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="acknowledgements" id="acknowledgements" shape="rect"/>K Acknowledgements</h2><p>This document has been developed with contributions by the
           <a href="http://www.w3.org/International/multilingualweb/lt/" shape="rect">MultilingualWeb-LT Working Group</a> and collaborators:  Mihael Arcan (DERI Galway at the National University of Ireland, Galway, Ireland), Pablo Badía (Linguaserve), Aaron Beaton (Opera Software), Renat Bikmatov (Logrus Plus LLC), Aljoscha Burchardt (German Research Center for Artificial Intelligence (DFKI GmbH)), Nicoletta Calzolari (CNR--Consiglio Nazionale delle Ricerche), Somnath Chandra (Department of Information Technology, Government of India), John Colosi (Verisign, Inc.), Mauricio del Olmo (Linguaserve), Giuseppe Deriard (Linguaserve), Pedro Luis Díez Orzas (Linguaserve), David Filip (University of Limerick), Leroy Finn (Trinity College Dublin), Karl Fritsche (Cocomore AG), Serge Gladkoff (Logrus Plus LLC), Tatiana Gornostay (Tilde), Daniel Grasmick (Lucy Software and Services GmbH), Declan Groves (Centre for Next Generation Localisation), Manuel Honegger (University of Limerick), Dominic Jones (Trinity CollegeDublin), Matthias Kandora (]init[), Milan Karásek (Moravia Worldwide), Jirka Kosek (University of Economics, Prague), Michael Kruppa (Cocomore AG), Alejandro Leiva (Cocomore AG), Swaran Lata (Department of Information Technology, Government of India), David Lewis (Trinity College Dublin), Fredrik Liden (ENLASO Corporation), Christian Lieske (SAP AG), Qun Liu (Centre for Next Generation Localisation), Arle Lommel (German Research Center for Artificial Intelligence (DFKI GmbH)), Priyanka Malik (Department of Information Technology, Government of India), Shaun McCance ((public) Invited expert), Sean Mooney (University of Limerick), Jan Nelson (Microsoft Corporation), Pablo Nieto Caride (Linguaserve), Pēteris Ņikiforovs (Tilde), Naoto Nishio (University of Limerick), Philip O'Duffy (University of Limerick), Des Oates (Adobe Systems Inc.), Georgios Petasis (Institute of Informatics &amp; Telecommunications (IIT), NCSR), Mārcis Pinnis (Tilde), Prashant Verma Prashant (Department of Information Technology, Govrnment of India), Georg Rehm (German Research Center for Artificial Intelligence (DFKI GmbH)), Phil Ritchie (VistaTEC), Thomas Rüdesheim (Lucy Software and Services GmbH), Nieves Sande (German Research Center for Artificial Intelligence (DFKI GmbH)), Felix Sasaki (DFKI / W3C Fellow), Yves Savourel (ENLASO Corporation), Jörg Schütz (W3C Invited Experts), Sebastian Sklarß (]init[), Ankit Srivastava (Centre for Next Generation Localisation), Tadej Štajner (Jozef Stefan Institute), Olaf-Michael Stefanov ((public) Invited expert), Najib Tounsi (Ecole Mohammadia d'Ingenieurs Rabat (EMI)), Naitik Tyagi Tyagi (Department of Information Technology, Government of India), Stephan Walter (Cocomore AG), Clemens Weins (Cocomore AG).</p><p>A special thanks goes to the following persons:
-          </p><ul><li><p>Sebastian Hellmann for introducing us to <a title="" href="#nif-reference" shape="rect">[NIF]</a> and for contributing to the creation of the <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS 2.0 ontology</a> and NIF testing.</p></li><li><p>Daniel Naber for introducing us to <a href="http://languagetool.org" shape="rect">LanguageTool</a> and for implementing <a href="#lqissue-typevalues" shape="rect">Localization Quality Issue Type</a> functionality in language tool.</p></li></ul></div></div></body></html>
\ No newline at end of file
+          </p><ul><li><p>Sebastian Hellmann for introducing us to <a title="NIF 2.0 Core Ontology" href="#nif-reference" shape="rect">[NIF]</a> and for contributing to the creation of the <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS 2.0 ontology</a> and NIF testing.</p></li><li><p>Daniel Naber for introducing us to <a href="http://languagetool.org" shape="rect">LanguageTool</a> and for implementing <a href="#lqissue-typevalues" shape="rect">Localization Quality Issue Type</a> functionality in language tool.</p></li></ul></div></div></body></html>
\ No newline at end of file
Received on Monday, 21 October 2013 20:11:13 UTC