Display Settings:

Format

Send to:

Choose Destination
See comment in PubMed Commons below
Biochem J. 2005 Aug 1;389(Pt 3):685-94.

Resolving the energy paradox of chaperone/usher-mediated fibre assembly.

Author information

  • 1Department of Molecular Biology, Uppsala Biomedical Center, Swedish University of Agricultural Sciences, Box 590, SE-753 24 Uppsala, Sweden. anton.zavialov@molbio.slu.se

Abstract

Periplasmic chaperone/usher machineries are used for assembly of filamentous adhesion organelles of Gram-negative pathogens in a process that has been suggested to be driven by folding energy. Structures of mutant chaperone-subunit complexes revealed a final folding transition (condensation of the subunit hydrophobic core) on the release of organelle subunit from the chaperone-subunit pre-assembly complex and incorporation into the final fibre structure. However, in view of the large interface between chaperone and subunit in the pre-assembly complex and the reported stability of this complex, it is difficult to understand how final folding could release sufficient energy to drive assembly. In the present paper, we show the X-ray structure for a native chaperone-fibre complex that, together with thermodynamic data, shows that the final folding step is indeed an essential component of the assembly process. We show that completion of the hydrophobic core and incorporation into the fibre results in an exceptionally stable module, whereas the chaperone-subunit pre-assembly complex is greatly destabilized by the high-energy conformation of the bound subunit. This difference in stabilities creates a free energy potential that drives fibre formation.

PMID:
15799718
[PubMed - indexed for MEDLINE]
PMCID:
PMC1180718
Free PMC Article

Images from this publication.See all images (6)Free text

Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for Portland Press Icon for PubMed Central
    Loading ...
    Write to the Help Desk