Authored by the wwPDB annotation staff
January 2014 Version 2.7
Since 1999, the wwPDB has been responsible for processing PDB data
with deposition centers at RCSB PDB, PDBe, and PDBj. The processed
entries follow the PDB format as described in the Protein Data Bank
Contents Guide Version 3.2 (September, 2008), and the mmCIF format
that complies with the PDB Exchange Dictionary (PDBx)
There are some data items for which the processing procedures are ambiguous. Over the course of the last 12 months the annotation teams at the wwPDB deposition sites have worked to formalize many aspects of PDB annotation policies and procedures.
This document presents the annotation processing rules that are a result of this review. These rules will be fully implemented by December 2008. The wwPDB staff will continue to update annotation practices in line with evolving structure determination and annotation methods.
The sections in this document are:
December 2008: Initial release as version 2.2
March 2009: minor revision 2.3, updates on citation, header list, SITE records and added cif templates for structure factors.
April 2009: minor revision 2.4, update header list.
November 2011: major revision 2.5, clarify content, update header list and UniProt sequence submission.
December 2012: Clarify Entry title.
January 2014: Clarify Re-refinement
(see PDB records DBREF and SEQRES)
Sequence is a list of the consecutive chemical components covalently linked in a linear fashion to form a polymer. The chemical components included in this listing may be standard or modified amino acid and nucleic acid residues. It may also include other residues that are linked to the standard backbone in the polymer. Chemical components or groups covalently linked to the side-chains of peptides or groups linked to sugars and/or bases in nucleic acid polymers will not be listed here.
Proteins containing three or more residues forming two consecutive standard peptide bonds will be assigned sequence related records (SOURCE, COMPND, DBREF, SEQRES).
Nucleic acids containing two or more residues linked by standard nucleotide bonding will be assigned sequence related records (SOURCE, COMPND, DBREF, SEQRES).
The sequence records must represent all macromolecules used in the experiment, including HIS- or other expression tags, as well as residues missing from the coordinates due to disorder. Residues cleaved from the macromolecules prior to or during the experiment are not part of the sequence. The sequence can include neighboring cross-linked residues (such as chromophores) and modified amino acids.
If the exact sequence of the sample is not known, due to, for example, proteolysis, the sequence should match the coordinates and a REMARK 999 (_pdbx_entry_details.sequence_details) added. If the entry is a crystal structure, the Matthew's coefficient and solvent content will list author-provided values instead of calculated values.
The sequence database reference token DBREF and _struct_ref, _struct_ref_seq provides the mapping between a polymer in the SEQRES section against a valid sequence database reference.
Each chain for which there is an appropriate sequence database reference will have DBREF, _struct_ref, and _struct_ref_seq records. When no sequence database reference is available the sequence will be self-referenced (i.e. the database reference will be the PDB entry itself).
UniProt (UNP) is the current preferred protein sequence database. Where there are multiple UNP entries for the same protein from the same organism, strain and sequence identity, the UNP entry that has the most annotation will be used. Also, UNP entries that contain the complete protein sequence will be preferred over those that represent protein fragments.
All DNA will be self-referenced. RNA polymers more than 50 residue long will be provide GB dbref if available.
UniProt does not contain variable or hyper-variable regions of the immune system or unnatural sequences, so the PDB entries for such structures will be self-referenced. If the protein does not fall into these categories and does not have a UniProt reference, UniProt automatically gets sequences from the PDB and add the new sequences to UniProt. Depositors do not need to submit their sequence information via SPIN (the UniProtKB submission tool).
The PDB file contains the sequence cross reference available at the time of processing of the entry. If at a point in the future the sequence does appear in UniProt or if a UNP accession code has been changed in Uniprot, the updated version of the sequence database match will be available to users through the SIFTS file generated at PDBe and distributed as part of the wwPDB ftp archive. The PDB file may not be modified to add the sequence cross-reference. Information about SIFTS is available from http://www.ebi.ac.uk/pdbe/docs/sifts/
If related entries with the same sequence do not have UNP references, the DBREF (_struct_ref, _struct_ref_seq_dif) will self-refer to the PDB entry and not refer back to the first PDB entry which contained the particular sequence. For example, if entries 1ABC, 1DEF and 1GHI all had the same antibody sequence, the DBREF (_struct_ref, _struct_ref_seq) in these entries will refer respectively to 1ABC, 1DEF and 1GHI.
Chimeras or fusion proteins should be deposited as a single chain with one chain ID because they were expressed as one chain. Chimeras that were refined with different chain IDs should be deposited with one chain ID for all parts of the chimera, including any linker regions.
The sections of the chimera which match the UNP entry or entries will each have database reference tokens. The sections of the chimera which do not match the UNP entry or entries, such as a linker region, will be self-referenced. Information about this can be added to REMARK 999.
SEQADV (_struct_ref_seq_dif) describes any rational disagreement between a sequence database and the sequence in the PDB file.
The discrepancies listed in the SEQADV records are annotated as engineered mutation(s), cloning artifact(s), variants(s), His tags, insertions, deletions, etc.
The following are not listed in the SEQADV records:
Polymer chains which have the same sequence must have the same chemistry (homogeneous). If one chain has microheterogeneity at one position, but not in another chain at the same position, then these two polymer chains will be treated as two different polymers with two sequences. If a residue has more than one identity at a particular residue number within a chain, this is called microheterogeneity. For heterogeneous chains, the residue which does not match the corresponding UNP residue will be listed in the sequence (SEQRES), regardless of its occupancy. The sum total of occupancies of the different identities of the residues which displays microheterogeneity should be less than or equal to 1.
If the microheterogeneity involves two or more identities for that residue number and no residue identity matches the UNP residue at the corresponding UNP location, the residue with the higher occupancy will be listed in the sequence (SEQRES). If there is no UNP reference, the higher occupancy will be listed in the sequence (SEQRES).
If a residue has two identities at a particular residue number, where one identity is a modified residue and one is the unmodified form, then the modified residue is listed in the sequence. A SEQADV record will be generated for the modified residue between the UNP entry, with the explanation of "microheterogeneity". This is the exception to the rule that SEQADV records would not be created for modified residues.
Alternate position indicators will be used in the coordinates for residues involve in microheterogeneity. The residue listed in the sequence will be listed first in the coordinates and be labeled as alternate position A. The other identity will be assigned alternate B. If there is a third or fourth residue identity, or if one of the identities has its own alternate conformations, these will be assigned alternate IDs in alphabetical order. In the mmCIF file, the microheterogeneity flag is indicated in _entity_poly_seq.hetero and_poly_seq_scheme.hetero.
A full explanation of the microheterogeneity for all residues at a particular residue number may be elaborated in REMARK 999.
This section describes cases of neighboring intra-chain cross-linked typically involving 2 or more sequential amino acids that react with each other to form one "residue". For example, residues 65, 66, and 67 in the PDB entry 1yjf underwent a reaction to form a circularized tri-peptide chromophore (Figure 1).
Figure 1: In entry 1yjf, residues 65, 66, and 67 (neighboring alanine, serine and glycine residues) reacted and generated a chromophore product called [2-(1-AMINOETHYL)-4-METHYLENE-5-OXO-4,5-DIHYDRO-1H-IMIDAZOL-1-YL]ACETIC ACID.
To describe this situation in a PDB entry the following annotation applies:
The wwPDB encourages depositors to provide a smile string and/or chemical name and/or chemical drawing including bond type, bond order and stereochemistry of the ligand in order to facilitate the correct annotation.
Specialized software is used to get the bond types, the stereochemistry, and where possible the IUPAC-compliant name for each ligand in the structure. Verification is done by comparing to the ligand structure in the experiment. When such ligand is found, the atom name is matches to what is defined in the dictionary.
Each ligand is assigned a unique ligand code (up to 3 alphanumeric characters). Annotators use multiple methods to determine if a ligand already exists in the chemical component dictionary. If the stereochemistry and bond types and connectivity match an existing ligand, the code for that ligand is used in the entry. If there is no match, the new ligand is added to the dictionary with an arbitrarily assigned unique identifier.
Several software programs are used to generate a chemical component cif file based on the author's deposited coordinates. The ligand's IUPAC-compliant name is predicted based on the deposited coordinates. All atoms in the component cif file (including H-atoms) will have coordinates. (add about missing atom for complete chemistry) Checks for chemical name, ligand code and connectivity are carried out to verify that duplicates are not added to the chemical component dictionary.
If a particular liagnd found to be existed in the CCD, the ligand code and atom names will be changed to match to dictionary. The atom labels and ligand name will be automatically updated according to the dictionary. It is noted that the atom names always start with element type.
If the polypeptide like inhibitor is a nature product or if it has a sequence database reference, or if the majority of the residue components are standard or modified amino acids, it is treated as a polymer chain with sequence and REMARK 400 (_pdbx_entity_annotation) can be added for additional information. Otherwise the inhibitor is treated as a ligand and REMARK 630 (_entity.details and _pdbx_struct_chem_comp_feature) will be used to describe this inhibitor.For details, see current Format Guide.
Whenever possible, the overall charge for new ligand definitions should be neutral. This provides maximum compatibility with other chemical databases such as CAS and PubChem. The overall charge of the ligand is included in the chemical component dictionary and also listed in the FORMUL record of the PDB format file. The individual atoms may have a charge in the atom records.
Ligands in NMR structures produce unique challenges, because all hydrogen atoms used in the structure must be present in the dictionary. The accurate chemical description of molecules which may exist in multiple protonation states is difficult to achieve in single chemical component definitions. To describe this complexity for the standard amino acids and nucleotides, a special component dictionary has been created. Within this dictionary are complete chemical descriptions of observed protonation states which include accurate formulae, formal charges and IUPAC atom nomenclature for each case.
HETNAM (_chem_comp.name) Whenever possible, the name automatically produced by specialized chemical naming software is used. Exceptions to this rule are common (as judged by annotation staff) biological names, and brand names for drugs. Should ACDlabs, Chemdraw or Pubchem fail to predict a name, common names or names supplied by the depositor may be used.
HETSYN (_chem_comp.pdbx_synonyms) Other names requested by depositors may be included as synonyms, at the discretion of the annotator. It should be noted any synonyms provided by the depositor should be meaningful and widely used names for the ligand.
Exceptions / Issues: Established common names can be used as HETNAM as long as the IUPAC-compliant name is stored in HETSYN. Examples would be "Fluconazole" as HETNAM and "2-(2,4-difluorophenyl)-1,3-bis(1,2,4-triazol-1-yl)propan-2-ol" as HETSYN. If a ligand name is changed or synonyms are added, every PDB entry containing that ligand will be updated.
Metals There are difficulties in handling dative bonds in coordination complexes and pi-bonding in organometallic complexes. These inorganic molecules need to be built on a case by case basis to reflect their chemical nature. An ambiguous flag (_chem_comp.pdbx_ambiguous_flag) is included in the chemical component files for such molecules where current cheminformatics software is inadequate or unable to in describing the true chemical structure.
A number of ligands that were defined as "metal bound to multiple waters" have been flagged in the dictionary with chem_comp.status = "OBS" (obsoleted) meaning they are no longer valid ligands, and should not be used in the future. While water coordinated metals can be strongly bound, these groups are not consistently used among all structures, and user analysis would benefit from standardizing on the single ion representation. Any entry contain such ligands will be split into metal and waters.
Leaving groups In order to accurately represent the polymerzation potential of entries in the chemical component dictionary, all atoms that can be lost from a ligand in the process of making a linkage will be marked with a special flag indicating these are 'leaving atoms'.
For example standard amino acids have the carbonyl oxygen atom OXT, and the N-terminal hydrogen HN2 are always marked as leaving atoms as these are lost in the process of creating a polypeptide chain. This, however, does not suggest that these atoms are always missing from the coordinates but rather these atoms are invariably missing in a polymeric state depending on the position and bonding state of the chemical entity.
Portions of ligands that are missing Ligands are defined as if all atoms were present in the experiment. If the ligand is only partially seen in the experiment (for example, a ring is missing in the density for a crystal structure), the ligand code that is used is for the fully defined ligand. If the ligand is new, the missing atoms are added to the definition of the ligand.
Modified amino acids and nucleotides If an amino acid or nucleotide is modified by a chemical group greater than 10 atoms, the residue will be split into two groups: the amino acid/nucleotide group and the modification. A link record will be generated between the amino acid/nucleotide group and the modification. For modified amino acids and nucleotides that were not split will follow standard atom nomenclature.
Nucleotide residue nomenclature The only difference between DNA and RNA is the presence of the O2' group on the ribose ring. The current nucleotides are handled the following residues for DNA: DA, DG, DC, DT and the following residues for RNA: A, G, C, U.
Use of UNX/UNL/UNK There are times when an amino acid residue, nucleotide, atom, or ligand is unidentified. These ligand codes should be used in the following cases:
UNX UNX is the code for one atom or ion, by itself, when author does not know the identity of that atom or ion. NOTE: The ligand name is UNX, but the atom name is UNK. The atom type is "X".
UNL UNL is the code for unknown ligand. This is for where author has added atoms to the coordinates to satisfy the electron density but the true ligand identity is not known. . For example, see PDB entry 3MHO.
UNK UNK is the code for unknown amino acid only. For example, a poly-ALA or poly-GLY chain would be processed as poly-UNK, if the author does not know how the coordinates align with the sequence and the residue numbering is arbitrary. The sequence would be poly UNK and the residues in coordinates would be listed as UNK. The sequence, if it is known, may be listed in the REMARK 999 and its mmCIF tokens. (If the authors do know the alignment of sequence and coordinates, the poly-ALA or poly-GLY residues should be changed to match the sequence). The atom names of UNK are N,CA,CB,CG,O,C, and the atom types are N,C,C,C,O,C. We are aware of issue regarding where atom passed CG but amino acid identity is not known, and the issues for the break in electron densi between UNK residues.
N is the code for unknown nucleotide where the base is not observed.
Conflicts between the author's identification of a ligand and the software and/or annotator identification of a ligand are brought to the attention of the author. In case of disagreement between the depositor and the wwPDB staff, the ligand name will be based on what is derived from the coordinates by specialized chemical naming software. If the stereochemistry cannot be determined by a program, the author's description of the stereochemistry will be used. For ambigious stereochemistry or bond length, A REMARK 600 and a flag will be added to the mmCIF file.
(see ATOM and HETATM)
Sometimes an atom, several atoms, or an entire side chain has more than one conformation. Each set of coordinates for the atom is assigned alternate position A and B, or if there are three alternate positions, A, B, and C, etc. The combined occupancies of the alternate positions should not exceed 1.00. Generally alternate conformation A should have the higher occupancy.
Alternate conformations for same atom, same residue, and same atom type with the same coordinates and same B value are not allowed.
Chemical group alternate conformations are handled in the same way as amino acids, unless the alternate conformations involve two different chemical groups.
For example, a zinc ion labeled with residue number 100 is in two alternate conformations. Generally, the higher occupancy will be labeled as alternate position A, the lower occupancy labeled as B. The occupancies of the two conformations should be less than or equal to 1.00.
HETATM 5255 CA A CA A1677 24.997 -8.766 8.266 0.70 4.26 CA HETATM 5256 CA B CA A1677 25.089 -8.689 8.940 0.30 7.58 CA
The author may state that two chemical groups are in alternate conformations of each other, but have different identities. For example, the author may state that the chemical group at a particular location is both zinc and copper. Unlike polymorphic residues, the ligands can not be assigned the same residue number; different residue numbers must be assigned. In this example, zinc would be residue 100, and copper residue 101. Zinc would be assigned alternate conformation A, and copper would be assigned alternate conformation B. The ligand with the higher occupancy is generally, but not always, assigned alternate conformation A. The occupancies of each ligand should be less than 1.00, and combined should be less than or equal to 1.00.
HETATM 2237 C1 AGLC A1145 24.054 15.397 10.953 0.50 23.40 C HETATM 2238 C2 AGLC A1145 24.511 14.510 12.107 0.50 24.19 C HETATM 2239 C3 AGLC A1145 24.469 13.035 11.755 0.50 23.62 C HETATM 2240 C4 AGLC A1145 23.159 12.668 11.058 0.50 22.89 C HETATM 2241 C5 AGLC A1145 22.775 13.655 9.964 0.50 22.60 C HETATM 2242 C6 AGLC A1145 21.379 13.410 9.391 0.50 23.15 C HETATM 2243 O1 AGLC A1145 24.965 15.362 9.884 0.50 25.48 O HETATM 2244 O2 AGLC A1145 25.808 14.839 12.545 0.50 27.92 O HETATM 2245 O3 AGLC A1145 24.599 12.347 12.979 0.50 23.35 O HETATM 2246 O4 AGLC A1145 23.265 11.376 10.487 0.50 20.21 O HETATM 2247 O5 AGLC A1145 22.790 14.942 10.534 0.50 22.57 O HETATM 2248 O6 AGLC A1145 21.350 13.819 8.039 0.50 21.51 O HETATM 2249 C1 BBGC A1146 22.835 15.552 11.694 0.50 28.27 C HETATM 2250 C2 BBGC A1146 23.484 14.650 12.745 0.50 27.74 C HETATM 2251 C3 BBGC A1146 23.616 13.199 12.308 0.50 26.77 C HETATM 2252 C4 BBGC A1146 22.545 12.755 11.314 0.50 25.44 C HETATM 2253 C5 BBGC A1146 22.324 13.751 10.180 0.50 25.87 C HETATM 2254 C6 BBGC A1146 21.228 13.236 9.247 0.50 26.00 C HETATM 2255 O1 BBGC A1146 23.216 16.914 11.644 0.50 29.46 O HETATM 2256 O2 BBGC A1146 24.789 15.102 13.053 0.50 28.71 O HETATM 2257 O3 BBGC A1146 23.586 12.419 13.484 0.50 27.44 O HETATM 2258 O4 BBGC A1146 22.977 11.537 10.738 0.50 22.74 O HETATM 2259 O5 BBGC A1146 21.961 15.012 10.707 0.50 27.65 O HETATM 2260 O6 BBGC A1146 20.690 14.271 8.459 0.50 24.91 O
Terminal oxygen, OXT, should be present on the final residue of a protein or peptide sequence. Some refinement programs use an OXT atom to denote the last atom of any polypeptide chain. Thus OXT atoms are added to
Inclusion of such OXT atoms in the middle of a polypeptide sequence does not describe the true contents of the crystal and is chemically incorrect.
The wwPDB corrects the OXT problem in one of the following 2 ways:
Authors are notified of how the annotation staff handled this case. If this atom is retained, the OXT will be changed to N of the following residue and the following remark is copied into REMARK 3, OTHER REFINEMENT REMARKS (_refine.details):
"Due to a feature in the refinement program, the structure was refined with OXT on one or more residues that are not the terminal residues of the sequence. In all these instances the OXT was changed to N of the next residue."
Any resulting C-N deviations will be removed from remark 500, because the atom was refined as oxygen, not nitrogen.
Missing residues (REMARK 465) and atoms (REMARK 470)
Missing residues (at the N- or C-termini or in flexible loops) and missing side chain atoms of the polymer component are listed in REMARK 465 if listed in _pdbx_unobs_or_zero_occ_residues with polymer_flag (Y) and occupancy_flag (1). Similarly, missing atoms are listed in REMARK 470 if listed in _pdbx_unobs_or_zero_occ_atoms with polymer_flag (Y) and occupancy_flag (1). Atoms which are leaving atoms such as polymer linkage (OXT in amino acids, OP3 in nucleic acids, O1 in saccharides) and hydrogens will not be listed as missing atoms in REMARK 470.
REMARK 465 REMARK 465 MISSING RESIDUES REMARK 465 THE FOLLOWING RESIDUES WERE NOT LOCATED IN THE REMARK 465 EXPERIMENT. (M=MODEL NUMBER; RES=RESIDUE NAME; C=CHAIN REMARK 465 IDENTIFIER; SSSEQ=SEQUENCE NUMBER; I=INSERTION CODE.) REMARK 465 REMARK 465 M RES C SSSEQI REMARK 465 MET A 1 REMARK 465 ALA A 280 REMARK 465 MET B 1 REMARK 465 ALA B 280
Zero occupancy residues (REMARK 475) and atoms (REMARK 480)
Some refinement programs allow inclusion of missing residues and side chain atoms in the coordinate files as atoms with occupancy 0.00. Since these atoms are usually ignored during refinement, their location and properties may not be reliable. Therefore, if such atoms are included in the deposited coordinate file, these atoms will still be retained in the file but also listed in separate new remarks: REMARK 475 (for zero occupancy residues) and REMARK 480 (for zero occupancy atoms). These remarks will also be available in the corresponding mmCIF file (_pdbx_unobs_or_zero_occ_residues or _pdbx_unons_or_zero_occ_atoms with polymer_flag (Y) and occupancy_flag (0))
Atoms which are leaving atoms such as polymer linkage (OXT in amino acids, OP3 in nucleic acids, O1 in saccharides) and hydrogens will not be listed as missing atoms in REMARK 480. The text in these remarks will be as follows:
For zero occupancy residues (pdbx_unobs_or_zero_occ_residues with polymer_flag (Y) and occupancy_flag (0)):
REMARK 475 REMARK 475 ZERO OCCUPANCY RESIDUES REMARK 475 THE FOLLOWING RESIDUES WERE MODELED WITH ZERO OCCUPANCY) REMARK 475 THE LOCATION AND PROPERTIES OF THESE RESIDUES MAY NOT REMARK 475 BE RELIABLE. (M=MODEL NUMBER; RES; REMARK 475 C=CHAIN IDENTIFIER; SSSEQ=SEQUENCE NUMBER; I=INSERTION CODE) REMARK 475 REMARK 475 M RES C SSSEQI REMARK 475 MET A 1 REMARK 475 ALA A 2
For zero occupancy atoms: (pdbx_unobs_or_zero_occ_atoms with polymer_flag (Y) and occupancy_flag (0))
REMARK 480 ZERO OCCUPANCY ATOM REMARK 480 THE FOLLOWING RESIDUES HAVE ATOMS MODELED WITH ZERO REMARK 480 OCCUPANCY. THE LOCATION AND PROPERTIES OF THESE ATOMS REMARK 480 MAY NOT BE RELIABLE. (M=MODEL NUMBER; REMARK 480 RES=RESIDUE NAME; C=CHAIN IDENTIFIER; SSEQ=SEQUENCE NUMBER; REMARK 480 I=INSERTION CODE): REMARK 480 M RES C SSEQI ATOMS REMARK 480 GLU A 42 CG CD OE1 OE2 REMARK 480 GLN A 44 CG CD OE1 NE2
Ligands or hetgroups that are not part of any polymer (protein or nucleic acid) in the structure may also have missing atoms or atoms with zero occupancy. In such instances the name of the hetgroup or ligand, chain ID and model number (if applicable) will be listed in REMARK 610 (for missing atoms) or REMARK 615 (for atoms with 0.00 occupancy). Corresponding mmCIF categories listing this information will also be included in the mmCIF format file. As the list of specific atoms missing from a hetgroup may be really large, they will not listed in the remarks described above. The list of all missing atoms from the ligands may be easily derived by comparing the coordinates of the hetgroup to its definition in the ligand dictionary.
For non-polymer component with missing atoms (REMARK 610, pdbx_unobs_or_zero_occ_atoms with polymer_flag (N) and occupancy_flag (0))
REMARK 610 REMARK 610 MISSING HETEROATOM REMARK 610 THE FOLLOWING RESIDUES HAVE MISSING ATOMS (M=MODEL NUMBER; REMARK 610 ALT= ALT CODE; RES=RESIDUE NAME; C=CHAIN IDENTIFIER; REMARK 610 SSEQ=SEQUENCE NUMBER; I=INSERTION CODE): REMARK 610 M RES C SSSEQI REMARK 610 GL5 A 42C REMARK 610 GL7 A 44
For non-polymer component with zero occupancy atoms (REMARK 615, pdbx_unobs_or_zero_occ_atoms with polymer_flag (N) and occupancy_flag (0))
REMARK 615 ZERO OCCUPANCY ATOM REMARK 615 THE FOLLOWING RESIDUES HAVE ATOMS MODELED WITH ZERO REMARK 615 OCCUPANCY. THE LOCATION AND PROPERTIES OF THESE ATOMS REMARK 615 MAY NOT BE RELIABLE. (M=MODEL NUMBER; ALT= ALT CODE REMARK 615 RES=RESIDUE NAME; C=CHAIN IDENTIFIER; SSEQ=SEQUENCE NUMBER; REMARK 615 I=INSERTION CODE): REMARK 615 M RES C SSSEQI REMARK 615 GL5 A 42 REMARK 615 GL7 A 44
(see ATOM/HETATM record)
The chain ID is a unique identifier for each macromolecular polymer and all chemical groups (including waters) associated with it.
All atoms in the coordinate section of the PDB file will be assigned a chain ID.
Each polymer is assigned a unique chain ID. Chain IDs for all bound moieties and waters are assigned based on their proximity (number of contacts) to the nearest polymer. For example, all waters and chemical groups around a particular polymer are assigned the chain ID of the polymer they surround. Sugars are considered as ligands even if they have two or more covalently linked sugars. Therefore the mono and poly sugars are also assigned the chain ID of the polymer they surround.
The wwPDB has established this rule to improve the usability and interpretation of the structural data. Assigning the same chain ID for all moieties associated with a polymer enables rapid and uniform identification of feature analysis.
All chemical groups and waters within 5 Ångstroms of any atom of a polymeric chain will be considered to be associated with that chain and will be assigned the same chain ID as that polymer. If a particular chemical group/water is equidistant from more than one chain, then the chain ID is randomly assigned to be that of any one of these polymers.
Waters further than 5 Ångstroms away from the polymer that can be moved by symmetry to within 5 Ångstroms, will then be automatically moved and the author will be notified. If there are objections, the waters will be moved back to their original positions.
Waters further than 5 Ångstroms away from any polymer, which cannot be brought closer to a polymer chain by application of symmetry, will be brought to the attention of the depositor. The waters will be listed in REMARK 525 with the distance to the nearest macromolecule listed. Authors will be given the opportunity to remove the waters or update the coordinates. Authors may choose to retain the distant waters in the entry.
REMARK 525 REMARK 525 SOLVENT REMARK 525 REMARK 525 THE SOLVENT MOLECULES HAVE CHAIN IDENTIFIERS THAT REMARK 525 INDICATE THE POLYMER CHAIN WITH WHICH THEY ARE MOST REMARK 525 CLOSELY ASSOCIATED. THE REMARK LISTS ALL THE SOLVENT REMARK 525 MOLECULES WHICH ARE MORE THAN 5A AWAY FROM THE REMARK 525 NEAREST POLYMER CHAIN ( M=MODEL NUMBER; REMARK 525 RES=RESIDUE NAME; C=CHAIN IDENTIFIER; SSEQ=SEQUENCE REMARK 525 NUMBER; I=INSERTION CODE): REMARK 525 REMARK 525 M RES CSSEQI REMARK 525 0 HOH A 561 DISTANCE = 5.07 ANGSTROMS REMARK 525 0 HOH A 791 DISTANCE = 5.08 ANGSTROMS
All residues and chemical groups in a file should be uniquely identified. Once the polymers and chemical groups associated with them are assigned chain IDs, the numbering of all residues, chemical groups and waters for each chain ID must be unique. Numbering of residues that were not modelled due to limited experimental data should also be considered here. The wwPDB encourages deposition of polymer chains with sequential residue numbering. For protein chains, the authors are encouraged to follow the UniProt residue numbering, wherever possible. The use of non-sequential residue numbering and insertion codes should be avoided as far as possible in order to make structures easily interpretable by the larger scientific community. If the coordinate residue numbers, as provided by the author, are unique and sequential within a particular chain ID, the residues will not be renumbered. If the author has already sorted ligands to polymer chains with which they are associated, these are not reassigned.
Up to 62 chains can be included in the PDB entry. Upper case letters and numbers (0-9) should be used first for chain IDs. Lower case letters should be used only after all upper letters and numbers have been used. Symbols should never be used for chain IDs.
During the annotation of structures the numbering and chain IDs of the chemical groups and waters associated with the polymeric chains may be changed in accordance with the wwPDB chain ID rules. The wwPDB strongly encourages depositors to use the wwPDB-assigned chain ID and residue numbers in any publication material. Deposition and processing of structures prior to preparation of the manuscript will ensure consistent usage of chain IDs and residue numbers in the manuscript and the PDB file. Validation and structure analysis reports generated during annotation may also be helpful in the manuscript preparation.
The HEADER (_struct_keywds.pdbx_keywords) is used to briefly describe the broad function of the macromolecules present in the PDB entry. A list of classifications is available.
The annotator typically assigns the function after reviewing the UniProt keywords and keywords provided by the author. The keywords should include the header and if the header is a complex (/ separated), the word complex will be added in the keywords. If the protein is an enzyme, the general class of enzyme is used. For example, the header is assigned as oxidoreductase if the E.C. number starts with 1.
See Appendices for the header list.
(see COMPND, SOURCE and KEYWDS records)
Protein molecule names and synonyms are copied from the corresponding UniProt entry and inserted in the MOLECULE and SYNONYM field of the COMPND section (_entity.pdbx_description and _entity_name_com.name). Exceptions are as follows:
Nucleic acid molecule names
For all nucleic acid sequences, a biological name should be used when available. The biological name is either provided by the author or it is obtained from a sequence database, such as "16S RIBOSOMAL RNA".
If the sequence is shorter than 24 nucleotides and no biological name is available, the molecule name is given as the short sequence:
For sequences greater than or equal to 24 nucleotides, and no biological name, then the name may be something such as: 50-mer.
Typically, "fragments" are not used for nucleic acids. For example, the name "Loop E from 5S RNA" is represented as molecule: "5S RNA" but the fragment is NOT represented as "fragment: Loop E".
A protein fragment is a sequence where one or more residues are missing compared to the corresponding sequence in the Uniprot entry.
If the PDB entry contains a fragment of the protein in the sequence records when compared to the UniProt entry, the fragment field will also record the residue numbers listed as per the numbering in the corresponding Uniprot entry. If additional annotation is available for the complete fragment, for example annotation about ligand binding domain, this will be added to the fragment field e.g. "ligand binding domain, UNP residues 100-200" where the residue numbers are the UniProt numbers. The numbering from Uniprot is universal, sequential and preferred.
Any further information available on the fragment or provided by the authors will be listed in OTHER_DETAILS field in the COMPND section (_entity.details).
The EC number is automatically extracted from the UNP entry. If the author disagrees with the UNP assignment of EC number, the wwPDB staff will contact the Uniprot staff and try to clarify the matters. In the case where the matter can not be resolved the EC assignment will be removed and added to the OTHER_DETAILS field in the COMPND section and will be indicated as "Author provided EC number is xxxx".
Mutations are indicated in the COMPND section as "COMPND MUTATION: YES". The exact mutation will be described in the mmCIF file using numbering from the Uniprot entry, i.e. Y20K. The SEQADV records will contain the annotation "ENGINEERED MUTATION" which indicates the mutation(s).
The NCBI_TAXID is added to the source section of the PDB file and mmCIF tokens are created for the tax ID.
The source organism is indicated by the taxonomy id as listed in the NCBI Taxonomy database. The official scientific name, ORGANISM_SCIENTIFIC, _entity_src_gen.pdbx_gene_src_scientific_name fields of the PDB entry, is obtained from UNP database which is based on the NCBI Taxonomy id. If a common name is listed in the NCBI taxonomy database, then the common name is mapped to the ORGANISM COMMON, _entity_src_gen.gene_src_common_name field, otherwise this will be left blank. An exception to this rule is listed below. If an author wishes to provide a synonym for the scientific name, the name is mapped to SOURCE, OTHER_DETAILS, _entity_src_gen.pdbx_description. If the NCBI Taxonomy database name is "Escherichia coli (strain K12)", then "Escherichia coli" would map to scientific name and "K12" would map to strain. Note that the scientific name of the source and host organisms will be included in mixed case to match with standard scientific literature. Plasmid and gene names will also be represented similarly.
The scientific names of chimeric proteins are listed as a comma separated list. If an expression system was used, the expression system scientific name will be taken from the NCBI Taxonomy database. Other information about the source and expression system is not mandatory and will be included in the file only if the author has provided it.
Tax ID for synthetic is 32630
Tax ID for undefined is 32644
Tax ID for hybrid is 37965
Phage display Information about phage display can be mapped to source, "OTHER_DETAILS".
Cell-free synthesis, in vitro transcription and in vitro translation Cell-free synthesis, in vitro transcription and in vitro translation will all be described as "cell-free synthesis". All will have genetically manipulated sources and will be listed as expression system: cell-free synthesis in the PDB file. Other information about the synthesis, such as "wheat germ" can be added to the OTHER_DETAILS.
Baculovirus If a baculovirus was used, it will be listed under vector type. If cell line is provided, it will be added to the entry.
Synthetic The term "synthetic" means "synthesized using non biological methods".
Keywords are provided by the author. If author does not provide meaningful keywords, they may added from the corresponding UNP entry. Some of the UNP terms such as signalling or 3-D structure are not included, and redundant terms between the author's keywords and UNP are removed. If the author does not agree with the UNP keywords and/or if there is a valid scientific argument for removing the UNP keywords from the PDB entry, then the UNP keywords will be removed. The HEADER should be included in the keywords list. In the case of a complex (as indicated by a / in the HEADER), the word "complex" will be added to the keywords.
The authors for a PDB entry can be the same as the author list for the primary citation, or a subset of citation authors. Alternatively, there may be more authors listed for the entry compared to the citation author. Generally, at least one of the authors for the entry should be included in the author list for the primary citation.
The authorship of the entry is at the discretion of the principal investigator (PI). If more than one PI is responsible for the entry, they will need to come to a mutual decision on the authorship.
See section 11 for author information for structural genomics structures
See wwPDB Annotation Policy document for entry authorship
Entry title should be descriptive and match to the content of the entry. PDB staff may modify the entry title during data processing or before entry release if the title is ambiguous or does not match to the content of the structure.
Authors are encouraged to deposit their structures in advance of publication. The primary citation is the paper that describes the structure in the PDB entry.
Conference Proceedings and Thesis can only be included as primary citation, but not in reference citation.
PubMed IDs are available for the primary citations of entries in the PDB, mmCIF and XML files. When available, DOI numbers are also included.
If the author indicates that the entry will never be published, the journal section is not included in the PDB entry. A value 'unpublished' will be added to mmCIF token, citation.journal_abbrev, will be added to the mmCIF file to flag situations when the author has indicated the entry will never be published
Journal author names that have the suffix "junior" will be represented as "Jr." and not as "junior".
All titles, names etc. are included in mixed case in the mmCIF format file to match with the literature. The legacy PDB format files will have titles in upper case.
Numbered remarks include annotation of refinement, validation & biological assembly
Use of REMARKs 40 and 42 is discontinued.
There will be new validation package developed by the software community through Validation Task Force. Therefore any other programs used for validation will not be listed in the PDB or mmCIF files.
NDB id has been removed from this remark. This remark now indicates one of the four process sites: RCSB, PDBe, PDBj or BNL with uniform date and site id code with the exception of BNL entries which will not have process date and site id code.
These REMARKs describe quaternary structure which may include software calculated quaternary assembly and/or author determined biological assembly, or the biologically relevant form of the molecule for which there is experimental evidence.
Quaternary structure indicates the way in which many protein chains associate with one another. For example, hemoglobin consists of four protein chains of two slightly different types, all attached to an iron atom. In general two or more polypeptide chains that behave in many ways as a single structural and functional entity are said to exhibit quaternary structure. The separate chains are not linked through covalent chemical bonds but by weak forces of association. The quaternary structure is the shape or structure that results from the interactions of more than one protein molecule, usually called protein subunits in this context, which function as part of the larger assembly or protein complex. In biochemistry, quaternary structure is the arrangement of multiple folded protein molecules in a multi-subunit complex.
Many proteins are actually assemblies of more than one polypeptide chain, which in the context of the larger assemblage are known as protein subunits. In addition to the tertiary structure of the subunits, multiple-subunit proteins possess a quaternary structure, which is the arrangement into which the subunits assemble. Enzymes composed of subunits with diverse functions are sometimes called holoenzymes, in which some parts may be known as regulatory subunits and the functional core is known as the catalytic subunit. Examples of proteins with quaternary structure include hemoglobin, DNA polymerase, and ion channels. Other assemblies referred to instead as multiprotein complexes also possess quaternary structure. Examples include nucleosomes and microtubules. Changes in quaternary structure can occur through conformational changes within individual subunits or through reorientation of the subunits relative to each other. It is through such changes, which underlie cooperativity and allostery in "multimeric" enzymes, that many proteins undergo regulation and perform their physiological function.
The above definition follows a classical approach to biochemistry, established at times when the distinction between a protein and a functional, proteinaceous unit was difficult to elucidate. More recently, people refer to protein-protein interaction when discussing quaternary structure of proteins and consider all assemblies of proteins as protein complexes.
We derive a likely oligomeric state of the structure based on the surface area of interactions and the association of macromolecules. Frequently, this derived structure and the biological assembly are the same. However, due to crystal packing forces, experimental evidence, or author opinion, the biological assembly and the PDB derived oligomeric structure may be different. For example, a macromolecule may be assigned a hexameric quarterary structure in the crystal but the biological assembly may be monomeric. It is recognized that quaternary structure programs such as PISA2 and PQS3 do not work with every case, such as antibodies, or any case where a biological process has a low association/dissociation property. The quaternary assembly is calculated and evaluated by the annotation staff, while the biological assembly is provided by the author.
Each chain must be used once at the identity in building the biological assembly and/or quaternary structure. If necessary, the wwPDB staff will move the coordinates of the chain(s) so that every chain is used at identity. There is the potential for a PDB entry to have more than one oligomeric state.
The wwPDB is adding information about quaternary structure to make it more convenient for the larger scientific community to understand the quaternary assembly of the protein in any given experiment which could be different from the assumed biological assembly.
Quaternary structure will be calculated automatically, based on what is in the coordinate file and known about the macromolecule. The matrices forming the quaternary structure will be reported as BIOMT in REMARK 350 and will be assigned by the wwPDB annotators. In instances where the author's description of the biological assembly disagrees with what the crystal structure appears to present, the biological assembly can be chosen by the depositor, and reported in the file. However, inclusion of this in the file is NOT MANDATORY and in most cases it is likely to be identical to the quaternary structure. The total surface area, buried surface area and free energy gain will be listed if two polymers have an interface. If more than two proteins have an interface, the remark will list the "average buried surface area".
Nomenclature: The number of subunits in an oligomeric complex are described using names that end in -mer (Greek for "part, subunit"). Formal Greco-Latinate names are generally used for the first ten types and can be used for up to twenty subunits, whereas higher order complexes are usually described by the number of subunits, followed by -meric.
In PDB REMARK 300 and REMARK 350, any polypeptide of length of 3 or more amino acids or 2 or more nucleotides is considered in the naming of a quaternary structure as monomeric or dimeric etc.:
|1 = monomeric||8 = octameric||15 = pentadecameric|
|2 = dimeric||9 = nonameric||16 = hexadecameric|
|3 = trimeric||10 = decameric||17 = heptadecameric|
|4 = tetrameric||11 = undecameric||18 = octadecameric|
|5 = pentameric||12 = dodecameric||19 = nonadecameric|
|6 = hexameric||13 = tridecameric||20 = eicosameric|
|7 = heptameric||14 = tetradecameric||21-meric etc.|
Please note that the multi-mer described in PDB remark 350 represents either homo or hetero multi-mer for that entry.
For examples, see Format Guide.
REMARK 400 may be used to annotate additional functional details of the compounds. This information is not mandatory and will not be verified by the wwPDB. For peptide inhibitor which is treated as polymer, _pdbx_entity_annotation will be used to map to REMARK 400.
The calculation of bond and angle deviations for protein entries will be based on the updated Engh & Huber amino acid target values4. For nucleic acids, the Parkinson et al., statistics are used for these calculations5. All bonds and angles that deviate more than 6 times from their standard target values will be flagged as a deviation. The PHI/PSI values are based on Kleywegt's calculations6.
CLOSE CONTACTS IN SAME ASYMMETRIC UNIT (_pdbx_validate_close_contact)
SYMMETRY RELATED CLOSE CONTACTS (_pdbx_validate_symm_contact)
BOND LENGTHS (_pdbx_validate_rmsd_bond)
BOND ANGLES (_pdbx_validate_rmsd_angle)
TORSION ANGLES (_pdbx_validate_torsion)
NON-CIS, NON-TRANS (_pdbx_validate_peptide_omega)
SIDE CHAIN PLANAR GROUPS (_pdbx_validate_planes)
MAIN CHAIN PLANARITY (protein only) (_pdbx_validate_main_chain_plane)
CHIRAL CENTERS (protein C-alpha only) (_pdbx_validate_chiral)
REMARK 620 contains any additional annotation specific to the heterogens present in the structure. By default, software adds coordination angles for any metal coordination and surrounding residues (if present) in REMARK 620. Any other information about the ligand may be entered in REMARK 600 (_pdbx_entry_details.nonpolymer_details).
For examples, see Format Guide.
Details of inhibitors/peptide inhibitors which are presented as a single molecule (het group) are provided in REMARK 630. By default, molecule type and inhibitor's name will be provided in this REMARK.
For details, see Format Guide.
We encourage authors to use the calculated helix records and not provide their own remarks. HELIX records which have been provided by the author will have a remark added to the header REMARK 650 to indicate the helix records have been author provided.
HELIX DETERMINATION METHOD: AUTHOR PROVIDED.
We encourage authors to use the calculated sheet records and not provide their own remarks. SHEET records which have been provided by the author will have a remark added to the header REMARK 700 to indicate the sheet records have been author provided.
SHEET DETERMINATION METHOD: AUTHOR PROVIDED.
REMARK 800 is used to annotate the binding environment of any non-polymeric heterogen. The site identifiers provided in these records are listed in the corresponding SITE records. This information may be provided by the depositors.
Authors may provide REMARK 900 (pdbx_database_related), related entries, to relate other entries to the current entry.
The following text is for a dedicated remark for cases where an author re-refines another author's data (REMARK 0).The remark will always appear in entries where the author refined someone else's data. The entry will be treated as an experimental structure.
REMARK 0 REMARK 0 THIS ENTRY yyyy REFLECTS AN ALTERNATIVE MODELING OF THE REMARK 0 ORIGINAL STRUCTURAL DATA (RxxxxSF or xxxx.MR or XXXX.CS) REMARK 0 DETERMINED BY AUTHORS OF THE PDB ENTRY xxxx: REMARK 0 AUTHOR INITIALS, AUTHOR LAST NAME REMARK 0 REMARK 0 ORIGINAL DATA REFERENCE 1 REMARK 0 PDB ID: XXXX REMARK 0 AUTH AUTHOR INITIALS, AUTHOR LAST NAME REMARK 0 TITL REMARK 0 REF JRNL_NAME VOLUMNE PG YEAR REMARK 0 REFN ISSN # REMARK 0 PMID XXXXXXX REMARK 0 DOI YYYYYYY
Note: In entries where REMARK 0 (pdbx_database_PDB_remark) is included as described above, REMARK 900 will also reflect the reuse of existing experimental data as shown in the example below:
For the entry 1ZET,
REMARK 0 THIS ENTRY 1ZET REFLECTS AN ALTERNATIVE MODELING OF THE REMARK 0 STRUCTURAL DATA IN R1T3NSF ORIGINAL DATA DETERMINED BY REMARK 0 AUTHOR: D.T.NAIR,R.E.JOHNSON,S.PRAKASH,L.PRAKASH,A.K.AGGARWAL REMARK 0 REMARK 0 ORIGINAL DATA REFERENCE 1 REMARK 0 PDB ID: 1T3N REMARK 0 AUTH D.T.NAIR,R.E.JOHNSON,S.PRAKASH,L.PRAKASH,A.K.AGGARWAL REMARK 0 TITL REPLICATION BY HUMAN DNA POLYMERASE-IOTA OCCURS BY HOOGSTEEN REMARK 0 TITL 2 BASE-PAIRING. REMARK 0 REF NATURE V. 430 377 2004 REMARK 0 REFN ISSN 0028-0836 REMARK 0 PMID 15254543 REMARK 0 DOI 10.1038/NATURE02692
REMARK 200 REMARK: AUTHOR USED THE SF DATA FROM ENTRY XXXX.(NOTE: rest of REMARK 200 is blank, since the re-refinement author did not collect the original data)
REMARK 900 RELATED ENTRIES REMARK 900 RELATED ID: R1T3NSF RELATED DB: PDB REMARK 900 THIS ENTRY 1ZET REFLECTS AN ALTERNATIVE MODELING OF X-RAY REMARK 900 DATA R1T3NSF
_audit.revision_id 1_0 _audit.creation_date 2005-07-19 _audit.update_record ;Initial release, author used sf file from pdb entry 1t3n, and added columns Fcalc, phases and FOM ;
The version of the PDB file and its correspondence to the file format guide will be included in all files processed and released by the wwPDB.
(SITE, LINK, SSBOND, HELIX, SHEET)
REVDAT records contain a history of the modifications made to an entry since its release.
The Record Format
COLUMNS DATA TYPE FIELD DEFINITION -------------------------------------------------------- 1 - 6 Record name "REVDAT" 8 - 10 Integer modNum Modification number. 11 - 12 Continuation continuation Allows concatenation of multiple records 14 - 22 Date modDate Date of modification (or release for new entries). This is not repeated on continuation lines. 24 - 28 String(5) modId Identifies this particular modification. It links to the archive used internally by PDB. This is not repeated on continuation lines 32 Integer modType An integer identifying the type of modification. In case of revisions with more than one possible modType, the highest value applicable will be assigned 40 - 45 LString(6) record Modification detail. 47 - 52 LString(6) record Modification detail. 54 - 59 LString(6) record Modification detail. 61 - 66 LString(6) record Modification detail.
Each time revisions are made to the entry, a modification number is assigned in increasing (by 1) numerical order. REVDAT records appear in descending order (most recent modification appears first). New entries have a REVDAT record with modNum equal to 1 and modType equal to 0. Allowed modTypes are:
0 Initial released entry.
1 Other modification.
Each revision may have more than one REVDAT record, and each revision has a separate continuation field.
Modification details are typically PDB record names such as SOURCE, TITLE, or COMPND. A special modification detail VERSN indicates that the file has undergone a change in version. The current version will be specified in REMARK 4.Verification/Validation/Value Authority Control
The modType must be one of the defined types, and the given record type must be valid. If modType is 0, the modId must match the entry's ID code in the HEADER record.Relationships to Other Record Types
In the case of a version revision, the current will be specified in REMARK 4.
1 2 3 4 5 6 7 1234567890123456789012345678901234567890123456789012345678901234567890 REVDAT 2 15-OCT-99 1ABC 1 REMARK REVDAT 1 09-JAN-89 1ABC 0
1 2 3 4 5 6 7 1234567890123456789012345678901234567890123456789012345678901234567890 REVDAT 2 11-MAR-08 2ABC 1 JRNL VERSN REVDAT 1 09-DEC-03 2ABC 0
The SITE records supply the identification of groups comprising important sites in the macromolecule. Historically SITE records have been only used to annotate the catalytic residues in an enzyme. In new PDB entries, SITE records will define any interacting residues, based on distance. An evidence code (_struct_site.pdbx_evidence_code) has been added to identify whether the SITE records is software calculated or author provided.
The SITE records are created to annotate the residues in the environment of all free floating ligands and hetgroups (not around modified residues). These records can be created automatically using a script that selects all protein, water and hetgroup atoms within a specified distance of any atom of a ligand. Site identifiers are 3-letter codes in a character range of AC1-ZZ9 if it is software determined. An example of SITE records is shown in PDB entry 1W3M.
Software generated SITE records
In Jan 2009 the wwPDB annotation software is using software 'getsite.f'. getsite is a Fortran program derived from the CCP4 program contact.f (http://www.ccp4.ac.uk/html/contact.html) where the original keyword input is automated to find all atom-atom contacts between every hetgroup in a PDB entry that is not in a polymer chain designated by SEQRES, and then list in the SITE record the unique set of residues in PDB format irrespective of symmetry while in mmcif format the unique set of residues plus symmetry are listed.
The distance restraints are limited to non H-atom contacts less than 3.7 and greater than 0.8 Ang. The 3.7 is rounded 3.66 Ang which is the limit for O--H....O van der Waals with
O--H bonded 1.08 H van der Waals 1.09 O van der Waals 1.52 3.69 Ang
Additional SITE records may also be included upon author request to highlight biologically important residues in the protein (like catalytic residues and metal binding site).
Note that the metal coordination interactions will appear both in LINK and SITE records. The difference between these 2 instances is that the LINK records may be built between 2 symmetry related molecules, while site records are usually listed within the same asymmetric unit.
REMARK 800 is mandatory if SITE records exist.
LINK records will be automatically generated using the standard software. There are various cutoff distances specified in this software for various kinds of LINK records. LINK records can include covalent bonding, metal coordination etc. LINK records may also be added by the author.
Standard software will automatically add REMARK 620 to the header of the file listing the angles of the link records between metal ions and surrounding residues following standard coordination geometry. The distances between the atoms and the symmetry operations will be added to the end of the LINK record in the PDB file. An example of SITE and LINK records are shown in PDB entry 1W3M.
SSBOND records are created for cysteine residues involved in disulfide bonds and do not include disulfide bonds between other residues or ligands. The distance between the atoms will be added to the end of the SSBOND line in the PDB file. The symmetry operation for the atom, including the identity, will also be indicated.
Helix and sheet records are automatically generated by Promotif software. Authors who wish to provide their own helix and sheet records may do so; a remark will be added to REMARK 650 and REMARK 700 of the PDB entry to indicate that the helix and/or sheet records were author provided.
wwPDB will not accept REMARK 3 template which uses CNS seq ids as selection range in tls/ncs groups.
Structural genomics (SG) entries are usually either X-ray or NMR structures deposited by the various structural genomics groups around the world. In the USA, these structures are deposited primarily by the several Protein Structure Initiative (PSI) groups. Europe, UK, Canada and Japan also have several structural genomics centers. The SG structures are processed in the same way as any other depositions to the PDB. There are just a few additional rules for annotation of these entries. These are listed below:
All structures determined by crystal X-ray diffraction where the structure is that of a non-virus capsid should contain the atomic coordinates for the whole crystallographic asymmetric unit (ASU). The ASU is defined as the smallest unit that can be rotated and translated to generate one unit cell using only the symmetry operators allowed by the crystallographic symmetry. The asymmetric unit may be one molecule or one subunit of a multimeric protein, but it can also be more than one.
Structure factor (sf) files should include information such as cell, space group, symmetry, wavelength and number of reflections of the entry. The date included in the header of the sf file will be the date of release, not the deposition date. If authors include multiple structure factor files (such as a set for refinement, multiple sets for phasing, etc.), the data will be archived either as one data_block with multiple categories or as multiple data blocks. For example, the reflections for refinement will be listed in the category '_refln' and the phasing data sets will be listed in the category '_phasing_set_refln.' Use of multiple data blocks within one sf file will be discontinued in the future. The different data sets can be distinguished by crystal and/or wavelength ID as appropriate. If different cell dimensions are present, this information will also be included in the file.
The values provided by the author will be retained in the mmCIF and PDB files.
Hydrogens in crystal structures will be retained regardless of resolution with the occupancy provided by the depositor (even if the structure is a low resolution structure and the occupancy is 1.00).
For crystal structures, the Matthews coefficient and solvent content will be automatically calculated using the following equations:
Matthews coefficient7 = volume of unit cell/(the molecular weight of macromolecule*Y*X)
Where Y is the number of asymmetric units in the unit cell (i.e. the number of symmetry operators in the space group). The unknown variable, X, is the number of molecules in the asymmetric unit.
Solvent content = 1 - 1.23/ (Matthews coefficient)
The molecular weight includes protein and nucleic acids based on sequences, no water and ligands. In cases of viral capsids and proteolytic fragments, the Matthews coefficient and solvent content should be author provided and will not be automatically calculated.
The number of reflections for refinement is the number of crystallographically unique measured reflections that satisfy both the resolution and the observation limits. The number of reflections for data collection is the total number of crystallographically unique measured reflections that are labelled as observed by the criterion on sigma(I) or on sigma(F). The number of reflections reported for refinement should be less than or equal to the number reported for data collection, even if Friedel pairs were used.
Structures based on twinned crystal diffraction data can be identified through use of the recent addition of twinning tokens to the mmCIF public exchange dictionary, pdbx_twin. The tokens can be used for identification of twinning operator, type, and fraction. The information contained in these tokens should be automatically mapped to REMARK 3, OTHER REFINEMENT REMARKS, in the PDB file header except REFMAC refinement.
The structure factor file for a twinned structure should include the detwinned data used for refinement first. If the authors have the twinned data, it may also be included in the file. If authors include both the twinned and detwinned data, the pdbx_reflns_twin tokens should also be included in the sf file.
If MAD data were collected, authors are encouraged to provide all data sets used in structure solution and refinement. The data set used for refinement should be listed first in the structure factor file. Authors are encouraged to provide the other (phasing) datasets. Wavelengths, source and other data collection information for all data sets should also be provided.
For examples see Format Guide.
Information about synchrotron sources and beamlines will be made consistent with the standard names used in the BioSync database (http://biosync.rcsb.org/).
Pseudoatoms (also known as Q atoms) submitted for NMR entries will be removed from the entry.
At least one domain of the NMR entry should be superimposed across all models. It is recognized that for multi-domain NMR structures, domain movements prevent the whole structure from being aligned through the length of the molecule. However, in order to highlight the relative movement of the domains, it makes sense to superpose at least one part of the structure across all the models deposited under a PDB accession code. This does not detract from the scientific value of the coordinate set or the experiment, but on the contrary, serves to highlight domain motion with respect to a fixed point. The superposition need not be arbitrary but may be done at the choosing of the depositor. This will allow the larger scientific community easy identification of the protein folds. It also facilitates identification of model variations across different parts of the structure.
Experimental Methods: There are two types of NMR experimental methods (EXPDTA, _exptl.method):
All models in a deposition should be superimposed in an appropriate author determined manner and only one superposition method should be used. Structures from different experiments, or different domains of a structure should not be superimposed and deposited as models of a deposition.
All models in an NMR ensemble must be homogeneous - each model must have the exact same atoms (hydrogen and heavy atoms), sequence and chemistry.
Deposition of minimized average structure must be accompanied with ensemble and must be homogeneous with ensemble.
MDLTYP record contains additional annotation pertinent to the coordinates presented in the entry. This record will indicate minimized average structure with model number of the minized average structure. The corresponding cif is _struct.pdbx_model_type_details.
MDLTYP MINIMIZED AVERAGE, MODEL X
For homogeneous NMR ensemble, the missing residues will be listed in model range.
REMARK 465 MISSING RESIDUES REMARK 465 THE FOLLOWING RESIDUES WERE NOT LOCATED IN THE REMARK 465 EXPERIMENT. (RES=RESIDUE NAME; C=CHAIN IDENTIFIER; REMARK 465 SSSEQ=SEQUENCE NUMBER; I=INSERTION CODE.) REMARK 465 MODELS 1-20 REMARK 465 RES C SSSEQI REMARK 465 MET A 1 REMARK 465 GLY A 2
For homogeneous NMR ensemble, the missing atoms will be listed in model range.
REMARK 470 MISSING ATOM REMARK 470 THE FOLLOWING RESIDUES HAVE MISSING ATOMS(RES=RESIDUE NAME; REMARK 470 C=CHAIN IDENTIFIER; SSEQ=SEQUENCE NUMBER; I=INSERTION CODE): REMARK 470 MODELS 1-25 REMARK 470 RES CSSEQI ATOMS REMARK 470 ILE A 20 CD1 REMARK 470 THR A 59 CG2
BMRB id: The BMRB id assigned to the entry referencing the peak data will be listed in REMARK 900, related entries.
There are 2 types of data files associated with cryo-EM structures - EM volumes (maps) and atomic coordinates. The atomic coordinate data used in fitting to EM maps are submitted to the PDB and processed by all centers of the wwPDB. The EM (and Electron Tomography) maps (volume data) are deposited, processed and archived only in the Electron Microscopy Database (EMDB) at EBI. The atomic coordinates and their corresponding EM maps will be cross-referenced in both the EMDB and PDB depositions where appropriate. The EMDB ID will be listed in REMARK 900, related entries. Further information should also be included in REMARK 999.
New templates and mmCIF tokens were created in consultation with the EM scientific community to archive relevant details of the EM experiment, data collection, processing and structure solution.
There are two types of experimental methods for EM:
This remark is mandatory for ELECTRON CRYSTALLOGRAPHY. Three new PDB records have been added: RECONSTRUCTION METHOD, SAMPLE TYPE and SPECIMEN TYPE. The DATE OF DATA COLLECTION will have uniform date, dd-mmm-yy.
This remark is mandatory for ELECTRON MICROSCOPY. Four new PDB records have been added: RECONSTRUCTION METHOD, SAMPLE TYPE, SPECIMEN TYPE and PARTICLE TYPE if SAMPLE TYPE is PARTICLE. The DATE OF EXPERIMENT will have uniform date, dd-mmm-yy.
For examples see Format Guide.
For the purposes of annotation, a complex assembly is defined as a structure for which the full biological assembly and/or crystallographic asymmetric unit is built by applying a set of non-crystallographic rotation/translation transformations to a set of deposited coordinates.
The icosahedral virus is the most common complex assembly deposited to the PDB. The author generally deposits the coordinates of the icosahedral asymmetric unit and supplies a set of 60 transformation matrices to be applied to the coordinates to produce the full biological assembly. We will continue to request these matrices from the authors. From the author-provided matrices and coordinates we will calculate a standard set of 60 ordered matrices as well as the transformation that moves the complex to the standard icosahedral frame (same frame used by ViperDB). The calculated matrices, the frame transformation, and the description of how they are to be applied to the coordinates to build the assembly will be stored in _pdbx_struct records.
For crystal structures we will also request a complete description of how to build the crystal asymmetric unit, and the description will be archived in _pdbx_struct records. If the coordinates are provided in the crystal frame, the non-crystallographic symmetry transformations will also be placed in struct_ncs_oper records and will appear in MTRIX records, enabling validation against the structure factor data.
Icosahedral point symmetry is just one type of symmetry that can be adopted by a complex assembly. Other point symmetries (see table below) or helical symmetries are possible. For all structures deposited as complex assemblies, we will archive symmetry information as appropriate in _pdbx_point_symmetry or _pdbx_helical_symmetry records.
|point symmetry||Schoenflies symbol||# equivalent positions|
From: International Tables for Crystallography, Volume A, 4th edition, Table 10.4.2, p. 782-783
The point symmetry will reflect in the last line of REMARK 300
REMARK 300 THE ASSEMBLY REPRESENTED IN THIS ENTRY HAS REGULAR REMARK 300 CYCLIC POINT SYMMETRY (SCHOENFLIES SYMBOL = C38).
C = CYCLIC
T = TETRAHEDRAL
D = DIHEDRAL
O = OCTAHEDRAL
I = ICOSAHEDRAL
The mapping cif is _pdbx_point_symmetry. For example,
The wwPDB staff recognize that there are different ways to handle variants in the DBREF section of the PDB format file. The best way to handle these instances is currently being discussed.
Some authors wish to include information regarding patents as the primary citation for depositions. The wwPDB staff is discussing this matter.
The wwPDB recognizes there is a problem regarding the way B factors are represented in CCP4 refined depositions where TLS refinement was used. The wwPDB staff are in contact with CCP4 regarding the resolution of this.
The wwPDB is working on developing a better data model for electron microscopy, especially to represent cases where the sequence of the model is different from the sequence used in the experiment.
The wwPDB recognizes that there are cases where the coordinates do not fit into the PDB file format because the limit on the maximum number of chain IDs and/or atoms is exceeded. The best way to address this issue is being discussed.
The wwPDB recognizes that there are different ways to represent entries containing alternate conformations. The best possible and scientifically accurate representations of these structures are being considered.
ANTIBIOTIC (peptidic, saccharide containing)
CIRCADIAN CLOCK PROTEIN
CYTOKINE (includes interleukins, interferons)
DE NOVO PROTEIN (ARTIFICIALLY DESIGNED, OFTEN SYNTHETIC)
DNA-RNA HYBRID (used when biological assembly contains mixed DNA and RNA residues or strands)
GENE REGULATION (use only when TRANSCRIPTION, REPLICATION, TRANSLATION are not applicable)
IMMUNE SYSTEM (includes antibodies, antigens)
MEMBRANE PROTEIN (no other function known)
PLANT PROTEIN (no other function known)
PROTEIN TRANSPORT (a protein involved in transporting other protein)
RIBOSOME (use only when TRANSLATION is not correct; do not specify /RNA even when present!)
SIGNALING PROTEIN (includes G-proteins)
STRUCTURAL GENOMICS (product of a probable gene)
TOXIN (not antibiotic, can use e.g. HYDROLASE INHIBITOR, TOXIN)
TRANSCRIPTION (DNA to RNA)
TRANSLATION (protein synthesis; prefer over RIBOSOME)
TRANSPORT PROTEIN (a protein that transports anything)
NUCLEAR PROTEIN (whether involved in binding RNA/DNA or some sort of nuclear processing is unclear)
VIRUS (for entire viral capsid)
VIRAL PROTEIN (viral protein not involved in the viral capsid)
VIRUS LIKE PARTICLE ((for cases where virus like particles are assembled , but are not the standard virus)
CYTOSOLIC PROTEIN (a protein whose function is not known well but is known to be found in the cytosol of a cell.)
DNA BINDING PROTEIN
RNA BINDING PROTEIN
LIPID BINDING PROTEIN
METAL BINDING PROTEIN (such as ZN, FE)
PEPTIDE BINDING PROTEIN
PROTEIN BINDING (implies binding of protein by protein)
SUGAR BINDING PROTEIN
xxx-BINDING PROTEIN (for any xxx ligand if none of above applies, such as HEME, AVIDIN, BIOTIN)
data_rxxxxsf # _audit.revision_id 1_0 _audit.creation_date ? _audit.update_record 'Initial release' # # _entry.id rxxxxsf # # _cell.entry_id rxxxxsf _cell.length_a 118.8600 _cell.length_b 155.0300 _cell.length_c 155.5400 _cell.angle_alpha 90.0000 _cell.angle_beta 90.0000 _cell.angle_gamma 90.0000 # _symmetry.entry_id rxxxxsf _symmetry.Int_Tables_number 20 _symmetry.space_group_name_H-M 'C 2 2 21' # loop_ _symmetry_equiv.id _symmetry_equiv.pos_as_xyz 1 'X, Y, Z' 2 '-X, -Y, Z+1/2' 3 'X, -Y, -Z' 4 '-X, Y, -Z+1/2' 5 'X+1/2, Y+1/2, Z' 6 '-X+1/2, -Y+1/2, Z+1/2' 7 'X+1/2, -Y+1/2, -Z' 8 '-X+1/2, Y+1/2, -Z+1/2' # _reflns.entry_id rxxxxsf _reflns.d_resolution_high 2.598 _reflns.d_resolution_low 47.140 _reflns.limit_h_max 45 _reflns.limit_h_min 0 _reflns.limit_k_max 59 _reflns.limit_k_min 0 _reflns.limit_l_max 59 _reflns.limit_l_min 0 _reflns.number_all 44453 _reflns.number_obs 44453 # _diffrn_radiation_wavelength.id 1 # _exptl_crystal.id 1 # _reflns_scale.group_code 1 # loop_ _refln.wavelength_id _refln.crystal_id _refln.scale_group_code _refln.index_h _refln.index_k _refln.index_l _refln.status _refln.F_meas_au _refln.F_meas_sigma_au _refln.F_calc _refln.phase_calc _refln.fom _refln.pdbx_HL_A_iso _refln.pdbx_HL_B_iso _refln.pdbx_HL_C_iso _refln.pdbx_HL_D_iso 1 1 1 0 0 6 o 299.0 6.4 1306.2 0.0 0.32 0.33 0 0.00 0.00 1 1 1 0 0 10 o 726.8 15.0 1756.7 180.0 0.99 2.86 0 0.00 0.00 ... #END OF REFLECTIONS
data_rxxxxsf # _audit.revision_id 1_0 _audit.creation_date ? _audit.update_record 'Initial release' # #This file contains two data sets. The first data set is used for refinement. #The second data set is used for phasing. # _entry.id rxxxxsf # # _cell.entry_id rxxxxsf _cell.length_a 108.7420 _cell.length_b 61.6790 _cell.length_c 71.6520 _cell.angle_alpha 90.0000 _cell.angle_beta 97.1510 _cell.angle_gamma 90.0000 # _symmetry.entry_id rxxxxsf _symmetry.Int_Tables_number 5 _symmetry.space_group_name_H-M 'C 1 2 1' # loop_ _symmetry_equiv.id _symmetry_equiv.pos_as_xyz 1 'X, Y, Z' 2 '-X, Y, -Z' 3 'X+1/2, Y+1/2, Z' 4 '-X+1/2, Y+1/2, -Z' # _reflns.entry_id rxxxxsf _reflns.d_resolution_high 2.148 _reflns.d_resolution_low 70.711 _reflns.limit_h_max 50 _reflns.limit_h_min -50 _reflns.limit_k_max 28 _reflns.limit_k_min 0 _reflns.limit_l_max 33 _reflns.limit_l_min 0 _reflns.number_all 25739 _reflns.number_obs 25471 # _diffrn_radiation_wavelength.id 1 # _exptl_crystal.id 1 # _reflns_scale.group_code 1 # loop_ _refln.wavelength_id _refln.crystal_id _refln.scale_group_code _refln.index_h _refln.index_k _refln.index_l _refln.status _refln.F_meas_au _refln.F_meas_sigma_au 1 1 1 -50 0 1 x ? ? 1 1 1 49 5 1 o 37.7 9.4 1 1 1 50 0 0 x ? ? ... #END data_rxxxxAsf # #This is second data set for phasing. # # # loop_ _cell.entry_id _cell.CCP4_wavelength_id _cell.CCP4_crystal_id _cell.length_a _cell.length_b _cell.length_c _cell.angle_alpha _cell.angle_beta _cell.angle_gamma PHASE 1 1 108.7420 61.6790 71.6520 90.0000 97.1510 90.0000 PHASE 2 1 108.7420 61.6790 71.6520 90.0000 97.1510 90.0000 PHASE 3 1 108.7420 61.6790 71.6520 90.0000 97.1510 90.0000 PHASE 4 1 108.7420 61.6790 71.6520 90.0000 97.1510 90.0000 # _symmetry.entry_id PHASE _symmetry.Int_Tables_number 5 _symmetry.space_group_name_H-M 'C 1 2 1' # loop_ _symmetry_equiv.id _symmetry_equiv.pos_as_xyz 1 'X, Y, Z' 2 '-X, Y, -Z' 3 'X+1/2, Y+1/2, Z' 4 '-X+1/2, Y+1/2, -Z' # loop_ _reflns.entry_id _reflns.CCP4_wavelength_id _reflns.CCP4_crystal_id _reflns.d_resolution_high _reflns.d_resolution_low _reflns.limit_h_max _reflns.limit_h_min _reflns.limit_k_max _reflns.limit_k_min _reflns.limit_l_max _reflns.limit_l_min _reflns.number_all _reflns.number_obs PHASE 1 1 2.148 71.095 50 -50 28 0 33 0 25739 11565 PHASE 2 1 2.148 71.095 50 -50 28 0 33 0 25739 11895 PHASE 3 1 2.148 71.095 50 -50 28 0 33 0 25739 12000 PHASE 4 1 2.148 71.095 50 -50 28 0 33 0 25739 13346 # loop_ _diffrn_radiation_wavelength.id _diffrn_radiation_wavelength.CCP4_crystal_id _diffrn_radiation_wavelength.wavelength 1 1 0.00000 2 1 0.00000 3 1 0.00000 4 1 0.00000 # loop_ _exptl_crystal.id 1 # _reflns_scale.group_code 1 # loop_ _refln.wavelength_id _refln.crystal_id _refln.scale_group_code _refln.index_h _refln.index_k _refln.index_l _refln.status _refln.F_meas_au _refln.F_meas_sigma_au _refln.pdbx_anom_difference _refln.pdbx_anom_difference_sigma 1 1 1 -50 0 1 x ? ? ? ? 1 1 1 -50 0 2 x ? ? ? ? ... #END OF REFLECTIONS
data_rxxxxsf _entry.id XXXX _database_2.database_code PDB _database_2.database_id XXXX _audit.creation_date 'YYYY-MM-DD' _cell.entry_id XXXX _cell.length_a 117.259 _cell.length_b 127.319 _cell.length_c 191.227 _cell.angle_alpha 90.00 _cell.angle_beta 90.29 _cell.angle_gamma 90.00 _cell.formula_units_Z 44 _symmetry.entry_id XXXX _symmetry.space_group_name_H-M 'P 1 21 1' loop_ _symmetry_equiv.id _symmetry_equiv.pos_as_xyz 1 'X,Y,Z' 2 '-X,Y+1/2,-Z' _atom_sites.entry_id XXXX _atom_sites.fract_transf_matrix 0.008528 _atom_sites.fract_transf_matrix 0.000000 _atom_sites.fract_transf_matrix 0.000043 _atom_sites.fract_transf_matrix 0.000000 _atom_sites.fract_transf_matrix 0.007854 _atom_sites.fract_transf_matrix 0.000000 _atom_sites.fract_transf_matrix 0.000000 _atom_sites.fract_transf_matrix 0.000000 _atom_sites.fract_transf_matrix 0.005229 _atom_sites.fract_transf_vector 0.00000 _atom_sites.fract_transf_vector 0.00000 _atom_sites.fract_transf_vector 0.00000 _reflns.entry_id XXXX _reflns_scale.group_code 1 _exptl_crystal.id 1 _diffrn_radiation_wavelength.id 1 _diffrn_radiation_wavelength.wavelength 1.5418 _reflns.d_resolution_high 2.700 _reflns.d_resolution_low 182.574 _reflns.number_all 149457 loop_ _refln.wavelength_id _refln.crystal_id _refln.scale_group_code _refln.index_h _refln.index_k _refln.index_l _refln.status _refln.F_meas_au _refln.F_meas_sigma_au ... #END OF REFLECTIONS