P1-REQ-13-3-005
Statement
The Conceptual Architecture SHALL NOT treat an Ecosphere, Ecosystem, Domain, or Classification Path as a DDS Domain ID, DDS partition, Kubernetes namespace, container name, pod name, process identifier, topic name, 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:
Related requirement identifiers:
Status
Draft