I’m unfamiliar with the process for raising additions to the FIX specification.
Is there documentation available for how this process starts? @hanno.klein - I know you’ve talked before about the Gap Analysis process - could you advise?
The background to this is to seek standardisation on how to denote Actionable.
Value Meaning
Industry FIX specs seem to differ. In general however there are two levels of support:
- Actionable or not. This is simply a boolean flag - 0/1 or Y/N or T/F. Just harmonising this part would be helpful.
- High/mid/low touch. Some providers go beyond actionable to support different levels of touch. I’m not sure if this is practically useful or not (or whether it’s best stored here) but it’s used.
Perhaps:
0 - Not actionable
1 - Actionable
2 - Actionable - High Touch
3 - Actionable - Mid Touch
4 - Actionable - Low Touch
Tag:
There’s broad current usage of 11001. Ideally this wouldn’t change but I know there are reserved and unreserved ranges.