Localization of the Cl<sup>-</sup>/HCO<sub>3</sub><sup>-</sup> Anion Exchanger Binding Site to the Amino-Terminal Region of Carbonic Anhydrase II
Bibliographic record
Abstract
Human carbonic anhydrase II (CAII) possesses a binding site for an acidic motif (D887ADD) within the carboxyl-terminal region (Ct) of the human erythrocyte chloride/bicarbonate anion exchanger, AE1. In this study, the amino acid sequence comprising this AE1 binding site was localized to the first 17 residues of CAII, which form a basic patch on the surface of the protein. Truncation of the amino terminal of CAII by five residues resulted in a 3-fold reduction in the apparent affinity of the interaction with a GST fusion protein of the Ct of AE1 (GST-Ct) measured by a sensitive microtiter plate binding assay. Further amino-terminal truncation of CAII by 17 or 24 residues caused a loss of binding. The homologous isoform CAI does not bind AE1, despite having 60% sequence identity to CAII. One major difference between the two CA isoforms, within the amino-terminal region, is a high content of histidine residues in CAII (His3, -4, -10, -15, -17) not found in CAI. Mutation of pairs of these histidines (and one lysine) in CAII to the analogous residues in CAI (H3P/H4D or K9D/H10K or H15Q/H17S), or combinations of these various double mutants, did not greatly affect binding between GST-Ct and the mutant CAII. However, when all six of the targeted CAII residues were mutated to the corresponding sequence in CAI, binding of GST-Ct was lost. These results indicate that the AE1 binding site is located within the first 17 residues of CAII, and that the interaction is mediated by electrostatic interactions involving histidine and/or lysine residues. Further specificity for the interaction of AE1 and CAII is provided by a conserved leucine residue (L886) in AE1 that, when mutated to alanine, resulted in loss of GST-Ct binding to immobilized CAII. The binding of the basic amino-terminal region of CAII to an acidic Ct in AE1 provides a structural basis for linking bicarbonate transport across the cell membrane to intracellular bicarbonate metabolism.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".