The Structural Classification of Proteins (SCOP) database is a comprehensive ordering of all proteins of known structure, according to their evolutionary and structural relationships. The SCOP hierarchy comprises the following levels: Species , Protein , Family , Superfamily , Fold and Class . While keeping the original classification scheme intact, we have changed the production of SCOP in order to cope with a rapid growth of new structural data and to facilitate the discovery of new protein relationships. We describe ongoing developments and new features implemented in SCOP. A new update protocol supports batch classification of new protein structures by their detected relationships at Family and Superfamily levels in contrast to our previous sequential handling of new structural data by release date. We introduce pre-SCOP, a preview of the SCOP developmental version that enables earlier access to the information on new relationships. We also discuss the impact of worldwide Structural Genomics initiatives, which are producing new protein structures at an increasing rate, on the rates of discovery and growth of protein families and superfamilies. SCOP can be accessed at http://scop.mrc-lmb.cam.ac.uk/scop .
The Structural Classification of Proteins (SCOP) is a database of known structural and evolutionary relationships amongst proteins of known structure ( 1 ). By analogy with taxonomy, it has been created as a hierarchy of several obligatory levels. The fundamental unit of classification is a domain in the experimentally determined protein structure. Protein domains are grouped at different levels according to their sequence, structural and functional relationships. Proceeding from bottom to top, the SCOP hierarchy comprises the following levels: protein Species , representing a distinct protein sequence and its naturally occurring or artificially created variants; Protein , grouping together similar sequences of essentially the same functions that either originate from different biological species or represent different isoforms within the same organism; Family containing proteins with related sequences but typically distinct functions; and Superfamily bridging together protein families with common functional and structural features inferred to be from a common evolutionary ancestor. Near the root, the basis of classification is purely structural: structurally similar superfamilies with different characteristic features are grouped into Folds , which are further arranged into Classes based mainly on their secondary structure content and organization. The seven main classes in the latest release (1.73, forthcoming) contain 92 927 domains organized into 3464 families, 1777 superfamilies and 1086 folds. The SCOP domains correspond to 34 495 entries in the Protein Data Bank (PDB) ( 2 ). Statistics of the current and previous releases, summaries and full histories of changes and other information are available from the SCOP website ( http://scop.mrc-lmb.cam.ac.uk/scop/ ) together with parseable files encoding all SCOP data ( 3 ). The sequences and structures of SCOP domains are available from the ASTRAL compendium ( 4 ), and hidden Markov models of SCOP domains are available from the SUPERFAMILY database ( 5 ).
Since the creation of SCOP in 1994, the number of known protein structures has grown more than 20-fold, whereas the numbers of SCOP folds, superfamilies and families have increased 4-fold, 5-fold and 7-fold, respectively. Besides an increased workload caused by the rapid data growth, processing these data for SCOP classification revealed more subtleties of protein relationships as well as new types of such relationships. It has become increasingly difficult to update the database while maintaining its original design. Accommodation of large numbers of new structures and their relationships within the SCOP hierarchy required some adjustments of the original classification scheme. In particular, there are large superfamilies, which continue to grow, accumulating many more new families and proteins. The division of these most populous superfamilies into families departed from the original SCOP scheme: their families consist of proteins of very similar structures that may or may not have a significant global sequence similarity. The proteins in these families are presumably more closely related to each other than to proteins in other more structurally divergent families.
A large proportion of new structures come from worldwide Structural Genomics initiatives, which are producing them at an increasing rate ( 6 , 7 ). Generally these structures are functionally uncharacterized which complicates their classifications at the Protein and Superfamily levels. Therefore, the initial classifications of such structures may be provisional. Discoveries of new relationships may either confirm these classifications or revise them. Other complications for a hierarchical classification come from the discoveries of probable remote homologies between superfamilies of distinct protein folds and the non-trivial structural relationships within sequence families ( 8 , 9 ).
While keeping the original classification scheme intact, we have changed the production of SCOP in order to cope with the growing amount of the new structural data and to facilitate the discovery of new distant relationships. Here we describe ongoing developments and new features implemented in the SCOP database and changes introduced to the SCOP update protocol. We also analyze the classification of new structures targeted by the structural genomics initiatives and discuss the impact of these initiatives on the rates of discovery and growth of protein families and superfamilies.
NEW SCOP UPDATE PROTOCOL
We have introduced significant changes to the SCOP update protocol since our previous report ( 10 ). These include a new data management system that supports batch analysis of new structures and their relationships and that also makes use of a relational database. We use a new protocol to produce SCOP that adds steps of fully automatic classification and pre-classification of protein structures. Following these changes, future SCOP releases will attempt to include important new content from the PDB archive by prioritizing the representative structures of members of new protein families, superfamilies and folds, although this will compromise their completeness. SCOP release 1.71 is the last release guaranteed to provide a complete survey of all PDB entries released before a certain date.
The relationships in SCOP are established by expert analysis of sequence, structural and functional similarities amongst proteins with known structure. Typically, the protein domains at the bottom levels of the classification hierarchy share significant sequence similarity that together with their common functional features suggests a common evolutionary origin. The protein relationships at the Superfamily level (and in some families) are more distant, but some of them can be detected with more advanced profile searches. Taking into account these organizational principles, we have developed a new update pre-classification protocol to optimize production and accelerate classification of new protein structures in SCOP. The methodology includes consecutive steps of sequence clustering and database searches using a combination of search methods. The similarity thresholds for these methods are set to less restrictive values than defaults, resulting in less stringent matches. This approach is justified because these borderline results will be subjected to manual inspection. It can suggest additional ‘true’ distant relationships, which otherwise would be missed. Database searches are performed using a selected non-redundant sequence set of representative update structures. The outputs of the database-search programs are analyzed and compared automatically and provisional classification is made for those representative proteins where a sequence match indicates a possible relationship to SCOP domains. While the new pre-classification protocol is entirely based on sequence comparisons, the analysis of structural similarities and final classification of the protein structures in the database will continue to rely on the SCOP authors’ knowledge and expertise.
The workflow of the update protocol is shown in detail in Figure 1 . The BLAST search allows detection of close homologs, which usually belong to the same SCOP family, whereas the two-step PSI-BLAST ( 11 ) and RPS-BLAST searches are used to identify similarities indicative of a more distant relationship (at the Superfamily level). Where the results of PSI-BLAST and RPS-BLAST methods overlap, they provide a consensus pre-classification that has proved to be reliable. In addition, each of these methods detects unique matches, which assist the final classification. For example, such a unique match suggested the relationship of an uncharacterized protein AF0060 from Archaeoglobus fulgidus ( 12 ) to the recently discovered superfamily of all-alpha NTP pyrophosphohydrolases with a potential ‘house cleaning’ function ( 13 ). This relationship was detected only by RPS-BLAST through Pfam families PF03819 and PF08761, both being linked to this SCOP superfamily. Manual inspection of the AF0060 structure confirmed the superfamily assignment, but also revealed its distinct features, including the subunit fold, tetrameric biological unit and active site architecture. Therefore we classify AF0060 to a new family of this superfamily. This example underlines intrinsic differences between the sequence-based annotations and the structural classification. For example, Pfam assigns AF0060 to the MazG-like family (PF03819), to which it shares a local sequence similarity, including the conserved metal ion-binding motif. The SCOP classification does not support this family assignment but suggests that AF0060 has a more distant relationship to the MazG-like proteins at the Superfamily level.
The computed sequence comparisons and the automatic provisional classifications of the update structures are imported into a MySQL relational database together with the SCOP classification hierarchy and detailed information on the PDB entries. All data are stored in a relational table format that offers the ability to capture all necessary information for a given protein structure such as PDB coordinate and sequence data, protein source and NCBI taxonomy ( 14 ), relationships to other proteins within the database and relationships to external sequence resources such as Pfam ( 15 ) and UniProt ( 16 ). Having the data available in the relational database allows complex queries and extensive analysis of the protein relationships. The database schema is flexible and it can readily accommodate third-party resources or new extensions of different types of automatic and manual annotations. It also allows continuous data flow inputs and hence synchronization with the PDB releases.
The new SCOP update system supports analysis of unclassified protein structures by the detected relationships amongst themselves and to already classified structures in contrast to our previous sequential handling of new structural data by release date. Thus, the manual curation of the representative update structures is carried out incrementally by analyzing the proteins’ Family and Superfamily relationships. Priority is given to representatives of new sequence families, in particular those targeted by structural genomics. This allows a rapid accumulation of new SCOP families, superfamilies and folds. Related structures with identical and nearly identical sequences to representative domains classified in the latest official SCOP release or in the SCOP developmental version are classified automatically. Possible structural diversity amongst these proteins usually arises from segment swapping, presence of chameleon sequences or functional conformational changes. A comprehensive annotation of these will be provided in the SISYPHUS database, a companion to the SCOP database ( 9 ).
PRE-SCOP—A PREVIEW OF THE SCOP DEVELOPMENTAL VERSION
In addition to the official SCOP build, starting with the release 1.71, we provide a preview of the SCOP developmental version (pre-SCOP, http://www.mrc-lmb.cam.ac.uk/agm/pre-scop/ ) that shows a snapshot of the ongoing classification update. Pre-SCOP is built using the classification data from the current SCOP release and data from the SCOP update. Pre-SCOP can be updated more frequently than the official SCOP release, as the curation of the pre-classified data progresses. This enables earlier access to the information on new structural relationships. SCOP users can request a higher priority to be given to the classification of a particular recent structure of general interest in PDB to be added to pre-SCOP.
At present there is no reclassification of the current SCOP entries in pre-SCOP. These entries retain the same ‘stable’ identifiers as in the latest SCOP release. All new nodes are assigned provisional six-digit identifiers counting down from 999 999. These identifiers are unique for a given release of pre-SCOP but are not stable across updates. The pre-SCOP Web interface allows browsing the classification hierarchy in a similar manner as the official SCOP site. A search engine can be used to find entries matching any identifiers or other text. When browsing pre-SCOP, all new folds are listed at the top of each Class page. In all other levels of the SCOP hierarchy, the new entries are listed at the bottom of the parent node page. Some functionalities of the official SCOP web site such as molecular viewer, expand and shrink options, and links to domain sequences are not available in pre-SCOP. New features unique to pre-SCOP include graphical display of the sequence–structure mappings hyperlinked to the SCOP, PDB and UniProt entries, available at the Domain level. Pre-SCOP also lists the provisional classifications derived from the automatic sequence comparisons. These are displayed only for the entries assigned to a given family at the family page.
NEW ADDITIONS AND CLASSIFICATION REFINEMENT
Changes in SCOP domain boundary definitions
Previously, SCOP domains that span an entire PDB chain did not have explicit beginning and end boundaries. These single domains may contain artificial sequences such as purification tags and other parts of cloning constructs. They may include unstructured parts of neighboring domains at one or both termini. These artifacts can result in significant sequence matches between unrelated SCOP domains. Starting with this release, we have introduced explicit begin–end boundaries for each new domain in SCOP and will gradually extend this to older entries. Thus, all protein domains in SCOP, with the exception of those that are artificially designed, will represent a distinct region of protein structure that has been derived from a natural protein sequence.
The SCOP unique identifiers ( sunid ) denote a unique node in the classification hierarchy and therefore do not allow retrieval of proteins or protein domains from a given organism. The SCOP species name does not always coincide with the name of the protein's biological source but also may represent a distinct sequence variant (isoform) of the same functional protein in a given biological species. For example, human hemoglobin β-chain and its embryonic variants are classified as separate SCOP species. Therefore all SCOP domains from a given organism cannot always be retrieved by the species name. In order to provide a consistent taxonomic presentation of SCOP entries, we attributed the NCBI TaxIDs to the Species nodes. These relationships are provided as a parseable file.
Curated relationships to sequence databases
We have extended the scope of the curated data to SCOP–Pfam relationships and mappings of SCOP domains on UniProt sequences. Relationships between SCOP nodes and Pfam families are rather complex due to genuine design differences and technical underpinnings of these databases. The curated relationships between SCOP and Pfam families are currently shown mainly in the comment field at Family level. Similarly, many comments at Species level include curated UniProt domain boundaries of SCOP domains mapped to the corresponding sequences. Future SCOP releases will provide this information in a parseable format.
The new developments in SCOP assure a step to the future transitions we are planning to introduce in the database. An ongoing project aims to define a reference SCOP sequence that represents a set of identical or nearly identical proteins with known structure and corresponds to a natural sequence as deposited in the public databases. A large portion of the valuable information in SCOP is stored in the form of free-text description. We are currently working on converting these free-text comments into more structured and machine-readable format.
A major enterprise is the planned redefinition (and renaming) of the Fold level of the SCOP hierarchy to enable the grouping of superfamilies on more than one basis. This would allow the classifications of many more known relationships in SCOP while preserving its basic hierarchy.
SCOP AND REMEDIATED PDB
Remediation of the PDB archive resulted in a number of changes directly affecting the SCOP data, which have been ‘remediated’ in response. The reassignment of the PDB chain identifiers caused a corresponding reassignment in the affected SCOP domains, changing their sid identifiers. These identifiers, derived from the PDB filename and chain identifiers, are ‘short names’ for SCOP domains, conventionally used by bioinformatics databases and tools to link to the SCOP pages. We would like to advise that the SCOP unique identifiers ( sunid ) for these domains remain unchanged and will provide a stable reference to the remediated entries in SCOP. We also would like to caution that there are changes in some PDB sequences that may affect the associated ASTRAL data.
IMPACT OF STRUCTURAL GENOMICS ON THE DISCOVERY OF PROTEIN RELATIONSHIPS IN SCOP
We investigated the impact of structural genomics on the rates of discovery and growth of protein families and superfamilies. Using the new update procedure, we collected and classified the structures determined by worldwide Structural Genomics initiatives and related structures from structural biology projects. In our analysis, we focused on the two central levels of SCOP hierarchy, Family and Superfamily , specifying the probable near and far evolutionary relationships, respectively. Because the SCOP hierarchy is obligatory, each protein structure is assigned to a family and a superfamily, regardless of whether there is a related structure at the corresponding levels or not. If there is another protein in a family, it becomes a ‘true’ family; otherwise it is a ‘singleton’ family. Similarly, a ‘true’ superfamily must contain two or more families, whereas a ‘singleton’ superfamily consists of a single family.
There are classification caveats for functionally uncharacterized proteins. Those of similar sequences are usually grouped at Family level, but, when their functions are established, they may be reclassified at the lower, Protein level. Also, the lack of functional evidence hinders the discovery of Superfamily relationships for such protein families, so that it is not always achievable at the time of creation of new families in SCOP. If there is no such relationship discovered, a new ‘singleton’ superfamily is created. This classification can be revised during a subsequent database update, when new evidence appears. For example, the hypothetical protein PA1492 ( 17 ), initially classified in its own superfamily in release 1.69, was reclassified in the next release 1.71 in the N -(deoxy)ribosyltransferase-like superfamily. This superfamily also unified the functionally and structurally characterized N -deoxyribosyltransferase and ADP-ribosyl cyclase-like families, which structural and mechanistic similarities remained unrecognized for a decade since the unraveling of their structures. PA1942 has a very similar putative active site and is predicted by SCOP to have a deoxyribosyltransferase activity.
Hereafter, we refer to a SCOP family (superfamily) that contains a (domain of) structural genomics (SG) target as a SG-family (SG-superfamily, respectively). There were 1693 SG-families and 957 SG-superfamilies populated with domains from 4198 SG targets in PDB (released up to June 2007). For most of these domains, we found relationships to other proteins classified in SCOP at one or both of these two levels. For a small fraction (∼5%) of SG targets, we found no close or distant homolog. Only distant homologs were identified for <7% of SG targets. There was a nominal contribution to a small fraction (30%) of SG-families, where SG domains were neither the first nor the second member of the family and <30% of its content. About 30% of the SG-families were singletons. Nearly three-fifths of these singleton families belong to ‘true’ SG-superfamilies, and only 42% were a single member of superfamily ( Figure 2 ).
Nearly half of the SG domains, at the time of their release, represented a new SCOP family. We observed a general trend, wherein the release of the first representative structure of a family was followed shortly by the release of a related structure determined by a different group of authors. In a few cases, more than one structure had been determined independently for the same protein.
A significant increase in the number of structurally characterized families facilitated the discovery of new relationships at the Superfamily level. More than half of families in ‘true’ SG-superfamilies contain SG domains. About half of SG domains defined a new family and hence contributed to the discovery of a new relationship. Analysis of the distribution of protein families characterized by structural genomics has confirmed a dominant role of the largest known superfamilies, which have grown further in the numbers of constituent families. There are other superfamilies, which have grown large rather unexpectedly ( Table 1 ). The evolutionary success of these ‘new rich’ superfamilies is probably due to the presence of unusual conserved and, presumably, functionally important features in their folds. Interestingly, the first several structures of ‘metagenomic’ targets from environmental samples, selected as representative of novel sequence families ( 18 ), all belong to these ‘new rich’ superfamilies, mostly to the dimeric α + β barrel superfamily in SCOP.
|SCOP Superfamily||Number of SG-FA||Coverage by SG-FA (%)||Representative structure|
|Dimeric α + β barrel||18||78||1mwq|
|SCOP Superfamily||Number of SG-FA||Coverage by SG-FA (%)||Representative structure|
|Dimeric α + β barrel||18||78||1mwq|
SCOP was created over a decade ago, when remote homology between proteins was mainly deduced from structural analysis. Since its creation, the tree-like classification has continuously evolved with the increasing amount of structural data. The recent advances in sequencing technologies resulted in a wealth of sequence data and the progress in profile-based database searches allowed the inference of new distant relationships from sequence analysis. While remaining focused on the structure-guided discovery of new evolutionary relationships at Superfamily level, SCOP now relies on the integrated sequence resources in the classification of new structures and refinement of the existing classifications.
The growth of structurally characterized protein families facilitated the discovery of new protein relationships in SCOP. Expansion of the existing protein superfamilies has provided additional structural and functional insights for their constituent members. The identification of new relationships has benefited from the apparent redundancy of joint structural biology and structural genomics efforts. Structural comparisons have revealed many examples of non-trivial protein relationships, suggesting that significant structural variations within sequence families are more common than were thought before.
This work was supported in part by the MRC strategic grant G0100305. A.A. and D.H. thank Prof. Sir Alan Fersht for the continuing financial support. J.-M.C. and S.E.B. are supported by NIH grant R01-GM073109. J.-M.C. is supported by the US Department of Energy under contract DE-AC02-05CH11231. Funding to pay the Open Access publication charges for this article was provided by the MRC.
Conflict of interest statement . None declared.