Differences

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

--- fxdemo:01-part:13-conceptual-requirements:13-3-classification-requirements [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:13-3-classification-requirements to fxdemo:01-part:13-conceptual-requirements:13-3-classification-requirements owen
+++ fxdemo:01-part:13-conceptual-requirements:13-3-classification-requirements [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 13.3 Classification Requirements ======
-[[fxdemo:01-part:start | Go to Top ]]
+[[fxdemo:01-part:13-conceptual-requirements:start | Go to Conceptual Requirements]]
-  - The Conceptual Architecture SHALL define an Archetype Classification Model consisting of Ecosphere, Ecosystem, and Domain.
+This section identifies the normative requirements for classification established by Part 1. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-01:start|Annex C: Requirements, Part 1]].
-  - The Conceptual Architecture SHALL use Classification Paths to identify governed business and semantic scope.
-  - Each Classification Path SHALL identify an Ecosphere, an Ecosystem, and a Domain when all three levels apply.
-  - The Conceptual Architecture SHALL distinguish Classification Paths from runtime identifiers, deployment identifiers, repository paths, implementation artefacts, and communication boundaries.
-  - 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.
-  - A later profile that inherits a Classification Path SHALL preserve the meaning of the inherited Ecosphere, Ecosystem, and Domain.
-  - A later profile that introduces a new Ecosystem or Domain SHALL identify the parent classification, the reason for the new classification, and the relationship to existing classifications.
+<WRAP table-caption>
+**Table 13.3-1:** Part 1 classification requirements.
+</WRAP>
+^ Requirement ID ^ Statement ^
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-001:start|P1-REQ-13-3-001]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-001:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-002:start|P1-REQ-13-3-002]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-002:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-003:start|P1-REQ-13-3-003]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-003:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-004:start|P1-REQ-13-3-004]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-004:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-005:start|P1-REQ-13-3-005]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-005:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-006:start|P1-REQ-13-3-006]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-006:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-007:start|P1-REQ-13-3-007]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-007:start#statement&noheader&nofooter}} |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>