Author: buildbot
Date: Fri Jan 20 15:37:43 2012
New Revision: 802964
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html
websites/staging/stanbol/trunk/content/stanbol/images/rules/refactor.png
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules.html
(original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules.html Fri
Jan 20 15:37:43 2012
@@ -67,14 +67,15 @@ Any other entity not satisfying the cons
</p>
<h3 id="vocabulary_harmonization">Vocabulary harmonization</h3>
<p>Supposing we want to use some dataset in Linked
-Data as external knowledge bases for the IKS. Now the problem how to use data
-from those datasets expressed with some external and heterogeneous vocabularies
-or ontologies within the IKS has. Furthermore the IKS has its own way to
-formalize knowledge, namely the its Ontology Network managed by <a
href="../ontologymanager/ontonet.html">Stanbol OntoNet</a>.
+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>
+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>
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html
Fri Jan 20 15:37:43 2012
@@ -67,32 +67,49 @@
<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 the IKS. Now the problem how to use data
-from those datasets expressed with some external and heterogeneous vocabularies
-or ontologies within the IKS has. Furthermore the IKS has its own way to
-formalize knowledge, namely the its Ontology Network managed by <a
href="../ontologymanager/ontonet.html">Stanbol OntoNet</a>.
+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 IKS can benefit from the Refactor showing how external data can be
-aligned and used within the IKS.</p>
+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 the IKS.</figcaption>
+<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 IKS (i.e. <a
href="../entityhub.html">Stanbol EntityHub</a>) in order
+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 IKS. What we need to do is to write a recipe
and call
+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>todo...</p>
+<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:
+ PREFIX kn: <a href="http://foo.org/kinship#";>http://foo.org/kinship#</a>
+ CONSTRUCT { ?x kn:uncle ?z }
+ WHERE {
+ ?x kn:parent ?y .
+ ?y kn:sibling ?z
+ }</p>
+<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>
Modified:
websites/staging/stanbol/trunk/content/stanbol/images/rules/refactor.png
==============================================================================
Binary files - no diff available.
