CVS WWW/International/multilingualweb/lt/drafts/its20

Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv14801

Modified Files:
	its20.html its20.odd 
Log Message:
minor edit in 2.1

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/06/17 08:48:57	1.448
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/06/17 09:03:33	1.449
@@ -384,7 +384,12 @@
             <em>This section is informative.</em>
          </p><p>The purpose of this section is to provide basic knowledge about how ITS 2.0 works. Detailed knowledge (including formal definitions) is given in the subsequent sections.</p><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="basic-concepts-datacategories" id="basic-concepts-datacategories" shape="rect"/>2.1 Data Categories</h3><p>A key concept of ITS is the abstract notion of <a href="#def-datacat" shape="rect">data categories</a>. Data categories define the information that can be conveyed via ITS. An example is the <a href="#trans-datacat" shape="rect">Translate</a> data category. It conveys information about translatability of content.</p><p>
-               <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> defines data categories. It also describes their implementation, that is: ways to use them for example in an XML context. The motivation for separating data category definitions from their implementation is that only this way the reality can be reflected since data categories can be implemented</p><ul><li><p>In various types of content (XML in general or <a href="#specific-HTML-support" shape="rect">HTML</a>).</p></li><li><p>For a single piece of content, e.g. a <code>p</code> element. This is the so-called <a href="#basic-concepts-selection-local" shape="rect">local approach</a>.</p></li><li><p>for several pieces of content in one document or even a set of documents. This is the so-called <a href="#basic-concepts-selection-global" shape="rect">global approach</a>.</p></li><li><p>For a complete markup vocabulary. This is done by adding <a href="#its-schemas" shape="rect">ITS makup declarations</a> to the schema for the vocabulary.</p></li></ul><p>ITS 2.0 provides the following data categories, using most of the existing ITS 1.0 data categories and adding new ones. Modifications of existing ITS 1.0 data categories are summarized in <a class="section-ref" href="#high-level-differences-between-1.0-and-2.0" shape="rect">Section 1.4: High-level differences between ITS 1.0 and ITS 2.0</a>.</p><ul><li><p><a href="#trans-datacat" shape="rect">Translate</a>: express information about whether a selected piece of content should be translated or not.</p></li><li><p><a href="#locNote-datacat" shape="rect">Localization Note</a>: communicate notes to localizers about a particular item of content.</p></li><li><p><a href="#terminology" shape="rect">Terminology</a>: mark terms and optionally associate them with information, such as definitions or references to a term data base.</p></li><li><p><a href="#directionality" shape="rect">Directionality</a>: specify the base writing direction of blocks, mbeddings and overrides for the Unicode bidirectional algorithm.</p></li><li><p><a href="#language-information" shape="rect">Language Information</a>: express the language of a given piece of content.</p></li><li><p><a href="#elements-within-text" shape="rect">Elements Witin Text:</a> express how content of an element is related to the text flow (constitute its own segment like paragraphs, be part of a segment like emphasis marker etc.).</p></li><li><p><a href="#domain" shape="rect">Domain</a>: identify the topic or subject of the annotated content for translation-related applications.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotate content with lexical or conceptual information (e.g. for the purpose of contextual disambiguation).</p></li><li><p><a href="#LocaleFilter" shape="rect">Locale Filter</a>: specify that a piece of content is only applicable to certain locales. </p></li><li><p><a href="#provenance" shape="rect">Provenance</a>: communicate the identity of agents that ave been involved processing content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate reference points in a resource outside the document that need to be considered during localization or translation. Examples of such resources are external images and audio or video files.</p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a>: associate the markup node of a given source content (i.e. the content to be translated) and the markup node of its corresponding target content (i.e. the source content translated into a given target language). This is relevant for formats that hold the same content in different languages inside a single document.</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>:  identify a value that can be used as unique identifier for a given part of the content.
+               <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a> defines data categories. It
+            also describes their implementation, i.e. ways to use them for example in an XML
+            context. The motivation for separating data category definitions from their
+            implementation is to enable different implementations with the following
+            characteristics:</p><ul><li><p>For various types of content (XML in general or <a href="#specific-HTML-support" shape="rect">HTML</a>).</p></li><li><p>For a single piece of content, e.g. a <code>p</code> element. This is the so-called <a href="#basic-concepts-selection-local" shape="rect">local approach</a>.</p></li><li><p>For several pieces of content in one document or even a set of documents. This is the
+              so-called <a href="#basic-concepts-selection-global" shape="rect">global approach</a>.</p></li><li><p>For a complete markup vocabulary. This is done by adding <a href="#its-schemas" shape="rect">ITS markup declarations</a> to the schema for the vocabulary.</p></li></ul><p>ITS 2.0 provides the following data categories, using most of the existing ITS 1.0 data categories and adding new ones. Modifications of existing ITS 1.0 data categories are summarized in <a class="section-ref" href="#high-level-differences-between-1.0-and-2.0" shape="rect">Section 1.4: High-level differences between ITS 1.0 and ITS 2.0</a>.</p><ul><li><p><a href="#trans-datacat" shape="rect">Translate</a>: express information about whether a selected piece of content should be translated or not.</p></li><li><p><a href="#locNote-datacat" shape="rect">Localization Note</a>: communicate notes to localizers about a particular item of content.</p></li><li><p><a href="#terminology" shape="rect">Terminology</a>: mark terms and opionally associate them with information, such as definitions or references to a term data base.</p></li><li><p><a href="#directionality" shape="rect">Directionality</a>: specify the base writing direction of blocks, embeddings and overrides for the Unicode bidirectional algorithm.</p></li><li><p><a href="#language-information" shape="rect">Language Information</a>: express the language of a given piece of content.</p></li><li><p><a href="#elements-within-text" shape="rect">Elements Witin Text:</a> express how content of an element is related to the text flow (constitute its own segment like paragraphs, be part of a segment like emphasis marker etc.).</p></li><li><p><a href="#domain" shape="rect">Domain</a>: identify the topic or subject of the annotated content for translation-related applications.</p></li><li><p><a href="#textanalysis" shape="rect">Text Analysis</a>: annotate content with lexical or conceptual information (e.g. for the purpose of contextual disambiguation).</p></li><li><p><a href="#LocaleFlter" shape="rect">Locale Filter</a>: specify that a piece of content is only applicable to certain locales. </p></li><li><p><a href="#provenance" shape="rect">Provenance</a>: communicate the identity of agents that have been involved processing content.</p></li><li><p><a href="#externalresource" shape="rect">External Resource</a>: indicate reference points in a resource outside the document that need to be considered during localization or translation. Examples of such resources are external images and audio or video files.</p></li><li><p><a href="#target-pointer" shape="rect">Target Pointer</a>: associate the markup node of a given source content (i.e. the content to be translated) and the markup node of its corresponding target content (i.e. the source content translated into a given target language). This is relevant for formats that hold the same content in different languages inside a single document.</p></li><li><p><a href="#idvalue" shape="rect">Id Value</a>:  identify a value that can be used as unque identifier for a given part of the content.
             </p></li><li><p><a href="#preservespace" shape="rect">Preserve Space</a>:  indicate how whitespace should be handled in content.</p></li><li><p><a href="#lqissue" shape="rect">Localization Quality Issue</a>: describe the nature and severity of an error detected during a language-oriented quality assurance (QA) process.</p></li><li><p><a href="#lqrating" shape="rect">Localization Quality Rating</a>: express an overall measurement of the localization quality of a document or an item in a document.</p></li><li><p><a href="#mtconfidence" shape="rect">MT Confidence</a>: indicate the confidence that MT systems provide about their translation.
             </p></li><li><p><a href="#allowedchars" shape="rect">Allowed Characters</a>:  specify the characters that are permitted in a given piece of content.</p></li><li><p><a href="#storagesize" shape="rect">Storage Size</a>: specify the maximum storage size of a given content.</p></li></ul></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="basic-concepts-selection" id="basic-concepts-selection" shape="rect"/>2.2 Selection</h3><p>Information (e.g. “translate this”) captured by an ITS data category always pertains to one or more XML or HTML nodes, primarily element and attribute nodes. In a sense, the relevant node(s) get “selected”. Selection may be explicit or implicit. ITS distinguishes two mechanisms for explicit selection: (1) local approach, and (2) global approach (via <code class="its-elem-markup">rules</code>). Both local and global approach can interact with each other, and with additional ITS dimensions such as inheritance and defaults.</p><p>The mechanisms defined for ITS selection resemble those defined in <a title="Cascading Style Sheets,&#xA;                level 2 revision 1 CSS 2.1 Specification" href="#css2-1" shape="rect">[CSS 21]</a>. The local approach can be compared to the
