svn commit: r825215 - in /websites/staging/stanbol/trunk/content: ./ stanbol/docs/trunk/entityhub/index.html

[bu...@apache.org]

Author: buildbot
Date: Tue Jul 10 08:34:26 2012
New Revision: 825215

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/content/   (props changed)
    websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html

Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 10 08:34:26 2012
@@ -1 +1 @@
-1359520
+1359521

Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html Tue Jul 10 08:34:26 2012
@@ -86,7 +86,7 @@
 <p><img alt="Features of the Stanbol Entityhub" src="entityhub-overview.png" /></p>
 <p>The main Features are the:</p>
 <ul>
-<li><strong>Entityhub</strong> (<code>/entityhub<code>): Allows to manage local entities as well as import entities from Sites or to define mappings from local Entities to Entities managed by Sites. An Apache Stanbol instance can only have a single Entityhub so if you want to manage multiple controlled vocabularies you should preferable use <a href="managedsite.html">ManagedSite</a> instead.</li>
+<li><strong>Entityhub</strong> (<code>/entityhub</code>): Allows to manage local entities as well as import entities from Sites or to define mappings from local Entities to Entities managed by Sites. An Apache Stanbol instance can only have a single Entityhub so if you want to manage multiple controlled vocabularies you should preferable use <a href="managedsite.html">ManagedSite</a> instead.</li>
 <li><strong>Site Manager</strong> (<code>/entityhub/sites</code>): The SiteManager provides a unified access to all currently active Sites - your Entity Network. Requests sent to this endpoint will be forwarded to all currently active Sites. Users should note that queries (requests to the <code>/entityhub/sites/find</code> and <code>/entityhub/sites/query</code> endpoints) might be slow as remote services might need to be called for answering those requests. Retrieval of Entities (requests to the <code>/entityhub/sites/entity</code> endpoint) and also LDpath requests should perform reasonable well.</li>
 <li><strong>Sites</strong> (<code>/entityhub/site/{siteId}</code>): Sites represent entity sources that are integrated with the Stanbol Entityhub. There are two different types of Sites<ul>
 <li><strong>ReferencedSite</strong>: This site allows to refer remote services to dereference (Entity id based retrieval) and query entities. It also supports local caches and indexes. A local cache allows to locally store retrieved Entity data to speed-up retrieval on subsequent requests. A local index is a locally available index over all/some of the data of the remote dataset. If such an index is available all requests will be processed using the index. The remote services are only used as a fallback. Local Indexes are created by the Entityhub Indexing tool. The usage scenario <a href="../customvocabulary.html">Working with Custom Vocabularies</a> provides a good overview on how to use this feature.</li>