OWL API：如何确保域和范围限制？

Question

我尝试使用OWL API来创建OWL本体。我可以定义他们之间的阶级，个人和关系。

当我定义一个ObjectProperty #hasPart域#A和范围#B，我预计这个属性可以通过适用于这两个类的个人。但事实上，API不关心的限制，因此可以分配#hasPart也#C类的两个成员之间例如：

import org.semanticweb.owlapi.apibinding.OWLManager; 
import org.semanticweb.owlapi.model.*; 

public class OwlTest 
{ 
    public static void main(String[] args) 
    throws org.semanticweb.owlapi.model.OWLOntologyStorageException, org.semanticweb.owlapi.model.OWLOntologyCreationException, Exception 
    { 
     OWLOntologyManager manager = OWLManager.createOWLOntologyManager(); 
     OWLDataFactory df = manager.getOWLDataFactory(); 
     OWLOntology o = manager.createOntology(); 

     //------------------------------------------------------------------ 

     OWLClass clsA = df.getOWLClass(IRI.create("#A")); 
     OWLClass clsB = df.getOWLClass(IRI.create("#B")); 
     OWLClass clsC = df.getOWLClass(IRI.create("#C")); 

     OWLObjectProperty hasPart = df.getOWLObjectProperty(IRI.create("#hasPart")); 
     OWLObjectPropertyDomainAxiom domainAxiom = df.getOWLObjectPropertyDomainAxiom(hasPart, clsA); 
     OWLObjectPropertyRangeAxiom rangeAxiom = df.getOWLObjectPropertyRangeAxiom(hasPart, clsB); 

     manager.addAxiom(o, domainAxiom); 
     manager.addAxiom(o, rangeAxiom); 

     //------------------------------------------------------------------ 

     OWLNamedIndividual a1 = df.getOWLNamedIndividual(IRI.create("a1")); 
     OWLNamedIndividual b1 = df.getOWLNamedIndividual(IRI.create("b1")); 
     OWLNamedIndividual c1 = df.getOWLNamedIndividual(IRI.create("c1")); 
     OWLNamedIndividual c2 = df.getOWLNamedIndividual(IRI.create("c2")); 

     manager.addAxiom(o, df.getOWLClassAssertionAxiom(clsA, a1)); 
     manager.addAxiom(o, df.getOWLClassAssertionAxiom(clsB, b1)); 
     manager.addAxiom(o, df.getOWLClassAssertionAxiom(clsC, c1)); 
     manager.addAxiom(o, df.getOWLClassAssertionAxiom(clsC, c2)); 

     manager.addAxiom(o, df.getOWLObjectPropertyAssertionAxiom(hasPart, c1, c2)); // ObjectProperty '#hasPart' should only work for objects from Domain 'clsA' and Range 'clsB' 

     //------------------------------------------------------------------ 

     manager.saveOntology(o, IRI.create("file:/tmp/data.owl")); 
    } 
} 

输出/tmp/data.owl：

... 
    <ObjectProperty rdf:about="#hasPart"> 
     <rdfs:domain rdf:resource="#A"/> 
     <rdfs:range rdf:resource="#B"/> 
    </ObjectProperty> 

    <Class rdf:about="#A"/> 
    <Class rdf:about="#B"/> 
    <Class rdf:about="#C"/> 

    <NamedIndividual rdf:about="a1"> 
     <rdf:type rdf:resource="#A"/> 
    </NamedIndividual> 

    <NamedIndividual rdf:about="b1"> 
     <rdf:type rdf:resource="#B"/> 
    </NamedIndividual> 

    <NamedIndividual rdf:about="c1"> 
     <rdf:type rdf:resource="#C"/> 
     <p1:hasPart rdf:resource="c2"/> 
    </NamedIndividual> 
... 

我现在找推荐的方式来编程处理这种限制..？提前谢谢了！

Answer 1

是的，有什么错用hasPart W/C，在推理只会认为你最终会告诉它C1也是A或C是一样A.

OWL- API不会执行你想要的行为，这听起来像你正在寻找某种完整性约束，就像你在正常的关系系统中得到的一样。您必须将其烧入应用程序中，或者查看Pellet的integrity constraints之类的内容，这些内容将在即将推出的Pellet 3版本中提供，目前可在Stardog中获得。