Author: buildbot
Date: Tue Feb 14 09:33:28 2012
New Revision: 804759
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/index.html
Propchange: websites/staging/stanbol/trunk/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 14 09:33:28 2012
@@ -1 +1 @@
-1243838
+1243845
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/index.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/index.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/index.html
Tue Feb 14 09:33:28 2012
@@ -68,24 +68,26 @@
<h2 id="list_of_available_enhancement_engines">List of Available Enhancement
Engines</h2>
<p>Apache Stanbol comes with a <a href="engines/list.html">list of predefined
enhancement engines</a>. These engines are supported by the Apache Stanbol
community. If you would like to implement your own enhancement engine, you
should go on reading this documentation.</p>
<h2 id="main_interfaces_and_utilities">Main Interfaces and Utilities</h2>
-<p>A <strong><a href="contentitem.html">Content Item</a></strong> is the unit
of content that Stanbol Enhancer can deal with. It gives access to the binary
content that was registered, and the graph that represents its metadata
(provided by client and/or generated). The <strong><a
href="engines/">Enhancement Engine</a></strong> provides the interface to
internal or external semantic enhancement engines. There will usually be
several of those, that the EnhancementJobManager uses to enhance content items.
The <strong>Enhancement Job Manager</strong> accepts requests for enhancing
ContentItems, and processes them either synchronously or asynchronously (as
decided by the enhancement engines or by configuration). The
<strong>Enhancement Engine Helper</strong> provides the classes for the
resulting enhancement structure according to the defined <strong>Enhancement
Structure</strong>.</p>
+<p>A <a href="contentitem.html">content item</a> is the unit of content that
Stanbol Enhancer can deal with. It gives access to the binary content that was
registered, and the graph that represents its metadata (provided by client
and/or generated). The <a href="engines/">enhancement engine</a> provides the
interface to internal or external semantic enhancement engines. There will
usually be several of those, that the EnhancementJobManager uses to enhance
content items. The <a href="enhancementjobmanager.html">enhancement job
manager</a> accepts requests for enhancing <a href="contentitem.html">content
items</a>, and processes them either synchronously or asynchronously (as
decided by the enhancement engines or by configuration). The enhancement engine
helper provides the classes for the resulting enhancement structure according
to the defined enhancement structure.</p>
<h2 id="enhancement_structure">Enhancement Structure</h2>
-<p>The enhancement structure for Apache Stanbol is been described <a
href="http://wiki.iks-project.eu/index.php/EnhancementStructure";>here</a> in
full. It defines the types and properties used for the resulting metadata graph
of Apache Stanbol. <em>Note: There is a proposal and ongoing discussion to
update this structure in the future.</em> Every <strong>Enhancement</strong>
type is a description which contains the following important properties:</p>
+<p>The enhancement structure for Apache Stanbol is been described <a
href="http://wiki.iks-project.eu/index.php/EnhancementStructure";>here</a> in
full. It defines the types and properties used for the resulting metadata graph
of Apache Stanbol.</p>
+<p><em>Note: There is a proposal and ongoing discussion to update this
structure in the future.</em></p>
+<p>Each enhancement type description which contains the following important
properties:</p>
<ul>
<li>creator: the specific enhancement engine creating this enhancement</li>
<li>creation time: the local system time, when the annotation was created</li>
-<li>extracted-from: the content item for the enhancement. This links to the ID
of the content item as assigned by Stanbol.</li>
+<li>extracted-from: the content item for the enhancement. This links to the ID
of the content item as assigned by Apache Stanbol.</li>
<li>type: the type of the enhancement (e.g. Location, Person, Location,
Concept ...).</li>
<li>confidence: The level of confidence in the range from 0 to 1 </li>
</ul>
-<p>A <strong>Text Annotation</strong> type provides metadata for the selected
text. This is intended to be used in addition to the enhancement type if an
enhancement is based on a part of the content.</p>
+<p>A text annotation type provides metadata for the selected text. This is
intended to be used in addition to the enhancement type if an enhancement is
based on a part of the content.</p>
<ul>
<li>start: the character position of the start of the selection. If start is
not defined it is assumed, that the selection starts at the beginning of the
document</li>
<li>end: the character position of the end of the selection. If end is not
defined it is assumed, that the selection ends at the end of the document.</li>
<li>selected-text: The text selected by the enhancement. (optional).</li>
<li>selection-context: The context of the selected text. This adds the
possibility to specify the context used to extract entities such as persons,
organizations, locations ... from natural language documents.</li>
</ul>
-<p>The <strong>Entity Annotation</strong> refer to named entities which have
been recognized within the content. This type is intended to be used together
with the FISE enhancement type.</p>
+<p>The entity annotation type refers to named entities which have been
recognized within the content. This type is intended to be used together with
the FISE enhancement type.</p>
<ul>
<li>entity-reference: This refers to the URI identifying the Entity</li>
<li>entity-label: The label(s) of the referred entity</li>
@@ -93,7 +95,7 @@
<li>The occurrences of the entity within the content (the exact positions
within the text where this entity is referred) are determined by outgoing
dc:relation links.</li>
</ul>
<h2 id="response_in_rdf">Response in RDF</h2>
-<p>Apache Stanbol Enhancer is able to serialize the response in the following
RDF formats:</p>
+<p>The Apache Stanbol enhancer is able to serialize the response in the
following RDF formats:</p>
<div class="codehilite"><pre><span class="n">application</span><span
class="o">/</span><span class="n">json</span> <span class="p">(</span><span
class="n">JSON</span><span class="o">-</span><span class="n">LD</span><span
class="p">)</span>
<span class="n">application</span><span class="sr">/rdf+xml (RDF/</span><span
class="n">XML</span><span class="p">)</span>
<span class="n">application</span><span class="sr">/rdf+json (RDF/</span><span
class="n">JSON</span><span class="p">)</span>
