<owl:Class rdf:ID="aaa">
<rdfs:subClassOf>
      <owl:Restriction>
        ...
       </owl:Restriction>
...

我在使用pellet推理aaa的子类时，却得不到Restriction的对象呢？？
想使用别的jena推理机，可是速度太太太慢了。。。。

If this ontology is loaded in an OntModel backed by Pellet calling Student.listSuperClasses() would not include the restriction in the result. There are several reasons for this behavior: Treating each restriction as a named class would make it harder to reason with the ontology and the results you get in the end is not that useful. For example, in the above example, the reasoner can also return restriction(<a:hasAddress> minCardinality(1)) or restriction(<a:hasAddress> maxCardinality(1)) or restriction(<a:hasAddress> allValuesFrom(<a:Address>))  as a super class because they are all entailed by the above definition. Once class expression are considered, there are infinitely many possibilities, e.g. maxCardinality(1) implies maxCardinality(2) and so on. For this reason, Pellet will not return a restriction in an answer just because they physically exists in the ontology. However, one needs to get the syntactic definitions in the ontology and all the results Pellet returns are concatenated by the answers from the raw model. This means calling Person.listSuperClasses() for the above example would include the restriction in the results.

Note that, all the boolean functions would still work as expected. For example, asking the question like Student.hasSuperClass( restriction ) where restriction is the anonymous resource corresponding to the someValuesFrom restriction, Pellet will return true.

问题是:我确实是用类似于Person.listSuperClasses()的方法，还是得不到限制匿名类，这是怎么一回事啊？？？？ 哪位大哥知道啊，是不是我哪理解错了啊?