Skip to content
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

Closed
cthoyt opened this issue Sep 29, 2023 · 3 comments
Closed

Standardize http://purl.obolibrary.org/obo/hp#layperson to OMO:0003003 #10140

cthoyt opened this issue Sep 29, 2023 · 3 comments

Comments

@cthoyt
Copy link
Contributor

cthoyt commented Sep 29, 2023

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:

@pnrobinson
Copy link
Contributor

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.

cthoyt added a commit to cthoyt/human-phenotype-ontology that referenced this issue Nov 21, 2023
Closes obophenotype#10140

@matentzn can you help me update the configuration to properly import the OMO term?
@cthoyt
Copy link
Contributor Author

cthoyt commented Nov 21, 2023

@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.

@pnrobinson
Copy link
Contributor

Hi @cthoyt
it seems every time changes like this are made, multiple errors occur with protege, and I am not sure there is any use case right now. I would suggest let's wait until a user asks for this feature for something. I am struggling to get the annotation done and need to be choosy fwiw to avoid too much insanity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants