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

Remove OBO release for OMO #181

Open
matentzn opened this issue Nov 13, 2024 · 1 comment · May be fixed by #182
Open

Remove OBO release for OMO #181

matentzn opened this issue Nov 13, 2024 · 1 comment · May be fixed by #182

Comments

@matentzn
Copy link
Contributor

Context #179.

          Few Annotation properties are actually converted into OBO format. Maybe this has to do with the fact that they are not _used_ in the same ontology they are declared?

In any case, I vote to drop OBO support from OMO. I cant imagine anyone using it for anything but as an import into another ontology, which is always done through OWL API so always done through OWL..

Dear community, let us know if you have concerns not publishing OMO in OWL. Alternatively, we need someone to investigate why nearly no AP makes it through to OBO during conversion (not even into the owl-axioms: header in case you wondered).

I would suggest we merge this here because the problem was always present.

Originally posted by @matentzn in #179 (comment)

@cmungall
Copy link
Contributor

A horrible workaround is to use sparql to inject oboInOwl:is_metadata_tag into APs before conversion to OWL

But as you say there has never been an obo version so I think it's fine to officially drop support

@matentzn matentzn linked a pull request Nov 14, 2024 that will close this issue
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