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] owl:hasValue

Steve Wilder steven.m.wilder at lmco.com
Thu May 29 07:51:21 PDT 2008


I like the automatic inference better.  I tried classifying the taxonomy
using a reasoner, but that didn't seem to do the trick.

How can I get my protege server to do this kind of automatic inference
on hasValue?

Steve

Thomas Russ wrote:
> On May 27, 2008, at 9:34 AM, Steve Wilder wrote:
> 
>> I have a problem that I'm trying to diagnose.
>>
>> I have the following definition in OWL:
> 
>    AAR <= hasAssociatedMissions has AEW_instance
>    ...
>> If I create an instance of AAR in the Protege editor, the new instance
>> properly fills in the hasAssociatedMissions property with  
>> AEW_instance.
> 
> That is because the instance editor has a special purpose routine that  
> looks for fillers specified by hasValue restrictions on the instance.   
> In effect, there is some implicit inference done by the editor to  
> figure out the slot value.
> 
>> However, when using the Protege client/server in my program, I'm not
>> seeing this property filled in correctly for any instances of AAR.
>>
>> AAR myAAR = myFactory.createAAR("myAAR");
>> System.out.println("AAR: " + myAAR + " has associated missions: " +
>> myAAR.getHasAssociatedMissions().size());
>>
>> returns:
>>
>> AAR: DefaultAAR(myAAR of [DefaultOWLNamedClass(aco:AAR,  
>> FrameID(12:12042
>> 1))]) has associated missions: 0
> 
> That is because this does not do any inference.  It looks only at the  
> assserted information.
> 
> You can get the hasValue restrictions by using the  
> "getHasValuesOnTypes" method.  Note that this is a moderately  
> expensive method to call.
> 
> Ex:
> 
>      OWLProperty prop = model.getOWLProperty("hasAssociatedMissions");
>      myAAR.getHasValuesOnTypes(prop);
> 
> 
> 
> 
> 
>   
>   
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
> 
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: swilder.vcf
Type: text/x-vcard
Size: 187 bytes
Desc: not available
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20080529/dbbead53/attachment.vcf>


More information about the protege-owl mailing list