Definition

msp:role declares the function an entity performs in context. It may describe participation in authorship, review, contribution, maintenance, publication, governance, technical operation, or related responsibility.

The role term should not be confused with msp:type. role describes what function an entity performs; type classifies what kind of thing the entity or resource is.

Usage

The lean string form is preferred when role appears as an embedded field.

{
  "msp:role": "maintainer"
}

The structured form may be used when a standalone role declaration needs additional context.

{
  "msp:role": {
    "name": "ai-partner",
    "category": "technical",
    "entityType": "System",
    "scope": "content structure and analysis",
    "description": "AI system contributing structural, analytical, or generative support."
  }
}

Role labels may also appear inside contributor or provenance metadata.

{
  "msp:provenance": {
    "type": [
      "original",
      "ai-assisted"
    ],
    "contributors": [
      {
        "id": "mark-johnson",
        "role": "author"
      },
      {
        "id": "chatgpt-jdk",
        "role": "ai-partner"
      }
    ]
  }
}

Guidance

• Role declarations should accurately reflect actual functional participation.
• Role labels should be used consistently across an implementation.
• Role labels should be clear to both humans and agents.
• Role should be interpreted in relation to the entity and resource where it appears.
• Role should inform responsibility and participation but should not be treated as a trust guarantee by itself.

Deprecated compatibility note

The deprecated compliance term should not be emitted in new MSP-1 v1.0.1 declarations. Legacy role category values that refer to compliance should receive advisory compatibility handling rather than being treated as active role vocabulary.

Related Terms