- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Fri, 07 Jun 2013 08:36:43 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv7560
Modified Files:
its20.html its20.odd
Log Message:
small fixes in NIF section
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/06 09:56:55 1.441
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html 2013/06/07 08:36:43 1.442
@@ -1197,8 +1197,7 @@
<span class="hl-attribute" style="color: #F5844C">its-ta-ident-ref</span>=<span class="hl-value" style="color: #993300">"http://dbpedia.org/resource/Dublin"</span> <span class="hl-attribute" style="color: #F5844C">its-within-text</span>=<span class="hl-value" style="color: #993300">"yes"</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">></strong>Dublin<strong class="hl-tag" style="color: #000096"></span></strong> in <strong class="hl-tag" style="color: #000096"><b</strong> <span class="hl-attribute" style="color: #F5844C">translate</span>=<span class="hl-value" style="color: #993300">"no"</span> <span class="hl-attribute" style="color: #F5844C">its-within-text</span>=<span class="hl-value" style="color: #993300">"yes"</span><strong class="hl-tag" style="color: #000096">></strong>Ireland<strong class="hl-tag" style="color: #000096"></b></strong>!<strong class="hl-tag" style="color: #000096"></h2></strong><strong class="hl-tag" style="color: #000096"></body></strong><strong class="hl-tag" style="color: #000096"></html></strong></pre></div></div><p id="its2nif-algorithm">The conversion algorithm to generate NIF consists of seven
steps.</p><ul><li><p id="its2nif-algorithm-step1">STEP 1: Get an ordered list of all text nodes
- of the document.</p></li><li><p id="its2nif-algorithm-step2">STEP 2: Generate an XPath expression for each non-empty text node of all leaf elements and memorize them.</p></li><li><p id="its2nif-algorithm-step3">STEP 3: Get the text for each node and make a
- tuple with the XPath expressions (X,T). Since the text nodes have a certain order we
+ of the document.</p></li><li><p id="its2nif-algorithm-step2">STEP 2: Generate an XPath expression for each non-empty text node of all leaf elements and memorize them.</p></li><li><p id="its2nif-algorithm-step3">STEP 3: Get the text for each text node and make a tuple with the corresponding XPath expression (X,T). Since the text nodes have a certain order we
now have a list of ordered tuples ((x0,t0), (x1,t1), ..., (xn,tn)).</p></li><li><p id="its2nif-algorithm-step4">STEP 4 (optional): Serialize as XML or as RDF.
The list with the XPath-to-text mapping can also be kept in memory. Part of a
serialization example is given below. The upper part is in RDF Turtle Syntax while the lower part
@@ -5860,7 +5859,7 @@
itsrdf:taIdentRef <http://dbpedia.org/resource/Ireland> .
<http://dbpedia.org/resource/Ireland>
rdf:type <http:/nerd.eurecom.fr/ontology#Country> .</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:iString</code> property) directly or NIF RDF to the NLP tool, i.e. the text is send 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.
+ 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"><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">></strong>
<strong class="hl-tag" style="color: #000096"><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">/></strong>
<strong class="hl-tag" style="color: #000096"><nif:isString></strong>Welcome to Dublin in Ireland!<strong class="hl-tag" style="color: #000096"></nif:isString></strong>
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/06 09:56:55 1.441
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/07 08:36:43 1.442
@@ -1686,8 +1686,7 @@
<item><p xml:id="its2nif-algorithm-step1">STEP 1: Get an ordered list of all text nodes
of the document.</p></item>
<item><p xml:id="its2nif-algorithm-step2">STEP 2: Generate an XPath expression for each non-empty text node of all leaf elements and memorize them.</p></item>
- <item><p xml:id="its2nif-algorithm-step3">STEP 3: Get the text for each node and make a
- tuple with the XPath expressions (X,T). Since the text nodes have a certain order we
+ <item><p xml:id="its2nif-algorithm-step3">STEP 3: Get the text for each text node and make a tuple with the corresponding XPath expression (X,T). Since the text nodes have a certain order we
now have a list of ordered tuples ((x0,t0), (x1,t1), ..., (xn,tn)).</p></item>
<item><p xml:id="its2nif-algorithm-step4">STEP 4 (optional): Serialize as XML or as RDF.
The list with the XPath-to-text mapping can also be kept in memory. Part of a
@@ -5765,7 +5764,7 @@
of two steps.</p>
<list type="unordered">
<item>
- <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:iString</code> property) directly or NIF RDF to the NLP tool, i.e. the text is send 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 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">
Received on Friday, 7 June 2013 08:36:49 UTC