Inverse properties relations not inferred

[KayJay]

Hello,

I loaded an ontology in owlready2 (created with Protégé) and after having populated it and run the reasoner Pellet included in owlready2, I noticed that no inverse properties relations were inferred. I opened the populated ontology with Protégé, and this time the inverse properties relations were inferred with the Pellet reasoner included in Protégé (which validates the coding of the inverse property). Is this feature not supported yet in owlready2?

KayJay

[Jiba]

Hi,

Inverse properties are not stored in the quadstore, in order to reduce its size. However, most functionalities of Owlready consider inverse properties, so you normally do not want them in the quadstore... Do you have a particular reason for that?

Jiba

[Karlemami]

Hello,

I know this is years old, but I haven't found anything younger that's relevant to my problem. I do have a particular reason for inverse properties to be in the quadstore : SPARQL requests. Is there a way to force it ?

[Jiba]

Hello,

> I do have a particular reason for inverse properties to be in the quadstore : SPARQL requests. Is there a way to force it ?

No, there is no way to force that, unless you manually add the triples in the quadstore (which can have unpredictable results, as Owlready does not expect them).

The best approach is to modify the SPARQL query so that it works with inverse properties, e.g. using a UNION operator .

Jiba