Annotation Extension Relation:has direct input: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(24 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Back to [http://wiki.geneontology.org/index.php/Annotation_usage_examples_for_each_annotation_extension_relation  Annotation usage examples for each annotation extension relation]
#REDIRECT [[Annotation]]


Back to [http://wiki.geneontology.org/index.php/Annotation_Extension_Relation:has_input Annotation usage examples for has input]
'''THIS RELATION IS DEPRECATED'''
 
Curators should use  [http://wiki.geneontology.org/index.php/Annotation_Extension_Relation:has_input has input] to capture inputs/substrates/targets of Molecular Functions
 
<pre style="color:#808080">


==Definition==
==Definition==
Line 8: Line 12:


==Comment==
==Comment==
To use this relationship there must be evidence that the gene product in column 2 is known/predicted to bind the molecular target in column 16.
This can be a co-immunoprecipitation (for example) demonstrated in the paper being annotated, or from evidence available in another paper, or from evidence of protein interactions which have been demonstrated in another paper for orthologous molecules.


If the entity is indirectly bound/acted upon by the gene product that is the subject of an annotation, then the relation: has_indirect_input should be considered.
Without evidence of a relevant interaction use the relationship has_input


==Synonyms==
==Synonyms==
Line 33: Line 40:
[[ENTITY_UNION:0000005]] ! chemical, gene product, or complex
[[ENTITY_UNION:0000005]] ! chemical, gene product, or complex


==Annotation Extension Usage Examples==
</pre>
 
'''Transcription factor binding to potential target sequences in vitro:'''
 
Statement from paper: 
 
''By performing gel electrophoretic mobility shift assays, we could detect efficient binding of ATF-2 to the elements found in the bec-1 and lgg-1 promoters (Fig. 5C).'' 
 
(Note that binding to lin-48 is also reported as a positive control).
 
{| class="wikitable" border="1"
|-
! Gene Name (col 2)
! GO ID (col 5)
! Reference (col 6)
! Evidence (col 7)
! Annotation Extension (col 16)
|-
| WBGene00000220
|GO:0001012 <span style="color:green">RNA polymerase II regulatory region DNA binding</span>
| PMID:21502138
| IDA
|
has_direct_input(WB:WBGene00000247 <span style="color:green">bec-1</span>)|has_direct_input(WB:WBGene00002980 <span style="color:green">lgg-1</span>)|has_direct_input(WB:WBGene00003033 <span style="color:green">lin-48</span>)
 
|}
 
 
'''Targets of protein kinase activity:'''
 
Example 1 Statement from paper:
 
''A final line of evidence that BAF-1 is a substrate for VRK-1 was obtained with purified recombinant proteins, which demonstrated that BAF-1 was phosphorylated by VRK-1 in vitro (Figure 4H, lower panel). In addition, VRK-1 was autophosphorylated (Figure 4H, upper panel).''
 
 
{| class="wikitable" border="1"
|-
! Gene Name (col 2)
! GO ID (col 5)
! Reference (col 6)
! Evidence (col 7)
! Annotation Extension (col 16)
|-
| WBGene00017895
|GO:0004672 <span style="color:green">protein kinase activity</span>
| PMID:17170708
| IDA
|
has_direct_input(WB:WBGene00000235 <span style="color:green">baf-1</span>)|has_direct_input(WB:WBGene00017895  <span style="color:green">vrk-1</span>)
|}
 
Example 2:
 
''If protein SGD:A phosphorylates protein SGD:B then annotate A to:''
 
{| class="wikitable" border="1"
|-
! Gene Name (col 2)
! GO ID (col 5)
! Reference (col 6)
! Evidence (col 7)
! Annotation Extension (col 16)
|-
| SGD:A
|GO:0004672 <span style="color:green">protein kinase activity</span>
| PMID:17170708
| IDA
| has_direct_input(SGD:B <span style="color:green">B</span>)
|}
 
NOTE we would not include a separate annotation line for B, because we only have annotation lines for active participants
 
Strictly speaking, the input is SGD:B in the unphosphorylated state and the output is SGD:B in the phosphorylated state. However, currently we do not have IDs for these separate protein forms. Really B is both an input and an output. We standardize on has_input here.
 
'''Note there is no need to say:'''
 
{| class="wikitable" border="1"
|-
! Gene Name (col 2)
! GO ID (col 5)
! Reference (col 6)
! Evidence (col 7)
! Annotation Extension (col 16)
|-
| SGD:A
|GO:0004672 <span style="color:green">protein kinase activity</span>
| PMID:17170708
| IDA
|
has_direct_input(SGD:B <span style="color:green">B</span>)|has_direct_input(CHEBI:15422 <span style="color:green">ATP</span>)
|}
 
'''Or even:'''
 
{| class="wikitable" border="1"
|-
! Gene Name (col 2)
! GO ID (col 5)
! Reference (col 6)
! Evidence (col 7)
! Annotation Extension (col 16)
|-
| SGD:A
|GO:0004672 <span style="color:green">protein kinase activity</span>
| PMID:17170708
| IDA
|
has_direct_input(SGD:B <span style="color:green">B</span>)|has_direct_input(CHEBI:15422 <span style="color:green">ATP</span>)|has_output(SGD:B <span style="color:green">B</span>)|has_output(CHEBI:16761 <span style="color:green">ADP</span>)
|}
 
These are correct but this is pointless because the additional info is redundant with what we already know about kinase activity (this is actually made computable in MF x CHEBI)
 
Inclusion of the C16 information in the Molecular Function ''protein kinase'' and to the Biological Process ''phosphorylation'' can be useful, as these annotation extensions will not be created transitively. However, this information can be inferred computationally.
 
'''If protein SGD:A phosphorylates protein SGD:B and SGD:C then annotate A to:'''
 
{| class="wikitable" border="1"
|-
! Gene Name (col 2)
! GO ID (col 5)
! Reference (col 6)
! Evidence (col 7)
! Annotation Extension (col 16)
|-
| SGD:A
|GO:0004672 <span style="color:green">protein kinase activity</span>
| PMID:17170708
| IDA
|
has_direct_input(SGD:B <span style="color:green">B</span>)|has_direct_input(SGD:C <span style="color:green">C</span>)
|}
 
There is some redundancy with interaction databases here. Capturing this as GO annotation is more expressive as you can say "A phosphorylates B during pathway C". But if you want to capture this in interaction databases exclusively we have tools for generating GO annotations from these (just as we have tools for capturing GO annotations from pathway databases).
----
 
 
Back to [http://wiki.geneontology.org/index.php/Annotation_Extension:_Capturing_participants Annotation Extension: Capturing participants]


Back to [http://wiki.geneontology.org/index.php/Annotation_usage_examples_for_each_annotation_extension_relation  Annotation usage examples for each annotation extension relation]


[[Category:relations]]
[[Category:Deprecated]]
[[Category:annotation extension]]

Latest revision as of 08:36, 27 September 2021

Redirect to:

THIS RELATION IS DEPRECATED

Curators should use has input to capture inputs/substrates/targets of Molecular Functions

 

==Definition==

Identifies an entity directly affected (bound, transported, modified, consumed or destroyed) by the gene product's participation in a Molecular Function or Biological Process.

==Comment==
To use this relationship there must be evidence that the gene product in column 2 is known/predicted to bind the molecular target in column 16.
 
This can be a co-immunoprecipitation (for example) demonstrated in the paper being annotated, or from evidence available in another paper, or from evidence of protein interactions which have been demonstrated in another paper for orthologous molecules.

Without evidence of a relevant interaction use the relationship has_input

==Synonyms==

directly_localizes (NARROW)

has_direct_target (EXACT)

has_substrate (NARROW)

==Child terms==

* None

==Scope of use==

===Domain===

BFO:0000007 ! process (Biological Process or Molecular Function) 

===Range===

[[ENTITY_UNION:0000005]] ! chemical, gene product, or complex