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] Using datatype properties in 3.4

babar shahzad babarathotmail at
Tue Mar 10 11:25:54 PDT 2009


Thank you Samson, really thank you for your interest in my problem, that is continued....

Babar Shahzad Chaudary, 
Deptt of Information Processing
University of Oulu, Finland.

----- Original Message ----
From: Samson Tu <swt at>
To: protege-owl at
Sent: Tuesday, March 10, 2009 8:16:31 PM
Subject: Re: [protege-owl] Using datatype properties in 3.4

In that case, you are out of luck with Protege 3.4, which implements OWL 
1.0.  OWL 1.0 doesn't allow that kind of range restriction. That's one 
reason OWL 2.0 was developed.


babar shahzad wrote:
> I was too optimistic when same thing in mind only, using for my range problem(I knew this courtesy to u already). But when I envoke it, I realized that by this, all Shelves will end up in same boundary. 
> ' locationX ' is property used by all Shelves to represent their starting X-axes. If all they implement same property, they will end up within same bounds, 0.0-10.0. 
> I need to add a restriction of range specifically for each Shelve, not a common bound on values that a property overall can take.
> Restrictions in 3.4, as far as I understood, are made keeping datatype properties in mind only. I think only cardinality looks useful for datatype properties, may be.
> See this,
> --------------------------' PizzaSize that hasDiameter some int[>=0, <11] ’
> --------------------------' PizzaSize that hasDiameter some int[>=11, <21 ] ’
> ...
> ...
> how we represent it in 3.4.....??
> its my problem.
> thank you.

protege-owl mailing list
protege-owl at

Instructions for unsubscribing: 


More information about the protege-owl mailing list