Difference between revisions of "Annotation guidelines for annotating complexes as annotation objects"

From GO Wiki
Jump to: navigation, search
(Created page with "Category:Protein Complexes ==Annotation guidelines for annotating Complexes as objects== Since its inception, GO has annotated gene products (i.e. proteins or RNA) as the...")
 
(Annotation guidelines for annotating Complexes as objects)
Line 5: Line 5:
  
 
# Column 2 of GAF should have a stable ID of the macromolecular complex. So far IntAct ID or PRO ID are allowed.
 
# Column 2 of GAF should have a stable ID of the macromolecular complex. So far IntAct ID or PRO ID are allowed.
#
+
# Since there is overlap between GO and IntAct complexes, no need to restate that the Intact complex is_a GO complex. It is okay to annotate that the IntAct Complex to CC terms like mitochondrion or cytoplasm or to say that the IntAct complex is a specific type of a generic GO complex.
 +
# Do not annotate complexes that have been inferred by chemogenomics. IntAct will use ECO terms to prevent export of such complexes

Revision as of 13:19, 15 October 2015


Annotation guidelines for annotating Complexes as objects

Since its inception, GO has annotated gene products (i.e. proteins or RNA) as the object of annotation. The GOC has recognized the importance of capturing function and process annotations for macromolecular complexes as objects. This document provides guidelines for annotation complexes.

  1. Column 2 of GAF should have a stable ID of the macromolecular complex. So far IntAct ID or PRO ID are allowed.
  2. Since there is overlap between GO and IntAct complexes, no need to restate that the Intact complex is_a GO complex. It is okay to annotate that the IntAct Complex to CC terms like mitochondrion or cytoplasm or to say that the IntAct complex is a specific type of a generic GO complex.
  3. Do not annotate complexes that have been inferred by chemogenomics. IntAct will use ECO terms to prevent export of such complexes