obophenotype / obophenotype/uberon
scapulocoracoid
Nobody has claimed this yet.
- Dominant language
- Emacs Lisp
- Stars
- 163
- Forks
- 43
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
related to #41
related to #66
Definition of scapulocoracoid is yet unresolved.
From previous discussion:
The scapulocoracoid is the name given to the fused scapula and coracoid
(ancestrally they are basically one unit, they separate multiple
times independently) so since mammals have a scapula, they have part of the
scapulocoracoid.
Can be defined somewhat abstractly such as "the unit that contains the scapula and coracoid" (when present, may be fused or unfused) - as is implicit in http://en.wikipedia.org/wiki/Scapulocoracoid
Note discussion regarding the scapulocorocoid when they are very close in proximity but not fused, yet still called the scapulocorocoid. This was discussed on the RCN vertebrate call.
Current def:
def: "Skeletal element that consists of the scapula and the coracoid[VSAO, modified]."
comment: AO notes: ZFA defines as precursor to scapula and coracoid. Taxon notes: Fused, ossified portions of the scapula, procoracoid, and coracoid[AAO] Cartilage in TAO. Editor notes: todo - decide whether to create separate classes for cartilage & ossified
synonym: "coraco-scapular cartilage" NARROW [ZFA:0001455]
synonym: "scapulocoracoideum" EXACT [VSAO:0005002]
is_a: UBERON:0004765 ! skeletal element
relationship: part_of UBERON:0007831 {source="VSAO"} ! skeleton of pectoral girdle
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.
Research direction
Start by reviewing related issues #41 and #66 and the prior discussion referenced in this issue. Resolve the definition of scapulocoracoid, including the treatment of fused or separate structures and cartilage versus ossified portions, then update the ontology entry once the terminology is agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100