Differences

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

--- fxdemo:02-part:13-relationship-to-domain-logical-profiles:13-6-boundary-between-part-2-and-domain-logical-profiles:start [2026/07/11 11:10] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:02-part:13-relationship-to-domain-logical-profiles:13-6-boundary-between-part-2-and-domain-logical-profiles:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 [[fxdemo:02-part:start | Go To Top ]]
-Part 2 defines the reusable, distributed, node-based Logical Architecture / PIM. Domain Logical Profiles specialise that Logical Architecture for specific financial Domains.
+Part 2 defines the reusable, distributed, node-based Logical Architecture / PIM. Domain Logical Profiles specialize that Logical Architecture for specific financial Domains.
 Part 2 defines logical concepts and patterns that apply across financial Domains. A Domain Logical Profile defines Domain-specific logical content. This boundary prevents Domain-specific details from becoming part of the reusable logical foundation.
 When a Domain Logical Profile introduces a Domain-specific logical element, it identifies:
-  * The inherited Part 2 logical element it specialises
+  * The inherited Part 2 logical element it specializes
-  * The Domain-specific reason for the specialisation
+  * The Domain-specific reason for the specialization
   * Classification Path and Domain scope
-  * Affected [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]], [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]], [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definitions]], Runtime Planes, and interaction patterns
+  * Affected [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definitions]], Runtime Planes, and interaction patterns
-  * Governance and [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_compatibility|compatibility]] impact
+  * Governance and [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_compatibility|compatibility]] impact
-  * [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] and [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations
 This boundary allows multiple Domain Logical Profiles to share the same Logical Architecture / PIM while preserving Domain-specific meaning and reviewability.