Author: buildbot
Date: Wed Jun 27 11:55:39 2012
New Revision: 823457
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 11:55:39 2012
@@ -1 +1 @@
-1354424
+1354450
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
11:55:39 2012
@@ -82,30 +82,30 @@
</div>
<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." /></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" /><span></p>
+ <p>Apache Stanbol (currently <a
href="http://incubator.apache.org";>incubating</a>) provides a set of reusable
components for semantic content management. It is important to note that
Stanbol itself is NOT a semantic CMS. It extends existing CMSs with a number of
semantic services.</p>
+<p><img alt="Apache Stanbol - The semantic engine"
src="images/stanbol-semanticengine.png" title="Apache Stanbol brings semantic
technologies to current CMS Systems." /></p>
+<p>While Apache Stanbol was built with CMS in mind it can also be used for
e.g. web applications (tag extraction and suggestions, text completion in
search fields); 'smart' content workflows (using several Stanbol semantic
engines chained together) or email routing based on extracted entities/topics;
etc.</p>
+<p>This document provides an overview of Apache Stanbol in some 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" /><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 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>Extracting information from content is the most common use case for Apache
Stanbol. To achieve this, you use the <a
href="docs/trunk/enhancer/enhancerrest.html">RESTful API</a> of the Stanbol
Enhancer to send your content to Stanbol. The Enhancer now applies its <a
href="doc/trunk/enhancer/engines">Semantic Engines</a> to analyze the content.
Extracted information is represented as RDF and returned in the Response of the
Enhancement Request. For more information about how to use the Stanbol Enhancer
please see this <a href="docs/trunk/contentenhancement.html">Usage
Scenario</a>. </p>
+<p>The enhancements can be used to improve search and navigation. Enhancement
results can also be used to support content editors e.g. by suggesting tags or
by allowing the editor to directly interact with entities mentioned in the
text, as is 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>
<h3 id="customize-enhancement-results">Customize Enhancement Results</h3>
<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>
-<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>
+<p>Different application domains will have different needs for extracting
entities from texts. Because of this Apache Stanbol can be customized with
domain specific data as shown in the right hand figure (taken from life
sciences). </p>
+<p>For doing so you can either use the Stanbol Entityhub to manage your
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 is available in Stanbol you
can not only use it to extract information with the Stanbol Enhancer. You can
also use it 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>
+<li>searching and exploring 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>adding 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>
+<p>The Stanbol Enhancer 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 of the different configuration options. For specific
semantic requirements you can also extend the Stanbol Enhancers by implementing
your own <a href="docs/trunk/enhancer/engines/">Enhancement Engine</a>.</p>
+<h3 id="multilinguality">Multilinguality</h3>
+<p>Apache Stanbol is built with multilinguality support in mind. While many
components support multiple languages users need to be aware that not all
features are available for 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: Add features related to Knowledge Models and Reasoning.
<p style="text-align: center;">
