Author: buildbot
Date: Mon Jul 16 18:43:05 2012
New Revision: 826021
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components/index.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 16 18:43:05 2012
@@ -1 +1 @@
-1362029
+1362187
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components/index.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components/index.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components/index.html
Mon Jul 16 18:43:05 2012
@@ -88,7 +88,6 @@
<p><img alt="Apache Stanbol Components" src="stanbol-components.png"
title="Overview on the different Components included by Apache Stanbol" />
<figcaption>Figure 1: The Apache Stanbol Components</figcaption></p>
<ul>
-<li>Jump to<ul>
<li><a href="enhancer/">Enhancer</a> and <a
href="enhancer/engines/">Enhancement Engines</a></li>
<li><a href="entityhub/">Entityhub</a></li>
<li><a href="contenthub/">Contenthub</a></li>
@@ -98,50 +97,79 @@
<li><a href="cmsadapter/">CMS Adapter</a></li>
<li><a href="factstore/">FactStore</a></li>
</ul>
-</li>
-</ul>
-<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. </p>
-<p>Components do not depend on each other. However they can be easily combined
if needed as shown by the different <a href="scenarios.html">usage
scenarios</a>. This ensures that the list of used components depend on the
specific usage scenario and not on the Apache Stanbol architecture.</p>
-<p>All components are implemented as <a
href="http://www2.osgi.org/Specifications/HomePage";>OSGi</a> bundles,
components and services. By default Apache Stanbol uses <a
href="http://felix.apache.org";>Apache Felix</a> as OSGi environment. However
generally we try to avoid the use of Felix specific features. If you need to
run Stanbol in an other OSGi environment an encounter problems tell us by
opening a <a href="https://issues.apache.org/jira/browse/STANBOL";>JIRA
issue</a> and/or asking about it on the Stanbol Developer <a
href="mailinglists.html">mailing list</a>.</p>
-<p>For deployment Stanbol uses the <a href="http://sling.apache.org";>Apache
Sling</a> launcher. While the Stanbol Community maintains different launcher
options including run-able JARs and WAR files we expect users to configure
their custom launchers optimized for their usage scenario. However it os also
possible to us Stanbol with other launchers (such as <a
href="http://karaf.apache.org/";>Apache Karaf</a>) or to add its bundles to any
existing OSGi environment.</p>
-<p>Figure 2 depicts the main Apache Stanbol components and their arrangement
within the Apache Stanbol architecture.</p>
+<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.</p>
+<p>Components do not depend on each other. However they can be easily combined
if
+needed as shown by the different <a href="scenarios.html">usage scenarios</a>.
This
+ensures that the list of used components depend on the specific usage scenario
+and not on the Apache Stanbol architecture.</p>
+<p>All components are implemented as
+<a href="http://www2.osgi.org/Specifications/HomePage";>OSGi</a> bundles,
components and
+services. By default Apache Stanbol uses the
+<a href="http://felix.apache.org";>Apache Felix</a> OSGi environment. However
generally we try
+to avoid the use of Felix specific features. If you need to run Stanbol in an
+other OSGi environment an encounter problems tell us by opening a <a
href="https://issues.apache.org/jira/browse/STANBOL";>JIRA
+issue</a> and/or asking about it
+on the Stanbol Developer <a href="mailinglists.html">mailing list</a>.</p>
+<p>For deployment Stanbol uses the <a href="http://sling.apache.org";>Apache
Sling</a>
+launcher. While the Stanbol Community maintains different launcher options
+including run-able JARs and WAR files we expect users to configure their
+custom launchers optimized for their usage scenario. However it os also
+possible to us Stanbol with other launchers (such as
+<a href="http://karaf.apache.org/";>Apache Karaf</a>) or to add its bundles to
any existing OSGi
+environment.</p>
+<p>Figure 2 depicts the main Apache Stanbol components and their arrangement
+within the Apache Stanbol architecture.</p>
<p><img alt="Apache Stanbol Components" src="stanbol-architecture.png"
title="Apache Stanbol Components" />
<figcaption>Figure 2: Apache Stanbol Architecture</figcaption></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 RDF graphs of Apache Stanbol. This
especially includes the graph with all Enhancement Results managed by the
Stanbol <a href="contenthub/">Contenthub</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/">Rules</a> component provides you with the means to
refactor knowledge graphs, e.g. for supporting the schema.org vocabulary for
search engine optimization. </p>
-</li>
-<li>
-<p>The <a href="reasoner/">Reasoner</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>
+<li>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>.</li>
+<li>The 'Sparql endpoint' gives access to RDF graphs of Apache Stanbol. This
+ especially includes the graph with all enhancement results managed by the
+ Apache Stanbol <a href="contenthub/">Contenthub</a>.</li>
+<li>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.</li>
+<li>The <a href="rules/">Rules</a> component provides you with the means to
refactor
+ knowledge graphs, e.g. for supporting the schema.org vocabulary for search
+ engine optimization. </li>
+<li>The <a href="reasoner/">Reasoner</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".</li>
+<li>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.</li>
+<li>The <a href="cmsadapter/">CMS Adapter</a> CMS Adapter component acts as a
bridge
+ between JCR/CMIS compliant content management systems and 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 called
+ <a href="enhancer/contentitem.html">content items</a> within the
+ <a href="contenthub/">Contenthub</a>.</li>
+<li>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).</li>
+<li>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.</li>
+<li>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>.</li>
</ul>
-<hr />
-<p><em>Back to <a href="index.html">Documentation</a></em></p>
</div>
<div id="footer">
