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

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

Modified Files:
	its20.html its20.odd 
Log Message:
small fix of NIF section from sebastian - should be the last one related to NIF

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/06/10 16:48:53	1.443
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2013/06/12 07:24:21	1.444
@@ -220,18 +220,22 @@
 </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 2: 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">&lt;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">&gt;</strong>
+                  <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">&lt;dialogue</strong> <span class="hl-attribute" style="color: #F5844C">xml:lang</span>=<span class="hl-value" style="color: #993300">"en-gb"</span> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">its:version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
+  <strong class="hl-tag" style="color: #000096">&lt;its:rules</strong> <span class="hl-attribute" style="color: #F5844C">xmlns:its</span>=<span class="hl-value" style="color: #993300">"http://www.w3.org/2005/11/its"</span> <span class="hl-attribute" style="color: #F5844C">version</span>=<span class="hl-value" style="color: #993300">"2.0"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
+    <strong class="hl-tag" style="color: #000096">&lt;its:translateRule</strong> <span class="hl-attribute" style="color: #F5844C">selector</span>=<span class="hl-value" style="color: #993300">"//data"</span> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span><strong class="hl-tag" style="color: #000096">/&gt;</strong>
+  <strong class="hl-tag" style="color: #000096">&lt;/its:rules&gt;</strong>
+  
   <strong class="hl-tag" style="color: #000096">&lt;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">&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;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">&gt;</strong>
       <strong class="hl-tag" style="color: #000096">&lt;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">&gt;</strong>images/cancel.gif<strong class="hl-tag" style="color: #000096">&lt;/data&gt;</strong>
       <strong class="hl-tag" style="color: #000096">&lt;data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>12,20<strong class="hl-tag" style="color: #000096">&lt;/data&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;/component&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"789"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"caption"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
-      <strong class="hl-tag" style="color: #000096">&lt;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">&gt;</strong>Cancel<strong class="hl-tag" style="color: #000096">&lt;/data&gt;</strong>
-      <strong class="hl-tag" style="color: #000096">&lt;data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>60,40<strong class="hl-tag" style="color: #000096">&lt;/data&gt;</strong>
+      <strong class="hl-tag" style="color: #000096">&lt;data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>Cancel<strong class="hl-tag" style="color: #000096">&lt;/data&gt;</strong>
+        <strong class="hl-tag" style="color: #000096">&lt;data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"position"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>60,40<strong class="hl-tag" style="color: #000096">&lt;/data&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;/component&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;component</strong> <span class="hl-attribute" style="color: #F5844C">id</span>=<span class="hl-value" style="color: #993300">"792"</span> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"string"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
-      <strong class="hl-tag" style="color: #000096">&lt;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">&gt;</strong>Number of files: <strong class="hl-tag" style="color: #000096">&lt;/data&gt;</strong>
+      <strong class="hl-tag" style="color: #000096">&lt;data</strong> <span class="hl-attribute" style="color: #F5844C">type</span>=<span class="hl-value" style="color: #993300">"text"</span> <span class="hl-attribute" style="color: #F5844C">its:translate</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>Number of files: <strong class="hl-tag" style="color: #000096">&lt;/data&gt;</strong>
     <strong class="hl-tag" style="color: #000096">&lt;/component&gt;</strong>
   <strong class="hl-tag" style="color: #000096">&lt;/rsrc&gt;</strong>
 <strong class="hl-tag" style="color: #000096">&lt;/dialogue&gt;</strong>
@@ -691,7 +695,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="d0e1457" id="d0e1457" shape="rect"/>Example 14: 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="d0e1457" id="d0e1457" shape="rect"/>Example 14: 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
@@ -1261,6 +1265,7 @@
 &lt;http://example.com/exampledoc.html#char=0,29&gt;
  nif:wasConvertedFrom
  &lt;http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text())&gt; .
