Repository navigation
CMMF 1.3.0-beta.1 — Document-level validation hints
Pre-releaseCMMF 1.3.0-beta.1 is an experimental prerelease implementing document-level validation hints from RFC #1.
Stable 1.2.0 remains canonical and Latest. This release comes from feature/validation-hints; it is not merged into main. The beta checkout defaults to 1.3.0-beta.1 throughout its specification, schema, documentation, checker, and examples.
Included
- Optional model-level
validationHints, with required stable IDs and descriptions and intended content severity. - Structured conditional and cross-field rules, recursive conditions, and presence-based actions.
- Separate named-dialect expression and prose-only forms. JsonLogic is illustrative; no expression evaluator is included.
- Explicit empty-value, missing-value, strict comparison, and operator/type rules.
- A required per-hint translation disposition (
mapped,degraded, orunmapped) with model/hint identity and reason. - A runnable declaration checker, examples, adoption guidance, and 108 regression tests.
Try it
Pin tag v1.3.0-beta.1 and declare specVersion: "1.3.0-beta.1" in the manifest. With Node.js 22 or later:
git clone --branch v1.3.0-beta.1 https://github.com/cmmf-project/content-model-master-format.git
cd content-model-master-format
npm ci
npm run check
node scripts/validate-models.mjs --manifest /path/to/manifest.yamlBoundaries and compatibility
Hints declare intent; they do not enforce content checks by themselves. The checker validates declarations and semantic references/types, without evaluating content or executing expressions. It is not a complete model-graph validator. Studio integration is separate work.
The existing 1.2 schema allows unknown model properties and may silently accept hints without checking them. Explicitly select the beta and its matching schema; unsupported versions must not fall back to 1.2. No stable 1.3.0 release is published.
Field-level validation and existing structural semantics remain unchanged. Historical normative documents are preserved. Further betas will receive new immutable versioned tags; stable promotion and merging require a later decision after testing.
Validation: 108 tests passed and all five example models validated, including from a fresh committed source archive.