Matrix metalloproteinase-25 has a functional role in mouse secondary palate development and is a downstream target of TGF-β3
Bibliographic record
Abstract
BACKGROUND: Development of the secondary palate (SP) is a complex event and abnormalities during SP development can lead to cleft palate, one of the most common birth disorders. Matrix metalloproteinases (MMPs) are required for proper SP development, although a functional role for any one MMP in SP development remains unknown. MMP-25 may have a functional role in SP formation as genetic scans of the DNA of human cleft palate patients indicate a common mutation at a region upstream of the MMP-25 gene. We report on the gene expression profile of MMP-25 in the developing mouse SP and identify its functional role in mouse SP development. RESULTS: MMP-25 mRNA and protein are found at all SP developmental stages in mice, with the highest expression at embryonic day (E) 13.5. Immunohistochemistry and in situ hybridization localize MMP-25 protein and mRNA, respectively, to the apical palate shelf epithelial cells and apical mesenchyme. MMP-25 knockdown with siRNA in palatal cultures results in a significant decrease in palate shelf fusion and persistence of the medial edge epithelium. MMP-25 mRNA and protein levels significantly decrease when cultured palate shelves are incubated in growth medium with 5 μg/mL of a TGF-β3-neutralizing antibody. CONCLUSIONS: Our findings indicate: (i) MMP-25 gene expression is highest at E12.5 and E13.5, which corresponds with increasing palate shelf growth downward alongside the tongue; (ii) MMP-25 protein and mRNA expression predominantly localize in the apical epithelium of the palate shelves, but are also found in apical areas of the mesenchyme; (iii) knockdown of MMP-25 mRNA expression impairs palate shelf fusion and results in significant medial edge epithelium remaining in contacted areas; and (iv) bio-neutralization of TGF-β3 significantly decreases MMP-25 gene expression. These data suggest a functional role for MMP-25 in mouse SP development and are the first to identify a role for a single MMP in mouse SP development.
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.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 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.001 |
| Insufficient payload (model declined to judge) | 0.004 | 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".