[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/83c67b94 - PLEASE DO NOT REPLY BY MAIL.]
Two questions on naming conventions: Message PartyDetailsListReport provides a list of parties <PartyListGrp> with detailed information for each party <PartyDetail> and its relationships <RelatedPartyGrp>. Fragmentation is supported by a field called TotNoPartyList. The number of parties described in <PartyListGrp> is defined by the field NoPartyList. I find the usage of the term "List" confusing as the message does not provide a number of party lists but simply a number of parties. First question is if we can omit the term "List" as follows: TotNoPartyList --> TotNoParties <PartyListGrp> --> <PartiesGrp> NoPartyList --> NoParties Second question is related to the message name which are quite long. Similar messages for securities do not have the term "Detail" in their name, i.e. SecurityListRequest and SecurityList (does not even have "Report"). I find it obvious that a message contains details about the entity it describes. On the other hand, the term "List" is important here as it can be more than a single party per message. Second question is if we can omit the term "Detail" as follows: PartyDetailsListRequest --> PartyListRequest PartyDetailsListReport --> PartyListReport Regards, Hanno. [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 -~----------~----~----~----~------~----~------~--~---
