W3C home > Mailing lists > Public > public-multilingualweb-lt-commits@w3.org > September 2013

CVS WWW/International/multilingualweb/lt/drafts/its20/TR-version

From: CVS User fsasaki <cvsmail@w3.org>
Date: Sun, 15 Sep 2013 15:49:54 +0000
Message-Id: <E1VLEaA-0005ef-6A@gil.w3.org>
To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory gil:/tmp/cvs-serv21693/TR-version

Modified Files:
	Overview.html 
Log Message:
pub prep

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html	2013/09/13 06:46:20	1.120
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html	2013/09/15 15:49:53	1.121
@@ -5,13 +5,13 @@
 
 </style><link rel="stylesheet" href="local.css" type="text/css"/><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-PR.css"/></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"/></a></p>
 <h1><a name="title" id="title"></a>Internationalization Tag Set (ITS) Version 2.0</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Proposed Recommendation 17 September 2013</h2><dl><dt>This version:</dt><dd>
-         <a href="http://www.w3.org/TR/2013/PR-its20-20130917/">
-        http://www.w3.org/TR/2013/PR-its20-20130917/</a>
+<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Proposed Recommendation 19 September 2013</h2><dl><dt>This version:</dt><dd>
+         <a href="http://www.w3.org/TR/2013/PR-its20-20130919/">
+        http://www.w3.org/TR/2013/PR-its20-20130919/</a>
       </dd><dt>Latest version:</dt><dd>
          <a href="http://www.w3.org/TR/its20/">http://www.w3.org/TR/its20/</a>
       </dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2013/WD-its20-20130820/">
-        http://www.w3.org/TR/2013/WD-its20-20130820/</a></dd><dt>Editors:</dt><dd>David Filip, University of Limerick</dd><dd>Shaun McCance, Invited Expert</dd><dd>Dave Lewis, TCD</dd><dd>Christian Lieske, SAP AG</dd><dd>Arle Lommel, DFKI</dd><dd>Jirka Kosek, UEP</dd><dd>Felix Sasaki, DFKI / W3C Fellow</dd><dd>Yves Savourel, ENLASO</dd></dl><p>This document is also available in these non-normative formats: <a href="its20.odd">ODD/XML document</a>, <a href="itstagset20.zip">self-contained zipped archive</a>, and <a href="diffs/diff-wd20130917-wd20130820.html">XHTML Diff markup to previous publication
+        http://www.w3.org/TR/2013/WD-its20-20130820/</a></dd><dt>Editors:</dt><dd>David Filip, University of Limerick</dd><dd>Shaun McCance, Invited Expert</dd><dd>Dave Lewis, TCD</dd><dd>Christian Lieske, SAP AG</dd><dd>Arle Lommel, DFKI</dd><dd>Jirka Kosek, UEP</dd><dd>Felix Sasaki, DFKI / W3C Fellow</dd><dd>Yves Savourel, ENLASO</dd></dl><p>This document is also available in these non-normative formats: <a href="its20.odd">ODD/XML document</a>, <a href="itstagset20.zip">self-contained zipped archive</a>, and <a href="diffs/diff-wd20130919-wd20130820.html">XHTML Diff markup to previous publication
         2013-08-20</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
 <h2><a name="abstract" id="abstract"></a>Abstract</h2><p>The technology described in this document “<em>Internationalization Tag Set (ITS)
         2.0</em>“ enhances the foundation to integrate automated processing of human language
@@ -162,13 +162,13 @@
 <div class="toc1">B <a href="#its-mime-type">Internationalization Tag Set (ITS) MIME Type</a></div>
 <div class="toc1">C <a href="#lqissue-typevalues">Values for the Localization Quality Issue Type</a></div>
 <div class="toc1">D <a href="#its-schemas">Schemas for ITS</a></div>
