Releases: FIXTradingCommunity/fix-orchestra
Orchestra v1.0 Technical Standard
Version 1.6.10 conforms to Orchestra version 1.0 Technical Standard
Orchestra v1.0 Draft Standard
fix-orchestra version 1.5 conforms to Orchestra v1.0 Draft Standard
Version 1.0 Release Candidate 5
Release Candidate 5 was approved by the Global Technical Committee on Sept. 19, 2019 for 90 day public review.
Release candidate 4
Release Candidate 4 was approved by the Global Technical Committee on Feb. 21, 2019 for 90 day public review.
Release candidate 3
Release Candidate 3 was approved by the Global Technical Committee on March 8, 2018 for 90 day public review. The key enhancements in Release Candidate 3 were:
- The XML schema was simplified to support a single protocol version per file.
- Scenarios were extended down to the component level as well as to messages. For example, different flavors of the Instrument block can be defined for different asset classes or for a full version versus a brief version.
- Discriminator fields that modify the data domain of another field, such as SecurityIDSource and SecurityID, are now machine readable.
- The schema now supports rendering hints to inform code generators and the like.
- Facilities were added to define stable semantic concepts for which encoding changed between versions of FIX. For example, the Rule80A field in FIX 4.2 was replaced by OrderCapacity and OrderRestrictions fields.
Release candidate 2
Release Candidate 2 was approved by the Global Technical Committee on May 18, 2017 for 90 day public review. The themes for Release Candidate 2 were:
Completion of a DSL grammar for conditional expressions
FIXatdl integration
Session configuration
Release Candidate 1
Release Candidate 1 standardizes the XML schema for FIX Orchestra and FIX Repository 2016 Edition. Approved by GTC December 2016.