-
Notifications
You must be signed in to change notification settings - Fork 38
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
Map MS partof to RO #232
Map MS partof to RO #232
Conversation
@@ -45,6 +45,7 @@ name: has_units | |||
[Typedef] | |||
id: part_of | |||
name: part_of | |||
xref: BFO:0000050 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@matentzn Can you update the version of the ontology. See the failing Actions https://github.com/HUPO-PSI/psi-ms-CV/actions/runs/7638645173/job/20810093289
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to close this PR and redo it, I just wanted to show you how you can map your part of to RO, so it displays correctly in OLS and interoperates with other ontologies. You can also directly edit my PR and make the required changes!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Thanks a lot for the tip.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be funny if after all this pain, the solution is as simple as this..
I merged the PR to see the changes and opened the owl created in Protege as suggested; and it looks for me that the problem still remains Any advice @matentzn ? |
(I think the problem in Protege is that it will include the is a hierarchy no matter what, and superimposes the other "relation ships" after the fact - which means that what you see in terms of top level roots are all the roots according to the is a hierarchy) |
Fixes EBISPOT/ols4#600
Ideally, in a future PR, you should consider to import RO rather than copy pasting the semantics here (i.e. transitivity).