Author: buildbot
Date: Fri Feb 10 16:58:01 2012
New Revision: 804439

Log:
Staging update by buildbot for stanbol

Added:
    
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html
Modified:
    websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
    
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/index.html

Modified: 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html 
(original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html 
Fri Feb 10 16:58:01 2012
@@ -87,7 +87,7 @@
 <p>The <a href="cmsadapter/">CMS Adapter</a> 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 <a 
href="enhancer/contentitem.html">Content Item</a>s within Contenthub.</p>
 </li>
 <li>
-<p>The <a href="entityhub.html">Entityhub</a> 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).</p>
+<p>The <a href="entityhub/">Entityhub</a> 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).</p>
 </li>
 <li>
 <p>The <a href="contenthub/">Contenthub</a> 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 

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
 Fri Feb 10 16:58:01 2012
@@ -149,7 +149,7 @@ _TODO:_ To correctly construct this grap
 <li>the enhancement engine with the lowest "service.id"</li>
 </ol>
 <p>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 <a 
href="enhancementenginemanager.html">Enhancement Engine Manager</a> 
interface.</p>
-<p>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 <a 
href="../../entityhub/">Entity Hub</a> and configures an <a 
href="keywordlinkingengine.html">Named Entity Linking</a> engine to perform 
semantic lifting of extracted locations. However Apache Stanbol also provides 
the <a href="geonamesengine.html">geonames.org Engine</a> that provides a 
similar functionality by directly accessing <a 
href="http://geonames.org";>geonames.org</a>. 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 us
 ed for enhancement.</p>
+<p>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 <a 
href="../../entityhub/">Entityhub</a> and configures an <a 
href="keywordlinkingengine.html">Named Entity Linking</a> engine to perform 
semantic lifting of extracted locations. However Apache Stanbol also provides 
the <a href="geonamesengine.html">geonames.org Engine</a> that provides a 
similar functionality by directly accessing <a 
href="http://geonames.org";>geonames.org</a>. 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 use
 d for enhancement.</p>
 <h3 id="enhancement_engine_manager_interface">Enhancement Engine Manager 
Interface</h3>
 <p>The <a href="enhancementenginemanager.html">Enhancement Engine Manager</a> 
is the management interface for enhancement engines that can be used by 
components to lookup enhancement engines based on their name. There is also 
OSGI ServiceTracker like implementation that can be used to track only 
enhancement engines registered for a specific set of names. </p>
 <h2 id="enhancement_engine_implementations">Enhancement Engine 
Implementations</h2>

Added: 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html
==============================================================================
--- 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html 
(added)
+++ 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html 
Fri Feb 10 16:58:01 2012
@@ -0,0 +1,108 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+  <title>Apache Stanbol - Entityhub</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <link rel="icon" type="image/png" 
href="/stanbol/images/stanbol-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+  <div id="navigation"> 
+  <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" 
height="101" border="0" 
src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+  <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL";>Issue 
Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the_asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org";>Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html";>Become a 
Sponsor</a></li>
+<li><a href="http://www.apache.org/security/";>Security</a></li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Entityhub</h1>
+    <p>The Entityhub provides two main services. The Entityhub provides the 
connection to external linked open data sites as well as using indexes of them 
locally. Its services allow to manage a <strong>network of sites</strong> to 
consume entity information and to <strong>manage entities locally</strong>.<br 
/>
+</p>
+<p>A small index of approx. 43k entities from dbpedia comes with the default 
installation.</p>
+<h2 id="service_endpoints">Service Endpoints</h2>
+<p>The RESTful API of the Entityhub ist structured as follows:</p>
+<h3 id="entity_network_entityhubsite">Entity Network ("/entityhub/site*"):</h3>
+<ul>
+<li>The Referenced Site Manager @ <a 
href="http://localhost:8080/entityhub/sites";>/entityhub/sites</a> allows to 
manages sites and retrieve/search Entities in all sites of the Entity 
Network.</li>
+<li>A Referenced Site @ /entityhub/site/{siteName} refers to a single site of 
the Referenced Site Manager and allows to retrieve all active sites. Referenced 
sites provide the same interface as the referenced site manager.</li>
+</ul>
+<p>For both services, several features are available:</p>
+<ul>
+<li>
+<p><a 
href="http://localhost:8080/entityhub/sites/referenced";><strong>Referenced</strong></a>
 returns a json array containing the IDs of all available sites. Sites returned 
by this method can be accessed via the site service endpoint.</p>
+</li>
+<li>
+<p><a 
href="http://localhost:8080/entityhub/sites/entity";><strong>Entity</strong></a> 
searches all referenced sites for the entity with the parsed URI.</p>
+</li>
+<li>
+<p><a 
href="http://localhost:8080/entityhub/sites/find";><strong>Find</strong></a> 
provides a label based search service over all sites.</p>
+</li>
+<li>
+<p><a 
href="http://localhost:8080/entityhub/sites/query";><strong>Query</strong></a> 
allows to parse JSON serialized field queries to the sites endpoint.</p>
+</li>
+</ul>
+<p>Currently active referenced sites at the demo server are available and 
running for <a 
href="http://dev.iks-project.eu:8080/entityhub/site/dbpedia/";>dbpedia</a>, <a 
href="http://dev.iks-project.eu:8080/entityhub/site/dblp/";>dplp</a> and <a 
href="http://dev.iks-project.eu:8080/entityhub/site/geonames/";>geonames</a>.</p>
+<h3 id="entityhub_entityhub">Entityhub ("/entityhub"):</h3>
+<ul>
+<li>Local Entities @/entityhub/entity: Full CRUD operations on Entities 
managed by the Entityhub</li>
+<li>Entity Mappings @ /entityhub/mapping: Lookup mappings from local Entities 
to Entities managed by a Referenced Site</li>
+<li>Local Search @/entityhub/find: Find locally managed Entities by label 
based search.</li>
+<li>Local Query @/entityhub/query: Find locally managed Entities by parsing 
queries</li>
+<li>Entity Lookup @/entityhub/lookup: Lookup Entities by id. This supports 
also to lookup Entities managed by Referenced Sites and the import of found 
Entities to the Entityhub.</li>
+</ul>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2010 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0";>Apache 
License, Version 2.0</a>.
+        <br />
+        Apache, Stanbol and the Apache feather and Stanbol logos are 
trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>


Reply via email to