OwlReady调用Hermit推理机出现OwlReadyInconsistentOntologyError的解决咨询

First, let's break down what this error means:
OwlReadyInconsistentOntologyError gets thrown when the Hermit reasoner (used by OwlReady under the hood) spots logical contradictions in your ontology. These conflicts make it impossible for the reasoner to reach consistent conclusions, so it aborts and flags the inconsistency.

Root Cause of Your Error #

Looking closely at your ontology file, there are multiple mismatches between the datatype range constraints you defined for properties and the actual datatypes used for individual values:

Here are the conflicting cases:

1. Age property: Defined with range xsd:string, but individual L1 uses an xsd:integer value (18).
2. Qualification property: Defined with range xsd:string, but individual L1 uses an xsd:integer value (0).
3. Active_Reflective property: Defined with range xsd:integer, but individual L1 uses an xsd:string value ("1").
4. Sensitive_Intutive property: Defined with range xsd:integer, but individual L1 uses an xsd:string value ("0").
5. Visual_Verbal property: Defined with range xsd:integer, but individual L1 uses an xsd:string value ("1").
6. Global_Sequential property: Defined with range xsd:integer, but individual L1 uses an xsd:string value ("0").

OwlReady's reasoner enforces these range constraints strictly, which is why it throws the inconsistency error. Jena didn't flag this because either you didn't trigger full consistency checking in Jena, or Jena's default behavior is more permissive for such type mismatches.

Step-by-Step Fixes #

You need to align the property ranges with the actual datatypes of your individual values (or vice versa). Here are two approaches:

Option 1: Adjust property ranges to match individual values

Modify the rdfs:range for each conflicting property to match the datatype used in L1:

• For Age and Qualification: Change their range from xsd:string to xsd:integer.
• For Active_Reflective, Sensitive_Intutive, Visual_Verbal, Global_Sequential: Change their range from xsd:integer to xsd:string.

Example fix for the Age property:

<owl:DatatypeProperty rdf:about="#Age">
  <rdfs:domain rdf:resource="#Learner"/>
  <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#integer"/>
</owl:DatatypeProperty>

Option 2: Adjust individual values to match property ranges

Modify the rdf:datatype of each conflicting value in L1 to match the property's defined range:

• For Age and Qualification: Change their datatype to xsd:string (e.g., <Age rdf:datatype="xsd:string">18</Age>).
• For Active_Reflective and others: Change their datatype to xsd:integer (e.g., <Active_Reflective rdf:datatype="xsd:integer">1</Active_Reflective>).

Verify the Fix #

After making these changes, reload your ontology with OwlReady and run the reasoner again:

from owlready2 import *

world = World()
world.get_ontology("sample_ont.owl").load()
sync_reasoner(world)  # This should no longer throw the error
graph = world.as_rdflib_graph()

You can also use tools like Protégé to open your ontology and run its built-in reasoner to confirm there are no remaining inconsistencies.

内容的提问来源于stack exchange，提问作者RatheeshTS