Definition

msp:revisionVersion associates a revision event with a version label, release state, compatibility context, or structured versioning sequence.

The revisionVersion term should not be confused with protocol.version or the broader msp:version term. revisionVersion labels the version associated with a revision event; protocol.version identifies the MSP-1 protocol version being implemented; version may identify a broader site, page, section, resource, or implementation version.

Usage

The lean string form is preferred for ordinary revision metadata.

{
  "msp:revisionVersion": "1.0.2"
}

The structured form may be used when semantic-version components or compatibility metadata are needed.

{
  "msp:revisionVersion": {
    "major": 1,
    "minor": 0,
    "patch": 1,
    "string": "1.0.2",
    "label": "stable"
  }
}

Inside a revision object, the lean string form keeps the revision declaration compact.

{
  "msp:revision": {
    "id": "rev-2026-06-24",
    "revisionDate": "2026-06-24",
    "revisionNotes": "Clarified lifecycle term handling for v1.0.2 harmonization.",
    "revisionVersion": "1.0.1"
  }
}

Guidance

• revisionVersion should remain stable after it is associated with a revision unless the original record was incorrect.
• revisionVersion should be associated with a specific revision or revision context.
• Semantic versioning is preferred where applicable, but implementation-defined labels may be used when semantic versioning is not appropriate.
• revisionVersion should not be confused with protocol.version.
• revisionVersion should inform lifecycle and compatibility context but should not be treated as proof of correctness, trust, or freshness by itself.

Deprecated compatibility note

The deprecated compliance term should not be emitted in new MSP-1 v1.0.2 declarations. Older examples that use channel may receive advisory compatibility handling, but new structured revisionVersion metadata should prefer label.

Related Terms