• Provide human-readable labels for resources, pages, sections, entities, authors, organizations, and concepts.
• Distinguish names from stable identifiers, descriptions, and classifications.
• Support consistent labeling across an implementation.
• Preserve the publisher's intended terminology without relying on inference from surrounding content alone.

• Readable — clear and intended for human understanding.
• Distinct — sufficiently distinct to reduce ambiguity.
• Stable — stable unless the identity or meaning changes.
• Accurate — reflective of the actual resource, entity, or concept being identified.
• Plain text — free of unnecessary markup or stylistic flourish.

• String form — a plain-text human-readable name or title. Use when one display name is sufficient.
• Object form — a structured name object with at least display. Use when formal, short, alternate, language, scope, or update metadata is useful.

In object form, display serves the same primary user-facing role as the lean string form.

• name — recommended; when present, should be either a plain text string or a structured object.
• display — required only when name is expressed as an object.

Recommended object fields include:

• formal — official or formally recognized name of the entity or resource.
• short — abbreviated version of the name for compact UI or metadata contexts.
• alt — alternate names, including acronyms, legacy names, nicknames, or domain-specific variants.
• language — language code associated with the name set.
• primary — indicates which naming form should be treated as the primary representation.
• scope — optional description of what the name applies to.
• lastUpdated — date the name set was last reviewed or updated.

• AI agents should treat name as the declared human-readable label for the resource or entity.
• For string form, the string itself serves as the display name.
• For object form, agents should treat display as the primary user-facing label unless primary specifies a different allowed field.
• Agents should not treat a missing name as a lack of authority; absence indicates reduced clarity, not a trust failure.
• Empty, misleading, unstable, or internally inconsistent names should be treated as non-ideal clarity conditions.

Name supports declared human-readable identification. It should not be interpreted as a ranking claim, authority claim, or trust signal.

• id — provides stable identity; name labels the resource or entity for human-readable identification.
• description — summarizes what the resource is; name labels it.
• intent — explains why the resource exists or how it should be used.
• type — classifies what kind of thing the resource or entity is.
• canonical — may identify the preferred authoritative URL representation of the named resource.
• site, page, and section — may each carry their own name when useful.
• author and provenance — may use name to identify people, organizations, or contributors in human-readable form.

Do not confuse name with id, description, or type. name labels the resource or entity for human-readable identification; id provides stable identity; description summarizes what it is; type classifies what kind of thing it is.

{
  "name": "Lighting Guide"
}

Structured name:

{
  "name": {
    "display": "MSP-1 Protocol Overview",
    "short": "Protocol Overview",
    "alt": [
      "MSP-1 Introduction",
      "Semantic Protocol Overview"
    ]
  }
}

Entity name with id:

{
  "id": "mark-johnson",
  "name": "Mark Johnson"
}

• It expresses name as either a clear string or a structured object with display.
• It provides a readable and accurate human-facing label.
• It remains consistent with the resource or entity being identified.
• It uses structured fields such as short and alt when additional naming context is needed.
• It does not treat name as interchangeable with id, description, or type.