-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
phenio injects http://purl.obolibrary.org/obo/BFO_0000179 as an ObjectProperty #36
Comments
OK, I see it in PHENIO:
though I don't see it in any import. |
Grep through imports/*.owl for the relation. Most likely an import is using the relation in a domain restriction, and mostly likely it is SEPIO (which I would suggest to remove for now). |
Yep, that's what I've done so far - plus SEPIO hasn't been imported since 09d6ec2 |
Yes, the declartion could be injected if the BFO:179 was used in a logical axiom. What did the grep tell you, i.e. which ontologies use BFO:179? |
Strangely enough, none of the imports but the merged version:
and of the components, just BFO itself:
In
|
None of this explains the behaviour. Can you confirm the issue persists in the latest release? |
Try a ROBOT mirror before merge to get a better picture of the import chain |
NO BFO_0000179 in phenio after #94 |
This should be an AP
somewhere in the imports someone is injecting a declaration that says this is an OP
This causes all kinds of trouble, because we also have triples
OAK correctly interprets OPs as denoting edges between individuals, but the RHS is not a node in the above...
The text was updated successfully, but these errors were encountered: