[This message was posted by David Rosenborg of Pantor Engineering AB <[email protected]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/26de9a7c - PLEASE DO NOT REPLY BY MAIL.]
Marc - Of course it can be formalized. Just because it isn't part of the core specification doesn't mean you cannot write a formal specification for it. Constraints and optimization hints of this sort are perfectly suitable for layering using the extensibility mechanism. If this is important and general enough, I think FPL could be the owner of such a specification. Until then, if you've got some ideas about constrains and optimization hints, I suggest you try to formalize them in a proposal and share it with FPL and the forum. Kind regards, /David > > Yes but by doing this, the information will not be normalized. So it > could be MaxLength or MaxSize or StringLength or whatever. If some > attributes are added to the FASt spec then people will be reminded of > specifying them and everybody will use the same unambiguous names. > > Marc [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
