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] Problem with object properties

Chao, Tyrone (US SSA) tyrone.chao at baesystems.com
Mon Aug 20 15:38:58 PDT 2007


Hi Dimitris,

 

Instead of associating a range with the property, does setting a
restriction of the form "some values from <class>" on the property for a
particular class give the behavior you are looking for?

 

Sample Steps:

1)       Select from hierarchy class to associate property (e.g.,
Class1)

2)       In the Properties view, select the icon to "Add this class to
the domain of properties.

3)       Select desired property (e.g. is_associated_with)

4)       the Properties view, select icon to "Create restriction"

5)       Select the property in the Create Restriction dialog box.

6)       Select "someValuesFrom" the Restriction box.

7)       Type name of restricting class in Filler box (e.g., Class2)

8)       Press Ok to apply restriction.

9)       Class1 now has the is_associated_with property with values
restricted to instances of Class2. This restriction only applies to the
property associated with Class1.

 

Tyrone 

 

------------------------------

 

Message: 6

Date: Mon, 20 Aug 2007 19:44:33 +0300

From: "Dimitris Petsas" <dimitris at aueb.gr>

Subject: [protege-owl] Problem with object properties

To: protege-owl at lists.stanford.edu

Message-ID: <000601c7e349$64147ad0$fafffbc3 at DIMITRIS>

Content-Type: text/plain; charset="iso-8859-7"

 

Hi,

I am building an ontology in owl using protege for educational reasons.
I have a problem with object properties. Wishing to show the relation
between one class with another (those classes do not belong to the same
hierarchical structure) i define an object property named:
"is_associated_with". This property takes as domain and range values the
two classes. The problem is that i can't then associate one other class
with another using the same property. This is not allowed in protege.
The only alternative i have found is the creation of another object
property named "is_associated_with2", "is_associated_with3". This
relation is often found in my ontology and i have to create enough
properties of this kind. Is this correct? Is there any better way of
doing this?

 

Thank you for your help

Dimitris

 

------------------------------------------------------------------------
----------------- 
Tyrone Chao
Senior Software Engineer
BAE Systems                                       Phone: (781) 262-4258 
6 New England Executive Park             Fax: (781) 273-9345 
Burlington, MA 01803                          E-Mail:
tyrone.chao at baesystems.com

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-owl/attachments/20070820/a1f34759/attachment.html>


More information about the protege-owl mailing list