Author: rwesten
Date: Wed Oct 16 10:18:06 2013
New Revision: 1532706
URL: http://svn.apache.org/r1532706
Log:
Applied patch provided by Bruno P. Kinoshita for STANBOL-1175
Modified:
stanbol/site/trunk/content/docs/trunk/components/enhancer/index.mdtext
stanbol/site/trunk/content/docs/trunk/contentenhancement.mdtext
stanbol/site/trunk/content/docs/trunk/production-mode/index.mdtext
Modified: stanbol/site/trunk/content/docs/trunk/components/enhancer/index.mdtext
URL:
http://svn.apache.org/viewvc/stanbol/site/trunk/content/docs/trunk/components/enhancer/index.mdtext?rev=1532706&r1=1532705&r2=1532706&view=diff
==============================================================================
--- stanbol/site/trunk/content/docs/trunk/components/enhancer/index.mdtext
(original)
+++ stanbol/site/trunk/content/docs/trunk/components/enhancer/index.mdtext Wed
Oct 16 10:18:06 2013
@@ -9,7 +9,7 @@ The Apache Stanbol Enhancer provides bot
* [Enhancement Structure](#Enhancement_Structure)
* [List of Available Enhancement Engines](#List_of_Engines)
-Reader should note that this is the technical documentation of the Stanbol
Enhancer intended for Developer. For more practical - usage case oriented -
introduction to the Stanbol Enhancer as well as other components place have
look at the available [Usage Scenarios](../scenarios.html).
+Reader should note that this is the technical documentation of the Stanbol
Enhancer intended for Developer. For more practical - usage case oriented -
introduction to the Stanbol Enhancer as well as other components please have
look at the available [Usage Scenarios](../scenarios.html).
<a name="Using_Stanbol_Enhancer"></a>
## Using the Stanbol Enhancer
@@ -20,7 +20,7 @@ The figure below provides an overview of
<a name="RESTful_API"></a>
### RESTful API
-The content to be analyzed should be sent in a POST request with the mime-type
specified in the Content-type header. The parsed content is than processed by
the targeted [Enhancement Chain](chains). The response will hold the RDF
enhancement serialized in the format specified in the Accept header. The
following figure visualizes this process.
+The content to be analyzed should be sent in a POST request with the mime-type
specified in the Content-type header. The parsed content is then processed by
the targeted [Enhancement Chain](chains). The response will hold the RDF
enhancement serialized in the format specified in the Accept header. The
following figure visualizes this process.
<p style="text-align: center;"></p>
You can test that easily from the command line using the curl command:
Modified: stanbol/site/trunk/content/docs/trunk/contentenhancement.mdtext
URL:
http://svn.apache.org/viewvc/stanbol/site/trunk/content/docs/trunk/contentenhancement.mdtext?rev=1532706&r1=1532705&r2=1532706&view=diff
==============================================================================
--- stanbol/site/trunk/content/docs/trunk/contentenhancement.mdtext (original)
+++ stanbol/site/trunk/content/docs/trunk/contentenhancement.mdtext Wed Oct 16
10:18:06 2013
@@ -57,7 +57,7 @@ And here is another enhancement chain us
* [tika](components/enhancer/engines/tikaengine.html) - assuming we want to
send MS Word dokuments to Zemanta
* [zemanta](components/enhancer/engines/zemantaengine.html) - this wraps
[Zemanta.com/](http://www.zemanta.com/) as an Apache Stanbol Enhancement Engine
-_Tips for configuring enhancment chains:_
+_Tips for configuring enhancement chains:_
* [http://{host}:{port}/enhancer/chain](http://localhost:8080/enhancer/engine)
provides a list of all configured [Enhancement
Chains](components/enhancer/chains). It also includes direct links to their
configurations.
* As one needs to use the names of active [Enhancement
Engines](components/enhancer/engines) for the configuration of Enhancement
Chains it is very useful to open
[http://{host}:{port}/enhancer/engine](http://localhost:8080/enhancer/engine)
in an other browser window.
Modified: stanbol/site/trunk/content/docs/trunk/production-mode/index.mdtext
URL:
http://svn.apache.org/viewvc/stanbol/site/trunk/content/docs/trunk/production-mode/index.mdtext?rev=1532706&r1=1532705&r2=1532706&view=diff
==============================================================================
--- stanbol/site/trunk/content/docs/trunk/production-mode/index.mdtext
(original)
+++ stanbol/site/trunk/content/docs/trunk/production-mode/index.mdtext Wed Oct
16 10:18:06 2013
@@ -2,7 +2,7 @@ Title: Stanbol in Production Mode
This document provide some informations when running Apache Stanbol in
production mode.
-* [Create your launcher](your-launcher.html): The Apache Stanbol stack does
many things which results in a big launcher when all is included. Comming to
production not all Stanbol features are needed and the requirement to get a
"just what I need" come into play. This document give some pointers to get your
own custom launcher configuration.
+* [Create your launcher](your-launcher.html): The Apache Stanbol stack does
many things which results in a big launcher when all is included. Coming to
production not all Stanbol features are needed and the requirement to get a
"just what I need" come into play. This document give some pointers to get your
own custom launcher configuration.
* [Automatic bundle configuration](file-bundle-configuration.html): Apache
Stanbol is a highly configurable product, thanks to the Apache Felix system
console and the underlying OSGi technology. But how to safely keep this
configuration from old to new versions? How to get a configured server from the
first launch?
