search

information-artifact-ontology / IAO

information artifact ontology
Creative Commons Attribution 4.0 International
70 stars 25 forks source link

InverseOf axioms are stated in a verbose fashion #196

Closed cmungall closed 7 years ago

cmungall commented 7 years ago

E.g.

ObjectProperty: <http://purl.obolibrary.org/obo/IAO_0000221>
...
    EquivalentTo: 
         inverse (<http://purl.obolibrary.org/obo/IAO_0000417>)

this is perfectly valid, and any sensible OWL processor can rewrite this in the simpler form using an InverseProperties axiom.

However, not all consumers are capable of this transform, or implement it. And human users of the ontology may get confused. They may look in the 'inverse' slot in Protege and see nothing and miss the equivalence axiom. It may be simpler to reduce each axiom to its simplest form prior to release.

cmungall commented 7 years ago

oh and this one is classic:

ObjectProperty: <http://purl.obolibrary.org/obo/IAO_0000223>

    InverseOf: 
         inverse (<http://purl.obolibrary.org/obo/IAO_0000223>)

a tautology and therefore valid... but why... I assume a result of some kind of automated processing

alanruttenberg commented 7 years ago

I use the OWLAPI mechanism for adding inferred axioms. It's probably worth putting in an issue with them about this. As it happens doing that caused https://github.com/information-artifact-ontology/IAO/issues/195 and in order to address that in the short term this inference types: InferredObjectPropertyCharacteristicAxiomGenerator and InferredSubObjectPropertyAxiomGenerator

I will take into consideration the possibility of trying to reduce axioms to simpler forms, but this seems like it might better be taken up by the OWLAPI.

alanruttenberg commented 7 years ago

(There is a forthcoming release that fixes the inference issue)

alanruttenberg commented 7 years ago

I submitted a ticket to the OWLAPI project that includes this as an issue. https://github.com/owlcs/owlapi/issues/646