Imported from previous forum
Was wondering if the FIX community thought it a good idea for us to maintain a set of recommended min and max lengths for fields (primarily identifier fields)? Helping to build a new market - I checked around with some folks I knew on their practices - then I realized - why aren’t we maintaining this as part of the spec or even a separate document.
Note the Unified Repository already supports a couple of fields that can be used to specify implementation min and max lengths.
No I am not saying we establish a standard for field lengths - instead I am recommending an industry best practice guide for identifier lengths.
[ original email was from John Prewett - jprewett@lavatrading.com ]
> Was wondering if the FIX community thought it a good idea for us to
maintain a set of recommended min and max lengths for fields (primarily
identifier fields)? Helping to build a new market - I checked around
with some folks I knew on their practices - then I realized - why aren’t
we maintaining this as part of the spec or even a separate document.Note the Unified Repository already supports a couple of fields that can
be used to specify implementation min and max lengths.No I am not saying we establish a standard for field lengths - instead I
am recommending an industry best practice guide for identifier lengths.
I second this suggestion.
I have suffered from execution venues where the maximum length they were willing to accept for a ClOrdID was very small which made my life extremely difficult.
I have suffered from execution venues where the ExecID was absolutely massive which made my life extremely difficult.
For some strange reason I have never suffered from an execution venue where the OrderID was too big. Having said that, I’m sure it will happen tomorrow.
On a more positive note, I’m glad to say that the majority of execution venues act sensibly. Perhaps if there were some suggested recommendations or guidelines (not standards), it could reduce future issues.
JohnP
Was wondering if the FIX community thought it a good idea for us to
maintain a set of recommended min and max lengths for fields (primarily
identifier fields)? Helping to build a new market - I checked around
with some folks I knew on their practices - then I realized - why aren’t
we maintaining this as part of the spec or even a separate document.Note the Unified Repository already supports a couple of fields that can
be used to specify implementation min and max lengths.
Hey Jim,
That’s a great idea. There’s just too much ambiquity with respect to this and it’s certainly caused me plenty of grief over the years.
Cheers,
Russ
[ original email was from Christiaan de Vries - chrisdus@gmail.com ]
> Was wondering if the FIX community thought it a good idea for us to
maintain a set of recommended min and max lengths for fields (primarily
identifier fields)? Helping to build a new market - I checked around
with some folks I knew on their practices - then I realized - why aren’t
we maintaining this as part of the spec or even a separate document.Note the Unified Repository already supports a couple of fields that can
be used to specify implementation min and max lengths.No I am not saying we establish a standard for field lengths - instead I
am recommending an industry best practice guide for identifier lengths.
I think it would be a good idea; I have also seen certain field lengths (ClOrderID in particular) which caused problems in some platforms…
I will volunteer to generate an initial minimally accepted lengths and recommended lengths for identifiers and post.
Was wondering if the FIX community thought it a good idea for us to
maintain a set of recommended min and max lengths for fields (primarily
identifier fields)? Helping to build a new market - I checked around
with some folks I knew on their practices - then I realized - why aren’t
we maintaining this as part of the spec or even a separate document.Note the Unified Repository already supports a couple of fields that can
be used to specify implementation min and max lengths.No I am not saying we establish a standard for field lengths - instead I
am recommending an industry best practice guide for identifier lengths.