@@ -2063,7 +2068,8 @@
 				entity, the external resource may provide a full-fledged description
 				of the associated real world entity.</p><p>Extended example: The word 'City' in the fragment 'I am going to
 				the City' may be enhanced by one of the following:
-			</p><ul><li><p>one of WordNet's synsets that can be represented by 'city'</p></li><li><p>an ontological concept of 'City' that could represent a
+			</p><ul><li><p>one of WordNet's synsets that can be represented by 'city'
+				</p></li><li><p>an ontological concept of 'City' that could represent a
 					subclass of 'Populated Place' as a concept</p></li><li><p>the central area of a particular city - as interpreted as an entity instance (e.g., 'City
                   of London')</p></li></ul></div><div class="note"><p class="prefix"><b>Note:</b></p><p id="text-analysis-unique-annotation"> A given document fragment can only be annotated
                 once. When support for multiple annotations is necessary (e.g., when all three of
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/06/17 08:48:57	1.449
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/06/17 09:03:34	1.450
@@ -490,10 +490,16 @@
   <head>Data Categories</head>
   <p>A key concept of ITS is the abstract notion of <ref target="#def-datacat">data categories</ref>. Data categories define the information that can be conveyed via ITS. An example is the <ref target="#trans-datacat">Translate</ref> data category. It conveys information about translatability of content.</p>
   
-          <p><ptr target="#datacategory-description" type="specref"/> defines data categories. It also describes their implementation, that is: ways to use them for example in an XML context. The motivation for separating data category definitions from their implementation is that only this way the reality can be reflected since data categories can be implemented</p> 
-  <list type="unordered"><item>In various types of content (XML in general or <ref target="#specific-HTML-support">HTML</ref>).</item> 
+          <p><ptr target="#datacategory-description" type="specref"/> defines data categories. It
+            also describes their implementation, i.e. ways to use them for example in an XML
+            context. The motivation for separating data category definitions from their
+            implementation is to enable different implementations with the following
+            characteristics:</p> 
+  <list type="unordered"><item>For various types of content (XML in general or <ref target="#specific-HTML-support"
+                >HTML</ref>).</item> 
     <item>For a single piece of content, e.g. a <code>p</code> element. This is the so-called <ref target="#basic-concepts-selection-local">local approach</ref>.</item>
-    <item>for several pieces of content in one document or even a set of documents. This is the so-called <ref target="#basic-concepts-selection-global">global approach</ref>.</item>
+    <item>For several pieces of content in one document or even a set of documents. This is the
+              so-called <ref target="#basic-concepts-selection-global">global approach</ref>.</item>
     <item>For a complete markup vocabulary. This is done by adding <ref target="#its-schemas">ITS markup declarations</ref> to the schema for the vocabulary.</item>
   </list>

Received on Monday, 17 June 2013 09:03:41 UTC