- From: CVS User jkosek <cvsmail@w3.org>
- Date: Mon, 17 Jun 2013 09:34:05 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv17862
Modified Files:
its20.html its20.odd
Log Message:
Section 1.3 copyedit
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/17 09:30:06 1.453
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/17 09:34:05 1.454
@@ -282,7 +282,24 @@
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 <a title="
Internationalization Tag Set (ITS) Version 1.0
" href="#its10" shape="rect">[ITS 1.0]</a>
- <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “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 (the area for example of content authors): This part of the content has the directionality “right-to-left”.</p></li><li><p>Dynamic multi-lingual: (the area for example of machine translation systems): This part of the content must not be translated.</p></li></ul><p>Although ITS 1.0 made no assumptions about possible phases in a multilingual production process chai, 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 translation 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 actors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity identifiers/disambiguators to the same level. This change amongst others is reflected by the ITS 2.0 <a href="#its-tool-annotation" shape="rect">Tool Annotation</a> which allows systems to record tha they have processed as certain part of content.</p></div><div class="div2">
+ <a href="http://www.w3.org/TR/2007/REC-its-20070403/#introduction" shape="rect">introduction</a> states: “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 (for example, the area of content authors): This part of the
+ content has the directionality “right-to-left”.</p></li><li><p>Dynamic multi-lingual: (for example, the area of machine translation systems): This
+ part of the content must not be translated.</p></li></ul><p>Although ITS 1.0 made no assumptions about possible phases in a multilingual 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 translation 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 from 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 actors such as word processors/editors,
+ content management systems, machine translation systems, term candidate generators,
+ entity identifiers/disambiguators to the same level. This change amongst others is
+ reflected by the ITS 2.0 <a href="#its-tool-annotation" shape="rect">Tool Annotation</a> which
+ allows systems to record that they have processed a 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>Coverage of <a title="HTML5" href="#html5" shape="rect">[HTML5]</a>: </em>ITS 1.0 can 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> are given in <a class="section-ref" href="#specific-HTML-support" shape="rect">Section 2.5: 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="#basic-concepts-datacategories" shape="rect">Section 2.1: Data Categories</a>.</p><p>
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 09:30:06 1.455
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 09:34:05 1.456
@@ -332,16 +332,23 @@
<list type="unordered">
- <item>Static mono-lingual (the area for example of content authors): This part of the content has the directionality <q>right-to-left</q>.</item>
+ <item>Static mono-lingual (for example, the area of content authors): This part of the
+ content has the directionality <q>right-to-left</q>.</item>
- <item>Dynamic multi-lingual: (the area for example of machine translation systems): This part of the content must not be translated.</item>
+ <item>Dynamic multi-lingual: (for example, the area of machine translation systems): This
+ part of the content must not be translated.</item>
</list>
- <p>Although ITS 1.0 made no assumptions about possible phases in a multilingual production process chain, it was slanted towards a simple three phase <q>write->internationalize->translate</q> 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>
+ <p>Although ITS 1.0 made no assumptions about possible phases in a multilingual production
+ process chain, it was slanted towards a simple three phase
+ <q>write→internationalize→translate</q> 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>
<list type="unordered">
<item>Internationalization</item>
@@ -365,10 +372,20 @@
<item>Publishing</item></list>
- <p>The document <ptr target="#mlw-metadata-us-impl" type="bibref"/> lists a large variety of usage scenarios for ITS 2.0. Most of them are composed of several of the aforementioned phases.</p>
+ <p>The document <ptr target="#mlw-metadata-us-impl" type="bibref"/> lists a large variety
+ of usage scenarios for ITS 2.0. Most of them are composed from 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 <ref target="#terminology">Terminology</ref> 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 actors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity identifiers/disambiguators to the same level. This change amongst others is reflected by the ITS 2.0 <ref target="#its-tool-annotation">Tool Annotation</ref> which allows systems to record that they have processed as certain part of content.</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 <ref target="#terminology">Terminology</ref> 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 actors such as word processors/editors,
+ content management systems, machine translation systems, term candidate generators,
+ entity identifiers/disambiguators to the same level. This change amongst others is
+ reflected by the ITS 2.0 <ref target="#its-tool-annotation">Tool Annotation</ref> which
+ allows systems to record that they have processed a certain part of content.</p>
</div>
Received on Monday, 17 June 2013 09:34:07 UTC