+&lt;!-- XML Example --&gt; 
 &lt;mappings&gt;
  &lt;mapping x="xpath(/html/body[1]/h2[1]/text()[1])" b="0" e="11" /&gt;
  &lt;mapping x="xpath(/html/body[1]/h2[1]/span[1]/text()[1])" b="11" e="17" /&gt;
@@ -5871,12 +5876,12 @@
 &lt;http://dbpedia.org/resource/Ireland&gt; 
  rdf:type &lt;http:/nerd.eurecom.fr/ontology#Country&gt; .</pre></div></div><p id="nif2its-algorithm">The conversion algorithm to generate ITS out of NIF consists
           of two steps.</p><ul><li><p id="nif2its-algorithm-step1">STEP 1: NIF Web services accept two different types of input. It is possible to either send the extracted text (the object of the <code>nif:isString</code> property) directly or  NIF RDF to the NLP tool, i.e. the text is sent as a <code>nif:Context</code> node and included as <code>nif:isString</code>. Either way, the output of the Web service will be a NIF representation.
-            </p><p>Accepting text will be the minimal requirement of a NIF web service. Ideally, you would be able to send the <code>nif:Context</code> node with the isString as RDF directly, which has the advantage, that all other annotations can be used by the NLP tool:</p><div class="exampleInner"><div class="exampleOuter"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096">&lt;rdf:Description</strong> <span class="hl-attribute" style="color: #F5844C">rdf:about</span>=<span class="hl-value" style="color: #993300">"http://example.com/exampledoc.html#char=0,29"</span><strong class="hl-tag" style="color: #000096">&gt;</strong>
- <strong class="hl-tag" style="color: #000096">&lt;nif:sourceUrl</strong> <span class="hl-attribute" style="color: #F5844C">rdf:resource</span>=<span class="hl-value" style="color: #993300">"http://example.com/exampledoc.html"</span><strong class="hl-tag" style="color: #000096">/&gt;</strong>
- <strong class="hl-tag" style="color: #000096">&lt;nif:isString&gt;</strong>Welcome to Dublin in Ireland!<strong class="hl-tag" style="color: #000096">&lt;/nif:isString&gt;</strong>
- <strong class="hl-tag" style="color: #000096">&lt;rdf:type</strong> <span class="hl-attribute" style="color: #F5844C">rdf:resource</span>=<span class="hl-value" style="color: #993300">"http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#Context"</span><strong class="hl-tag" style="color: #000096">/&gt;</strong>
-<strong class="hl-tag" style="color: #000096">&lt;/rdf:Description&gt;</strong>
-</pre></div></div></li><li><p id="nif2its-algorithm-step3">STEP 2: Use the mapping from ITS2NIF (available
+            </p><p>Accepting text will be the minimal requirement of a NIF web service. Ideally, you would be able to send the <code>nif:Context</code> node with the isString as RDF directly, which has the advantage, that all other annotations can be used by the NLP tool:</p><div class="exampleInner"><div class="exampleOuter"><pre xml:space="preserve"><strong class="hl-tag" style="color: #000096">&lt;http:</strong>//example.com/exampledoc.html#char=0,29&gt; 
+ rdf:type nif:RFC5147String ;
+ rdf:type nif:Context ;
+ nif:beginIndex "0" ;
+ nif:endIndex "29" ;
+ nif:isString  "Welcome to Dublin in Ireland!" .</pre></div></div></li><li><p id="nif2its-algorithm-step3">STEP 2: Use the mapping from ITS2NIF (available
               after <a href="#its2nif-algorithm-step7" shape="rect">step 7</a> of the ITS2NIF algorithm) to
               reintegrate annotations in the original ITS annotated document.</p></li></ul><p>For step 2, three cases can occur.</p><p>CASE 1: The NLP annotation created in NIF matches the text node. Solution: Attach the
           annotation to the parent element of the text node.</p><div class="exampleInner"><div class="exampleOuter"><pre xml:space="preserve"># Based on:
@@ -6147,7 +6152,8 @@
             Selectors integration.</p></li><li><p>Added examples to <a class="section-ref" href="#externalresource" shape="rect">Section 8.12: External Resource</a>.</p></li><li><p>Simplified <a class="section-ref" href="#LocaleFilter" shape="rect">Section 8.10: Locale Filter</a>.</p></li><li><p>Added a note about HTML and the attributes <code class="its-attr-markup">dir</code> and <code class="its-attr-markup">translate</code>
             to <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.2: Local Selection in an XML Document</a>.</p></li><li><p>Added definition of <code class="its-elem-markup">param</code> element to <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>.</p></li><li><p>Added <a class="section-ref" href="#target-pointer" shape="rect">Section 8.13: Target Pointer</a>.</p></li><li><p>Original Ruby markup model changed to HTML5 Ruby model.</p></li><li><p>Updated references.</p></li><li><p>Added <a class="section-ref" href="#preservespace" shape="rect">Section 8.15: Preserve Space</a>.</p></li><li><p>Added <a class="section-ref" href="#lqissue" shape="rect">Section 8.16: Localization Quality Issue</a> and the related <a class="section-ref" href="#lqissue-typevalues" shape="rect">Appendix C: Values for the Localization Quality Issue Type</a>.</p></li><li><p>Added <a class="section-ref" href="#lqrating" shape="rect">Section 8.17: Loclization Quality Rating</a>.</p></li><li><p>Added a placeholder <a class="section-ref" href="#mtconfidence" shape="rect">Section 8.18: MT Confidence</a>.</p></li></ol><p id="changelog-since-20120626">The following log records major changes that have been
           made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20120626/" shape="rect">ITS 2.0 Working Draft 26 June 2012</a>.</p><ol class="depth1"><li><p>Various editorial changes (non-normative references update, style &amp; grammar
-            fixes).</p></li><li><p>Made clarifications to <a class="section-ref" href="#out-of-scope" shape="rect">Section 1.6: Out of Scope</a>, <a class="section-ref" href="#design-decisions" shape="rect">Section 1.7: Important Design Principles</a>.</p></li><li><p>Added explanatory note on precedence and overriding in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</a>.</p></li><li><p>Reordered some components in <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a>.</p></li><li><p>Restructured <a class="section-ref" href="#relation-to-its10-and-new-principles" shape="rect">Section 1.1: Relation to ITS 1.0 and New Principles</a>.</p></li><li><p>Added <a class="section-ref" href="#queryLanguage" shape="rect">Section 5.3.1: Choosing Query Language</a> as a stub.</p></li><li><p>Added <a class="section-ref" href="#LocaleFilter" shape="rect">Section 8.10: Locale Filter</a>.</p></li><li><p>Added <a class="sectionref" href="#domain" shape="rect">Section 8.8: Domain</a>.</p></li><li><p>Added <a class="section-ref" href="#usage-in-legacy-html" shape="rect">Section 1.4.5: Version of HTML</a>.</p></li><li><p>Added local markup in <a class="section-ref" href="#elements-within-text" shape="rect">Section 8.7: Elements Within Text</a>.</p></li><li><p>Added <a class="section-ref" href="#externalresource" shape="rect">Section 8.12: External Resource</a>.</p></li><li><p>Updated examples to use the <code class="its-attr-markup">version</code> attribute with the value<code>2.0</code>.</p></li></ol><p id="changelog-since-20070403">The following log records major changes that have been
+            fixes).</p></li><li><p>Made clarifications to <a class="section-ref" href="#out-of-scope" shape="rect">Section 1.6: Out of Scope</a>, <a class="section-ref" href="#design-decisions" shape="rect">Section 1.7: Important Design Principles</a>.</p></li><li><p>Added explanatory note on precedence and overriding in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.5: Precedence between Selections</a>.</p></li><li><p>Reordered some components in <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a>.</p></li><li><p>Restructured <a class="section-ref" href="#relation-to-its10-and-new-principles" shape="rect">Section 1.1: Relation to ITS 1.0 and New Principles</a>.</p></li><li><p>Added <a class="section-ref" href="#queryLanguage" shape="rect">Section 5.3.1: Choosing Query Language</a> as a stub.</p></li><li><p>Added <a class="section-ref" href="#LocaleFilter" shape="rect">Section 8.10: Locale Filter</a>.</p></li><li><p>Added <a class="sectionref" href="#domain" shape="rect">Section 8.8: Domain</a>.</p></li><li><p>Added <a class="section-ref" href="#usage-in-legacy-html" shape="rect">Section 1.4.5: Version of HTML</a>.</p></li><li><p>Added local markup in <a class="section-ref" href="#elements-within-text" shape="rect">Section 8.7: Elements Within Text</a>.</p></li><li><p>Added <a class="section-ref" href="#externalresource" shape="rect">Section 8.12: External Resource</a>.</p></li><li><p>Updated examples to use the <code class="its-attr-markup">version</code> attribute with the value
+              <code>2.0</code>.</p></li></ol><p id="changelog-since-20070403">The following log records major changes that have been
           made to this document between the <a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">ITS 1.0 Recommendation</a> and
           this document.</p><ol class="depth1"><li><p>Clarified <a href="#introduction" shape="rect">introduction</a> to cover ITS 2.0</p></li><li><p>Added a subsection on the relation to ITS 1.0 to the introduction, see <a class="section-ref" href="#relation-to-its10" shape="rect">Section 1.1.1: Relation to ITS 1.0</a></p></li><li><p>Created HTML based declarations for various data categories, see e.g., HTML
             declarations for the Terminology data category and the summary for local data categories
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/06/10 16:48:54	1.444
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/06/12 07:24:21	1.445
@@ -1758,6 +1758,7 @@
 <http://example.com/exampledoc.html#char=0,29>
  nif:wasConvertedFrom
  <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text())> .
