Do not "add OBO shorthands" to the RO mirror. #3359
+0
−5
Conversation
This file contains 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
RO is currently mirrored in Uberon using a custom rule that bypasses the normal ODK mirroring rule to include an additional step, the addition of OBO shorthands to RO relations. "OBO shorthands" are basically a trick allowing to use, e.g. `part_of` instead of `BFO:0000050` in a class expression, as in: relationship: part_of UBERON:00000033 However there is no reason to forcefully inject OBO shorthands to all RO relations as we are currently doing. We can already create OBO shorthands as needed within uberon-edit, for the relationships that are actually used. For example, we already have this in uberon-edit: [Typedef] id: part_of name: part of xref: BFO:0000050 which creates the `part_of` shorthand for BFO:0000050. We should stick to doing that for the relations we are actually using, and stop injectinf fabricated shorthands for the entirety of RO. If people believe that all RO relations should have OBO shorthands, then they should ask the RO folks to add them at the source. It's not Uberon's job to do it. So this commit removes the rule that adds the OBO shorthands to the RO mirror, so that RO is now mirrored using the standard ODK-generated rule. closes #3016
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.
RO is currently mirrored in Uberon using a custom rule that bypasses the normal ODK mirroring rule to include an additional step, the addition of OBO shorthands to RO relations.
"OBO shorthands" are basically a trick allowing to use, e.g.
part_ofinstead ofBFO:0000050in a class expression, as in:However there is no reason to forcefully inject OBO shorthands to all RO relations as we are currently doing. We can already create OBO shorthands as needed within uberon-edit, for the relationships that are actually used. For example, we already have this in uberon-edit:
which creates the
part_ofshorthand for BFO:0000050.We should stick to doing that for the relations we are actually using, and stop injectinf fabricated shorthands for the entirety of RO. If people believe that all RO relations should have OBO shorthands, then they should ask the RO folks to add them at the source. It's not Uberon's job to do it.
So this commit removes the rule that adds the OBO shorthands to the RO mirror, so that RO is now mirrored using the standard ODK-generated rule.
closes #3016