-<div class="toc1">E <a href="#informative-references">References</a> (Non-Normative)</div>
-<div class="toc1">F <a href="#conversion-to-nif">Conversion to NIF</a> (Non-Normative)</div>
-<div class="toc1">G <a href="#nif-backconversion">Conversion NIF2ITS</a> (Non-Normative)</div>
-<div class="toc1">H <a href="#localization-quality-guidance">Localization Quality Guidance</a> (Non-Normative)</div>
-<div class="toc1">I <a href="#list-of-elements-and-attributes">List of ITS 2.0 Global Elements and Local Attributes</a> (Non-Normative)</div>
-<div class="toc1">J <a href="#revisionlog">Revision Log</a> (Non-Normative)</div>
-<div class="toc1">K <a href="#acknowledgements">Acknowledgements</a> (Non-Normative)</div>
+<div class="toc1">E <a href="#informative-references">Informative References</a></div>
+<div class="toc1">F <a href="#conversion-to-nif">Conversion to NIF</a></div>
+<div class="toc1">G <a href="#nif-backconversion">Conversion NIF2ITS</a></div>
+<div class="toc1">H <a href="#localization-quality-guidance">Localization Quality Guidance</a></div>
+<div class="toc1">I <a href="#list-of-elements-and-attributes">List of ITS 2.0 Global Elements and Local Attributes</a></div>
+<div class="toc1">J <a href="#revisionlog">Revision Log</a></div>
+<div class="toc1">K <a href="#acknowledgements">Acknowledgements</a></div>
 </div><hr/><div class="body"><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="introduction" id="introduction"></a>1 Introduction</h2><p>
             <em>This section is informative.</em>
@@ -2503,7 +2503,7 @@
 <h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="idvalue" id="idvalue"></a>8.14 ID Value</h3><div class="div3">
 <h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="idvalue-definition" id="idvalue-definition"></a>8.14.1 Definition</h4><p>The <a href="#idvalue">ID Value</a> data category indicates a value that can be
               used as unique identifier for a given part of the content.</p><p>The recommended way to specify a unique identifier is to use <code>xml:id</code>
