12.4 Topic Participation Rules [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 12.4 Topic Participation Rules ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:12-data-plane-topics:start | Return to Data Plane Topics ]]

The Topic Catalogue should define which [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] publish and subscribe to each [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] Topic. A Node should not publish or subscribe to a Data Plane Topic simply because the implementation can do so. Topic participation should support a defined role in the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].

For each Data Plane Topic, the Topic Catalogue should identify:

  - Publisher Node or Nodes.
  - Subscriber Node or Nodes.
  - Carried Data Structure Definition.
  - Generated type used by the implementation.
  - QoS profile.
  - Expected message direction.
  - Validation or test coverage.
  - Relationship to the FX Demo Logical Profile.

A Node implementation should match the Topic Catalogue. If a Node publishes or subscribes to a Topic not listed in the catalogue, the team should treat that as a Baseline discrepancy. The team should either update the catalogue through review or remove the undocumented participation.

Topic participation rules should support future federation. Later phases may distribute Nodes across organizations, jurisdictions, operational schedules, or policy domains. Phase 0 should therefore avoid assumptions that all Nodes can see all Data Plane Topics unless the profile explicitly allows that visibility.

----

<WRAP centeralign>

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

</WRAP>