Registry [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Registry ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A Registry is a managed collection of records that authoritatively identifies subjects under a defined registration process.

A Registry can register:

  * [[dido:99_annexes:annex-b-terms-and-definitions:o:organization|Organizations]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:community_of_interest|Communities of Interest]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:u:user|Users]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:r:role|Roles]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_set|Node Sets]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Targets]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definitions]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]]
  * Identifiers
  * Names
  * Versions
  * Other subjects requiring authoritative registration

A Registry can provide capabilities for:

  * Submitting a registration request
  * Validating registration information
  * Assigning an identifier
  * Recording a registration
  * Approving or rejecting a registration
  * Updating a registration
  * Suspending a registration
  * Revoking a registration
  * Retiring a registration
  * Resolving an identifier
  * Discovering registered subjects
  * Recording registration status
  * Recording registration history
  * Preserving registration authority
  * Preserving [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Maintaining [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

A Registry can identify:

  * Its identity
  * Its name
  * Its description
  * Its Registry type
  * Its registration [[dido:99_annexes:annex-b-terms-and-definitions:a:authority|Authority]]
  * Its owner
  * Its operator
  * Its registrar Roles
  * Its applicable scope
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_domain|Governance Domain]]
  * Its permitted subject types
  * Its registration requirements
  * Its identifier-assignment rules
  * Its validation rules
  * Its registration statuses
  * Its update and correction rules
  * Its suspension and revocation rules
  * Its interfaces
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:e:endpoint|Endpoints]]
  * Its access controls
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:p:policy|Policies]]
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_policy|Governance Policies]]
  * Its Provenance
  * Its Traceability

===== Definition =====

//managed collection of records that authoritatively identifies subjects under a defined registration process//

===== Source =====

Adapted from:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:catalog|Catalog]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]]
  * DIDO Reference Architecture
  * DIDO Reference Implementation Conceptual Model
  * DIDO-TE draft Requirements Register

===== Note =====

A Registry requires:

  * An identified registration Authority
  * A defined registration process
  * Defined registration requirements
  * Defined registration statuses
  * An authoritative registration record

A Registry differs from a [[dido:99_annexes:annex-b-terms-and-definitions:c:catalog|Catalog]]:

  * A Registry authoritatively records subjects under a registration process
  * A Catalog describes subjects and enables their discovery

A Registry can provide Catalog capabilities. A Catalog does not necessarily provide authoritative registration.

A Registry differs from a [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]]:

  * A Registry maintains authoritative registration records
  * A Repository stores, preserves, and provides access to retained content

A Repository can store the records maintained by a Registry. The same system can provide Registry and Repository capabilities when it satisfies both definitions.

A Registry differs from an [[dido:99_annexes:annex-b-terms-and-definitions:i:inventory|Inventory]]:

  * A Registry records subjects recognized under an authoritative registration process
  * An Inventory accounts for subjects held, controlled, allocated, available, or otherwise tracked within a defined scope

A registered subject does not need to be possessed or controlled by the registration Authority. An inventoried subject does not need to be authoritatively registered.

A registration does not necessarily establish:

  * Approval for use
  * Availability
  * Certification
  * Conformance
  * Deployment
  * Ownership
  * Validation

The registration record must state these characteristics explicitly when they apply.

A Registry can be:

  * Centralized
  * Distributed
  * Federated
  * Public
  * Private
  * Organization-specific
  * Community-specific
  * Domain-specific

A federated Registry can coordinate authoritative records maintained by multiple registration Authorities. The federation rules must define identifier uniqueness, authority, conflict resolution, and record synchronization.

A change to a registered subject does not necessarily create a new registration. The registration Policy determines whether the change:

  * Updates the existing registration
  * Creates a new registered Version
  * Creates a separate registration
  * Suspends or retires the previous registration

===== Example =====

A DIDO-TE Node Registry authoritatively records Nodes permitted to participate in a defined Governance Domain.

Each registration record identifies:

  * The Node identity
  * The Node owner
  * The applicable Node Roles
  * The applicable Node Version
  * The applicable Endpoints
  * The registration status
  * The registering Authority
  * The registration time
  * The applicable Governance Policies
  * The applicable Provenance
  * The applicable Traceability

The Node Registry establishes the authoritative registration of the Node. A separate Catalog can provide additional discovery information, and an Inventory can record whether the Node is currently deployed or available.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>