-                  <a title="xml:id Version&#xA;                1.0" href="#xml-id">[XML ID]</a> or <code>id</code> in HTML (See the best
+                  <a title="xml:id Version&#xA;              1.0" href="#xml-id">[XML ID]</a> or <code>id</code> in HTML (See the best
               practice “<a href="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#DevUniqueID">Defining
                   markup for unique identifiers</a>” from <a title="Best&#xA;                Practices for XML Internationalization" href="#xml-i18n-bp">[XML i18n BP]</a>). The <code class="its-elem-markup">idValueRule</code> element is intended only as a fall-back
               mechanism for documents in which unique identifiers are available with another
@@ -3178,7 +3178,10 @@
             editors. <a href="http://www.w3.org/TR/2006/REC-xml-20060816/"><cite>Extensible Markup Language
                 (XML) 1.0 (Fifth Edition)</cite></a>, W3C Recommendation 26 November 2008. Available at <a href="http://www.w3.org/TR/2008/REC-xml-20081126/">
               http://www.w3.org/TR/2008/REC-xml-20081126//</a>. The latest version of <a href="http://www.w3.org/TR/xml/">XML 1.0</a> is available at
-            http://www.w3.org/TR/xml/.</dd><dt class="label"><a name="xmlinfoset" id="xmlinfoset"/>XML Infoset</dt><dd>John Cowan, Richard Tobin. <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>XML Information Set
+            http://www.w3.org/TR/xml/.</dd><dt class="label"><a name="xml-id" id="xml-id"/>XML ID</dt><dd>Jonathan Marsh, Daniel Veillard, Norman Walsh.
+            <a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/"><cite>xml:id Version
+              1.0</cite></a>. W3C Recommendation 9 September 2005. Available at <a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/">http://www.w3.org/TR/2005/REC-xml-id-20050909/</a>. The latest version of <a href="http://www.w3.org/TR/xml-id/">xml:id Version 1.0</a> is available at
+            http://www.w3.org/TR/xml-id/.</dd><dt class="label"><a name="xmlinfoset" id="xmlinfoset"/>XML Infoset</dt><dd>John Cowan, Richard Tobin. <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>XML Information Set
                 (Second Edition)</cite></a>. W3C Recommendation 4 February 2004. Available at <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">
               http://www.w3.org/TR/2004/REC-xml-infoset-20040204/</a>. The latest version of <a href="http://www.w3.org/TR/xml-infoset/">XML Infoset</a> is available at
             http://www.w3.org/TR/xml-infoset/.</dd><dt class="label"><a name="xmlns" id="xmlns"/>XML Names</dt><dd>Tim Bray, Dave Hollander, Andrew Layman, Richard Tobin. <a href="http://www.w3.org/TR/2006/REC-xml-names-20060816/"><cite>Namespaces in XML
@@ -3191,10 +3194,7 @@
             available at http://www.w3.org/TR/xmlschema-1/.</dd><dt class="label"><a name="xmlschema2" id="xmlschema2"/>XML Schema Part 2</dt><dd>Paul V. Biron, Ashok Malhotra. <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>XML Schema Part 2:
                 Datatypes Second Edition</cite></a>. W3C Recommendation 28 October 2004. Available at <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
               http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>. The latest version of <a href="http://www.w3.org/TR/xmlschema-2/">XML Schema</a> is
-            available at http://www.w3.org/TR/xmlschema-2/.</dd><dt class="label"><a name="xml-id" id="xml-id"/>XML ID</dt><dd>Jonathan Marsh, Daniel Veillard, Norman Walsh.
-                <a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/"><cite>xml:id Version
-                1.0</cite></a>. W3C Recommendation 9 September 2005. Available at <a href="http://www.w3.org/TR/2005/REC-xml-id-20050909/">http://www.w3.org/TR/2005/REC-xml-id-20050909/</a>. The latest version of <a href="http://www.w3.org/TR/xml-id/">xml:id Version 1.0</a> is available at
-            http://www.w3.org/TR/xml-id/.</dd><dt class="label"><a name="xpath" id="xpath"/>XPath 1.0</dt><dd>James Clark. <a href="http://www.w3.org/TR/1999/REC-xpath-19991116/"><cite>XML Path Language (XPath)
+            available at http://www.w3.org/TR/xmlschema-2/.</dd><dt class="label"><a name="xpath" id="xpath"/>XPath 1.0</dt><dd>James Clark. <a href="http://www.w3.org/TR/1999/REC-xpath-19991116/"><cite>XML Path Language (XPath)
                 Version 1.0</cite></a>. W3C Recommendation 16 November 1999. Available at <a href="http://www.w3.org/TR/1999/REC-xpath-19991116/">
               http://www.w3.org/TR/1999/REC-xpath-19991116/</a>. The latest version of <a href="http://www.w3.org/TR/xpath/">XPath 1.0</a> is available at
             http://www.w3.org/TR/xpath/ .</dd></dl></div><div class="div1">
@@ -5556,7 +5556,9 @@
                      <a href="schemas/its20-types.xsd">its20-types.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
+<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 Informative References</h2><p>
+            <em>This section is informative.</em>
+         </p><dl><dt class="label"><a name="bidiarticle" id="bidiarticle"/>Bidi Article</dt><dd>Richard Ishida. <a href="http://www.w3.org/International/articles/inline-bidi-markup/"><cite>What you
                 need to know about the bidi algorithm and inline markup</cite></a>. Article of
             the <a href="http://www.w3.org/International/">W3C Internationalization
               Activity</a>, June 2005.</dd><dt class="label"><a name="charmod-norm" id="charmod-norm"/>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/"><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/">http://www.w3.org/TR/2012/WD-charmod-norm-20120501/</a>. The latest version of <a href="http://www.w3.org/TR/charmod-norm/">Charmod Norm</a> is available at http://www.w3.org/TR/charmod-norm/ .</dd><dt class="label"><a name="checkmate" id="checkmate"/>CheckMate Quality Check</dt><dd>Okapi Project. <a href="http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration"><cite>CheckMate – Quality Check Configuration</cite></a>. Available at <a href="http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Cofiguration">http://www.opentag.com/okapi/wiki/index.php?title=CheckMate_-_Quality_Check_Configuration</a>.</dd><dt class="label"><a name="css2-1" id="css2-1"/>CSS 2.1</dt><dd> Bert Bos, Tantek Çelik, Ian Hickson Håkon Wium Lie. <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/"><cite>Cascading Style Sheets,
@@ -5569,7 +5571,7 @@
               https://www.oasis-open.org/committees/download.php/15316/dita10.zip</a>.</dd><dt class="label"><a name="docbook" id="docbook"/>DocBook</dt><dd>Norman Walsh and Leonard Muellner. <a href="http://www.docbook.org/"><cite>DocBook: The Definitive Guide</cite></a>. Available at <a href="http://www.docbook.org/">
               http://www.docbook.org/</a>.</dd><dt class="label"><a name="geo-i18n-l10n" id="geo-i18n-l10n"/>l10n i18n</dt><dd>Richard Ishida, Susan Miller. <a href="http://www.w3.org/International/questions/qa-i18n">Localization vs.
               Internationalization</a>. Article of the <a href="http://www.w3.org/International/">W3C Internationalization Activity</a>,
-            January 2006.</dd><dt class="label"><a name="microdata" id="microdata"/>Microdata</dt><dd>Ian Hickson <a href="http://www.w3.org/TR/microdata/"><cite>HTML Microdata</cite></a>. W3C Working Draft 25 October 2012. Available at <a href="http://www.w3.org/TR/2012/WD-microdata-20121025/">http://www.w3.org/TR/2012/WD-microdata-20121025/</a>. </dd><dt class="label"><a name="iso30042" id="iso30042"/>ISO 30042</dt><dd>(International Organization for Standardization).
+            January 2006.</dd><dt class="label"><a name="iso30042" id="iso30042"/>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"/>ISO/TS 11669:2002</dt><dd>(International Organization for
             Standardization). <cite>Translation projects – General guidance</cite>. [Geneva]:
@@ -5578,7 +5580,7 @@
                 Localization Markup Requirements</cite></a>. W3C Working Draft 18 May 2006. Available at <a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/">
               http://www.w3.org/TR/2006/WD-itsreq-20060518/</a>. The latest version of <a href="http://www.w3.org/TR/itsreq/">ITS REQ</a> is available at
             http://www.w3.org/TR/itsreq/.</dd><dt class="label"><a name="reqlocdtd" id="reqlocdtd"/>Localizable DTDs</dt><dd>Richard Ishida, Yves Savourel <a href="http://people.w3.org/rishida/localizable-dtds/"><cite>Requirements for Localizable
-                DTD Design</cite></a>. Working Draft 7 July 2003. Available at <a href="http://people.w3.org/rishida/localizable-dtds/">http://people.w3.org/rishida/localizable-dtds/</a>. </dd><dt class="label"><a name="mlw-metadata-us-impl" id="mlw-metadata-us-impl"/>MLW US IMPL</dt><dd>Christian Lieske (ed.). <a href="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/"><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/">http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/</a>. The latest version of <a href="http://www.w3.org/TR/mlw-metadata-us-impl/">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"/>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/">http://people.w3.org/rishida/localizable-dtds/</a>. </dd><dt class="label"><a name="microdata" id="microdata"/>Microdata</dt><dd>Ian Hickson <a href="http://www.w3.org/TR/microdata/"><cite>HTML Microdata</cite></a>. W3C Working Draft 25 October 2012. Available at <a href="http://www.w3.org/TR/2012/WD-microdata-20121025/">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"/>MLW US IMPL</dt><dd>Christian Lieske (ed.). <a href="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/"><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/">http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/</a>. The latest version of <a href="http://www.3.org/TR/mlw-metadata-us-impl/">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"/>NERD</dt><dd>Named Entity Recognition and Disambiguation ontology (NERD)
             available at: <a href="http://nerd.eurecom.fr/ontology">http://nerd.eurecom.fr/ontology</a>
             </dd><dt class="label"><a name="nif-reference" id="nif-reference"/>NIF</dt><dd>Hellmann, S. et al. (ed.). <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#">NIF 2.0 Core Ontology</a>, as of August 2013. Available at <a href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#">http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#</a> under CC-BY 3.0  license maintained by the <a href="http://nlp2rdf.org">NLP2RDF project</a>.</dd><dt class="label"><a name="nvdl" id="nvdl"/>NVDL</dt><dd>Information technology – Document Schema Definition
             Languages (DSDL) – Part 4: <cite>Namespace-based Validation Dispatching Language
