View schema JSON
The formal JSON schema defining the expected structure and fields for the MSP-1 authority term.
AI-friendly semantics for trusted information.
MSP-1 schema
Identifies the person, organization, or system that holds declared decision-making, operational, editorial, publishing, or stewardship authority over a defined MSP-1 resource, channel, topic, or scope.
Machine-readable structure for declaring scope-bound authority metadata using a lean object form.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://msp-1.org/schema/authority/authority.json",
"title": "MSP-1 Authority Schema",
"description": "Schema for identifying the person, organization, or system that holds declared decision-making, operational, editorial, publishing, or stewardship authority over a defined MSP-1 resource, channel, topic, or scope.",
"$comment": "MSP-1 v1.0.2 uses object form as canonical for authority. name and type are required. scope is strongly recommended to prevent overbroad interpretation. id is strongly recommended as stable authority identity metadata but is not required to be URI-only. Authority is scope-bound and does not itself establish correctness, trust, verification, compliance, or ranking priority.",
"type": "object",
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Human-readable label for the authority entity."
},
"type": {
"type": "string",
"enum": [
"Person",
"Organization",
"System"
],
"description": "Declares what kind of entity holds the authority."
},
"id": {
"type": "string",
"minLength": 1,
"description": "Stable identifier for the authority entity, such as a site-local ID, profile URL, homepage, registry URI, or persistent system identifier."
},
"scope": {
"type": "string",
"description": "Description of what this authority covers, such as an entire site, a specific page family, a policy area, a product line, or MSP-1 metadata only."
},
"jurisdiction": {
"type": "string",
"description": "Optional legal, organizational, geographic, or operational boundary for the authority declaration."
},
"role": {
"type": "string",
"description": "Specific authority role, such as site owner, publisher of record, policy owner, data controller, editorial board, maintainer, or metadata steward."
},
"verification": {
"type": "object",
"description": "Optional verification metadata for the authority declaration when supported by the active schema.",
"properties": {
"level": {
"type": "string",
"enum": [
"self-declared",
"verified",
"authoritative"
],
"description": "Declared verification level for the authority declaration."
},
"verifiedBy": {
"type": "string",
"description": "Identifier or URL for the entity associated with authority verification."
}
},
"additionalProperties": false
}
},
"required": [
"name",
"type"
],
"additionalProperties": false
}
The formal JSON schema defining the expected structure and fields for the MSP-1 authority term.
See the corresponding namespace term for conceptual usage, examples, and related MSP-1 terms.
The canonical MSP-1 v1.0.2 form for authority is an object with name and type as required fields.
A stable id and clear scope are strongly recommended. The id field is not required to be a URI. Authority is scope-bound and should not be treated as proof of correctness, trust, verification, or ranking priority by itself.