Author: buildbot
Date: Wed Jun 27 10:47:37 2012
New Revision: 823448
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/overview.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jun 27 10:47:37 2012
@@ -1 +1 @@
-1354378
+1354413
Modified: websites/staging/stanbol/trunk/content/stanbol/overview.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/overview.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/overview.html Wed Jun 27
10:47:37 2012
@@ -83,23 +83,29 @@
<div id="content">
<h1 class="title">Overview about Apache Stanbol (incubating)</h1>
<p>Apache Stanbol (currently in <a
href="http://incubator.apache.org";>incubating</a>) 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.</p>
-<p><img alt="Apache Stanbol - The semantic engine"
src="images/stanbol-semanticengine.png" title="Apache Stanbol is aimed to bring
semantic technologies to current CMS Systems." />
-<figcaption>Figure 1: Apache Stanbol is aimed to bring semantic technologies
to current CMS Systems. </figcaption></p>
+<p><img alt="Apache Stanbol - The semantic engine"
src="images/stanbol-semanticengine.png" title="Apache Stanbol is aimed to bring
semantic technologies to current CMS Systems." /></p>
<p>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,
...</p>
<p>The remaining part of this Document provides an overview about Apache
Stanbol by means of describing typical usage scenarios.</p>
-<p><span style="float:right"> <img alt="Content Enhancement with the Stanbol
Enhancer" src="images/stanbol-feature-enhance.png" title="Extract semantic
information from parsed Content" /><figcaption>Figure 1: The Apache Stanbol
Components</figcaption><span></p>
+<p><span style="float:right"> <img alt="Content Enhancement with the Stanbol
Enhancer" src="images/stanbol-feature-enhance.png" title="Extract semantic
information from parsed Content" /><span></p>
<h3 id="content-enhancement">Content Enhancement</h3>
<p>Extracting information of parsed content is the most common use case
forApache Stanbol. For that users need to use the <a
href="docs/trunk/enhancer/enhancerrest.html">RESTful API</a> of the Stanbol
Enhancer to send their Content to Stanbol. The Enhancer that uses its <a
href="doc/trunk/enhancer/engines">Semantic Engines</a> 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 <a
href="docs/trunk/contentenhancement.html">Usage Scenario</a>. </p>
-<p>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.</p>
-<p>Results are represented as RDF graph and can be used on the front end e.g.
to improve <a
href="docs/trunk/enhancementusage.html#entity-tagging-use-tags-to-relate-you-content-to-persons-places-events">Tagging</a>
or even <a
href="docs/trunk/enhancementusage.html#entity-checker-inline-editing-of-content-enhancements">inline
Content Annotation</a>. In the backend extracted information can be used to
improve search and content processing workflows.</p>
-<p>In more details the Stanbol Enhancer can enhancer Content in <a
href="docs/trunk/multilingual.html">multiple languages</a>. It can be
configured to use <a href="docs/trunk/customvocabulary.html">custom
vocabularies</a>. This <a href="docs/trunk/enhancer/engines/list.html">List of
Enhancement Engines</a> provides a good overview about the different option.
However users with special needs can also extend the Stanbol Enhancers by
implementing their own <a href="docs/trunk/enhancer/engines/">Enhancement
Engine</a>.</p>
-<h3 id="manage-your-domain-data">Manage your Domain Data</h3>
-<p>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;">
-<img alt="Entity Management with the Stanbol Entityhub"
src="images/stanbol-feature-entityhub.png" title="Manage your Vocabulary and
fast local caches of Linked Data sets with the Stanbol Entityhub" />
-</p></p>
-<p>The Entityhub allows you to create/manage your own local Entities. It also
provides a tool for <a href="docs/trunk/customvocabulary.html">create local
indexes</a> 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 <a
href="http://linkeddata.org";>Linked Data</a> protocols but can also be extended
to work with services that use special protocols and formats.</p>
-<p>The Apache Entityhub also implements the <a
href="http://code.google.com/p/google-refine/";>Google Refine</a> <a
href="http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi";>Reconciliation
API</a>. 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.</p>
+<p>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.</p>
+<p><img alt="Inline Content Enhancement Example"
src="images/inline-content-enhancements-with-vie-hallo-annodate.png" />
+<figcaption>Example showing inline Content Editing with <a
href="http://viejs.org/";>VIE</a> and the <a
href="http://szabyg.github.com/annotate.js";>annotate.js</a> widget integrated
in the <a href="http://hallojs.org/";>Hallo</a> editor.</figcaption></p>
+<p>Detailed information on how to make use of the enhancement results returned
by the Stanbol Enhancer are described in this <a
href="docs/trunk/enhancementusage.html">usage scenario</a>.</p>
+<p><span style="float:right"> <img alt="Customize Enhancement Results"
src="images/enhancer-custom-vocabularies.png" title="The Stanbol Enhancer
customized to analyze content in the Life Science domain" /><span></p>
+<h3 id="customize-enhancement-results">Customize Enhancement Results</h3>
+<p>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. </p>
+<p>For doing so users can either use the Stanbol Entityhub to manage their
vocabulary or import existing data into the Entityhub. The usage scenario <a
href="docs/trunk/customvocabulary.html">Working with Custom Vocabularies</a>
provides a detailed description about how to customize Apache Stanbol with
application specific information.</p>
+<p>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:</p>
+<ul>
+<li>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</li>
+<li>Add auto-completion to your UI by using <a
href="http://viejs.org/";>VIE</a> with the <a
href="http://viejs.org/widgets/autocomplete/";>autocomplete</a> widget</li>
+<li>Using the Stanbol Entityhub together with <a
href="http://code.google.com/p/google-refine/";>Google Refine</a> to clean-up
and <a
href="http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi";>reconcile</a>
your data.</li>
+</ul>
+<p>In more details the Stanbol Enhancer can enhancer Content in . It can be
configured to use <a href="docs/trunk/customvocabulary.html">custom
vocabularies</a>. This <a href="docs/trunk/enhancer/engines/list.html">List of
Enhancement Engines</a> provides a good overview about the different option.
However users with special needs can also extend the Stanbol Enhancers by
implementing their own <a href="docs/trunk/enhancer/engines/">Enhancement
Engine</a>.</p>
+<h3 id="multi-linguality">Multi Linguality</h3>
+<p>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](<a
href="docs/trunk/multilingual.html">multiple languages</a>.</p>
<h3 id="knowledge-models-and-reasoning">Knowledge Models and Reasoning</h3>
<p>TODO: Services that are used to define and manipulate the data models (e.g.
ontologies) that are used to store the semantic information.
<p style="text-align: center;">
