[This message was posted by Hanno Klein of Deutsche Börse Systems <[email protected]> to the "4.4 Changes" discussion forum at http://fixprotocol.org/discuss/17. You can reply to it on-line at http://fixprotocol.org/discuss/read/430fd981 - PLEASE DO NOT REPLY BY MAIL.]
Your argument is semantically correct but this is one of a few cases where the desire to re-use valid value lists leads to values that do not apply. The choice was made to not maintain two overlapping value lists. Similar issues arise with the re-use of component blocks where its fields do not apply for every occurrence of the component block. The alternative is to create dedicated blocks for each message type. There are also cases where this has been done, i.e. it is a case by case decision to re-use valid values / components or to create new elements that are slightly redundant to existing ones. Your Rules of Engagement should clearly define the set of valid values supported for tag 300 vs. 368. This is where the FIX interface designer needs to show his/her skills :-) Regards, Hanno. > Can someone please say what the difference is supposed to be? > QuoteRejectReason (300) is outside the Quote entry block and so applies to > the whole Mass Quote Message whereas QuoteEntryRejectReason (368) applies at > Quote Entry level? > If thats the case the standard enumerations for 300 do not really make sense > i.e. 7 = InvSpread and 8 = InvPx? [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.
