svn commit: r823433 - in /websites/staging/stanbol/trunk/content: ./ stanbol/docs/trunk/components.html

[bu...@apache.org]

Author: buildbot
Date: Wed Jun 27 08:00:26 2012
New Revision: 823433

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 Wed Jun 27 08:00:26 2012
@@ -1 +1 @@
-1354355
+1354356

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 Wed Jun 27 08:00:26 2012
@@ -82,9 +82,8 @@
   </div>
   <div id="content">
     <h1 class="title">Apache Stanbol Components</h1>
-    <p style="text-align: center;">![Apache Stanbol Components](images/stanbol-components.png "Overview on the different Components included by Apache Stanbol")
+    <p><img alt="Apache Stanbol Components" src="images/stanbol-components.png" title="Overview on the different Components included by Apache Stanbol" />
 <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>