Author: wernher
Date: Wed Jun 27 11:55:33 2012
New Revision: 1354450
URL: http://svn.apache.org/viewvc?rev=1354450&view=rev
Log:
revised the English (jp, wb)
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=1354450&r1=1354449&r2=1354450&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/overview.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/overview.mdtext Wed Jun 27
11:55:33 2012
@@ -1,20 +1,20 @@
Title: Overview about Apache Stanbol (incubating)
-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.
+Apache Stanbol (currently [incubating](http://incubator.apache.org)) 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.
-
+
-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, ...
+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.
-The remaining part of this Document provides an overview about Apache Stanbol
by means of describing typical usage scenarios.
+This document provides an overview of Apache Stanbol in some typical usage
scenarios.
-<span style="float:right"> <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).
+Extracting information from content is the most common use case for Apache
Stanbol. To achieve this, you use the [RESTful
API](docs/trunk/enhancer/enhancerrest.html) of the Stanbol Enhancer to send
your content to Stanbol. The Enhancer now applies its [Semantic
Engines](doc/trunk/enhancer/engines) 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 [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
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.
+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.
<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>
@@ -25,22 +25,22 @@ Detailed information on how to make use
<span style="float:right"> <span>
-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.
+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).
-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.
+For doing so you can either use the Stanbol Entityhub to manage your
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:
+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:
-* 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.
+* 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
+* adding 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/).
+The Stanbol Enhancer 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 of the
different configuration options. For specific semantic requirements you can
also extend the Stanbol Enhancers by implementing your own [Enhancement
Engine](docs/trunk/enhancer/engines/).
-### Multi Linguality
+### Multilinguality
-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).
+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]([multiple
languages](docs/trunk/multilingual.html).
### Knowledge Models and Reasoning
