-
Notifications
You must be signed in to change notification settings - Fork 51
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
Standardize http://purl.obolibrary.org/obo/hp#layperson
to OMO:0003003
#10140
Comments
Can you present the OMO resource on an upcoming Monarch call? I am open to linking this, but worried that it will introduce more complications in Protege and not sure there is a big audience for this at the present. |
Closes obophenotype#10140 @matentzn can you help me update the configuration to properly import the OMO term?
@pnrobinson yes, I can give an outline of what I've been working on across the oboverse. In the mean time, I made a proof of concept PR in #10241. None of the other OBO ontologies where we made this update (CL, UBERON, NCBITAXON, ENVO, etc.) have had any issues with protege as far as I know. |
Hi @cthoyt |
This is part of the campaign to standardize synonym type definitions across the OBO Foundry: OBOFoundry/OBOFoundry.github.io#2450
I would like to replace the ad-hoc synonym type http://purl.obolibrary.org/obo/hp#layperson for layperson synonyms with the new OMO standard OMO:0003003 "layperson synonym"
This will improve the ability of tools that care about synonym types to better leverage HP's content. Further, it is part of a more general effort to reduce the number of hash IRIs across OBO ontologies.
If this gets good feedback, I will follow-up with other issues about additional synonym updates including:
The text was updated successfully, but these errors were encountered: