Author: anuzzolese
Date: Fri Jan 20 15:37:32 2012
New Revision: 1233964

URL: http://svn.apache.org/viewvc?rev=1233964&view=rev
Log:
[STANBOL-453] Applied patch proposed by Alberto Musetti.
It contains 
        * the "Features" section for the Refactor documentation;
        * the removal of any reference to IKS project in every section and from 
the image refactor.png.

Modified:
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules.mdtext
    
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules/refactor.mdtext
    incubator/stanbol/site/trunk/content/stanbol/images/rules/refactor.png

Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules.mdtext
URL: 
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules.mdtext?rev=1233964&r1=1233963&r2=1233964&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules.mdtext 
(original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules.mdtext Fri 
Jan 20 15:37:32 2012
@@ -13,15 +13,16 @@ Any other entity not satisfying the cons
 ### Vocabulary harmonization
 
 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 [Stanbol 
OntoNet](../ontologymanager/ontonet.html).
+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 [Stanbol OntoNet](../ontologymanager/ontonet.html).
 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.
+inference as refactoring rules in order harmonize external data to the 
Stanbol's ontologies.
 
-Also, Stanbol Rules can be used to derive new knowledge or integrate 
information from different semantically enhanced contents.
+Also, Stanbol Rules can be used to derive new knowledge or integrate 
information 
+from different semantically enhanced contents.
 
 ## Features
 

Modified: 
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules/refactor.mdtext
URL: 
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules/refactor.mdtext?rev=1233964&r1=1233963&r2=1233964&view=diff
==============================================================================
--- 
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules/refactor.mdtext 
(original)
+++ 
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/rules/refactor.mdtext 
Fri Jan 20 15:37:32 2012
@@ -13,37 +13,55 @@ The Refactor is a service which allows t
 ### Vocabulary harmonization
 
 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 [Stanbol 
OntoNet](../ontologymanager/ontonet.html).
+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 [Stanbol 
OntoNet](../ontologymanager/ontonet.html).
 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.
+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.
 
 <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>
 
 We can specify a concrete scenario for a better understanding of the
-Refactor. Suppose we have configured the IKS (i.e. [Stanbol 
EntityHub](../entityhub.html)) in order
+Refactor. Suppose we have configured the CMS (i.e. [Stanbol 
EntityHub](../entityhub.html)) 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.
 
 ## Features
 
-todo...
+In the Refactor rules are interpreted as [SPARQL 
CONSTRUCT](http://www.w3.org/TR/rdf-sparql-query/#construct) 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. 
+
+As an example, we can take in account the following rule:
+
+       prefix kn = <http://foo.org/kinship#> . 
+       uncleRule[ has(kn:parent, ?x, ?y) . has(kn:sibling, ?y, ?z) -> 
has(kn:uncle, ?x, ?z) ]
+
+The rule above is transformed into the following SPARQL CONSTRUCT query: 
+       PREFIX kn: <http://foo.org/kinship#>
+       CONSTRUCT { ?x kn:uncle ?z }
+       WHERE { 
+               ?x kn:parent ?y .
+               ?y kn:sibling ?z
+       }
+       
+The SPARQL engines used internally by the Refactor for running rules is 
[Apache Jena ARQ](http://incubator.apache.org/jena/documentation/query/)
 
+We remand any detail about the syntax and the expressivity of the Stanbole 
Rule language to its [section](./language.html).  
+       
 ## Service Endpoints
 
 The Refactor RESTful API is structured as follows:

Modified: incubator/stanbol/site/trunk/content/stanbol/images/rules/refactor.png
URL: 
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/images/rules/refactor.png?rev=1233964&r1=1233963&r2=1233964&view=diff
==============================================================================
Binary files - no diff available.


Reply via email to