Difference between revisions of "Guide to Character Annotation"

From phenoscape
Line 73: Line 73:
 
Annotations are made using the most specific term or post-composition possible for Entity and Quality. This may not be possible for some characters involving very complex phenotypes, particularly those with descriptions of shape variation. In these cases, annotations are made to 'attribute' level PATO terms (e.g., PATO: <span style="font-family:courier new,courier,monospace">shape</span>).
 
Annotations are made using the most specific term or post-composition possible for Entity and Quality. This may not be possible for some characters involving very complex phenotypes, particularly those with descriptions of shape variation. In these cases, annotations are made to 'attribute' level PATO terms (e.g., PATO: <span style="font-family:courier new,courier,monospace">shape</span>).
  
== Character Annotation Examples ==
+
== Character Annotation Examples<br/> ==
  
The following are examples of character types commonly encountered in the systematic literature and how we annotate them using the EQ model in Phenex. Abbreviations: E, entity; Q, quality, RE, related entity, C, count.
+
The following are examples of character types commonly encountered in the systematic literature and how we annotate them using the EQ model in Phenex. Abbreviations:<span style="font-family:courier new,courier,monospace">E</span>, entity; <span style="font-family:courier new,courier,monospace">Q</span>, quality, <span style="font-family:courier new,courier,monospace">RE</span>, related entity, <span style="font-family:courier new,courier,monospace">C</span>, count.
  
 
=== 1. Qualities of single physical entities ===
 
=== 1. Qualities of single physical entities ===
Line 121: Line 121:
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: vertebra, Q: count, Comment: ≥48</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: vertebra, Q: count, Comment: ≥48</span>
  
*The "Count" field in Phenex currently does not accept ranges or symbols; therefore, please record these in the Comments field.
+
*NOTE: the "Count" field in Phenex currently does not accept ranges or symbols; therefore, please record these in the Comment field, as seen above.
  
 
=== 6. Size<br/> ===
 
=== 6. Size<br/> ===
  
In the systematics literature, the size of a structure is usually described relative to another structure, or size of a structure is compared across taxa.
+
There are various ways an author may describe or compare the size of a structure across taxa. These include:
  
*The '''size of one structure relative to another structure ''' (e.g., state 0: "frontal length greater than parietal length", with taxonomic distribution recorded in the character by taxon matrix) is represented as:
+
*The '''size of one structure relative to another structure. '''For example, "frontal length greater than parietal length" is represented as:
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: frontal, Q: increased length, E2: parietal</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: frontal, Q: increased length, E2: parietal</span>
  
*Comparison of the '''size of a structure across taxa''' (e.g., “state 0: frontal large”) is represented as:
+
*Comparison of the '''size of a single structure across taxa'''. For example, "frontal large” is represented as:
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: frontal, Q: increased size</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: frontal, Q: increased size</span>
  
*'''Size comparisons within a single structure''' are represented by using a size quality in the entity field. For example, an author may describe the frontal bone as having a "greater length relative to width". This is represented as:
+
*'''Comparison of multiple dimensions of size for a single structure'''. For example, an author may describe the frontal bone as having a "greater length relative to width". This requires post-composing the quality with the two PATO terms for length and width:
  
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: frontal bone, Q: increased length, E2: width^inheres_in(frontal bone)</span>
+
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: frontal bone, Q: length^''increased_in_magnitude_relative_to''(width^''inheres_in''(frontal bone)</span>)
  
 
*'''Locally relative phenotypes''' describe a range of sizes in more than two states.
 
*'''Locally relative phenotypes''' describe a range of sizes in more than two states.
Line 163: Line 163:
 
==== ''Example 1'' ====
 
==== ''Example 1'' ====
  
Epibranchial 1: (0) present and ossified  
+
Epibranchial 1: (0) present and ossified
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: Epibranchial 1 bone, Q: present</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: Epibranchial 1 bone, Q: present</span>
  
Epibranchial 1: (1) present and cartilaginous  
+
Epibranchial 1: (1) present and cartilaginous
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: Epibranchial 1 cartilage, Q: present</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: Epibranchial 1 cartilage, Q: present</span>
  
