instance occurances restrictions

6 messages Options
Embed this post
Permalink
ED-633

instance occurances restrictions

Reply Threaded More More options
Print post
Permalink
hi,

could you please tell me how i represente the fact that on my body ontology i
should'n have more than one heart ?

it should be on the instance layer ... is it possible, to say that a concept
shouldn't have more than one instance ?


thanks ;)



_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
Thomas Russ

Re: instance occurances restrictions

Reply Threaded More More options
Print post
Permalink

On Jun 26, 2009, at 12:53 AM, ED wrote:

> hi,
>
> could you please tell me how i represente the fact that on my body  
> ontology i
> should'n have more than one heart ?

You use a cardinality restriction.

Make it a necessary condition of the Body class that there be exactly  
one heart.*

-Tom.
* Unless you are a Time Lord....
_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
Faraz Fallahi

Re: instance occurances restrictions

Reply Threaded More More options
Print post
Permalink
keyword only, i'd guess

2009/6/26 Thomas Russ <[hidden email]>

On Jun 26, 2009, at 12:53 AM, ED wrote:

> hi,
>
> could you please tell me how i represente the fact that on my body
> ontology i
> should'n have more than one heart ?

You use a cardinality restriction.

Make it a necessary condition of the Body class that there be exactly
one heart.*

-Tom.
* Unless you are a Time Lord....
_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03


_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
Vivek Anandan

Re: instance occurances restrictions

Reply Threaded More More options
Print post
Permalink
Use restrictions 

On Sat, Jun 27, 2009 at 4:17 PM, Faraz Fallahi <[hidden email]> wrote:
keyword only, i'd guess

2009/6/26 Thomas Russ <[hidden email]>

On Jun 26, 2009, at 12:53 AM, ED wrote:

> hi,
>
> could you please tell me how i represente the fact that on my body
> ontology i
> should'n have more than one heart ?

You use a cardinality restriction.

Make it a necessary condition of the Body class that there be exactly
one heart.*

-Tom.
* Unless you are a Time Lord....
_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03


_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03




--
Regards,
Vivekanandan Ramachandran.

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
ED-633

Re: instance occurances restrictions

Reply Threaded More More options
Print post
Permalink
Well i don't have something like the body, actually i have only
sibling classes ... i'll explain you , i have a systeme composed of 5
sub-systems, with are all sub-classes of thing and none of theme is a
subclass of another super-class (they are all siblings ) how could
i say that i want only one occurrence of a kind of classes
... of it's instances or of that classe as well !

Well i don't have something like the body,actually i have only
sibling classes ... i'll explain you , i have a systeme composed
of 5 sub-systems, with are all sub-classes of thing and none
of theme is a subclass of another super-class (they are all siblings )
 how could i say that i want only one occurrence of a kind of classes...
*of it's instances or of that classe as well !


i have an other problem with restrictions ;

i have a class named "" this kind of bus must have at each
extremity one (and exactly one)  "lever" class and on the
other extremity one (and exactly one) class "stomach" ...
 i did it with and "exactly 1"   restriction but when
 i want to instantiate the lever classe that give me
the choice to have relation with two instances of liver ou stomach ...
wich should be prohibited !

1 Liver <----- vein ---->  1 stomach  : want i want and nothing else !

what i have the choixe to do now  --->

1 stomach <----- vein ---->  1 stomach  : should be forbiden

1 Liver <----- vein ---->  1 liver  : should be forbiden


i hope that i've been clear ... do you have any idea ?

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
Thomas Russ

Re: instance occurances restrictions

Reply Threaded More More options
Print post
Permalink

On Jun 29, 2009, at 1:07 AM, ED wrote:

> i have a class named "" this kind of bus must have at each
> extremity one (and exactly one)  "lever" class and on the
> other extremity one (and exactly one) class "stomach" ...
> i did it with and "exactly 1"   restriction but when
> i want to instantiate the lever classe that give me
> the choice to have relation with two instances of liver ou stomach ...
> wich should be prohibited !
>
> 1 Liver <----- vein ---->  1 stomach  : want i want and nothing else !
>
> what i have the choixe to do now  --->
>
> 1 stomach <----- vein ---->  1 stomach  : should be forbiden
>
> 1 Liver <----- vein ---->  1 liver  : should be forbiden
>
>
> i hope that i've been clear ... do you have any idea ?

1)  Make sure you tell OWL that Stomach and Liver are disjoint classes.
2)  Create a subclass of Vein, perhaps called HepaticVein.
3)  On the class HepaticVein include the restrictions
       endpoint someValuesFrom Stomach
       endpoint someValuesFrom Liver

     This will require at least one filler.  You can't restrict it to  
exactly one filler of that type using OWL 1.0, although you could with  
OWL 2.0

Perhaps, since veins are directional, you could instead use

      startpoint allValuesFrom Stomach
      startpoint exactly 1
      endpoint allValuesFrom Liver
      endpoint exactly 1

which will indicate that a consistent model will have only one stomach  
at the start and one liver at the end.

You would also need to make sure that any individuals you create are  
allDifferent from the other individuals.

_______________________________________________
protege-owl mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03