Author: rwesten
Date: Thu Feb 16 10:29:17 2012
New Revision: 1244919
URL: http://svn.apache.org/viewvc?rev=1244919&view=rev
Log:
changed links to /engines/enhancementengine.html to /engines; changed :::none
to :::text; added style for java multi line comments to stanbol,css; some minor
formatting related changes
Modified:
incubator/stanbol/site/trunk/content/stanbol/css/stanbol.css
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/index.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/index.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/list.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementjobmanager.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.mdtext
Modified: incubator/stanbol/site/trunk/content/stanbol/css/stanbol.css
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/css/stanbol.css?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/css/stanbol.css (original)
+++ incubator/stanbol/site/trunk/content/stanbol/css/stanbol.css Thu Feb 16
10:29:17 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:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/defaultchain.mdtext
Thu Feb 16 10:29:17 2012
@@ -1,6 +1,6 @@
Title: DefaultChain
-Implementation that keeps track of all currently active
[EnhancementEngine](../engines/enhancementengine.html) and registers itself as
a Chain service with the "stanbol.enhancer.chain.name=default" an service
ranking of Integer.MIN_VALUE.
+Implementation that keeps track of all currently active
[EnhancementEngine](../engines) and registers itself as a Chain service with
the "stanbol.enhancer.chain.name=default" an service ranking of
Integer.MIN_VALUE.
This will cause this chain to be returned by the ChainManager.getDefault()
method if users:
@@ -22,7 +22,7 @@ The implementation is part of the "org.a
### Calculation of the ExecutionPlan
-This chain considers all currently active
[EnhancementEngine](../engines/enhancementengine.html)s. The ExecutionPlan is
calculated by using the value for the
"org.apache.stanbol.enhancer.engine.order" property provided by the
EnhancementEngine:
+This chain considers all currently active [EnhancementEngine](../engines)s.
The ExecutionPlan is calculated by using the value for the
"org.apache.stanbol.enhancer.engine.order" property provided by the
EnhancementEngine:
* Engines with a lower order are executed before Engines with a higher value
* Engines with the same order may be executed simultaneously if the
EnhancementJobMananger and the EnhancementEngine do support this feature.
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.mdtext
Thu Feb 16 10:29:17 2012
@@ -16,13 +16,13 @@ The RDFS schema used for the execution p
* __ep:inExecutionPlan__ (domain: ep:ExecutionNode; range:
ep:ExecutionPlan ;inverseOf: ep:hasExecutionNode): functional property that
links the execution node with an execution plan
* __ep:engine__ (domain: ep:ExecutionNode; range: xsd:string): The
property used to link to the Enhancement Engine by the name of the engine.
* __ep:dependsOn__ (domain: ep:ExecutionNode; range: ep:ExecutionNode)
Defines that the execution of this node depends on the completion of the
referenced one.
- * __ep:optional__ (domain: ep:ExecutionNode; range: xsd:boolean) Can be
used to specify that the execution of this
[EnhancementEngine](../engines/enhancementengine.html) 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).
+ * __ep:optional__ (domain: ep:ExecutionNode; range: xsd:boolean) Can be
used to specify that the execution of this [EnhancementEngine](../engines) 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).
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.
#### Example:
-This example shows an ExecutionPlan with three nodes for the "langId", "ner",
"dbpediaLinking" "geonamesLinking" and "zemanta" engine. Note that this names
refer to actual [EnhancementEngine](../engines/enhancementengine.html) Services
registered with the current OSGI Environment.
+This example shows an ExecutionPlan with three nodes for the "langId", "ner",
"dbpediaLinking" "geonamesLinking" and "zemanta" engine. Note that this names
refer to actual [EnhancementEngine](../engines) Services registered with the
current OSGI Environment.
This example assumes that
@@ -34,7 +34,7 @@ This example assumes that
The RDF graph of such a chain would look:
- :::none
+ :::text
urn:execPlan
rdf:type ep:ExecutionPlan
ep:hasExecutionNode urn:node1, urn:node2, urn:node3, urn:node4,
urn:node5
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/graphchain.mdtext
Thu Feb 16 10:29:17 2012
@@ -1,6 +1,6 @@
Title: GraphChain
-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
[EnhancementEngine](../engines/enhancementengine.html)s and the ExecutionPlan
model form the user.
+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 [EnhancementEngine](../engines)s and the
ExecutionPlan model form the user.
Typically it is a good practice to start with other - more simple to use -
Chain implementation such as the [Weighted Chain](weightedchain.html) 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.
@@ -12,12 +12,12 @@ The GraphChain supports two variants to
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:
- :::none
+ :::text
stanbol.enhancer.chain.graph.graphresource=myExecutionPlan.rdf
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
- :::none
+ :::text
stanbol.enhancer.chain.graph.graphresource=myExecutionPlan.something;format=application/rdf+xml
The GraphCain will track for that file and activate itself as soon as the file
gets available. Removing the file, waiting some seconds and providing the new
version afterwards should also work. Just replacing the file will not work,
because the DataFileProvider does not have supports for updates. In such cases
it might be needed to deactivate/activate the GraphChain.
@@ -30,12 +30,12 @@ _NOTE_: As soon as a graph resource is c
The Syntax is defined as follows:
- :::none
+ :::text
{engine-name};[optional];[dependsOn={engine-name1},{engine-name2}]
The following Example shows how this Syntax can be used to define an
ExecutionPlan.
- :::none
+ :::text
metaxa;optional
langId;dependsOn=metaxa
ner;dependsOn=langId
@@ -48,7 +48,7 @@ Not that the internal oder of the list d
Within an osgi configuration file
(org.apache.stanbol.enhancer.chain.graph.impl.GraphChain-myGraphChain.config)
this would look like
- :::none
+ :::text
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"]
A better visual expression provides this screenshot of the Apache Feilx
Webconsole showing the dialog for the same configuration
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/index.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/index.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/index.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/index.mdtext
Thu Feb 16 10:29:17 2012
@@ -1,15 +1,15 @@
Title: Enhancement Chains
-An Enhancement Chain defines how Content parsed to the Stanbol Enhancer is
processed. More concrete it defines what
[EnhancementEngine](../engines/enhancementengine.html)s and in what order are
used to process [ContentItem](../contentitem.html)s. Chains are not responsible
for the actual processing of ContentItems. They provide the
[ExecutionPlan](executionplan.html) to the
[EnhancementJobManger](../enhancementjobmanager.html) that does the actual
processing of the ContentItem.
+An Enhancement Chain defines how Content parsed to the Stanbol Enhancer is
processed. More concrete it defines what [EnhancementEngine](../engines)s and
in what order are used to process [ContentItem](../contentitem.html)s. Chains
are not responsible for the actual processing of ContentItems. They provide the
[ExecutionPlan](executionplan.html) to the
[EnhancementJobManger](../enhancementjobmanager.html) that does the actual
processing of the ContentItem.
In the RESTful API enhancement chains can be accessed by there name under
- :::none
+ :::text
http://{host}:{port}/{stanbol-path}/enhancer/chain/{chain-name}
Enhancement requestes issued to
- :::none
+ :::text
http://{host}:{port}/{stanbol-path}/enhancer
http://{host}:{port}/{stanbol-path}/engines
@@ -60,7 +60,7 @@ Each Chain has an name assigned. This is
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.
-The getEngines method returns the name of all
[EnhancementEngine](../engines/enhancementengine.html)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.
+The getEngines method returns the name of all [EnhancementEngine](../engines)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.
Components that need to know the details about a Chain need to process the
[ExecutionPlan](executionplan.html) returned by the getExectuonPlan() method.
The [ExecutionPlan](executionplan.html) 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 [ExecutionPlan](executionplan.html).
@@ -95,7 +95,7 @@ The default Chain is determined by the f
If no chain is active a ChainException with an according message MUST BE
thrown.
-All Stanbol launchers are configured with the [Default
Chain](defaultchain.html) 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
[EnhancementEngine](../engines/enhancementengine.html)s and sorts them based on
there ordering information (see the [Calculation of the Execution Plan based on
the EnhancementEngine
Ordering](weightedchain.html#calculation_of_the_executionplan) for details).
+All Stanbol launchers are configured with the [Default
Chain](defaultchain.html) 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
[EnhancementEngine](../engines)s and sorts them based on there ordering
information (see the [Calculation of the Execution Plan based on the
EnhancementEngine
Ordering](weightedchain.html#calculation_of_the_executionplan) for details).
### ChainManager interface
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/listchain.mdtext
Thu Feb 16 10:29:17 2012
@@ -1,6 +1,6 @@
Title: ListChain
-The List Chain creates the ExecutionPlan based on the exact order of the
configured [EnhancementEngine](../engines/enhancementengine.html)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
[GraphChain](graphchain.html).
+The List Chain creates the ExecutionPlan based on the exact order of the
configured [EnhancementEngine](../engines)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 [GraphChain](graphchain.html).
A typical usage scenario would be that users start of with configuring a
ListChain and later optimize the execution by migrating functional
configuration to [GraphChain](graphchain.html)s.
@@ -12,7 +12,7 @@ In addition it is possible to define Eng
The syntax to define an Engine as optional is as follows
- :::none
+ :::text
<name>;optional
<name>;optional=true
@@ -26,10 +26,10 @@ It is also possible to configure a ListC
To create the same configuration as in the above screenshot the file would
need to look like this:
- :::none
+ :::text
stanbol.enhancer.chain.name="list"
stanbol.enhancer.chain.list.enginelist=["metaxa;optional","langid","ner","dbpediaLinking"]
### Calculation of the ExecutionPlan
-The ExecutionPlan is created based on the exact order of the
[EnhancementEngine](../engines/enhancementengine.html)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.
+The ExecutionPlan is created based on the exact order of the
[EnhancementEngine](../engines)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.
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/weightedchain.mdtext
Thu Feb 16 10:29:17 2012
@@ -1,6 +1,6 @@
Title: WeightedChain
-The Wighted Chain takes a list of
[EnhancementEngine](../engines/enhancementengine.html) names as input and uses
the "org.apache.stanbol.enhancer.engine.order" metadata of the configured
Engines to calculate the ExecutionPlan.
+The Wighted Chain takes a list of [EnhancementEngine](../engines) names as
input and uses the "org.apache.stanbol.enhancer.engine.order" metadata of the
configured Engines to calculate the ExecutionPlan.
This Chain is designed for easy configuration - just a list of the engine
names - but has limited possibilities to control the execution order.
@@ -12,7 +12,7 @@ In addition it is possible to define Eng
The syntax to define an Engine as optional is as follows
- :::none
+ :::text
<name>;optional
<name>;optional=true
@@ -22,7 +22,7 @@ both variants result that the execution
### Calculation of the ExecutionPlan
-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
[EnhancementEngine](../engines/enhancementengine.html)s is calculated only by
using the value for the "org.apache.stanbol.enhancer.engine.order" property
provided by the EnhancementEngine:
+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
[EnhancementEngine](../engines)s is calculated only by using the value for the
"org.apache.stanbol.enhancer.engine.order" property provided by the
EnhancementEngine:
* Engines with a lower order are executed before Engines with a higher value
* Engines with the same order may be executed simultaneously if the
EnhancementJobMananger and the EnhancementEngine do support this feature.
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
Thu Feb 16 10:29:17 2012
@@ -47,9 +47,9 @@ The <code>getStream()</code> and <code>g
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
:::java
- contentItem.getPart(0,Blob.class)
- contentItem.getPart(contentItem.getUri(),Blob.class)
- contentItem.getBlob()
+ contentItem.getPart(0,Blob.class)
+ contentItem.getPart(contentItem.getUri(),Blob.class)
+ contentItem.getBlob()
returns the same blob instance.
@@ -64,7 +64,7 @@ This graph is used to store all enhancem
During the Apache Stanbol enhancement process as executed by the [enhancement
job manager](enhancementjobmanager.html) 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.
:::java
- /** Getter for the ReadWirteLock of a ContentItem +/
+ /** Getter for the ReadWirteLock of a ContentItem */
+ getLock() : java.util.concurrent.ReadWriteLock
Note also that
@@ -92,7 +92,7 @@ However, whenever components need to ens
contentItem.getLock().readLock().unlock()
}
-While accessing content items within an [enhancement
engine](engines/enhancementengine.html) there is an exception to this rule. If
an engine declares that is only supports the <code>SYNCHRONOUS</code>
enhancement mode the [enhancement job manager](enhancementjobmanager.html)
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.
+While accessing content items within an [enhancement engine](engines) there is
an exception to this rule. If an engine declares that is only supports the
<code>SYNCHRONOUS</code> enhancement mode the [enhancement job
manager](enhancementjobmanager.html) 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.
## Multipart MIME serialization
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/enhancementenginemanager.mdtext
Thu Feb 16 10:29:17 2012
@@ -1,6 +1,6 @@
Title: EnhancementEngineManager
-The EnhancementEngineManager provides name based access to all active
[EnhancementEngine](enhancementengine.html)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.
+The EnhancementEngineManager provides name based access to all active
[EnhancementEngine](index.html)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.
### EnhancementEngineManager interface
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/geonamesengine.mdtext
Thu Feb 16 10:29:17 2012
@@ -6,14 +6,14 @@ This engine creates fise:EntityAnnotatio
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:
- :::none
+ :::text
?textAnnotation rdf:type fise:TextAnnotation .
?textAnnotation dc:type dbpedia:Place
?textAnnotation fise:selected-text ?text
Here an example for such an TextAnnotations selecting the text "Vienna" form
the content "The community Workshop will take place in Vienna".
- :::none
+ :::text
urn:enhancement:text-enhancement:id1
a fise:TextAnnotation , fise:Enhancement ;
dc:type
@@ -47,7 +47,7 @@ The following example shows three Entity
The first Entity found in the geonames.orf dataset is the capital city in
Austria with an confidence level of 1.0:
- :::none
+ :::text
urn:enhancement:entity-enhancement:id1
a fise:EntityAnnotation , fise:Enhancement ;
fise:confidence
@@ -65,7 +65,7 @@ The first Entity found in the geonames.o
With lower confidence levels there are a lot of other populated places with
the name "Vienna" found in the geonames.org dataset.
- :::none
+ :::text
urn:enhancement:entity-enhancement:id2
a fise:EntityAnnotation , fise:Enhancement ;
fise:confidence
@@ -108,7 +108,7 @@ The following example shows the entity h
First the enhancement for the continent Europe:
- :::none
+ :::text
urn:enhancement:entity-hierarchy-enhancement:id1
a fise:EntityAnnotation , fise:Enhancement ;
fise:confidence
@@ -127,7 +127,7 @@ First the enhancement for the continent
###Country: Austria
Next the enhancement for the country "Austria", classified as an independent
political entry within geonames.org
- :::none
+ :::text
urn:enhancement:entity-hierarchy-enhancement:id2
a fise:EntityAnnotation , fise:Enhancement ;
fise:confidence
@@ -147,7 +147,7 @@ Next the enhancement for the country "Au
Now three enhancement describing the different hierarchies of administrative
regions within Austria. First the "Bundesland", next the "Stadtteil" and last
the "Gemeindebezirk".
- :::none
+ :::text
urn:enhancement:entity-hierarchy-enhancement:id3
a fise:EntityAnnotation , fise:Enhancement ;
fise:confidence
@@ -164,7 +164,7 @@ Now three enhancement describing the dif
urn:enhancement:entity-enhancement:id1 .
### A.ADM2 - A city
- :::none
+ :::text
urn:enhancement:entity-hierarchy-enhancement:id4
a fise:EntityAnnotation , fise:Enhancement ;
fise:confidence
@@ -182,7 +182,7 @@ Now three enhancement describing the dif
### A.ADM3 - A village
- :::none
+ :::text
urn:enhancement:entity-hierarchy-enhancement:id5
a fise:EntityAnnotation , fise:Enhancement ;
fise:confidence
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/index.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/index.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/index.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/index.mdtext
Thu Feb 16 10:29:17 2012
@@ -4,12 +4,12 @@ Enhancement engines are the components t
The RESTful interface of an enhancement engine can be accessed by
- :::none
+ :::text
http://{host}:{port}/{stanbol-root}/enhancer/engine/{engine-name}
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
- :::none
+ :::text
http://localhost:8080/enhancer/engine/ner
When using the Java API enhancement engines can be liked up as OSGI services.
The [Enhancement Engine Manager](enhancementenginemanager.html) service is
designed to ease this by providing a API that allows to access enhancement
engine by their name.
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext
Thu Feb 16 10:29:17 2012
@@ -15,7 +15,7 @@ The text to be checked must be provided
The result of language identification is added as TextAnnotation to the
content item's metadata as string value of the property
- :::none
+ :::text
http://purl.org/dc/terms/language
This RDF snippet illustrates the output:
@@ -59,7 +59,7 @@ Additional language models can be create
Assuming that the Stanbol endpoint with the full launcher is running at
- :::none
+ :::text
http://localhost:8080
and the engine is activated, from the command line commands like this
@@ -78,5 +78,5 @@ can be used for submitting some text fil
Alternatively, the Stanbol web interface can be used for submitting documents
and viewing the metadata at
- :::none
+ :::text
http://localhost:8080/contenthub
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/list.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/list.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/list.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/list.mdtext
Thu Feb 16 10:29:17 2012
@@ -1,8 +1,10 @@
Title: Enhancement Engines and their main features
+This provides an overview about all [Enhancement Engine](index.html)
implementations managed by the Apache Stanbol community.
+
## Preprocessing
-- __[Language Identification Engine](enhancer/engines/langidengine.html)__
+ __[Language Identification Engine](enhancer/engines/langidengine.html)__
- language detection for textual content utilizing [Apache
Tika](http://tika.apache.org/)
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.mdtext
Thu Feb 16 10:29:17 2012
@@ -14,7 +14,7 @@ The general structure of the Metaxa anno
#### The top-level <tt>TextAnnotation</tt> instance
- :::none
+ :::text
<urn:enhancement-03c9e85e-2681-21b7-a5af-6da62d67ef6b>
a <http://fise.iks-project.eu/ontology/TextAnnotation> ,
<http://fise.iks-project.eu/ontology/Enhancement> ;
@@ -30,7 +30,7 @@ The general structure of the Metaxa anno
#### The top-level document metadata, referenced from the
<tt>TextAnnotation</tt> instance via the *extracted-from* property:
- :::none
+ :::text
<http://localhost:8080/store/content/mf_example.htm>
a
<http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#HtmlDocument> ;
<http://www.semanticdesktop.org/ontologies/2007/01/19/nie#contains>
@@ -47,7 +47,7 @@ NOTE: The extracted plain text is no lon
#### Embedded <tt>hCard</tt> microformat data referenced via the
<tt>nie:contains</tt> property:
- :::none
+ :::text
<urn:rnd:-9e25553:12b3843df43:-7ffe>
a <http://www.w3.org/2006/vcard/ns#VCard> ;
<http://www.w3.org/2006/vcard/ns#adr>
@@ -158,24 +158,24 @@ Metaxa uses a set of vocabularies ("onto
These ontologies belong to the underlying Aperture subsystem, contained in the
package
- :::none
+ :::text
org.semanticdesktop.aperture.vocabulary
The most important ones with respect to top-level document properties are
* NIE (Nepomuk Information Element):
- :::none
+ :::text
http://www.semanticdesktop.org/ontologies/2007/01/19/nie#
* NFO (Nepomuk File Object):
- :::none
+ :::text
http://www.semanticdesktop.org/ontologies/2007/01/19/nfo#
Documentation of Aperture's core ontologies is provided in Aperture's Javadoc
[http://aperture.sourceforge.net/doc/javadoc/1.5.0/index.html](http://aperture.sourceforge.net/doc/javadoc/1.5.0/index.html)
for the packages in
- :::none
+ :::text
org.semanticdesktop.aperture.vocabulary.
#### HTML Microformat Extractors
@@ -266,7 +266,7 @@ The following table describes which voca
By default, Metaxa uses the extractors specified in the resource
"extractionregistry.xml", and for HTML pages, the resource "htmlregistry.xml".
Alternative configurations and extractors can be attached to Metaxa as
fragment bundles, specifying as host bundle
- :::none
+ :::text
Fragment-Host: org.apache.stanbol.enhancer.engines.metaxa
The alternative configuration files then can be set as values of the properties
@@ -279,24 +279,24 @@ The alternative configuration files then
Assuming that the Stanbol endpoint with the full launcher is running at
- :::none
+ :::text
http://localhost:8080
and the engine is activated, from the command line commands like this can be
used for submitting some file as content item, where the mime type must match
the document type:
* stateless interface
- :::none
+ :::text
curl -i -X POST -H "Content-Type:text/html" -T testpage.html
http://localhost:8080/engines
* stateful interface
- :::none
+ :::text
curl -i -X PUT -H "Content-Type:text/html" -T testpage.html
http://localhost:8080/contenthub/content/someFileId
Alternatively, the Stanbol web interface can be used for submitting documents
and viewing the metadata at
- :::none
+ :::text
http://localhost:8080/contenthub
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext
Thu Feb 16 10:29:17 2012
@@ -9,7 +9,7 @@ This engine is based on the NLP features
This engine adds **TextAnnotation-Enhancements** for the text "John Smith
lives in London", (amongst other) the following information to the enhancement
graph, suggesting London (of type: Place) for the string London:
- :::none
+ :::text
{
"@subject": "<urn:enhancement-e6a08398-a49f-5bf6-c09f-6da5db63507e>",
"@type": [
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.mdtext
Thu Feb 16 10:29:17 2012
@@ -19,7 +19,7 @@ The configuration decides, which dataset
For the sentence "John Smith lives in London", you will get several
EntityAnnotations for the terms "London", "John Smith" form your linking target
resource (in this case DBpedia) together with a confidence value, which can be
used to sort the suggestions.
- :::none
+ :::text
{
"@subject": "<urn:enhancement-2ec0662c-3a10-f8f5-43b4-cf7403e4c39d>",
"@type": [
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext
Thu Feb 16 10:29:17 2012
@@ -13,7 +13,7 @@ The engine natively supports the mime ty
*text/html*. Additionally, text can be processed that is provided in the
content
item's metadata as value of the property
- :::none
+ :::text
http://www.semanticdesktop.org/ontologies/2007/01/19/nie#plainTextContent
Supported languages are
@@ -30,7 +30,7 @@ obtained from [http://www.opencalais.com
In the OSGi configuration the key is set as value of the property
- :::none
+ :::text
org.apache.stanbol.enhancer.engines.opencalais.license
@@ -47,7 +47,7 @@ The following configuration properties a
* <tt>org.apache.stanbol.enhancer.engines.opencalais.url</tt>: The URL of the
OpenCalais RESTful service. That needs only be changed when OpenCalais should
change its web service address.
* <tt>org.apache.stanbol.enhancer.engines.opencalais.typeMap</tt>: The value
is the name of a file for mapping the NER types from OpenCalais to other types.
By default, a mapping to the DBPedia types is provided in order to achieve
compatibility with the Stanbol OpenLNLP-NER engine. If no mapping is desired
one might pass an empty mapping file. Types for which no mapping is defined are
passed as is to the metadata. The syntax of the mapping table is similar to
that of Java property files. Each entry takes the form
- :::none
+ :::text
CalaisTypeURI=TargetTypeURI
* <tt>org.apache.stanbol.enhancer.engines.opencalais.NERonly</tt>: A Boolean
property to specify whether in addition to the NER enhancements also the
OpenCalais Linked Data references are included as entity references. By
default, these are omitted.
@@ -56,7 +56,7 @@ The following configuration properties a
Assuming that the Stanbol endpoint with the full launcher is running at
- :::none
+ :::text
http://localhost:8080
the license key has been defined and the engine is activated, from the
@@ -75,6 +75,6 @@ command line commands like this can be u
Alternatively, the Stanbol web interface can be used for submitting documents
and viewing the metadata at
- :::none
+ :::text
http://localhost:8080/contenthub
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementjobmanager.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementjobmanager.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementjobmanager.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementjobmanager.mdtext
Thu Feb 16 10:29:17 2012
@@ -14,7 +14,7 @@ The interface of the EnhancementJobManag
/** Enhances the content item by using the parsed Chain */
+ enhanceContent(ContentItem ci, Chain chain)
-Note that the parsed ContentItem will be changed during the enhancement
process. [EnhancementEngine](engines/enhancementengine.html)s will add
extracted knowledge to the metadata of the content item. Also additional
content parts may be added to the content item.
+Note that the parsed ContentItem will be changed during the enhancement
process. [EnhancementEngine](engines)s will add extracted knowledge to the
metadata of the content item. Also additional content parts may be added to the
content item.
## Enhancement Process
@@ -40,7 +40,7 @@ For details on how to initialize/load th
### Engine Execution
-The ExecutionPlan provides the necessary information what
[EnhancementEngine](engines/enhancementengine.html)s can be executed at any
given state. The following code shows how to determine executable engines.
+The ExecutionPlan provides the necessary information what
[EnhancementEngine](engines)s can be executed at any given state. The following
code shows how to determine executable engines.
This code snippet assumes to be called after the execution of an
EnhancementEngine has completed. Note that in a multi threaded environment
access to the list of executed and running engines need to be synchronized.
:::java
@@ -62,7 +62,7 @@ This code snippet assumes to be called a
_NOTE_ that the NonLiterals contained in the two collections are
'ep:ExecutionNode' instances and NOT 'em:EngineExecution' instances. Each
'em:EngineExecution' instance in the the ExecutionMetadata' is linked by the
'em:executionNode' property to the corresponding 'ep:ExecutionNode' of the
ExecutionPlan.
-Before executing an [EnhancementEngine](engines/enhancementengine.html) the
EnhancementJobManager needs to check if and how the engine can enhance a
content item. This is indicated by the integer returned by the
"canEnhance(ContentItem ci)" method:
+Before executing an [EnhancementEngine](engines) the EnhancementJobManager
needs to check if and how the engine can enhance a content item. This is
indicated by the integer returned by the "canEnhance(ContentItem ci)" method:
* __CANNOT_ENHANCE__: Indicates that this engines can not process the parsed
content item. In this case the EnhancementJobManager needs to skip this engine
and mark the EngineExectuion as skipped with a status message that the
EnhancementEngine was unable to process the content item. If this engine is
marked as optional the enhancement process can continue if not, than the
execution MUST be marked as failed and an according Exception needs to be
thrown.
* __ENHANCE_SYNCHRONOUS__: Indicates that the engines needs exclusive access
to the parsed content item. The EnhancementJobManager needs to ensure that in
some way. Typically by calling the "computeEnhancement(ContentItem ci)" method
within an write lock.
@@ -76,7 +76,7 @@ For all the details on how to reflect st
### Multi Threaded enhancement processes
-In case the EnhancementJobManager supports to simultaneously call
[EnhancementEngine](engines/enhancementengine.html)s for the same content item
in multiple threads it is important to correctly use the ReadWriteLock as
provided by the ContentItem.getLock() method.
+In case the EnhancementJobManager supports to simultaneously call
[EnhancementEngine](engines)s for the same content item in multiple threads it
is important to correctly use the ReadWriteLock as provided by the
ContentItem.getLock() method.
There are manny good examples on how to correctly use
"java.util.concurrent.ReadWriteLock" available on the web.
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.mdtext
Thu Feb 16 10:29:17 2012
@@ -51,7 +51,7 @@ This example describes the following sit
The RDF graph with the Execution Metadata:
- :::none
+ :::text
urn:exec
rdf:type em:ChainExecution
em:executionPlan urn:execPlan
@@ -91,7 +91,7 @@ The RDF graph with the Execution Metadat
The Execution Plan: (copy from the example provided in the ExecutionPlan
section)
- :::none
+ :::text
urn:execPlan
rdf:type ep:ExecutionPlan
ep:hasExecutionNode urn:node1, urn:node2, urn:node3, urn:node4,
urn:node5
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext
Thu Feb 16 10:29:17 2012
@@ -118,7 +118,7 @@ The entity annotation type refers to nam
The Apache Stanbol enhancer is able to serialize the response in the following
RDF formats:
- :::none
+ :::text
application/json (JSON-LD)
application/rdf+xml (RDF/XML)
application/rdf+json (RDF/JSON)
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.mdtext?rev=1244919&r1=1244918&r2=1244919&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.mdtext
Thu Feb 16 10:29:17 2012
@@ -62,7 +62,7 @@ A special NOTE to the usage of <{code
The ContentItem <ci> represents a content parsed to the Stanbol Enhancer.
It is the central resource used to link all the enhancements created by the
EnhancementEngines.
- :::none
+ :::text
<ci> rdf:type sb:ContentItem
[<ci> sb:embeds-knowledge {knowlegeGraphId}]
[<ci> sb:has-section sb:ContentItem]
@@ -112,7 +112,7 @@ The concept "Enhancement" defines proper
The following code segments shows the knowledge typically described by using
the Enhancement concept
- :::none
+ :::text
<e> rdf:type sb:Enhancement
<e> dc:creator enhancementEngine^^xsd:anyURI
<e> dc:contributor enhancementEngine^^xsd:anyURI
@@ -150,7 +150,7 @@ Sections below are not yet updated
The concept "Annotation" provides metadata about the extracted feature. This
information are important both for the enhancement process and the users of the
Stanbol Enhancer.
The following code segment shows the knowledge typically provided by an
Annotation <a>. A description of the properties is provided below:
- :::none
+ :::text
<a> rdf:type sb:Annotation
[<a> rdf:type sb:Enhancement, sb:Occurrence]
<a> sb:extracted-from <ci>
@@ -240,7 +240,7 @@ As example lets assume that the followin
Both for Rupert Westenthaler and Olivier Grisel an EntityAnnotation would be
present - in that case created by the RDFa extractor, but in principle this
could also work if the RDFa markup is missing. In such cases the
EntityAnnotations could be created by an NLPEnhancementEngine.
- :::none
+ :::text
<a1> rdf:type sb:EntityAnnotation
<a1> dc:title Rupert Westenthaler
<a1> sb:entity-type foaf:Person
@@ -255,7 +255,7 @@ Both for Rupert Westenthaler and Olivier
Lets ignore the occurrences - because how to create Occurrences for RDFa
markup is a whole different story that needs to be specified - and concentrate
on the suggestions.
- :::none
+ :::text
<s1> rdf:type sb:Suggestion
<s1> sb:entity <http://www.example.com/person/Rupert_Westenthaler>
<s1> sb:entity-type foaf:Person, vCard:vCard, dbpedia-ont:Person
@@ -277,7 +277,7 @@ If the suggestion is accepted by the cli
Now lets have a detailed look at the suggestions to add Rupert and Olivier as
a "cal:attendee" to the meeting.
First we need to create an EntityAnnotation for the Meeting that would be
created by the RDFa extractor
- :::none
+ :::text
<a> rdf:type sb:EntityAnnotation
<a> dc:title "Stanbol Teleconference"
<a> sb:entity-type cal:Vevent
@@ -291,7 +291,7 @@ It is important to suggest here the anno
The following suggestions also use the sb:field property to tell the user that
the suggestions is about values for the "cal:attendee" property.
- :::none
+ :::text
<s3> rdf:type sb:Suggestion
<s3> sb:field cal:attendee
<s3> sb:entity <a1>
@@ -347,7 +347,7 @@ Different Occurrence descriptions are ne
Describe the occurrence of a feature within an textual content.
- :::none
+ :::text
<o> rdf:type sb:TextOccurrence
sb:TextOccurrence rdfs:subClassOf sb:Occurrence
<o> rdf:type sb:Occurrence
@@ -367,7 +367,7 @@ Describe the occurrence of a feature wit
Describes the occurrence of an feature within the metadata of the parsed
content. This are extremely useful to link entities for literal values provided
by metadata standards such as creator information for Dublin Core, Artist,
Album, Label ... information provided by ID3 or Camera Model information as
present in EXIF metadata. Also geo-point to City, Region, Country enhancements
could be done by using this type of occurrences.
- :::none
+ :::text
<o> rdf:type sb:MetadataOccurrence
sb:MetadataOccurrence rdfs:subClassOf sb:Occurrence
<o> rdf:type sb:Occurrence
@@ -399,7 +399,7 @@ An User types the text "Next week I will
Lets assume that Paris was detected to describe a location and travel to be a
keyword. There are also two known Entities with the name "Paris" and the type
Location.
This would result in an enhancement graph as follows
- :::none
+ :::text
# The content item
<ci> rdf:type sb:ContentItem
@@ -473,7 +473,7 @@ When consuming the following queries wou
Getting all Tags: to get all Keywords/Categories replace sb:Tag with
sb:Keyword/sb:Category
- :::none
+ :::text
PREFIX dc: <http://purl.org/dc/terms/>
PREFIX sb: <http://stanbol.apache.org/ontology/1.0/>
SELECT ?id, ?title, ?type
@@ -485,7 +485,7 @@ Getting all Tags: to get all Keywords/Ca
Getting suggestions for an known Annotation (e.g. urn:annotation1)
- :::none
+ :::text
PREFIX dc: <http://purl.org/dc/terms/>
PREFIX sb: <http://stanbol.apache.org/ontology/1.0/>
SELECT ?entity, ?title, ?type ?score
@@ -499,7 +499,7 @@ Getting suggestions for an known Annotat
Getting all selected Entities within the Text
- :::none
+ :::text
PREFIX dc: <http://purl.org/dc/terms/>
PREFIX sb: <http://stanbol.apache.org/ontology/1.0/>
SELECT ?id, ?title, ?start, ?end, ?type
@@ -513,7 +513,7 @@ Getting all selected Entities within the
Getting all Locations and optionally the occurrences within the text
- :::none
+ :::text
PREFIX dc: <http://purl.org/dc/terms/>
PREFIX sb: <http://stanbol.apache.org/ontology/1.0/>
PREFIX dbpedia-ont: <http://dbpedia.org/ontology/>
@@ -540,7 +540,7 @@ Lets assume that a user parses a content
Further assume that both Richard and Rachel works for the company running the
Stanbol Enhancer and there is an EnhancementEngine that knows about Company
resource.
This example uses the URI "http://www.company.org/team/Richard_Cypher"; and
"http://www.company.org/team/Rachel_Brandstone"; to identify the two example
employees.
- :::none
+ :::text
#The content item
<ci> rdf:type sb:ContentItem
<ci> dc:creator "Richard Cypher", "Rachel Brandstone"
@@ -594,7 +594,7 @@ This example uses the URI "http://www.co
*NOTE*: One could also create two sb:Annotations for both Richard and Rachel,
one Annotation describing the annotated value and a second suggesting the
entity for the first, but that seams like an unnecessary complexity as long as
there is only one person with this name in the company. Nonetheless this
decision needs to be reviewed.
Therefore the code for Richard when using this variant.
- :::none
+ :::text
#Annotation describing "Richard Cypher" as extracted from the DC
description
<a1> rdf:type sb:Enhancement
<a1> rdf:type sb:Annotation
@@ -636,7 +636,7 @@ Getting all Annotations for the dc:creat
Version based on variant 1:
- :::none
+ :::text
PREFIX dc: <http://purl.org/dc/terms/>
PREFIX sb: <http://stanbol.apache.org/ontology/1.0/>
SELECT ?id, ?title, ?creatorId
@@ -648,7 +648,7 @@ Version based on variant 1:
Version for variant 2:
- :::none
+ :::text
PREFIX dc: <http://purl.org/dc/terms/>
PREFIX sb: <http://stanbol.apache.org/ontology/1.0/>
SELECT ?id, ?title, ?creatorId
@@ -665,7 +665,7 @@ Getting all Annotations created for DC p
Version based on variant 1:
- :::none
+ :::text
PREFIX dc: <http://purl.org/dc/terms/>
PREFIX sb: <http://stanbol.apache.org/ontology/1.0/>
SELECT ?id, ?title, ?field, ?entity
@@ -678,7 +678,7 @@ Version based on variant 1:
Version based on variant 2:
- :::none
+ :::text
PREFIX dc: <http://purl.org/dc/terms/>
PREFIX sb: <http://stanbol.apache.org/ontology/1.0/>
SELECT ?id, ?title, ?field, ?entity
