Author: buildbot
Date: Mon Jul 16 12:51:13 2012
New Revision: 825983
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 16 12:51:13 2012
@@ -1 +1 @@
-1362009
+1362011
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
(original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
Mon Jul 16 12:51:13 2012
@@ -89,10 +89,10 @@
<figcaption>Figure 1: The Apache Stanbol Components</figcaption></p>
<p>Apache Stanbol is built as a modular set of components. Each component is
accessible via its own RESTful web interface. From this viewpoint, all Apache
Stanbol features can be used via RESTful service calls. </p>
<p>Components do not depend on each other. However they can be easily combined
if needed as shown by the different <a href="scenarios.html">Usage
Scenarios</a>. This ensures that the list of used components depend on the
specific usage scenario and not on the Stanbol architecture.</p>
-<p>All components are implemented as <a
href="http://www2.osgi.org/Specifications/HomePage";>OSGi</a> bundles,
components and services. By default Apache Stanbol uses <a
href="http://felix.apache.org";>Apache Felix</a> as OSGI environment. However
generally we try to avoid the use of Felix specific features. If you need to
run Stanbol in an other OSGI environment an encounter problems tell us by
opening a <a href="https://issues.apache.org/jira/browse/STANBOL";>JIRA
issue</a> and/or asking about it on the Stanbol Developer <a
href="mailinglists.html">mailing list</a>.</p>
-<p>For deployment Stanbol uses the <a href="http://sling.apache.org";>Apache
Sling</a> launcher. While the Stanbol Community maintains different launcher
options including run-able JARs and WAR files we expect users to configure
their custom launchers optimized for their usage scenario. However it os also
possible to us Stanbol with other launchers (such as <a
href="http://karaf.apache.org/";>Apache Karaf</a>) or to add its bundles to any
existing OSGI environment.</p>
-<p>Figure 2 depicts the main Apache Stanbol components and their arrangement
within the Apache Stanbol architecture.
-<img alt="Apache Stanbol Components" src="images/stanbol-architecture.png"
title="Apache Stanbol Components" />
+<p>All components are implemented as <a
href="http://www2.osgi.org/Specifications/HomePage";>OSGi</a> bundles,
components and services. By default Apache Stanbol uses <a
href="http://felix.apache.org";>Apache Felix</a> as OSGi environment. However
generally we try to avoid the use of Felix specific features. If you need to
run Stanbol in an other OSGi environment an encounter problems tell us by
opening a <a href="https://issues.apache.org/jira/browse/STANBOL";>JIRA
issue</a> and/or asking about it on the Stanbol Developer <a
href="mailinglists.html">mailing list</a>.</p>
+<p>For deployment Stanbol uses the <a href="http://sling.apache.org";>Apache
Sling</a> launcher. While the Stanbol Community maintains different launcher
options including run-able JARs and WAR files we expect users to configure
their custom launchers optimized for their usage scenario. However it os also
possible to us Stanbol with other launchers (such as <a
href="http://karaf.apache.org/";>Apache Karaf</a>) or to add its bundles to any
existing OSGi environment.</p>
+<p>Figure 2 depicts the main Apache Stanbol components and their arrangement
within the Apache Stanbol architecture.</p>
+<p><img alt="Apache Stanbol Components" src="images/stanbol-architecture.png"
title="Apache Stanbol Components" />
<figcaption>Figure 2: Apache Stanbol Architecture</figcaption></p>
<ul>
<li>
@@ -105,7 +105,7 @@
<p>The 'EnhancerVIE' is a stateful interface to submit content to analyze and
store the results on the server. It is then possible to browse the resulting
enhanced content items.</p>
</li>
<li>
-<p>The <a href="rules.html">Rules</a> component provides you with the means to
re-factor knowledge graphs, e.g. for supporting the schema.org vocabulary for
Search Engine Optimization. </p>
+<p>The <a href="rules.html">Rules</a> component provides you with the means to
refactor knowledge graphs, e.g. for supporting the schema.org vocabulary for
search engine optimization. </p>
</li>
<li>
<p>The <a href="reasoners.html">Reasoners</a> can be used to automatically
infer additional knowledge. It is used to obtain new facts in the knowledge
base, e.g. if your enhanced content tells you about a shop located in
"Montparnasse", you can infer via a "located-in" relation that the same shop is
located in "Paris", in the "Ãle-de-France" and in "France".</p>
