obophenotype / obophenotype/uberon
Obsolete "life cycle temporal boundary" and descendants
Open
@matentzn is already working on this.
Since Apr 14, 2026.
obsolete
- Dominant language
- Emacs Lisp
- Stars
- 163
- Forks
- 43
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
We have the following branch in Uberon:
- [] UBERON:0000000 ! processual entity "An occurrent [span:Occurrent] that exists in time by occurring or happening, has temporal parts and always involves and depends on some entity."
- [i] UBERON:0035943 ! life cycle temporal boundary "A temporal boundary connecting two life cycle stages that follow in immediate succession. A temporal boundary is an abstract, instantaneous entity."
- [i] UBERON:0035946 ! start of neonate stage "A life cycle temporal boundary that marks the start of the neonate stage of the organism."
- [i] UBERON:0035945 ! start of life cycle "A life cycle temporal boundary that marks the start of the life cycle of the organism."
- [i] UBERON:0035944 ! life-death temporal boundary "A life cycle temporal boundary that marks the end of the life cycle of the organism."
- [i] UBERON:0035943 ! life cycle temporal boundary "A temporal boundary connecting two life cycle stages that follow in immediate succession. A temporal boundary is an abstract, instantaneous entity."
I would like to suggest to obsolete life cycle temporal boundary from Uberon for the following reasons:
- The classes are not, themselves, used anywhere in Uberon for formalisation (they are themselves defined in terms of other classes). This suggests that they are part of an incomplete attempt many years ago to model process boundaries in Uberon.
- There are only three temporal boundaries - which means the list is highly incomplete. In 7 years, there have not been any attempts to flesh out / extend this list.
- The original creator of Uberon calls them "useless vestiges of the heady days of over-formalization" (cite).
Please file your objects here until end of March, else I will go ahead with the plan. If you can add a like to indicate you agree with the decision, that would make me feel confident that someone at least has seen it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.