Catalog [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.
====== Catalog ======

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

===== Discussion =====

A Catalog is a managed collection of [[dido:99_annexes:annex-b-terms-and-definitions:c:catalog_entry|Catalog Entries]] that describes and enables discovery of identified subjects.

A Catalog can describe:

  * [[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:t:test_run|Test Runs]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]]
  * [[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:e:executable_artifact|Executable Artifacts]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_resource|Operational Resources]]
  * Other identifiable subjects

A Catalog can provide capabilities for:

  * Identifying subjects
  * Describing subjects
  * Classifying subjects
  * Discovering subjects
  * Searching for subjects
  * Filtering subjects
  * Comparing subjects
  * Locating subjects
  * Selecting subjects
  * Retrieving references to subjects
  * Determining subject availability
  * Determining subject status
  * Determining applicable [[dido:99_annexes:annex-b-terms-and-definitions:v:version|Versions]]
  * Identifying relationships among subjects

A Catalog can identify:

  * Its identity
  * Its name
  * Its description
  * Its Catalog type
  * Its Version
  * Its owner
  * Its administrator
  * Its governing [[dido:99_annexes:annex-b-terms-and-definitions:a:authority|Authority]]
  * Its applicable scope
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_domain|Governance Domain]]
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:community_of_interest|Community of Interest]]
  * Its entry requirements
  * Its classification scheme
  * Its supported search and discovery capabilities
  * Its applicable interfaces
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:e:endpoint|Endpoints]]
  * Its applicable 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 [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

A Catalog can contain descriptive information directly or reference descriptive information maintained by another system.

A Catalog can reference a subject without containing or storing the subject itself.

===== Definition =====

//managed collection of [[dido:99_annexes:annex-b-terms-and-definitions:c:catalog_entry|Catalog Entries]] that describes and enables discovery of identified subjects//

===== Source =====

Adapted from:

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

This definition establishes Catalog as the general concept from which specialized catalogs can derive.

===== Note =====

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

  * A Catalog is the managed collection
  * A Catalog Entry describes and references one identified subject or a defined grouping of subjects

A Catalog differs from the subjects it describes. Adding, changing, or removing a Catalog Entry does not necessarily add, change, or remove the described subject.

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

  * A Catalog describes subjects and enables their discovery
  * A Repository stores and manages Artifacts or other retained content

A Catalog can reference subjects stored in a Repository. The same system can provide both Catalog and Repository capabilities when it satisfies both definitions.

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

  * A Catalog describes subjects and enables their discovery
  * A Registry records subjects under an identified registration authority and registration process

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

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

  * A Catalog describes subjects that users can discover or select
  * An Inventory records subjects held, controlled, allocated, available, or otherwise accounted for within a defined scope

A Catalog can describe subjects that are not currently possessed, deployed, or available. An Inventory ordinarily reflects subjects accounted for within its defined scope.

A Catalog is not necessarily:

  * Authoritative
  * Complete
  * Public
  * Centrally managed
  * Stored in one location
  * Limited to one subject type
  * A Repository
  * A Registry
  * An Inventory

A Catalog can be:

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

A federated Catalog can provide discovery across multiple independently governed Catalogs while preserving the ownership and governance of their Catalog Entries.

A Catalog Entry should identify the exact subject and applicable Version when multiple Versions exist.

A Catalog should preserve Traceability among:

  * The Catalog Entry
  * The described subject
  * The applicable Version
  * The source of the descriptive information
  * The governing Authority
  * The applicable Policies
  * The applicable Provenance

===== Example =====

A DIDO-TE Test Definition Catalog contains Catalog Entries describing approved Test Definitions.

Each Catalog Entry identifies:

  * The Test Definition identity
  * The Test Definition Version
  * The test purpose
  * The applicable Test Items
  * The applicable Test Environment requirements
  * The applicable Validation Criteria
  * The approving Authority
  * The approval status
  * The applicable Governance Policies
  * The Repository location
  * The applicable content digest
  * The applicable Provenance
  * The applicable Traceability

The Test Definition Catalog enables a User acting in the Test Operator Role to discover and select an approved Test Definition.

The Catalog Entry references the Test Definition stored in an Artifact Repository. The Catalog describes and locates the Test Definition but does not need to contain the Test Definition itself.

----

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