Stable meaning
Namespace terms define canonical meaning and should not be redefined, overloaded, or repurposed by local implementations.
AI-friendly semantics for trusted information.
MSP-1 Namespace
The MSP-1 namespace provides stable, human-readable identifiers for core Mark Semantic Protocol terms. These terms define canonical meaning for protocol fields used in MSP-1 declarations, schemas, validators, and implementation tooling.
MSP-1 namespace terms exist to give agents, validators, developers, and reviewers a stable reference point for the meaning of protocol fields. Each namespace URI identifies a term used by MSP-1 without requiring the term to be redefined in every schema, declaration, or implementation guide.
The namespace is schema-agnostic. It may be referenced from JSON-LD contexts, JSON schemas, documentation, validation tools, and other machine-readable or human-readable implementations.
Namespace terms define canonical meaning and should not be redefined, overloaded, or repurposed by local implementations.
MSP-1 namespace terms can support JSON-LD, JSON Schema, documentation, validators, and tooling without depending on a single serialization format.
The absence of a namespace term in a declaration does not automatically imply invalidity. Required and optional fields are defined by the applicable MSP-1 schema or specification scope.
The following terms are part of the MSP-1 core namespace. Each term links to a human-readable reference page for that term.
| Term | Namespace URI | Meaning |
|---|---|---|
| protocol | https://msp-1.org/ns/protocol |
Declares protocol identity and version. |
| discovery | https://msp-1.org/ns/discovery |
Declares the canonical discovery mechanism for MSP-1 metadata. |
| site | https://msp-1.org/ns/site |
Defines the canonical identity of a website. |
| page | https://msp-1.org/ns/page |
Defines a web page as a scoped MSP-1 entity. |
| id | https://msp-1.org/ns/id |
Provides a stable identifier for a resource or entity. |
| url | https://msp-1.org/ns/url |
Identifies the URL associated with a resource. |
| title | https://msp-1.org/ns/title |
Represents the observable document title of a page or resource. |
| name | https://msp-1.org/ns/name |
Provides a human-readable display name for a resource. |
| description | https://msp-1.org/ns/description |
Provides a concise explanation of a resource. |
| intent | https://msp-1.org/ns/intent |
Declares why a resource exists. |
| interpretiveFrame | https://msp-1.org/ns/interpretiveFrame |
Declares assumptions, framing, or interpretive constraints. |
| provenance | https://msp-1.org/ns/provenance |
Documents content origin and lineage. |
| authority | https://msp-1.org/ns/authority |
Declares authoritative standing within a defined scope. |
| trust | https://msp-1.org/ns/trust |
Provides reliability and verification signals. |
| canonical | https://msp-1.org/ns/canonical |
Identifies the authoritative representation of a resource. |
| compliance | https://msp-1.org/ns/compliance |
Declares the level of MSP-1 protocol implementation. |
| author | https://msp-1.org/ns/author |
Identifies the entity responsible for creating content. |
| reviewer | https://msp-1.org/ns/reviewer |
Identifies an independent evaluator of content. |
| role | https://msp-1.org/ns/role |
Defines the contextual role held by an entity. |
| type | https://msp-1.org/ns/type |
Classifies a resource or entity. |
| parent | https://msp-1.org/ns/parent |
Declares a hierarchical relationship. |
| section | https://msp-1.org/ns/section |
Defines a subdivision of a page or resource. |
| revision | https://msp-1.org/ns/revision |
Represents a discrete update event. |
| revisionDate | https://msp-1.org/ns/revisionDate |
Records the timestamp of a revision. |
| revisionNotes | https://msp-1.org/ns/revisionNotes |
Describes changes made in a revision. |
| revisionVersion | https://msp-1.org/ns/revisionVersion |
Identifies the semantic version associated with a revision. |
| version | https://msp-1.org/ns/version |
Identifies semantic version state or compatibility. |
MSP-1 schemas may use the namespace base as a JSON-LD prefix so that compact field names resolve to stable MSP-1 namespace identifiers.
{
"@context": {
"msp": "https://msp-1.org/ns/",
"protocol": "msp:protocol",
"site": "msp:site",
"page": "msp:page",
"intent": "msp:intent",
"provenance": "msp:provenance",
"trust": "msp:trust",
"discovery": "msp:discovery",
"wellKnown": "msp:wellKnown"
}
}
MSP-1 uses the discovery and wellKnown terms to support deterministic
discovery of site-level declarations. The canonical site-level endpoint is:
/.well-known/msp.json
This endpoint is used for site-level MSP-1 metadata. Inline page-level MSP-1 declarations may include a discovery object pointing back to the canonical well-known resource.
Defines MSP-1 entities, required fields, discovery behavior, and interpretation rules.
Provides JSON schemas for validation, generation, and implementation tooling.
Documents the intended well-known URI registration details for msp.json.