Epibranchial 1: (2) absent  
+
Epibranchial 1: (2) absent
  
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: Epibranchial 1 cartilage, Q: absent <br/></span>
+
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: Epibranchial 1 cartilage, Q: absent</span>
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; E: Epibranchial 1 bone, Q: absent</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; E: Epibranchial 1 bone, Q: absent</span>
Line 181: Line 181:
 
==== ''Example 2'' ====
 
==== ''Example 2'' ====
  
Epibranchial 1 (0) present, (0) absent. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:  
+
Epibranchial 1 (0) present, (0) absent. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: epibranchial 1 element, Q: present or Q: absent</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: epibranchial 1 element, Q: present or Q: absent</span>
Line 187: Line 187:
 
==== ''Example 3'' ====
 
==== ''Example 3'' ====
  
Epibranchial 1 bone: (0) present; (1) absent  
+
Epibranchial 1 bone: (0) present; (1) absent
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: epibranchial 1 bone; Q: present or Q: absent</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: epibranchial 1 bone; Q: present or Q: absent</span>
Line 193: Line 193:
 
==== ''Example 4'' ====
 
==== ''Example 4'' ====
  
Epibranchial 1: (0) triangular. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:  
+
Epibranchial 1: (0) triangular. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: epibranchial 1 element, Q: shape</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: epibranchial 1 element, Q: shape</span>
Line 199: Line 199:
 
==== ''Example 5'' ====
 
==== ''Example 5'' ====
  
Epibranchial number: (0) 3; (1) 4. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:  
+
Epibranchial number: (0) 3; (1) 4. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; E: epibranchial element; Q: count; Comment: 3 or Comment: 4</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; E: epibranchial element; Q: count; Comment: 3 or Comment: 4</span>
Line 205: Line 205:
 
==== ''Example 6''<br/> ====
 
==== ''Example 6''<br/> ====
  
Epibranchial bone number: (0) 3; (1) 4  
+
Epibranchial bone number: (0) 3; (1) 4
  
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: epibranchial bone; Q: count; Comment: 3 or Comment: 4</span>
 
<span style="font-family:courier new,courier,monospace">&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="font-family:courier new,courier,monospace">E: epibranchial bone; Q: count; Comment: 3 or Comment: 4</span>

Revision as of 17:23, 17 June 2013

PATO terms used to annotate systematic characters

Below is a simplified graph showing a subset of quality terms from the Phenotype and Trait Ontology (PATO) used to curate systematic characters. Terms in orange represent attribute-level qualities.

Image:1000 pixels

PATO attribute-level term Synonyms Examples of child terms
shape triangular, lobed, concave, protruding into
position placement, location horizontal, anterior to
size thin, large, decreased height
structure porous, fused with
composition ligamentous, cartilaginous
texture smooth, wrinkled
optical quality color, brightness
mass increased mass
quality of a solid flexible, hard
mobility mobile, immobile
closure open, closed
behavioral quality
count present, absent

Annotation Specificity

Annotations are made using the most specific term or post-composition possible for Entity and Quality. This may not be possible for some characters involving very complex phenotypes, particularly those with descriptions of shape variation. In these cases, annotations are made to 'attribute' level PATO terms (e.g., PATO: shape).

Character Annotation Examples

The following are examples of character types commonly encountered in the systematic literature and how we annotate them using the EQ model in Phenex. Abbreviations:E, entity; Q, quality, RE, related entity, C, count.

1. Qualities of single physical entities

Qualities of single physical entities are those that exist in a single entity. These qualities include 'shape,' 'size', and 'structure.' For example, “sigmoid-shaped supraorbital bone” is annotated as:

     E: supraorbital, Q: sigmoid

2. Qualities of related physical entities

Relational qualities are those that exist between multiple entities. For example, “parietal fused with supraoccipital” is represented as:

     E: parietal, Q: fused with, RE: supraoccipital

3. Multiple phenotypes for a single character state

Some characters describe multiple aspects of phenotypic variation in an entity (or entities). These characters are represented with multiple EQ statements. For example, a character state may describe "premaxillary teeth round and multicuspidate." This is represented with the following two phenotypes:

     E: premaxillary tooth, Q: round
     E: premaxillary tooth, Q: multicuspidate

