W3C home > Mailing lists > Public > public-owl-dev@w3.org > April to June 2010

Re: The notion of a "classification criterion" as a class

From: Alan Rector <rector@cs.man.ac.uk>
Date: Thu, 22 Apr 2010 09:36:05 +0100
Cc: ontolog-forum@ontolog.cim3.net, OwlED-list <public-owl-dev@w3.org>, Robert Stevens <robert.stevens@manchester.ac.uk>
Message-Id: <7E169C29-626B-48CB-BF05-77DA42DD0518@cs.man.ac.uk>
To: Benedicto Rodriguez <br205r@ecs.soton.ac.uk>
Benedicto


For a generic reference on the mechanism we call "Normalisation" which  
addresses this issue, see
A. Rector 2003. Modularisation of domain ontologies Implemented in  
description logics and related formalisms including OWL. Knowledge  
Capture 2003. 121-128.
http://www.cs.man.ac.uk/~rector/papers/Modularisation-normalisation-rector.pdf

Robert Stevens, copied on this email, has an extensive family history  
ontology that addresses all these issues.

In principle we would address issues of this sort following the  
reference above  as something like:

Independent_entity
	...
		Person

Dependent Entity
	Value_partition
		Gender
			Male
			Female

Plus properties such as
	has_child
	has_sibling

