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] Automatic domain/range and sub property assignments in P4 don't work

Tania Tudorache tudorache at
Fri Jan 4 14:03:55 PST 2008

Please repost your message on the Protege 4 feedback list:


enki wrote:
> Hi there,
> I am new to Protege. Yesterday I downloaded Protege 4.0 alpha; started 
> reading and going through the tutorial "ProtegeOWLTutorial-p4.0.pdf" 
> from the CO-ODE site. I have come across some inconsistenties between 
> what I see and what I supposedly have to see:
> 1) No automatic assignment of sub properties:
> In the Inverse Properties section (p.29), it says:
> Press the ‘Add inverse property’ button on the ‘Inverse Property’ 
> view. This
> will pop up a dialog that contains information about the newly created 
> property.
> Use this dialog to rename the property isBaseOf and the close the 
> dialog window
> (using the operating system close window button on the title bar). 
> Notice that the
> isBaseOf property has been created as a sub property of the 
> isIngredientOf property.
> This corresponds to the fact that hasBase is a sub property of 
> hasIngredient, and
> isIngredientOf is the inverse property of hasIngredient.
> What I see, however, is just a button to add inverse property which 
> does not perform anything automatically. There is nothing to rename, 
> but only properties to choose from. I can create new properties from 
> the "add inverse property" window opened, however they create this 
> property independently, without being aware that it is supposed to be 
> a sub property.
> 2) No automatic assignment of domains and ranges:
> In the tutorial it is mentioned that domain for a property is the 
> range for its inverse, and the range for a property is the domain for 
> its inverse. It says on p.38:
> Notice that Protege has automatically filled in domain and range of 
> the isToppingOf property because the domain and range of the inverse 
> property were specified. The range of isToppingOf is the domain of the 
> inverse property hasTopping, and the domain of isToppingOf is the 
> range of the inverse property hasTopping.
> Again, similar to previous issue I mentioned, no automatic domain and 
> range assignment is done for the inverse properties.
> After that I installed Protege3.3.1 and saw that it does not have 
> these problems. Are these features not yet implemented in Protege 4.0 
> or am I missing something here? I really liked the interface of 4.0 
> and don't know if I should uninstall it and continue to learn on 3.x.
> Thanks,
> dj_enkidu
> ------------------------------------------------------------------------
> Looking for last minute shopping deals? Find them fast with Yahoo! 
> Search. 
> <*> 
> ------------------------------------------------------------------------
> _______________________________________________
> protege-owl mailing list
> protege-owl at
> Instructions for unsubscribing: 

More information about the protege-owl mailing list