5.6 Classification Values and Runtime Identifiers [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.

====== 5.6 Classification Values and Runtime Identifiers ======
[[fxdemo:01-part:start | Go to Top ]]

[[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification]] values do not act as runtime identifiers.

They identify governed business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] scope. They do not identify runtime communication [[dido:99_annexes:annex-b-terms-and-definitions:d:domain|Domain]]s, deployment namespaces, containers, pods, processes, repositories, files, or executable artifacts.

Authors and implementers must not treat classification values as substitutes for:

  * DDS Domain IDs
  * DDS partitions
  * Kubernetes namespaces
  * Container names
  * Pod names
  * Process identifiers
  * Topic names
  * [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identities]]
  * Repository paths
  * Deployment profile names

Later parts may include classification values in metadata, documentation, configuration, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], or naming conventions for readability and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. Those uses do not turn classification values into runtime identifiers.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>