Abstract

In eukaryotic cells, protein phosphorylation is an important and widespread mechanism used to regulate protein function. Yet, of the thousands of phosphosites identified to date, only a few hundred at best have a characterized function. It was recently shown that these functional sites are significantly more conserved than phosphosites of unknown function, stressing the importance of considering evolutionary conservation in assessing the global functional landscape of phosphosites. This leads us to review studies that examined the impact of phosphorylation on evolutionary conservation. While all these studies have shown that conservation is greater among phosphorylated sites compared with non-phosphorylated ones, the magnitude of this difference varies greatly. Further, not all studies have considered key factors that may influence the rate of phosphosite evolution. Such key factors are their localization in ordered or disordered regions, their stoichiometry or the abundance of their corresponding protein. Here we take into account all of these factors simultaneously, which reveals remarkable evolutionary patterns. First, while it is well established that protein conservation increases with abundance, we show that phosphosites partly follow an opposite trend. More precisely, Saccharomyces cerevisiae phosphosites present among abundant proteins are 1.5 times more likely to diverge in the closely related species Saccharomyces bayanus when compared with phosphosites present in the 5 per cent least abundant proteins. Second, we show that conservation is coupled to stoichiometry, whereby sites frequently phosphorylated are more conserved than those rarely phosphorylated. Finally, we provide a model of functional and noisy or 'accidental' phosphorylation that explains these observations.

Interaction Annotations

Increase the total number of rows showing on this page by using the pull-down located below the table, or use the
page scroll at the table's top right to browse through the table's pages; use the arrows to the right of a column
header to sort by that column; filter the table using the "Filter" box at the top of the table; click on the small
"i" buttons located within a cell for an annotation to view further details about experiment type and any other
genes involved in the interaction.

Gene Ontology Annotations

Increase the total number of rows showing on this page using the pull-down located below the table, or use the page
scroll at the table's top right to browse through the table's pages; use the arrows to the right of a column header
to sort by that column; filter the table using the "Filter" box at the top of the table.

Phenotype Annotations

Increase the total number of rows showing on this page using the pull-down located below the table, or use the page
scroll at the table's top right to browse through the table's pages; use the arrows to the right of a column header
to sort by that column; filter the table using the "Filter" box at the top of the table; click on the small "i"
buttons located within a cell for an annotation to view further details.

Regulation Annotations

Increase the total number of rows displayed on this page using the pull-down located below the table, or use the
page scroll at the table's top right to browse through the table's pages; use the arrows to the right of a column
header to sort by that column; to filter the table by a specific experiment type, type a keyword into the Filter box
(for example, “microarray”); download this table as a .txt file using the Download button or click Analyze to
further view and analyze the list of target genes using GO Term Finder, GO Slim Mapper, SPELL, or YeastMine.

Expression Datasets

Increase the total number of rows displayed on this page using the pull-down located below the table, or use the
page scroll at the table's top right to browse through the table's pages; use the arrows to the right of a column
header to sort by that column; filter the table using the "Filter" box at the top of the table; download this table
as a .txt file using the Download button;