| Literature DB >> 19638971 |
Anna Bauer-Mehren1, Laura I Furlong, Ferran Sanz.
Abstract
In past years, comprehensive representations of cell signalling pathways have been developed by manual curation from literature, which requires huge effort and would benefit from information stored in databases and from automatic retrieval and integration methods. Once a reconstruction of the network of interactions is achieved, analysis of its structural features and its dynamic behaviour can take place. Mathematical modelling techniques are used to simulate the complex behaviour of cell signalling networks, which ultimately sheds light on the mechanisms leading to complex diseases or helps in the identification of drug targets. A variety of databases containing information on cell signalling pathways have been developed in conjunction with methodologies to access and analyse the data. In principle, the scenario is prepared to make the most of this information for the analysis of the dynamics of signalling pathways. However, are the knowledge repositories of signalling pathways ready to realize the systems biology promise? In this article we aim to initiate this discussion and to provide some insights on this issue.Entities:
Mesh:
Year: 2009 PMID: 19638971 PMCID: PMC2724977 DOI: 10.1038/msb.2009.47
Source DB: PubMed Journal: Mol Syst Biol ISSN: 1744-4292 Impact factor: 11.429
Comparison between SBML and BioPAX
| SBML | BioPAX | |
|---|---|---|
| Representation format | XML (Extensible Markup Language) | OWL (Web Ontology Language), XML |
| Main purpose | Representation of computational models of biological networks | Pathway description with all details on reactions, components, information on cellular location etc. |
| Entities and reactions | Based on species and reactions ( | Basic ontology based on three classes ( |
| Species (proteins, small molecules etc.) | Pathway (set of interactions) | |
| Reactions (how species interact) | Physical entity with subclasses, such as RNA, DNA, protein, complex and small molecules | |
| Compartment (in which interactions take place) | Interaction with subclasses, such as conversion having biochemicalReaction as subclass, etc. | |
| Number of pathways represented | One model per SBML file | Several pathways per BioPAX file possible (each object has its own RDF id and is hence uniquely identifiable) |
| Reaction kinetics | Allows representation of kinetics, including parameters for reaction rates, initial concentrations etc. | No kinetics as BioPAX is not meant for modelling but pathway representation |
| Levels | Built in levels with different versions. Each level adds new features, such as the incorporation of controlled vocabularies. At the time of writing, the most stable version is SBML Level 2 | BioPAX Level 1: representation of chemical reactions involved in metabolism |
| BioPAX Level 2: adds molecular interactions and protein post-translational modifications | ||
| BioPAX Level 3: any kind of biological reaction, including regulation of gene expression (BioPAX L3 is at the time of writing still in release process) | ||
| The BioPAX project roadmap envisages two additional levels capturing interactions at the cellular level. ( | ||
| Pathway database support | Reactome | Reactome |
| KEGG | KEGG (only BioPAX Level 1) | |
| PID | ||
| PathwayCommons | ||
| Model database support | BioModels | BioModels (conversion from SBML to BioPAX possible) |
| Library for reading/writing | libSBML( | Paxtools ( |
| Software support | Standard modelling software, such as CellDesigner or Copasi ( | Network visualization software, such as Cytoscape or VisANT |
| Network visualization software, such as Cytoscape |
Online pathway and protein–protein interaction (PPI) databases
| Pathway/PPI database | Web link | Standard exchange formats for download | Web service API |
|---|---|---|---|
| Reactome | BioPAX Level 2 | SOAP web service API | |
| BioPAX Level 3 (only some reactions) | Detailed user manual available, example client in Java | ||
| SBML Level 2 | |||
| KEGG | KGML (default format) | SOAP web service API | |
| BioPAX Level 1 (only metabolic reactions) | Example client in Java, Ruby, Perl | ||
| SBML (using converter) | Direct import into Cytoscape | ||
| GPML (using converter) | |||
| WikiPathways | GPML (default format) | SOAP web service API | |
| Converters to standards, such as SBML and BioPAX are in progress | Example clients in Java, Perl, Python, R | ||
| NCI/Nature Pathway Interaction Database (PID) | PID XML (default format) | Access through Pathway Commons | |
| BioPAX Level 2 | |||
| BioCarta | BioPAX Level 2 through NCI/ Nature Pathway Interaction Database (PID) | ||
| Pathway commons | BioPAX Level 2 (default format for pathways) | HTTP URL-based XML web service through cPath | |
| PSI-MI (default format for protein–protein interactions) | Direct import into Cytoscape | ||
| Cancer cell map | BioPAX Level 2 | HTTP URL-based XML web service via cPath | |
| HumanCyc | BioPAX Level 2 | Access through Pathway Commons and Pathway Tools ( | |
| BioPAX Level 3 | |||
| IntAct | PSI-MI | Access through Pathway Commons | |
| HPRD | PSI-MI | Access through Pathway Commons | |
| MINT | PSI-MI | Access through Pathway Commons |
Figure 1EGFR map. EGFR map created using CellDesigner ver.2.0 (Oda ). This map has been coloured to show the entities and reactions that are in common between the EGFR map and information found in Reactome. Red colour denotes that the entities and reactions are equivalent, purple connotes that they are similar but differ in some description details, and white is used for entities and reactions that could not be directly found in Reactome. In a second step, the map was extended by querying Reactome with key entities appearing in the EGFR map, which were missing in the representation of the EGFR pathway in Reactome. After this extension process, we coloured new equivalent entities in green and new similar entities (the ones that are differently described in both resources) in turquoise. For comparing the EGFR map with the pathways downloaded from Reactome, the Reactome pathways have been imported into Cytoscape and the entities and reactions have been manually compared using the node and edge search functions of Cytoscape. As the SBML version of the EGFR map does not contain unique identifiers for the nodes (species), all names have been first matched to Entrez Gene identifiers, which have then been used for comparing entities between the EGFR map and Reactome. In the extension process canonical names as well as Entrez Gene and UniProt identifiers have been used to retrieve all the information available in Reactome. In some cases, when no results were obtained in this way, the search was additionally expanded. For example, to find the EGFR crosstalk with the GPCR signalling, we additionally searched for ‘G protein'. GPCR signalling pathways activated by S1P1, S1P2/3, LPA1, LPA2, EP3 and EP2/4 were not found in Reactome. Instead, GPCR signalling through thrombin and glucagon receptors that are related to EGFR signalling (Prenzel ; Buteau ) are present in Reactome and were incorporated into the EGFR map to complete the missing crosstalk.
Figure 2Comparison of ERK signalling as found in the EGFR map and in Reactome. In Reactome, ERK1 or ERK2 are phosphorylated by MKK1 or MKK2, respectively. The same reaction is found in the EGFR map, but here ERK1 and ERK2 are represented as a single entity, namely ERK1/2, which combines both proteins and can be phosphorylated by MKK1 and MKK2. In Reactome, dimerization and translocation to the nucleus are still separately described for each entity. Then, the representation switches from separate entities to one combined entity. In addition, the dissociation of MKK1 or MKK2, which is needed before the dimerization of ERK can take place, is not described in Reactome. Manual intervention is needed to correctly map both representations.
Figure 3Example—annotation issue. The two reactions ‘Active PLCγ hydrolyses PI4,5-P2' (REACT_12078.2) and ‘IP3 binds with the IP3 receptor, opening the Ca2+ channel' (REACT_12008.1) are connected through the entity IP3 as the hydrolysis of PI4,5-P2 results in DAG and IP3, and then IP3 binds to its receptor enabling the Ca2+ release. However, the process in which IP3, located in the cytosol, translocates to the plasma membrane to bind to its receptor is not precisely described in Reactome, leading to differences in the annotation of both IP3 entities. This precludes the automated merging of both chains of reactions and manual intervention was needed to connect the reactions correctly.
Pathways downloaded for extending the EGFR map
| Extension to | Reactome pathways downloaded | Reactome identifier |
|---|---|---|
| MAP kinase | RAF activation | REACT_2077.4 |
| cascade | MAP kinase cascade | REACT_634.4 |
| ERK1/2 activates ELK1 | REACT_12406.1 | |
| ERK1/2/5 activate RSK1/2/3 | REACT_12487.1 | |
| RSK1/2/3 phosphorylates CREB at serine 133 | REACT_12622.1 | |
| Ca2+ signalling | Active PLCG1 hydrolyses PIP2 | REACT_12078.2 |
| DAG stimulates protein kinase C-delta | REACT_12062.1 | |
| IP3 binds to the IP3 receptor, opening the Ca2+ channel | REACT_12008.1 | |
| Release of calcium from intracellular stores by IP3 receptor activation | REACT_12074.1 | |
| Calcium binds calmodulin | REACT_12602.1 | |
| GPCR signaling | Thrombin-activated activation cascade | REACT_57.1 |
| Glucagon signalling in metabolic regulation | REACT_1665.2 | |
| Cell cycle | p53-dependent G1/S DNA damage checkpoint | REACT_85.1 |
| NRAGE signals death through JNK | REACT_13638.1 | |
| Activation of BAD and translocation to mitochondria | REACT_549.2 | |
| BH3-only proteins associate with and inactivate anti-apoptotic BCL-2 members | REACT_330.1 | |
| Cyclin D-associated events in G1 | REACT_821.2 | |
| Cyclin E-associated events during G1/S transition | REACT_1574.2 |