For organizations
Institutions that hold information about land, living systems, facilities, materials, and organizations can take part in one identity system without giving up custody of their records or their responsibility for them — and without adopting anyone else’s software.
Who benefits
Land records, business registers, environmental and food-safety regulators
What stays with you
Official records, legal definitions, and the authority to register and amend them.
What shared identity adds
Other systems can reference registered objects exactly, reducing re-keying and mismatched records — without the register being copied.
Universities, laboratories, field stations, data repositories
What stays with you
Observations, methods, datasets, and the scientific responsibility for them.
What shared identity adds
Findings attach to the specific parcels, organisms, facilities, and samples they describe, and remain connected as they are reused.
Producers, processors, cooperatives, buyers, certifiers, logistics providers
What stays with you
Commercial records, contracts, and control over what is shared and with whom.
What shared identity adds
Partners refer to the same farms, facilities, lots, and shipments without merging databases or adopting each other’s codes.
Lenders, insurers, impact and transition finance
What stays with you
Underwriting, credit decisions, and the confidentiality of both.
What shared identity adds
Confidence that the parcel, facility, or organization being financed is the one that others observe and report on.
Farm and factory software, platforms, digital agents
What stays with you
Their products, data models, and customer relationships.
What shared identity adds
A neutral identity contract for interoperability, so integrations do not depend on fragile name and address matching.
How participation is designed
The RSM ID specification describes how independently governed organizations take part. In outline, an organization would participate in five ways. None of these processes is open yet.
Roles
One organization may hold several of these roles, or none. The specification records them separately because each carries different responsibilities — and none of them, including issuing an identity, grants legal ownership of a resource or access to its records.
| Role | Responsible for | Does not | Source |
|---|---|---|---|
| Namespace controller | Holds a registered RID prefix and decides who may issue under it, with delegation, signing keys, and succession arrangements recorded in the registry. | Own the resources identified under the prefix, or reveal who currently owns any of them. | Doc 08 §3.2 · Doc 08 §5.2 |
| Authorized issuer | Issues RIDs and registers RRNs within a delegated namespace, atomically and with auditable provenance. | Acquire ownership of, consent over, or access to anything it registers. | Doc 08 §5.4 · Doc 08 §11.2 |
| Resource steward | Maintains information about a resource and governs its disclosure — as legal owner, operational custodian, or the community entitled to steward its knowledge. | Need to be the issuer. Issuance, ownership, custody, and stewardship are recorded as separate roles. | Doc 08 §8.5 |
| Semantic Space administrator | Governs a Semantic Space — its content, policies, and the deployment that serves it. The space has its own RID and RSN. | Own every resource described in the space. Delegated administration and resource ownership are separate relationships. | Doc 08 §4.6 · Doc 08 §4.5 |
| Consuming participant | References resources by RID, resolves them through a conforming resolver, and keeps the provenance of what it aggregates. | Treat cached or aggregated descriptions as its own canonical knowledge, or assume ownership of what it references. | Doc 08 §10.3 · Doc 08 §14.4 |
Namespaces
Every RID begins with a registered prefix, an issuance namespace that is globally unique and never reused. Within it, registered namespace authorities issue identities and names; the authority segment of an RRN records which one.
A person, cooperative, company, research institution, or community may administer one or more Semantic Spaces. Authority can be delegated without transferring ownership of the resources described — delegation and ownership are separate relationships. Participation does not require 451 applications or any single hosting provider.
Example
A regional cooperative could administer its own space, rrn:451:willowcreek:us-ca:willowcreek:space/root, and issue names in it — without owning the farms it describes. (Fictional.)
In the specification
The 451 prefix is proposed for the controlled 451 federation and must be registered before production use (Doc 08 §3.2).
Read the RSM ID specification against the resources your systems already manage, keep a field ready for a canonical RID beside your own identifiers, and see how resolution is presented using the demonstration resolver. When registration and participation processes exist, they will be described on this site.
No organization is listed as a participant on this site because no participation programme exists yet. The spaces named in the specification — RSM, Wellzai, and Musewoods — are proposed, not operating.