- From: CVS User jkosek <cvsmail@w3.org>
- Date: Mon, 17 Jun 2013 09:24:19 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv17215
Modified Files:
its20.html its20.odd
Log Message:
Section 1.2 copyedit
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/17 09:10:10 1.451
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/17 09:24:19 1.452
@@ -59,9 +59,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="#d0e2582" shape="rect">XPath 1.0</a></div>
+<div class="toc3">5.3.2 <a href="#d0e2585" 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="#d0e2827" shape="rect">Additional query languages</a></div>
+<div class="toc3">5.3.4 <a href="#d0e2830" 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>
@@ -266,7 +266,21 @@
<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 are simple:</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 associate meta data with 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. ters already marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <a href="http://www.w3.org/International/its/ig/" 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 for possible future versions of ITS:</p><ol class="depth1"><li><p>“Context” = What specific related information might be helpful?</p></li><li><p>“Automated Languge” = Does this content lend itself 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 (multilingual) Natural Language Processing contexts</p></li><li><p>Computer-supported linguistic quality assurance</p></li><li><p>Content Management and translation platforms</p></li><li><p>Cross-language scenarios</p></li><li><p>Content enrichment</p></li><li><p>Support for W3C provenance <a title="" href="#prov-dm" shape="rect">[PROV-DM]</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, eliability or trustworthiness”</p></li><li><p>Provisions for extended deployment in Semantic Web/Linked Open Data scenarios.</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 multilingual 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 facilitate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a>, <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>) that are interested for example in information sharing, andlossless round tripping of meta data in localization workflows.</p></li></ul><p>One example outcome of the resulting synergies is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> 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 <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="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 are simple:</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 associate meta data with 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. ters already marked up with HTML markup such as <code>dt</code>)</p></li></ol><p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to
+ identify additional meta data categories for internationalization-related processes. The
+ <a href="http://www.w3.org/International/its/ig/" 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 Filter</a>. Others are still discussed as requirements
+ for possible future versions of ITS:</p><ol class="depth1"><li><p>“Context” = What specific related information might be helpful?</p></li><li><p>“Automated Language” = Does this content lend itself 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 (multilingual) Natural Language Processing contexts</p></li><li><p>Computer-supported linguistic quality assurance</p></li><li><p>Content Management and translation platforms</p></li><li><p>Cross-language scenarios</p></li><li><p>Content enrichment</p></li><li><p>Support for W3C provenance <a title="" href="#prov-dm" shape="rect">[PROV-DM]</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
+ scenarios</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 multilingual 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 facilitate human translation</p></li><li><p>Open standards endeavours (e.g. related to <a title="XLIFF Version 1.2" href="#xliff1.2" shape="rect">[XLIFF 1.2]</a>, <a title="XLIFF Version 2.0" href="#xliff2.0" shape="rect">[XLIFF 2.0]</a> and <a title="" href="#nif-reference" shape="rect">[NIF]</a>)
+ that are interested for example in information sharing, and lossless round tripping of
+ meta data in localization workflows</p></li></ul><p>One example outcome of the resulting synergies is the <a href="#its-tool-annotation" shape="rect">ITS Tool Annotation</a> 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 <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">
<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>
@@ -387,10 +401,12 @@
data categories allow to add information, and which allow to point to existing information.</p><p>Adding information and pointing to existing information are
<em>mutually exclusive</em>: attributes for adding information and attributes for pointing to
the same information must not appear at the same rule element.</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="specific-HTML-support" id="specific-HTML-support" shape="rect"/>2.5 Specific HTML support</h3><p>For applying ITS 2.0 data categories to HTML, five aspects must be considered:</p><ol class="depth1"><li><p>global approach</p></li><li><p>local approach</p></li><li><p>HTML markup with ITS 2.0 counterparts</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="div3">
+<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="specific-HTML-support" id="specific-HTML-support" shape="rect"/>2.5 Specific HTML support</h3><p>For applying ITS 2.0 data categories to HTML, five aspects are of importance:</p><ol class="depth1"><li><p>global approach</p></li><li><p>local approach</p></li><li><p>HTML markup with ITS 2.0 counterparts</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="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="html5-global-approach" id="html5-global-approach" shape="rect"/>2.5.1 Global approach in HTML5</h4><p>To account for the so-called <a href="#basic-concepts-selection-global" shape="rect">global
approach</a> in HTML, this specification (see <a class="section-ref" href="#html5-global-rules" shape="rect">Section 6.2: Global rules</a>) defines
- </p><ul><li><p>a link type for referring to external files with global rules from a <code>link</code> element</p></li><li><p>an approach to have inline global rules in the HTML <code>script</code> element.</p></li></ul><p>It is preferred to use external global rules linked via the <code>link</code> element than to have inline global rules in the HTML document.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 6: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
+ </p><ul><li><p>a link type for referring to external files with global rules from a <code>link</code> element</p></li><li><p>an approach to have inline global rules in the HTML <code>script</code> element.</p></li></ul><p>It is preferable to use external global rules linked via the <code>link</code> element rather than to have inline global rules in the HTML document.
+ The advantage is in being able to reuse the same rules file for many documents and also inline rules require secondary parsing
+ of the <code>script</code> element.</p><div class="exampleOuter"><div class="exampleHeader"><a name="EX-translate-html5-global-1" id="EX-translate-html5-global-1" shape="rect"/>Example 6: Using ITS global rules in HTML</div><p>The <code>link</code> element points to the rules file
<code>EX-translateRule-html5-1.xml</code> The <code>rel</code> attribute identifies
the ITS specific link relation <code>its-rules</code>.</p><div class="exampleInner"><pre xml:space="preserve"><strong class="hl-tag" style="color: blue"><!DOCTYPE html></strong>
<strong class="hl-tag" style="color: #000096"><html></strong>
@@ -478,7 +494,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="d0e1616" id="d0e1616" shape="rect"/>Example 9: 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="d0e1619" id="d0e1619" shape="rect"/>Example 9: 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
@@ -750,9 +766,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="d0e2582" id="d0e2582" 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="d0e2585" id="d0e2585" 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="d0e2593" id="d0e2593" 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="d0e2596" id="d0e2596" 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
that 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>.
@@ -797,14 +813,14 @@
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 the value <code>css</code> in the
<code class="its-attr-markup">queryLanguage</code> attribute.</p><div class="div4">
-<h5><a name="d0e2804" id="d0e2804" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2807" id="d0e2807" shape="rect"/>5.3.3.1 Absolute selector</h5><p>An absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
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="d0e2814" id="d0e2814" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
+<h5><a name="d0e2817" id="d0e2817" shape="rect"/>5.3.3.2 Relative selector</h5><p>A relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as a
selector as defined in <a title="Selectors Level
 3" href="#css3-selectors" shape="rect">[Selectors Level 3]</a>. A selector is
