-
Notifications
You must be signed in to change notification settings - Fork 30
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
Updating pro import #2413
Updating pro import #2413
Conversation
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.
This does not seem to solve the issue.. Hmmmm.. How did no one ever notice that?
I provided an ODK fix.. We should prioritise moving Uberon to base module system.. |
@matentzn the PRO-short-label is still there in this branch |
<!-- http://purl.obolibrary.org/obo/pr#PRO-common-name --> | ||
|
||
<owl:AnnotationProperty rdf:about="http://purl.obolibrary.org/obo/pr#PRO-common-name"> | ||
<rdfs:subPropertyOf rdf:resource="http://www.geneontology.org/formats/oboInOwl#SynonymTypeProperty"/> |
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.
This is the key row @shawntanzk
If you run sh run.sh make uberon.obo IMP=false PAT=false BRI=false
the subsets should look correct.
@shawntanzk How did you verify this? I checked the source, and it looks correct (I also tagged you on the line so you can see it) |
Oh I thought you wanted to remove it, I just checked in protege if it was still there. But I see that you changed it to a has_synonym_type AP |
I dont know whether I ever explained the problem to you: Basically OBO format has this thing where it expects synonym types and subsets to be sub-annotation-properties of some specific parent. But the ROBOT module extraction process does not know about that - and |
btws is this ready to merge? also do we have to do a release for this? |
Yeah, lets do another release on Friday. It will be easier now. |
Sure, merge |
Fixes #2373
@matentzn - doesnt seem to fix after updating pro -> not sure if it got updated right? (I update mirror and all) could you help me check if the diff has the changes?