This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| fxdemo:01-part:11-conceptual-rules-and-constraints:11-4-classification-values-do-not-define-runtime-boundaries [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | fxdemo:01-part:11-conceptual-rules-and-constraints:11-4-classification-values-do-not-define-runtime-boundaries [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[fxdemo:01-part:start | Go to Top ]] | [[fxdemo:01-part:start | Go to Top ]] |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification]] values identify governed business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] scope. They do not define [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime]] communication boundaries, deployment boundaries, security zones, repository paths, or executable artefacts. | [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification]] values identify governed business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] scope. They do not define [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime]] communication boundaries, deployment boundaries, security zones, repository paths, or executable artifacts. |
| |
| For example, the classification path: | For example, the classification path: |