19.9 Full Multi-Vendor Interoperability [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.

===== 19.9 Full Multi-Vendor Interoperability =====

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

[[fxdemo:05-part:19-phase-0-non-goals:start | Return to Phase 0 Non-Goals ]]

Phase 0 does not require full multi-vendor interoperability unless the applicable checklist instance and acceptance criteria explicitly include it. The architecture may anticipate DDS interoperability across conforming implementations, but Phase 0 may use a single primary DDS product to establish the initial baseline.

If Phase 0 includes more than one DDS product, the team should identify which products it tested, which version ranges it used, which generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] it produced, which runtime combinations it validated, and which interoperability claims the [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] supports.

Later phases may expand interoperability testing across DDS vendors, operating systems, container runtimes, generated bindings, QoS profiles, and deployment environments.

----

<WRAP centeralign>

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

</WRAP>