MSP-1 Namespace Term

msp:revision

Describes a discrete change event in the lifecycle of an MSP-1 resource, providing a stable anchor for revision identity, date, version association, and explanatory notes.

IRI: https://msp-1.org/ns/revision

Definition

msp:revision declares a documented change event or update point for a resource. Each revision should provide a stable identity anchor and may include date, notes, version association, reviewer context, provenance context, or related change references.

Revision metadata helps describe change history and temporal context. It should not be confused with msp:version or msp:provenance. revision identifies a documented change event; revisionVersion labels the version associated with that event; protocol.version identifies the MSP-1 protocol version being implemented.

Usage

Minimal revision metadata may declare only a stable revision identifier.

{
  "msp:revision": {
    "id": "rev-2026-06-24"
  }
}

Preferred MSP-1 v1.0.2 revision metadata uses explicit revision subterms.

{
  "msp:revision": {
    "id": "rev-2026-06-24",
    "revisionDate": "2026-06-24",
    "revisionNotes": "Clarified namespace definitions and updated examples.",
    "revisionVersion": "1.0.1"
  }
}

Reviewer context may be included when a revision was reviewed or validated by a declared reviewer.

{
  "msp:revision": {
    "id": "rev-2026-06-24",
    "revisionDate": "2026-06-24",
    "revisionNotes": "Updated page metadata for v1.0.2.",
    "revisionVersion": "1.0.1",
    "reviewer": {
      "id": "editorial-team"
    }
  }
}

Guidance

  • Each revision should represent one meaningful change event or documented update point.
  • Revision identifiers should remain stable after declaration.
  • Revision dates should support coherent chronological interpretation.
  • Revision notes should provide enough context to understand the nature of a meaningful change.
  • Revision metadata should inform freshness and change history but should not be treated as proof of correctness or trust by itself.

Deprecated compatibility note

The deprecated compliance term should not be emitted in new MSP-1 v1.0.2 declarations. Older revision structures using generic fields such as version, date, summary, or notes may receive compatibility handling, but new output should prefer revisionVersion, revisionDate, and revisionNotes.

Related Terms