- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Mon, 03 Jun 2013 19:49:44 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv2734
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/06/03 18:24:32 1.8
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.html 2013/06/03 19:49:44 1.9
@@ -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="#d0e2045" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2146" 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="#d0e2290" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2391" 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>
@@ -394,10 +394,9 @@
.
- </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="general-motiviation-for-ITS2.0" id="general-motiviation-for-ITS2.0" shape="rect"/>1.2 General motivation for going beyond ITS 1.0</h3><span class="editor-note">[Ed. note: We need to have the example <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">EX-motivation-its-2.xml</a> here since it was part of resolving <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/100" shape="rect">issue-100</a>.]</span><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 2: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those <code>string</code>
- elements that are translatable and those that are not. Only the addition of an
- explicit flag could resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
+ </p><span class="editor-note">[Ed. note: We need to have the example <a href="examples/xml/EX-motivation-its-2.xml" shape="rect">EX-motivation-its-2.xml</a> here since it was part of resolving <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/100" shape="rect">issue-100</a>.]</span><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-1" id="EX-motivation-its-1" shape="rect"/>Example 2: Document with partially translatable content</div><p>In this document it is difficult to distinguish between those <code>string</code>
+ elements that are translatable and those that are not. Only the addition of an
+ explicit flag could resolve the issue.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><resources></strong>
<strong class="hl-tag" style="color: #000096"><section</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"Homepage"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><arguments></strong>
<strong class="hl-tag" style="color: #000096"><string></strong>page<strong class="hl-tag" style="color: #000096"></string></strong>
@@ -420,9 +419,9 @@
<strong class="hl-tag" style="color: #000096"></section></strong>
<strong class="hl-tag" style="color: #000096"></resources></strong>
</pre></div><p>[Source file: <a href="examples/xml/EX-motivation-its-1.xml" shape="rect">examples/xml/EX-motivation-its-1.xml</a>]</p></div><div class="exampleOuter"><div class="exampleHeader"><a name="EX-motivation-its-2" id="EX-motivation-its-2" shape="rect"/>Example 3: Document with partially translatable content</div><p>Even when metadata are available to identify non-translatable text, the conditions
- may be quite complex and not directly indicated with a simple flag. Here, for
- instance, only the text in the nodes matching the expression
- <code>//component[@type!='image']/data[@type='text']</code> is translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><dialogue</strong> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-gb"</span><strong class="hl-tag" style="color: #000096">></strong>
+ may be quite complex and not directly indicated with a simple flag. Here, for
+ instance, only the text in the nodes matching the expression
+ <code>//component[@type!='image']/data[@type='text']</code> is translatable.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096"><dialogue</strong> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-gb"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><rsrc</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"123"</span><strong class="hl-tag" style="color: #000096">></strong>
<strong class="hl-tag" style="color: #000096"><component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"456"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"image"</span><strong class="hl-tag" style="color: #000096">></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">"text"</span><strong class="hl-tag" style="color: #000096">></strong>images/cancel.gif<strong class="hl-tag" style="color: #000096"></data></strong>
@@ -438,6 +437,7 @@
<strong class="hl-tag" style="color: #000096"></rsrc></strong>
<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="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">
@@ -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="d0e1134" id="d0e1134" 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="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
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="d0e2045" id="d0e2045" 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="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>
attribute.</p><div class="div4">
-<h5><a name="d0e2056" id="d0e2056" 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="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
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="d0e2267" id="d0e2267" 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="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
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="d0e2277" id="d0e2277" 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="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
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="d0e2290" id="d0e2290" 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="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
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
@@ -5837,7 +5837,7 @@
W3C Recommendation 30 April 2013. Available at <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/" shape="rect">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>.
The latest version of <a href="http://www.w3.org/TR/prov-dm/" shape="rect">The PROV Data Model</a>
is available at http://www.w3.org/TR/prov-dm/.
- </dd><dt class="label"><a name="rdfa-lite" id="rdfa-lite" shape="rect"/>RDFaLite</dt><dd>Manu Sporny (ed.). <a href="http://www.w3.org/TR/rdfa-lite/" shape="rect"><cite>RDFa Lite 1.1</cite></a>. W3C Recommendation 07 June 2012. Available at <a href="http://www.w3.org/TR/2012/REC-rdfa-lite-20120607/" shape="rect">http://www.w3.org/TR/2012/REC-rdfa-lite-20120607/</a>. </dd><dt class="label"><a name="schematron" id="schematron" shape="rect"/>Schematron</dt><dd>Information technology -- Document Schema
+ </dd><dt class="label"><a name="prov-overview" id="prov-overview" shape="rect"/>PROV-OVERVIEW</dt><dd>Groth, Paul, and Luc Moreau (eds.). <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/" shape="rect">PROV-Overview - An Overview of the PROV Family of Documents</a>. W3C Working Group Note 30 April 2013. Available at <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/" shape="rect">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>. The latest version of <a href="http://www.w3.org/TR/prov-overview/" shape="rect">PROV-Overview</a> is available at http://www.w3.org/TR/prov-overview/ .</dd><dt class="label"><a name="rdfa-lite" id="rdfa-lite" shape="rect"/>RDFaLite</dt><dd>Manu Sporny (ed.). <a href="http://www.w3.org/TR/rdfa-lite/" shape="rect"><cite>RDFa Lite 1.1</cite></a>. W3C Recommendation 07 June 2012. Available at <a href="http://www.w3.org/TR/2012/REC-rdfa-lite-20120607/" shape="rect">http://www.w3.org/TR/2012/REC-rdfa-lite-20120607/</a>. </dd><dt class="labe"><a name="schematron" id="schematron" shape="rect"/>Schematron</dt><dd>Information technology -- Document Schema
Definition Languages (DSDL) -- Part 3: <cite>Rule-based validation --
Schematron</cite>. International Organization for Standardization (ISO) ISO/IEC
19757-3:2003.</dd><dt class="label"><a name="structuredspecs" id="structuredspecs" shape="rect"/>Structured Specifications</dt><dd>(BYU Translation Research
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/03 18:24:32 1.10
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/06/03 19:49:44 1.11
@@ -416,27 +416,74 @@
.
</p>
-
+
+ <note type="ed">We need to have the example <ref target="examples/xml/EX-motivation-its-2.xml">EX-motivation-its-2.xml</ref> here since it was part of resolving <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/100">issue-100</ref>.</note>
+ <exemplum xml:id="EX-motivation-its-1">
+ <head>Document with partially translatable content</head>
+ <p>In this document it is difficult to distinguish between those <code>string</code>
+ elements that are translatable and those that are not. Only the addition of an
+ explicit flag could resolve the issue.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-motivation-its-1.xml"/>
+ </exemplum>
+ <exemplum xml:id="EX-motivation-its-2">
+ <head>Document with partially translatable content</head>
+ <p>Even when metadata are available to identify non-translatable text, the conditions
+ may be quite complex and not directly indicated with a simple flag. Here, for
+ instance, only the text in the nodes matching the expression
+ <code>//component[@type!='image']/data[@type='text']</code> is translatable.</p>
+ <egXML xmlns="http://www.tei-c.org/ns/Examples"
+ target="examples/xml/EX-motivation-its-2.xml"/>
+ </exemplum>
</div>
- <div xml:id="general-motiviation-for-ITS2.0"><head>General motivation for going beyond ITS 1.0</head> <note type="ed">We need to have the example <ref target="examples/xml/EX-motivation-its-2.xml">EX-motivation-its-2.xml</ref> here since it was part of resolving <ref target="https://www.w3.org/International/multilingualweb/lt/track/issues/100">issue-100</ref>.</note>
- <exemplum xml:id="EX-motivation-its-1">
- <head>Document with partially translatable content</head>
- <p>In this document it is difficult to distinguish between those <code>string</code>
- elements that are translatable and those that are not. Only the addition of an
- explicit flag could resolve the issue.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-motivation-its-1.xml"/>
- </exemplum>
- <exemplum xml:id="EX-motivation-its-2">
- <head>Document with partially translatable content</head>
- <p>Even when metadata are available to identify non-translatable text, the conditions
- may be quite complex and not directly indicated with a simple flag. Here, for
- instance, only the text in the nodes matching the expression
- <code>//component[@type!='image']/data[@type='text']</code> is translatable.</p>
- <egXML xmlns="http://www.tei-c.org/ns/Examples"
- target="examples/xml/EX-motivation-its-2.xml"/>
- </exemplum></div>
+ <div xml:id="general-motiviation-for-ITS2.0"><head>General motivation for going beyond ITS 1.0</head>
+
+ <p>The basics of ITS 1.0 fit onto a beer mat:</p>
+
+
+
+ <list type="ordered">
+ <item>Provide meta data (e.g. <q>Do not translate</q>) to assist internationalization-related processes</item>
+
+ <item>Use XPath (so-called <ref target="#selection-global">global appraoch</ref>) 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 <ref target="#def-local-attributes">local approach</ref>)</item>
+
+ <item>Work with a well-defined set of meta data categories or values (e.g. only the values <val>yes</val> and <val>no</val> for certain data categories)</item>
+
+ <item>Take advantage of existing meta data (e.g. terms already marked up with HTML markup such as <code>dt</code>)</item></list>
+
+
+
+ <p>This conciseness made real-world deployment easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <ref target="http://www.w3.org/International/its/ig/links.html">ITS Interest Group</ref> for example compiled a list of additional data categories (see this <ref target="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf">related summary</ref>). Some of these were then defined in ITS 2.0: <ref target="#idvalue">ID Value</ref>, local <ref target="#elements-within-text">Elements Within Text</ref>, <ref target="#preservespace">Preserve Space</ref>, and <ref target="#LocaleFilter">Locale Filte</ref>. Others are still discussed as requirements:</p>
+
+<list type="ordered">
+ <item><q>Context</q> = What specific related information might be helpful?</item>
+<item><q>Automated Language</q>: Does this content lend itself to automatic processing?</item></list>
+
+
+ <p>The real-world deployments also helped to understand that for the <ref target="http://www.webplatform.org/">Open Web Platform</ref> - 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>
+
+ <list type="ordered"><item>Applicability of ITS to formats such as HTML in general, and HTML5 in particular</item>
+
+ <item>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)</item>
+
+ <item>Support for provenance <ptr target="#prov-overview" type="bibref"/>, <q>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</q></item>
+
+ <item>Provisions for extended deployment in Semantic Web/Linked Open Data scenarios.</item></list>
+
+ <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>
+
+<list type="unordered">
+ <item>Providers of content management and machine translation solutions who want to easily integrate for efficient content updates in production chains</item>
+
+ <item>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</item>
+
+ <item>Open standards endeavours (e.g. related to <ptr target="#xliff" type="bibref"/> and <ptr target="#nif-reference" type="bibref"/>) that are interested for example in lossless roundtripping of meta data in localization workflows.</item></list>
+
+
+
+ <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>
@@ -5691,6 +5738,7 @@
The latest version of <ref target="http://www.w3.org/TR/prov-dm/">The PROV Data Model</ref>
is available at http://www.w3.org/TR/prov-dm/.
</bibl>
+ <bibl xml:id="prov-overview" n="PROV-OVERVIEW">Groth, Paul, and Luc Moreau (eds.). <ref target="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">PROV-Overview - An Overview of the PROV Family of Documents</ref>. W3C Working Group Note 30 April 2013. Available at <ref target="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</ref>. The latest version of <ref target="http://www.w3.org/TR/prov-overview/">PROV-Overview</ref> is available at http://www.w3.org/TR/prov-overview/ .</bibl>
<!-- <bibl xml:id="rfc3066" n="RFC 3066">Harald Alvestrand. <title><ref
target="http://www.ietf.org/rfc/rfc3066.txt">Tags for the Identification of
Languages</ref></title>. RFC 3066, January 2001. Available at <ref
Received on Monday, 3 June 2013 19:49:50 UTC