com.emdashcms.experimental.publisher.profile

A publisher's identity-level profile. Distinct from `com.emdashcms.experimental.package.profile`, which carries per-package metadata. The publisher profile is the canonical landing page for the entity behind a DID: 'who is publishing these packages?'. The record key is the literal string `self`. Per-package fields like `authors[]` and `security[]` on package profile records remain authoritative for their respective packages and MAY differ from the values here; clients render package-level fields when present, falling back to publisher profile values otherwise. The publisher profile's `displayName` is the value that `com.emdashcms.experimental.publisher.verification` records bind against — see that lexicon's docs for the validity rules.

Repository @emdashcms.com did:plc:ilznslhspsvk6naatedr66pi namespace authority
Details · record, key literal:self
Kindrecord
Record keyliteral:self
Authoritypublisher.experimental.emdashcms.com
Indexed

Record

record · key literal:self

Properties

contact

array

Identity-level contact channels for the publisher (general / security). Per-package security contacts on package profile records remain authoritative for their respective packages; this list is for the publisher entity itself.

  • maxLength: 8
itemsref
Reference

Short description / bio of the publisher. SHOULD NOT exceed 280 characters per UI convention. Plain text; no Markdown.

  • maxLength: 2048
  • maxGraphemes: 280

displayName

requiredstring

Human-readable name for the publisher (e.g. 'Acme Plugin Co.'). Displayed alongside packages and verification badges. Verification records bind against this value: a change to displayName invalidates any unexpired verification claims targeting this DID until the issuer re-attests.

  • maxLength: 1024
  • maxGraphemes: 100

updatedAt

string · datetime

When this profile was last updated.

url

string · uri

Publisher's primary homepage. Distinct from per-package repo or homepage URLs.

  • maxLength: 2048

#contact

object

Identity-level publisher contact. At least one of url or email MUST be present; Lexicon cannot express required-one-of, so aggregators MUST validate this and reject records carrying a contact with neither field. Same shape as `com.emdashcms.experimental.package.profile#contact`.

Properties

email

string
  • maxLength: 256

kind

string

Channel role. 'general' for ordinary contact, 'security' for vulnerability reporting.

  • maxLength: 32
  • knownValues: general | security

url

string · uri
  • maxLength: 1024

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Plugin package profile record. EXPERIMENTAL: this NSID is part of the experimental phase of the EmDash plugin registry. The stable namespace target is com.emdashcms.package.profile.

  • Verification claim by one DID about another's status as a trusted EmDash plugin publisher. Modeled on Bluesky's app.bsky.graph.verification shape but in EmDash's own namespace so the semantics are scoped to plugin publishing. EXPERIMENTAL: shape may change before stabilisation.

  • What a publisher says about themselves in the marketplace.

  • A HappyView plugin package, in its publisher's repo. The record key is the package slug, so the slug is immutable: changing it means a different package.

  • An author's byline.pub profile, signed by and stored in the author's own repository. The repo's DID is the author identity; this record is the byline.pub-specific public profile that extends it, independent of any venue's own profile record. One record per repo (key 'self').