General information

Name	OnlynessIsLoneliness (OIL)
Also known as
Author(s)
SubmittedBy	Catherine Roussey, Oscar Corcho

Description

Motivation	We have identified a set of patterns that are commonly used by domain experts in their DL formalisations and OWL implementations, and that normally result in unsatisfiable classes or modelling errors. As aforementioned all these antipatterns come from a misuse and misunderstanding of DL expressions by ontology developers. Thus they are all Logical AntiPatterns (LAP): they are independent from a specific domain of interest, but dependent on the expressivity of the logical formalism used for the representation. We have categorized them into three groups:
Aim	The ontology developer created a universal restriction to say that C1 instances can only be linked with property R to C2 instances. Next, a new universal restriction is added saying that C1 instances can only be linked with R to C3 instances, with C2 and C3 disjoint. In general, this is because the ontology developer forgot the previous axiom in the same class or in the parent class.
Solution description	C1 subClassOf R only C2; C1 subClassOf R only C3; C2 disjointWith C3 If it makes sense, we propose to the domain expert to transform the two universal restrictions into only one that refers to the disjunction of C2 and C3. C1 subClassOf R only (C2 or C3); C2 disjointWith C3
Elements
Implementation
Reusable component
Component type

Problem example	Transtitional_Waters subClassOf is_nearby only Sea_Waters; Transitional_Waters subClassOf is_nearby only River_Mouths; River_Mouths disjointWith Sea_Waters see Aguas_de_Transicion concept in hydrontology.
Pattern solution example	http://www.dia.fi.upm.es/~ocorcho/OWLDebugging/
Consequences	Transtitional_Waters subClassOf is_nearby only (Sea_Waters or River_Mouths); River_Mouths disjointWith Sea_Waters

Scenarios about OnlynessIsLoneliness (OIL)

No scenario is added to this Content OP.

Reviews about OnlynessIsLoneliness (OIL)

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 5347) takes in account the reviews: none

	Submission to event WOP2009:Main