Author: fchrist
Date: Mon Jul 16 18:43:01 2012
New Revision: 1362187
URL: http://svn.apache.org/viewvc?rev=1362187&view=rev
Log:
STANBOL-692 minor edits
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext?rev=1362187&r1=1362186&r2=1362187&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext
Mon Jul 16 18:43:01 2012
@@ -3,49 +3,89 @@ Title: Apache Stanbol Components
<figcaption>Figure 1: The Apache Stanbol Components</figcaption>
-* Jump to
- * [Enhancer](enhancer/) and [Enhancement Engines](enhancer/engines/)
- * [Entityhub](entityhub/)
- * [Contenthub](contenthub/)
- * [Ontology Manager](ontologymanager/)
- * [Rules](rules/)
- * [Reasoners](reasoner/)
- * [CMS Adapter](cmsadapter/)
- * [FactStore](factstore/)
+* [Enhancer](enhancer/) and [Enhancement Engines](enhancer/engines/)
+* [Entityhub](entityhub/)
+* [Contenthub](contenthub/)
+* [Ontology Manager](ontologymanager/)
+* [Rules](rules/)
+* [Reasoners](reasoner/)
+* [CMS Adapter](cmsadapter/)
+* [FactStore](factstore/)
+
+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.
+
+Components do not depend on each other. However they can be easily combined if
+needed as shown by the different [usage scenarios](scenarios.html). This
+ensures that the list of used components depend on the specific usage scenario
+and not on the Apache Stanbol architecture.
+
+All components are implemented as
+[OSGi](http://www2.osgi.org/Specifications/HomePage) bundles, components and
+services. By default Apache Stanbol uses the
+[Apache Felix](http://felix.apache.org) 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 [JIRA
+issue](https://issues.apache.org/jira/browse/STANBOL) and/or asking about it
+on the Stanbol Developer [mailing list](mailinglists.html).
+
+For deployment Stanbol uses the [Apache Sling](http://sling.apache.org)
+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
+[Apache Karaf](http://karaf.apache.org/)) or to add its bundles to any
existing OSGi
+environment.
-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.
-
-Components do not depend on each other. However they can be easily combined if
needed as shown by the different [usage scenarios](scenarios.html). This
ensures that the list of used components depend on the specific usage scenario
and not on the Apache Stanbol architecture.
-
-All components are implemented as
[OSGi](http://www2.osgi.org/Specifications/HomePage) bundles, components and
services. By default Apache Stanbol uses [Apache
Felix](http://felix.apache.org) 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 [JIRA
issue](https://issues.apache.org/jira/browse/STANBOL) and/or asking about it on
the Stanbol Developer [mailing list](mailinglists.html).
-
-For deployment Stanbol uses the [Apache Sling](http://sling.apache.org)
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 [Apache Karaf](http://karaf.apache.org/))
or to add its bundles to any existing OSGi environment.
-
-Figure 2 depicts the main Apache Stanbol components and their arrangement
within the Apache Stanbol architecture.
+Figure 2 depicts the main Apache Stanbol components and their arrangement
+within the Apache Stanbol architecture.
<figcaption>Figure 2: Apache Stanbol Architecture</figcaption>
-* The [Enhancer](enhancer/) component together with its [Enhancement
Engines](enhancer/engines/list.html) 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 [Apache Clerezza](http://incubator.apache.org/clerezza).
-
-* The 'Sparql endpoint' gives access to RDF graphs of Apache Stanbol. This
especially includes the graph with all Enhancement Results managed by the
Stanbol [Contenthub](contenthub/).
-
-* 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.
-
-* The [Rules](rules/) component provides you with the means to refactor
knowledge graphs, e.g. for supporting the schema.org vocabulary for search
engine optimization.
-
-* The [Reasoner](reasoner/) 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".
-
-* The [Ontology Manager](ontologymanager/) 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.
-
-* The [CMS Adapter](cmsadapter/) CMS Adapter component acts as a bridge
between JCR/CMIS compliant content management systems and the Apache Stanbol.
It can be used to map existing node structures from JCR/CMIS content
repositories to RDF models or vica versa. It also provides services for the
management of content repository items as [Content
Item](enhancer/contentitem.html)s within Contenthub.
-
-* The [Entityhub](entityhub/) is the component, which lets you cache and
manage local indexes of repositories such as dbpedia but also custom data (e.g.
product descriptions, contact data, specialized topic thesauri).
-
-* The [Contenthub](contenthub/) is the component which provides persistent
document store whose back-end is Apache Solr. On top of the store, it enables
semantic indexing facilities during text based document submission
-and semantic search together with faceted search capability on the documents.
-
-* The [FactStore](factstore/) is a component that let's use store relations
between entities identified by their URIs. This relation between two entities
is called a _fact_.
-
------------------------------------------------------------------------------
-_Back to [Documentation](index.html)_
+* The [Enhancer](enhancer/) component together with its [Enhancement
+ Engines](enhancer/engines/list.html) 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 [Apache
Clerezza](http://incubator.apache.org/clerezza).
+* 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 [Contenthub](contenthub/).
+* 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.
+* The [Rules](rules/) component provides you with the means to refactor
+ knowledge graphs, e.g. for supporting the schema.org vocabulary for search
+ engine optimization.
+* The [Reasoner](reasoner/) 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".
+* The [Ontology Manager](ontologymanager/) 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.
+* The [CMS Adapter](cmsadapter/) 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
+ [content items](enhancer/contentitem.html) within the
+ [Contenthub](contenthub/).
+* The [Entityhub](entityhub/) is the component, which lets you cache and
+ manage local indexes of repositories such as DBPedia but also custom data
+ (e.g. product descriptions, contact data, specialized topic thesauri).
+* The [Contenthub](contenthub/) is the component which provides persistent
+ document store whose back-end is Apache Solr. On top of the store, it
+ enables semantic indexing facilities during text based document submission
+ and semantic search together with faceted search capability on the
+ documents.
+* The [FactStore](factstore/) is a component that let's use store relations
+ between entities identified by their URIs. This relation between two
+ entities is called a _fact_.