Then Parent == Person that has_child some Person.
Man == Person that has_gender some Male
etc.
(If you prefer you can see individuals for values such as male and  
female; there are
tradeoffs in either approach.  See the W3C Best Practice note on  
"Specified Values".
http://www.w3.org/TR/swbp-specified-values/ )

It would be nice to define the relation has_sibling in terms of  
has_child, but this is tricky, since if you use the natural  
representation:

inv(has_child) o has_child --> has_sibling

then everybody is their own sibling. There's no easy way around this.

As to categories such as "Person by Gender" that might be defined in  
OWL as
"Person that has_gender some Gender", there are two problems: one  
technical and one philosophical.

The technical problem is that if you have made the generic assertion  
that all people have genders,
	Person subclassOf has_gender some Gender
Then
	Person_by_gender is logically equivalent to Person.

If you are willing to forgo the generic statement, then you can create  
the subclass.

The Philosophical problem concerns the status of classes such as  
"Person by Gender" which many ontologists deplore as not being a  
proper "universal".  From a purely logical point of view, this need  
not be a problem.  In practice such constructs are commonly used in  
OWL KBs for convenience, but best defined to reflect the developer's  
intentions, so that as the KB evolves, the reasoner keeps the KB  
consistent with those intentions.

Regards

Alan


On 15 Apr 2010, at 20:30, Benedicto Rodriguez wrote:

> Hello everyone,
>
> Apologies for cross-posting but I thought the email might be  
> relevant to both mailing lists: ontolog-forum@ontolog.cim3.net and public-owl-dev@w3.org 
> .
>
> I am trying to put together an ontology design pattern (or  
> combination of patterns) with the intent of modeling multiple  
> alternative classification criteria of a domain concept.  At this  
> point, I have to commit my focus to OWL (or more specifically, to an  
> expressivity level within OWL-DL).
>
> In the process I have come across what I think it is an interesting  
> modeling scenario. Let me use a simple example to describe it  
> extracted from [1].  Consider the following set of classes (as a  
> subset of a larger ontology model) in the popular domain of "family  
> relationships" organized according to the following subsumption  
> hierarchy:
>
> :Person
>     |-- :Man
>     |-- :Woman
>     |-- :Parent
>     |-- :Child
>     |-- :Sibling
>
> We could argue that this inheritance structure is not satisfactory  
> because different concepts are represented by classes at the same  
> level.  That is, the concept of gender, represented by the  
> classes :Man and :Woman, and the concept of kinship relationships,  
> represented by the classes :Parent, :Child and :Sibling.  In that  
> sense, the concepts of gender and kinship could be seen as two  
> different classification criteria for all the subclasses of :Person.
>
> The issue that I am trying to solve deals with how to incorporate  
> the representation of these classification criteria concepts into  
> the ontology model.
>
> An initial approach (kind of intuitive to me) would be two represent  
> the two classification criteria as classes (say :PersonByGender  
> and :PersonByKinship) and regroup all the subclasses of :Person  
> accordingly. The result would look like:
>
> :Person
>     |-- :PersonByGender
>     |   |-- :Man
>     |   |-- :Woman
>     |-- :PersonByKinship
>         |-- :Parent
>         |-- :Child
>         |-- :Sibling
>
> However, I see a conceptual problem with this model regarding the  
> subsumption relation between :Person and the classification criteria  
> classes :PersonByGender and :PersonByKinship, given that:
>
> - Who would be the individuals of classes such as :PersonByGender  
> and :PersonByKinship? For example, if we consider :John and  
> individual of type :Man, we can say that :John is also of  
> type :Person.  But does it make sense to say that :John is of  
> type :PersonByGender???
>
> - Are these classes :PersonByGender and :PersonByKinship in fact  
> meta-classes? (If I could use an analogy with object-oriented  
> design, it is as if these two classes could be seen as abstract or  
> deferred classes).
>
> This type of modeling scenario can be found in many concepts from  
> various domains (essentially any concept whose individuals/instances  
> could be grouped according to multiple different classification  
> criteria). Below is another popular example in the OWL literature  
> modified to fit into the same scenario and illustrate the problem [2]:
>
> :Wine
>     |-- :WineByColor
>     |   |-- :WhiteWine
>     |   |-- :RedWine
>     |   |-- (etc.)
>     |-- :WineByGrape
>          |-- :PinotGrigioWine
>          |-- :MerlotWine
>          |-- :CabernetSauvignonWine
>          |-- (etc.)
>
> In this case the classification criteria of :Wine are wines based on  
> their color and wines based on their type of grape.  Like in the  
> example of :Person, the classification criteria classes :WineByColor  
> and :WineByGrape seem intuitive choices to group the rest of all  
> subclasses of :Wine.  However, the subsumption relation  
> between :Wine <-  :WineByColor and :Wine <- :WineByGrape seems  
> problematic.  Who would be the individuals of classes such  
> as :WineByColor or :WineByGrape?
>
> In general terms, the subsumption relation between a :DomainConcept  
> and a :ClassificationCriterion for that concept seems a bit  
> controversial.  For example, It does not seem to fit into one of the  
> 4 kinds of is-a relations defined by Johansson[3] plus  I think it  
> would violate the constraints of the OntoClean evaluation as well.   
> (Even though, for the most part I understand the theory behind the  
> OntoClean method and I think it is very useful, I personally find it  
> a bit difficult to apply coming from a software developer background).
>
> In summary, after this lengthy introduction, below are the questions  
> that I am trying to answer:
>
> - Are subsumption relations such as :Person <- :PersonByGender  
> or :Wine <- :WineByGrape acceptable?
>
> - Can classes such as :PersonByGender or :WineByGrape be “correctly”  
> represented in the ontology model?  That is, classes that correspond  
> to a “classification criterion” and that may not have individuals  
> (or extensional representation) in the real world.
>
> - Are there some guidelines or good-practices on how to represent  
> concepts that correspond to a“classification criterion” of the  
> domain concept that is being modeled?
>
> Thanks a lot for any comments you may have!
>
> (For the record, I'll mention that this work is part of my PhD  
> research.  One aspect of the overall idea is trying to adapt faceted  
> classification design guidelines to ontology design.  The notion of  
> “facet” and “classification criterion” seem to be fairly similar.  
> Identifying a reasonable representation of a “classification  
> criterion” in an ontology can help to bridge the gap between these  
> two design methodologies and that’s the reason for the examples  
> above.  Finally, I would like to present if possible, the overall  
> outcome as an ontology design pattern or combination of them).
>
> Regards,
> Bene Rodriguez-Castro
>
> Postgraduate Student | Intelligence, Agents and Multimedia Group |  
> School of Electronics and Computer Science | University of  
> Southampton | Southampton SO17 1BJ | United Kingdom | Phone: +44 23  
> 8059 4059 | Email: b.rodriguez@ecs.soton.ac.uk
>
> ----
> [1] http://protege.cim3.net/file/pub/ontologies/generations/generations.owl
> [2] http://protege.cim3.net/file/pub/ontologies/wine/wine.owl
> [3] Ingvar Johansson. Four kinds of is_a relations: genus- 
> subsumption, determinable-subsumption, specification, and  
> specialization. In WSPI 2006: Contributions to the Third  
> International Workshop on Philosophy and Informatics, Saarbrucken,  
> 2006.
>

-----------------------
Alan Rector
Professor of Medical Informatics
School of Computer Science
University of Manchester
Manchester M13 9PL, UK
TEL +44 (0) 161 275 6149/6188
FAX +44 (0) 161 275 6204
www.cs.man.ac.uk/~rector
www.co-ode.org
http://clahrc-gm.nihr.ac.uk/
Received on Thursday, 22 April 2010 08:36:38 GMT

This archive was generated by hypermail 2.3.1 : Wednesday, 27 March 2013 09:32:58 GMT