Deprecate UBERONs "processual entity" #3647
Open
+7
−13
Conversation
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
All orphaned classes are placed under BFO classes for now. This is a precursor for COB alignment. (BFO:0000015 is a COB class). I placed the weird "life cycle temporal boundary" class under BFO:entity for now as a stop gap - We will probably deprecate all of these (discussion ongoing), or else find a better home in COB.
Member
|
I would prefer to avoid confusing dangling classes, can we resolve #3488 first |
Contributor
Author
I feel like this will hold up this issue here unnecessarily. Its on the roadmap though - but I want to clean up Uberon for my COB Workshop presentation and the boundary issue is a bit of a red herring here. I would still prefer we deal with this here first, and I will do the boundaries as an issue totally isolated from all other concerns.. |
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.
All orphaned classes are placed under BFO classes for now. This is a precursor for COB alignment. (BFO:0000015 is a COB class). I placed the weird "life cycle temporal boundary" class under BFO:entity for now as a stop gap - We will probably deprecate all of these (discussion ongoing), or else find a better home in COB.
See #2301