4. Presence/absence characters

Variation in the presence or absence of an entity is annotated using the terms present and absent, e.g. :
 

    E: pectoral fin, Q: present E: pectoral fin, Q: absent

The use of present and absent in curation is a curatorial shortcut to the more logically sound syntax discussed on the PATO wiki. These annotations will be translated into the logically sound form prior to their addition in the Phenoscape KB.

If a character describes the presence or absence of a structure located on another entity (for example, teeth present on a particular bone), first check to see whether the structure exists as a term in the ontology before creating a post-composition. For example, a character might describe "teeth absent on basihyal bone." Rather than create a post-composition for entity ("tooth^part_of(basihyal bone)"), the entity in this case is a preexisting term chosen from TAO:

     E: basihyal tooth, Q: absent

Inferred presence from annotation to other attributes

If a character describes both the presence of an entity and some other attribute regarding its features (e.g., 'frontal bone' with state 'present and round'), only the attribute ('round') is annotated because the presence of the entity can be inferred by annotations to any other attribute.

5. Counts

Characters involving counts of entities are annotated using the “count” quality. Values for counts are entered in the “Comment” field(*). Note that ranges and lower or upper bounds are recorded as follows:

     E: vertebra, Q: count, Count: 33

     E: vertebra, Q: count, Comment: 34-38

     E: vertebra, Q: count, Comment: >38

     E: vertebra, Q: count, Comment: ≥48

  • NOTE: the "Count" field in Phenex currently does not accept ranges or symbols; therefore, please record these in the Comment field, as seen above.

6. Size

There are various ways an author may describe or compare the size of a structure across taxa. These include:

  • The size of one structure relative to another structure. For example, "frontal length greater than parietal length" is represented as:

     E: frontal, Q: increased length, E2: parietal

  • Comparison of the size of a single structure across taxa. For example, "frontal large” is represented as:

     E: frontal, Q: increased size

  • Comparison of multiple dimensions of size for a single structure. For example, an author may describe the frontal bone as having a "greater length relative to width". This requires post-composing the quality with the two PATO terms for length and width:

     E: frontal bone, Q: length^increased_in_magnitude_relative_to(width^inheres_in(frontal bone))

  • Locally relative phenotypes describe a range of sizes in more than two states.

Example: "opercle size: small, medium, or large". Choose the quality being compared, and place a number in the Count column indicating the proper sort order (1 < 2 < 3). For "small":

     E: opercle, Q: size, Count: 1

Note: Representation of size in Phenex uses curatorial shortcuts because PATO size terms are precomposed relative to "normal" (e.g., increased size has an increased_in relationship to "normal"). These annotations will be converted in the KB data loader to the correct form using the appropriate relations (increased_in_magnitude_relative_to, decreased_in_magnitude_relative_to, similar_in_magnitude_relative_to).

7. Contralateral halves of bilaterally paired structures

Terms for the contralateral halves of bilaterally paired structures are created using the in_right_side_of and in_left_side_of relations in a post-composition, where the perspective is from the standpoint of the organism. For example: E: frontal^in_right_side_of(body), Q: fused with, RE: frontal^in_left_side_of(body).

8. Complementary phenotypes ("negation")

Example: "opercle, not round". Create a postcomposition for the quality, choosing a meaningful genus term and using the "not" relation. E: opercle, Q: shape^not(round)

9. Annotation involving bone and cartilage terms

Authors sometimes refer to endochondral structures without specifying whether the structure is “bone” or “cartilage.” For example, the convention for a term like “epibranchial 2” or “basibranchial” is that it is composed of bone and when composed of cartilage an author will say “epibranchial 2 cartilage” or “basibranchial cartilage”. However, this is not universally followed and a curator must read the character description and examine associated text and figures to ascertain this. If after reviewing the publication it is still not clear, then the curator can use the “element” term for the structure. In general, the “element” terms should be used sparingly, and only when an author does not indicate whether a structure (e.g. “epibranchial”) is composed of cartilage or bone.

The following are a series of examples demonstrating the use of bone, cartilage, and element terms.

Example 1

