MSP-1 schema

reviewer

Identifies a person, organization, or system that reviewed, audited, evaluated, or approved an MSP-1 resource, metadata declaration, revision, or implementation component.

MSP-1 v1.0.2 • Last updated 2026-08-29

reviewer schema definition

Machine-readable structure for declaring review responsibility metadata using a lean object form.

reviewer schema JSON


{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://msp-1.org/schema/reviewer/reviewer.json",
  "title": "MSP-1 Reviewer Schema",
  "description": "Schema for identifying a person, organization, or system that reviewed, audited, evaluated, or approved an MSP-1 resource, metadata declaration, revision, or implementation component.",
  "$comment": "MSP-1 v1.0.2 uses object form as canonical for reviewer. name and type are required. id is strongly recommended as stable reviewer identity metadata but is not required to be URI-only. @type is supported as a JSON-LD compatibility field; type remains the preferred MSP-1 field.",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "description": "Name or identifier of the reviewer, whether a person, organization, or automated system."
    },
    "type": {
      "type": "string",
      "enum": [
        "Person",
        "Organization",
        "System"
      ],
      "description": "Classification of the reviewer entity."
    },
    "@type": {
      "type": "string",
      "enum": [
        "Person",
        "Organization",
        "System"
      ],
      "description": "JSON-LD compatibility field. The preferred canonical MSP-1 field is type."
    },
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Stable identifier for the reviewer, such as a site-local ID, profile URL, system identifier, or other persistent reference."
    },
    "role": {
      "type": "string",
      "description": "Specific reviewing role, such as editor, auditor, subject-expert, metadata reviewer, or AI validator."
    },
    "scope": {
      "type": "string",
      "description": "Description of what was reviewed, such as entire site, metadata only, technical accuracy, editorial clarity, or revision-specific review."
    },
    "reviewDate": {
      "type": "string",
      "format": "date",
      "description": "Date when the review occurred."
    },
    "verification": {
      "type": "object",
      "description": "Optional verification metadata regarding the reviewer or review event when supported by the active schema.",
      "properties": {
        "level": {
          "type": "string",
          "enum": [
            "self-declared",
            "verified",
            "authoritative"
          ],
          "description": "Declared verification level for reviewer or review-event metadata."
        },
        "verifiedBy": {
          "type": "string",
          "description": "Identifier or URL for the entity associated with reviewer or review-event verification."
        }
      },
      "additionalProperties": false
    },
    "notes": {
      "type": "string",
      "description": "Optional contextual notes about the review or reviewer."
    }
  },
  "required": [
    "name",
    "type"
  ],
  "additionalProperties": false
}


 

Schema notes

The canonical MSP-1 v1.0.2 form for reviewer is an object with name and type as required fields.

A stable id, review scope, and reviewDate are recommended when available, but id is not required to be a URI. The JSON-LD @type field may appear in compatibility contexts, while type remains the preferred MSP-1 field.