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

Should ontologies submitted to OBO be rejected based on their lack of relation to biomedical domain? #1918

Open
matentzn opened this issue May 18, 2022 · 6 comments
Labels
policy Issues and discussion related to OBO Foundry policies

Comments

@matentzn
Copy link
Contributor

It is very hard to answer this question in general, as all things in the world are related, but we should add some clear guidelines somewhere that clarify this. In yesterdays OFOC call, the following suggestions were made:

  • Ontologies should be at least Related to biomedical ontologies (@cstoeckert)
    • again hard to qualify what that means (@matentzn)
    • It should be possible to link to related ontologies outside of OBO from within OBO ontologies. There should not be a need to accept all related ontologies (@jamesaoverton)
  • FAIR is such an important orthogonal domain that it should at least be considered (@ddooley, @addiehl)

If you have opinions for a crisp definition of the content scope of OBO ontologies, let us know!

@cthoyt
Copy link
Collaborator

cthoyt commented May 18, 2022

Simple suggestion (maybe stolen from Nico?) - if the root terms don't subclass/inherit somehow from terms in COB then it's not in scope - reject it outright. Allow people whose requests don't fall under COB to have the option to petition COB to add things, but also have clear guidance there on what will be considered for COB.

@matentzn
Copy link
Contributor Author

There are though some pretty general things is COB, like planned process. You can imagine some "crypto-currency server farm ontology" which has a bunch of planned processes in it!

@nlharris nlharris added the policy Issues and discussion related to OBO Foundry policies label May 18, 2022
@nlharris
Copy link
Contributor

Are you working on that ontology, Nico?? 🤨

@nlharris
Copy link
Contributor

nlharris commented May 26, 2022

I think what Charlie suggested above and Nico's response don't actually contradict each other.

Charlie: if (ontology NOT inherit_from COB) then (ontology NOT relevant_to OBOFoundry)
Nico: CryptoCurrencyOntology inherit_from COB
Nomi: Ok, but Charlie did not say "if (ontology inherit_from COB) then (ontology relevant_to OBOFoundry)".

ETA: but that doesn't actually solve this conundrum, because if you say to CryptoCurrencyOntology, "Sorry, you're not relevant, we reject you," they could say, "but we inherit from some COB terms!" which might be true but not good enough. So I guess I agree more with Nico. :-)

@cthoyt
Copy link
Collaborator

cthoyt commented May 27, 2022

I would say that my criteria is useful, but not sufficient

@nataled
Copy link
Contributor

nataled commented Sep 26, 2023

Just dropping by to say that we have in fact done this. The one that comes to mind is "African Traditional Medicine Ontology" that was rejected (in the days before GitHub!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
policy Issues and discussion related to OBO Foundry policies
Projects
None yet
Development

No branches or pull requests

4 participants