Latest Posts

234: Partial Termination should be separated from Full Termination

By

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.

232: Increases: message exchange is not clear

By

-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?

229: Relax schema validation on certain Swaption elements to support confirmation under ISDA Settlement Matrix and broker confirms

By

Supplement number 20 to the 2000 ISDA Definitions (http://www.isda.org/cgi-bin/_isdadocsdownload/download.asp?DownloadID=163) incorporated the ISDA Settlement Matrix into the 2000 Definitions. This removed the need to specify certain terms within each confirmation since they would be incorporated by virtue of referencing the ISDA Settlement Matrix. As a result it is proposed that certain schema constraints are relaxed to … Continued

228: Message types in the wrong XML Schema

By

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