Author: enridaga
Date: Fri Nov 4 17:14:40 2011
New Revision: 1197674
URL: http://svn.apache.org/viewvc?rev=1197674&view=rev
Log:
Fixed a type (Employer->Employee)
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/reasoners.mdtext
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/reasoners.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/reasoners.mdtext?rev=1197674&r1=1197673&r2=1197674&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/reasoners.mdtext
(original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/reasoners.mdtext
Fri Nov 4 17:14:40 2011
@@ -171,8 +171,8 @@ The following example shows the use of c
</rdfs:subClassOf>
</owl:Class>
-<!-- Employers are all who #worksAt any kind of Organization
(owl:equivalentClass) -->
-<owl:Class rdf:about="#Employer">
+<!-- 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" />
@@ -183,13 +183,13 @@ The following example shows the use of c
</pre>
<a
href="https://raw.github.com/enridaga/reasoners.examples/master/enridaga.reasoners.examples/owl/some-values-from.xml";
target="_blank">download it</a>
-We expect an OWL reasoner to state that John is an <tt>Employer</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>.
+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>.
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 employer must have some features: firstname, familyname, email
+<!-- any Employee must have some features: firstname, familyname, email
and worksAt (in one of the allowed places) -->
-<owl:Class rdf:about="#Employer">
+<owl:Class rdf:about="#Employee">
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
@@ -207,7 +207,7 @@ The <tt>/owl</tt> service support the mo
<owl:someValuesFrom
rdf:resource="&rdfs;Literal" />
</owl:Restriction>
<!-- -->
- <!-- Let's say that Employers can work only
in #Rome , #Catania and
+ <!-- Let's say that Employees can work only
in #Rome , #Catania and
#Bologna -->
<owl:Restriction>
<owl:onProperty
rdf:resource="#worksAt" />
@@ -246,11 +246,11 @@ The <tt>/owl</tt> service support the mo
</owl:AllDifferent>
-<!-- enridaga, to be an employer, must fulfill the restrictions defined
- for the class #Employer. -->
+<!-- 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 #Employer. -->
+ to result as #Employee. -->
<firstname>Enrico</firstname>
<familyname>Daga</familyname>
<email>[email protected]</email>
@@ -258,7 +258,7 @@ The <tt>/owl</tt> service support the mo
<!-- 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="#Employer"
+ <!-- <worksAt rdf:resource="#Moricone" /> <rdf:type
rdf:resource="#Employee"
/> -->
</Person>
</pre>
