You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by bu...@apache.org on 2012/06/26 13:12:20 UTC

svn commit: r823264 - in /websites/staging/stanbol/trunk/content: ./ stanbol/overview.html

Author: buildbot
Date: Tue Jun 26 11:12:20 2012
New Revision: 823264

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 Tue Jun 26 11:12:20 2012
@@ -1 +1 @@
-1353946
+1353949

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 Tue Jun 26 11:12:20 2012
@@ -84,8 +84,7 @@
     <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 style="text-align: center;">
-![Apache Stanbol - The semantic engine](images/stanbol-semanticengine.png "Apache Stanbol is aimed to bring semantic technologies to current CMS Systems.")
-</p>
+![Apache Stanbol - The semantic engine](images/stanbol-semanticengine.png "Apache Stanbol is aimed to bring semantic technologies to current CMS Systems.")</p>
 
 <p>All the features described in the following sections are meant to be accessed over RESTful services. Typically they are use to extend traditional content management systems with semantic services. Other feasible use cases include: 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>
 <h3 id="content-enhancement">Content Enhancement</h3>