View schema JSON
The formal JSON schema defining the accepted value forms for the MSP-1 revisionDate term.
AI-friendly semantics for trusted information.
MSP-1 schema
Records the date or date-time associated with a specific revision or lifecycle event in an MSP-1 resource.
Machine-readable structure for declaring revision or lifecycle dates using either a lean string form or a structured object form.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://msp-1.org/schema/revisionDate/revisionDate.json",
"title": "MSP-1 Revision Date Schema",
"description": "Schema for recording the date or date-time associated with a specific revision or lifecycle event in an MSP-1 resource.",
"$comment": "MSP-1 v1.0.2 allows both the lean string form and the structured object form for revisionDate. String form is preferred inside ordinary revision objects. For object form, value and kind are required. The value field corresponds to the string form when revisionDate is emitted as a plain string. revisionDate informs temporal context but does not itself establish correctness, trust, verification, or ranking priority.",
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "A date or date-time string associated with a revision event, preferably using ISO 8601-compatible formatting."
},
{
"type": "object",
"properties": {
"value": {
"type": "string",
"minLength": 1,
"description": "The date or date-time associated with the revision or lifecycle event, typically in ISO 8601 format.",
"examples": [
"2025-12-11",
"2025-12-11T10:30:00Z"
]
},
"kind": {
"type": "string",
"enum": [
"created",
"updated",
"reviewed",
"published",
"deprecated",
"effectiveFrom",
"effectiveUntil",
"other"
],
"description": "The lifecycle role this date plays."
},
"precision": {
"type": "string",
"enum": [
"date",
"datetime"
],
"description": "Indicates whether the value is date-only or a full date-time."
},
"timezone": {
"type": "string",
"description": "Optional timezone identifier or offset if relevant."
},
"label": {
"type": "string",
"description": "Optional human-readable label for this revision date."
},
"notes": {
"type": "string",
"description": "Optional notes giving additional context about the revision date."
},
"lastUpdated": {
"type": "string",
"format": "date",
"description": "Date when this revisionDate record itself was last reviewed or updated."
}
},
"required": [
"value",
"kind"
],
"additionalProperties": false
}
]
}
The formal JSON schema defining the accepted value forms for the MSP-1 revisionDate term.
See the corresponding namespace term for conceptual usage, examples, and related MSP-1 terms.
MSP-1 v1.0.2 allows revisionDate as either a string or a structured object. The string form is preferred when revisionDate appears as a simple field inside a revision object.
For structured lifecycle-date metadata, value and kind are required. revisionDate provides temporal context, but it should not be treated as proof of correctness or trust by itself.