Author: buildbot
Date: Mon Jan 16 11:29:35 2012
New Revision: 802712
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/store.html
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
Mon Jan 16 11:29:35 2012
@@ -20,7 +20,7 @@
-->
<link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
- <title>Apache Stanbol - Refactor</title>
+ <title>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>
@@ -56,18 +56,44 @@
</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>
-<p>Supposing we have configured the IKS (i.e. Stanbol EntityHub) in order to
fetch entities about persons from DBpedia. Now we want to represent these
entities adopting the vocabulary from schema.org and produce schemaOrg Rich
Snippets in order to provide to the IKS search engine optimization
capabilities. What we need to do is to write a recipe and calling the Refactor
via HTTP REST passing to it the recipe itself and the entities we have fetched
frol Linked Data.</p>
-<h2 id="usage">Usage</h2>
-<h3 id="service_endpoints">Service Endpoints</h3>
+ <h1 class="title"></h1>
+ <h2 id="usage_scenarios">Usage Scenarios</h2>
+<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>.
+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>
+<p><figure>
+<img alt="Apache Stanbol Components" src="../../images/rules/refacor.png" />
+<figcaption>Figure 1: the refactor is used to
+ align external data to the ontologies used in the IKS.</figcaption>
+</figure></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
+to fetch entities about persons from DBpedia. Now we want to represent these
+entities adopting the vocabulary from schema.org and produce
+schemaOrg Rich Snippets in order to provide to the IKS search engine
+optimization capabilities. 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>
+<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>
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/store.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/store.html
(original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/store.html
Mon Jan 16 11:29:35 2012
@@ -66,7 +66,7 @@
</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>
+<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>
