- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 24 Jun 2013 17:48:00 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version
In directory gil:/tmp/cvs-serv3098/TR-version
Modified Files:
Overview.html
Log Message:
link fix
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/06/24 17:37:36 1.93
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/TR-version/Overview.html 2013/06/24 17:47:59 1.94
@@ -32,7 +32,7 @@
Web content. ITS 2.0 focuses on HTML, XML-based formats in general, and can leverage
processing based on the XML Localization Interchange File Format (XLIFF), as well as the
Natural Language Processing Interchange Format (NIF).</p><p>This document was published by the <a href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT Working
- Group</a> as a Proposed Recommendation Working Draft. Comments submitted against the <a href="http://www.w3.org/TR/2013/WD-its20-20130521/">second Last Call specification</a> are consolidated in a <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html">comment tracking document</a>. All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <a href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</a> and created an <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</a> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
+ Group</a> as a Proposed Recommendation. Comments submitted against the <a href="http://www.w3.org/TR/2013/WD-its20-20130521/">second Last Call specification</a> are consolidated in a <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/disposition-of-comments-2nd-last-call.html">comment tracking document</a>. All of the comments resulted in non-normative changes to the specification. The Working Group has completed and approved this specification's <a href="https://github.com/finnle/ITS-2.0-Testsuite/">Test Suite</a> and created an <a href="http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20-implementation-report.html">Implementation Report</a> that shows that two or more independent implementations pass each test. The Working Group expects to advance this
document to Recommendation status (see <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C document
maturity levels</a>).</p><p> The W3C Membership and other interested parties are invited to review the document and send comments to <a href="mailto:public-multilingualweb-lt-comments@w3.org">public-multilingualweb-lt-comments@w3.org</a>. Use "Comment on ITS 2.0 specification
WD" in the subject line of your email. The <a href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/">archives
@@ -560,7 +560,7 @@
<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-NIF" id="mapping-NIF"></a>2.7.1 ITS and RDF/NIF</h4><p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
representations) that contain ITS metadata to the RDF format based on <a title="" href="#nif-reference">[NIF]</a>. NIF is an RDF/OWL-based format that aims at interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion from <a href="#conversion-to-nif">ITS 2.0 to NIF</a> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content-related triples and relies on an <a href="http://www.w3.org/2005/11/its/rdf#">ITS RDF vocabulary</a>.</p><p>The back conversion from <a href="#nif-backconversion">NIF to ITS 2.0</a> is defined informatively. One motivation for the back conversion is a roundtrip workflow like: 1) conversion to NIF 2) in NIF representation detection of named entities using NLP tools 3) back conversion to HTML and generation of <a href="#textanalysis">Text Analysis</a> markup. The outcome are HTML documents with liked information, see <a href="#EX-text-analysis-html5-local-1">Example 53</a>.</p></div><div class="div3">
<h4><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="mapping-XLIFF" id="mapping-XLIFF"></a>2.7.2 ITS and XLIFF</h4><p>The XML Localization Interchange File Format <a title="XLIFF Version 1.2" href="#xliff1.2">[XLIFF 1.2]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localization and translation workflows. <a title="XLIFF Version 2.0" href="#xliff2.0">[XLIFF 2.0]</a> is the successor of <a title="XLIFF Version 1.2" href="#xliff1.2">[XLIFF 1.2]</a> and under development. XLIFF has been widely implemented in various translation management systems, computer aided translation tools and in utilities for extracting translatable content from source documents and merging back the content in the target language..</p><p>The mapping between ITS and XLIFF therefore unpins several important ITS 2.0 usage scenarios <atitle="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl">[MLW US IMPL]</a>. These usage scenarios involve:</p><ul><li><p>the extraction of ITS metadata from a source language file into XLIFF</p></li><li><p>the addition of ITS metadata into an XLIFF file by translation tools</p></li><li><p>the mapping of ITS metadata in an XLIFF file into ITS metadata in the resulting target language files.</p></li></ul><p>ITS 2.0 has no normative dependency on XLIFF, however a <a href="http://www.w3.org/International/its/wiki/XLIFF_Mapping">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</a> is being defined within the <a href="http://www.w3.org/International/its/ig/">Internationalization Tag Set Interest Group</a>.</p></div></div><div class="div2">
-<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="implementing-its20" id="implementing-its20"></a>2.8 ITS 2.0 Implementations and Conformance</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer (see <a class="section-ref" href="#conformance">Section 4: Conformance</a>). The clauses target different types of implementers:</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> tell implementers how to process XML content accordng to ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html5-its">Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> clarify how information needs to be made available for iven pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <a href="@@@@">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually is to be used. This is due to the fact that there is a wide variety of usage scenarios for ITS 2.0, and a wide variety of tools for working with ITS 2.0 is possible. Each of these tools may have its own way of using ITS 2.0 data categories (see <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl">[MLW US IMPL]</a> for more information).</p></div></div><div class="div1">
+<h3><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="implementing-its20" id="implementing-its20"></a>2.8 ITS 2.0 Implementations and Conformance</h3><p>What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the normative answer (see <a class="section-ref" href="#conformance">Section 4: Conformance</a>). The clauses target different types of implementers:</p><ul><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-schema">Section 4.1: Conformance Type 1: ITS Markup Declarations</a> tell markup vocabulary developers how to add ITS 2.0 markup declarations to their schemas.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> tell implementers how to process XML content accordng to ITS 2.0 data categories.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html-processing-expectations">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> tell implementers how to process <a title="HTML5" href="#html5">[HTML5]</a> content.</p></li><li><p>Conformance clauses in <a class="section-ref" href="#conformance-product-html5-its">Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents</a> tell implementers how ITS 2.0 markup is integrated into <a title="HTML5" href="#html5">[HTML5]</a>.</p></li></ul><p>The conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a> and <a class="section-ref" href="#conformance-product-html-processing-expectations">Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in HTML</a> clarify how information needs to be made available for iven pieces of markup when processing a dedicated ITS 2.0 data category. To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are reflected in separate conformance clauses and also in the <a href="https://github.com/finnle/ITS-2.0-Testsuite/">ITS 2.0 test suite</a>.</p><p>ITS 2.0 processing expectations only define which information needs to be made available. They do not define how that information actually is to be used. This is due to the fact that there is a wide variety of usage scenarios for ITS 2.0, and a wide variety of tools for working with ITS 2.0 is possible. Each of these tools may have its own way of using ITS 2.0 data categories (see <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl">[MLW US IMPL]</a> for more information).</p></div></div><div class="div1">
<h2><a href="#contents"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="notation-terminology" id="notation-terminology"></a>3 Notation and Terminology</h2><p>
<em>This section is normative.</em>
</p><div class="div2">
@@ -1538,8 +1538,7 @@
attributes. The default is that elements are translatable and attributes are not.</p><p id="html5-translate-handling">For HTML: The interpretation of the <code class="its-attr-markup">translate</code> attribute is given in <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">HTML5</a>. Nodes in an HTML document selected via a <a href="#translate-global">global rule</a> are also interpreted following <a href="http://www.w3.org/TR/html51/dom.html#the-translate-attribute">HTML5</a>.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>As of writing, the default in <a title="HTML5" href="#html5">[HTML5]</a> is that elements are translatable, and that translatable attributes inherit from the respective elements. There is a pre-defined list of translatable attributes, for example <code>alt</code> or <code>title</code>.</p><p>Since the <a title="HTML5" href="#html5">[HTML5]</a> definition also applies to nodes selected via global rules, a <code class="its-elem-markup">translatRule</code> like
<code><its:translateRule selector=""//h:img" translate="yes"/></code> will set the <code>img</code> element and its translatable attributes like <code>alt</code> to "yes".</p></div><p id="translate-global">GLOBAL: The <code class="its-elem-markup">translateRule</code> element contains the
following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors">absolute selector</a> that selects the nodes to which this
- rule applies.</p></li><li><p>A required <code class="its-attr-markup">translate</code> attribute with the value
- "yes" or "no".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-1" id="EX-translate-selector-1"></a>Example 28: The <a href="#trans-datacat">Translate</a> data category expressed
+ rule applies.</p></li><li><p>A required <code class="its-attr-markup">translate</code> attribute with the value"yes" or "no".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-selector-1" id="EX-translate-selector-1"></a>Example 28: The <a href="#trans-datacat">Translate</a> data category expressed
globally</div><p>The <code class="its-elem-markup">translateRule</code> element specifies that the elements <code>code</code>
is not to be translated.</p><div class="exampleInner"><pre><strong class="hl-tag" style="color: #000096"><its:rules</strong> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//code"</span><strong class="hl-tag" style="color: #000096">/></strong>
Received on Monday, 24 June 2013 17:48:01 UTC