The current content model of FpML uses the same message type for Partial Termination and Full Termination. This is a problem for modeling a business process (choreography) since the outcome of these messages is different. Partial Termination should have its own message type and be called Decrease (?) to be symmetric with Increase.
Both messages have a very similar content model. We should deprecate one of them.
-IncreaseConfirmed- not sure when it should be sent. -No response for RequestIncreaseConfirmation. Shouldn’t IncreaseConfirmed be a response message? -Failure/successes are missing. -At what point do we send the RequestIncreaseConfirmation? What’s the condition that triggers it? If you are just confirming a later version of the trade, do we really need this message pattern?
Add support for eCore annotations
All the message types should be in pre-trade, trade-exec, or post-trade. Recent changes have broken this. Messages have been added in the wrong location: * CancelTradeCashFlows should be in post-trade * TraceCashflowsAsserted should be in post-trade * TradeCashflowsMatchResult should be in post-trade * PositionReport should be in post-trade * RequestValuationReport should be in post-trade * … Continued
Were looking to use the inflation scheme definitions (the ones published in http://www.fpml.org/coding-scheme/inflation-index-description-1-0.xml). We were reconciling these against the index descriptions defined in Section 1.12 of the 2006 ISDA Inflation Derivatives Definitions (see http://www.isda.org/cgi-bin/_isdadocsdownload/download.asp?DownloadID=158) and noticed some anomalies that wed like to get corrected: 1. EUR-EXT-CPI The description (EUR Excluding Tobacco-Non-revised Consumer Price) is missing … Continued
I cannot determine the version of a message schema from a message. In the above example the version attribute says it is “4-2”, but I cannot determine which 4-2 it is. For example it could be any of: 4-2TR 4-2LCWD 4-2WD1 4-2WD2 4-2WD3 This is important as you need to know what to validate against. … Continued
WSDL does not support xsi:type in root node. http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR078
Please merge this XML Spy project file into the trunk: https://dedicated.fpml.org:8443/svn/fpml/branches/annotated/FpML.spp Many of us use XML Spy and this small file makes life much easier for us, making us more productive with FpML.
This, defined at line 1699 of fpml-shared-4-2.xsd should be replaced by specifically types references. Specifies the anchor as an href attribute. The href attribute value is a pointer style reference to the element or component elsewhere in the document where the anchor is defined.