Viewgraph · 5 frames
The anatomy of an Identity Record
What an RSM Identity Record contains, keyed by RID: the required minimum, the recommended additions, and the things it deliberately does not hold.
Viewgraph5 frames
Identity Record
One durable record, keyed by the RID
Not a second identity, and not the resource itself.
RSM ID Learning Center
rsmid.org
Required minimum
What every record must contain
Enough to identify the referent and to prevent the RID from ever being reassigned.
The canonical key and the namespace it was issued under.
When the identity was registered.
Which one thing this RID identifies.
Its registry state, and who issued it under which authority.
Where applicable
Names, kind, space, and bindings join the record
Several names may map to one RID over time; the space binding names a logical space, not a host.
Rendering diagram…
The space binding identifies the logical Semantic Space — never a particular Locus process, host, or database.
Boundaries
What an Identity Record is not
Each boundary keeps identity separate from content, ownership, and equivalence.
Content, revisions, and relationships stay with the Semantic Space.
Recording a referent proves nothing about who owns it.
External identifiers listed beside it are not thereby the same referent.
On the wire and in storage
One logical record, several projections
A resolver's JSON response and a reference database are views of the record, not the record's final schema.
At least rid, kind, identityStatus, and resolutionStatus.
Spread across identities, names, bindings, and events tables, keyed by RID.
A versioned normative schema is still to be published.
Read as text
- Identity RecordOne durable record, keyed by the RIDNot a second identity, and not the resource itself.Source: Document 08 v1.1 §5.3.1
- Required minimumWhat every record must containEnough to identify the referent and to prevent the RID from ever being reassigned.RID and issuing prefixThe canonical key and the namespace it was issued under.Creation timestampWhen the identity was registered.Registered referent descriptorWhich one thing this RID identifies.Lifecycle status and issuance provenanceIts registry state, and who issued it under which authority.Source: Document 08 v1.1 §5.3
- Where applicableNames, kind, space, and bindings join the recordSeveral names may map to one RID over time; the space binding names a logical space, not a host.The Identity Record for RID 451.7K4M9Q2X8D5P0R6T links to its current and historical RRNs, to its registered kind, and to the Wellzai Semantic Space as its authoritative space binding, along with governance references.Source: Document 08 v1.1 §5.3, §5.3.1 — identifiers illustrative
- BoundariesWhat an Identity Record is notEach boundary keeps identity separate from content, ownership, and equivalence.Not a copy of the resourceContent, revisions, and relationships stay with the Semantic Space.Not evidence of ownershipRecording a referent proves nothing about who owns it.Not proof of samenessExternal identifiers listed beside it are not thereby the same referent.Source: Document 08 v1.1 §5.3.1
- On the wire and in storageOne logical record, several projectionsA resolver's JSON response and a reference database are views of the record, not the record's final schema.JSON identity responseAt least rid, kind, identityStatus, and resolutionStatus.Reference schemaSpread across identities, names, bindings, and events tables, keyed by RID.Final schemaA versioned normative schema is still to be published.Source: Document 08 v1.1 §18.6; Document 09 v1.1 §4.1.1
Sources and provenance
Normative basis
- Document 08 v1.1 — Section 5.3Resource identity record
- Document 08 v1.1 — Section 5.3.1Canonical RSM Identity Record
- Document 08 v1.1 — Section 18.6Resolution response and representation distinction
- Document 09 v1.1 — Section 4.1.1RSM Identity Record mapping
This viewgraph is an informative explanation. Where it and the specifications differ, Documents 08 and 09 v1.1 govern.
What it contains
- Document 08 v1.1 · normative
- Grounded directly in Document 08, the controlling standard. Cited by section.
- Document 09 v1.1 · reference implementation
- Guidance from Document 09, the proposed reference implementation. Subordinate to Document 08; its technology choices are not requirements.
- Interpretation
- Explanation or design rationale written for this Learning Center. It does not add requirements.
- Hypothetical example
- An illustrative scenario. Its identifiers are examples or fictional; none has been issued.
Related
Pathway: Resolution · Technical · Revised 2026-10-09 · Content ID viewgraph.identity-record (a page identifier on this site, not an RID)