Go annotation reliability ?
1
1
Entering edit mode
6.6 years ago
Stane ▴ 90

Hey, I have been using Gene Ontology to try to understand some differently express gene and I am now wondering if I should trust the GO annotation.

I was looking at serpinb2, for this gene I am getting GO term: GO:0005576 'extracellular region' and GO:0005615 'extracellular space'. However when I cross reference with Protein atlas, which have antibodies staining assays, then it seems to be clearly inside the cell around the golgi apparatus.

I have been trying to get the reference of those go annotation without success. Therefore which one should be trust, annotation or antibodies staining ?

GO • 6.1k views
ADD COMMENT
0
Entering edit mode

As an aside, when you have discrepancies between two data sources, you should question both data sources. Here, you imply that not seeing the protein in the extracellular space in the HPA antibody staining means the GO annotation is likely wrong. The problem is that the antibody staining may be done under fixation conditions that do not preserve extracellular proteins and so the HPA can't report on them. Absence of evidence is not evidence of absence. When dealing with experimental data, you need to make sure you understand their limitations before reaching conclusions.

ADD REPLY
0
Entering edit mode

Well I may have add that I looked at mass spec data of cell surface for many cell lines, and didn't find much serpinb2, also for some reason the source of the go annotation can not be verified, the link does not work for me. I am not saying the annotation if false, but in this case I am more likely to discard it until I can verify the source.

ADD REPLY
0
Entering edit mode

As far as I could figure it out, one annotation comes from the Reactome database which is largely manually curated, the other from the Panther database annotation of the serpin family. On the other hand, experimental evidence is often conflicted and a lot also depends on context which current GO annotations don't capture, e.g. maybe SERPINB2 is extracellular in certain cell types or conditions and this may or may not be relevant to your work. In this case, SERPINB2 is a well known secreted protein (its synonym is plasminogen activator inhibitor 2) but only in response to some signal, see for example this paper. My point is that in the end, trusting a data set is a subjective matter. However, for statistical data analysis, the handling has to be consistent. It is fine to go gene by gene and review the evidence but when playing this game, one often needs to go deep in the literature to form an opinion.

ADD REPLY
8
Entering edit mode
6.6 years ago

I would encourage you to read about the Gene Ontology's evidence codes: http://www.geneontology.org/page/guide-go-evidence-codes

When you do your enrichment, you should see one of those codes beside your gene(s) of interest. The two GO terms that you've mentioned are very broad and undoubtedly have many 1000s of genes listed.

I just searched and SERPINB2 belongs to a few different GO categories; however, for both GO:0005576 'extracellular region' and GO:0005615 'extracellular space', the evidence code is just 'TAS', i.e., 'Traceable Author Statement (TAS)' (see through the link on evidence codes that I pasted above). Thus, you can make your own interpretation on that...

All of SERPINB2's GO terms are here: http://amigo.geneontology.org/amigo/gene_product/UniProtKB:P05120

My general rule of thumb, and something that I tell all students that I train, is to never trust gene enrichment unless there is clear experimental evidence to back up the enrichment.

Hope that this helps.

ADD COMMENT
1
Entering edit mode

Correction: for GO:0005576 'extracellular region', it is Traceable Author Statement (TAS); for GO:0005615 'extracellular space', it is Inferred from Biological aspect of Ancestor (IBA)

ADD REPLY
1
Entering edit mode

Thank you very much, great answer

ADD REPLY

Login before adding your answer.

Traffic: 2455 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6