-
Notifications
You must be signed in to change notification settings - Fork 52
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
Proposal for Bioregistry SOP: "No manual registration of OBO URI prefixes" #1212
Comments
@matentzn I understood. We'll need a suitable revision to the Foundry NOR instructions to account for this: In addition to checking the Bioregistry and BioPortal, submitters will need to also check (at least) the NOR Dashboard (for ontologies in the in-between). |
This should be more generic to say that new resources should not park on external IRI spaces. This isn't only applicable for OBO Foundry, but also the Crop Ontology IRI space, Identifiers.org IRI space, Name-to-Thing IRI space, RRID IRI space, or anything similar. For people trying to pick something that is PURL-like, they could consider w3id.org or similar We can't make a technical solution that says non-OBO prefixes can't use OBO IRI space, as I've linked a few times in this discussion, there are people doing this whether we like it or not, for a variety of reasons. Therefore, I propose that what you're asking for is articulated in terms of improving reviewer guidelines. How can you educate Bioregistry reviewers to spot these situations, and help them to explain to submitters why they shouldn't be doing this? Then, how can you guide them towards a better solution? Will one of you take the lead on writing a more coherent explanation? |
I framed it a bit differently, lets work on this and see what you think: https://docs.google.com/document/d/1aIP8YjyVnMzKnksMbBu1kYriV9jlMejWDrZ7E3GmXlY/edit?usp=sharing |
Some context.
I would like to suggest the following addition to the bioregistry SOP:
@nataled that is what I meant - if OBCI say is accepted in OBO, the OBO URI prefix will automatically finds its way into bioregistry through the OBO metadata.
The text was updated successfully, but these errors were encountered: