Removes input for: Difference between revisions
Jump to navigation
Jump to search
Line 16: | Line 16: | ||
** Guidelines | ** Guidelines | ||
*** What to capture | *** 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 | *** 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 | ** Examples | ||
**** Acetylation of a lysine residue removes the ability of that residue to be ubiquitinated. Thus, the acetylation effectively removes the substrate for the ubiquitination enzymes. [https://pubmed.ncbi.nlm.nih.gov/25527407/ Link to Reference] | |||
== Ontology Usage Guidelines == | == Ontology Usage Guidelines == |
Revision as of 10:50, 8 November 2022
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
- Guidelines
- 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.
- What to capture
- Examples
- Acetylation of a lysine residue removes the ability of that residue to be ubiquitinated. Thus, the acetylation effectively removes the substrate for the ubiquitination enzymes. Link to Reference
- Guidelines
Ontology Usage Guidelines
Quality Control Checks
- Annotations can be validated using a Shape Expressions (ShEx) representation of allowed relations between ontology terms.(STILL NEEDS TO BE ENTERED)
Child Terms
Relations Ontology
Review Status
Modified on October 31, 2022
Last reviewed: