Make sure the SSSOM-derived cross-reference use correct OBO prefixes. #3465
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.
Most of the prefixes used by the taxon-specific life stage ontologies (SSLSO) are not intrinsically known by ROBOT (prefixes such as BtauDv, GgalDv, PpanDv, etc.).
As a result, when the mappings from SSLSO are transformed into cross-references for injection into the ontology (when we create the
mappings.owl
component), the SSLSO term IDs are shortened using the only suitable prefix that ROBOT knows about, theobo:
prefix.This means that a mapping to, say, http://purl.obolibrary.org/obo/BtauDv_0000078 gets turned into a cross-reference to
obo:BtauDv_0000078
-- which is, strictly speaking, correct, but not the format most people would expect for OBO-style cross-references (which would beBtauDv:0000078
).The fix is simply to make sure the prefixes are correctly declared.