PUBLIC COMMENT PERIOD – Orchestra Version 1.1 RC3

, ,
1

This proposal from the FIX Orchestra Subcommittee provides the details of the Orchestra Technical Standard Version 1.1 Release Candidate 3. It has been approved for public comment by the FIX Global Technical Committee.

Orchestra was conceived as machine readable rules of engagement between counterparties. As such, it is a standard for exchange of metadata about the data elements and behaviour of electronic interfaces (FIX and non-FIX). Orchestra cuts time to on-board counterparties and improves accuracy of implementations. It can also be used to capture interface documentation and generate Rules of Engagement documents for clients.

The documents for the third release candidate of Orchestra Version 1.1 can be found as follows:

Previous documents related to the Orchestra Standard can be found here.

The most important enhancement of Orchestra V1.1 RC3 compared to the previous Release Candidate is a generic framework to support multiple encodings in a single Orchestra XML file. This allows a clean separation of the logical model from encoding-specific information that can now be provided with external schemas outside of the core Orchestra standard.

The proposal is following the technical standards review process described in the document found here. The Orchestra Subcommittee continues to work on the fourth release candidate, intended to be the final one for Orchestra V1.1. There are already a number of issues that have been captured in the GitHub repository of the FIX Trading Community, see here for details.

Please send an email to fix@fixtrading.org if you are interested in contributing to the work.

This release candidate now enters a public comment period in which public review and feedback is encouraged. The public comment period will run for a period of 90 days ending on August 21, 2026.

Please post feedback, comments, and questions as replies to this discussion thread.

1 Like
2

The Technical Proposal has an omission, i.e. GitHub issue #271 removed the numeric identifier of scenarios in favour of just the name.

The Technical Specification reflects the removal with the exception of Chapter 3.11.2 that mentions the attribute scenarioRefID instead of only scenarioRef.

The Orchestra Schema reflects the removal with the exception of the attribute group scenarioRefGrp that still contains the attribute scenarioRef.

These issues will be resolved with the next release candidate (RC4) and captured in its Technical Proposal document.