Author: rwesten
Date: Wed Jun 27 10:47:25 2012
New Revision: 1354413
URL: http://svn.apache.org/viewvc?rev=1354413&view=rev
Log:
overview on Stanbol is now more usage case oriented
Modified:
incubator/stanbol/site/trunk/content/stanbol/overview.mdtext
Modified: incubator/stanbol/site/trunk/content/stanbol/overview.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/overview.mdtext?rev=1354413&r1=1354412&r2=1354413&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/overview.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/overview.mdtext Wed Jun 27
10:47:25 2012
@@ -3,34 +3,45 @@ Title: Overview about Apache Stanbol (in
Apache Stanbol (currently in [incubating](http://incubator.apache.org))
provides a set of reusable components for semantic content management. For
users it is important to note that Stanbol is NOT a semantic CMS by it own. It
is designed to provide semantic services for existing content management.
-<figcaption>Figure 1: Apache Stanbol is aimed to bring semantic technologies
to current CMS Systems. </figcaption>
However while Apache Stanbol was build with CMS in mind it can also be used in
different usage scenarios including: Direct usage from web applications (e.g.
for Tag extraction/suggestion; or text completion in search fields), 'smart'
Content workflows or email routing based on extracted Entities/Topics, ...
The remaining part of this Document provides an overview about Apache Stanbol
by means of describing typical usage scenarios.
-<span style="float:right"> <figcaption>Figure 1: The Apache Stanbol
Components</figcaption><span>
+<span style="float:right"> <span>
### Content Enhancement
Extracting information of parsed content is the most common use case forApache
Stanbol. For that users need to use the [RESTful
API](docs/trunk/enhancer/enhancerrest.html) of the Stanbol Enhancer to send
their Content to Stanbol. The Enhancer that uses its [Semantic
Engines](doc/trunk/enhancer/engines) to analyze the parsed Content. Extracted
information are represented as RDF and returned in the Response of the
Enhancement Request. For more Information about how to use the Stanbol Enhancer
for Enhancing your Content please see this [Usage
Scenario](docs/trunk/contentenhancement.html).
-This service is intended to be used by Content Management Systems to extract
information from managed content. Those information can than be used to improve
search and navigation. However Enhancement Results can be also used to support
users while during content Editing e.g. by suggesting mentioned entities as
Tags or by allowing them to directly interact with mentions within the text as
shown by the next figure.
+This service is intended to be used by Content Management Systems to extract
information from managed content. Those information can than be used to improve
search and navigation. However Enhancement Results can be also used to support
Content Editors e.g. by suggesting Tags or by allowing them to directly
interact with Entities mentioned in the Text as shown in the following figure.
-Results are represented as RDF graph and can be used on the front end e.g. to
improve
[Tagging](docs/trunk/enhancementusage.html#entity-tagging-use-tags-to-relate-you-content-to-persons-places-events)
or even [inline Content
Annotation](docs/trunk/enhancementusage.html#entity-checker-inline-editing-of-content-enhancements).
In the backend extracted information can be used to improve search and content
processing workflows.
+
+<figcaption>Example showing inline Content Editing with
[VIE](http://viejs.org/) and the
[annotate.js](http://szabyg.github.com/annotate.js) widget integrated in the
[Hallo](http://hallojs.org/) editor.</figcaption>
-In more details the Stanbol Enhancer can enhancer Content in [multiple
languages](docs/trunk/multilingual.html). It can be configured to use [custom
vocabularies](docs/trunk/customvocabulary.html). This [List of Enhancement
Engines](docs/trunk/enhancer/engines/list.html) provides a good overview about
the different option. However users with special needs can also extend the
Stanbol Enhancers by implementing their own [Enhancement
Engine](docs/trunk/enhancer/engines/).
+Detailed information on how to make use of the enhancement results returned by
the Stanbol Enhancer are described in this [usage
scenario](docs/trunk/enhancementusage.html).
-### Manage your Domain Data
+<span style="float:right"> <span>
-Information (Data/Knowledge) about relevant Entities are key for any semantic
System. But those information may come from a variety of source. The Stanbol
Entityhub provides tools and services that allow you and the other Stanbol
components to access those data via RESTful services.
-<p style="text-align: center;">
-
-</p>
+### Customize Enhancement Results
+
+Different Application Domain will need to extract different Entities of the
Text. Because of this Apache Stanbol can be customized with Domain specific
data as shown by the right hand figure for the Life Science domain.
+
+For doing so users can either use the Stanbol Entityhub to manage their
vocabulary or import existing data into the Entityhub. The usage scenario
[Working with Custom Vocabularies](docs/trunk/customvocabulary.html) provides a
detailed description about how to customize Apache Stanbol with application
specific information.
+
+As soon as the application specific information are available in Stanbol you
can not only use it to extract information with the Stanbol Enhancer. They can
be also used for:
+
+* Search and Explore your Domain knowledge using the Apache Entityhub RESTful
services e.g. to get more/related information for Entities extracted by the
Stanbol Enhancer
+* Add auto-completion to your UI by using [VIE](http://viejs.org/) with the
[autocomplete](http://viejs.org/widgets/autocomplete/) widget
+* Using the Stanbol Entityhub together with [Google
Refine](http://code.google.com/p/google-refine/) to clean-up and
[reconcile](http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi)
your data.
+
+
+In more details the Stanbol Enhancer can enhancer Content in . It can be
configured to use [custom vocabularies](docs/trunk/customvocabulary.html). This
[List of Enhancement Engines](docs/trunk/enhancer/engines/list.html) provides a
good overview about the different option. However users with special needs can
also extend the Stanbol Enhancers by implementing their own [Enhancement
Engine](docs/trunk/enhancer/engines/).
+
+### Multi Linguality
-The Entityhub allows you to create/manage your own local Entities. It also
provides a tool for [create local indexes](docs/trunk/customvocabulary.html) of
datasets. This is important for supporting fast local queries as required by
the Stanbol Enhancer. The Entityhub can also reference and cache remotely
hosted datasets. It directly supports [Linked Data](http://linkeddata.org)
protocols but can also be extended to work with services that use special
protocols and formats.
+Apache Stanbol is built with multi lingually in mind. All components do
support multi lingually however user need to be aware the not all features are
available in all languages. Especially the Stanbol Enhancer depends on the
availability of Natural Language Processing (NLP) functionality for given
languages. Also the linking to Entities requires users to provide language
specific labels. For detailed information please see the usage scenario about
[Working with Multiple Languages]([multiple
languages](docs/trunk/multilingual.html).
-The Apache Entityhub also implements the [Google
Refine](http://code.google.com/p/google-refine/) [Reconciliation
API](http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi).
Google Refine is a powerful tool for working with messy data. The
reconciliation step allows to link those data with information of other data
sets - similar to the Stanbol Enhancer suggesting links within parsed content.
### Knowledge Models and Reasoning
