Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model to dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Platform Independent Model (PIM)======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
 ===== Discussion =====
@@ Line 7: / Line 7: @@
 A Platform Independent Model, or PIM, provides a technology-neutral logical model of a system. It sits between the conceptual architecture and one or more platform-specific models.
-Within the FX Demo Reference Architecture, the PIM identifies architectural structures and obligations preserved across conforming implementations. These include node roles, topic concepts, information flows, metadata obligations, control-plane responsibilities, release constraints, jurisdictional constraints, evidence requirements, and behavioural obligations.
+Within the FX Demo Reference Architecture, the PIM identifies architectural structures and obligations preserved across conforming implementations. These include node roles, topic concepts, information flows, metadata obligations, control-plane responsibilities, release constraints, jurisdictional constraints, evidence requirements, and behavioral obligations.
-The PIM excludes programming languages, middleware platforms, databases, network transports, vendor products, deployment environments, generated artefact formats, and implementation repository structures. These concerns belong to a Platform Specific Model, implementation guidance, or implementation artefact.
+The PIM excludes programming languages, middleware platforms, databases, network transports, vendor products, deployment environments, generated artifact formats, and implementation repository structures. These concerns belong to a Platform Specific Model, implementation guidance, or implementation artifact.
 ===== Definition =====
@@ Line 23: / Line 23: @@
 A PIM defines architecture-level meaning, structure, and obligations independently of implementation technology.
-In the FX Demo Reference Architecture, DDS domains, DDS topics, IDL definitions, generated types, QoS settings, OpenDDS configuration, adapters, code modules, repository structure, scripts, logs, build artefacts, containers, and deployment files are Platform Specific Model or implementation artefacts, not PIM artefacts.
+In the FX Demo Reference Architecture, DDS domains, DDS topics, IDL definitions, generated types, QoS settings, OpenDDS configuration, adapters, code modules, repository structure, scripts, logs, build artifacts, containers, and deployment files are Platform Specific Model or implementation artifacts, not PIM artifacts.
 ===== Example =====