@@ -5616,7 +5618,9 @@
             http://www.w3.org/TR/xslt.</dd><dt class="label"><a name="xul" id="xul"/>XUL</dt><dd>
                <a href="http://www.xulplanet.com/"><cite>exTensible User Interface Language</cite></a>. Available at <a href="http://www.xulplanet.com/">
               http://www.xulplanet.com/</a>.</dd></dl></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="conversion-to-nif" id="conversion-to-nif"></a>F Conversion to NIF (Non-Normative)</h2><p>This section provides an informative algorithm to convert XML or HTML documents (or their DOM
+<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="conversion-to-nif" id="conversion-to-nif"></a>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">[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">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
@@ -5738,7 +5742,9 @@
             dereferenceablility. The future definition and registration of these 
             fragment types, while a potentially  attractive feature, is beyond the 
             scope of this specification.</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="nif-backconversion" id="nif-backconversion"></a>G Conversion NIF2ITS (Non-Normative)</h2><p>The following algorithm relies on <a href="#EX-HTML-whitespace-normalization">Example 97</a>. It is assumed that the example has been
+<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="nif-backconversion" id="nif-backconversion"></a>G Conversion NIF2ITS</h2><p>
+            <em>This section is informative.</em>
+         </p><p>The following algorithm relies on <a href="#EX-HTML-whitespace-normalization">Example 97</a>. It is assumed that the example has been
           converted to NIF, leading to the <a href="examples/nif/EX-nif-conversion-output.ttl">output</a> exemplified for the <a href="#its2nif-algorithm">ITS2NIF conversion
             algorithm</a>.</p><p>This example uses <a href="https://github.com/dbpedia-spotlight/dbpedia-spotlight">DBpedia
             Spotlight</a> as an example natural language processing (NLP) tool. In it, DBpedia
@@ -5797,8 +5803,12 @@
 &lt;/html&gt;</pre></div></div><p>Case 3: The NLP annotation created in NIF starts in one region and ends in another.
           Solution: No straight mapping is possible; a mapping can be created if both regions have
           the same parent.</p></div><div class="div1">
