Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:l:logical_interaction_traceability [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:l:logical_interaction_traceability [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 9: / Line 9: @@
 Logical Interaction Traceability supports review of how the architecture behaves. It identifies the structure of recurring interactions such as Register Node, Report Node Status, Publish Domain Information, Subscribe to Domain Information, Issue Control Command, Acknowledge Control Command, Request Policy Decision, Record Audit and Provenance, and Replay or Reconstruct Information.
-Logical Interaction Traceability also supports domain-profile specialisation. A domain profile specialises a logical interaction pattern while preserving the trace to the reusable Part 2 pattern.
+Logical Interaction Traceability also supports domain-profile specialization. A domain profile specializes a logical interaction pattern while preserving the trace to the reusable Part 2 pattern.
 ===== Definition =====
@@ Line 17: / Line 17: @@
 ===== Source =====
-Specialisation of Traceability, Communication Endpoint, Node Role, Data Structure Instance, and Runtime Plane from Part 1, Sections 7.10, 7.6, 7.4, 7.8, and 7.5; generalised from interaction-sequence and use-case material in the original FX Demo Reference Architecture.
+Specialization of Traceability, Communication Endpoint, Node Role, Data Structure Instance, and Runtime Plane from Part 1, Sections 7.10, 7.6, 7.4, 7.8, and 7.5; generalised from interaction-sequence and use-case material in the original FX Demo Reference Architecture.
 ===== Note =====