W3C home > Mailing lists > Public > www-rdf-logic@w3.org > July 2003

Defining "flavors" of subClassOf in OWL ?

From: Bernard Vatant <bernard.vatant@mondeca.com>
Date: Thu, 10 Jul 2003 18:19:36 +0200
To: "Www-Rdf-Logic@W3.Org" <www-rdf-logic@w3.org>
Cc: Frédéric Delahaye <frederic.delahaye@mondeca.com>
Message-ID: <GOEIKOOAMJONEFCANOKCOEBBCCAA.bernard.vatant@mondeca.com>

In Mondeca ITM internal management of classes, we have a generic
functionality somehow equivalent to the distinction between "abstract" and
"concrete" classes in Protégé. However, the distinction is not made by
typing the classes themselves, but by typing the class-subClass
relationship (aka Topic Map association). This means we have two "flavors"
of subclassing, supporting different technical treatments.

Trying to represent this in OWL, I defined two properties like

p1 rdfs:subPropertyOf rdfs:subClassOf
p2 rdfs:subPropertyOf rdfs:subClassOf

Now if I have three classes X, Y, Z such as (X p1 Y) and (Y p2 Z)

I expect from the semantics of subPropertyOf that an OWL validator would
(X subClassOf Y) (Y subClassOf Z) (X subClassOf Z)

Meaning if an ObjectProperty q has been declared e.g. of range Z, it should
be validated if used with values in X.

Not quite sure about it, I've tested precisely that situation on an example
[1], and my two favourite OWL on-line validators seem to differ on the
validation results.

http://phoebus.cs.man.ac.uk:9999/OWL/Validator seems happy with it.
http://owl.bbn.com/validator/ is not, and sends back a bunch of "range
mismatch" error.

Is this a bug in the validator, or is it a borderline example, or is it
that subtyping "subClassOf" is altogether invalid in OWL, or what?

A bottom line question is to know if that could be considered a
recommended/neutral/bad practice.

Thanks for your help

Bernard Vatant
Senior Consultant
Knowledge Engineering
Mondeca - www.mondeca.com

Received on Thursday, 10 July 2003 12:26:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 11:10:40 UTC