Definition

msp:revisionDate provides temporal context for a revision or lifecycle event. It identifies when a resource was created, updated, reviewed, published, deprecated, or otherwise changed when that context is declared.

The revisionDate term should not be confused with msp:revisionVersion or msp:revisionNotes. revisionDate records when the revision event occurred; revisionVersion labels the associated version; revisionNotes explain what changed.

Usage

The lean string form is preferred for ordinary revision metadata.

{
  "msp:revisionDate": "2025-01-10"
}

A date-time string may be used when time-level precision is useful.

{
  "msp:revisionDate": "2025-12-11T14:32:00Z"
}

The structured form may be used when lifecycle-date metadata requires kind, precision, timezone, or labeling.

{
  "msp:revisionDate": {
    "value": "2025-12-11T14:32:00Z",
    "kind": "updated",
    "precision": "datetime",
    "timezone": "UTC"
  }
}

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

{
  "msp:revision": {
    "id": "rev-2025-03",
    "revisionDate": "2025-12-10",
    "revisionNotes": "Corrected terminology and added citation.",
    "revisionVersion": "1.0.3"
  }
}

Guidance

• revisionDate values should use ISO 8601-compatible date or date-time formatting.
• A revisionDate should remain stable once recorded unless the original record was incorrect.
• revisionDate should support coherent chronological ordering of revision events.
• Date-only values are acceptable when exact time is unnecessary or unknown.
• revisionDate should inform freshness and temporal context 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.1 declarations. Older examples that place precision beside a string revisionDate may receive advisory compatibility handling, but new structured date metadata should place precision inside the revisionDate object.

Related Terms