Errata In Repository 2010 Edition (FIX 4.3)

1

Hi,
I would like to report an error in the FIX Repository 2010 Edition.
The root XML element in the file FIX.4.3/Base/Fields.xml has a version="FIX.4.2" tag, but it should be version="FIX.4.3".

- Filippo Costa

2

Looks like the file is actually a FIX 4.2 file, i.e. I do not see tag numbers 447 etc. which were introduced with FIX 4.3. Suggest to use the next higher, supported version which is FIX 4.4. It also includes everything added by FIX 4.3.

If you are only just starting to use repository meta-data, it is advisable to start with the new format FIX Orchestra right away. Repository 2010 is (supported) legacy since the FIX Orchestra V1.0 Technical Standard was published in February 2020 (https://www.fixtrading.org/standards/fix-orchestra/).

3

Thank you for the help @hanno.klein . I would have thought that that the version tag was updated along with the file, but that’s good to know. Also I’m not working directly with FIX 4.3, but I am building some open source stuff and backtesting it for all legacy versions helps me improve the confidence in the correctness of the program.

For now I’m using both the Basic and the Unified 2010 FIX Repository (I still don’t understand why sometimes they differ, e.g. some enums are missing in one but not the other). Using FIX Orchestra seems like a great idea though. Do you know if FIX Orchestra repository is available anywhere or if I have to generate it myself with the reference implementation?

- Filippo Costa

4

Hi Filippo, thank you for that question. You do not have to create it yourself.

The FIX Global Technical Committee (GTC) has just begun to add an Orchestra file to each Extension Pack. An announcement was actually planned for this week. The file name is OrchestraEPxxx.zip with xxx=256 being the latest EP (FIX Extension Packs – FIX Trading Community v2.1). Please also have a look at the GTC blog at The Orchestra has begun to play…. – FIX Trading Community v2.1.

Inconsistencies between the basic and unified repository should be considered as errors. They are different representations of the same meta-data. There may be errors in older versions that have only been corrected with newer versions or Extension Packs.

Regards,
Hanno.