[This message was posted by Hanno Klein of Deutsche Börse Systems <[email protected]> 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/ea151690 - PLEASE DO NOT REPLY BY MAIL.]
I agree to omit it whenever you want to create a new entity (order, quote, trade) that has an empty string as one of its attributes. However, I would not omit it in case of a modification in general, especially if it currently has a non-empty value. The proper way to "remove" a previous value is by sending spaces. Vol 4 of the spec says "All of the application-level fields in the original order should be retransmitted with the original values in the Order Cancel/Replace Request, except the fields that are being changed.". If the field could have a non-empty value, the receiver will have to initialize it upon entry if the field is omitted. For modification, the receiver should not interpret an omitted field as a request to leave the field unchanged. Others might interpret it to be a request to "remove" the value. Regards, Hanno. > > Hi all, > > > > Hope you guys are doing great!! > > Could you please anwser my questions below? > > > > Is it valid to have tags with field value as spaces? > > In other words "Is it valid to have a Tag with Field value of spaces ?' > > > > What is a better option, to send tags with field of spaces or not to send > > the entire tag if it has spaces as field value? > > String type tags can have spaces, and it is also ok if they are entirely > composed of spaces. > > > Having said that, a 'blank' value does not convey much. Thus, if the tag in > question is optional, you probably should just omit it. [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.
