====== 9.8 Cross-Concern Relationships ======
[[fxdemo:01-part:start | Go to Top ]]

The concerns in this model interact, but they remain distinguishable.

For example, a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] combines [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|Structure]] with references to [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] meaning. A validation process may [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpret]] [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]] using [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] definitions and [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]]-approved rules. A release decision may depend on [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]] values, [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] classification, policy authority, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] requirements. A provenance record may connect [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]], [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]], and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] into a single reviewable chain.

To identify a cross-concern relationship, record:

  * Concerns involved
  * Element, artifact, rule, or decision creating the relationship
  * [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]] mechanism controlling the relationship, where applicable
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship preserving the connection
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] supporting later review, where applicable

Table 9.8-1 provides examples of cross-concern relationships.

Table 9.8-1: Examples of cross-concern relationships in structured information processing

^ Originating concern ^ Related concern ^ Example ^
| [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|Structure]] | [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]] | A field definition references the governed meaning of a currency code. |
| [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]] | [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]] | A semantic classification provides context for a validation rule. |
| [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]] | [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | A derived analytical assertion records the rule version and input [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]] used to produce it. |
| [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]] | [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]] | A semantic authority approves a change to a definition or classification. |
| [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]] | [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability_and_evidence|Traceability and Evidence]] | A release policy requires [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] of the release decision and handling obligations. |
| [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]] | [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability_and_evidence|Traceability and Evidence]] | A persisted transaction record links to provenance and audit records. |

Cross-concern relationships support a governable architecture. They allow concerns to interact without allowing one concern to absorb or obscure another.
----

<WRAP centeralign>

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

</WRAP>