13.4 What Domain Profiles Preserve

Go To Top

A Domain Logical Profile preserves the architecture inherited from Part 1 and Part 2.

A Domain Logical Profile preserves:

Part 1: Conceptual definitionsPart 1: Separation of concernsPart 1: Runtime Plane conceptsPart 1: Traceability and Evidence conceptsPart 2: Logical Node conceptsPart 2: Logical Communication ModelPart 2: Logical Information ModelPart 2: Logical Runtime Plane ModelPart 2: Logical Interaction PatternsPart 2: Logical Governance ModelPart 2: Logical Traceability ModelA Domain Logical Profile does not redefine Node, Node Identity, Node Role, Runtime Plane, Communication Endpoint, Data Structure Definition, Data Structure Instance, Evidence, Traceability, Logical Node, Logical Communication Endpoint, Logical Data Structure Definition, Logical Data Structure Instance, or Logical Runtime Plane.

A Domain Logical Profile also preserves platform independence. It does not bind logical elements to DDS, REST, RPC, Protocol Buffers, IDL, Python, Kubernetes, K3S, Docker, RTI Connext DDS, Crucible, or other implementation-specific mechanisms.

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