+<!-- XML Example --> 
 <mappings>
  <mapping x="xpath(/html/body[1]/h2[1]/text()[1])" b="0" e="11" />
  <mapping x="xpath(/html/body[1]/h2[1]/span[1]/text()[1])" b="11" e="17" />
@@ -5779,12 +5780,12 @@
             <p xml:id="nif2its-algorithm-step1">STEP 1: NIF Web services accept two different types of input. It is possible to either send the extracted text (the object of the <code>nif:isString</code> property) directly or  NIF RDF to the NLP tool, i.e. the text is sent as a <code>nif:Context</code> node and included as <code>nif:isString</code>. Either way, the output of the Web service will be a NIF representation.
             </p>
             <p>Accepting text will be the minimal requirement of a NIF web service. Ideally, you would be able to send the <code>nif:Context</code> node with the isString as RDF directly, which has the advantage, that all other annotations can be used by the NLP tool:</p>
-            <eg><![CDATA[<rdf:Description rdf:about="http://example.com/exampledoc.html#char=0,29">
- <nif:sourceUrl rdf:resource="http://example.com/exampledoc.html"/>
- <nif:isString>Welcome to Dublin in Ireland!</nif:isString>
- <rdf:type rdf:resource="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#Context"/>
-</rdf:Description>
-]]></eg>
+            <eg><![CDATA[<http://example.com/exampledoc.html#char=0,29> 
+ rdf:type nif:RFC5147String ;
+ rdf:type nif:Context ;
+ nif:beginIndex "0" ;
+ nif:endIndex "29" ;
+ nif:isString  "Welcome to Dublin in Ireland!" .]]></eg>
           </item>
           <item>
             <p xml:id="nif2its-algorithm-step3">STEP 2: Use the mapping from ITS2NIF (available

Received on Wednesday, 12 June 2013 07:24:23 UTC