W3C home > Mailing lists > Public > semantic-web@w3.org > September 2006

Inheriting property restrictions

From: ben syverson <w3@likn.org>
Date: Wed, 6 Sep 2006 16:23:21 -0500
Message-Id: <86CF9F6F-DBD7-4699-9997-BCDBC8F3D962@likn.org>
To: semantic-web@w3.org

Hi everyone,

I have a two-part question that the OWL specs don't seem to address.

1. Does a subClass inherit its parents' property restrictions? I  
assume it does, but what if the subclass declares a restriction of  
its own for the same property? Which restriction should be paid  
attention to?

For example, say I have a class "Car" which restricts the property  
"PaintColor" to the class "Colors":
<owl:Class rdf:ID="Car">
			<owl:onProperty rdf:resource="#PaintColor" />
			<owl:allValuesFrom rdf:resource="#Colors" />

But then a subclass of "Car" is added, named "WebCar," and it  
restricts the same property (PaintColor) to "HTMLColors," which is a  
totally different class than "Colors."
<owl:Class rdf:ID="WebCar">
	<rdfs:subClassOf rdf:resource="#Car" />
			<owl:onProperty rdf:resource="#PaintColor" />
			<owl:allValuesFrom rdf:resource="#HTMLColors" />

I'm not even sure if that's the correct way to express what I'm  
saying in RDF/XML, but you get the picture.

Which restriction on PaintColor should be heeded?

2. If you were building a tool that output OWL, would it make sense  
to prevent the user from creating the restriction that "WebCar's  
PaintColor must be from HTMLColors," if we knew that a parent of  
WebCar already had a restriction on PaintColor?

Thanks in advance!

- ben syverson
Received on Wednesday, 6 September 2006 21:23:48 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:44:58 UTC