Epibranchial 1: (0) present and ossified

     E: Epibranchial 1 bone, Q: present

Epibranchial 1: (1) present and cartilaginous

     E: Epibranchial 1 cartilage, Q: present

Epibranchial 1: (2) absent

     E: Epibranchial 1 cartilage, Q: absent

     E: Epibranchial 1 bone, Q: absent

The curator should use both the cartilage and bone terms to annotate state 2 because the author clearly differentiates between the two.

Example 2

Epibranchial 1 (0) present, (0) absent. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:

     E: epibranchial 1 element, Q: present or Q: absent

Example 3

Epibranchial 1 bone: (0) present; (1) absent

     E: epibranchial 1 bone; Q: present or Q: absent

Example 4

Epibranchial 1: (0) triangular. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:

     E: epibranchial 1 element, Q: shape

Example 5

Epibranchial number: (0) 3; (1) 4. After careful reading of associated text in the publication, the curator cannot conclude that the author refers to bone or cartilage, and therefore uses "element" term:

     E: epibranchial element; Q: count; Comment: 3 or Comment: 4

Example 6

Epibranchial bone number: (0) 3; (1) 4

     E: epibranchial bone; Q: count; Comment: 3 or Comment: 4

Creating or refining terms by post-composition

Often times the need arises to create a new term at the time of annotation ("post-composition"), rather than requesting that the new term is formally added to the ontology. Such cases typically arise when annotating the presence of processes on bones. In some cases a more granular term is required than is already present in the ontology, whether it is the anatomical entity or the quality. For example, to prevent ontology "bloat", regions, margins, and projections of a bone are not in the anatomy ontology, but the bone itself is, and the concepts of margin, relative location of the margin (anterior, posterior, ventral, dorsal, etc), or bony projection are too, or are in other ontologies (spatial aspect, for example). Similarly, the directionality of a phenotype (such as a rotation, or curvature) isn't necessarily present in PATO, but the component terms necessary to express it are. The act of combining terms on-the-fly into cross-product terms is called post-composition, as opposed to pre-composed terms that are already in the ontology.

Post-composed terms can be created in Phenex following the genus-differentia principle of defining terms, where one term serves as the genus, which is then differentiated using a relationship and a differentia term. Unlike pre-composed terms, post-composed terms do not have an ID, and hence are "anonymous." Therefore if the same post-composition is used multiple times, it has the same semantics, but not the same identity. For example, if one wants to assign multiple annotations to the same process of the lateral ethmoid in the same specimen, using post-composed terms does not allow the identity of the anatomical structure between the annotations to be inferred.

The order in which the terms are composed is important if the composition relationship is not symmetric (a relationship is symmetric iff A rel B <=> B rel A). Most relationships are not symmetric. As a general rule, choose the more general part as the genus, and then use the relationship and differentia to narrow down. For example, for "process of the lateral ethmoid" use "process" as the genus, and use the relationship and differentia to narrow down which process of the many that are possible you mean, such as using part_of for the relationship and "lateral ethmoid" as the differentia (formally, the "process that is part_of the lateral ethmoid").

Note that semantically, the post-composed term is equivalent to a pre-composed term, provided the pre-composed term has both the inheritance relationship and the cross-product relationship properly recorded. For example, "process of lateral ethmoid" is-a "process", and "process of lateral ethmoid" part-of "lateral ethmoid".

Creating post-composition in Phenex

To post-compose a term (for example, "maxillary process") using Phenex, first type in the genus term 'process' in the Entity field within the "Phenotypes" panel. Then open the Post-composition Editor box by right-clicking on the Entity cell (make sure that the entity cell is blue in color) :

Error creating thumbnail: Unable to save thumbnail to destination


Now click on “Edit Post-composed Term.” The Editor box should now appear (see below), with “process” in the Genus field. The Genus is the feature of specific interest (varying feature in systematics). Click the “+” button to add a row in the table, type “part_of” in the relationship field, and type “maxilla” in the differentia field. Click OK.

Error creating thumbnail: Unable to save thumbnail to destination

The post-composed term appears in the Entity field as:  process^part_of(maxilla)

Refining post-compositions using spatial terms

