-
Notifications
You must be signed in to change notification settings - Fork 1
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
RO terms that normalize but the "invertedness" is not reported #7
Comments
This is causing inverted relationships in KG2 that lead to strange results, like "shellfish allergy" causes "shellfish". |
Ah, this is an excellent point. We'll get on it. |
Well, having dug in a little, and talked to @balhoff I think that this is actually an RO bug. Both @saramsey if you know that RO really encodes inverses as part of a property inheritance, can you explain how it's coded there? I'll file a bug report at RO and see what they say. Leaving this issue open until I hear from them. |
Hi @cbizon thanks for your thoughtful reply. I guess I should restate my claim: I surmised that RO encodes this information because it seems to be available in Ontobee (see screencap in the OP), see the plusses and minuses in the treeview. Apologies if I've misinterpreted the meaning of the plusses & minuses. http://www.ontobee.org/ontology/RO?iri=http://purl.obolibrary.org/obo/RO_0001023 |
Also thanks to @balhoff for consulting on this issue. |
Ok, I think (not 100% sure) that the +/- on ontobee indicates whether the term has children (+) or not (-). |
@cbizon that's right. If there is an inverse property, it is stated in a "Inverse Properties" section further down. |
When I attempt to normalize
RO:0001022
("has allergenic trigger"), I getbiolink:causes
, which I think is close, but not quite correct (I think it should be the inverse of that).The Relation Ontology (RO) has "inversion" encoded in their hierarchy relationships, as shown in Ontobee:
were these taken into account in the ETL of RO that was (presumably) done to generate the synonym relationships in the Edge Normalizer?
The text was updated successfully, but these errors were encountered: