- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 10 Jun 2013 03:51:56 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv25284
Modified Files:
its20-for-editing-sec1-sec2.html
its20-for-editing-sec1-sec2.odd
Log Message:
more sec1-2 edits
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/09 21:52:31 1.14
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/10 03:51:56 1.15
@@ -448,10 +448,10 @@
<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="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><p>The basics of ITS 1.0 fit onto a beer mat:</p><ol class="depth1"><li><p>Provide meta data (e.g. “Do not translate”) to assist internationalization-related processes</p></li><li><p>Use XPath (so-called <a href="#selection-global" shape="rect">global appraoch</a>) to tie the meta data to specific XML nodes (e.g. all elements named <code>uitext</code>) or put the meta data straight onto the XML nodes themselves (so-called <a href="#def-local-attributes" shape="rect">local approach</a>)</p></li><li><p>Work with a well-defined set of meta data categories or values (e.g. only the values "yes" and "no" for certain data categories)</p></li><li><p>Take advantage of existing meta data (e.g terms already marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <a href="http://www.w3.org/International/its/ig/links.html" shape="rect">ITS Interest Group</a> for example compiled a list of additional data categories (see this <a href="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf" shape="rect">related summary</a>). Some of these were then defined in ITS 2.0: <a href="#idvalue" shape="rect">ID Value</a>, local <a href="#elements-within-text" shape="rect">Elements Within Text</a>, <a href="#preservespace" shape="rect">Preserve Space</a>, and <a href="#LocaleFilter" shape="rect">Locale Filte</a>. Others are still discussed as requirements:</p><ol class="depth1"><li><p>“Context” = What specific related information might be helpful?</p></li><li><p>“Automated Language”: Does this content lend iself to automatic processing?</p></li></ol><p>The real-world deployments also helped to understand that for the <a href="http://www.webplatform.org/" shape="rect">Open Web Platform</a> - the ITS 1.0 restriction to XML was an obstacle for quite a number of environments. What was missing was for example the following:</p><ol class="depth1"><li><p>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</p></li><li><p>Easy use of ITS in various Web-exposed Natural Language Processing contexts (e.g. machine translation, cross-language information retrieval, computer-supported linguistic quality assurance)</p></li><li><p>Support for provenance <a title="" href="#prov-overview" shape="rect">[PROV-OVERVIEW]</a>, “information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data scenaris.</p></li></ol><p>ITS 2.0 was created by an alliance of stakeholders who are involved in content for global use. Thus, ITS 2.0 was developed with input from/with a view towards the following:</p><ul><li><p>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in production chains</p></li><li><p>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to faciliate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="" href="#xliff" shape="rect">[XLIFF]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>) that are interested for example in lossless roundtripping of meta data in localization workflows.</p></li></ul><p>One example outcome of work on the requirements is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> mechanism. It addresses the provenance-related requirement b allowing ITS processors to leave a trace: ITS processors can basically say "It is me that generated this bit of information". Another example are the <a title="" href="#nif-reference" shape="rect">[NIF]</a> related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</p></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="usage-scenarios" id="usage-scenarios" shape="rect"/>1.3 Usage Scenarios</h3><p>The ITS 1.0 specification <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a> states in <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">the introduction</a>: “ITS is a technology to easily create XML which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 provided examples for <a href="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage" shape="rect">users and usages</a>. Implicitly, these examples carried the information that ITS covers two areas: one that is related to the static dimension of mono-lingual content, and one that is related to the dynamic dimension of multi-lingual production.<p><ul><li><p>Static mono-lingual: This part of the content has the directionality “right-to-left”.</p></li><li><p>Dynamic multi-lingual: This part of the content should be excluded from a possible translation phase.</p></li></ul><p>Although the ITS 1.0 made no assumptions about possible phases in a production process chain, it was slanted towards a simple three phase “write->internationalize->translate” model. Even a birds-eye-view at ITS 2.0 shows that ITS 2.0 explicitly targets a much more comprehensive model for multi-lingual content production. The model comprises support for multi-lingual content production phases such as:</p><ul><li><p>Internationalization</p></li><li><p>Pre-production (e.g. related to marking terminology)</p></li><li><p>Automated content enrichment (e.g. automatic hyperlinking for entities)</p></li><li><p>Extraction/filtering of translation-relevant content</p></li><li><p>Segmentation</p></li><li><p>Leveraging (e.g. of existing translation-related assets such as translaion memories)</p></li><li><p>Machine Translation (e.g. geared towards a specific domain)</p></li><li><p>Quality assessment or control of source language or target language content</p></li><li><p>Generation of translation kits (e.g. packages based on XLIFF)</p></li><li><p>Post-production</p></li><li><p>Publishing</p></li></ul><p>The document <a title="Metadata for the Multilingual Web - Usage Scenarios and Implementations " href="#mlw-metadata-us-impl" shape="rect">[MLW US IMPL]</a> lists a large variety of usage scenarios for ITS 2.0. Most of them are composed of several of the aforementioned phases.</p><p>In a similar vein, ITS 2.0 takes a much more comprehensive view on the actors that may participate in a multi-lingual content production process. ITS 1.0 annotations (e.g. local markup for the <a href="#terminology" shape="rect">Terminology</a> data category) most of the time were conceived as being closely tied to human actors such as content authors or information architects. ITS 2.0 raises non-human acors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity idenfiers/disambiguators to the same level. This change amongst others is reflected in the introduction of the ITS 2.0 <a href="#its-tool-annotation" shape="rect">Tool Annotation</a> which allows systems to record that they have processed as certain part of content.</p></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="high-level-differences-between-1.0-and-2.0" id="high-level-differences-between-1.0-and-2.0" shape="rect"/>1.4 High-level differences between ITS 1.0 and ITS 2.0</h3><p>The differences between ITS 1.0 and ITS 2.0 can be summarized as follows.</p><p>
- <em>Covering <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>: </em>ITS 1.0 provides data categories to be applied to XML content. ITS 2.0 extends the coverage to <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>. Explanatory details about ITS 2.0 and <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> is given in <a class="section-ref" href="#specific-HTML-support" shape="rect">Section 2.4: Specific HTML support</a>.</p><p>
- <em>Adding data categories</em>: ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 1.0 and ITS 2.0 data categories is given in <a class="section-ref" href="#datacategories-summary" shape="rect">Section 2.7: Summary: ITS 2.0 data categories</a>.</p><p>
- <em>Modifying data categories</em>:</p><ul><li><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, because of the the <a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element" shape="rect">ruby model in HTML5</a> was still under development. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p></li><li><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 enhancements 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 enhancemens are not finalized yet. They will be reflected in a future revision of ITS.</p></li></ul><p>
- <em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified for all data categories.</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global" shape="rect">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors" shape="rect">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param" shape="rect">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has a <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="secion-ref" href="#traceability" shape="rect">Section 2.5: Traceability</a> for details.</p></li></ul><p>
+ <em>Coverage of <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>: </em>ITS 1.0 provides data categories to be applied to XML content. ITS 2.0 extends the coverage to <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>. Explanatory details about ITS 2.0 and <a title="HTML5" href="#html5" shape="rect">[HTML5]</a> is given in <a class="section-ref" href="#specific-HTML-support" shape="rect">Section 2.4: Specific HTML support</a>.</p><p>
+ <em>Addition of data categories</em>: ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 2.0 data categories are given in <a class="section-ref" href="#datacategories-summary" shape="rect">Section 2.7: Summary: ITS 2.0 data categories</a>.</p><p>
+ <em>Modification of data categories</em>:</p><ul><li><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, because of the the <a href="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element" shape="rect">ruby model in HTML5</a> was still under development. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p></li><li><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 enhancements 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 enhacements are not finalized yet. They will be reflected in a future revision of ITS.</p></li></ul><p>
+ <em>Additional or modified mechanisms:</em> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0.</p><ul><li><p id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <a href="#basic-concepts-selection-global" shape="rect">global rules</a>. ITS 2.0 allows for choosing the <a href="#selectors" shape="rect">query language of selectors</a>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></li><li><p id="parameters-in-selector">In global rules it is now possible to set <a href="#its-param" shape="rect">variables for the selectors</a> (XPath expression). The <code class="its-elem-markup">param</code> element serves this purpose.</p></li><li><p>ITS 2.0 has a <a href="#its-tool-annotation" shape="rect">ITS Tools Annotation</a> mechanism to associate processor information with the use of individual data categories. See <a class="sectio-ref" href="#traceability" shape="rect">Section 2.5: Traceability</a> for details.</p></li></ul><p>
<em>Mappings:</em> ITS 2.0 provides a normative algorithm to convert ITS 2.0 information into <a title="" href="#nif-reference" shape="rect">[NIF]</a> and links to guidance about ITS 2.0 and XLIFF. See <a class="section-ref" href="#mapping-conversion" shape="rect">Section 2.6: Mapping and conversion</a> for details.</p><p>
<em>Changes to the conformance section</em>: The <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a> tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed, and a conformance clause related to processing <a title="" href="#nif-reference" shape="rect">[NIF]</a> has been added. For <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>, a dedicated conformance section has been created. Finally, a conformance clause related to Non-ITS elements and attributes has been added.</p></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="extended-implementation-hints" id="extended-implementation-hints" shape="rect"/>1.5 Extended implementation hints</h3><p id="unicode-normalization">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><div class="div1">
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/09 21:52:31 1.16
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/10 03:51:56 1.17
@@ -538,14 +538,14 @@
<p>The differences between ITS 1.0 and ITS 2.0 can be summarized as follows.</p>
- <p><emph>Covering <ptr type="bibref" target="#html5"/>: </emph>ITS 1.0 provides data categories to be applied to XML content. ITS 2.0 extends the coverage to <ptr target="#html5" type="bibref"/>. Explanatory details about ITS 2.0 and <ptr target="#html5" type="bibref"/> is given in <ptr target="#specific-HTML-support" type="specref"/>.</p>
- <p><emph>Adding data categories</emph>: ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 1.0 and ITS 2.0 data categories is given in <ptr target="#datacategories-summary" type="specref"/>.</p>
+ <p><emph>Coverage of <ptr type="bibref" target="#html5"/>: </emph>ITS 1.0 provides data categories to be applied to XML content. ITS 2.0 extends the coverage to <ptr target="#html5" type="bibref"/>. Explanatory details about ITS 2.0 and <ptr target="#html5" type="bibref"/> is given in <ptr target="#specific-HTML-support" type="specref"/>.</p>
+ <p><emph>Addition of data categories</emph>: ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 2.0 data categories are given in <ptr target="#datacategories-summary" type="specref"/>.</p>
- <p><emph>Modifying data categories</emph>:</p>
+ <p><emph>Modification of data categories</emph>:</p>
<list><item> <p xml:id="ruby-in-its2">ITS 1.0 provided the <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#ruby-annotation">Ruby data category</ref>. ITS 2.0 does not provide ruby since at the time of writing, because of the the <ref target="http://www.w3.org/TR/html51/text-level-semantics.html#the-ruby-element">ruby model in HTML5</ref> was still under development. Once these discussions are settled, in a subsequent version of ITS, the ruby data category may be re-introduced.</p></item>
<item> <p>The <ref target="#directionality">Directionality</ref> data category reflects directionality markup in <ptr target="#html4" type="bibref"/>. The reason is that enhancements 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></item></list>
- <p><emph>Additional or modified mechanisms:</emph> The following mechanisms from ITS 1.0 have been modified for all data categories.</p>
+ <p><emph>Additional or modified mechanisms:</emph> The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0.</p>
<list>
<item><p xml:id="query-language-on-rules-element">ITS 1.0 used only XPath as the mechanism for selecting nodes in <ref target="#basic-concepts-selection-global">global rules</ref>. ITS 2.0 allows for choosing the <ref target="#selectors">query language of selectors</ref>. The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.</p></item>
Received on Monday, 10 June 2013 03:51:57 UTC