Author: buildbot
Date: Tue Jun 26 09:49:17 2012
New Revision: 823249

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/content/   (props changed)
    websites/staging/stanbol/trunk/content/stanbol/index.html

Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jun 26 09:49:17 2012
@@ -1 +1 @@
-1353899
+1353900

Modified: websites/staging/stanbol/trunk/content/stanbol/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/index.html Tue Jun 26 
09:49:17 2012
@@ -82,19 +82,32 @@
   
   <div id="content">
     <h1 class="title">Welcome to Apache Stanbol (incubating)</h1>
-    <p>Apache Stanbol (currently in <a 
href="http://incubator.apache.org";>incubation</a>) is an open source modular 
software stack and reusable set of components for semantic content 
management.</p>
-<p>Apache Stanbol <a href="docs/trunk/components.html">components</a> are 
meant to be accessed over RESTful interfaces to provide semantic services for 
content management. Thus, one application is to extend traditional content 
management systems with (internal or external) semantic services. Additionally, 
Apache Stanbol let's you create new types of content management systems with 
semantics at their core. The current code is written in Java and based on the 
<a href="http://www2.osgi.org/Specifications/HomePage";>OSGi</a> component 
framework.</p>
-<p>Apache Stanbol's main features are:</p>
+    <p>Apache Stanbol (<a href="http://incubator.apache.org";>incubating</a>) 
provides a set of RESTful services that aim to extend traditional content 
management systems with semantic services. bring semantic technologies to  
Content Management Systems. </p>
+<p><img alt="Apache Stanbol - The semantic engine" 
src="images/stanbol-semanticengine.png" title="Apache Stanbol is aimed to bring 
semantic technologies to current CMS Systems." /></p>
+<p>the main <strong>Features</strong> are</p>
+<h3 id="content-enhancement">Content Enhancement</h3>
+<p><span style="float:right"> <img alt="Content Enhancement with the Stanbol 
Enhancer" src="images/stanbol-feature-enhancer.png" title="Extract semantic 
information from parsed Content" /></span></p>
+<p>The Stanbol Enhancer provides a <a 
href="docs/trunk/enhancer/enhancerrest.html">RESTful API</a> that allows to <a 
href="docs/trunk/contentenhancement.html">extract semantic information</a> from 
parsed Content. Results are represented as RDF graph and can be used on the 
front end e.g. to improve <a 
href="docs/trunk/enhancementusage.html#entity-tagging-use-tags-to-relate-you-content-to-persons-places-events">Tagging</a>
 or even <a 
href="docs/trunk/enhancementusage.html#entity-checker-inline-editing-of-content-enhancements">inline
 Content Annotation</a>. In the backend extracted information can be used to 
improve search and content processing workflows.</p>
+<p>In more details the Stanbol Enhancer can enhancer Content in <a 
href="docs/trunk/multilingual.html">multiple languages</a>. It can be 
configured to use <a href="docs/trunk/customvocabulary.html">custom 
vocabularies</a>. This <a href="docs/trunk/enhancer/engines/list.html">List of 
Enhancement Engines</a> provides a good overview about the different option. 
However users with special needs can also extend the Stanbol Enhancers by 
implementing their own <a href="docs/trunk/enhancer/engines/">Enhancement 
Engine</a>.</p>
+<h3 id="manage-your-domain-data">Manage your Domain Data</h3>
+<p><span style="float:right"> <img alt="Entity Management with the Stanbol 
Entityhub" src="images/stanbol-feature-entityhub.png" title="Manage your 
Vocabulary and fast local caches of Linked Data sets with the Stanbol 
Entityhub" /></span></p>
+<p>Information (Data/Knowledge) about relevant Entities are key for any 
semantic System. But those information may come from a variety of source. The 
Stanbol Entityhub provides tools and services that allow you and the other 
Stanbol components to access those data via  RESTful services.</p>
+<p>The Entityhub allows you to create/manage your own local Entities. It also 
provides a tool for <a href="docs/trunk/customvocabulary.html">create local 
indexes</a> of datasets. This is important for supporting fast local queries as 
required by the Stanbol Enhancer. The Entityhub can also reference and cache 
remotely hosted datasets. It directly supports <a 
href="http://linkeddata.org";>Linked Data</a> protocols but can also be extended 
to work with services that use special protocols and formats.</p>
+<p>The Apache Entityhub also implements the <a 
href="http://code.google.com/p/google-refine/";>Google Refine</a> <a 
href="http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi";>Reconciliation
 API</a>. Google Refine is a powerful tool for working with messy data. The 
