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/04/11 10:30:50 UTC
svn commit: r812318 [1/10] - in /websites/staging/stanbol/trunk/content: ./
stanbol/docs/0.9.0-incubating/ stanbol/docs/0.9.0-incubating/cmsadapter/
stanbol/docs/0.9.0-incubating/contenthub/
stanbol/docs/0.9.0-incubating/enhancer/ stanbol/docs/0.9.0-in...
Author: buildbot
Date: Wed Apr 11 08:30:47 2012
New Revision: 812318
Log:
Staging update by buildbot for stanbol
Added:
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/building.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/cmsadapter5min.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/components.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contentenhancement.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contenthub/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contenthub/contenthub5min.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contenthub/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/customvocabulary.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/downloads.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/chainmanager.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/defaultchain.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/enhancer-defaultchain-config.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/enhancer-graphchain-config.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/enhancer-listchain-config.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/enhancer-weightedchain-allactive.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/enhancer-weightedchain-config.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/enhancer-weightedchain-optionalinactive.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/enhancer-weightedchain-requiredinactive.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/executionplan.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/executionplan.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/graphchain.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/listchain.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/chains/weightedchain.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/contentitem.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/contentitemmultipartmime.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/contentitemoverview.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/enhancementenginemanager.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/geonamesengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/keywordlinkingengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/keywordlinkingengineconfig.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/langidengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/list.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/metaxaengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/namedentityextractionengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/namedentitytaggingengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/opencalaisengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/refactorengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/tikaengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/engines/zemantaengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/enhancementexample.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/enhancementjobmanager.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/enhancementjobmanageroverview.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/enhancementstructureoverview.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/enhanceroverview-s.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/enhanceroverview.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/enhancerrest.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/executionmetadata.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/executionmetadata.png (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/ses_annotationontology.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/setting-enhancement.owl (with props)
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/enhancer/stanbolenhancementstructure.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/entityhub/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/entityhub/entityhubandlinkeddata.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/entityhub/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/examples/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/examples/anl-mappings.txt
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/factstore/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/factstore/implementation.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/factstore/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/factstore/specification.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/faq.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/features.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/mailinglists.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/multilingual.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/ontologymanager/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/ontologymanager/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/ontologymanager/ontonet/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/ontologymanager/ontonet/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/ontologymanager/registry/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/ontologymanager/registry/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/ontologymanager/registry/language.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/reasoners.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/language.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/refactor.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/store.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/scenarios.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/services.html
websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/tutorial.html
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr 11 08:30:47 2012
@@ -1 +1 @@
-1307342
+1324628
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/building.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/building.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/building.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,105 @@
+<!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 - Building Apache Stanbol</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">Building Apache Stanbol</h1>
+ <p>To build Stanbol from source you need Java 6 and maven 2.2.1 + (version as defined in the pom). You probably need also: <code>$ export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=128M </code></p>
+<p>Fetch the sources from the Apache code repository</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">co</span> <span class="n">http:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span class="n">asf</span><span class="sr">/incubator/s</span><span class="n">tanbol</span><span class="o">/</span><span class="n">trunk</span> <span class="n">stanbol</span>
+</pre></div>
+
+
+<p>From the source directory run:</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mvn</span> <span class="n">clean</span> <span class="n">install</span>
+</pre></div>
+
+
+<p><em>Updating sources</em>: From your Stanbol root directory call <code>$ mvn clean</code>, then <code>% svn update</code> and build a new version with <code>$ mvn clean install</code>.</p>
+<p>Now, several launchers should be available under the <code>launchers/</code> directory:</p>
+<ul>
+<li>The <em>"stable launcher"</em> provides you with the most stable components only,</li>
+<li>the <em>"full launcher"</em> contains all major components available, </li>
+<li>the <em>"stateless launcher"</em> lets you work with Apache Stanbol components in offline mode and </li>
+<li>the <em>"kres launcher"</em> activates the rules machinery only.</li>
+</ul>
+<p>You can launch the server with:</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">java</span> <span class="o">-</span><span class="n">Xmx1g</span> <span class="o">-</span><span class="n">jar</span> <span class="n">full</span><span class="sr">/target/o</span><span class="n">rg</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">stanbol</span><span class="o">.</span><span class="n">launchers</span><span class="o">.</span><span class="n">full</span><span class="o">-</span><span class="mf">0.9</span><span class="o">-</span><span class="n">SNAPSHOT</span><span class="o">.</span><span class="n">jar</span>
+</pre></div>
+
+
+<p>Your instance is then available on <a href="http://localhost:8080">http://localhost:8080</a>. You may change the default
+port number by passing a <code>-p 9090</code> options to the commandline launcher. Use <code>-h</code>
+to see more options.</p>
+<p>Upon first startup, a folder named <code>sling/</code> is created in the current folder. This folder
+contains Stanbol's persistent data, deployment configuration and logs.</p>
+<p><strong>HTTP entry points: Web view and REST API</strong></p>
+<p>The web interface of your Apache Stanbol installation provides information for the main HTTP entry points. Each resource also comes with a web view that documents the matching RESTful API for applications.</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 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>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/cmsadapter5min.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/cmsadapter5min.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/cmsadapter5min.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,134 @@
+<!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 - </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"></h1>
+ <h1 id="5-minutes-documentation-for-cms-adapter">5 Minutes Documentation for CMS Adapter</h1>
+<p>The CMS Adapter component acts as a bridge between content management systems and the Apache Stanbol. Please note that all components of Apache Stanbol also provides RESTful services which allow accessing them directly from outside. CMS Adapter interacts with content management systems through JCR and CMIS specifications. In other words, any content repository compliant with JCR or CMIS specifications can make use of CMS Adapter functionalities. For the time being, there are two main functionalities that CMS Adapter offers: "Bidirectional Mapping" and "Contenthub Feed". </p>
+<p><strong>Note</strong>: URLs given in the curl commands and link are valid as long as full launcher of the Stanbol is launched with the default configurations. In other words, it assumed that the root URL of the Stanbol is <strong>http://localhost:8080</strong>.</p>
+<h2 id="session-management">Session Management</h2>
+<p>To be able to use Contenthub features, it is necessary to get a session key beforehand. While obtaining this key, CMS Adapter caches a JCR/CMIS session to be used when the generated session key is passed in the subsequent operations that require interaction with the content repository. A session can key can be obtained through REST services as follows:</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">X</span> <span class="n">GET</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Accept: text/plain"</span> <span class="s">"http://localhost:8080/cmsadapter/session?repositoryURL=rmi://localhost:1099/crx&workspaceName=demo&username=admin&password=admin&connectionType=JCR"</span>
+</pre></div>
+
+
+<p>In this example a session key is obtained for a JCR compliant repository. CMS Adapter use RMI protocol to get session from JCR repositories or it tries to access repository via a URL. So, RMI endpoint or URL of the repository is specified. Furthermore target workspace in the repository has been specified together with the username and password to access it. While accessing CMIS repositories AtomPub binding is used, so repository URL should be specified considering this protocol.</p>
+<p>Apart from the retrieval of session key by providing one by one as in the RESTful example, Java API of CMS Adapter also allows obtaining a session key with an already available session object through the SessionManager service. Thus, this is a more convenient way while obtaining a session key using CMS Adapter through its Java API.</p>
+<h2 id="bidirectional-mapping">Bidirectional Mapping</h2>
+<p>This feature provides bidirectional mappings between JCR/CMIS compliant content repositories and external RDF data. Using this feature it is possible to generate RDF data from content repository or populate content repository based on the external RDF data.</p>
+<p>The functionality described in this feature is realized by a two-step process. This process includes sequential execution of RDFBridge and RDFMapper services of CMS Adapter. Considering the update of content repository based on external RDF data, in the first step the given raw RDF data is annotated with standard terms by RDFBridge. There are a few terms that are described in the <strong>CMS Vocabulary</strong> section. RDFMapper processes the annotated RDF and update the content repository accordingly. From the other direction, in the first step content repository structure is transformed into RDF annotated with the CMS Vocabulary terms by RDFMappers. In the second step RDFBridges add implementation specific annotations.</p>
+<p>From one perspective, bidirectional mapping feature makes possible to exploit open linked data, which is already available on the web, in content management systems. Apart from the already available RDF data on the web, any RDF data can be mapped to content repository. By mapping external RDF data existing content repository items can be updated or new ones created. </p>
+<p>This services is also available through RESTful API. A curl command as follows will map the rdf data given in rdfData file to content repository. The mapping done according to configurations of default RDF Bridge implementation which can be changed through the <strong>Apache Stanbol CMS Adapter Default RDF Bridge Configurations</strong> entry of <a href="http://localhost:8080/system/console/configMgr">Configuration Panel Apache Felix Web Console</a>. It is possible to define several configurations and all of these configurations are processed in transformation process. In case of no configuration, provided RDF is processed by RDFMapper directly.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span class="o">--</span><span class="n">data</span><span class="o">-</span><span class="n">urlencode</span> <span class="s">"serializedGraph@rdfData"</span> <span class="o">--</span><span class="n">data</span> <span class="s">"sessionKey=9ef42d3c-aaa3-494f-ba6f-c247a58ac2db"</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/cmsadapter/m</span><span class="n">ap</span><span class="o">/</span><span class="n">rdf</span>
+</pre></div>
+
+
+<p>This <a href="http://blog.iks-project.eu/adding-knowledge-to-jcrcmis-content-repositories/">blog post</a> from October 2011 describes the process of adding knowledge from DBPedia to a Nuxeo content management system which is a CMIS compliant repository. </p>
+<p>From the other perspective, thanks to this feature repository structure can be transformed into RDF through RESTful services as well. A curl command similar to following one can be used to map content repository structure into RDF format.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span class="o">--</span><span class="n">data</span> <span class="s">"sessionKey=9ef42d3c-aaa3-494f-ba6f-c247a58ac2db&baseURI=http://www.apache.org/stanbol/cms"</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/cmsadapter/m</span><span class="n">ap</span><span class="o">/</span><span class="n">cms</span>
+</pre></div>
+
+
+<p>Note that during the mapping process of bidirectional mappings the same RDF Bridge configurations are used in both directions. Also, <strong>baseURI</strong> is a mandatory parameter that is used as the base URI of the RDF to be generated.</p>
+<p>RDF representation of a content management system helps building semantic services on top of the existing system. Contenthub component of Apache Stanbol can be used to provide semantic indexing and search functionalities based on the RDF representation of content repositories. That is, the RDF representation is used as a resource that Contenthub uses to populate the underlying semantic index.</p>
+<h2 id="contenthub-feed">Contenthub Feed</h2>
+<p>Contenthub feed feature aims to manage content repository items within the Contenthub component of Apache Stanbol. The management process includes only two types of operations, submit and delete. </p>
+<p>Submission and deletion operations can be done based on the identifiers of path of the content repository items. During the submission process, properties of content repository items are collected and they are stored along with the actual content. This makes possible faceted search over the properties of items.</p>
+<p>RESTful API of CMS Adapter can be used submit content repository items to Contenthub.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span class="o">--</span><span class="n">data</span> <span class="s">"sessionKey=9ef42d3c-aaa3-494f-ba6f-c247a58ac2db&path=/contenthubfeedtest&recursive=true"</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/cmsadapter/co</span><span class="n">ntenthubfeed</span>
+</pre></div>
+
+
+<p>The previous curl command submits all content repository items under the <strong>/contenthubfeedtest</strong> path to the Contenthub. In a similar way content item can be deleted from Contenthub. Following command deletes the content items corresponding to the content repository items under the /contenthubfeedtest path.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">DELETE</span> <span class="o">--</span><span class="n">data</span> <span class="s">"sessionKey=9ef42d3c-aaa3-494f-ba6f-c247a58ac2db&path=/contenthubfeedtest&recursive=true"</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/cmsadapter/co</span><span class="n">ntenthubfeed</span>
+</pre></div>
+
+
+<h2 id="cms-vocabulary">CMS Vocabulary</h2>
+<p>This vocabulary aims to provide a standardized mapping between content repositories and RDF data. This vocabulary includes a small number of essential terms to map an RDF data to a content repository. As well as general terms that are commonly used for both JCR and CMIS repositories there are also JCR or CMIS specific terms.</p>
+<h3 id="general-terms">General Terms</h3>
+<ul>
+<li>CMS_OBJECT: In a CMS vocabulary annotated RDF, if a resource has this URI reference as value of its rdf:type property, the subject of that resource represents a content repository item e.g a node in JCR compliant content repositories or an object in CMIS compliant content repositories.</li>
+<li>CMS_OBJECT_NAME: This URI reference represents the name of the content repository item.</li>
+<li>CMS_OBJECT_PATH: This URI reference represents the absolute path of the content repository item.</li>
+<li>CMS_OBJECT_PARENT_REF: This URI reference represents the item to be created as parent of the item having this property.</li>
+<li>CMS_OBJECT_HAS_URI: This URI reference represents the URI which is associated with the content repository item.</li>
+</ul>
+<h3 id="jcr-specific-properties">JCR Specific Properties</h3>
+<ul>
+<li>JCR_PRIMARY_TYPE: This URI reference represents primary node of the content repository item associated with the resource within the RDF.</li>
+<li>JCR_MIXIN_TYPES: This URI reference represents the mixin type of the content repository item associated with the resource within the RDF.</li>
+</ul>
+<h3 id="cmis-specific-properties">CMIS Specific Properties</h3>
+<ul>
+<li>CMIS_BASE_TYPE_ID: This URI reference represents the base type of the content repository item associated with the resource within the RDF.</li>
+</ul>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 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>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/index.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/cmsadapter/index.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,89 @@
+<!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 - CMS Adapter</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">CMS Adapter</h1>
+ <p>The CMS Adapter component acts as a bridge between content management systems and the Apache Stanbol. Please note that all components of Apache Stanbol also provides RESTful services which allow accessing them directly from outside. CMS Adapter interacts with content management systems through JCR and CMIS specifications. In other words, any content repository compliant with JCR or CMIS specifications can make use of CMS Adapter functionalities. For the time being, there are two main functionalities that CMS Adapter offers: "Bidirectional Mapping" and "Contenthub Feed". </p>
+<h2 id="bidirectional-mapping">Bidirectional Mapping</h2>
+<p>From one perspective, this feature enables content management systems to represent their content repository structure in RDF format. This helps building semantic services on top of the existing content management systems using their RDF representation. </p>
+<p>From the other perspective, bidirectional mapping feature makes possible to exploit open linked data, which is already available on the web, in content management systems. Apart from the already available data on the web, any RDF data can be mapped to content repository. By mapping external RDF data existing content repository items can be updated or new ones created. </p>
+<h2 id="contenthub-feed">Contenthub Feed</h2>
+<p>Contenthub feed feature of CMS Adapter provides management of content repository items within Contenthub. The management process includes only two types of operations, namely: submit and delete. By submitting content items to Contenthub, you can make use of indexing and search functionalities of Contenthub over the submitted items.</p>
+<h2 id="use-cases">Use Cases</h2>
+<h3 id="faceted-search">Faceted Search</h3>
+<p>As properties of content repository items are submitted to Contenthub along with the actual content, it is possible to provide to obtain faceted search facility for the content items managed within Contenthub. Furthermore, any kind of Solr query can be executed on the index keeping the submitted content items.</p>
+<h3 id="exploiting-linked-data">Exploiting Linked Data</h3>
+<p>Chance of mapping any RDF data to content repository enables users making use of <a href="http://linkeddata.org/">open linked data</a> available on the web. Current implementation is especially handy for hierarchical RDF data e.g. category, topic hierarchies. Users can populate content repositories with hierarchies in which further content items can be created.</p>
+<h2 id="building-and-launching">Building and Launching</h2>
+<p>Since CMS Adapter is included in the Full Launcher of Apache Stanbol it is built with Apache Stanbol by default and can be launched under Apache Stanbol Full Launcher. For detailed instructions to build and launch Apache Stanbol see this README file.</p>
+<p>CMS Adapter serves its features through its Java API together with the corresponding RESTful services. Restful services can be accessed starting from the root resource: http://localhost:8080/cmsadapter after launching the full launcher with default configurations.</p>
+<p>More detailed information can be found in <a href="cmsadapter5min">5-minute documentation</a> of CMS Adapter.</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 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>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/components.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/components.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/components.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,117 @@
+<!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 - Apache Stanbol Components</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">Apache Stanbol Components</h1>
+ <p>Apache Stanbol is built as a modular set of components. Each component is accessible via its own RESTful web interface. From this viewpoint, all Apache Stanbol features can be used via RESTful service calls. The components are implemented as <a href="http://www2.osgi.org/Specifications/HomePage">OSGi</a> components based on <a href="http://felix.apache.org">Apache Felix</a>.</p>
+<p>This page gives an overview of the major features of various Apache Stanbol components. Figure 1 depicts the main Apache Stanbol components and their arrangement within the Apache Stanbol architecture. Additionally, we have documented some <a href="scenarios.html">usage scenarios</a>.</p>
+<figure>
+
+<figcaption>Figure 1: Apache Stanbol Components</figcaption>
+</figure>
+
+<p>We will shortly describe the components from top to bottom and link to their detailed descriptions.</p>
+<ul>
+<li>
+<p>The <a href="enhancer/">Enhancer</a> component together with its <a href="enhancer/engines/list.html">Enhancement Engines</a> provides you with the ability to post content to Apache Stanbol and get suggestions for possible entity annotation in return. The enhancements are provided via natural language processing, metadata extraction and linking named entities to public or private entity repositories. Furthermore, Apache Stanbol provides a machinery to further process this data and add additional knowledge and links via applying rules and reasoning. Technically, the enhancements are stored in a triple-graph that is maintained by <a href="http://incubator.apache.org/clerezza">Apache Clerezza</a>.</p>
+</li>
+<li>
+<p>The 'Sparql endpoint' gives access to the semantic enhancements form the Apache Stanbol <a href="enhancer/">Enhancer</a>.</p>
+</li>
+<li>
+<p>The 'EnhancerVIE' is a stateful interface to submit content to analyze and store the results on the server. It is then possible to browse the resulting enhanced content items.</p>
+</li>
+<li>
+<p>The <a href="rules.html">Rules</a> component provides you with the means to re-factor knowledge graphs, e.g. for supporting the schema.org vocabulary for Search Engine Optimization. </p>
+</li>
+<li>
+<p>The <a href="reasoners.html">Reasoners</a> can be used to automatically infer additional knowledge. It is used to obtain new facts in the knowledge base, e.g. if your enhanced content tells you about a shop located in "Montparnasse", you can infer via a "located-in" relation that the same shop is located in "Paris", in the "Ãle-de-France" and in "France".</p>
+</li>
+<li>
+<p>The <a href="ontologymanager/">Ontology Manager</a> is the facility that manages your ontologies. Ontologies are used to define the knowledge models that describe the metadata of content. Additionally, the semantics of your metadata can be defined through an ontology.</p>
+</li>
+<li>
+<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/">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
+and semantic search together with faceted search capability on the documents.</p>
+</li>
+<li>
+<p>The <a href="factstore/">FactStore</a> is a component that let's use store relations between entities identified by their URIs. This relation between two entities is called a <em>fact</em>.</p>
+</li>
+</ul>
+<hr />
+<p><em>Back to <a href="index.html">Documentation</a></em></p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 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>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contentenhancement.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contentenhancement.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contentenhancement.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,218 @@
+<!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 - Using Apache Stanbol for enhancing textual content</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">Using Apache Stanbol for enhancing textual content</h1>
+ <p>For enhancing content you simply post plain text content to the Enhancement Engines and you will get back enhancement data. The enhancement process is stateless, so neither your content item, nor the enhancements will be stored. </p>
+<p>You can test this via the [web interface of the engines][stan-engines] or from console via</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Accept: text/turtle"</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Content-type: text/plain"</span> <span class="o">\</span>
+<span class="o">--</span><span class="n">data</span> <span class="s">"The Stanbol enhancer can detect famous cities such as Paris \</span>
+<span class="s">and people such as Bob Marley."</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="o">/</span><span class="n">engines</span>
+</pre></div>
+
+
+<p>or by using the text examples delivered with Stanbol.</p>
+<div class="codehilite"><pre><span class="k">for</span> <span class="n">file</span> <span class="n">in</span> <span class="n">enhancer</span><span class="sr">/data/</span><span class="n">text</span><span class="o">-</span><span class="n">examples</span><span class="o">/*.</span><span class="n">txt</span><span class="p">;</span>
+<span class="k">do</span>
+<span class="n">curl</span> <span class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Accept: text/turtle"</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Content-type: text/plain"</span> <span class="o">-</span><span class="n">T</span> <span class="nv">$file</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="o">/</span><span class="n">engines</span><span class="p">;</span>
+<span class="n">done</span>
+</pre></div>
+
+
+<p>Content items in formats other than plain text can be tested via the [web interface of contenthub][stan-contenthub] or via the console by attaching files. (The Metaxa Engine needs to be activated).</p>
+<h2 id="using-the-enhancement-engines">Using the enhancement engines</h2>
+<p>Apache Stanbol starts with a number of active enhancement engines by default. You can activate or deactivate engines as well as configure them to your needs via the [OSGI administration console][stan-admin].</p>
+<p>For the enhancement engines, a workflow for the enhancement process is defined as pre-processing, content-extraction, extraction-enhancement, default and post-processing. </p>
+<p>The following pre-processing engines are available:</p>
+<ul>
+<li>
+<p>The <strong>Language Identification Engine</strong> detects several European languages of the content items you want to process.</p>
+</li>
+<li>
+<p>The <strong>Metaxa Engine</strong> extracts embedded metadata and textual content from a large variety of document types and formats.</p>
+</li>
+</ul>
+<p>For content extraction / natural language processing one engine is available:</p>
+<ul>
+<li>The <strong>Named Entity Extraction Enhancement Engine</strong> leverages the sentence detector and name finder tools of the OpenNLP project bundled with statistical models trained to detect occurrences of names of persons, places and organizations.</li>
+</ul>
+<p>The extracted items will then be enhanced by a dedicated engine:</p>
+<ul>
+<li>The <strong>Named Entity Tagging Engine</strong> provides according suggestions from dbpedia (default) and other references sites for entities extracted by the NER engine .</li>
+</ul>
+<p>Specific additional enhancement engines are: </p>
+<ul>
+<li>
+<p>The <strong>Location Enhancement Engine</strong> takes its suggestions from geonames.org only.</p>
+</li>
+<li>
+<p>The <strong>OpenCalais Enhancement Engine</strong> uses services from Open Calais. (Note: You need to provide a key in order to use this engine)</p>
+</li>
+<li>
+<p>The <strong>Zemanta Enhancement Engine</strong> uses the Zemanta services. (Note: You need to provide a key in order to use this engine)</p>
+</li>
+</ul>
+<p>For post-processing the results of the enhancement engines</p>
+<ul>
+<li>The <strong>CachingDereferencerEngine</strong> is used for the Web UI and fetches files such as images for locations from external sites and is used to present the enhancement results. </li>
+</ul>
+<h2 id="using-an-index-of-linked-open-data-locally">Using an index of linked open data locally</h2>
+<p>To use the pre-configured indexes you can download them from [here][stan-download]. You will get two files for each index:</p>
+<ul>
+<li>org.apache.stanbol.data.site.{name}-{version}.jar </li>
+<li>{name}.solrindex.zip</li>
+</ul>
+<p>By copying the zip archive into the "/sling/datafiles" folder before installing the bundle, the data will used during the installation of the bundle automatically. If you provide the file after installing the bundle, you will need to restart the SolrYard installed by the bundle.</p>
+<p>The jar can be installed at any OSGI environment running the Apache Stanbol Entityhub. When started it will create and configure:</p>
+<ul>
+<li>a "ReferencedSite" accessible at "http://{host}/{root}/entityhub/site/{name}"</li>
+<li>a "Cache" used to connect the ReferencedSite with your Data and</li>
+<li>a "SolrYard" that manages the data indexed by this utility.</li>
+</ul>
+<p>This bundle does not contain the indexed data but only the configuration for the Solr Index.</p>
+<p>If one has not copied the archive beforehand, the ZIP archive will be requested by the Apache Stanbol Data File Provider after installing the Bundle. To install the data you need copy this file to the "/sling/datafiles" folder within the working directory of your Stanbol Server.</p>
+<p><em>Note: {name} denotes to the value you configured for the "name" property within the "indexing.properties" file.</em></p>
+<h2 id="enhancement-example">Enhancement Example</h2>
+<p>The text "The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley." with the default configuration of enhancement engines and with a local index of dbpedia entities will result in the following output graph of several <strong>Entity Annotations</strong> and <strong>Text Annotations</strong>. </p>
+<p>Two of the relevant fragments for "Paris" are listed below in Turtle-Syntax:</p>
+<h3 id="example-for-text-annotation">Example for Text Annotation</h3>
+<div class="codehilite"><pre><span class="sr"><urn:enhancement-4a2543d8-4d83-43ce-3a33-2924f457c872></span>
+ <span class="n">a</span> <span class="sr"><http://fise.iks-project.eu/ontology/TextAnnotation></span> <span class="p">,</span>
+ <span class="sr"><http://fise.iks-project.eu/ontology/Enhancement></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/confidence></span>
+ <span class="s">"0.9322403510215739"</span><span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#double></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/end></span>
+ <span class="s">"59"</span><span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#int></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/extracted-from></span>
+ <span class="sr"><urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/selected-text></span>
+ <span class="s">"Paris"</span><span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/selection-context></span>
+ <span class="s">"The Stanbol enhancer can detect famous cities such as </span>
+<span class="s"> Paris and people such as Bob Marley."</span>
+ <span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/start></span>
+ <span class="s">"54"</span><span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#int></span> <span class="p">;</span>
+
+ <span class="sr"><http://purl.org/dc/terms/created></span>
+ <span class="s">"2012-02-29T11:18:36.282Z"</span><span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#dateTime></span> <span class="p">;</span>
+
+ <span class="sr"><http://purl.org/dc/terms/creator></span>
+ <span class="s">"org.apache.stanbol.enhancer.engines.opennlp.impl.NEREngineCore"</span>
+ <span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span class="p">;</span>
+
+ <span class="sr"><http://purl.org/dc/terms/type></span>
+ <span class="sr"><http://dbpedia.org/ontology/Place></span> <span class="o">.</span>
+</pre></div>
+
+
+<h3 id="example-for-entity-annotation">Example for Entity Annotation</h3>
+<div class="codehilite"><pre><span class="sr"><urn:enhancement-b5e71f70-4978-a70b-7111-8d6e31283a58></span>
+ <span class="n">a</span> <span class="sr"><http://fise.iks-project.eu/ontology/EntityAnnotation></span> <span class="p">,</span>
+ <span class="sr"><http://fise.iks-project.eu/ontology/Enhancement></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/confidence></span>
+ <span class="s">"1323049.5"</span><span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#double></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/entity-label></span>
+ <span class="s">"Paris"</span><span class="nv">@en</span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/entity-reference></span>
+ <span class="sr"><http://dbpedia.org/resource/Paris></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/entity-type></span>
+ <span class="sr"><http://www.w3.org/2002/07/owl#Thing></span> <span class="p">,</span>
+ <span class="sr"><http://www.opengis.net/gml/_Feature></span> <span class="p">,</span>
+ <span class="sr"><http://dbpedia.org/ontology/Place></span> <span class="p">,</span>
+ <span class="sr"><http://dbpedia.org/ontology/Settlement></span> <span class="p">,</span>
+ <span class="sr"><http://dbpedia.org/ontology/PopulatedPlace></span> <span class="p">;</span>
+
+ <span class="sr"><http://fise.iks-project.eu/ontology/extracted-from></span>
+ <span class="sr"><urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10></span> <span class="p">;</span>
+
+ <span class="sr"><http://purl.org/dc/terms/created></span>
+ <span class="s">"2012-02-29T11:18:36.320Z"</span>
+ <span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#dateTime></span> <span class="p">;</span>
+
+ <span class="sr"><http://purl.org/dc/terms/creator></span>
+ <span class="s">"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine"</span>
+ <span class="o">^^</span><span class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span class="p">;</span>
+
+ <span class="sr"><http://purl.org/dc/terms/relation></span>
+ <span class="sr"><urn:enhancement-4a2543d8-4d83-43ce-3a33-2924f457c872></span> <span class="o">.</span>
+</pre></div>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 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>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contenthub/contenthub5min.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contenthub/contenthub5min.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/contenthub/contenthub5min.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,205 @@
+<!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 - Contenthub (5 minutes tutorial)</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">Contenthub (5 minutes tutorial)</h1>
+ <p>The Apache Stanbol Contenthub is an Apache Solr based document repository which enables storage of text-based documents and customizable semantic search facilities. Contenthub exposes an efficient Java API together with the corresponding RESTful services. </p>
+<p>Contenthub is basically a document repository. A document within Contenthub is referred as a "Content Item". A content item consists of metadata of the document in addition to the text-based content of the document. Contenthub has two main subcomponents, namely Store and Search. As their names indicate, Store is specifically responsible for persistent storage of content items. And Search provides strong semantic search facilities on top of the content items.</p>
+<h2 id="contenthub-store">Contenthub Store</h2>
+<p>It is the part of Contenthub which actually stores the documents and their metadata persistently. In current implementation only text/plain documents are supported.</p>
+<p>The storage part of the Contenthub provide basic methods such as create, put, get and delete. When a document is submitted, it delegates the textual content to Stanbol Enhancer to retrieve its enhancements. (Enhancements of a content item are called its metadata within the terminology) While submitting the document, it is also possible to specify external metadata (in addition to the enhancements retrieved from Enhancer) as field:value pairs along with the document.</p>
+<p>The document itself and all metadata are indexed through an embedded Apache Solr core/index which is created specifically for Contenthub. Since documents are given unique IDs while indexing, using its unique ID, a document can be retrieved or deleted from Contenthub. Contenthub provides an HTML interface for its functionalities under the following endpoint, which is available after running the full launcher of Apache Stanbol:</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>
+</pre></div>
+
+
+<p>Apache Solr can manage several cores (indexes) within the same running instance, and Contenthub makes use of this facility to manage different those cores. This management performed by LDPath programs<a href="http://code.google.com/p/ldpath/">1</a>.</p>
+<p>LDPath is a simple path-based query language similar to XPath or SPARQL Property Paths that is particularly well-suited for querying and retrieving resources from the Linked Data Cloud by following RDF links between resources and servers. For example, the following path query would select the names of objects (people) who is known by the context resource (the resource on which this path is being executed):<br />
+</p>
+<div class="codehilite"><pre><span class="err">foaf:knows</span> <span class="err">/</span> <span class="err">foaf:name</span>
+</pre></div>
+
+
+<p>An LDPath program is a collection of path queries. For example, following LDPath program can be executed on the resources which can be retrieved from Stanbol Enhancer as a result of the enhancement process. An LDPath program can be executed on any semantic collection of resources to extract specific information.</p>
+<div class="codehilite"><pre><span class="nv">@prefix</span> <span class="n">rdf</span> <span class="p">:</span> <span class="sr"><http://www.w3.org/1999/02/22-rdf-syntax-ns#></span><span class="p">;</span>
+<span class="nv">@prefix</span> <span class="n">rdfs</span> <span class="p">:</span> <span class="sr"><http://www.w3.org/2000/01/rdf-schema#></span><span class="p">;</span>
+<span class="nv">@prefix</span> <span class="n">db</span><span class="o">-</span><span class="n">ont</span> <span class="p">:</span> <span class="sr"><http://dbpedia.org/ontology/></span><span class="p">;</span>
+<span class="n">title</span> <span class="o">=</span> <span class="n">rdfs:label</span> <span class="o">::</span> <span class="n">xsd:string</span><span class="p">;</span>
+<span class="n">dbpediatype</span> <span class="o">=</span> <span class="n">rdf:type</span> <span class="o">::</span> <span class="n">xsd:anyURI</span><span class="p">;</span>
+<span class="n">population</span> <span class="o">=</span> <span class="n">db</span><span class="o">-</span><span class="n">ont:populationTotal</span> <span class="o">::</span> <span class="n">xsd:int</span><span class="p">;</span>
+</pre></div>
+
+
+<p>Given an LDPath program, Contenthub can create a corresponding Solr core to index the content items through that core. When you submit a document to Contenthub Store by providing an LDPath program, this means the content item (the document content and its metadata/enhancements) will be indexed according to the fields determined by the LDPath program. For instance, the example LDPath program above will lead to a Solr core including the following fields (in addition to default configuration and several default fields)</p>
+<div class="codehilite"><pre><span class="o"><</span><span class="n">field</span> <span class="n">name</span><span class="o">=</span><span class="s">"title"</span> <span class="n">type</span><span class="o">=</span><span class="s">"string"</span> <span class="n">stored</span><span class="o">=</span><span class="s">"true"</span> <span class="n">indexed</span><span class="o">=</span><span class="s">"true"</span> <span class="n">multiValued</span><span class="o">=</span><span class="s">"true"</span><span class="o">/></span>
+<span class="o"><</span><span class="n">field</span> <span class="n">name</span><span class="o">=</span><span class="s">"dbpediatype"</span> <span class="n">type</span><span class="o">=</span><span class="s">"uri"</span> <span class="n">stored</span><span class="o">=</span><span class="s">"true"</span> <span class="n">indexed</span><span class="o">=</span><span class="s">"true"</span> <span class="n">multiValued</span><span class="o">=</span><span class="s">"true"</span><span class="o">/></span>
+<span class="o"><</span><span class="n">field</span> <span class="n">name</span><span class="o">=</span><span class="s">"population"</span> <span class="n">type</span><span class="o">=</span><span class="s">"int"</span> <span class="n">stored</span><span class="o">=</span><span class="s">"true"</span> <span class="n">indexed</span><span class="o">=</span><span class="s">"true"</span> <span class="n">multiValued</span><span class="o">=</span><span class="s">"true"</span><span class="o">/></span>
+</pre></div>
+
+
+<p>To submit an LDPath program, you can use the following command through the REST API of Contenthub</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span class="o">-</span><span class="n">d</span> <span class="o">\</span>
+ <span class="s">"name=myindex&program=\</span>
+<span class="s"> @prefix rdf : <http://www.w3.org/1999/02/22-rdf-syntax-ns#>; \ </span>
+<span class="s"> @prefix rdfs : <http://www.w3.org/2000/01/rdf-schema#>; \</span>
+<span class="s"> @prefix db-ont : <http://dbpedia.org/ontology/>; \</span>
+<span class="s"> title = rdfs:label :: xsd:string; dbpediatype = rdf:type :: xsd:anyURI; \ </span>
+<span class="s"> population = db-ont:populationTotal :: xsd:int;"</span> <span class="o">\</span>
+ <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/contenthub/</span><span class="n">ldpath</span><span class="o">/</span><span class="n">program</span>
+</pre></div>
+
+
+<p>You can retrieve the list of managed LDPath programs in JSON format with the following command. This is also the list of available Solr cores (except the default Solr core)</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">GET</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/contenthub/</span><span class="n">ldpath</span>
+</pre></div>
+
+
+<p>LDPath related management is performed through SemanticIndexManager of Contenthub. To take advantage of semantic indexes while storing content items, you need to specify the name of the index in the path of the url while submitting the document. Default index for contenthub is named as "contenthub". Hence, following command submits document to the default index:</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Content-Type:application/x-www-form-urlencoded"</span> <span class="o">\</span>
+ <span class="o">-</span><span class="n">d</span> <span class="s">"title=about me&content=I live in Istanbul."</span> <span class="o">\</span>
+ <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/contenthub/co</span><span class="n">ntenthub</span><span class="o">/</span><span class="n">store</span>
+</pre></div>
+
+
+<p>Following command will store the content item into Solr core names with "myindex". Therefore, the indexing will be performed through the field properties indicated with the LDPath program named with "myindex".</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Content-Type:application/x-www-form-urlencoded"</span> <span class="o">\</span>
+ <span class="o">-</span><span class="n">d</span> <span class="s">"title=about me&content=I live in Istanbul."</span> <span class="o">\</span>
+ <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/contenthub/m</span><span class="n">yindex</span><span class="o">/</span><span class="n">store</span>
+</pre></div>
+
+
+<h2 id="contenthub-search">Contenthub Search</h2>
+<p>Contenthub provides three search interfaces so that capabilities of Stanbol can be adopted by the users through different levels of complexities. These interfaces are;</p>
+<ul>
+<li><strong>SolrSearch</strong>: provides native Solr interface to the outside world.
+ Retrieved the resulting content items (documents) from the Solr
+ backend. SolrJ users can easily make use of this interface. Search
+ is performed on the corresponding Solr index and results are
+ returned in "org.apache.solr.client.solrj.response.QueryResponse"
+ format.</li>
+<li><strong>RelatedKeywordSearch</strong>: provides supporting functionalities for search
+ facilities. Given a keyword, services of this interface finds other
+ related keywords from several sources. Wordnet, domain ontologies
+ and referenced sites are the data sources for these services to
+ retrieve the related keywords.</li>
+<li><strong>FeaturedSearch</strong>: Combines the services of SolrSearch and
+ RelatedKeywordSearch for the users who want the results of a query
+ term all in one interface. Featured search not only returns
+ resulting documents, but also related keywords retrieved from
+ various resources (if the resources are available within the running
+ Stanbol instance) Given a query term, returns the resultant
+ documents from the queried Solr core/index and related keywords from
+ different sources.</li>
+</ul>
+<p>Following request retrieves all documents from the default index (whose name is "contenthub") of Solr:</p>
+<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/solr/</span><span class="n">default</span><span class="sr">/contenthub/s</span><span class="n">elect</span><span class="p">?</span><span class="n">q</span><span class="o">=*</span><span class="p">:</span><span class="o">*</span>
+</pre></div>
+
+
+<p>Following request retrieves all documents from the Solr index named as "myindex":</p>
+<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/solr/</span><span class="n">default</span><span class="sr">/myindex/s</span><span class="n">elect</span><span class="p">?</span><span class="n">q</span><span class="o">=*</span><span class="p">:</span><span class="o">*</span>
+</pre></div>
+
+
+<p>RelatedKeywordSearch is performed by three independent search engines within the Stanbol system, namely: </p>
+<ul>
+<li><strong>OntologyResourceSearch</strong>: If an ontology is already registered to
+ Stanbol (e.g. a domain ontology), it can be used to look for similar
+ keywords, given a keyword. A SPARQL query based on a LARQ index is
+ executed on the specified ontology to find individual and class
+ resources related with the keyword.</li>
+<li><strong>ReferencedSiteSearch</strong>: Referenced sites are used to retrieve the
+ enhancements of a content item. Stanbol Enhancer handles all
+ enhancement operations through the referenced sites. This interface
+ makes use of the referenced sites to look for similar keywords,
+ given a keyword.</li>
+<li><strong>WordnetSearch</strong>: If a Wordnet database is registered to the system
+ (through the OSGi console), this service is ready for use. Looks for
+ several relations among keywords (such as synonyms, hyponyms etc...)
+ and retrieves a list of related keywords from the Wordnet database.</li>
+</ul>
+<p>Following command will retrieve related keywords about "turkey" from referenced sites and wordnet (ReferencedSiteSearch and WordnetSearch). Since no ontology is specified, OntologyResourceSearch will not execute.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">GET</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Accept: application/json"</span> <span class="o">\</span>
+ <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/contenthub/co</span><span class="n">ntenthub</span><span class="sr">/search/</span><span class="n">related</span><span class="p">?</span><span class="n">keyword</span><span class="o">=</span><span class="n">turkey</span>
+</pre></div>
+
+
+<p>If URI of an ontology is also specified with the keyword as follows, result of the service will include related keywords found through the specified ontology in addition to referenced site and wordnet data. Following command will add the related keywords of "turkey" which are retrieved from the ontology identified with "uri-dummy" to the search result of related keyword service.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">GET</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Accept: application/json"</span> <span class="o">\</span>
+ <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/contenthub/co</span><span class="n">ntenthub</span><span class="sr">/search/</span><span class="n">related</span><span class="p">?</span><span class="n">keyword</span><span class="o">=</span><span class="n">turkey</span><span class="o">&</span><span class="n">ontologyURI</span><span class="o">=</span><span class="n">uri</span><span class="o">-</span><span class="n">dummy</span>
+</pre></div>
+
+
+<p>Lastly, Contenthub provides a featured search interface which combines the services of SolrSearch and RelatedKeywordSearch. Results of the services of FeaturedSearch interface includes resultant documents and related keywords of the given query term. Following query will retrieve the documents whose indexed fileds includes the term "turkey" and related keywords from several sources about "turkey".</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">i</span> <span class="o">-</span><span class="n">X</span> <span class="n">GET</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Accept: application/json"</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Content-Type:text/plain"</span> <span class="o">\</span>
+ <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/contenthub/co</span><span class="n">ntenthub</span><span class="sr">/search/</span><span class="n">featured</span><span class="p">?</span><span class="n">queryTerm</span><span class="o">=</span><span class="n">turkey</span>
+</pre></div>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 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>