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/04/11 10:30:50 UTC
svn commit: r812318 [10/10] - in /websites/staging/stanbol/trunk/content: ./
stanbol/docs/0.9.0-incubating/ stanbol/docs/0.9.0-incubating/cmsadapter/
stanbol/docs/0.9.0-incubating/contenthub/
stanbol/docs/0.9.0-incubating/enhancer/ stanbol/docs/0.9.0-i...
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/reasoners.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/reasoners.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/reasoners.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,343 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+ <title>Apache Stanbol - Reasoners</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>
+
+<body>
+ <div id="navigation">
+ <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" height="101" border="0" src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+ <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL">Issue Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the-asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Reasoners</h1>
+ <p>The Stanbol Reasoners component provides a set of services that take advantage of automatic inference engines.</p>
+<p>The module implements a common api for reasoning services, providing the possibility to plug different reasoners and configurations in parallel.</p>
+<p>Actually the module includes <a href="http://owlapi.sourceforge.net/" target="_blank">OWLApi</a> and <a href="http://jena.sourceforge.net/" target="_blank">Jena</a> based abstract services, with concrete implementations for Jena RDFS, OWL, OWLMini and HermiT reasoning service.</p>
+<p>The Reasoners module expose a REST endpoint at the following location:</p>
+<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="o">/</span><span class="n">reasoners</span>
+</pre></div>
+
+
+<p>with the following preloaded services:</p>
+<ul>
+<li><tt>/rdfs</tt>, which is based on Jena RDFS reasoner and supports almost all of the RDFS <a href="#ref1">[1]</a> entailments.</li>
+<li><tt>/owl</tt>, a Jena reasoner configured to support OWL <a href="#ref2">[2]</a> (with some limitations, <a href="#ref4">[4]</a>)</li>
+<li><tt>/owlmini</tt>, another Jena configuration that partially supports OWL (see <a href="#ref5">[5]</a>)</li>
+</ul>
+<p>In addition, it is also available a service which uses the HermiT <a href="#ref6">[6]</a> reasoner to exploit the full OWL 2 <a href="#ref3">[3]</a> specification.</p>
+<p>Each reasoner can be accessed with one of three tasks:</p>
+<ul>
+<li>check: to perform a consistency check. This service returns HTTP Status <tt>200</tt> if data is consistent, <tt>204</tt> otherwise (at the current state of implementation the service does not include an explanation about why the input is inconsistent. This feature is in our todo list, by the way)</li>
+<li>classify: to materialize all inferred <tt>rdf:type</tt> statements.</li>
+<li>enrich: to materialize all inferred statements.</li>
+</ul>
+<p>For example:</p>
+<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/reasoners/o</span><span class="n">wl</span><span class="sr">/check /</span><span class="o">/</span> <span class="n">expose</span> <span class="n">the</span> <span class="n">Jena</span> <span class="n">owl</span> <span class="n">service</span> <span class="n">with</span> <span class="n">task</span> <span class="n">check</span><span class="p">,</span> <span class="ow">or</span>
+<span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/reasoners/o</span><span class="n">wl2</span><span class="sr">/classify /</span><span class="o">/</span> <span class="n">to</span> <span class="k">use</span> <span class="n">the</span> <span class="n">HermiT</span> <span class="n">service</span> <span class="n">with</span> <span class="n">task</span> <span class="n">classify</span>
+</pre></div>
+
+
+<p>We can use the curl command line utility to ask the Jena OWL reasoning service to materialize all inferences produced by loading the FOAF ontology:</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">curl</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Accept: text/n3"</span> <span class="s">"http://localhost:8080/stanbol/reasoners/owl/enrich?url=http://xmlns.com/foaf/0.1/"</span>
+</pre></div>
+
+
+<p>The above example performs a GET asking for a <tt>text/n3</tt> representation of the result. For example, the equivalency of <tt>foaf:Agent</tt> and <tt>dc:Agent</tt> result in the <tt>rdfs:subClassOf</tt> statements for the <tt>foaf:Person</tt> type:
+<pre>[...]
+<http://xmlns.com/foaf/0.1/Person>
+ a <http://www.w3.org/2002/07/owl#Thing> ,
+ <http://www.w3.org/2002/07/owl#Class> ,
+ <http://www.w3.org/2000/01/rdf-schema#Resource> ,
+ <http://www.w3.org/2000/01/rdf-schema#Class> ;
+ <http://www.w3.org/2000/01/rdf-schema#label>
+ "Person" ;
+ <http://www.w3.org/2000/01/rdf-schema#subClassOf>
+ <http://xmlns.com/foaf/0.1/Person> ,
+ <http://purl.org/dc/terms/Agent> ,
+ <http://xmlns.com/foaf/0.1/Agent> ,
+ <http://www.w3.org/2002/07/owl#Thing> ,
+ <http://www.w3.org/2000/01/rdf-schema#Resource> ,
+ <http://www.w3.org/2000/10/swap/pim/contact#Person> ,
+ <http://www.w3.org/2003/01/geo/wgs84_pos#SpatialThing> ;
+ <http://www.w3.org/2002/07/owl#disjointWith>
+ <http://xmlns.com/foaf/0.1/Organization> ,
+ <http://xmlns.com/foaf/0.1/Project> ;
+[...]</pre>
+This behaviour is equivalent if we use the method POST with the header <tt>Content-type: application/x-www-form-urlencoded</tt>. In addition, if the <tt>target</tt> parameter is provided, the service saves the output in the given graph in the triple store and does not return the RDF stream.</p>
+<h2 id="differences-between-the-reasoners">Differences between the reasoners</h2>
+<p>Let's give some example on the differences between the available reasoners (to try the example ontology snippets you can download them from <a href="https://github.com/enridaga/reasoners.examples/tree/master/enridaga.reasoners.examples" target="_blank">here</a>).</p>
+<p>The first snippet uses rdfs:subClassOf to declare that any Article is a Document, which is in turn a ContentItem.
+<pre>
+<!-- item_1 is an Article -->
+<ex:Article rdf:about="http://www.example.org/reasoners/item_1"/></p>
+<p><!-- An article is a kind of Document -->
+<rdf:Description rdf:about="http://www.example.org/reasoners/Article">
+ <rdfs:subClassOf rdf:resource="http://www.example.org/reasoners/Document"/>
+</rdf:Description></p>
+<p><!-- An document is a kind of content item -->
+<rdf:Description rdf:about="http://www.example.org/reasoners/Document">
+ <rdfs:subClassOf rdf:resource="http://www.example.org/reasoners/ContentItem"/>
+</rdf:Description>
+</pre>
+<a href="https://raw.github.com/enridaga/reasoners.examples/master/enridaga.reasoners.examples/rdfs/subclass.xml" target="_blank">download it</a></p>
+<p>Giving it to the /rdfs reasoning service, we obtain as resulted inferred statement that item_1 is also a Document and a ContentItem. Another feature of RDFS is the definition of the domain and range of a property.
+<pre style="overflow: auto">
+<!-- Both enridaga and alexdma are authors of item_1 -->
+<rdf:Description rdf:about="http://www.example.org/reasoners/enridaga">
+ <ex:author rdf:resource="http://www.example.org/reasoners/item_1"/>
+</rdf:Description>
+<rdf:Description rdf:about="http://www.example.org/reasoners/alexdma">
+ <ex:author rdf:resource="http://www.example.org/reasoners/item_1"/>
+</rdf:Description></p>
+<p><!-- ex:author wants a person as subject, and a content-item as object -->
+<rdf:Description rdf:about="http://www.example.org/reasoners/author">
+ <rdfs:domain rdf:resource="http://www.example.org/reasoners/Person"/>
+ <rdfs:range rdf:resource="http://www.example.org/reasoners/ContentItem"/>
+</rdf:Description>
+</pre>
+<a href="https://raw.github.com/enridaga/reasoners.examples/master/enridaga.reasoners.examples/rdfs/domain-range.xml" target="_blank">download it</a>
+We will obtain, in this case, that both <tt>enridaga</tt> and <tt>alexdma</tt> are <tt>Authors</tt>, and that <tt>item_1</tt> is a <tt>ContentItem</tt>. RDFS semantics is considered also by other reasoners. The <tt>/rdfs</tt> service is the less "expressive" of the four.</p>
+<p>The following snippet will work with <tt>/owl</tt>, <tt>/owlmini</tt> and <tt>/owl2</tt> (but not with <tt>/rdfs</tt>):
+<pre style="overflow: auto">
+<!-- ogrisel, enridaga and alexdma are developers -->
+<ex:Developer rdf:about="#enridaga" />
+<ex:Developer rdf:about="#ogrisel" />
+<ex:Developer rdf:about="#alexdma" /></p>
+<p><!-- We know: #alexdma #workedTogheter #enridaga and #ogrisel -->
+<rdf:Description rdf:about="#alexdma">
+<workedTogheter rdf:resource="#ogrisel"/>
+<workedTogheter rdf:resource="#enridaga"/>
+</rdf:Description></p>
+<p><!-- #workedTogheter is an owl:SymmetricProperty (well, this is an example...) -->
+<owl:SymmetricProperty rdf:about="#workedTogheter"/>
+<!-- #workedTogheter is also a owl:TransitiveProperty (well, this is an example...) -->
+<owl:TransitiveProperty rdf:about="#workedTogheter"/>
+</pre>
+<a href="https://raw.github.com/enridaga/reasoners.examples/master/enridaga.reasoners.examples/owlmini/symmetric.xml" target="_blank">download it</a>
+The OWL vocabulary introduce logical capabilities, allowing more complex inferences to be produced. In the above example we state that <tt>alexdma workedWith enridaga</tt> and <tt>ogrisel</tt>. Since we declare the property <tt>workedTogheter</tt> to be "Symmetric" and "Transitive", the result will include the following:
+<ul>
+<li><tt>enridaga workedWith alexdma</tt> (is symmetric)</li>
+<li><tt>ogrisel workedWith alexdma</tt></li>
+<li><tt>ogrisel workedWith enridaga</tt> (is transitive)</li>
+<li><tt>enridaga workedWith ogrisel</tt></li>
+</ul></p>
+<p>Next snippet is inconsistent. This means that the OWL based reasoners will not return any inference, but a 204 HTTP response:
+<pre style="overflow: auto">
+<!-- enridaga is a person -->
+<ex:Person rdf:about="http://www.example.org/reasoners/enridaga" /></p>
+<p><!-- Persons and Organizations are disjoint -->
+<owl:Class rdf:about="http://www.example.org/reasoners/Person" />
+<owl:Class rdf:about="http://www.example.org/reasoners/Organization">
+ <owl:disjointWith rdf:resource="http://www.example.org/reasoners/Person" />
+</owl:Class></p>
+<p><!-- A Public Limited Company is a kind of Company, which is a kind of Organization -->
+<owl:Class rdf:about="http://www.example.org/reasoners/PublicLimitedCompany">
+ <rdfs:subClassOf rdf:resource="http://www.example.org/reasoners/Company" />
+</owl:Class>
+<owl:Class rdf:about="http://www.example.org/reasoners/Company">
+ <rdfs:subClassOf rdf:resource="http://www.example.org/reasoners/Organization" />
+</owl:Class></p>
+<p><!-- enridaga cannot be a Public Limited Company -->
+<ex:PublicLimitedCompany rdf:about="http://www.example.org/reasoners/enridaga" />
+</pre>
+<a href="https://raw.github.com/enridaga/reasoners.examples/master/enridaga.reasoners.examples/owlmini/inconsistent-types.xml" target="_blank">download it</a>
+The <tt>/owlmini</tt> implements the OWL language with some (more) limitations then <tt>/owl</tt> (both are based on the Jena rule based reasoner, as said before).</p>
+<p>The following example shows the use of class restrictions, in particular the usage of <tt>owl:someValuesFrom</tt>:
+<pre style="overflow: auto">
+<!-- john, is an developer, but we don't know anything else -->
+<ex:Developer rdf:about="#john">
+</ex:Developer></p>
+<p><!-- a #SoftwareCompany is a kind of #Organization -->
+<owl:Class rdf:about="SoftwareCompany">
+ <rdfs:subClassOf rdf:resource="#Organization" />
+</owl:Class></p>
+<p><!-- #Developers #worksAt some #SoftwareCompany (they are not the only one...,
+ this is why we use owl:subClassOf) -->
+<owl:Class rdf:about="#Developer">
+ <rdfs:subClassOf>
+ <owl:restriction>
+ <owl:onProperty rdf:resource="#worksAt" />
+ <owl:someValuesFrom rdf:resource="#SoftwareCompany" />
+ </owl:restriction>
+ </rdfs:subClassOf>
+</owl:Class></p>
+<p><!-- Employees are all who #worksAt any kind of Organization (owl:equivalentClass) -->
+<owl:Class rdf:about="#Employee">
+ <owl:equivalentClass>
+ <owl:restriction>
+ <owl:onProperty rdf:resource="#worksAt" />
+ <owl:someValuesFrom rdf:resource="#Organization" />
+ </owl:restriction>
+ </owl:equivalentClass>
+</owl:Class>
+</pre>
+<a href="https://raw.github.com/enridaga/reasoners.examples/master/enridaga.reasoners.examples/owl/some-values-from.xml" target="_blank">download it</a></p>
+<p>We expect an OWL reasoner to state that John is an <tt>Employee</tt>. This example does not work with <tt>/rdfs</tt> (it ignores the OWL semantics), and does not work with <tt>/owlmini</tt>, because the Jena OWL(mini) reasoner omits the forward entailments for <tt>owl:someValuesFrom restrictions</tt> (see <a href="#ref4">[4]</a>). It works correctly if we use the service <tt>/owl</tt>.</p>
+<p>The <tt>/owl</tt> service support the most of the semantic of OWL. The HermiT reasoner is based on <a href="http://owlapi.sourceforge.net/">OWLApi</a> and is an example of a DL reasoner. It fully covers OWL and OWL2, which introduces lot of interesting features. Here is an example:
+<pre style="overflow: auto">
+<!-- any Employee must have some features: firstname, familyname, email
+ and worksAt (in one of the allowed places) -->
+<owl:Class rdf:about="#Employee">
+ <owl:equivalentClass>
+ <owl:Class>
+ <owl:intersectionOf rdf:parseType="Collection">
+ <rdf:Description rdf:about="#Person" />
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="#firstname" />
+ <owl:someValuesFrom rdf:resource="&rdfs;Literal" />
+ </owl:Restriction>
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="#familyname" />
+ <owl:someValuesFrom rdf:resource="&rdfs;Literal" />
+ </owl:Restriction>
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="#email" />
+ <owl:someValuesFrom rdf:resource="&rdfs;Literal" />
+ </owl:Restriction>
+ <!-- -->
+ <!-- Let's say that Employees can work only in #Rome , #Catania and
+ #Bologna -->
+ <owl:Restriction>
+ <owl:onProperty rdf:resource="#worksAt" />
+ <owl:someValuesFrom>
+ <owl:Class>
+ <owl:oneOf rdf:parseType="Collection">
+ <owl:Thing rdf:about="#Rome" />
+ <owl:Thing rdf:about="#Catania" />
+ <owl:Thing rdf:about="#Bologna" />
+ </owl:oneOf>
+ </owl:Class>
+ </owl:someValuesFrom>
+ </owl:Restriction>
+ </owl:intersectionOf>
+ </owl:Class>
+ </owl:equivalentClass>
+</owl:Class></p>
+<p><owl:DatatypeProperty rdf:about="#firstname" />
+<owl:DatatypeProperty rdf:about="#familyname" />
+<owl:DatatypeProperty rdf:about="#email" /></p>
+<p><!-- #worksAt has range #Place -->
+<owl:ObjectProperty rdf:about="#worksAt">
+ <rdfs:range rdf:resource="#Place" />
+</owl:ObjectProperty></p>
+<p><!-- all the following places are distinct (no synonyms here) -->
+<owl:AllDifferent>
+ <owl:distinctMembers rdf:parseType="Collection">
+ <owl:Thing rdf:about="#Rome" />
+ <owl:Thing rdf:about="#Catania" />
+ <owl:Thing rdf:about="#Bologna" />
+ <owl:Thing rdf:about="#Moricone" />
+ </owl:distinctMembers>
+</owl:AllDifferent></p>
+<p><!-- enridaga, to be an Employee, must fulfill the restrictions defined
+ for the class #Employee. -->
+<Person rdf:about="#enridaga">
+ <!-- If you comment one of the next 4 statement, you won't have #enridaga
+ to result as #Employee. -->
+ <firstname>Enrico</firstname>
+ <familyname>Daga</familyname>
+ <email>enridaga@example.org</email>
+ <worksAt rdf:resource="#Catania" />
+ <!-- If you uncomment the two statements below you will obtain an inconsistency,
+ because #Moricone is not an allowed place for developers -->
+ <!-- <worksAt rdf:resource="#Moricone" /> <rdf:type rdf:resource="#Employee"
+ /> -->
+</Person>
+</pre>
+<a href="https://raw.github.com/enridaga/reasoners.examples/master/enridaga.reasoners.examples/owl2/class-restrictions-owl2.xml" target="_blank">download it</a></p>
+<p>The above differences depend on the semantic supported by the specific reasoner and from the implementation, which limit the power of the system in favour of a better efficiency (is the case of the <tt>/owlmini</tt> implementation of Jena, more efficient then the respective <tt>/owl</tt>). If you need to work with RDFS semantic, and don't need OWL for your inferences, just use the RDFS one.</p>
+<h2 id="build-and-install">Build and install</h2>
+<p>Run Stanbol, for example:</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">java</span> <span class="o">-</span><span class="n">jar</span> <span class="o">-</span><span class="n">Xmx1g</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">stanbol</span><span class="o">.</span><span class="n">launchers</span><span class="o">.</span><span class="n">full</span><span class="o">-</span><span class="mf">0.9.0</span><span class="o">-</span><span class="n">incubating</span><span class="o">-</span><span class="n">SNAPSHOT</span><span class="o">.</span><span class="n">jar</span>
+</pre></div>
+
+
+<p>You must have the Ontonet and Rules modules already installed (they are if you have followed the above example).
+Move to the <tt>/reasoners</tt> directory, then run</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">mvn</span> <span class="n">install</span> <span class="o">-</span><span class="n">PinstallBundle</span> <span class="o">-</span><span class="n">Dsling</span><span class="o">.</span><span class="n">url</span><span class="o">=&</span><span class="ow">lt</span><span class="p">;</span><span class="n">the</span> <span class="n">path</span> <span class="n">to</span> <span class="n">your</span> <span class="n">running</span> <span class="n">Felix</span> <span class="n">administration</span> <span class="n">console</span><span class="o">&</span><span class="ow">gt</span><span class="p">;</span>
+</pre></div>
+
+
+<p>for example</p>
+<p>% mvn install -PinstallBundle http://localhost:8080/system/console</p>
+<h3 id="add-the-hermit-reasoner">Add the HermiT reasoner</h3>
+<p>To enable HermiT as OWL2 reasoner you can download and install it from the Stanbol (Incubating) svn repository. The steps are the following:</p>
+<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">co</span> <span class="n">https:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span class="n">asf</span><span class="sr">/incubator/s</span><span class="n">tanbol</span><span class="sr">/trunk/</span><span class="n">reasoners</span><span class="o">/</span><span class="n">hermit</span> <span class="n">stanbol</span><span class="o">-</span><span class="n">hermit</span>
+<span class="nv">$</span> <span class="nv">cd</span> <span class="n">stanbol</span><span class="o">-</span><span class="n">hermit</span>
+<span class="nv">$</span> <span class="nv">mvn</span> <span class="n">install</span> <span class="o">-</span><span class="n">PinstallBundle</span> <span class="o">-</span><span class="n">Dsling</span><span class="o">.</span><span class="n">url</span><span class="o">=</span><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/system/co</span><span class="n">nsole</span> <span class="sr">//</span> <span class="n">change</span> <span class="n">this</span> <span class="n">to</span> <span class="n">the</span> <span class="n">path</span> <span class="n">related</span> <span class="n">to</span> <span class="n">your</span> <span class="n">Stanbol</span> <span class="n">instance</span>
+</pre></div>
+
+
+<h2 id="references">References:</h2>
+<ul>
+<li>[1] <a name="ref1" href="http://www.w3.org/TR/rdf-schema/" target="_blank">RDFS</a></li></li>
+<li>[2] <a name="ref2" href="http://www.w3.org/TR/owl-features/" target="_blank">OWL</a></li></li>
+<li>[3] <a name="ref3" href="http://www.w3.org/TR/owl2-overview/" target="_blank">OWL 2</a></li></li>
+<li>[4] <a name="ref4" href="http://jena.sourceforge.net/inference/" target="_blank">Jena inference support</a></li></li>
+<li>[5] <a name="ref5" href="http://jena.sourceforge.net/inference/#OWLnotes" target="_blank">Jena OWL notes</a></li></li>
+<li>[6] <a name="ref6" href="http://hermit-reasoner.com/" target="_blank">HermiT</a></li>
+</ul>
+<hr />
+<p><em><a href="components.html">Back to components</a></em></p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Stanbol and the Apache feather and Stanbol logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+ <title>Apache Stanbol - Rules</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>
+
+<body>
+ <div id="navigation">
+ <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" height="101" border="0" src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+ <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL">Issue Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the-asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <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>
+<h2 id="usage-scenarios">Usage Scenarios</h2>
+<h3 id="integrity-check-from-data-fusion">Integrity check from data fusion</h3>
+<p>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.
+In such a way the administrator is able to configure the CMS in order filter knowledge retrieved in Linked Data, e.g., via the <a href="enhancer.html">Enhancer</a>, that satisfies some integrity driven constraint. The constraint can be defined by means of Stanbol Rules.
+For instance in a CMS which collects core knowledge about musicians it might possible to define integrity check rules which keep only entities that are typed as Musicians in DBpedia <a href="#dbpedia">[5]</a> and have an associated image, a birth place and the instrument played.
+Any other entity not satisfying the constraints is discarded. <br />
+</p>
+<h3 id="vocabulary-harmonization">Vocabulary harmonization</h3>
+<p>Supposing we want to use some dataset in Linked
+Data as external knowledge bases for a generic CMS enhanced with Stanbol.
+Now the problem how to use data from those datasets expressed with some external
+and heterogeneous vocabularies or ontologies within the CMS has.
+Furthermore the CMS has its own way to formalize knowledge, namely the its
+Ontology Network managed by <a href="../ontologymanager/ontonet.html">Stanbol OntoNet</a>.
+The solution is provided by Refactor which allows to interpret the rules of
+inference as refactoring rules in order harmonize external data to the Stanbol's ontologies.</p>
+<p>Also, Stanbol Rules can be used to derive new knowledge or integrate information
+from different semantically enhanced contents.</p>
+<h2 id="features">Features</h2>
+<p>Stanbol allows to provide rules to other component, i.e., Stanbol Reasoners, or to third parties in three different formats.</p>
+<ul>
+<li><strong>SWRL</strong> <a href="#swrl">[1]</a>. The Semantic Web Rule Language (SWRL) is a rule language which combines OWL DL with the Unary/Binary Datalog RuleML sublanguages of the Rule Markup Language and enables enables Horn-like rules to be combined with an OWL knowledge base. Providing Stanbol Rules as SWRL rules means that they can be interpreted in classical DL reasoning. That allows, for inantace, to use Stanbol Rules with any of the OWL 2 reasoners configured in the <a href="reasoners.html">Stanbol Reasoners component</a>; </li>
+<li><strong>Jena Rules</strong> <a href="#jena">[2]</a>. It enables compatibility with inference engines based on Jena inference and rule language. Internally, the <a href="reasoners.html">Stanbol Reasoners component</a> provides a reasoning profile based on Jena inference;</li>
+<li><strong>SPARQL</strong> <a href="#sparql">[3]</a>. SPARQL is a W3C recommendation as a query language for RDF. A natural way to represent inference transformation rules in SPARQL is by using the CONSTRUCT query form. Stanbl Rules can be converted to SPARQL CONSTRUCTs and executed by any SPARQL engine. Stanbol provides a particular SPARQL engine, namely the <a href="rules/refactor.html">Refactor</a> which is supposed to perform transformation of RDF graphs based on transformation rules defined in Stanbol. The latter allows, for instance, the vocabulary harmonization of RDF graphs retrieved from different sources in Linked Data <a href="#linkeddata">[4]</a>.</li>
+</ul>
+<p>The rule pattern used for representing rules is the <em>modus ponens</em>, e.g. <strong><em>if</em></strong> <em>condition</em> <strong><em>then</em></strong> <em>consequent</em> . For example the axiom <em>"every person has a father"</em> can be expressed with
+the modus ponens in the following way:</p>
+<p><center>
+<strong>if</strong> X is a person <strong>then</strong> X has a father
+</center></p>
+<p>and by means of predicate calculus as:</p>
+<p><center>
+∀x∃y.Person(x) ⇒ hasFather(x, y)
+</center></p>
+<p>where Person and hasF ather are two predicates.</p>
+<p>The Stanbol Rules component allows to add a layer which enables Stanbol to express business logics by means of axioms, i.e., rules. These axioms can be organized into a container called Recipe, which groups and identifies set of rules which share the same business logic and interprets them as a whole.</p>
+<h3 id="sub-components">Sub-Components</h3>
+<ul>
+<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>
+<h2 id="references">References</h2>
+<p>[1] <a name="swrl" href="http://www.w3.org/Submission/SWRL/" target="_blank">SWRL</a> <br/>
+[2] <a name="jena" href="http://jena.sourceforge.net/inference/#rules" target="_blank">Jena Rules</a><br/>
+[3] <a name="sparql" href="http://www.w3.org/TR/rdf-sparql-query/" target="_blank">SPARQL</a><br/>
+[4] <a name="linkeddata" href="http://linkeddata.org/" target="_blank">Linked Data</a><br/>
+[5] <a name="linkeddata" href="http://dbpedia.org/About" target="_blank">DBpedia</a><br/></p>
+<hr />
+<p><em><a href="components.html">Back to components</a></em></p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Stanbol and the Apache feather and Stanbol logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/language.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/language.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/language.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,124 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+ <title>Apache Stanbol - Stanbol Rule Language</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>
+
+<body>
+ <div id="navigation">
+ <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" height="101" border="0" src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+ <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL">Issue Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the-asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Stanbol Rule Language</h1>
+ <h2 id="example">Example</h2>
+<p>The following is a rule, called <code>uncleRule</code>, for inferring the relation <code>hasUncle</code> between individuals <code>x</code> and <code>y</code> if <code>z</code> is a parent of <code>x</code> and <code>z</code> is brother of <code>y</code>.</p>
+<p>In <strong>Stanbol Rule</strong> syntax it is:</p>
+<div class="codehilite"><pre><span class="n">uncleRule</span><span class="p">[</span><span class="n">has</span><span class="p">(</span><span class="sr"><http://www.foo.org/myont.owl#hasParent></span><span class="p">,</span> <span class="p">?</span><span class="n">x</span><span class="p">,</span> <span class="p">?</span><span class="n">z</span><span class="p">)</span> <span class="o">.</span>
+ <span class="n">has</span><span class="p">(</span><span class="sr"><http://www.foo.org/myont.owl#hasSibling></span><span class="p">,</span> <span class="p">?</span><span class="n">z</span><span class="p">,</span> <span class="p">?</span><span class="n">y</span><span class="p">)</span>
+ <span class="o">-></span>
+ <span class="n">has</span><span class="p">(</span><span class="sr"><http://www.foo.org/myont.owl#hasUncle></span><span class="p">,</span> <span class="p">?</span><span class="n">x</span><span class="p">,</span> <span class="p">?</span><span class="n">y</span><span class="p">)</span>
+<span class="p">]</span>
+</pre></div>
+
+
+<p>The rule above becomes the following <strong>SWRL</strong> rule:</p>
+<div class="codehilite"><pre><span class="nt"><swrl:Variable</span> <span class="na">rdf:ID=</span><span class="s">"x"</span><span class="nt">/></span>
+<span class="nt"><swrl:Variable</span> <span class="na">rdf:ID=</span><span class="s">"z"</span><span class="nt">/></span>
+<span class="nt"><swrl:Variable</span> <span class="na">rdf:ID=</span><span class="s">"y"</span><span class="nt">/></span>
+<span class="nt"><ruleml:Imp></span>
+ <span class="nt"><ruleml:body</span> <span class="na">rdf:parseType=</span><span class="s">"Collection"</span><span class="nt">></span>
+ <span class="nt"><swrl:IndividualPropertyAtom></span>
+ <span class="nt"><swrl:propertyPredicate</span> <span class="na">rdf:resource=</span><span class="s">"&eg;hasParent"</span><span class="nt">/></span>
+ <span class="nt"><swrl:argument1</span> <span class="na">rdf:resource=</span><span class="s">"#x"</span> <span class="nt">/></span>
+ <span class="nt"><swrl:argument2</span> <span class="na">rdf:resource=</span><span class="s">"#z"</span> <span class="nt">/></span>
+ <span class="nt"></swrl:IndividualPropertyAtom></span>
+ <span class="nt"><swrl:IndividualPropertyAtom></span>
+ <span class="nt"><swrl:propertyPredicate</span> <span class="na">rdf:resource=</span><span class="s">"&eg;hasSibling"</span><span class="nt">/></span>
+ <span class="nt"><swrl:argument1</span> <span class="na">rdf:resource=</span><span class="s">"#z"</span> <span class="nt">/></span>
+ <span class="nt"><swrl:argument2</span> <span class="na">rdf:resource=</span><span class="s">"#y"</span> <span class="nt">/></span>
+ <span class="nt"></swrl:IndividualPropertyAtom></span>
+ <span class="nt"></ruleml:body></span>
+ <span class="nt"><ruleml:head</span> <span class="na">rdf:parseType=</span><span class="s">"Collection"</span><span class="nt">></span>
+ <span class="nt"><swrl:IndividualPropertyAtom></span>
+ <span class="nt"><swrl:propertyPredicate</span> <span class="na">rdf:resource=</span><span class="s">"&eg;hasUncle"</span><span class="nt">/></span>
+ <span class="nt"><swrl:argument1</span> <span class="na">rdf:resource=</span><span class="s">"#x"</span> <span class="nt">/></span>
+ <span class="nt"><swrl:argument2</span> <span class="na">rdf:resource=</span><span class="s">"#y"</span> <span class="nt">/></span>
+ <span class="nt"></swrl:IndividualPropertyAtom></span>
+ <span class="nt"></ruleml:head></span>
+<span class="nt"></ruleml:Imp></span>
+</pre></div>
+
+
+<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="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>
+
+
+<hr />
+<p><em><a href="../rules.html">Back to Rules</a></em> </p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Stanbol and the Apache feather and Stanbol logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/refactor.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/refactor.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/refactor.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,143 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+ <title>Apache Stanbol - Refactor</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>
+
+<body>
+ <div id="navigation">
+ <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" height="101" border="0" src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+ <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL">Issue Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the-asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Refactor</h1>
+ <p>The Refactor is a service which allows to interpret rules in order to perform refactoring of RDF graphs. For the refactoring the set of rules in the recipes are interpreted and run as SPARQL CONTRUCT in which the where clause is derived from the body of the rule and the construct clause is derived from the head of the rule. The output of a refactoring is a transformed graph which satisfies the constraints expressed in the rules. The refactoring in useful for tasks of semantic harmonization of RDF graphs expressed with different ontologies/vocabularies towards their representation with a single ontology or vocagulary. The output of a refactoring is a transformed graph which satisfies the constraints expressed in the rules. </p>
+<h2 id="terminology">Terminology</h2>
+<ul>
+<li>A <strong>Recipe</strong> is a set of rules defined according to a specific task. Rules are written in a specific syntax, and can then be executed for refactoring (as SPARQL queries) or through reasoning services.</li>
+<li><strong>Refactoring</strong> is the task aimed to perform the transformation of RDF graphs. The transformation is driven by refactoring rules, basically Stanbol Rules interpreted as SPARQL CONSTRUCT clauses.</li>
+<li><strong>Reasoning</strong> is the activity of interpreting axioms for inferring new knowledge, classifying, checking the consistency of an ontology, etc...</li>
+</ul>
+<h2 id="usage-scenarios">Usage Scenarios</h2>
+<h3 id="vocabulary-harmonization">Vocabulary harmonization</h3>
+<p>Supposing we want to use some dataset in Linked
+Data as external knowledge bases for a generic CMS enhanced with Stanbol.
+Now the problem how to use data from those datasets expressed with some
+external and heterogeneous vocabularies or ontologies within the CMS has.
+Furthermore the CMS has its own way to formalize knowledge, namely the
+its Ontology Network managed by <a href="../ontologymanager/ontonet.html">Stanbol OntoNet</a>.
+The solution is provided by Refactor which allows to interpret the rules of
+inference as refactoring rules in order harmonize external data to the
+Stanbol's ontologies. Figure 1 gives a very quick idea about how the CMS can
+benefit from the Refactor showing how external data can be aligned and used within the CMS.</p>
+<p><center>
+<figure>
+<img width="500px" src="../../../images/rules/refactor.png" alt="Vocabulary harmonization via Stanbol Refactor">
+<figcaption>Figure 1: the refactor is used to align external data to the ontologies used in a generic CMS enhanced with Stanbol.</figcaption>
+<figure>
+</center></p>
+<p>We can specify a concrete scenario for a better understanding of the
+Refactor. Suppose we have configured the CMS (i.e. <a href="../entityhub.html">Stanbol EntityHub</a>) in order
+to fetch entities about persons from DBpedia. Now we want to represent these
+entities adopting the vocabulary from schema.org and produce
+schema.org Rich Snippets in order to provide search engine
+optimization capabilities to the CMS. What we need to do is to write a recipe and call
+the Refactor via HTTP REST passing to it the recipe itself and the entities we
+have fetched from Linked Data.</p>
+<h2 id="features">Features</h2>
+<p>In the Refactor rules are interpreted as <a href="http://www.w3.org/TR/rdf-sparql-query/#construct">SPARQL CONSTRUCT</a> queries in which
+the premises (the left part before the arrow in the rule) are the WHERE clause, while the conclusion (the right part after the arrow in the rule) is
+translated into the construct template, i.e., triple patterns in conjunctive form. </p>
+<p>As an example, we can take in account the following rule:</p>
+<div class="codehilite"><pre><span class="n">prefix</span> <span class="n">kn</span> <span class="o">=</span> <span class="sr"><http://foo.org/kinship#></span> <span class="o">.</span>
+<span class="n">uncleRule</span><span class="p">[</span> <span class="n">has</span><span class="p">(</span><span class="n">kn:parent</span><span class="p">,</span> <span class="p">?</span><span class="n">x</span><span class="p">,</span> <span class="p">?</span><span class="n">y</span><span class="p">)</span> <span class="o">.</span> <span class="n">has</span><span class="p">(</span><span class="n">kn:sibling</span><span class="p">,</span> <span class="p">?</span><span class="n">y</span><span class="p">,</span> <span class="p">?</span><span class="n">z</span><span class="p">)</span> <span class="o">-></span> <span class="n">has</span><span class="p">(</span><span class="n">kn:uncle</span><span class="p">,</span> <span class="p">?</span><span class="n">x</span><span class="p">,</span> <span class="p">?</span><span class="n">z</span><span class="p">)</span> <span class="p">]</span>
+</pre></div>
+
+
+<p>The rule above is transformed into the following SPARQL CONSTRUCT query:</p>
+<div class="codehilite"><pre><span class="n">PREFIX</span> <span class="n">kn:</span> <span class="sr"><http://foo.org/kinship#></span>
+<span class="n">CONSTRUCT</span> <span class="p">{</span> <span class="p">?</span><span class="n">x</span> <span class="n">kn:uncle</span> <span class="p">?</span><span class="n">z</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">kn:parent</span> <span class="p">?</span><span class="n">y</span> <span class="o">.</span>
+ <span class="p">?</span><span class="n">y</span> <span class="n">kn:sibling</span> <span class="p">?</span><span class="n">z</span>
+<span class="p">}</span>
+</pre></div>
+
+
+<p>The SPARQL engines used internally by the Refactor for running rules is <a href="http://incubator.apache.org/jena/documentation/query/">Apache Jena ARQ</a></p>
+<p>We remand any detail about the syntax and the expressivity of the Stanbole Rule language to its <a href="./language.html">section</a>.<br />
+</p>
+<h2 id="service-endpoints">Service Endpoints</h2>
+<p>The Refactor 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="refactor-engine-refactor">Refactor Engine ("/refactor"):</h3>
+<ul>
+<li>The Refactor Engine <strong>@/refactor</strong> performs a refactoring applying an existing recipe in the rule store to the provided RDF graph.</li>
+</ul>
+<h3 id="refactor-engine-refactorapply">Refactor Engine ("/refactor/apply"):</h3>
+<ul>
+<li>Refactor Engine <strong>@/refactor/apply</strong> performs a refactoring applying an recipe as string to the provided RDF graph as input source.</li>
+</ul>
+<hr />
+<p><em><a href="../rules.html">Back to Stanbol Rules</a></em></p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Stanbol and the Apache feather and Stanbol logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/store.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/store.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/rules/store.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,86 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+ <title>Apache Stanbol - Rule Store</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>
+
+<body>
+ <div id="navigation">
+ <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" height="101" border="0" src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+ <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL">Issue Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the-asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Rule Store</h1>
+ <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>
+<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/recipe">/rules/recipe</a> allows to manage, store and retrieve pre-defined rule sequences, or <strong>recipes</strong>.</li>
+</ul>
+<p>TODO</p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Stanbol and the Apache feather and Stanbol logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/scenarios.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/scenarios.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/scenarios.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,106 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+ <title>Apache Stanbol - Usage Scenarios for Apache Stanbol</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>
+
+<body>
+ <div id="navigation">
+ <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" height="101" border="0" src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+ <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL">Issue Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the-asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Usage Scenarios for Apache Stanbol</h1>
+ <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>
+<figure>
+
+<figcaption>Figure 1: Traditional CMS using Apache Stanbol via its HTTP RESTful interface.</figcaption>
+</figure>
+
+<p>The following usage scenarios explain in more detail 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 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>
+</li>
+<li>
+<p><a href="multilingual.html">Working with multiple languages</a>: Get enhancements for textual content in multiple languages (EN, DE, SV, DA, PT and NL).</p>
+</li>
+<li>
+<p>Semantic Search in Portals: Store/index enhancements and content items. For a portal this would facilitate semantic search applications.</p>
+</li>
+<li>
+<p>Refactoring Enhancements for SEO: Refactor the enhancement result, its property names and ontology types according your target ontology.</p>
+</li>
+<li>
+<p>Transforming CMS repository structures into ontologies.</p>
+</li>
+<li>
+<p>Provide repository structures as thesaurus or domain ontology, e.g. categories.</p>
+</li>
+</ul>
+<hr />
+<p><em>Back to <a href="index.html">Documentation</a></em></p>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Stanbol and the Apache feather and Stanbol logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/services.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/services.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/services.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,122 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+ <title>Apache Stanbol - HTTP entry points for Apache Stanbol services</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>
+
+<body>
+ <div id="navigation">
+ <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" height="101" border="0" src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+ <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL">Issue Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the-asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">HTTP entry points for Apache Stanbol services</h1>
+ <p>The web interface of your Apache Stanbol installation provides information for the main HTTP entry points. Each resource comes with a web view that documents the matching RESTful API for applications. </p>
+<p>Depending on which launcher you use, you will get a different set of services. By choosing the <strong>full launcher</strong>, you will get everything including experimental components, if you choose the <strong>stable launcher</strong> you will get the most stable components only.</p>
+<p><em>Note: all links on this page direct to <a href="http://dev.iks-project.eu">demo instances</a> of Apache Stanbol. To be able to configure all services to your needs, you have run your own installation.</em></p>
+<h2 id="stable-services">Stable Services</h2>
+<ul>
+<li><a href="http://dev.iks-project.eu:8080/engines">/engines</a></li>
+</ul>
+<p>This is a stateless interface to allow clients to submit content to be analyzed by the Enhancement Engines and get the resulting RDF enhancements at once without storing anything on the server-side.</p>
+<ul>
+<li><a href="http://dev.iks-project.eu:8080/entityhub">/entityhub</a></li>
+</ul>
+<p>The Entityhub provides two main services: The entity network manages (external) referenced sites and lets one consume entity information, the Entityhub supports managing and using local entities.</p>
+<ul>
+<li><a href="http://dev.iks-project.eu:8080/system/console/bundles">/system/console</a></li>
+</ul>
+<p>This is the OSGi administration console (for administrators and developers). The initial username / password is set to admin / admin. Use the console to add new bundles and activate, de-activate and configure components. The console can also be used to perform hot-(re)deployment of any OSGi bundles. </p>
+<p>For instance to re-deploy a new version of this web interface, go to the <code>$STANBOL_HOME/enhancer/jersey</code> source folder and run the following command:</p>
+<p><code>$ mvn install -o -DskipTests -PinstallBundle \
+ -Dsling.url=http://localhost:8080/system/console</code></p>
+<h2 id="services-in-the-lab">Services "in the Lab"</h2>
+<ul>
+<li>
+<p><a href="http://dev.iks-project.eu:8081/sparql">/sparql</a>: This is the SPARQL endpoint for the Stanbol store. SPARQL is the standard query language the most commonly used to provide interactive access to semantic knowledge bases.</p>
+</li>
+<li>
+<p><a href="http://dev.iks-project.eu:8081/contenthub">/contenthub</a>: This 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. The longer-term goal of this endpoint is to implement faceted semantic search of the enhanced content items. (Note: Up to now, this endpoint is a proof of concept / experimental feature. It does not actually store the content on the disk, just in memory.)</p>
+</li>
+<li>
+<p><a href="http://dev.iks-project.eu:8081/cmsadapter">/cmsadapter</a>: A component for bi-directional mapping of knowledge structures between CMIS or JCR content repositories and RDF models.</p>
+</li>
+<li>
+<p><a href="http://dev.iks-project.eu:8081/ontonet">/ontonet</a>: Ontonet provides a controlled environment for managing ontologies and ontology networks and user sessions managing them.</p>
+</li>
+<li>
+<p><a href="http://dev.iks-project.eu:8081/reasoners">/reasoners</a>: The reasoners are made for classification, consistency checking, and enrichment of an ontology. Reasoning services are provided through the built-in HermiT reasoner.</p>
+</li>
+<li>
+<p><a href="http://dev.iks-project.eu:8081/rules">/rules</a>: The rules component lets you define rules to be used within the ontology networks and the reasoning services. </p>
+</li>
+<li>
+<p><a href="http://dev.iks-project.eu:8081/factstore">/factstore</a>: The FactStore implements a store for facts plus the ability to query for single facts and for combinations of facts. It implements:</p>
+<ul>
+<li>Persistence storage for n-ary facts about entities</li>
+<li>Query language to query for a single fact</li>
+<li>Query language to query for combinations of facts (reasoning)</li>
+</ul>
+</li>
+</ul>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Stanbol and the Apache feather and Stanbol logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/tutorial.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/tutorial.html (added)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/0.9.0-incubating/tutorial.html Wed Apr 11 08:30:47 2012
@@ -0,0 +1,131 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE- 2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+ <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+ <title>Apache Stanbol - Tutorial for Apache Stanbol - Enhancing content items</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>
+
+<body>
+ <div id="navigation">
+ <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" height="101" border="0" src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+ <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL">Issue Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the-asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+ </div>
+
+ <div id="content">
+ <h1 class="title">Tutorial for Apache Stanbol - Enhancing content items</h1>
+ <p>This tutorial targets at content management system developers, who want to enrich unstructured textual content with "named entity" tags (locations, persons or organizations such as "Paris", "Barack Obama", "BBC"). Apache Stanbol can provide such enhancements together with links to public (e.g. DBpedia) or private (e.g. an enterprise specific terminology) repositories.</p>
+<h2 id="build-and-run-your-apache-stanbol-instance">Build and run your Apache Stanbol instance</h2>
+<p>To build Apache Stanbol from source you need Java 6 and maven 2.2.1 + (version as defined in the pom). You probably need also:<br />
+</p>
+<div class="codehilite"><pre><span class="c">% export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=128M"</span>
+</pre></div>
+
+
+<p>Fetch the sources from the Apache Stanbol code repository</p>
+<div class="codehilite"><pre><span class="c">% svn co http://svn.apache.org/repos/asf/incubator/stanbol/trunk stanbol</span>
+</pre></div>
+
+
+<p>From the source directory run</p>
+<div class="codehilite"><pre><span class="c">% mvn clean install</span>
+</pre></div>
+
+
+<p>Run the stable launcher of Apache Stanbol from your local server machine from the your local directory <code>{root}/stanbol/launchers/</code> with</p>
+<div class="codehilite"><pre><span class="c">% java -Xmx1g -jar stable/target/org.apache.stanbol.launchers.stable-{snapshot-version}-SNAPSHOT.jar</span>
+</pre></div>
+
+
+<p>Your instance runs within the <code>stanbol/sling/</code> directory and is accessible at</p>
+<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span>
+</pre></div>
+
+
+<h2 id="post-content-item-get-an-enhancement-graph">Post content item, get an enhancement graph</h2>
+<p>Goto the local HTTP web endpoint</p>
+<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="o">/</span><span class="n">enhancer</span>
+</pre></div>
+
+
+<p>This stateless interface allows the caller to submit content to the Apache Stanbol enhancer engines and get the resulting enhancements formatted as RDF at once without storing anything on the server-side.</p>
+<p>Simply copy arbitrary english textual content into the input field and get back the enhancements for Bob Marley and Paris together with the enhancement graph. If you want to work with the REST interface directly, you may also post the text with the cURL command below. The resulting enhancement RDF will be in turtle notation.</p>
+<div class="codehilite"><pre><span class="c">% curl -X POST -H "Accept: text/turtle" -H "Content-type: text/plain" \</span>
+ <span class="o">--</span><span class="n">data</span> "<span class="n">The</span> <span class="n">Stanbol</span> <span class="n">enhancer</span> <span class="n">can</span> <span class="n">detect</span> <span class="n">famous</span> <span class="n">cities</span> <span class="n">such</span> <span class="n">as</span> <span class="n">Paris</span> <span class="n">and</span> <span class="n">people</span> <span class="n">such</span> <span class="n">as</span> <span class="n">Bob</span> <span class="n">Marley</span><span class="p">.</span>" <span class="o">\</span>
+ <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">localhost</span><span class="p">:</span>8080<span class="o">/</span><span class="n">enhancer</span>
+</pre></div>
+
+
+<h2 id="configuration">Configuration</h2>
+<p>The "default" enhancement chain includes the following, by default active Enhancement Engines:</p>
+<ul>
+<li>one engine for conversions from various document formats to plain text</li>
+<li>one for detection of the language of the text,</li>
+<li>one for named entity extractions from the content item and</li>
+<li>one engine configured to link the extracted entities to DBpedia entities.</li>
+</ul>
+<p>You can use the <a href="http://localhost:8080/">OSGI console (http://{yourdomain}:{port}/)</a> (user/pwd: admin/admin) of your running Stanbol instance to activate and configure additional engines. Additional engines provide support keyword extraction together with a better language support, for geonames, zemanta or opencalais. See the overview of available Apache Stanbol <a href="enhancer/engines/list.html">Enhancement Engines</a>.</p>
+<p>Another feature of this Apache Stanbol version is to manage and locally cache external entity repositories such as DBpedia as well as the possibility to use custom vocabularies as linking target repositories. Read more about this scenario <a href="customvocabulary.html">using custom vocabularies</a>.</p>
+<h2 id="advanced-explore-apache-stanbol-full-launcher">Advanced: Explore Apache Stanbol "full" launcher</h2>
+<p>The full (including experimental) features of Apache Stanbol can be accessed via Apache Stanbol's "full launcher". See the <a href="components.html">list of all available components</a> and their features.</p>
+<p>To start the full launcher, you just have to execute its JAR via the following command:</p>
+<div class="codehilite"><pre><span class="c">% java -Xmx1g -jar full/target/org.apache.stanbol.launchers.full-{snapshot-version}-SNAPSHOT.jar</span>
+</pre></div>
+ </div>
+
+ <div id="footer">
+ <div class="copyright">
+ <p>
+ Copyright © 2010 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Stanbol and the Apache feather and Stanbol logos are trademarks of The Apache Software Foundation.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>