Differences
This shows you the differences between two versions of the page.
| fxdemo:02-part:15-logical-rules-and-constraints:15-5-logical-runtime-planes-remain-distinct-from-implementation-groupings:start [2026/07/03 14:07] – created owen | fxdemo:02-part:15-logical-rules-and-constraints:15-5-logical-runtime-planes-remain-distinct-from-implementation-groupings:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| A Logical Runtime Plane classifies logical interactions by architectural purpose. It does not represent a DDS Domain, DDS partition, DDS Topic namespace, REST resource group, RPC service group, message-bus namespace, Kubernetes namespace, network segment, security zone, deployment environment, | A Logical Runtime Plane classifies logical interactions by architectural purpose. It does not represent a DDS Domain, DDS partition, DDS Topic namespace, REST resource group, RPC service group, message-bus namespace, Kubernetes namespace, network segment, security zone, deployment environment, | ||
| - | Implementation and deployment profiles select grouping mechanisms that help realise | + | Implementation and deployment profiles select grouping mechanisms that help realize |
| - | Logical Runtime Plane separation continues to apply when a single implementation mechanism carries interactions from several planes, or when several implementation mechanisms | + | Logical Runtime Plane separation continues to apply when a single implementation mechanism carries interactions from several planes, or when several implementation mechanisms |
| ---- | ---- | ||