Author: buildbot
Date: Tue Oct 28 11:18:55 2014
New Revision: 927146
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/nif20.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Oct 28 11:18:55 2014
@@ -1 +1 @@
-1634579
+1634847
Modified:
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/nif20.html
==============================================================================
---
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/nif20.html
(original)
+++
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/nif20.html
Tue Oct 28 11:18:55 2014
@@ -91,17 +91,17 @@
<h1 class="title">NIF 2.0 Transformation Engine</h1>
<p>Typically low level NLP results are not included to the RDF enhancement
results. This engine supports the serialization of such results by using the <a
href="http://persistence.uni-leipzig.org/nlp2rdf/";>NIF 2.0</a> (NLP Interchange
Format) standard.</p>
<h2 id="processed-information-input">Processed Information (Input)</h2>
-<p>Apache Stanbol manages NLP results by the <a
href="../nlp/analyzedtext">Analysed Text</a> content part. This ContentPart
provides a Java API for accessing those results. This engine reads such
information and transformes it according to the <a
href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core/nif-core.html";>NIF
2.0</a> core ontology. </p>
+<p>Apache Stanbol manages NLP results by the <a
href="../nlp/analyzedtext">Analysed Text</a> content part. This ContentPart
provides a Java API for accessing those results. This engine reads such
information and transformes it according to the <a
href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core/nif-core.html";>NIF
2.0</a> core ontology. Transformed information will be added as RDF to the
Enhancement Metadata and be included in the RDF response of the enhancement
request. </p>
<p>If a ContentItem does not contain this content part it will not be
processed by this engine.</p>
<h2 id="created-rdf">Created RDF</h2>
-<p>The engine serializes the following information:</p>
+<p>The engine serializes NLP annotations as defined by the <a
href="http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core/nif-core.html";>NIF
2.0 core ontology</a>. More specifically the engine is capable of it the
following information:</p>
<ul>
-<li>Segment URIs by using the <a href="http://tools.ietf.org/html/rfc5147";>RFC
5147</a> URI scheme</li>
-<li>Selector information like <code>nif:beginIndex</code>,
<code>nif:endIndex</code> as well as <code>nif:before</code>,
<code>nif:anchorOf</code> and <code>nif:after</code>. For spans longer as 100
chars the <code>nif:head</code> property is used instead of
<code>nif:anchorOf</code>.</li>
-<li>Context information: This includes <code>nif:referenceContext</code> links
for all Strings as well as additional metadata for the context.</li>
-<li>String hierarchies: <code>nif:sub-/nif:superWord</code>,
<code>nif:sentence</code></li>
-<li>String navigation: <code>nif:next-/nif:previousSentnece</code>,
<code>nif:next-/nif:previousWord</code></li>
-<li>String annotations: <code>nif:oliaCategory</code>,
<code>nif:oliaConfidence</code> and <code>nif:posTag</code></li>
+<li>Segment URIs do use <a href="http://tools.ietf.org/html/rfc5147";>RFC
5147</a>. It can be configured if the <code>nif:RFC5147String</code> type is
only added to the <code>nif:Context</code> instance or to all serialized
<code>nif:String</code>instances.</li>
+<li>Selector information like <code>nif:beginIndex</code>,
<code>nif:endIndex</code> as well as <code>nif:before</code>,
<code>nif:anchorOf</code> and <code>nif:after</code>. For spans longer as 100
chars the <code>nif:head</code> property is used instead of
<code>nif:anchorOf</code>. Their is an option to prevent those features to be
serialized. This will greatly decrease the triple count however clients will
need to parse the start/end positions from the segment URI.</li>
+<li>All serialized <code>nif:String</code> instances do refer the
<code>nif:Context</code> with the <code>nif:referenceContext</code>. The
context will refer to the URI of the ContentItem by using the
<code>nif:sourceUrl</code> property. The inclusion of the content as String
literal is NOT supported by this engine.</li>
+<li>String hierarchies: This includes <code>nif:subWord</code>
<code>nif:superWord</code> and <code>nif:sentence</code> properties. If not
required serializing of those can be deactivated.</li>
+<li>String navigation: This includes <code>nif:nextSentence</code>,
<code>nif:previousSentnece</code>, <code>nif:nextWord</code> and
<code>nif:previousWord</code> properties. The transitive versions of those
properties are NOT supported. Users that want to have transitive reasoning will
anyway get those from the reasoner. String navigation properties can be
deactivated. This will greatly decrease the triple count.</li>
+<li>String annotations: This currently includes <code>nif:oliaCategory</code>,
<code>nif:oliaConfidence</code> and <code>nif:posTag</code>.
<code>nif:oliaLink</code> is not supported as the Stanbol NLP API does not
provide the required information. Also support for word level sentiment
annotations is not yet implemented.</li>
</ul>
<h3 id="configuration">Configuration</h3>
<p>The Engine supports several switches that allow to enable/disable the
serialization of NIF information. The engine supports the configuration of
multiple instances with different configurations. The following figure shows
the configuration dialog:</p>
