dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-005:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-005:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-005:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-3-005 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The Conceptual Architecture SHALL NOT treat an [[dido:99_annexes:annex-b-terms-and-definitions:e:ecosphere|Ecosphere]], [[dido:99_annexes:annex-b-terms-and-definitions:e:ecosystem|Ecosystem]], [[dido:99_annexes:annex-b-terms-and-definitions:d:domain|Domain]], or [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification Path]] as a DDS Domain ID, DDS partition, Kubernetes namespace, container name, pod name, process identifier, topic name, [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]], repository path, or deployment profile name.
 +
 +===== Source =====
 +
 +Part 1, Section 13.3: Classification Requirements.
 +
 +===== Rationale =====
 +
 +Ecosphere, Ecosystem, Domain, and Classification Path identify governed conceptual classification. DDS Domain IDs, DDS partitions, Kubernetes namespaces, container names, pod names, process identifiers, topic names, Node Identities, repository paths, and deployment profile names identify runtime, implementation, deployment, or repository concerns.
 +
 +Treating a conceptual classification as one of these identifiers collapses conceptual scope into implementation or deployment mechanics.
 +
 +===== Applies To =====
 +
 +This requirement applies to all uses of conceptual classification terms within the Conceptual Architecture.
 +
 +It applies specifically to separation between conceptual classification and:
 +
 +  * DDS Domain IDs
 +  * DDS partitions
 +  * Kubernetes namespaces
 +  * Container names
 +  * Pod names
 +  * Process identifiers
 +  * Topic names
 +  * Node Identities
 +  * Repository paths
 +  * Deployment profile names
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Conceptual Architecture does not treat an Ecosphere, Ecosystem, Domain, or Classification Path as a runtime, implementation, deployment, or repository identifier.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Conceptual classification terms retain conceptual meaning
 +  * DDS identifiers do not replace classification terms
 +  * Kubernetes identifiers do not replace classification terms
 +  * Runtime names do not replace classification terms
 +  * Repository paths and deployment profile names do not replace classification terms
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-3-classification-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-004:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-005:start]]
 +
 +===== Status =====
 +
 +Draft