Provides input for: Difference between revisions
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
== Annotation Usage Guidelines== | == Annotation Usage Guidelines== | ||
*'''What to capture''' | |||
** Upstream activities that provide an input for a downstream activity. | ** Upstream activities that provide an input for a downstream activity. | ||
Revision as of 06:05, 8 February 2023
Overview and Scope of Use
- This relation is used in GO-CAMs but not in standard annotation extensions.
- This relation is intended to connect successive enzymatic reactions in a pathway, i.e. where the product (output) of the upstream activity is the substrate (input) for the downstream activity.
- When the output molecule of the upstream activity is available in ChEBI, curators should not use this relation, and should instead connect the successive activities via the output molecule: [upstream] has_output [ChEBI] is_input [downstream].
- When the output molecule is not available (usually a modified protein or RNA), use: [upstream] provides_input_for [downstream].
- The 'provides input for' relation is used to relate two GO Molecular Functions when:
- Two Molecular Functions succeed one another directly
- The output of the first molecular function is an input of the second Molecular Function.
- The output of the first molecular function is not available in ChEBI.
Annotation Usage Guidelines
- What to capture
- Upstream activities that provide an input for a downstream activity.
- What not to capture
- Pathways in which all inputs and outputs are described in ChEBI.
Examples
Ontology Usage Guidelines
- This relation is not used in the ontology.
Cross Reference to the Relation Ontology (RO)
Review Status
Last reviewed: February 8, 2023
Reviewed by: Cristina Casals, Marc Feuermann, Pascale Gaudet, David Hill, Patrick Masson, Paul Thomas, Kimberly Van Auken