[This message was posted by Christiaan de Vries of Baxter-FX <chris...@gmail.com> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/795f0c98 - PLEASE DO NOT REPLY BY MAIL.]
> 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.. [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to fix-proto...@googlegroups.com. To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