-<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="localization-quality-guidance" id="localization-quality-guidance"></a>H Localization Quality Guidance (Non-Normative)</h2><p>The <a href="#lqissue">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 pparent 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 provide 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 usd. 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. Review 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 ma 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 to consult the ISO standard definition of translation project specifications included in <a title="Translation projects – General guidance" href="#isots11669">[ISO/TS 11669:2002]</a>. Details about translation specifications are available at <a title="Structured Specifications and Translation Parameters" href="#structuredspecs">[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) framewor. 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 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"><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"></a>I List of ITS 2.0 Global Elements and Local Attributes (Non-Normative)</h2><p>The following table lists global ITS 2.0 elements inside <code class="its-elem-markup">rules</code> element and local
+<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="localization-quality-guidance" id="localization-quality-guidance"></a>H Localization Quality Guidance</h2><p>
+            <em>This section is informative.</em>
+         </p><p>The <a href="#lqissue">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 provide specific rference 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. Review may be tid 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 to consult the SO standard definition of translation project specifications included in <a title="Translation projects – General guidance" href="#isots11669">[ISO/TS 11669:2002]</a>. Details about translation specifications are available at <a title="Structured Specifications and Translation Parameters" href="#structuredspecs">[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 interoperability needs. For situations requirin additional expressive capability or categories, further custom markup may be required.</p></div><div class="div1">
+<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="list-of-elements-and-attributes" id="list-of-elements-and-attributes"></a>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
           ITS 2.0 markup in XML and HTML. Note that for the local markup there are various
           constraints on what local attributes can be used together. Here these constraints are
           expressed via occurrence indicators: optional "?", alternatives "|", or
@@ -5956,7 +5966,9 @@
               <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>J Revision Log (Non-Normative)</h2><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/">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">mail thread</a>.</p></li><li><p>Edits in <a class="section-ref" href="#lqissue">Section 8.16: Localization Quality Issue</a> and <a class="section-ref" href="#lqissue-typevalues">Appendix C: Values for the Localization Quality Issue Type</a> (plus a new informative <a class="section-ref" href="#localization-quality-guidance">Appendix H: Localization Quality Guidance</a>) to clarify the <a hrf="#lqissue">Localization Quality Issue</a> data category, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/132">issue-132</a>.</p></li><li><p>Edits in <a class="section-ref" href="#conversion-to-nif">Appendix F: Conversion to NIF</a> and <a class="section-ref" href="#nif-backconversion">Appendix G: Conversion NIF2ITS</a> to resolve <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/131">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/">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>J Revision Log</h2><p>
+            <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/">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">mail thread</a>.</p></li><li><p>Edits in <a class="section-ref" href="#lqissue">Section 8.16: Localization Quality Issue</a> and <a class="section-ref" href="#lqissue-typevalues">Appendix C: Values for the Localization Quality Issue Type</a> (plus a new informative <a class="section-ref" href="#localization-quality-guidance">Appendix H: Localization Quality Guidance</a>) to clarify the <a href="#lqissue">Localization Quality Issue</a> data category, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/132">issue-132</a>.</p></li><li><p>Edits in <a class="section-ref" href="#conversion-to-nif">Appedix F: Conversion to NIF</a> and <a class="section-ref" href="#nif-backconversion">Appendix G: Conversion NIF2ITS</a> to resolve <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/131">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/">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.
             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&amp;index-type=t&amp;keywords=action-502&amp;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><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">Section 5.5: Precedence between Selections</a> and <a class="section-ref" href="#html5-selection-precedence">Section 6.4: Precedence between Selections</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/130">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/2013Jul/0041.html">editorial edits</a> in <a class="section-ref" href="#idvalue">Section 8.14: ID Value</a> and <a class="section-ref" href="#locNote-datacat">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">clrification</a> about <code class="its-attr-markup">annotatorsRef</code> attribute in <a class="section-ref" href="#its-tool-annotation">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">clarification</a> in <a class="section-ref" href="#mtconfidence-definition">Section 8.18.1: Definition</a> and added <a href="#mt-confidence-score-generation-tools">a note</a> that <a href="#mtconfidence">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">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/">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#">IT 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">Appendix F: 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">Appendix F: 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-mappings">clarification</a> about the role of mappings from tools to quality issue types,
@@ -6032,6 +6044,6 @@
           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 40</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">Appendix F: 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>K Acknowledgements (Non-Normative)</h2><p>This document has been developed with contributions by the
+<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>K Acknowledgements</h2><p>This document has been developed with contributions by the
           <a href="http://www.w3.org/International/multilingualweb/lt/">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 College Dublin), Mathias 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, Government of Inia), 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), Ronny Unger (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">[NIF]</a> and for contributing to the creation of the <a href="http://www.w3.org/2005/11/its/rdf#">ITS 2.0 ontology</a> and NIF testing.</p></li><li><p>Daniel Naber for introducing us to <a href="http://languagetool.org">LanguageTool</a> and for implementing <a href="#lqissue-typevalues">Localization Quality Issue Type</a> functionality in language tool.</p></li></ul></div></div></body></html>
\ No newline at end of file
Received on Sunday, 15 September 2013 15:49:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:43 UTC