You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by bu...@apache.org on 2012/02/16 11:29:24 UTC
svn commit: r805052 [1/3] - in /websites/staging/stanbol/trunk: ./
content/stanbol/css/ content/stanbol/docs/trunk/enhancer/
content/stanbol/docs/trunk/enhancer/chains/
content/stanbol/docs/trunk/enhancer/engines/
Author: buildbot
Date: Thu Feb 16 10:29:23 2012
New Revision: 805052
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/css/stanbol.css
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/contentitem.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/list.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancementjobmanager.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.html
Propchange: websites/staging/stanbol/trunk/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb 16 10:29:23 2012
@@ -1 +1 @@
-1244912
+1244919
Modified: websites/staging/stanbol/trunk/content/stanbol/css/stanbol.css
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/css/stanbol.css (original)
+++ websites/staging/stanbol/trunk/content/stanbol/css/stanbol.css Thu Feb 16 10:29:23 2012
@@ -137,7 +137,7 @@ div.codehilite {
border: 1px solid #bebab0;
line-height: 133%;
}
-span.c1 {
+span.c1, span.cm {
color: #667f5b;
}
span.k {
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.html Thu Feb 16 10:29:23 2012
@@ -57,7 +57,7 @@
<div id="content">
<h1 class="title">DefaultChain</h1>
- <p>Implementation that keeps track of all currently active <a href="../engines/enhancementengine.html">EnhancementEngine</a> and registers itself as a Chain service with the "stanbol.enhancer.chain.name=default" an service ranking of Integer.MIN_VALUE.</p>
+ <p>Implementation that keeps track of all currently active <a href="../engines">EnhancementEngine</a> and registers itself as a Chain service with the "stanbol.enhancer.chain.name=default" an service ranking of Integer.MIN_VALUE.</p>
<p>This will cause this chain to be returned by the ChainManager.getDefault() method if users:</p>
<ul>
<li>do not deactivate this Chain (see below)</li>
@@ -71,7 +71,7 @@
<p>Note that the DefaultChain does not actually implement the Chain interface, but only registers an instance of the AllActiveEnginesChain on activation.
The implementation is part of the "org.apache.stanbol.enhancer.chain.allactive" module.</p>
<h3 id="calculation_of_the_executionplan">Calculation of the ExecutionPlan</h3>
-<p>This chain considers all currently active <a href="../engines/enhancementengine.html">EnhancementEngine</a>s. The ExecutionPlan is calculated by using the value for the "org.apache.stanbol.enhancer.engine.order" property provided by the EnhancementEngine:</p>
+<p>This chain considers all currently active <a href="../engines">EnhancementEngine</a>s. The ExecutionPlan is calculated by using the value for the "org.apache.stanbol.enhancer.engine.order" property provided by the EnhancementEngine:</p>
<ul>
<li>Engines with a lower order are executed before Engines with a higher value</li>
<li>Engines with the same order may be executed simultaneously if the EnhancementJobMananger and the EnhancementEngine do support this feature.</li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.html Thu Feb 16 10:29:23 2012
@@ -72,13 +72,13 @@
<li><strong>ep:inExecutionPlan</strong> (domain: ep:ExecutionNode; range: ep:ExecutionPlan ;inverseOf: ep:hasExecutionNode): functional property that links the execution node with an execution plan</li>
<li><strong>ep:engine</strong> (domain: ep:ExecutionNode; range: xsd:string): The property used to link to the Enhancement Engine by the name of the engine.</li>
<li><strong>ep:dependsOn</strong> (domain: ep:ExecutionNode; range: ep:ExecutionNode) Defines that the execution of this node depends on the completion of the referenced one.</li>
-<li><strong>ep:optional</strong> (domain: ep:ExecutionNode; range: xsd:boolean) Can be used to specify that the execution of this <a href="../engines/enhancementengine.html">EnhancementEngine</a> is optional. If this property is set to TRUE an engine will be marked as executed even if it execution was not possible (e.g. because an engine with this name was not active) or the execution failed (e.g. because of the Exception). </li>
+<li><strong>ep:optional</strong> (domain: ep:ExecutionNode; range: xsd:boolean) Can be used to specify that the execution of this <a href="../engines">EnhancementEngine</a> is optional. If this property is set to TRUE an engine will be marked as executed even if it execution was not possible (e.g. because an engine with this name was not active) or the execution failed (e.g. because of the Exception). </li>
</ul>
</li>
</ul>
<p>Note the the data for the ep:ExecutionPlan and the ep:hasExecutionNode/ep:inExecutionPlan typically need not to be parsed as configuration of a Chain. This information are typically automatically added based on the assumption that all ep:ExecutionNode parsed in the configuration for a chain are member of the execution plan for such chain. Therefore this information is typically added by the Chain itself when the configuration is parsed and validated.</p>
<h4 id="example">Example:</h4>
-<p>This example shows an ExecutionPlan with three nodes for the "langId", "ner", "dbpediaLinking" "geonamesLinking" and "zemanta" engine. Note that this names refer to actual <a href="../engines/enhancementengine.html">EnhancementEngine</a> Services registered with the current OSGI Environment.</p>
+<p>This example shows an ExecutionPlan with three nodes for the "langId", "ner", "dbpediaLinking" "geonamesLinking" and "zemanta" engine. Note that this names refer to actual <a href="../engines">EnhancementEngine</a> Services registered with the current OSGI Environment.</p>
<p>This example assumes that</p>
<ul>
<li>"langId" is the singleton instance of <a href="../engines/langidengine.html">LangIdEnhancementEngine</a></li>
@@ -88,39 +88,39 @@
<li>"zemanta" is the singleton instance of the <a href="../engines/zemantaengine.html">ZemantaEnhancementEngine</a></li>
</ul>
<p>The RDF graph of such a chain would look:</p>
-<div class="codehilite"><pre><span class="err">urn:execPlan</span>
- <span class="err">rdf:type</span> <span class="err">ep:ExecutionPlan</span>
- <span class="err">ep:hasExecutionNode</span> <span class="err">urn:node1,</span> <span class="err">urn:node2,</span> <span class="err">urn:node3,</span> <span class="err">urn:node4,</span> <span class="err">urn:node5</span>
- <span class="err">ep:chain</span> <span class="err">"demoChain"</span>
-
-<span class="err">urn:node1</span>
- <span class="err">rdf:type</span> <span class="err">stanbol:ExecutionNode</span>
- <span class="err">ep:inExecutionPlan</span> <span class="err">urn:execPlan</span>
- <span class="err">stanbol:engine</span> <span class="err">langId</span>
-
-<span class="err">urn:node2</span>
- <span class="err">rdf:type</span> <span class="err">ep:ExecutionNode</span>
- <span class="err">ep:inExecutionPlan</span> <span class="err">urn:execPlan</span>
- <span class="err">ep:dependsOn</span> <span class="err">urn:node1</span>
- <span class="err">ep:engine</span> <span class="err">ner</span>
-
-<span class="err">urn:node3</span>
- <span class="err">rdf:type</span> <span class="err">ep:ExecutionNode</span>
- <span class="err">ep:inExecutionPlan</span> <span class="err">urn:execPlan</span>
- <span class="err">ep:dependsOn</span> <span class="err">urn:node1</span>
- <span class="err">ep:engine</span> <span class="err">dbpediaLinking</span>
-
-<span class="err">urn:node4</span>
- <span class="err">rdf:type</span> <span class="err">ep:ExecutionNode</span>
- <span class="err">ep:inExecutionPlan</span> <span class="err">urn:execPlan</span>
- <span class="err">ep:dependsOn</span> <span class="err">urn:node1</span>
- <span class="err">ep:engine</span> <span class="err">geonamesLinking</span>
-
-<span class="err">urn:node5</span>
- <span class="err">rdf:type</span> <span class="err">ep:ExecutionNode</span>
- <span class="err">ep:inExecutionPlan</span> <span class="err">urn:execPlan</span>
- <span class="err">ep:engine</span> <span class="err">zemanta</span>
- <span class="err">ep:optional</span> <span class="err">"true"^^xsd:boolean</span>
+<div class="codehilite"><pre>urn:execPlan
+ rdf:type ep:ExecutionPlan
+ ep:hasExecutionNode urn:node1, urn:node2, urn:node3, urn:node4, urn:node5
+ ep:chain "demoChain"
+
+urn:node1
+ rdf:type stanbol:ExecutionNode
+ ep:inExecutionPlan urn:execPlan
+ stanbol:engine langId
+
+urn:node2
+ rdf:type ep:ExecutionNode
+ ep:inExecutionPlan urn:execPlan
+ ep:dependsOn urn:node1
+ ep:engine ner
+
+urn:node3
+ rdf:type ep:ExecutionNode
+ ep:inExecutionPlan urn:execPlan
+ ep:dependsOn urn:node1
+ ep:engine dbpediaLinking
+
+urn:node4
+ rdf:type ep:ExecutionNode
+ ep:inExecutionPlan urn:execPlan
+ ep:dependsOn urn:node1
+ ep:engine geonamesLinking
+
+urn:node5
+ rdf:type ep:ExecutionNode
+ ep:inExecutionPlan urn:execPlan
+ ep:engine zemanta
+ ep:optional "true"^^xsd:boolean
</pre></div>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.html Thu Feb 16 10:29:23 2012
@@ -57,18 +57,18 @@
<div id="content">
<h1 class="title">GraphChain</h1>
- <p>The GraphChain allows to directly configure the ExecutionPlan returned by the Chain.getExecutionPlan() method. This means on the one hand that it allows to configure any kind of execution process on the other hand its usage also requires a lot of knowledge about the <a href="../engines/enhancementengine.html">EnhancementEngine</a>s and the ExecutionPlan model form the user.</p>
+ <p>The GraphChain allows to directly configure the ExecutionPlan returned by the Chain.getExecutionPlan() method. This means on the one hand that it allows to configure any kind of execution process on the other hand its usage also requires a lot of knowledge about the <a href="../engines">EnhancementEngine</a>s and the ExecutionPlan model form the user.</p>
<p>Typically it is a good practice to start with other - more simple to use - Chain implementation such as the <a href="weightedchain.html">Weighted Chain</a> and only afterwards convert this configuration to a GraphChain to configure optimizations to the enhancement process such as to allow more Engines to be executed in parallel.</p>
<h3 id="configuration">Configuration</h3>
<p>The GraphChain supports two variants to configure the ExecutionPlan</p>
<h4 id="graphresource">GraphResource</h4>
<p>A GraphResource is a RDF file available via the DataFileProvider. The easiest way is to copy the RDF file defining the ExecutionPlan to the "/sling/datafile" directory within the Stanbol home directory. The configuration of the GraphChain needs than only to refer to that file such as:</p>
-<div class="codehilite"><pre><span class="n">stanbol</span><span class="o">.</span><span class="n">enhancer</span><span class="o">.</span><span class="n">chain</span><span class="o">.</span><span class="n">graph</span><span class="o">.</span><span class="n">graphresource</span><span class="o">=</span><span class="n">myExecutionPlan</span><span class="o">.</span><span class="n">rdf</span>
+<div class="codehilite"><pre>stanbol.enhancer.chain.graph.graphresource=myExecutionPlan.rdf
</pre></div>
<p>The used RDF encoding is guessed by the file extension. If the extension is not recognized the format can be also parsed as additional parameter</p>
-<div class="codehilite"><pre><span class="n">stanbol</span><span class="o">.</span><span class="n">enhancer</span><span class="o">.</span><span class="n">chain</span><span class="o">.</span><span class="n">graph</span><span class="o">.</span><span class="n">graphresource</span><span class="o">=</span><span class="n">myExecutionPlan</span><span class="o">.</span><span class="n">something</span><span class="p">;</span><span class="nb">format</span><span class="o">=</span><span class="n">application</span><span class="o">/</span><span class="n">rdf</span><span class="o">+</span><span class="n">xml</span>
+<div class="codehilite"><pre>stanbol.enhancer.chain.graph.graphresource=myExecutionPlan.something;format=application/rdf+xml
</pre></div>
@@ -77,24 +77,24 @@
<p>This allows to directly configure the ExecutionPlan as value of the "stanbol.enhancer.chain.graph.chainlist" property. Both arrays and Collections are supported. </p>
<p><em>NOTE</em>: As soon as a graph resource is configures the ChainList is ignored. This is even true if the configured GraphResource is currently not available!</p>
<p>The Syntax is defined as follows:</p>
-<div class="codehilite"><pre><span class="p">{</span><span class="n">engine</span><span class="o">-</span><span class="n">name</span><span class="p">};[</span><span class="n">optional</span><span class="p">];[</span><span class="n">dependsOn</span><span class="o">=</span><span class="p">{</span><span class="n">engine</span><span class="o">-</span><span class="n">name1</span><span class="p">},{</span><span class="n">engine</span><span class="o">-</span><span class="n">name2</span><span class="p">}]</span>
+<div class="codehilite"><pre>{engine-name};[optional];[dependsOn={engine-name1},{engine-name2}]
</pre></div>
<p>The following Example shows how this Syntax can be used to define an ExecutionPlan.</p>
-<div class="codehilite"><pre><span class="n">metaxa</span><span class="p">;</span><span class="n">optional</span>
-<span class="n">langId</span><span class="p">;</span><span class="n">dependsOn</span><span class="o">=</span><span class="n">metaxa</span>
-<span class="n">ner</span><span class="p">;</span><span class="n">dependsOn</span><span class="o">=</span><span class="n">langId</span>
-<span class="n">zemanta</span><span class="p">;</span><span class="n">optional</span>
-<span class="n">dbpedia</span><span class="o">-</span><span class="n">linking</span><span class="p">;</span><span class="n">dependsOn</span><span class="o">=</span><span class="n">ner</span>
-<span class="n">geonames</span><span class="p">;</span><span class="n">optional</span><span class="p">;</span><span class="n">dependsOn</span><span class="o">=</span><span class="n">ner</span>
-<span class="n">refactor</span><span class="p">;</span><span class="n">dependsOn</span><span class="o">=</span><span class="n">geonames</span><span class="p">,</span><span class="n">dbpedia</span><span class="o">-</span><span class="n">linking</span><span class="p">,</span><span class="n">zemanta</span>
+<div class="codehilite"><pre>metaxa;optional
+langId;dependsOn=metaxa
+ner;dependsOn=langId
+zemanta;optional
+dbpedia-linking;dependsOn=ner
+geonames;optional;dependsOn=ner
+refactor;dependsOn=geonames,dbpedia-linking,zemanta
</pre></div>
<p>Not that the internal oder of the list does not influence the resulting ExecutionPlan. Only the "dependsOn" properties are used to determine the execution order of the Engines and if Engines can be executed in parallel.</p>
<p>Within an osgi configuration file (org.apache.stanbol.enhancer.chain.graph.impl.GraphChain-myGraphChain.config) this would look like</p>
-<div class="codehilite"><pre><span class="n">stanbol</span><span class="o">.</span><span class="n">enhancer</span><span class="o">.</span><span class="n">chain</span><span class="o">.</span><span class="n">graph</span><span class="o">.</span><span class="n">chainlist</span><span class="o">=</span><span class="p">[</span><span class="s">"metaxa;optional"</span><span class="p">,</span><span class="s">"langId;dependsOn\=metaxa"</span><span class="p">,</span><span class="s">"ner;dependsOn\=langId"</span><span class="p">,</span><span class="s">"zemanta;optional"</span><span class="p">,</span><span class="s">"dbpedia-linking;dependsOn\=ner"</span><span class="p">,</span><span class="s">"geonames;optional;dependsOn\=ner"</span><span class="p">,</span><span class="s">"refactor;dependsOn\=geonames,dbpedia-linking,zemanta"</span><span class="p">]</span>
+<div class="codehilite"><pre>stanbol.enhancer.chain.graph.chainlist=["metaxa;optional","langId;dependsOn\=metaxa","ner;dependsOn\=langId","zemanta;optional","dbpedia-linking;dependsOn\=ner","geonames;optional;dependsOn\=ner","refactor;dependsOn\=geonames,dbpedia-linking,zemanta"]
</pre></div>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/index.html Thu Feb 16 10:29:23 2012
@@ -57,15 +57,15 @@
<div id="content">
<h1 class="title">Enhancement Chains</h1>
- <p>An Enhancement Chain defines how Content parsed to the Stanbol Enhancer is processed. More concrete it defines what <a href="../engines/enhancementengine.html">EnhancementEngine</a>s and in what order are used to process <a href="../contentitem.html">ContentItem</a>s. Chains are not responsible for the actual processing of ContentItems. They provide the <a href="executionplan.html">ExecutionPlan</a> to the <a href="../enhancementjobmanager.html">EnhancementJobManger</a> that does the actual processing of the ContentItem.</p>
+ <p>An Enhancement Chain defines how Content parsed to the Stanbol Enhancer is processed. More concrete it defines what <a href="../engines">EnhancementEngine</a>s and in what order are used to process <a href="../contentitem.html">ContentItem</a>s. Chains are not responsible for the actual processing of ContentItems. They provide the <a href="executionplan.html">ExecutionPlan</a> to the <a href="../enhancementjobmanager.html">EnhancementJobManger</a> that does the actual processing of the ContentItem.</p>
<p>In the RESTful API enhancement chains can be accessed by there name under</p>
-<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}:{</span><span class="n">port</span><span class="p">}</span><span class="sr">/{stanbol-path}/</span><span class="n">enhancer</span><span class="sr">/chain/</span><span class="p">{</span><span class="n">chain</span><span class="o">-</span><span class="n">name</span><span class="p">}</span>
+<div class="codehilite"><pre>http://{host}:{port}/{stanbol-path}/enhancer/chain/{chain-name}
</pre></div>
<p>Enhancement requestes issued to </p>
-<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}:{</span><span class="n">port</span><span class="p">}</span><span class="sr">/{stanbol-path}/</span><span class="n">enhancer</span>
-<span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}:{</span><span class="n">port</span><span class="p">}</span><span class="sr">/{stanbol-path}/</span><span class="n">engines</span>
+<div class="codehilite"><pre>http://{host}:{port}/{stanbol-path}/enhancer
+http://{host}:{port}/{stanbol-path}/engines
</pre></div>
@@ -112,7 +112,7 @@
<p>within the activate method of the Chain. There is also an AbstractChain implementation provided by the servicesapi module of the Stanbol Enhancer that already implements this functionality.</p>
-<p>The getEngines method returns the name of all <a href="../engines/enhancementengine.html">EnhancementEngine</a>s referenced by a Chain. Note that this method returns a Set. This method is intended to allow fast access to the referenced engines and does not provide any information about the execution order.</p>
+<p>The getEngines method returns the name of all <a href="../engines">EnhancementEngine</a>s referenced by a Chain. Note that this method returns a Set. This method is intended to allow fast access to the referenced engines and does not provide any information about the execution order.</p>
<p>Components that need to know the details about a Chain need to process the <a href="executionplan.html">ExecutionPlan</a> returned by the getExectuonPlan() method. The <a href="executionplan.html">ExecutionPlan</a> is represented as an RDF graph following the ExecutionPlan Ontology. It formally describes how a ContentItem must be processed by the EnhancementJobManager. For details see the documentation for the <a href="executionplan.html">ExecutionPlan</a>.</p>
<p>For Chain implementation it is important that the returned Graph holding the execution plan MUST BE read-only AND final. Meaning that a change in the configuration of a Chain MUST NOT change the graph returned by calls to the getExecutionPlan method.</p>
<p>Because the configuration of a Chain might change at any time EnhancementJobManager implementation MUST retrieve the execution plan once and than use this instance for the whole enhancement process. Because of the above requirement that the execution plan is stored in an read-only and final Graph this ensures that the plan can not change even for long lasting enhancement processes. Therefore any change to the configuration of a chain will not influence ongoing enhancement processes.</p>
@@ -135,7 +135,7 @@
<li>the Chain with the lowest "service.id"</li>
</ol>
<p>If no chain is active a ChainException with an according message MUST BE thrown.</p>
-<p>All Stanbol launchers are configured with the <a href="defaultchain.html">Default Chain</a> enabled. This registers itself with the name "default" and the lowest possible service ranking - Integer.MIN_VALUE. This default provides a Chain that considered all currently active <a href="../engines/enhancementengine.html">EnhancementEngine</a>s and sorts them based on there ordering information (see the <a href="weightedchain.html#calculation_of_the_executionplan">Calculation of the Execution Plan based on the EnhancementEngine Ordering</a> for details).</p>
+<p>All Stanbol launchers are configured with the <a href="defaultchain.html">Default Chain</a> enabled. This registers itself with the name "default" and the lowest possible service ranking - Integer.MIN_VALUE. This default provides a Chain that considered all currently active <a href="../engines">EnhancementEngine</a>s and sorts them based on there ordering information (see the <a href="weightedchain.html#calculation_of_the_executionplan">Calculation of the Execution Plan based on the EnhancementEngine Ordering</a> for details).</p>
<h3 id="chainmanager_interface">ChainManager interface</h3>
<p>The <a href="chainmanager.html">ChainManager</a> is the management interface for EnhancementChains that can be used by components to lookup chains based on their name. It also provides a getter for the default chain. There is also OSGI ServiceTracker like implementation that can be used to track only chains with specific names and to get even notified on any change of such chains.</p>
<h2 id="chain_implementations">Chain implementations</h2>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.html Thu Feb 16 10:29:23 2012
@@ -57,14 +57,14 @@
<div id="content">
<h1 class="title">ListChain</h1>
- <p>The List Chain creates the ExecutionPlan based on the exact order of the configured <a href="../engines/enhancementengine.html">EnhancementEngine</a>s. This provides users with a simple possibility configure the exact oder in that the referenced EnhancementEngines are called during the enhancement process of a content item. However the ListChain can not support parallel execution of engines a considerable disadvantage in contrast to the <a href="graphchain.html">GraphChain</a>.</p>
+ <p>The List Chain creates the ExecutionPlan based on the exact order of the configured <a href="../engines">EnhancementEngine</a>s. This provides users with a simple possibility configure the exact oder in that the referenced EnhancementEngines are called during the enhancement process of a content item. However the ListChain can not support parallel execution of engines a considerable disadvantage in contrast to the <a href="graphchain.html">GraphChain</a>.</p>
<p>A typical usage scenario would be that users start of with configuring a ListChain and later optimize the execution by migrating functional configuration to <a href="graphchain.html">GraphChain</a>s.</p>
<h3 id="configuration">Configuration</h3>
<p>The property "stanbol.enhancer.chain.list.enginelist" is used to provide the list of engine names. This configuration MUST BE parsed as an Array as string because the ordering if the configured entries is central for the configuration.</p>
<p>In addition it is possible to define Engines as optional. This allows to specify that the enhancement process should not fail if an Engine is not active or fails while processing a content item.</p>
<p>The syntax to define an Engine as optional is as follows</p>
-<div class="codehilite"><pre><span class="sr"><name></span><span class="p">;</span><span class="n">optional</span>
-<span class="sr"><name></span><span class="p">;</span><span class="n">optional</span><span class="o">=</span><span class="n">true</span>
+<div class="codehilite"><pre><name>;optional
+<name>;optional=true
</pre></div>
@@ -73,13 +73,13 @@
<p><img alt="Configuration Dialog for the ListChain" src="enhancer-listchain-config.png" title="Sceenshot of the Configuration Dialog for a ListChain with required and optional Engines" /></p>
<p>It is also possible to configure a ListChain by directly installing a configuration with the name "{classname}-{configName}.config". Note that the {configName} needs not to be the same as the name of the chain. The {configName} is just used by the OSGI environment to distinguish different configuration for {classname}.</p>
<p>To create the same configuration as in the above screenshot the file would need to look like this:</p>
-<div class="codehilite"><pre><span class="n">stanbol</span><span class="o">.</span><span class="n">enhancer</span><span class="o">.</span><span class="n">chain</span><span class="o">.</span><span class="n">name</span><span class="o">=</span><span class="s">"list"</span>
-<span class="n">stanbol</span><span class="o">.</span><span class="n">enhancer</span><span class="o">.</span><span class="n">chain</span><span class="o">.</span><span class="n">list</span><span class="o">.</span><span class="n">enginelist</span><span class="o">=</span><span class="p">[</span><span class="s">"metaxa;optional"</span><span class="p">,</span><span class="s">"langid"</span><span class="p">,</span><span class="s">"ner"</span><span class="p">,</span><span class="s">"dbpediaLinking"</span><span class="p">]</span>
+<div class="codehilite"><pre>stanbol.enhancer.chain.name="list"
+stanbol.enhancer.chain.list.enginelist=["metaxa;optional","langid","ner","dbpediaLinking"]
</pre></div>
<h3 id="calculation_of_the_executionplan">Calculation of the ExecutionPlan</h3>
-<p>The ExecutionPlan is created based on the exact order of the <a href="../engines/enhancementengine.html">EnhancementEngine</a>s provided by the "stanbol.enhancer.chain.list.enginelist" property. The configuration MUST contain at least a single engine. In addition no engine MUST be mentioned twice.</p>
+<p>The ExecutionPlan is created based on the exact order of the <a href="../engines">EnhancementEngine</a>s provided by the "stanbol.enhancer.chain.list.enginelist" property. The configuration MUST contain at least a single engine. In addition no engine MUST be mentioned twice.</p>
</div>
<div id="footer">
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.html Thu Feb 16 10:29:23 2012
@@ -57,21 +57,21 @@
<div id="content">
<h1 class="title">WeightedChain</h1>
- <p>The Wighted Chain takes a list of <a href="../engines/enhancementengine.html">EnhancementEngine</a> names as input and uses the "org.apache.stanbol.enhancer.engine.order" metadata of the configured Engines to calculate the ExecutionPlan.</p>
+ <p>The Wighted Chain takes a list of <a href="../engines">EnhancementEngine</a> names as input and uses the "org.apache.stanbol.enhancer.engine.order" metadata of the configured Engines to calculate the ExecutionPlan.</p>
<p>This Chain is designed for easy configuration - just a list of the engine names - but has limited possibilities to control the execution order.</p>
<h3 id="configuration">Configuration</h3>
<p>The property "stanbol.enhancer.chain.weighted.chain" is used to provide the list of engine names. Both Arrays and Collections are supported as values.</p>
<p>In addition it is possible to define Engines as optional. This allows to specify that the enhancement process should not fail if an Engine is not active or fails while processing a content item.</p>
<p>The syntax to define an Engine as optional is as follows</p>
-<div class="codehilite"><pre><span class="sr"><name></span><span class="p">;</span><span class="n">optional</span>
-<span class="sr"><name></span><span class="p">;</span><span class="n">optional</span><span class="o">=</span><span class="n">true</span>
+<div class="codehilite"><pre><name>;optional
+<name>;optional=true
</pre></div>
<p>both variants result that the execution of the engine with the name <name> is optional.</p>
<p><img alt="Configuration Dialog for the WeightedCahin" src="enhancer-weightedchain-config.png" title="Sceenshot of the Configuration Dialog for a WeightedChain with two required and one optional Engine" /></p>
<h3 id="calculation_of_the_executionplan">Calculation of the ExecutionPlan</h3>
-<p>It is important to note that the ordering of the list has no influence on the ExecutionPlan because the order of execution of the configured <a href="../engines/enhancementengine.html">EnhancementEngine</a>s is calculated only by using the value for the "org.apache.stanbol.enhancer.engine.order" property provided by the EnhancementEngine:</p>
+<p>It is important to note that the ordering of the list has no influence on the ExecutionPlan because the order of execution of the configured <a href="../engines">EnhancementEngine</a>s is calculated only by using the value for the "org.apache.stanbol.enhancer.engine.order" property provided by the EnhancementEngine:</p>
<ul>
<li>Engines with a lower order are executed before Engines with a higher value</li>
<li>Engines with the same order may be executed simultaneously if the EnhancementJobMananger and the EnhancementEngine do support this feature.</li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/contentitem.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/contentitem.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/contentitem.html Thu Feb 16 10:29:23 2012
@@ -94,20 +94,19 @@
<p>The <code>getStream()</code> and <code>getMimeType()</code> methods are shortcuts for the according methods of the content item's blob object. Calling <code>contentItem.getBlob.getStream()</code> will return an InputStream over the exact same content as directly calling <code>getStream()</code> on the content item. Note that the blob interface also provides a <code>getParameter()</code> method that allows to retrieve mime type parameters such as the charset of textual content.</p>
<p>The content parsed by the user is stored as content part at the index '0' with the URI of the content item in the form of a blob. Therefore calling</p>
-<div class="codehilite"><pre>
+<div class="codehilite"><pre><span class="n">contentItem</span><span class="o">.</span><span class="na">getPart</span><span class="o">(</span><span class="mi">0</span><span class="o">,</span><span class="n">Blob</span><span class="o">.</span><span class="na">class</span><span class="o">)</span>
+<span class="n">contentItem</span><span class="o">.</span><span class="na">getPart</span><span class="o">(</span><span class="n">contentItem</span><span class="o">.</span><span class="na">getUri</span><span class="o">(),</span><span class="n">Blob</span><span class="o">.</span><span class="na">class</span><span class="o">)</span>
+<span class="n">contentItem</span><span class="o">.</span><span class="na">getBlob</span><span class="o">()</span>
</pre></div>
-<p>contentItem.getPart(0,Blob.class)
- contentItem.getPart(contentItem.getUri(),Blob.class)
- contentItem.getBlob()</p>
<p>returns the same blob instance.</p>
<h3 id="metadata_of_the_content_item">Metadata of the Content Item</h3>
<p>The metadata of the content item are managed by an lockable MGraph. This is basically a normal <code>java.util.Collections</code> for triples. The only RDF specific method is support for filtered iterators that support wildcards for subjects, predicates and objects.</p>
<p>This graph is used to store all enhancement results as well as metadata about the content item (such as content parts) and the enhancement process (see <a href="executionmetadata.html">execution metadata</a>.</p>
<h3 id="readwrite_locks">Read/Write locks</h3>
<p>During the Apache Stanbol enhancement process as executed by the <a href="enhancementjobmanager.html">enhancement job manager</a> components running in multiple threads need to access the state of the content item. Because of that the content item provides the possibility to acquire locks.</p>
-<div class="codehilite"><pre><span class="o">/**</span> <span class="n">Getter</span> <span class="k">for</span> <span class="n">the</span> <span class="n">ReadWirteLock</span> <span class="n">of</span> <span class="n">a</span> <span class="n">ContentItem</span> <span class="o">+/</span>
+<div class="codehilite"><pre><span class="cm">/** Getter for the ReadWirteLock of a ContentItem */</span>
<span class="o">+</span> <span class="n">getLock</span><span class="o">()</span> <span class="o">:</span> <span class="n">java</span><span class="o">.</span><span class="na">util</span><span class="o">.</span><span class="na">concurrent</span><span class="o">.</span><span class="na">ReadWriteLock</span>
</pre></div>
@@ -135,7 +134,7 @@
</pre></div>
-<p>While accessing content items within an <a href="engines/enhancementengine.html">enhancement engine</a> there is an exception to this rule. If an engine declares that is only supports the <code>SYNCHRONOUS</code> enhancement mode the <a href="enhancementjobmanager.html">enhancement job manager</a> needs to take care the an engine has exclusive access to the content item. In that case implementors of enhancement engines need not to care about using read/write locks.</p>
+<p>While accessing content items within an <a href="engines">enhancement engine</a> there is an exception to this rule. If an engine declares that is only supports the <code>SYNCHRONOUS</code> enhancement mode the <a href="enhancementjobmanager.html">enhancement job manager</a> needs to take care the an engine has exclusive access to the content item. In that case implementors of enhancement engines need not to care about using read/write locks.</p>
<h2 id="multipart_mime_serialization">Multipart MIME serialization</h2>
<p><span style="float:right"> <img alt="ConentItem Multipart MIME format" src="contentitemmultipartmime.png" title="This figure provides an overview on how ContentItems are serialize as MultiPart MIME" /></span></p>
<p>Stanbol supports the serialization of ContentItems as Multipart MIME. This serialization is used by the RESTful API of the Stanbol Enhancer. This section provides details about how ContentItems are represented using Multipart MIME. For more information on how to send/receive multipart content items via the RESTful Serivces provided by the Stanbol Enhancer please see the documentation provided in the Web Interface (e.g. http://localhost:8080/enhancer).</p>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.html Thu Feb 16 10:29:23 2012
@@ -57,7 +57,7 @@
<div id="content">
<h1 class="title">EnhancementEngineManager</h1>
- <p>The EnhancementEngineManager provides name based access to all active <a href="enhancementengine.html">EnhancementEngine</a>s and their ServiceReferences. This interface is typically used by components that need to lookup EnhancementEngiens based on their name. However the EngineTracker implementation can also be used to track specific EnhancementEngines.</p>
+ <p>The EnhancementEngineManager provides name based access to all active <a href="index.html">EnhancementEngine</a>s and their ServiceReferences. This interface is typically used by components that need to lookup EnhancementEngiens based on their name. However the EngineTracker implementation can also be used to track specific EnhancementEngines.</p>
<h3 id="enhancementenginemanager_interface">EnhancementEngineManager interface</h3>
<p>This is the Java API providing access to registered EnhancementEngines in the ways as described above. This interface includes the following methods:</p>
<div class="codehilite"><pre><span class="cm">/** Getter for all names with active engines */</span>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.html Thu Feb 16 10:29:23 2012
@@ -60,29 +60,29 @@
<p>This engine creates fise:EntityAnnotations based on the http://geonames.org dataset. It does not directly work on the parsed content, but processes named entities extracted by some NLP (natural language processing) engine. This engine creates EnityAnnotations for Features found for named entities in the geonames.org data set. In addition it adds EntityAnnotations for the continent, country and administrative regions for entities with an high confidence level.</p>
<h2 id="processed_annotations_input">Processed Annotations (Input)</h2>
<p>This engine consumes fise:TextAnnotations of type dbpedia:Place. More concrete it filters for enhancements that confirm to the following two requirements and consumes the text selected by the TextAnnotations:</p>
-<div class="codehilite"><pre><span class="p">?</span><span class="n">textAnnotation</span> <span class="n">rdf:type</span> <span class="n">fise:TextAnnotation</span> <span class="o">.</span>
-<span class="p">?</span><span class="n">textAnnotation</span> <span class="n">dc:type</span> <span class="n">dbpedia:Place</span>
-<span class="p">?</span><span class="n">textAnnotation</span> <span class="n">fise:selected</span><span class="o">-</span><span class="n">text</span> <span class="p">?</span><span class="n">text</span>
+<div class="codehilite"><pre>?textAnnotation rdf:type fise:TextAnnotation .
+?textAnnotation dc:type dbpedia:Place
+?textAnnotation fise:selected-text ?text
</pre></div>
<p>Here an example for such an TextAnnotations selecting the text "Vienna" form the content "The community Workshop will take place in Vienna".</p>
-<div class="codehilite"><pre><span class="err">urn:enhancement:text-enhancement:id1</span>
- <span class="err">a</span> <span class="err">fise:TextAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">dc:type</span>
- <span class="err">dbpedia:Place</span> <span class="err">;</span>
- <span class="err">fise:selected-text</span>
- <span class="err">"Vienna"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:selection-context</span>
- <span class="err">"The</span> <span class="err">community</span> <span class="err">Workshop</span> <span class="err">will</span> <span class="err">take</span> <span class="err">place</span> <span class="err">in</span> <span class="err">Vienna"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:start</span>
- <span class="err">"46"^^xsd:int</span> <span class="err">;</span>
- <span class="err">fise:end</span>
- <span class="err">"52"^^xsd:int</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"0.9773640902587215"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">.</span>
+<div class="codehilite"><pre>urn:enhancement:text-enhancement:id1
+ a fise:TextAnnotation , fise:Enhancement ;
+ dc:type
+ dbpedia:Place ;
+ fise:selected-text
+ "Vienna"^^xsd:string ;
+ fise:selection-context
+ "The community Workshop will take place in Vienna"^^xsd:string ;
+ fise:start
+ "46"^^xsd:int ;
+ fise:end
+ "52"^^xsd:int ;
+ fise:confidence
+ "0.9773640902587215"^^xsd:double ;
+ fise:extracted-from
+ urn:content-item:id1 .
</pre></div>
@@ -93,53 +93,53 @@
<p>Entity suggestions are EntityEnhancements that suggest Features of the geonames.org dataset for an processed TextAnnotation. This suggestions are currently only calculated based on the fise:selected-text of the TextAnnotation. </p>
<p>The following example shows three EntityAnnotations for the TextAnnotation used in the above example. See the fise:relation statements at the end of each of the two EntityAnnotations.</p>
<p>The first Entity found in the geonames.orf dataset is the capital city in Austria with an confidence level of 1.0:</p>
-<div class="codehilite"><pre><span class="err">urn:enhancement:entity-enhancement:id1</span>
- <span class="err">a</span> <span class="err">fise:EntityAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"1.0"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:entity-label</span>
- <span class="err">"Vienna"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:entity-reference</span>
- <span class="err">http:</span><span class="c1">//sws.geonames.org/2761369/ ;</span>
- <span class="err">fise:entity-type</span>
- <span class="err">geonames:Feature</span> <span class="err">,</span> <span class="err">dbpedia:Place</span> <span class="err">,</span> <span class="err">dbpedia:Settlement</span> <span class="err">,</span> <span class="err">dbpedia:PopulatedPlace</span> <span class="err">,</span> <span class="err">geonames:P.PPLC</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">;</span>
- <span class="err">dc:relation</span>
- <span class="err">urn:enhancement:text-enhancement:id1</span> <span class="err">.</span>
+<div class="codehilite"><pre>urn:enhancement:entity-enhancement:id1
+ a fise:EntityAnnotation , fise:Enhancement ;
+ fise:confidence
+ "1.0"^^xsd:double ;
+ fise:entity-label
+ "Vienna"^^xsd:string ;
+ fise:entity-reference
+ http://sws.geonames.org/2761369/ ;
+ fise:entity-type
+ geonames:Feature , dbpedia:Place , dbpedia:Settlement , dbpedia:PopulatedPlace , geonames:P.PPLC ;
+ fise:extracted-from
+ urn:content-item:id1 ;
+ dc:relation
+ urn:enhancement:text-enhancement:id1 .
</pre></div>
<p>With lower confidence levels there are a lot of other populated places with the name "Vienna" found in the geonames.org dataset.</p>
-<div class="codehilite"><pre><span class="err">urn:enhancement:entity-enhancement:id2</span>
- <span class="err">a</span> <span class="err">fise:EntityAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"0.42163702845573425"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:entity-label</span>
- <span class="err">"Vienna"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:entity-reference</span>
- <span class="err">http:</span><span class="c1">//sws.geonames.org/4496671/ ;</span>
- <span class="err">fise:entity-type</span>
- <span class="err">geonames:Feature</span> <span class="err">,</span> <span class="err">dbpedia:Place</span> <span class="err">,</span> <span class="err">dbpedia:Settlement</span> <span class="err">,</span> <span class="err">dbpedia:PopulatedPlace</span> <span class="err">,</span> <span class="err">geonames:P.PPL</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">;</span>
- <span class="err">dc:relation</span>
- <span class="err">urn:enhancement:text-enhancement:id1</span> <span class="err">.</span>
-
-<span class="err">urn:enhancement:entity-enhancement:id3</span>
- <span class="err">a</span> <span class="err">fise:EntityAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"0.42163702845573425"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:entity-label</span>
- <span class="err">"Vienna"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:entity-reference</span>
- <span class="err">http:</span><span class="c1">//sws.geonames.org/4825976/ ;</span>
- <span class="err">fise:entity-type</span>
- <span class="err">geonames:Feature</span> <span class="err">,</span> <span class="err">dbpedia:Place</span> <span class="err">,</span> <span class="err">dbpedia:Settlement</span> <span class="err">,</span> <span class="err">dbpedia:PopulatedPlace</span> <span class="err">,</span> <span class="err">geonames:P.PPL</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">;</span>
- <span class="err">dc:relation</span>
- <span class="err">urn:enhancement:text-enhancement:id1</span> <span class="err">.</span>
+<div class="codehilite"><pre>urn:enhancement:entity-enhancement:id2
+ a fise:EntityAnnotation , fise:Enhancement ;
+ fise:confidence
+ "0.42163702845573425"^^xsd:double ;
+ fise:entity-label
+ "Vienna"^^xsd:string ;
+ fise:entity-reference
+ http://sws.geonames.org/4496671/ ;
+ fise:entity-type
+ geonames:Feature , dbpedia:Place , dbpedia:Settlement , dbpedia:PopulatedPlace , geonames:P.PPL ;
+ fise:extracted-from
+ urn:content-item:id1 ;
+ dc:relation
+ urn:enhancement:text-enhancement:id1 .
+
+urn:enhancement:entity-enhancement:id3
+ a fise:EntityAnnotation , fise:Enhancement ;
+ fise:confidence
+ "0.42163702845573425"^^xsd:double ;
+ fise:entity-label
+ "Vienna"^^xsd:string ;
+ fise:entity-reference
+ http://sws.geonames.org/4825976/ ;
+ fise:entity-type
+ geonames:Feature , dbpedia:Place , dbpedia:Settlement , dbpedia:PopulatedPlace , geonames:P.PPL ;
+ fise:extracted-from
+ urn:content-item:id1 ;
+ dc:relation
+ urn:enhancement:text-enhancement:id1 .
</pre></div>
@@ -149,94 +149,94 @@
The following example shows the entity hierarchy enhancements for the suggested entity for Vienna (Autria). <em>Please note the dc:requires relation to this EntityAnnotation at the end of each of the following enhancement.</em></p>
<h3 id="continent_europe">Continent: Europe</h3>
<p>First the enhancement for the continent Europe:</p>
-<div class="codehilite"><pre><span class="err">urn:enhancement:entity-hierarchy-enhancement:id1</span>
- <span class="err">a</span> <span class="err">fise:EntityAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"0.42163702845573425"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:entity-label</span>
- <span class="err">"Europe"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:entity-reference</span>
- <span class="err">http:</span><span class="c1">//sws.geonames.org/6255148/ ;</span>
- <span class="err">fise:entity-type</span>
- <span class="err">geonames:Feature</span> <span class="err">,</span> <span class="err">dbpedia:Place,</span> <span class="err">geonames:L.CONT</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">;</span>
- <span class="err">dc:requires</span>
- <span class="err">urn:enhancement:entity-enhancement:id1</span> <span class="err">.</span>
+<div class="codehilite"><pre>urn:enhancement:entity-hierarchy-enhancement:id1
+ a fise:EntityAnnotation , fise:Enhancement ;
+ fise:confidence
+ "0.42163702845573425"^^xsd:double ;
+ fise:entity-label
+ "Europe"^^xsd:string ;
+ fise:entity-reference
+ http://sws.geonames.org/6255148/ ;
+ fise:entity-type
+ geonames:Feature , dbpedia:Place, geonames:L.CONT ;
+ fise:extracted-from
+ urn:content-item:id1 ;
+ dc:requires
+ urn:enhancement:entity-enhancement:id1 .
</pre></div>
<h3 id="country_austria">Country: Austria</h3>
<p>Next the enhancement for the country "Austria", classified as an independent political entry within geonames.org</p>
-<div class="codehilite"><pre><span class="err">urn:enhancement:entity-hierarchy-enhancement:id2</span>
- <span class="err">a</span> <span class="err">fise:EntityAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"0.42163702845573425"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:entity-label</span>
- <span class="err">"Austria"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:entity-reference</span>
- <span class="err">http:</span><span class="c1">//sws.geonames.org/2782113/ ;</span>
- <span class="err">fise:entity-type</span>
- <span class="err">geonames:Feature</span> <span class="err">,</span> <span class="err">dbpedia:Place,</span> <span class="err">dbpedia:</span> <span class="err">AdministrativeRegion,</span> <span class="err">geonames:A.PCLI</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">;</span>
- <span class="err">dc:requires</span>
- <span class="err">urn:enhancement:entity-enhancement:id1</span> <span class="err">.</span>
+<div class="codehilite"><pre>urn:enhancement:entity-hierarchy-enhancement:id2
+ a fise:EntityAnnotation , fise:Enhancement ;
+ fise:confidence
+ "0.42163702845573425"^^xsd:double ;
+ fise:entity-label
+ "Austria"^^xsd:string ;
+ fise:entity-reference
+ http://sws.geonames.org/2782113/ ;
+ fise:entity-type
+ geonames:Feature , dbpedia:Place, dbpedia: AdministrativeRegion, geonames:A.PCLI ;
+ fise:extracted-from
+ urn:content-item:id1 ;
+ dc:requires
+ urn:enhancement:entity-enhancement:id1 .
</pre></div>
<h3 id="aadm1_-_a_county">A.ADM1 - A county</h3>
<p>Now three enhancement describing the different hierarchies of administrative regions within Austria. First the "Bundesland", next the "Stadtteil" and last the "Gemeindebezirk".</p>
-<div class="codehilite"><pre><span class="err">urn:enhancement:entity-hierarchy-enhancement:id3</span>
- <span class="err">a</span> <span class="err">fise:EntityAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"0.42163702845573425"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:entity-label</span>
- <span class="err">"Vienna"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:entity-reference</span>
- <span class="err">http:</span><span class="c1">//sws.geonames.org/2761367/ ;</span>
- <span class="err">fise:entity-type</span>
- <span class="err">geonames:Feature</span> <span class="err">,</span> <span class="err">dbpedia:Place,</span> <span class="err">dbpedia:</span> <span class="err">AdministrativeRegion,</span> <span class="err">geonames:A.ADM1</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">;</span>
- <span class="err">dc:requires</span>
- <span class="err">urn:enhancement:entity-enhancement:id1</span> <span class="err">.</span>
+<div class="codehilite"><pre>urn:enhancement:entity-hierarchy-enhancement:id3
+ a fise:EntityAnnotation , fise:Enhancement ;
+ fise:confidence
+ "0.42163702845573425"^^xsd:double ;
+ fise:entity-label
+ "Vienna"^^xsd:string ;
+ fise:entity-reference
+ http://sws.geonames.org/2761367/ ;
+ fise:entity-type
+ geonames:Feature , dbpedia:Place, dbpedia: AdministrativeRegion, geonames:A.ADM1 ;
+ fise:extracted-from
+ urn:content-item:id1 ;
+ dc:requires
+ urn:enhancement:entity-enhancement:id1 .
</pre></div>
<h3 id="aadm2_-_a_city">A.ADM2 - A city</h3>
-<div class="codehilite"><pre><span class="err">urn:enhancement:entity-hierarchy-enhancement:id4</span>
- <span class="err">a</span> <span class="err">fise:EntityAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"0.42163702845573425"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:entity-label</span>
- <span class="err">"Politischer</span> <span class="err">Bezirk</span> <span class="err">Wien</span> <span class="err">(Stadt)"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:entity-reference</span>
- <span class="err">http:</span><span class="c1">//sws.geonames.org/2761333/ ;</span>
- <span class="err">fise:entity-type</span>
- <span class="err">geonames:Feature</span> <span class="err">,</span> <span class="err">dbpedia:Place,</span> <span class="err">dbpedia:</span> <span class="err">AdministrativeRegion,</span> <span class="err">geonames:A.ADM2</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">;</span>
- <span class="err">dc:requires</span>
- <span class="err">urn:enhancement:entity-enhancement:id1</span> <span class="err">.</span>
+<div class="codehilite"><pre>urn:enhancement:entity-hierarchy-enhancement:id4
+ a fise:EntityAnnotation , fise:Enhancement ;
+ fise:confidence
+ "0.42163702845573425"^^xsd:double ;
+ fise:entity-label
+ "Politischer Bezirk Wien (Stadt)"^^xsd:string ;
+ fise:entity-reference
+ http://sws.geonames.org/2761333/ ;
+ fise:entity-type
+ geonames:Feature , dbpedia:Place, dbpedia: AdministrativeRegion, geonames:A.ADM2 ;
+ fise:extracted-from
+ urn:content-item:id1 ;
+ dc:requires
+ urn:enhancement:entity-enhancement:id1 .
</pre></div>
<h3 id="aadm3_-_a_village">A.ADM3 - A village</h3>
-<div class="codehilite"><pre><span class="err">urn:enhancement:entity-hierarchy-enhancement:id5</span>
- <span class="err">a</span> <span class="err">fise:EntityAnnotation</span> <span class="err">,</span> <span class="err">fise:Enhancement</span> <span class="err">;</span>
- <span class="err">fise:confidence</span>
- <span class="err">"0.42163702845573425"^^xsd:double</span> <span class="err">;</span>
- <span class="err">fise:entity-label</span>
- <span class="err">"Gemeindebezirk</span> <span class="err">Innere</span> <span class="err">Stadt"^^xsd:string</span> <span class="err">;</span>
- <span class="err">fise:entity-reference</span>
- <span class="err">http:</span><span class="c1">//sws.geonames.org/2775259/ ;</span>
- <span class="err">fise:entity-type</span>
- <span class="err">geonames:Feature</span> <span class="err">,</span> <span class="err">dbpedia:Place,</span> <span class="err">dbpedia:</span> <span class="err">AdministrativeRegion,</span> <span class="err">geonames:A.ADM3</span> <span class="err">;</span>
- <span class="err">fise:extracted-from</span>
- <span class="err">urn:content-item:id1</span> <span class="err">;</span>
- <span class="err">dc:requires</span>
- <span class="err">urn:enhancement:entity-enhancement:id1</span> <span class="err">.</span>
+<div class="codehilite"><pre>urn:enhancement:entity-hierarchy-enhancement:id5
+ a fise:EntityAnnotation , fise:Enhancement ;
+ fise:confidence
+ "0.42163702845573425"^^xsd:double ;
+ fise:entity-label
+ "Gemeindebezirk Innere Stadt"^^xsd:string ;
+ fise:entity-reference
+ http://sws.geonames.org/2775259/ ;
+ fise:entity-type
+ geonames:Feature , dbpedia:Place, dbpedia: AdministrativeRegion, geonames:A.ADM3 ;
+ fise:extracted-from
+ urn:content-item:id1 ;
+ dc:requires
+ urn:enhancement:entity-enhancement:id1 .
</pre></div>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/index.html Thu Feb 16 10:29:23 2012
@@ -59,12 +59,12 @@
<h1 class="title">Enhancement Engines</h1>
<p>Enhancement engines are the components that are responsible to enhance <a href="../contentitem.html">content itmes</a>. They are called by the <a href="../enhancementjobmanager.html">Enhancement Job Manager</a>. Enhancement engines do have full access to the parsed content items. They are expected to modify their state.</p>
<p>The RESTful interface of an enhancement engine can be accessed by</p>
-<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}:{</span><span class="n">port</span><span class="p">}</span><span class="sr">/{stanbol-root}/</span><span class="n">enhancer</span><span class="sr">/engine/</span><span class="p">{</span><span class="n">engine</span><span class="o">-</span><span class="n">name</span><span class="p">}</span>
+<div class="codehilite"><pre>http://{host}:{port}/{stanbol-root}/enhancer/engine/{engine-name}
</pre></div>
<p>e.g. an enhancement engine with the name "ner" running at a Apache Stanbol instance on local host with the default configuration will be accessible at</p>
-<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/enhancer/</span><span class="n">engine</span><span class="o">/</span><span class="n">ner</span>
+<div class="codehilite"><pre>http://localhost:8080/enhancer/engine/ner
</pre></div>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.html Thu Feb 16 10:29:23 2012
@@ -70,7 +70,7 @@ The text to be checked must be provided
</li>
</ul>
<p>The result of language identification is added as TextAnnotation to the content item's metadata as string value of the property</p>
-<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">purl</span><span class="o">.</span><span class="n">org</span><span class="sr">/dc/</span><span class="n">terms</span><span class="o">/</span><span class="n">language</span>
+<div class="codehilite"><pre>http://purl.org/dc/terms/language
</pre></div>
@@ -111,7 +111,7 @@ The text to be checked must be provided
</ul>
<h2 id="usage">Usage</h2>
<p>Assuming that the Stanbol endpoint with the full launcher is running at</p>
-<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span>
+<div class="codehilite"><pre>http://localhost:8080
</pre></div>
@@ -131,7 +131,7 @@ curl -i -X PUT -H "Content-Type:text/pla
</ul>
<p>Alternatively, the Stanbol web interface can be used for submitting documents
and viewing the metadata at</p>
-<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="o">/</span><span class="n">contenthub</span>
+<div class="codehilite"><pre>http://localhost:8080/contenthub
</pre></div>
</div>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/list.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/list.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/list.html Thu Feb 16 10:29:23 2012
@@ -57,15 +57,12 @@
<div id="content">
<h1 class="title">Enhancement Engines and their main features</h1>
- <h2 id="preprocessing">Preprocessing</h2>
-<ul>
-<li><strong><a href="enhancer/engines/langidengine.html">Language Identification Engine</a></strong><ul>
-<li>language detection for textual content utilizing <a href="http://tika.apache.org/">Apache Tika</a></li>
-</ul>
-</li>
-<li>
-<p><strong><a href="enhancer/engines/metaxaengine.html">Metaxa Engine</a></strong></p>
+ <p>This provides an overview about all <a href="index.html">Enhancement Engine</a> implementations managed by the Apache Stanbol community.</p>
+<h2 id="preprocessing">Preprocessing</h2>
+<p><strong><a href="enhancer/engines/langidengine.html">Language Identification Engine</a></strong>
+ - language detection for textual content utilizing <a href="http://tika.apache.org/">Apache Tika</a></p>
<ul>
+<li><strong><a href="enhancer/engines/metaxaengine.html">Metaxa Engine</a></strong><ul>
<li>text extraction from various document formats</li>
<li>extraction of metadata from document formats
-</li>