Removes input for

From GO Wiki
Jump to navigation Jump to search

Overview and Scope of Use

  • The 'removes input for' relation is used to relate GO Molecular Functions (MF) when:
    • The upstream MF occurs before the downstream MF
    • The upstream MF has a negative effect on the downstream MF
    • The execution of the upstream MF is restricted to a specific condition
    • The execution of the upstream MF results in an input of the downstream MF becoming unavailable for the downstream MF

Annotation Usage Guidelines

  • Standared Annotation (This relation should not be used in standard annotation)
    • Guidelines
      • What to capture
      • What not to capture
    • Examples
  • GO-CAM Annotation
    • Guidelines
      • What to capture
        • This relation should be used to capture processes where the cell or organism has a 'choice' about a causal pathway and one choice excludes the other because a substrate is no loger available for a step in the other pathway. Two examples of this are the 'histone code' (PMID:11498575)and the 'ubiquitin code' (PMID:27012465), in which a modification of an amino acid essentially makes that amino acid unavailable for a different modification.
      • What not to capture
        • This relation should not be used for inducible processes that remove substrates or inputs of a process in order to regulate the process.
    • Examples
      • Acetylation of a lysine residue in ubiquitin removes the ability of that residue to be polyubiquitinated. Thus, the acetylation effectively removes the substrate for the ubiquitination enzymes. Link to Reference
      • Methylation of CpG islands in promoters and enhancers prevents DNA binding transcription factors from being able to interact with those regions. So although the overall process is regulatory, the activity of the methyltransferase removes an input (the promoter region or enhancer region) for the DNA binding transcription factor. Link to Reference

Ontology Usage Guidelines

Quality Control Checks

  • Annotations can be validated using a Shape Expressions (ShEx) representation of allowed relations between ontology terms.

Child Terms


Relations Ontology

removes input for

Review Status

Modified on October 31, 2022

Last reviewed:

Back to: Annotation Relations