- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 03 Jun 2013 20:10:22 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv4167
Modified Files:
its20-for-editing-sec1-sec2.html
its20-for-editing-sec1-sec2.odd
Log Message:
more sec1 sec 2 edits
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/03 19:49:44 1.9
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/03 20:10:22 1.10
@@ -53,9 +53,9 @@
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#selectors" shape="rect">Query Language of Selectors</a><div class="toc3">5.3.1 <a href="#queryLanguage" shape="rect">Choosing Query Language</a></div>
-<div class="toc3">5.3.2 <a href="#d0e2146" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2210" shape="rect">XPath 1.0</a></div>
<div class="toc3">5.3.3 <a href="#css-selectors" shape="rect">CSS Selectors</a></div>
-<div class="toc3">5.3.4 <a href="#d0e2391" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2455" shape="rect">Additional query languages</a></div>
<div class="toc3">5.3.5 <a href="#its-param" shape="rect">Variables in selectors</a></div>
</div>
<div class="toc2">5.4 <a href="#link-external-rules" shape="rect">Link to External Rules</a></div>
@@ -438,7 +438,7 @@
<strong class="hl-tag" style="color: #000096"></dialogue></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">examples/xml/EX-motivation-its-2.xml</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="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 NIF-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>tbd</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 href="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/" shape="rect">Metadata for the Multilingual Web - Usage Scenarios and Implementations</a> lists 18 different 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 nonhuman actors 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><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="specific-HTML-support" id="specific-HTML-support" shape="rect"/>1.4.1 Specific HTML support</h4><p>For applying ITS 2.0 data categories to HTML, five aspects must be considered:</p><ol class="depth1"><li><p>referencing global rules</p></li><li><p>specifities of inserting local ITS 2.0 data categories</p></li><li><p>relationship between HTML markup and data categories,</p></li><li><p>standoff markup in HTML5</p></li><li><p>HTML version.</p></li></ol><p>In the following sections these aspects are briefly discussed.</p><div class="div4">
<h5><a name="html5-reference-global-rules" id="html5-reference-global-rules" shape="rect"/>1.4.1.1 Referencing global rules</h5><p>To account for the so-called “<a href="#basic-concepts-selection-global" shape="rect">global
@@ -671,7 +671,7 @@
and localization of XML schemas and documents.] The concept of a data
category is independent of its implementation in an XML and HTML environment (e.g. using
an element or attribute).</p><p>For each data category, ITS distinguishes between the following:</p><ul><li><p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language independent formalization, see the "implementation" subsections in
- <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1235" id="d0e1235" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
+ <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="d0e1299" id="d0e1299" shape="rect"/>Example 10: A data category and its implementation</div><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys information as
to whether a piece of content should be translated or not.</p><p>The simplest formalization of this prose description on a schema language independent
level is a <code class="its-attr-markup">translate</code> attribute with two possible values:
"yes" and "no". An implementation on a schema language specific
@@ -936,9 +936,9 @@
actual query language. The query language is set by <code class="its-attr-markup">queryLanguage</code> attribute
on <code class="its-elem-markup">rules</code> element. If <code class="its-attr-markup">queryLanguge</code> is not specified XPath 1.0 is
used as a default query language.</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="d0e2146" id="d0e2146" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
+<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="d0e2210" id="d0e2210" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2157" id="d0e2157" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+<h5><a name="d0e2221" id="d0e2221" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
which starts with "<code>/</code>". That is, it must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a>s as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
@@ -983,14 +983,14 @@
implementations can be used.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="css-selectors-and-attributes">CSS selectors have no ability to point to
attributes.</p></div><p>CSS Selectors are identified by <code>css</code> value in <code class="its-attr-markup">queryLanguage</code>
attribute.</p><div class="div4">
-<h5><a name="d0e2368" id="d0e2368" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2432" id="d0e2432" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Both simple selectors
and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2378" id="d0e2378" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2442" id="d0e2442" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. Selector is not
evaluated against the complete document tree but only against subtrees rooted at
nodes selected by selector in the <code class="its-attr-markup">selector</code> attribute.</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="d0e2391" id="d0e2391" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
+<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="d0e2455" id="d0e2455" shape="rect"/>5.3.4 Additional query languages</h4><p>ITS processors <a href="#rfc-keywords" shape="rect">MAY</a> support additional query
languages. For each additional query language the processor <a href="#rfc-keywords" shape="rect">MUST</a> define:</p><ul><li><p>identifier of query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating absolute selector to collection of nodes;</p></li><li><p>rules for evaluating relative selector to collection of nodes.</p></li></ul><p>Because future versions of this specification are likely to define additional query
languages, the following query language identifiers are reserved: <code>xpath</code>,
<code>css</code>, <code>xpath2</code>, <code>xpath3</code>, <code>xquery</code>,
@@ -2367,7 +2367,7 @@
the following:</p><ul><li><p>A required <code class="its-attr-markup">selector</code> attribute. It contains an <a href="#selectors" shape="rect">absolute selector</a> which selects the nodes to which this
rule applies.</p></li><li><p>A required <code class="its-attr-markup">localeFilterList</code> attribute with a comma-separated list of
extended language ranges, or an empty string value.</p></li><li><p>An optional <code class="its-attr-markup">localeFilterType</code> attribute with a value
-"include" or "exclude".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locale-filter-selector-1" id="EX-locale-filter-selector-1" shape="rect"/>Example 56: The <a href="#LocaleFilter" shape="rect">Locale Filter</a> data category expressed
+ "include" or "exclude".</p></li></ul><div class="exampleOuter"><div class="exampleHeader"><a name="EX-locale-filter-selector-1" id="EX-locale-filter-selector-1" shape="rect"/>Example 56: The <a href="#LocaleFilter" shape="rect">Locale Filter</a> data category expressed
globally</div><p>This document contain three <code class="its-elem-markup">localeFilterRule</code> elements: The first one
specifies that the elements <code>legalnotice</code> with a <code>role</code> set to
"Canada" apply only to the Canadian locales. The second one specifies
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/03 19:49:44 1.11
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/03 20:10:22 1.12
@@ -485,7 +485,55 @@
<p>One example outcome of work on the requirements is the <ref target="#its-tool-annotation">ITS Tool Annotation</ref> mechanism. It addresses the provenance-related requirement by 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 NIF-related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</p>
</div>
- <div xml:id="usage-scenarios"><head>Usage Scenarios</head> <p>tbd</p></div>
+ <div xml:id="usage-scenarios"><head>Usage Scenarios</head>
+
+
+
+ <p>The ITS 1.0 specification <ptr target="#its10" type="bibref"/> states in <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#introduction">the introduction</ref>: <q>ITS is a technology to easily create XML which is internationalized and can be localized effectively</q>. In order to make this tangible, ITS 1.0 provided examples for <ref target="http://www.w3.org/TR/2007/REC-its-20070403/#users-usage">users and usages</ref>. 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>
+
+
+
+ <list type="unordered">
+ <item>Static mono-lingual: This part of the content has the directionality <q>right-to-left</q>.</item>
+
+
+
+ <item>Dynamic multi-lingual: This part of the content should be excluded from a possible translation phase.</item>
+ </list>
+
+
+
+ <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 <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>
+
+ <item>Pre-production (e.g. related to marking terminology)</item>
+
+ <item>Automated content enrichment (e.g. automatic hyperlinking for entities)</item>
+
+ <item>Extraction/filtering of translation-relevant content</item>
+
+ <item>Segmentation</item>
+
+ <item>Leveraging (e.g. of existing translation-related assets such as translation memories)</item>
+
+ <item>Machine Translation (e.g. geared towards a specific domain)</item>
+
+ <item>Quality assessment or control of source language or target language content</item>
+
+ <item>Generation of translation kits (e.g. packages based on XLIFF)</item>
+
+ <item>Post-production</item>
+
+ <item>Publishing</item></list>
+
+ <p>The document <ref target="http://www.w3.org/TR/2013/WD-mlw-metadata-us-impl-20130307/">Metadata for the Multilingual Web - Usage Scenarios and Implementations</ref> lists 18 different 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 <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 idenfiers/disambiguators to the same level. This change amongst others is reflected in the introduction of 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>
+
+
+ </div>
<div xml:id="high-level-differences-between-1.0-and-2.0"><head>High-level differences between ITS 1.0 and ITS 2.0</head>
<div xml:id="specific-HTML-support"><head>Specific HTML support</head>
Received on Monday, 3 June 2013 20:10:25 UTC