W3C home > Mailing lists > Public > public-owl-wg@w3.org > November 2007

Axiom prioritization

From: Kashyap, Vipul <VKASHYAP1@PARTNERS.ORG>
Date: Thu, 29 Nov 2007 14:32:06 -0500
Message-ID: <DBA3C02EAD0DC14BBB667C345EE2D1240180CB21@PHSXMB20.partners.org>
To: <public-owl-wg@w3.org>


This probably might be out of scope for this WG, but just wanted to feedback on
this aspect.

I have a use case that might need axiom prioritization due to misuse of property
chain axioms in situations where there are a few exceptions
consider the following set of axioms:

Class1 subClassOf (containedIn some Class2)
Class2 subClassOf (coveredBy some Class3)
containedIn o coveredBy => coveredBy
Class1 disjointWith (coveredBy some Class3)

The reason of the inconsistency is the sub property chain axiom propagates the
converedBy property
so that we can infer:

Class1 subClassOf (some coveredBy Class3)

In general, the coveredBy property can apply to the complete containment
hierarchy, but there are a few exceptions,
one of which is expressed using the disjointness axiom.

As is, the Fact++ reasoner declares this KB inconsistent.

Was wondering if the reasoner could give "higher priority" to the disjointness
axiom and not propagate the property to that particular class?

Any alternative ways of remodeling this?



The information transmitted in this electronic communication is intended only
for the person or entity to whom it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or other
use of or taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you received this
information in error, please contact the Compliance HelpLine at 800-856-1983 and
properly dispose of this information.
Received on Thursday, 29 November 2007 19:32:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:42:00 UTC