Often we will want to include spatial information in a post-composed term. The Spatial Ontology is used to post-compose terms related to bone margins, surfaces, or regions. For example, the entity “anterior process of the maxilla" is post-composed as follows:

Within the Entity field, type “process” and right-click the field to open the Post-Composition Editor box. Within this box, Click the + button to add relationship = "part_of" and differentia = "anterior region". Right click on the differentia field to open another Post-Composition Editor box to add second post-composed term for "anterior margin of maxilla" (see below). Click the OK button after you have filled out the genus and differentia for this nested composition.

Error creating thumbnail: Unable to save thumbnail to destination

Within Phenex, the post-composed term for process on the anterior margin of the maxilla appears as: process^part_of(anterior region^part_of(maxilla))

As for semantics, identifiability, and rules for post-composing, the same applies as above for entity terms applies to spatial terms. In creating the nested term "anterior region of maxilla", start with the more general term (for example, the "anterior region") as the genus, then refine it using a relationship and a differentia term (for example, anterior region that is part_of the "supraorbital bone").

Multiple differentia terms and nesting in post-composition

Post-compositions can contain multiple differentia terms that are either nested:process^part_of(anterior region^part_of(maxilla))

or not: joint^connects(metapterygoid)^connects(hyomandibula)

For nested post-compositions, the order of nested terms is important (e.g., maxilla^part_of(anterior region^part-of(process)) is incorrect), as is the nesting itself (e.g., process^part_of(anterior region)^part_of(maxilla) is incorrect).

Some post-compositions with multiple differentia do not require nesting (see discussion of joint post-compositions).

Creating "joint" terms on-the-fly

Joints are defined in Uberon according to the skeletal elements that participate in the joint. The connects relation is used to relate skeletal elements to skeletal joints.  We post-compose joint terms that are not likely to be used repeatedly for annotation. To post-compose a joint, for example the "metapterygoid-hyomandibular joint", open the post-composition editor box by right-clicking on the Entity field, and enter the following terms in the window:

Error creating thumbnail: Unable to save thumbnail to destination

The post-composed term for metapterygoid-hyomandibular joint will appear as:

     skeletal joint^connects(metapterygoid)^connects (hyomandibula)

Relations used for post-compositions

Relation
Category Design  Pattern   
Examples
anteriorly connected to connectedness E anteriorly_connected_to E
'head' and (anteriorly_connected_to some 'neck')
attaches_to connectedness E attaches_to E
Used primarily to represent attachment of teeth, scales, and ligaments. Examples:

'tooth' and (attaches_to some 'maxilla')

'scale' and (attaches_to some 'caudal fin')

NOTE: Teeth and scales are not always related to structures by attaches_to; they can also be part_of an anatomical structure, e.g., 'tooth' part_of (some 'dentition') or 'scale' (part_of some 'scale row')

connected_to connectedness E connected_to E
'sternum' and (connected_to some 'rib')
distally_connected_to connectedness E distally_connected_to E
'leg' and (distally_connected_to some 'pes')
posteriorly connected to connectedness E posteriorly_connected_to E

'neck' and (posteriorly connected to some 'trunk')
proximally connected to connectedness E proximally_connected_to E
'forelimb skeleton' and (proximally_connected_to some 'pectoral girdle skeleton')
develops_from development E develops_from E
'endochondral bone' and (develops_from some 'cartilage element')
has_muscle_insertion muscle attachment 'muscle X' has_muscle_insertion E
'triceps brachii' and (has_muscle_insertion some 'olecranon')
has_muscle_origin muscle attachment 'muscle X' has_muscle_origin E
'triceps brachii' and (has_muscle_origin some 'humerus')
serves_ as _attachment _site_ for muscle attachment E serves_as_attachment_site_for muscle X

has_part mereological E has_part E
'premaxilla' and (has_part some 'anatomical projection')
part_of mereological E part_of E
'anatomical projection' and (part_of some 'premaxilla')
bearer_of quality E bearer_of Q
tooth' and (bearer_of some 'tapered')
inheres_in quality Q inheres_in E
'length' and (inheres_in some 'coracoid bone')
decreased_in_magnitude_relative_to size
[1]
increased_in_magnitude_relative_to size
[1]
similar_in_magnitude_relative_to size
[1]
adjacent_to spatial E adjacent_to E

