fxdemo:02-part:13-relationship-to-domain-logical-profiles:13-4-what-domain-profiles-preserve:start

Book Creator
 Add this page to your book
Book Creator
 Remove this page from your book  

 Manage book(0 page(s))
 Help

This is an old revision of the document!

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 definitions
  • Part 1: Separation of concerns
  • Part 1: Runtime Plane concepts
  • Part 1: Traceability and Evidence concepts
  • Part 2: Logical Node concepts
  • Part 2: Logical Communication Model
  • Part 2: Logical Information Model
  • Part 2: Logical Runtime Plane Model
  • Part 2: Logical Interaction Patterns
  • Part 2: Logical Governance Model
  • Part 2: Logical Traceability Model

A 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.

  • fxdemo/02-part/13-relationship-to-domain-logical-profiles/13-4-what-domain-profiles-preserve/start.1783793451.txt.gz
  • Last modified: 2026/07/11 11:10
  • by nick_dido