All Projects → FIXTradingCommunity → fix-orchestra-spec

FIXTradingCommunity / fix-orchestra-spec

Licence: other
Technical specification for FIX Orchestra (machine readable rules of engagement)

Programming Languages

HTML
75241 projects

Projects that are alternatives of or similar to fix-orchestra-spec

ccapi
A header-only C++ library for interacting with crypto exchanges. Binding for Python is provided. A spot market making application is also provided as an end-to-end solution for liquidity providers.
Stars: ✭ 227 (+1318.75%)
Mutual labels:  fixprotocol
fix-decoder
Unravels FIX messages into human readable tables
Stars: ✭ 71 (+343.75%)
Mutual labels:  fixprotocol
ferrumfix
Financial Information eXchange protocol implemented in Rust
Stars: ✭ 192 (+1100%)
Mutual labels:  fixprotocol
FsFIX
an F# FIX engine
Stars: ✭ 22 (+37.5%)
Mutual labels:  fixprotocol
fix2json
A command-line utility to present FIX protocol messages as JSON or YAML
Stars: ✭ 44 (+175%)
Mutual labels:  fixprotocol
finspec-spec
Multi-protocol, machine-readable specifications for financial services
Stars: ✭ 18 (+12.5%)
Mutual labels:  fixprotocol
fixp-specification
FIXP - FIX performance session layer specification
Stars: ✭ 40 (+150%)
Mutual labels:  fixprotocol
clearth
Test automation tool for Clearing, Settlement and Back-Office Systems
Stars: ✭ 26 (+62.5%)
Mutual labels:  fixprotocol
fix-json-encoding-spec
Technical specification for mapping FIX to JSON encoding
Stars: ✭ 21 (+31.25%)
Mutual labels:  fixprotocol
Stocksharp
Algorithmic trading and quantitative trading open source platform to develop trading robots (stock markets, forex, crypto, bitcoins, and options).
Stars: ✭ 4,601 (+28656.25%)
Mutual labels:  fixprotocol
coinbase-fix-example
Simple example application for Coinbase Pro FIX API
Stars: ✭ 42 (+162.5%)
Mutual labels:  fixprotocol

FIX Orchestra Technical Specification

This project contains specifications for FIX Orchestra version 1.0. The purpose of FIX Orchestra is to support the exchange of machine readable rules of engagement between FIX counterparties.

Additional resources and sample code is available in project fix-orchestra.

Planned Lifecycle

The planned lifecycle of this project is to roll out new features in a series of release candidates. After each release candidate is approved, it will be exposed to public review. When a version is considered complete, the last release candidate will be promoted to Draft Standard. A Draft Standard may be promoted to final Technical Standard when at least two interoperable implementations are demonstrated.

Participation

Issues may be entered here in GitHub or in a discussion forum on the FIX Trading Community site. In GitHub, anyone may enter issues or pull requests for the next release candidate.

Standards Versions

Version 1.1 Release Candidate 1

Version 1.1 RC1 is currently work in progress. Release Candidates and Draft Standard no longer use their own folders. Instead, there is only one folder per minor version of FIX Orchestra and GitHub tags will be used to identify them. Public review comments continue to be applied to the next Release Candidate or Draft Standard, i.e. do not require to make changes to the previous Release Candidate.

Version 1.0 Technical Standard

Draft Standard was promoted to Technical Standard with minor corrections on February 18, 2021.

Version 1.0 Draft Standard

Release candidate 5 was promoted to Draft Standard with minor enhancements and corrections on February 20, 2020. A draft standard must have at least two interoperable implementations in order to be promoted to a final Technical 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. The key enhancements in Release Candidate 5 were:

  • Security keys for sessions
  • Support for XML Inclusions (XInclude)
  • Syntax for mutually exclusive message elements

Version 1.0 Release Candidate 4

Release Candidate 4 was approved by the Global Technical Committee on Feb. 21, 2019 for 90 day public review. The key enhancements in Release Candidate 4 were:

  • Scenarios were extended to fields and code sets.
  • Components and repeating groups were separated in the XML schema.
  • Identifiers were normalized and simplified.

Version 1.0 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.

Version 1.0 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

Version 1.0 Release Candidate 1

Version 1.0 RC1 standardized the XML schema for FIX Orchestra and FIX Repository 2016 Edition. Release Candidate 1 was approved by the Global Technical Committee on Dec. 15, 2016 for 90 day public review.

License

FIX Orchestra specifications are © Copyright 2016-2021 FIX Protocol Ltd.

Creative Commons License
FIX Orchestra Technical Specification by FIX Protocol Ltd. is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License.
Based on a work at https://github.com/FIXTradingCommunity/fix-orchestra-spec.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].