anterior_to spatial E anterior_to E
'basal fulcrum' and (anterior_to some 'dorsal fin')
deep_to spatial E deep_to E

distal_to spatial E distal_to E
'radial' and (distal_to some 'ulnare')
dorsal_to spatial E dorsal_to E
'anatomical region' and (dorsal_to some (glenoid fossa and (part_of some 'scapula')
encloses spatial E encloses E

extends_from spatial E extends_from E
'anatomical surface' and (extends_from some 'parietal bone')
extends_to spatial E extends_to E
'anatomical surface' and (extends_to some 'frontal bone')
has_cross_section spatial

in_anterior_side_of spatial E in_anterior_side_of E

in_distal_side_of spatial E in_distal_side_of E

in_lateral_side_of spatial E in_lateral_side_of E

in_left_side_of spatial E in_left_side_of E
'frontal bone' and (in_left_side_of some 'body')
in_median_plane_of spatial E in_median_plane_of E

in_posterior_side_of spatial E in_posterior_side_of E

in_proximal_side_of spatial E in_proximal_side_of E

in_right_side_of spatial E in_right_side_of E
 'frontal bone' and (in_right_side_of some 'body')
located_in spatial E located_in E

overlaps spatial E overlaps E
Two structures overlap if they have some part in common. For example, metapterygoid-hyomandibular joint is post-composed as:

'joint' and (overlaps some 'metapterygoid') and (overlaps some 'hyomandibula')

passes_through spatial
BSPO relation. Need to check usage
posterior_to spatial E posterior_to E

proximal_to spatial E proximal_to E

surrounded_by spatial E surrounded_by E

surrounds spatial E surrounds E
'anatomical projection' and (surrounds some 'popliteal area')
ventral_to spatial E ventral_to E

vicinity_of spatial E vicinity_of E

not
Q not Q
Used to represent complementary phenotypes, for example:

'shape' and (not some 'round')

Evidence Codes

**Note: Does not apply to current curation

We record phenotype descriptions as properties of species, and annotations are assigned one of three evidence codes based on the level of evidence given by an author for phenotype observations. These specimen evidence codes are in an Evidence Codes Ontology that was developed by the broader biological community (see http://obofoundry.org/cgi-bin/detail.cgi?id=evidence_code). We have added evidence codes to this ontology, and we use the following in order below from strong to weak evidence.

Inferred from Voucher Specimen (IVS)

Used when an annotation is made on the basis of a phenotype description for a species or higher level group that is given by an author who explicitly references an observation of a voucher specimen(s). Voucher specimens are defined as those specimens with permanent museum catalog numbers. Thus it would be possible for a person to examine this particular specimen and observe the annotated phenotype.

  • Note: if there is a matrix in the paper, the IVS evidence code is assigned to all annotations linked to the character list.

Traceable Author Statement (TAS)

The TAS evidence code covers author statements that are attributed to a cited source. Typically this type of information comes from review articles. Material from the introductions and discussion sections of non-review papers may also be suitable if another reference is cited as the source of experimental work or analysis. When annotating with this code the curator should use caution and be aware that authors often cite papers dealing with experiments that were performed in organisms different from the one being discussed in the paper at hand. Thus a problem with the TAS code is that it may turn out from following up the references in the paper that no experiments were performed on the gene in the organism actually being characterized in the primary paper. For this reason we recommend (when time and resources allow) that curators track down the cited paper and annotate directly from the experimental paper using the appropriate experimental evidence code. When this is not possible and it is necessary to annotate from reviews, the TAS code is the appropriate code to use for statements that are associated with a cited reference. Once an annotation has been made to a given term using an experimental evidence code, we recommend removing any annotations made to the same term using the TAS evidence code.

Nontraceable Author Statement (NAS)

The NAS evidence code should be used in all cases where the author makes a statement that a curator wants to capture but for which there are neither results presented nor a specific reference cited in the source used to make the annotation. The source of the information may be peer reviewed papers, textbooks, database records or vouchered specimens.