Source of machine readable input for "FIX Latest" specs?

Hallo everyone,

I’m looking for the input files used to generate the specifications found on https://www.fixtrading.org/online-specification - in particular for “Order State Changes”. I presume it is some sort of parseable format to support different renderings.
I know the message definition is available in XML format but I’m more interested in the appendix doc(s). I checked with fixtrading . org and on github so far.

Thx & best regards

Frank

@ratzlow what is the use case behind your question? Is it only about the tables in the order state changes document? The Orchestra XML repository is the machine-readable representation of FIX Latest. They reflect the appendices that are part of the downloadable PDF docs and also available online (e.g. https://www.fixtrading.org/online-specification/trade-appendix/).

The remainder of the specs is not part of Orchestra XML and is publicly available online and as downloadable PDF docs via the link you show above. The direct link to the online version of the order state changes document is https://www.fixtrading.org/online-specification/order-state-changes/.

The specs are licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License. The idea is that users can provide URLs into the master version of the online spec on the FIX website from within their (online) documentation. That ensures that the latest normative text is being provided as it is being updated with every Extension Pack.

Hi Hanno,

I was curious whether the table scenarios were formulated as orchestra markup, so they could be used and extended for some kind of interface tests. Thx a lot for the clarification.

BR

Frank

They are currently only stored as html that is mixed with surrounding markdown. The tables have many columns and are not well suited for markdown. They are not part of the Orchestra XML file but they could be defined in there as Orchestra scenarios and workflows. They could be part of the Orchestrations repository on GitHub and it would be great if there is someone out there that would volunteer to create them. :grinning:

I like this idea. Let me play a bit with this stuff.

(+ Actually I was wandering whether the standardisation org also envisions something like a TCK, with let’s say different “compliance levels”. Anyway, thx for your hints, will see what I can do.)