Author: apparry

Elsewhere productType is minOccurs=”0″ maxOccurs=”unbounded”, such as in complex type product Please use model group to ensure consistent content

Version Identification is required in order to support unambiguous and correct automation of business processes Please review file “fpml-doc-4-2.xsd” in branch “choreography”

At present there is a great deal of inconsistent token usage, which is most evident in the area of token usage to identify trades Marc Gratacos and Andrew Jacobs are aware of this issue, and are working on it, but this needs to be brought to a rapid conclusion in order that the user community … Continued

Schema commonly uses xsd:restriction for “no-op” where content is restricted out, and them restored, providing no value to the content model produced, and causing additional difficulty for software tools and our user community Please review the file “fpml-msg-4-2.xsd” in the “choreography” branch on the FpML Subversion Server where I have derived the current content model … Continued

Duplication of content model

Duplication of content model

Incorrect content model between long form “object” and short form “identification of object” Example: TradeCancelled ( PartyTradeIdentifier vs TradeIdentifier ) which results in linkId being present in long form, but not in short form #1 Long Form “Full Trade” TradeCancelled.Trade.TradeHeader.PartyTradeIdentifier #2 Short Form “Identification of Trade” TradeCancelled.TradeIdentifier

Addition “LUN” to RollConventionEnum is required to support Lunar Roll Convention What we call “LUN” follows the convention for the MXN TIIE. Here is a definition for TIIE: TIIE (Tasa de Interes Interbancario de Equilibrio) is the benchmark for the Mexican interbank money market introduced by the Bank of Mexico in April 1997. The TIIE … Continued

Current content model is odd, in that productId ( identification ) is unbounded, whereas productType ( classification ) is not I request that productType should be unbounded in common with productId

No status is provided, either through other distinct message types extending this type, or through status being provided in the message content model