Display Settings:

Format

Send to:

Choose Destination
See comment in PubMed Commons below
J Proteomics. 2012 Jun 18;75(11):3138-44. doi: 10.1016/j.jprot.2011.12.013. Epub 2011 Dec 20.

Carbohydrate transporting membrane proteins of the rumen bacterium, Butyrivibrio proteoclasticus.

Author information

  • 1AgResearch Ltd, Grasslands Research Centre, Tennent Drive, Palmerston North, New Zealand. judy.bond@vuw.ac.nz

Abstract

The research was aimed at finding which membrane proteins of the rumen bacterium Butyrivibrio proteoclasticus are involved in the uptake of carbohydrates resulting from extracellular enzymatic degradation of hemicellulose and fructan. The proteomic analysis of cells grown with fructose or xylan as the sole substrate identified 13 membrane proteins predicted to function as carbohydrate transporters. One protein detected was the membrane component of a fructose-specific phosphoenolpyruvate:sugar phosphotransferase system believed to be involved in the fructose uptake following extracellular fructan breakdown. The other 12 proteins were all ABC transport system substrate-binding proteins, nine of which belong to functional category COG1653 that includes proteins predicted to transport oligosaccharides. Four of the SBPs were significantly upregulated in xylan grown cells, and three of these were found in polysaccharide utilisation loci where they are clustered with other genes involved in hemicellulose breakdown and metabolism. It is possible that the carbon source available regulates a wider network of genes. The information on the mechanisms used by rumen bacteria to take up carbohydrates from their environment may improve our understanding of the ruminant digestion and facilitate strategies for improved pasture and stored feed utilisation.

Crown Copyright © 2012. Published by Elsevier B.V. All rights reserved.

PMID:
22200676
[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Icon for Elsevier Science
    Loading ...
    Write to the Help Desk