View schema JSON
The formal JSON schema defining the expected structure and fields for the MSP-1 provenance term.
AI-friendly semantics for trusted information.
MSP-1 schema
Documents the origin, lineage, creation method, source relationship, and contributor context of an MSP-1 resource.
Machine-readable structure for declaring origin, lineage, creation method, source relationship, and contributor context using a lean object form.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://msp-1.org/schema/provenance/provenance.json",
"title": "MSP-1 Provenance Schema",
"description": "Schema for documenting the origin, lineage, creation method, source relationship, and contributor context of an MSP-1 resource.",
"$comment": "MSP-1 v1.0.2 uses object form as canonical for provenance. type is required and may be either a single allowed provenance category or an array of unique allowed provenance categories. Provenance informs interpretation but does not itself establish authority, verification, correctness, trust, or ranking value.",
"type": "object",
"properties": {
"type": {
"oneOf": [
{
"type": "string",
"enum": [
"original",
"derived",
"aggregated",
"ai-assisted",
"ai-generated"
]
},
{
"type": "array",
"items": {
"type": "string",
"enum": [
"original",
"derived",
"aggregated",
"ai-assisted",
"ai-generated"
]
},
"minItems": 1,
"uniqueItems": true
}
],
"description": "Declares the provenance category or categories for the resource."
},
"source": {
"type": "string",
"format": "uri-reference",
"description": "Original source URL or identifier if the resource derives from an external origin."
},
"contributors": {
"type": "array",
"description": "Entities that materially contributed to the creation, development, transformation, or review context of the resource.",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Stable identifier for the contributor."
},
"name": {
"type": "string",
"description": "Human-readable contributor name."
},
"role": {
"type": "string",
"description": "Contributor role or function."
}
},
"additionalProperties": false
}
},
"confidence": {
"type": "string",
"enum": [
"low",
"medium",
"high"
],
"description": "Self-assessed confidence in the accuracy of the provenance declaration."
},
"timestamp": {
"type": "string",
"format": "date-time",
"description": "Date and time when the provenance declaration was created or updated."
},
"notes": {
"type": "string",
"description": "Free-form provenance notes, caveats, or clarifications."
}
},
"required": [
"type"
],
"additionalProperties": false
}
The formal JSON schema defining the expected structure and fields for the MSP-1 provenance term.
See the corresponding namespace term for conceptual usage, examples, and related MSP-1 terms.
The canonical MSP-1 v1.0.2 form for provenance is an object with type as the required field.
The type field may be a single string or an array of unique provenance categories. Provenance informs interpretation, but does not by itself establish authority, verification, correctness, trust, or ranking value.