reviewer
Identifies a person, organization, or system that reviewed, audited, evaluated, or approved a resource.
AI-friendly semantics for trusted information.
MSP-1 Namespace Term
Identifies the human individual or organization primarily responsible for creating or originating an MSP-1 resource.
msp:author declares the primary creator or originating responsible party for a resource. The author may be a person or an organization.
The author term supports attribution and provenance context. It should not be confused with msp:reviewer, msp:provenance, msp:authority, or msp:trust. Authorship identifies creation or origination; review, lineage, authority, and trust are separate interpretive signals.
The canonical MSP-1 form uses type to distinguish a person from an organization.
{
"msp:author": {
"name": "Mark Johnson",
"type": "Person",
"id": "mark-johnson",
"role": "author"
}
}
Organization authorship may be declared when an organization is the originating responsible party.
{
"msp:author": {
"name": "MSP-1",
"type": "Organization",
"id": "https://msp-1.org/",
"role": "publisher"
}
}
The preferred MSP-1 field is type. The JSON-LD field @type may appear in compatibility contexts, but canonical MSP-1 author declarations should use type.
{
"msp:author": {
"@type": "Person",
"name": "Example Author"
}
}
name and type.id is strongly recommended for durable attribution.id may be a site-local identifier, URL, profile reference, ORCID, or other persistent string.Identifies a person, organization, or system that reviewed, audited, evaluated, or approved a resource.
Documents origin, lineage, creation method, source relationship, and contributor context.
Identifies the function or responsibility an entity has in relation to a resource.
Provides a stable identifier for a resource, entity, page, section, or conceptual element.