not evaluated against the complete document tree but only against subtrees rooted at
nodes selected by the 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="d0e2827" id="d0e2827" 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="d0e2830" id="d0e2830" 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>the identifier of the query language used in <code class="its-attr-markup">queryLanguage</code>;</p></li><li><p>rules for evaluating an absolute selector to a collection of nodes;</p></li><li><p>rules for evaluating a relative selector to a 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>,
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 09:12:30 1.453
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 09:24:19 1.454
@@ -264,14 +264,26 @@
- <p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to identify additional meta data categories for internationalization-related processes. The <ref target="http://www.w3.org/International/its/ig/">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 for possible future versions of ITS:</p>
+ <p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to
+ identify additional meta data categories for internationalization-related processes. The
+ <ref target="http://www.w3.org/International/its/ig/">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 Filter</ref>. Others are still discussed as requirements
+ for possible future versions of ITS:</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>
+ <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>
@@ -285,7 +297,8 @@
<item>Support for W3C provenance <ptr target="#prov-dm" 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>
+ <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>
@@ -294,11 +307,20 @@
<item>Language technology providers who want to automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to facilitate human translation</item>
- <item>Open standards endeavours (e.g. related to <ptr target="#xliff1.2" type="bibref"/>, <ptr target="#xliff2.0" type="bibref"/> and <ptr target="#nif-reference" type="bibref"/>) that are interested for example in information sharing, and lossless round tripping of meta data in localization workflows.</item></list>
+ <item>Open standards endeavours (e.g. related to <ptr target="#xliff1.2" type="bibref"/>, <ptr
+ target="#xliff2.0" type="bibref"/> and <ptr target="#nif-reference" type="bibref"/>)
+ that are interested for example in information sharing, and lossless round tripping of
+ meta data in localization workflows</item></list>
- <p>One example outcome of the resulting synergies 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 <ptr target="#nif-reference" type="bibref"/> related details of ITS 2.0 which help to couple Natural Language Processing with concepts of the Semantic Web.</p>
+ <p>One example outcome of the resulting synergies 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 <q>It is me that generated this bit of
+ information</q>. Another example are the <ptr target="#nif-reference"
+ type="bibref"/> 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>
Received on Monday, 17 June 2013 09:24:25 UTC