reconciliation step allows to link those data with information of other data 
sets - similar to the Stanbol Enhancer suggesting links within parsed 
content.</p>
+<h3 id="knowledge-models-and-reasoning">Knowledge Models and Reasoning</h3>
+<p><span style="float:right"> <img alt="Knowledge Models, Reasoning and Rule 
support in Apache Stanbol" src="images/stanbol-feature-ont-reason-rules.png" 
title="Define your Knowledge Models and use it for Reasoning and Rule based 
transformation of your Data" /></span></p>
+<p>TODO: Services that are used to define and manipulate the data models (e.g. 
ontologies) that are used to store the semantic information.</p>
+<h3 id="semantic-indexing-and-search">Semantic Indexing and Search</h3>
+<p><span style="float:right"> <img alt="Semantic Indexing and Search with the 
Stanbol Contenthub" src="images/stanbol-feature-entityhub.png" title="Manage a 
customize semantic index over your Documents with the Stanbol Contenthub" 
/></span></p>
+<p>TODO: Services that store (or cache) semantic information, i.e. enhanced 
content, entities, facts, and make it searchable</p>
+<h3 id="used-technologies">Used Technologies</h3>
 <ul>
-<li><strong><a href="docs/trunk/enhancer">Content Enhancement</a></strong><br>
-  Services that add semantic information to “non-semantic” pieces of 
content.</li>
-<li><strong><a href="docs/trunk/reasoners.html">Reasoning</a></strong><br>
-  Services that are able to retrieve additional semantic information about the 
content based on the semantic information retrieved via content 
enhancement.</li>
-<li><strong><a href="docs/trunk/ontologymanager">Knowledge 
Models</a></strong><br>
-  Services that are used to define and manipulate the data models (e.g. 
ontologies) that are used to store the semantic information.</li>
-<li><strong><a href="docs/trunk/contenthub">Persistence</a></strong><br>
-  Services that store (or cache) semantic information, i.e. enhanced content, 
entities, facts, and make it searchable.</li>
+<li>Features provided as <strong>RESTful Services* returning results as 
</strong><a href="http://www.w3.org/RDF/";>RDF</a><strong>(Resource Description 
Language) and <a href="http://www.json.org/";>JSON</a>. Stanbol also supports 
the use of </strong><a href="http://json-ld.org/";>JSON-LD</a>**.</li>
+<li>Available as <strong>Standalone application</strong> (runable Jar) or 
<strong>Web Archive</strong>(WAR file) deployable on any Servlet Container such 
as Apache Tomcat.</li>
+<li>Written in <strong>Java</strong> based on <strong><a 
href="http://www2.osgi.org/Specifications/HomePage";>OSGi</a></strong> as 
component framework</li>
+<li>Implemented using frameworks such as <a 
href="http://lucene.apache.org/solr/";>Apache Solr</a> - for semantic search; <a 
href="http://tika.apache.org/";>Apache Tika</a> - for plain text and metadata 
extraction; <a href="http://opennlp.apache.org/";>Apache OpenNLP</a> - for 
natural language processing; <a 
href="http://incubator.apache.org/clerezza/";>Apache Clerezza</a> and <a 
href="http://jena.apache.org/";>Apache Jena</a> - as RDF framework and Storage; 
<a href="http://felix.apache.org";>Apache Felix</a> as default OSGI framework 
and <a href="http://sling.apache.org";>Apache Sling</a> for deployment.</li>
 </ul>
+<p>Apache Stanbol <a href="docs/trunk/components.html">components</a> are 
meant to be accessed over RESTful interfaces to provide semantic services for 
content management. Thus, one application is to extend traditional content 
management systems with (internal or external) semantic services. Additionally, 
Apache Stanbol let's you create new types of content management systems with 
semantics at their core. The current code is written in Java and based on the 
<a href="http://www2.osgi.org/Specifications/HomePage";>OSGi</a> component 
framework.</p>
 <p>Apache Stanbol features provide the basics to create content management 
systems with semantically advanced user interfaces. Those user interfaces 
benefit from the semantic information that can be handled by Apache Stanbol. 
See the <a href="docs/trunk/">documentation</a> pages for more details.</p>
 <hr />
 <p>The Apache Stanbol project was initiated by the European R&amp;D project <a 
href="http://www.iks-project.eu";>IKS</a> - Interactive Knowledge Stack for 
small to medium CMS providers. Some people who are working on the project are 
part-funded by the IKS project, as well as by several European SME CMS 
providers, who are <a 
href="http://wiki.iks-project.eu/index.php/Participants";>adopting Apache 
Stanbol</a>. </p>


Reply via email to