Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Relation between "clavicle bone", "shoulder bone" and "shoulder joint" #1227
There are relations that lead to infer that "clavicle bone" exists only in tetrapoda, see: BgeeDB/anatomical-similarity-annotations#12 (comment)
Is this relation correct?
referenced this issue
Jun 15, 2016
OK, a few things going on here
The 'source' axiom is:
'shoulder bone' EquivalentTo 'bone element' and overlaps some 'shoulder
(let's leave aside the state-specific bone and state-generic 'bone
overlaps = has_part o part_of
(ie if two things have a part in common, they overlap_
but we can't state this as an OWL axiom, so we expand as a
'shoulder bone' EquivalentTo 'bone element' and has-part some (part-of
Again ignore the bone/element mismatch, I think this is justifiable,
There are some interesting discussions here about logic and how to
but all that aside, the real issue here is:
'clavicle bone' SubClassOf 'shoulder bone'
This should clearly by a taxon GCI, for the reasons you mention.
And on top of that: why didn't the extensive taxon constraints catch