Repository navigation
Explicitly annotate URI prefixes for non-standard resources - #2951
Merged
Merged
Conversation
jsstevenson
approved these changes
Sep 29, 2026
jsstevenson
left a comment
Contributor
There was a problem hiding this comment.
seems fine from a technical standpoint 👍
This was referenced Sep 29, 2026
cthoyt
added a commit
to biopragmatics/bioregistry
that referenced
this pull request
Sep 29, 2026
Some OBO Foundry ontologies do not use OBO PURLs. As of OBOFoundry/OBOFoundry.github.io#2951, these are now made explicit in the metadata of the OBO Foundry. This PR incorporates that data and removes an incomplete custom override. This PR is requires the OBO Foundry to update its metadata before it can be merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are a handful of ontologies in OBO Foundry that don't use standard OBO PURLs. This leads to some inaccuracies in the build files.
This PR adds a new field to capture that. I curated four by hand, I'm not sure if there are some others. Maybe a bioregistry analysis could reveal more, but this is a PoC that would be ready to merge.
Some specifics:
uri_prefixto thevann:preferredNamespaceUripredicate in the manually curated context