| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:02-part:13-relationship-to-domain-logical-profiles:13-4-what-domain-profiles-preserve:start [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | fxdemo:02-part:13-relationship-to-domain-logical-profiles:13-4-what-domain-profiles-preserve:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| * Part 2: Logical Traceability Model | * Part 2: Logical Traceability Model |
| |
| A Domain Logical Profile does not redefine [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]], [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]], [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definition]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|Logical Data Structure Instance]], or Logical Runtime Plane. | A Domain Logical Profile does not redefine [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]], [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]], [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_definition|Logical Data Structure Definition]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_structure_instance|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. | 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. |