Provides input for: Difference between revisions
Jump to navigation
Jump to search
m (→Examples) |
m (→Examples) |
||
| Line 12: | Line 12: | ||
*'provides input for' should be reserved to related successive Molecular Functions in GO-CAM models. | *'provides input for' should be reserved to related successive Molecular Functions in GO-CAM models. | ||
== Examples == | == Examples == | ||
[[File:Provides_input.png|500px|Provides input]] | |||
[http://noctua.geneontology.org/workbench/noctua-visual-pathway-editor/?model_id=63d320cd00001536 GO-CAM model] | [http://noctua.geneontology.org/workbench/noctua-visual-pathway-editor/?model_id=63d320cd00001536 GO-CAM model] | ||
Revision as of 06:00, 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
- 'provides input for' should be reserved to related successive Molecular Functions in GO-CAM models.
Examples
Ontology Usage Guidelines
- This relation is not used in the ontology.
Cross Reference to the Relation Ontology (RO)
Review Status
Reviewed: Nov 2, 2022 DavidH