- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 14 Oct 2013 07:50:59 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv24477
Modified Files:
its20.html its20.odd
Log Message:
spell fix and commmitting latest diffs
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/09/22 17:28:03 1.503
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/10/14 07:50:58 1.504
@@ -541,7 +541,7 @@
<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">
-<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 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">
+<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>
<em>This section is normative.</em>
@@ -3467,12 +3467,7 @@
schema</a>)</p></div><p>
<em>3. Base RELAX NG schema for ITS</em>: All ITS elements and attributes referenced
by previous two schemas are defined in the base RELAX NG schema for ITS. </p><div class="exampleOuter"><div class="exampleHeader"><a name="its20.rng" id="its20.rng" shape="rect"/>Example 94: Base RELAX NG schema for ITS</div><div class="exampleInner"><pre xml:space="preserve"><span class="hl-directive" style="color: maroon"><?xml version="1.0" encoding="UTF-8"?></span>
-<strong class="hl-tag" style="color: #000096"><grammar</strong> <span class="hl-attribute" style="color: #F5844C">ns</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span>
- <span class="hl-attribute" style="color: #F5844C">xmlns:a</span>=<span class="hl-value" style="color: #993300">"http://relaxng.org/ns/compatibility/annotations/1.0"</span>
- <span class="hl-attribute" style="color: #F5844C">xmlns:xlink</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xlink"</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>
- <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://relaxng.org/ns/structure/1.0"</span>
- <span class="hl-attribute" style="color: #F5844C">datatypeLibrary</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2001/XMLSchema-datatypes"</span><strong class="hl-tag" style="color: #000096">></strong>
+<strong class="hl-tag" style="color: #000096"><grammar</strong> <span class="hl-attribute" style="color: #F5844C">ns</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:a</span>=<span class="hl-value" style="color: #993300">"http://relaxng.org/ns/compatibility/annotations/1.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:xlink</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/1999/xlink"</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> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://relaxng.org/ns/structure/1.0"</span> <span class="hl-attribute" style="color: #F5844C">datatypeLibrary</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2001/XMLSchema-datatypes"</span><strong lass="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><include</strong> <span class="hl-attribute" style="color: #F5844C">href</span>=<span class="hl-value" style="color: #993300">"its20-types.rng"</span><strong class="hl-tag" style="color: #000096">/></strong>
<strong class="hl-tag" style="color: #000096"><define</strong> <span class="hl-attribute" style="color: #F5844C">name</span>=<span class="hl-value" style="color: #993300">"its-attribute.translate"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><attribute</strong> <span class="hl-attribute" style="color: #F5844C">name</span>=<span class="hl-value" style="color: #993300">"its:translate"</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -5087,10 +5082,7 @@
</pre></div><p>[Source file: <a href="schemas/its20.rng" shape="rect">schemas/its20.rng</a>]</p><p>(<a href="schemas/its20.rnc" shape="rect">RELAX NG compact syntax version of schema</a>)</p></div><p>
<em>4. Data type definitions</em>: All datatypes used in the base RELAX NG schema are
defined the following schema. </p><div class="exampleOuter"><div class="exampleHeader"><a name="its20-types.rng" id="its20-types.rng" shape="rect"/>Example 95: RELAX NG schema with datatypes for ITS</div><div class="exampleInner"><pre xml:space="preserve"><span class="hl-directive" style="color: maroon"><?xml version="1.0" encoding="UTF-8"?></span>
-<strong class="hl-tag" style="color: #000096"><grammar</strong>
- <span class="hl-attribute" style="color: #F5844C">xmlns:a</span>=<span class="hl-value" style="color: #993300">"http://relaxng.org/ns/compatibility/annotations/1.0"</span>
- <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://relaxng.org/ns/structure/1.0"</span>
- <span class="hl-attribute" style="color: #F5844C">datatypeLibrary</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2001/XMLSchema-datatypes"</span><strong class="hl-tag" style="color: #000096">></strong>
+<strong class="hl-tag" style="color: #000096"><grammar</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:a</span>=<span class="hl-value" style="color: #993300">"http://relaxng.org/ns/compatibility/annotations/1.0"</span> <span class="hl-attribute" style="color: #F5844C">xmlns</span>=<span class="hl-value" style="color: #993300">"http://relaxng.org/ns/structure/1.0"</span> <span class="hl-attribute" style="color: #F5844C">datatypeLibrary</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2001/XMLSchema-datatypes"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><define</strong> <span class="hl-attribute" style="color: #F5844C">name</span>=<span class="hl-value" style="color: #993300">"its-version.type"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><a:documentation></strong>Version of ITS<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
<strong class="hl-tag" style="color: #000096"><data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"string"</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -5125,8 +5117,7 @@
<strong class="hl-tag" style="color: #000096"></data></strong>
<strong class="hl-tag" style="color: #000096"></define></strong>
<strong class="hl-tag" style="color: #000096"><define</strong> <span class="hl-attribute" style="color: #F5844C">name</span>=<span class="hl-value" style="color: #993300">"its-translate.type"</span><strong class="hl-tag" style="color: #000096">></strong>
- <strong class="hl-tag" style="color: #000096"><a:documentation></strong>The Translate data category information
- to be attached to the current node<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
+ <strong class="hl-tag" style="color: #000096"><a:documentation></strong>The Translate data category information to be attached to the current node<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
<strong class="hl-tag" style="color: #000096"><choice></strong>
<strong class="hl-tag" style="color: #000096"><value></strong>yes<strong class="hl-tag" style="color: #000096"></value></strong>
<strong class="hl-tag" style="color: #000096"><a:documentation></strong>The nodes need to be translated<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
@@ -5181,14 +5172,11 @@
<strong class="hl-tag" style="color: #000096"><a:documentation></strong>States whether current context is regarded as "within text"<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
<strong class="hl-tag" style="color: #000096"><choice></strong>
<strong class="hl-tag" style="color: #000096"><value></strong>yes<strong class="hl-tag" style="color: #000096"></value></strong>
- <strong class="hl-tag" style="color: #000096"><a:documentation></strong>The element and its content are part of the flow of
- its parent element<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
+ <strong class="hl-tag" style="color: #000096"><a:documentation></strong>The element and its content are part of the flow of its parent element<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
<strong class="hl-tag" style="color: #000096"><value></strong>no<strong class="hl-tag" style="color: #000096"></value></strong>
- <strong class="hl-tag" style="color: #000096"><a:documentation></strong>The element splits the text flow of its parent element and its content
- is an independent text flow<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
+ <strong class="hl-tag" style="color: #000096"><a:documentation></strong>The element splits the text flow of its parent element and its content is an independent text flow<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
<strong class="hl-tag" style="color: #000096"><value></strong>nested<strong class="hl-tag" style="color: #000096"></value></strong>
- <strong class="hl-tag" style="color: #000096"><a:documentation></strong>The element is part of the flow of its parent element,
- its content is an independent flow<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
+ <strong class="hl-tag" style="color: #000096"><a:documentation></strong>The element is part of the flow of its parent element, its content is an independent flow<strong class="hl-tag" style="color: #000096"></a:documentation></strong>
<strong class="hl-tag" style="color: #000096"></choice></strong>
<strong class="hl-tag" style="color: #000096"></define></strong>
<strong class="hl-tag" style="color: #000096"><define</strong> <span class="hl-attribute" style="color: #F5844C">name</span>=<span class="hl-value" style="color: #993300">"its-domainMapping.type"</span><strong class="hl-tag" style="color: #000096">></strong>
@@ -5409,9 +5397,8 @@
<strong class="hl-tag" style="color: #000096"><define</strong> <span class="hl-attribute" style="color: #F5844C">name</span>=<span class="hl-value" style="color: #993300">"its-lineBreakType.type"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><choice></strong>
<strong class="hl-tag" style="color: #000096"><value></strong>cr<strong class="hl-tag" style="color: #000096"></value></strong>
- <strong class="hl-tag" style="color: #000096"><value></strong>lr<strong class="hl-tag" style="color: #000096"></value></strong>
+ <strong class="hl-tag" style="color: #000096"><value></strong>lf<strong class="hl-tag" style="color: #000096"></value></strong>
<strong class="hl-tag" style="color: #000096"><value></strong>crlf<strong class="hl-tag" style="color: #000096"></value></strong>
- <strong class="hl-tag" style="color: #000096"><value></strong>nel<strong class="hl-tag" style="color: #000096"></value></strong>
<strong class="hl-tag" style="color: #000096"></choice></strong>
<strong class="hl-tag" style="color: #000096"></define></strong>
<strong class="hl-tag" style="color: #000096"><define</strong> <span class="hl-attribute" style="color: #F5844C">name</span>=<span class="hl-value" style="color: #993300">"its-annotatorsRef.type"</span><strong class="hl-tag" style="color: #000096">></strong>
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/09/22 17:28:03 1.518
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/10/14 07:50:59 1.519
@@ -782,7 +782,7 @@
<p>The XML Localization Interchange File Format <ptr target="#xliff1.2" type="bibref"/> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localization and translation workflows. <ptr target="#xliff2.0" type="bibref"/> is the successor of <ptr target="#xliff1.2" type="bibref"/> 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 <ptr target="#mlw-metadata-us-impl" type="bibref"/>. These usage scenarios involve:</p>
+ <p>The mapping between ITS and XLIFF therefore underpins several important ITS 2.0 usage scenarios <ptr target="#mlw-metadata-us-impl" type="bibref"/>. These usage scenarios involve:</p>
<list type="unordered">
<item>the extraction of ITS metadata from a source language file into XLIFF</item>
<item>the addition of ITS metadata into an XLIFF file by translation tools</item>
Received on Monday, 14 October 2013 07:51:01 UTC