Repository navigation
Releases
CMMF 1.2.1 — Mixed-case model and field IDs
CMMF 1.2.1 fixes the restriction that rejected capital letters in model and field IDs. IDs such as pageTitle and ArticlePage are now valid.
- IDs accept ASCII letters (
A-Z,a-z), digits, underscores, and hyphens. - Identity is case-sensitive, and references preserve the original casing.
- Translators must log target-required renaming, update references consistently, and detect collisions.
- Existing lowercase IDs remain valid. To adopt the patch, declare
specVersion: "1.2.1"and use the matching schema. - Automated regression and example validation checks are included; all 24 checks pass.
The historical 1.2.0 specification and existing release tags remain unchanged. The casing fix is also incorporated into the 1.3 beta development branch; the published v1.3.0-beta.1 tag remains immutable.
Full changes: v1.2.0...v1.2.1
CMMF 1.3.0-beta.1 — Document-level validation hints
CMMF 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.
v1.2.0
CMMF 1.2.0
CMMF 1.2.0 simplifies repeatability across the format by standardising on field-level list as the canonical way to express plural fields. This replaces the previous split where most field types used list: true but references used relation.cardinality.
Highlights
- Standardised repeatability on list for all field types, including reference
- Added versioned 1.2.0 specification and translation contract documents
- Updated examples and reference docs to show repeatable references with list: true
- Updated the JSON Schema to describe relation.cardinality as a legacy compatibility alias
- Added migration guidance for translators and validators
Why This Changed
Before 1.2.0, CMMF used two different mechanisms for the same modelling question: whether a field is singular or repeatable. That added avoidable complexity for model authors, translators, validators, and tooling.
In 1.2.0, repeatability is treated as a general field concern. Relationship semantics remain in relation, while list now consistently answers whether a field holds one item or many.
Migration Notes
- Replace relation.cardinality: many with list: true on reference fields
- Omit both list and relation.cardinality for singular references
- Legacy relation.cardinality remains accepted for compatibility during migration
- Treat conflicting list and relation.cardinality values as invalid
Compatibility
CMMF 1.2.0 is designed to ease migration rather than force an immediate break. Existing translators and validators can continue accepting legacy relation.cardinality on reference fields, but new models and examples should prefer list.
Example
Before:
type: reference
targets: [article]
relation:
cardinality: many
ownership: linked
After:
type: reference
list: true
targets: [article]
relation:
ownership: linked
Included In This Release
- New 1.2.0 spec draft
- New 1.2.0 translation contract draft
- Updated docs and examples
- Updated schema validation rules for the new convention
Full Changelog: https://github.com/cmmf-project/content-model-master-format/commits/v1.2.0