Removes input for: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
 
Line 1: Line 1:
== Overview and Scope of Use ==
== Overview and Scope of Use ==
*This relation is used in GO-CAMs but not in standard annotation extensions.
*This relation is used in GO-CAMs but not in standard annotation extensions.
* This relation is intended to represent a negative causal effect of an upstream activity on a downstream activity, in which the two activities act on or modify the same molecular target at the same site(s). As a result, the execution of the upstream activity prevents the downstream activity from occurring (or reduces its rate). This acts like a molecular 'switch' between two outcomes.
* This relation links two activities when the upstream activity effects the execution of the downstream activity due to the two activities acting on or modifying the same molecular target at the same site(s). As a result, the execution of the upstream activity prevents the downstream activity from occurring (or reduces its rate). This acts like a molecular 'switch' between two outcomes.
*The 'removes input for' relation is used to relate GO Molecular Functions (MF) when:
*The 'removes input for' relation is used to relate GO Molecular Functions (MF) when:
**The upstream activity occurs before the downstream activity
**The upstream activity occurs before the downstream activity

Latest revision as of 10:25, 16 March 2023

Overview and Scope of Use

  • This relation is used in GO-CAMs but not in standard annotation extensions.
  • This relation links two activities when the upstream activity effects the execution of the downstream activity due to the two activities acting on or modifying the same molecular target at the same site(s). As a result, the execution of the upstream activity prevents the downstream activity from occurring (or reduces its rate). This acts like a molecular 'switch' between two outcomes.
  • The 'removes input for' relation is used to relate GO Molecular Functions (MF) when:
    • The upstream activity occurs before the downstream activity
    • The upstream activity has a negative effect on the downstream activity
    • The execution of the upstream activity results in an input of the downstream activity becoming unavailable for the downstream activity

Annotation Usage 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 longer 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 makes that amino acid unavailable for a different modification.
  • What not to capture
    • This relation should not be used for inducible activities that remove substrates or inputs of a downstream activity in order to regulate the process.

Examples

  • 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. PMID:36471082

Removes input for GO-CAM example 1

GO-CAM model

  • KMT5A methylates histones H4 at Lys-20, preventing the histone reader activity of TONSL, which specifically binds histone H4 lacking methylation at 'Lys-20' (H4K20me0). PMID:27338793

Removes input for GO-CAM example 2

GO-CAM model

Ontology Usage Guidelines

This relation is not used in the ontology.

Relations Ontology

removes input for

Review Status

Last reviewed: February 15, 2023

Reviewed by: Cristina Casals, Marc Feuermann, Pascale Gaudet, David Hill, Patrick Masson, Chris Mungall, Paul Thomas, Kimberly Van Auken


Back to: Annotation Relations