Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] equivalent class and N-ary Relations

Timothy Redmond tredmond at
Thu Feb 16 11:59:39 PST 2012

It sounds like you are talking about something like the attached 
ontology.  (I used the Manchester syntax for clarity.)  This ontology 
has two definitions:

    Class: Diagnosis_Relation_20

             (diagnosis_value some Disease)
              and (diag_prob only xsd:int[>= 20])

    Class: Diagnosis_Relation_40

             (diagnosis_value some Disease)
              and (diag_prob only xsd:int[>= 40])

In this case it can be deduced that Diagnosis_Relation_40 is a subclass 
of Diagnosis_Relation_20.

Putting this into English, I would say that Diagnosis_Relation_40 is the 
class containing all individuals that have a diagnosis_value that 
belongs to the Disease class and such that all their diag_prob values 
are integers greater than or equal to 40.

Suppose that we have an individual 'i' that is a member of 
Diagnosis_Relation_40.  Since the individual 'i' has all its diag_prob 
values greater than or equal to 40, it also follows that all the 
diag_prob values for the individual 'i' are also integers greater than 
or equal to 20.  Thus 'i' satisfies the requirements for belonging to 
Diagnosis_Relation_20:  all its dig_prob values are integers greater 
than or equal to 20 and it has some diagnosis_value in the Disease class.

Does this help?


On 2/16/12 9:29 AM, Arnab Sinha wrote:
> Hi All,
> Here is a situation I would like to present before I put forward my 
> question:
> I tried some minor modifications to the N-ary relations using "Use 
> Case 1" in . I required a 
> numerical probability value (like int[>= 40]) instead of discrete 
> values (like High, Medium or Low) and so took the 
> "diagnosis_probablity" as a data property.
> Now I defined two connecting classes "Diagnosis_Relation_20" and 
> "Diagnosis_Relation_40" as equivalent classes which differs in the 
> minimum probability value. The definition of the class 
> Diagnosis_Relation_20 in OWL is as follows:
> <owl:Class 
> rdf:about="">
> <owl:equivalentClass>
> <owl:Class>
> <owl:intersectionOf rdf:parseType="Collection">
> <owl:Restriction>
> <owl:onProperty 
> rdf:resource=""/>
> <owl:someValuesFrom 
> rdf:resource=""/>
> </owl:Restriction>
> <owl:Restriction>
> <owl:onProperty 
> rdf:resource=""/>
> <owl:allValuesFrom>
> <rdfs:Datatype>
> <owl:onDatatype rdf:resource="&xsd;int"/>
> <owl:withRestrictions rdf:parseType="Collection">
> <rdf:Description>
> <xsd:minInclusive rdf:datatype="&xsd;integer">20</xsd:minInclusive>
> </rdf:Description>
> </owl:withRestrictions>
> </rdfs:Datatype>
> </owl:allValuesFrom>
> </owl:Restriction>
> </owl:intersectionOf>
> </owl:Class>
> </owl:equivalentClass>
> </owl:Class>
> Now, invoking the reasoner infers class Diagnosis_Relation_20 as 
> superclass of Diagnosis_Relation_40. I am unable to understand the 
> explanation of this inference. It seems something obvious but I want 
> to get the detailed explanation. If someone can help me out, it would 
> be really nice.
> Have a good day!
> Thanks in advance,
> Arnab.
> _______________________________________________
> protege-owl mailing list
> protege-owl at
> Instructions for unsubscribing:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Diagnosis.owl
URL: <>

More information about the protege-owl mailing list