Author: fchrist
Date: Fri Jan 13 18:46:30 2012
New Revision: 802572
Log:
Latest changes of the work on STANBOL-447 and STANBOL-448.
Added:
websites/production/stanbol/content/stanbol/docs/trunk/enhancer/STANBOL-414-specification.html
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/STANBOL-414-specification.html
websites/production/stanbol/content/stanbol/docs/trunk/factstore/
- copied from r802571,
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/
websites/production/stanbol/content/stanbol/docs/trunk/factstore/implementation.html
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/implementation.html
websites/production/stanbol/content/stanbol/docs/trunk/factstore/index.html
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/index.html
websites/production/stanbol/content/stanbol/docs/trunk/factstore/specification.html
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/specification.html
websites/production/stanbol/content/stanbol/docs/trunk/rules/refactor.html
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html
websites/production/stanbol/content/stanbol/docs/trunk/rules/store.html
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/store.html
websites/production/stanbol/content/stanbol/images/stanbol-cms-scenario.png
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-cms-scenario.png
websites/production/stanbol/content/stanbol/images/stanbol-cms-scenario.svg
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-cms-scenario.svg
websites/production/stanbol/content/stanbol/images/stanbol-components.png
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-components.png
websites/production/stanbol/content/stanbol/images/stanbol-components.svg
- copied unchanged from r802571,
websites/staging/stanbol/trunk/content/stanbol/images/stanbol-components.svg
Modified:
websites/production/stanbol/ (props changed)
websites/production/stanbol/content/stanbol/docs/trunk/components.html
websites/production/stanbol/content/stanbol/docs/trunk/downloads.html
websites/production/stanbol/content/stanbol/docs/trunk/factstore.html
websites/production/stanbol/content/stanbol/docs/trunk/index.html
websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager.html
websites/production/stanbol/content/stanbol/docs/trunk/rules.html
websites/production/stanbol/content/stanbol/docs/trunk/rules/language.html
websites/production/stanbol/content/stanbol/docs/trunk/scenarios.html
websites/production/stanbol/content/stanbol/index.html
Propchange: websites/production/stanbol/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Fri Jan 13 18:46:30 2012
@@ -1 +1 @@
-/websites/staging/stanbol/trunk:779452-801891
+/websites/staging/stanbol/trunk:779452-802571
Modified: websites/production/stanbol/content/stanbol/docs/trunk/components.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/components.html
(original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/components.html Fri
Jan 13 18:46:30 2012
@@ -20,7 +20,7 @@
-->
<link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
- <title>Apache Stanbol - Apache Stanbol RESTful Services and
Components</title>
+ <title>Apache Stanbol - Apache Stanbol Components</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="icon" type="image/png"
href="/stanbol/images/stanbol-logo/stanbol-favicon.png"/>
</head>
@@ -50,20 +50,23 @@
</div>
<div id="content">
- <h1 class="title">Apache Stanbol RESTful Services and Components</h1>
- <p>This is an overview of the major features of various Stanbol components
and services for analyzing and enhancing your content. The enhancements are
provided via natural language processing, metadata extraction and linking named
entities to public or private entity repositories. Furthermore, Stanbol
provides a machinery to further process this data and add additional knowledge
and links via applying rules and reasoning. Stanbol let you also generate
distinct indexes of content items together with their linked metadata to serve
faceted semantic search.</p>
+ <h1 class="title">Apache Stanbol Components</h1>
+ <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. The components
are implemented as <a
href="http://www2.osgi.org/Specifications/HomePage";>OSGi</a> components based
on <a href="http://felix.apache.org";>Apache Felix</a>.</p>
+<p>This page gives an overview of the major features of various Apache Stanbol
components. The following figure depicts the main Apache Stanbol components and
their arrangement within the Apache Stanbol architecture.</p>
+<p><figure>
+<img alt="Apache Stanbol Components" src="../../images/stanbol-components.png"
/>
+<figcaption>Figure 1: Apache Stanbol Components</figcaption>
+</figure></p>
+<p>We will shortly describe the components from top to bottom and link to
their detailed descriptions.</p>
<ul>
<li>
-<p>The <a href="enhancer.html">Enhancer</a> component together with its <a
href="engines.html">Enhancement Engines</a> provides you with the ability to
post content to Stanbol and get suggestions for possible entity annotation in
return.</p>
+<p>The <a href="enhancer.html">Enhancer</a> component together with its <a
href="engines.html">Enhancement Engines</a> provides you with the ability to
post content to Apache Stanbol and get suggestions for possible entity
annotation in return. The enhancements are provided via natural language
processing, metadata extraction and linking named entities to public or private
entity repositories. Furthermore, Apache Stanbol provides a machinery to
further process this data and add additional knowledge and links via applying
rules and reasoning. Technically, the enhancements are stored in a triple-graph
that is maintained by <a href="http://incubator.apache.org/clerezza";>Apache
Clerezza</a>.</p>
</li>
<li>
-<p>The <a href="entityhub.html">Entityhub</a> is the component, which lets you
cache and manage local indexes of repositories such as dbpedia but also custom
data (e.g. product descriptions, contact data, specialized topic thesauri).</p>
-</li>
-<li>
-<p>The <a href="contenthub.html">Contenthub</a> provides you with an combined
index of your content items together with enhancements to facilitate semantic
search on your entire knowledge base.</p>
+<p>The 'Sparql endpoint' gives access to the semantic enhancements form the
Apache Stanbol <a href="enhancer.html">Enhancer</a>.</p>
</li>
<li>
-<p>The <a href="cmsadapter.html">CMS Adapter</a> can be used to map
(bidirectionally) existing node structures from content repositories (CMIS) to
RDF models.</p>
+<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>
@@ -72,16 +75,19 @@
<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>
</li>
<li>
-<p>The <a href="ontologymanager.html">Ontology Manager</a> is the facility to
manage all your ontologies i.e. the knowledge models you use to describe your
metadata of your content as well as knowledge about the semantics of your
content.</p>
+<p>The <a href="ontologymanager.html">Ontology Manager</a> has the facility to
manage your ontologies. Ontologies are used to define the knowledge models that
describe the content's metadata. Additionally, the semantic of you metadata can
be defined through an ontology.</p>
</li>
<li>
-<p>The <a href="factstore.html">FactStore</a> is a component that let's use
store relations between entities identified by their URIs. This relation
between two entities is called a <em>fact</em>.</p>
+<p>The <a href="cmsadapter.html">CMS Adapter</a> can be used to map
(bidirectionally) existing node structures from content repositories (CMIS) to
RDF models.</p>
</li>
<li>
-<p>The 'Sparql endpoint' gives access to the semantic enhancements form the
Stanbol Enhancer.</p>
+<p>The <a href="entityhub.html">Entityhub</a> is the component, which lets you
cache and manage local indexes of repositories such as dbpedia but also custom
data (e.g. product descriptions, contact data, specialized topic thesauri).</p>
</li>
<li>
-<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>
+<p>The <a href="contenthub.html">Contenthub</a> provides you with a combined
index of your content items together with enhancements to facilitate semantic
search on your entire knowledge base.</p>
+</li>
+<li>
+<p>The <a href="factstore/">FactStore</a> is a component that let's use store
relations between entities identified by their URIs. This relation between two
entities is called a <em>fact</em>.</p>
</li>
</ul>
</div>
Modified: websites/production/stanbol/content/stanbol/docs/trunk/downloads.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/downloads.html
(original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/downloads.html Fri
Jan 13 18:46:30 2012
@@ -51,7 +51,7 @@
<div id="content">
<h1 class="title">Downloads</h1>
- <p>As there is no official release of Apache Stanbol so far, one needs to
install and <a href="/building.html">build the software from source</a>. </p>
+ <p>As there is no official release of Apache Stanbol so far, one needs to
install and build the software from source. </p>
<p>In the meantime, you may download and use pre-builts of Stanbol launchers
served <a
href="http://dev.iks-project.eu/downloads/stanbol-launchers/";>here</a>.</p>
</div>
Modified: websites/production/stanbol/content/stanbol/docs/trunk/factstore.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/factstore.html
(original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/factstore.html Fri
Jan 13 18:46:30 2012
@@ -51,7 +51,7 @@
<div id="content">
<h1 class="title">Factstore</h1>
- <p>The FactStore is a component that let's use store relations between
entities identified by their URIs. A relation between two or more entities is
called a <em>fact</em>. The FactStore let's you store N-ary facts. In
consequence you can store relations between N participating entities.</p>
+ <p>The FactStore is a component that let's use store relations between
entities identified by their URIs. A relation between two or more entities is
called a <em>fact</em>. The FactStore let's you store N-ary facts according to
a user defined fact schema. In consequence you can store relations between N
participating entities.</p>
<h2 id="example">Example</h2>
<p>Imagine you want to store the fact that the person named John Doe works for
the company Winzigweich. John Doe is represented by the URI
http://www.doe.com/john and the company by http://www.winzigweich.de. This fact
is stored as a relation between the entity http://www.doe.com/john and
http://www.winzigweich.de.</p>
<p>For this, we first need to create a so called fact schema that tells the
FactStore what we would like to store. A fact schema has a unique name (often
an URI is used) to identify it. To specify what kinds of entities we would like
to store, we specify the type of the entities. Each type has an URI and should
be defined by some ontology. For example, we can use the ontology specified by
http://schema.org/.</p>
Modified: websites/production/stanbol/content/stanbol/docs/trunk/index.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/index.html (original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/index.html Fri Jan
13 18:46:30 2012
@@ -51,7 +51,7 @@
<div id="content">
<h1 class="title">Documentation</h1>
- <p>This documentation of Apache Stanbol targets at Content Management
System (CMS) developers and integrators, who want to use and integrate Stanbol
RESTful services into their CMS. Secondly, it is for Stanbol contributors,
which are developing Stanbol components and engines.</p>
+ <p>This documentation of Apache Stanbol targets at Content Management
System (CMS) developers and integrators, who want to use and integrate Apache
Stanbol RESTful services into their CMS. Secondly, it is for Apache Stanbol
contributors, which are developing Apache Stanbol components and engines.</p>
<h2 id="documentation_for_cms_developers">Documentation for CMS Developers</h2>
<ul>
<li><a href="scenarios.html">Usage Scenarios</a></li>
@@ -59,8 +59,8 @@
<li><a href="faq.html">FAQ</a></li>
<li>Demos</li>
</ul>
-<p><em>Note</em>: In addition to the documentation on this site, every Stanbol
instance provides you with live documentation when pointing your browser to the
Stanbol start page. It contains further descriptions and the most up-to-date
documenation for each component and its RESTful API. Additional technical notes
for each component can be found within various README files within the <a
href="http://svn.apache.org/repos/asf/incubator/stanbol/trunk/";>source
code</a>.</p>
-<h2 id="documentation_for_stanbol_contributors">Documentation for Stanbol
Contributors</h2>
+<p><em>Note</em>: In addition to the documentation on this site, every Apache
Stanbol instance provides you with live documentation when pointing your
browser to the Apache Stanbol start page. It contains further descriptions and
the most up-to-date documenation for each component and its RESTful API.
Additional technical notes for each component can be found within various
README files within the <a
href="http://svn.apache.org/repos/asf/incubator/stanbol/trunk/";>source
code</a>.</p>
+<h2 id="documentation_for_apache_stanbol_contributors">Documentation for
Apache Stanbol Contributors</h2>
<ul>
<li>Java API for developers</li>
<li>How to contribute to software development</li>
Modified:
websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager.html
(original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager.html
Fri Jan 13 18:46:30 2012
@@ -51,15 +51,25 @@
<div id="content">
<h1 class="title">Ontology Manager</h1>
- <p>The Stanbol Ontology Manager provides a controlled environment for
managing ontologies, ontology networks and user sessions for semantic data
modeled after them. It provides full access to ontologies stored into the
Stanbol persistence layer.</p>
+ <p>The Stanbol Ontology Manager provides a <strong>controlled
environment</strong> for managing ontologies, <strong>ontology
networks</strong> and user sessions for semantic data modeled after them. It
provides full access to ontologies stored into the Stanbol persistence layer.
Managing an ontology network means that you can activate or deactivate parts of
a complex model from time to time, so that your data can be viewed and
classified under different "logical lenses". This is especially
useful in <a href="reasoners.html">Reasoning</a> operations.</p>
+<h2 id="usage_scenarios">Usage Scenarios</h2>
+<h3 id="user_networks">User networks</h3>
+<p>In your CMS, you might be interested in figuring out the trust and
acquaintance network of its users. This can be a combination of the
<em>asserted</em> network (i.e. what other users are included in the contact or
friend list of a given user) with the <em>inferred</em> network (e.g. exclude
those who are in the contact list of a blacklisted user). The latter can be
derived from the user activities over the user-generated content of your CMS
(e.g. blogs posts, forum posts, reviews, tweets, ratings). </p>
+<p>Both types of networks can be modelled as ontologies. Models can be build
on the <em>class</em> level, or <em>TBox</em> (e.g. everyone who is an
Administrator is also a User, and collaborates with every other Administrator
of the same system) and on the <em>instance</em> level, or <em>ABox</em> (e.g.
John is a friend of Mary, who created blog post bp345263 on 3/10/2012 at
15:10). These models can all be stored using the Store facility of the Ontology
Manager.</p>
+<p>Using a <a href="reasoners.html">reasoner</a> you can classify all the
knowledge loaded on Stanbol, but this can be a time-consuming process due to
classifying knowledge we are not interested in for this task. <a
href="ontologymanager/ontonet.html">OntoNet</a> allows you to select only the
"interesting" parts of your knowledge base. For example, if the
knowledge contains classifications of animal species, you may want to
deactivate that model when reasoning on user networks. Likewise, you may want
to consider the user profiles <em>today</em>, rather than who was a user's
friend five years ago. Therefore, on the instance level you will exclude the
profile history and only consider today's snapshot.</p>
+<h3 id="knowledge_within_content">Knowledge within content</h3>
+<h2 id="features">Features</h2>
+<p>A Web <strong>Ontology</strong> in computer and information science is a
shareable conceptual model of a part of the world <a href="#ref1">[1]</a>. This
model describes concepts terms of their characteristics and their relations
with other concepts.</p>
<h3 id="sub-components">Sub-Components</h3>
<ul>
<li><a href="ontologymanager/ontonet.html">OntoNet</a> - allows to
construct subsets of the knowledge base managed by Stanbol into OWL/OWL2
ontology networks</li>
<li><a href="ontologymanager/registry.html">Registry</a> - manages ontology
libraries for bootstrapping the network using both external and internal
ontologies</li>
<li>Store - create, read, update and delete operations on single
ontologies stored in Stanbol. These operations can be performed on entities,
axioms, and whole ontologies.</li>
</ul>
-<h2 id="examples">Examples</h2>
-<p>TODO</p>
+<h2 id="references">References:</h2>
+<ul>
+<li>[1] <a name="ref1"
href="http://tomgruber.org/writing/ontolingua-kaj-1993.pdf";
target="_blank">Ontologies (PDF)</a></li></li>
+</ul>
</div>
<div id="footer">
Modified: websites/production/stanbol/content/stanbol/docs/trunk/rules.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/rules.html (original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/rules.html Fri Jan
13 18:46:30 2012
@@ -53,29 +53,11 @@
<h1 class="title">Rules</h1>
<p>Stanbol Rules is a component that supports the construction and
execution of inference rules. An <strong>inference rule</strong>, or
transformation rule, is a syntactic rule or function which takes premises and
returns a conclusion. Stanbol Rules allows to add a layer for expressing
business logics by means of axioms, which encode the inference rules. These
axioms can be organized into a container called <strong>recipe</strong>, which
identifies a set of rules that share the same business logic and interpret them
as a whole.</p>
<p>For instance, with Stanbol Rules the administrator can define integrity
checks for data fetched from heterogeneous and external sources in order to
prevent unwanted formats or inconsistent data. Also, Stanbol Rules can be used
to derive new knowledge or integrate information from different semantically
enhanced contents.</p>
-<h2 id="rule_language">Rule Language</h2>
-<p>Rules are written in the <a href="rules/language.html">Stanbol Rule</a>
language and can be interpreted either as SWRL rules (for classical Description
Logic reasoning) or SPARQL CONSTRUCT queries (for RDF querying and
transformation).</p>
-<h2 id="service_endpoints">Service Endpoints</h2>
-<p>The Rules RESTful API is structured as follows:
-<em>(Please note, that the following links to the actual service endpoint link
to a running instance of Apache Stanbol. If you use other domains or ports than
"localhost:8080", then please change accordingly)</em></p>
-<h3 id="rule_manager_rulesrule">Rule Manager ("/rules/rule"):</h3>
+<h3 id="sub-components">Sub-Components</h3>
<ul>
-<li>The Rule Manager @ <a
href="http://localhost:8080/rules/rule";>/rules/rule</a> allows to manage and
retrieve inference rules.</li>
-</ul>
-<h3 id="recipe_manager_rulesrecipe">Recipe Manager ("/rules/recipe"):</h3>
-<ul>
-<li>The Recipe Manager @ <a
href="http://localhost:8080/rules/rule";>/rules/rule</a> allows to manage, store
and retrieve pre-defined rule sequences, or <strong>recipes</strong>.</li>
-</ul>
-<h3 id="refactorer_rulesrefactor">Refactorer ("/rules/refactor"):</h3>
-<ul>
-<li>
-<p>The Refactorer @ <a
href="http://localhost:8080/rules/refactor";>/rules/refactor</a> applies a
recipe to a supplied RDF graph, in order to return a new graph containing the
output of the recipe execution.</p>
-</li>
-<li>
-<p><a
href="http://localhost:8080/rules/refactor";><strong>Refactor</strong></a>
refactors the input RDF graph using a recipe already stored in Stanbol.</p>
-</li>
-<li>
-<p><a
href="http://localhost:8080/rules/refactor/apply";><strong>Apply</strong></a>
refactors the input RDF graph using a recipe provided on the fly.</p>
+<li><a href="rules/language.html">Rule language</a> - specifies the syntax
used in Stanbol in order to represent rules. Stanbol rules can be as SWRL, Jema
rules or SPARQL CONSTRUCT</li>
+<li><a href="rules/store.html">Rule Store</a> - allows to rules
persistence. Rules in set called <strong>recipies</strong>, which are designed
to aggregate rules by their functionality</li>
+<li><a href="rules/refactor.html">Refactor</a> - performs RDF graphs
transformations to specific target vocabularies or ontologies by means of
rules. This allows the harmonization and the alignment of RDF graphs expressed
with different vocabularies, e.g., DBpedia, schema.org etc... <br />
</li>
</ul>
<hr />
Modified:
websites/production/stanbol/content/stanbol/docs/trunk/rules/language.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/rules/language.html
(original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/rules/language.html
Fri Jan 13 18:46:30 2012
@@ -93,7 +93,7 @@
<p>or the following <strong>SPARQL CONSTRUCT</strong> statement:</p>
<div class="codehilite"><pre><span class="n">PREFIX</span> <span
class="n">myont:</span> <span
class="sr"><http://www.foo.org/myont.owl#></span>
-<span class="n">CONSTRUCT</span> <span class="p">{</span> <span
class="p">?</span><span class="n">x</span> <span
class="n">myont:hasUncle</span><span class="p">}</span> <span
class="p">?</span><span class="n">y</span> <span class="p">}</span>
+<span class="n">CONSTRUCT</span> <span class="p">{</span> <span
class="p">?</span><span class="n">x</span> <span
class="n">myont:hasUncle</span> <span class="p">?</span><span
class="n">y</span> <span class="p">}</span>
<span class="n">WHERE</span> <span class="p">{</span> <span
class="p">?</span><span class="n">x</span> <span
class="n">myont:hasParent</span> <span class="p">?</span><span
class="n">z</span> <span class="o">.</span>
<span class="p">?</span><span class="n">z</span> <span
class="n">myont:hasSibling</span> <span class="p">?</span><span
class="n">y</span><span class="p">}</span>
</pre></div>
Modified: websites/production/stanbol/content/stanbol/docs/trunk/scenarios.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/scenarios.html
(original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/scenarios.html Fri
Jan 13 18:46:30 2012
@@ -51,10 +51,15 @@
<div id="content">
<h1 class="title">Usage Scenarios for Apache Stanbol</h1>
- <p>The following usage scenarios explain how to use various components and
services together with content management systems.</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 its HTTP
RESTful interface.</figcaption>
+</figure></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>
Modified: websites/production/stanbol/content/stanbol/index.html
==============================================================================
--- websites/production/stanbol/content/stanbol/index.html (original)
+++ websites/production/stanbol/content/stanbol/index.html Fri Jan 13 18:46:30
2012
@@ -51,37 +51,37 @@
<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 components are meant to be accessed over RESTful interfaces
to provide semantic services for content management. The current code is
written in Java and based on the OSGi modularization framework.</p>
-<p>Applications include extending existing content management systems with
(internal or external) semantic services, and creating new types of content
management systems with semantics at their core. Its main features will
include:</p>
+ <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>
<ul>
-<li>Persistence: services that store (or cache) semantic information and make
it searchable</li>
-<li>Lifting/Enhancement: services that add semantic information to
ânon-semanticâ pieces of content</li>
-<li>Knowledge models and reasoning: services that enhance the semantic
information</li>
-<li>Interaction: intelligent user interface management and generation </li>
+<li><strong>Content Enhancement</strong><br>
+ Services that add semantic information to ânon-semanticâ pieces of
content.</li>
+<li><strong>Reasoning</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>Knowledge Models</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>Persistence</strong><br>
+ Services that store (or cache) semantic information, i.e. enhanced content,
entities, facts, and make it searchable.</li>
</ul>
-<p>The Apache Stanbol project was initiated by the European R&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>
+<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/index.html">documentation</a> and <a
href="docs/trunk/scenarios.html">usage scenarios</a> pages for more details.</p>
<p>An online demo of the basic/stable features of Apache Stanbol is available
<a href="http://stanbol.demo.nuxeo.com/";>here</a> and <a
href="http://dev.iks-project.eu:8080/";>here</a>. An experimental/full version
of Apache Stanbol is available <a
href="http://dev.iks-project.eu:8081/";>here</a>.</p>
+<hr />
+<p>The Apache Stanbol project was initiated by the European R&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>
<h2 id="how_to_get_involved">How to get involved</h2>
<h3 id="mailing_lists">Mailing lists</h3>
-<p>The dev mailing list is where the action is, so make sure you subscribe
-to the Stanbol developers mailing list by sending an
-email to <code>stanbol-dev-subscribe AT incubator.apache.org</code> .</p>
+<p>The dev mailing list is where the action is, so make sure you subscribe to
the Apache Stanbol developers mailing list by sending an email to
<code>stanbol-dev-subscribe AT incubator.apache.org</code> .</p>
<p>We don't have a users mailing list at this time, we'll create it if traffic
becomes too high on the dev list. User questions are welcome on the dev list
for now.</p>
-<p>Mailing list archives are available at <a
href="http://mail-archives.apache.org/mod_mbox/";>mail-archives.apache.org</a>,
-<a
href="http://markmail.org/search/?q=list:org.apache.incubator.stanbol-*";>markmail.org</a>
and the other usual places.</p>
+<p>Mailing list archives are available at <a
href="http://mail-archives.apache.org/mod_mbox/";>mail-archives.apache.org</a>,
<a
href="http://markmail.org/search/?q=list:org.apache.incubator.stanbol-*";>markmail.org</a>
and the other usual places.</p>
<p>Additional mailing lists:</p>
<ul>
<li><code>stanbol-commits AT incubator.apache.org</code> : commit messages</li>
-<li><code>stanbol-private AT incubator.apache.org</code> : private list for
Stanbol PPMC members</li>
+<li><code>stanbol-private AT incubator.apache.org</code> : private list for
Apache Stanbol <a href="http://incubator.apache.org/guides/ppmc.html";>PPMC</a>
<a href="team.html">members</a></li>
</ul>
<h3 id="issue_tracker">Issue tracker</h3>
-<p>The Stanbol issue tracker is at <a
href="https://issues.apache.org/jira/browse/STANBOL";>https://issues.apache.org/jira/browse/STANBOL</a>.
-You can report issues and submit patches there, and you're welcome to discuss
those on the
-mailing list first, as needed.</p>
+<p>The Stanbol issue tracker is at <a
href="https://issues.apache.org/jira/browse/STANBOL";>https://issues.apache.org/jira/browse/STANBOL</a>.
You can report issues and submit patches there, and you're welcome to discuss
those on the mailing list first, as needed.</p>
<h3 id="source_code">Source code</h3>
-<p>The Stanbol source code can be found at <a
href="http://svn.apache.org/repos/asf/incubator/stanbol/trunk/";>incubator/stanbol/trunk/</a>.
</p>
+<p>The Apache Stanbol source code can be found at <a
href="http://svn.apache.org/repos/asf/incubator/stanbol/trunk/";>incubator/stanbol/trunk/</a>.
</p>
<h3 id="disclaimer">Disclaimer</h3>
<p>Apache Stanbol is an effort undergoing incubation at <a
href="http://apache.org/";>The Apache Software Foundation (ASF)</a>, sponsored
by the <a href="http://incubator.apache.org/";>Apache Incubator PMC</a>.
Incubation is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the completeness or
stability of the code, it does indicate that the project has yet to be fully
endorsed by the ASF.</p>
</div>
