CVS WWW/International/multilingualweb/lt/drafts/its20 from CVS User fsasaki on 2013-06-24 (public-multilingualweb-lt-commits@w3.org from June 2013)

From: CVS User fsasaki <cvsmail@w3.org>
Date: Mon, 24 Jun 2013 17:47:59 +0000
To: public-multilingualweb-lt-commits@w3.org
Message-Id: <E1UrArv-0000uz-Ik@gil.w3.org>
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv3098

Modified Files:
	its20.html its20.odd 
Log Message:
link fix

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/06/24 17:37:35	1.469
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/06/24 17:47:59	1.470
@@ -537,7 +537,7 @@
 <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 defines an algorithm to convert XML or HTML documents (or their DOM
         representations) that contain ITS metadata to the RDF format based on <a title="" href="#nif-reference" 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. 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 53</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 XLIFFtherefore unpins 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="@@@@" 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-us-impl" shape="rect">[MLW US IMPL]</a for more information).</p></div></div><div class="div1">
+<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/finnle/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-metadat-us-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>
             <em>This section is normative.</em>
          </p><div class="div2">
@@ -1516,7 +1516,7 @@
                 <code>&lt;its:translateRule selector=""//h:img" translate="yes"/&gt;</code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></div><p id="translate-global">GLOBAL: The <code class="its-elem-markup">translateRule</code> element contains the
               following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors" shape="rect">absolute selector</a> that selects the nodes to which this
                 rule applies.</p></li><li><p>A required <code class="its-attr-markup">translate</code> attribute with the value
-    "yes" or "no".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-1" id="EX-translate-selector-1" shape="rect"/>Example 28: The <a href="#trans-datacat" shape="rect">Translate</a> data category expressed
+                  "yes" or "no".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-1" id="EX-translate-selector-1" shape="rect"/>Example 28: The <a href="#trans-datacat" shape="rect">Translate</a> data category expressed
                 globally</div><p>The <code class="its-elem-markup">translateRule</code> element specifies that the elements <code>code</code>
                 is not to be translated.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096">&lt;its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
   <strong class="hl-tag" style="color: #000096">&lt;its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//code"</span><strong class="hl-tag" style="color: #000096">/&gt;</strong>
@@ -6005,7 +6005,7 @@
             to <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.2: Local Selection in an XML Document</a>.</p></li><li><p>Added definition of <code class="its-elem-markup">param</code> element to <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>.</p></li><li><p>Added <a class="section-ref" href="#target-pointer" shape="rect">Section 8.13: Target Pointer</a>.</p></li><li><p>Original Ruby markup model changed to HTML5 Ruby model.</p></li><li><p>Updated references.</p></li><li><p>Added <a class="section-ref" href="#preservespace" shape="rect">Section 8.15: Preserve Space</a>.</p></li><li><p>Added <a class="section-ref" href="#lqissue" shape="rect">Section 8.16: Localization Quality Issue</a> and the related <a class="section-ref" href="#lqissue-typevalues" shape="rect">Appendix C: Values for the Localization Quality Issue Type</a>.</p></li><li><p>Added <a class="section-ref" href="#lqrating" shape="rect">Section 8.17: Loclization Quality Rating</a>.</p></li><li><p>Added a placeholder <a class="section-ref" href="#mtconfidence" shape="rect">Section 8.18: MT Confidence</a>.</p></li></ol><p id="changelog-since-20120626">The following log records major changes that have been
           made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20120626/" shape="rect">ITS 2.0 Working Draft 26 June 2012</a>:</p><ol class="depth1"><li><p>Various editorial changes (non-normative references update, style &amp; grammar
             fixes).</p></li><li><p>Made clarifications about what is out of scope of ITS 2.0 and about design decisions.</p></li><li><p>Added explanatory note on precedence and overriding in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</a>.</p></li><li><p>Reordered some components in <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a>.</p></li><li><p>Restructured description of relation to ITS 1.0 and new principles in <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a>.</p></li><li><p>Added <a class="section-ref" href="#queryLanguage" shape="rect">Section 5.3.1: Choosing Query Language</a> as a stub.</p></li><li><p>Added <a class="section-ref" href="#LocaleFilter" shape="rect">Section 8.10: Locale Filter</a>.</p></li><li><p>Added <a class="section-ref" href="#domain" shape="rect">Section 8.8: Domain</a>.</p></li><li><p>Added <a class="section-ref" href="#usage-in-legacy-htl" shape="rect">Section 2.5.5: Version of HTML</a>.</p></li><li><p>Added local markup in <a class="section-ref" href="#elements-within-text" shape="rect">Section 8.7: Elements Within Text</a>.</p></li><li><p>Added <a class="section-ref" href="#externalresource" shape="rect">Section 8.12: External Resource</a>.</p></li><li><p>Updated examples to use the <code class="its-attr-markup">version</code> attribute with the value
-              <code>2.0</code>.</p></li></ol><p id="changelog-since-20070403">The following log records major changes that have been
+    <code>2.0</code>.</p></li></ol><p id="changelog-since-20070403">The following log records major changes that have been
           made to this document between the <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0 Recommendation</a> and
           this document:</p><ol class="depth1"><li><p>Clarified <a href="#introduction" shape="rect">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
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/06/24 17:37:36	1.480
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/06/24 17:47:59	1.481
@@ -90,7 +90,7 @@
         Natural Language Processing Interchange Format (NIF).</p>
       <p>This document was published by the <loc
           href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
-        Group</loc> as a Proposed Recommendation Working Draft. Comments submitted against the <loc href="http://www.w3.org/TR/2013/WD-its20-20130521/">second Last Call specification</loc> are consolidated in a <loc href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html">comment tracking document</loc>. All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <loc href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</loc> and created an <loc href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</loc> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
+        Group</loc> as a Proposed Recommendation. Comments submitted against the <loc href="http://www.w3.org/TR/2013/WD-its20-20130521/">second Last Call specification</loc> are consolidated in a <loc href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html">comment tracking document</loc>. All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <loc href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</loc> and created an <loc href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</loc> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
         document to Recommendation status (see <loc
           href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
           maturity levels</loc>).</p>
@@ -795,7 +795,7 @@
             <item>Conformance clauses in <ptr type="specref" target="#conformance-product-html-processing-expectations"/> tell implementers how to process <ptr target="#html5" type="bibref"/> content.</item>
             <item>Conformance clauses in <ptr target="#conformance-product-html5-its" type="specref"/> tell implementers how ITS 2.0 markup is integrated into <ptr type="bibref" target="#html5"/>.</item>
           </list>
-          <p>The conformance clauses in <ptr target="#conformance-product-processing-expectations" type="specref"/> and <ptr type="specref" target="#conformance-product-html-processing-expectations"/> 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 <ref target="@@@@">ITS 2.0 test suite</ref>.</p>
+          <p>The conformance clauses in <ptr target="#conformance-product-processing-expectations" type="specref"/> and <ptr type="specref" target="#conformance-product-html-processing-expectations"/> 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 <ref target="https://github.com/finnle/ITS-2.0-Testsuite/">ITS 2.0 test suite</ref>.</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 <ptr type="bibref" target="#mlw-metadata-us-impl"/> for more information).</p>
         </div>
       </div>
Received on Monday, 24 June 2013 17:48:01 UTC