- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Thu, 30 May 2013 16:49:04 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv4312
Modified Files:
its20-for-editing-sec1-sec2.html
its20-for-editing-sec1-sec2.odd
Log Message:
more sec 1-2 edits
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/05/30 16:29:37 1.4
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/05/30 16:49:04 1.5
@@ -512,7 +512,7 @@
<code>its-*</code> attributes introduced for <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> in older versions of HTML (such
as 3.2 or 4.01) and pages using these attributes will work without any problems,
<code>its-*</code> attributes will be marked as invalid in validators.</p></div></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="additional-data-categories" id="additional-data-categories" shape="rect"/>1.4.2 Additional data categories</h4><p>The following new data categories have been introduced in ITS 2.0</p><ul><li><p><a href="#domain" shape="rect">Domain</a>: identify the topic or subject of a given content by passing domain identifiers from the content to applications and potentially mapping to application specific identifiers.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotate the results of text analysis to be annotated in content.</p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a>: specify that a piece of content is only applicable to certain locales. </p></li><li><p><a href="#provenance" shape="rect">Provenance</a>: communicate the identity of agents that have been involved in the translaion of the content or the revision of the translated content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate that a reference points to potentially translatable data in a resource outside the document. Examples of such resources are external images and audio or video files.</p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a>: associate a given piece of source content (i.e. the content to be translated) and its corresponding target content (i.e. the source content translated into a given target language).</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>: identify a value that can be used as unique identifier for a given part of the content.
+<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="additional-data-categories" id="additional-data-categories" shape="rect"/>1.4.2 Additional data categories</h4><p>The following new data categories have been introduced in ITS 2.0.</p><ul><li><p><a href="#domain" shape="rect">Domain</a>: identify the topic or subject of the annotated content for translation related applications.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotate content with lexical or conceptual information for the purpose of contextual disambiguation.</p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a>: specify that a piece of content is only applicable to certain locales. </p></li><li><p><a href="#provenance" shape="rect">Provenance</a>: communicate the identity of agents that have been involved in the translation of the content or the revision of the ranslated content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate that a reference points to potentially translatable data in a resource outside the document. Examples of such resources are external images and audio or video files.</p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a>: associate a given piece of source content (i.e. the content to be translated) and its corresponding target content (i.e. the source content translated into a given target language).</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>: identify a value that can be used as unique identifier for a given part of the content.
</p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a>: indicate how whitespace should be handled in content.</p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a>: describe the nature and severity of an error detected during a language-oriented quality assurance (QA) process.</p></li><li><p><a href="#lqrating" shape="rect">Localization Quality Rating</a>: express an overall measurement of the localization quality of a document or an item in a document.</p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a>: indicate the confidence that MT systems provide about their translation.
</p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a>: specify the characters that are permitted in a given piece of content.</p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a>: specify the maximum storage size of a given content.</p></li></ul></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="modified-datacategories" id="modified-datacategories" shape="rect"/>1.4.3 Modified data categories</h4><p id="ruby-in-its2">ITS 1.0 provided the <a href="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation" shape="rect">Ruby data category</a>. ITS 2.0 does not provide ruby since at the time of writing, a stable model for ruby was not available. There are ongoing discussions about the <a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element" shape="rect">ruby model in HTML5</a>. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p><p>The <a href="#directionality" shape="rect">Directionality</a> data category reflects directionality markup in <a title="HTML 4.01" href="#html4" shape="rect">[HTML 4.01]</a>. The reason is that enancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.</p></div><div class="div3">
@@ -523,9 +523,9 @@
<h5><a name="traceability" id="traceability" shape="rect"/>1.4.4.4 Traceability</h5><p>tbd</p></div></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="mappings" id="mappings" shape="rect"/>1.4.5 Mappings</h4><div class="div4">
<h5><a name="mapping-NIF" id="mapping-NIF" shape="rect"/>1.4.5.1 ITS and RDF/NIF</h5><p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
- representations) that contain ITS metadata to the RDF-based format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations. The conversion results in RDF triples.</p><p>The conversion <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples that represent the textual content of the original document as RDF typed information and the ITS annotation as properties of those nodes defined in an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDf vocabulary</a>.</p><p>The backconversion <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div><div class="div4">
-<h5><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>1.4.5.2 ITS and XLIFF</h5><p>The XML Localization Interchange File Format <a title="" href="#xliff" shape="rect">[XLIFF]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.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: 1) the mapping of ITS meta-data in a source document into XLIFF and ITS meta-data of the translatable content in XLIFF file; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS eta-data in an XLIFF file into ITS meta-data in the resulting target language files. 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="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="unicode-normalization" id="unicode-normalization" shape="rect"/>1.4.6 Unicode normalization</h4><p>As a general guidance, implementations of ITS 2.0 should use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. Further information on the topic of Unicode normalization is provided by <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</a>.</p></div><div class="div3">
+ representations) that contain ITS metadata to the RDF-based format based on <a title="" href="#nif-reference" shape="rect">[NIF]</a>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p><p>The conversion <a href="#conversion-to-nif" shape="rect">ITS 2.0 to NIF</a> results in RDF triples that represent the textual content of the original document as RDF typed information and the ITS annotation as properties of those nodes defined in an <a href="http://www.w3.org/2005/11/its/rdf#" shape="rect">ITS RDF vocabulary</a>.</p><p>The backconversion <a href="#nif-backconversion" shape="rect">NIF to ITS 2.0</a> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div><div class="div4">
+<h5><a name="mapping-XLIFF" id="mapping-XLIFF" shape="rect"/>1.4.5.2 ITS and XLIFF</h5><p>The XML Localization Interchange File Format <a title="" href="#xliff" shape="rect">[XLIFF]</a> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.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: 1) the extraction of ITS meta-data from a source language file into XLIFF; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in te resulting target language files. 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="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="unicode-normalization" id="unicode-normalization" shape="rect"/>1.4.6 Unicode normalization</h4><p>As a general guidance, implementations of ITS 2.0 should use a <a href="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder" shape="rect">normalizing transcoder</a>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided by <a title="Character Model for the World Wide Web 1.0: Normalization" href="#charmod-norm" shape="rect">[Charmod Norm]</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="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.4.7 Extended implementation hints</h4><p>tbd</p></div></div></div><div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="basic-concepts" id="basic-concepts" shape="rect"/>2 Basic Concepts</h2><p>
<em>This section is informative.</em>
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/05/30 16:29:37 1.6
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/05/30 16:49:04 1.7
@@ -573,14 +573,14 @@
-->
<div xml:id="additional-data-categories"><head>Additional data categories</head>
- <p>The following new data categories have been introduced in ITS 2.0</p>
+ <p>The following new data categories have been introduced in ITS 2.0.</p>
<list type="unordered">
- <item><ref target="#domain">Domain</ref>: identify the topic or subject of a given content by passing domain identifiers from the content to applications and potentially mapping to application specific identifiers.</item>
+ <item><ref target="#domain">Domain</ref>: identify the topic or subject of the annotated content for translation related applications.</item>
- <item><ref target="#textanalysis">Text Analysis</ref>: annotate the results of text analysis to be annotated in content.</item>
+ <item><ref target="#textanalysis">Text Analysis</ref>: annotate content with lexical or conceptual information for the purpose of contextual disambiguation.</item>
@@ -649,19 +649,19 @@
<div xml:id="mapping-NIF"><head>ITS and RDF/NIF</head>
<p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
representations) that contain ITS metadata to the RDF-based format based on <ptr
- target="#nif-reference" type="bibref"/>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations. The conversion results in RDF triples.</p>
+ target="#nif-reference" type="bibref"/>. NIF is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p>
<p>The conversion <ref target="#conversion-to-nif">ITS 2.0 to NIF</ref> results in RDF triples that represent the textual content of the original document as RDF typed information and the ITS annotation as properties of those nodes defined in an <ref target="http://www.w3.org/2005/11/its/rdf#">ITS RDF vocabulary</ref>.</p>
<p>The backconversion <ref target="#nif-backconversion">NIF to ITS 2.0</ref> is defined informatively; it exemplifies a roundtripping involving automatic enrichment of HTML documents with linked information.</p></div>
<div xml:id="mapping-XLIFF"><head>ITS and XLIFF</head>
- <p>The XML Localization Interchange File Format <ptr target="#xliff" type="bibref"/> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.0 usage scenarios <ptr target="#mlw-metadata-us-impl" type="bibref"/>. These usage scenarios involve: 1) the mapping of ITS meta-data in a source document into XLIFF and ITS meta-data of the translatable content in XLIFF file; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files. ITS 2.0 has no normative dependency on XLIFF, however a <ref target="http://www.w3.orgInternational/its/wiki/XLIFF_Mapping">non-normative definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</ref> is being defined within the <ref target="http://www.w3.org/International/its/ig/">Internationalization Tag Set Interest Group</ref>.</p>
+ <p>The XML Localization Interchange File Format <ptr target="#xliff" type="bibref"/> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localisation and translation workflows. It has been widely implemented in translation management systems, computer supported translation tools and in utilities for extracting translatable content from source documents. The mapping between ITS and XLIFF therefore unpins several important ITS2.0 usage scenarios <ptr target="#mlw-metadata-us-impl" type="bibref"/>. These usage scenarios involve: 1) the extraction of ITS meta-data from a source language file into XLIFF; 2) the addition of ITS meta-data into an XLIFF file by translation tools; and 3) the mapping of ITS meta-data in an XLIFF file into ITS meta-data in the resulting target language files. ITS 2.0 has no normative dependency on XLIFF, however a <ref target="http://www.w3.org/International/its/wiki/XLIFF_Mapping">non-normatie definition of how to represent ITS 2.0 data categories in XLIFF 1.2 or XLIFF 2.0</ref> is being defined within the <ref target="http://www.w3.org/International/its/ig/">Internationalization Tag Set Interest Group</ref>.</p>
</div>
</div>
<div xml:id="unicode-normalization"><head>Unicode normalization</head>
- <p>As a general guidance, implementations of ITS 2.0 should use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. Further information on the topic of Unicode normalization is provided by <ptr target="#charmod-norm" type="bibref"/>.</p>
+ <p>As a general guidance, implementations of ITS 2.0 should use a <ref target="http://www.w3.org/TR/2012/WD-charmod-norm-20120501/#sec-NormalizingTranscoder">normalizing transcoder</ref>. It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided by <ptr target="#charmod-norm" type="bibref"/>.</p>
</div>
<div xml:id="extended-implementation-hints"><head>Extended implementation hints</head> <p>tbd</p></div>
Received on Thursday, 30 May 2013 16:49:10 UTC