Author: buildbot
Date: Wed Jan 11 15:26:59 2012
New Revision: 802378
Log:
Staging update by buildbot
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/scenarios.html
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/scenarios.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/scenarios.html
(original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/scenarios.html
Wed Jan 11 15:26:59 2012
@@ -51,15 +51,15 @@
<div id="content">
<h1 class="title">Usage Scenarios for Apache Stanbol</h1>
- <p>Apache Stanbol was designed to bring semantic technologies to existing
content management systems. If you have a content management system and you
want to start using semantic technologies in combination with your content,
Apache Stanbol is a good software candidate for you. To make the integration as
easy and painless as possible all Apache Stanbol features are accessible via
RESTful web services. All you need is to connect your content management system
via HTTP to an instance of Apache Stanbol. Additionally, Apache Stanbol comes
with a <a href="cmsadapter.html">CMS Adapter</a> as a bridge between a CMIS/JCR
compliant content repositories and the semantic metadata repository in Apache
Stanbol.</p>
+ <p>Apache Stanbol is designed to bring semantic technologies to existing
content management systems (CMS). If you have a CMS and you want to start using
semantic technologies in combination with your content, Apache Stanbol is a
good software candidate for you. To make the integration as easy and painless
as possible all Apache Stanbol features are accessible via RESTful web
services. All you need is to connect your CMS via HTTP to an instance of Apache
Stanbol. Additionally, Apache Stanbol comes with a <a
href="cmsadapter.html">CMS Adapter</a> component as a bridge between a CMIS/JCR
compliant content repositories and the semantic metadata repository in Apache
Stanbol. Figure 1 gives you an overview of using Apache Stanbol from a CMS.</p>
<p><figure>
<img alt="Traditional CMS using Apache Stanbol"
src="../../images/stanbol-cms-scenario.png" />
-<figcaption>Figure 1: Traditional CMS using Apache Stanbol via HTTP RESTful
interface</figcaption>
+<figcaption>Figure 1: Traditional CMS using Apache Stanbol via its HTTP
RESTful interface.</figcaption>
</figure></p>
-<p>The following usage scenarios explain in more details how to use various
services from a content management system.</p>
+<p>The following usage scenarios explain in more details how to use various
services from a CMS.</p>
<ul>
<li>
-<p><a href="contentenhancement.html">Basic Content Enhancement</a>: Analyze
textual content, enhance with with named entities (person, place,
organization), suggest links to open data sources.</p>
+<p><a href="contentenhancement.html">Basic Content Enhancement</a>: Analyze
textual content, enhance with it with named entities (person, place,
organization), suggest links to open data sources.</p>
</li>
<li>
<p><a href="customvocabulary.html">Working with "local" Entities</a>: Use
locally defined entities (e.g. thesaurus concepts) from an organization's
context.</p>
