Author: fchrist
Date: Fri Feb 10 16:57:56 2012
New Revision: 1242853
URL: http://svn.apache.org/viewvc?rev=1242853&view=rev
Log:
STANBOL-450 Refactoring - moved entityhub docs into subfolder
Added:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/entityhub/index.mdtext
- copied unchanged from r1242750,
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/entityhub.mdtext
Removed:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/entityhub.mdtext
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/index.mdtext
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext?rev=1242853&r1=1242852&r2=1242853&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext
(original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext
Fri Feb 10 16:57:56 2012
@@ -25,7 +25,7 @@ We will shortly describe the components
* The [CMS Adapter](cmsadapter/) CMS Adapter component acts as a bridge
between JCR/CMIS compliant content management systems and the Apache Stanbol.
It can be used to map existing node structures from JCR/CMIS content
repositories to RDF models or vica versa. It also provides services for the
management of content repository items as [Content
Item](enhancer/contentitem.html)s within Contenthub.
-* The [Entityhub](entityhub.html) is the component, which lets you cache and
manage local indexes of repositories such as dbpedia but also custom data (e.g.
product descriptions, contact data, specialized topic thesauri).
+* The [Entityhub](entityhub/) is the component, which lets you cache and
manage local indexes of repositories such as dbpedia but also custom data (e.g.
product descriptions, contact data, specialized topic thesauri).
* The [Contenthub](contenthub/) is the component which provides persistent
document store whose back-end is Apache Solr. On top of the store, it enables
semantic indexing facilities during text based document submission
and semantic search together with faceted search capability on the documents.
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=1242853&r1=1242852&r2=1242853&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
Fri Feb 10 16:57:56 2012
@@ -106,7 +106,7 @@ As enhancement engines are identified by
will be selected on requests for a enhancement engine with a given name.
Requests on the RESTful service API will always answer with the enhancement
engine selected as default. When using the Java API there are also means to
retrieve all enhancement engines for a given name via the [Enhancement Engine
Manager](enhancementenginemanager.html) interface.
-Out of a user perspective there is one major use case for configuring multiple
enhancement engines for the same name. This is to allow the definition of
fallback engines if the main one becomes unavailable. e.g. lets assume that a
user has a local cache of geonames.org loaded into the [Entity
Hub](../../entityhub/) and configures an [Named Entity
Linking](keywordlinkingengine.html) engine to perform semantic lifting of
extracted locations. However Apache Stanbol also provides the [geonames.org
Engine](geonamesengine.html) that provides a similar functionality by directly
accessing [geonames.org](http://geonames.org). By configuring both engines for
the same name, but specifying a higher service ranking for the one using the
local cache one can ensure that the local cache is used for the enhancement
under normal circumstances. However in case the local cache becomes unavailable
the other engine using the remote service will be used for enhancement.
+Out of a user perspective there is one major use case for configuring multiple
enhancement engines for the same name. This is to allow the definition of
fallback engines if the main one becomes unavailable. e.g. lets assume that a
user has a local cache of geonames.org loaded into the
[Entityhub](../../entityhub/) and configures an [Named Entity
Linking](keywordlinkingengine.html) engine to perform semantic lifting of
extracted locations. However Apache Stanbol also provides the [geonames.org
Engine](geonamesengine.html) that provides a similar functionality by directly
accessing [geonames.org](http://geonames.org). By configuring both engines for
the same name, but specifying a higher service ranking for the one using the
local cache one can ensure that the local cache is used for the enhancement
under normal circumstances. However in case the local cache becomes unavailable
the other engine using the remote service will be used for enhancement.
### Enhancement Engine Manager Interface
