The relation-graph produce produces classes that are subclasses of each other. Here is the output from nmdco-relation-graph.owl:
fluid astronomical body part is a subclass of compound astronomical body part:
And compound astronomical body part is a subclass of fluid astronomical body part:
Unfortunately, I can't use robot reason b/c of incoherencies in ENVO. PO uses the domain and range constraints from RO. And the addition of these domains causes unsatisfiable classes, and a DL profile error. A ticket about lack of domain/range constraints has been filed for ENVO: https://github.com/EnvironmentOntology/envo/issues/1182
But, there has not been follow up.
Jim B. suggested I could make a "base" version of PO, using robot like so:
The
relation-graph
produce produces classes that are subclasses of each other. Here is the output fromnmdco-relation-graph.owl
:fluid astronomical body part
is a subclass ofcompound astronomical body part
:And
compound astronomical body part
is a subclass offluid astronomical body part
:Unfortunately, I can't use
robot reason
b/c of incoherencies in ENVO. PO uses the domain and range constraints from RO. And the addition of these domains causes unsatisfiable classes, and a DL profile error. A ticket about lack of domain/range constraints has been filed for ENVO: https://github.com/EnvironmentOntology/envo/issues/1182But, there has not been follow up.
Jim B. suggested I could make a "base" version of PO, using robot like so:
cc @cmungall @turbomam