Author: Admin

Add definition for MarketDisruption in fpml-eq-shared.xsd

Add a definition for the complex type AdjustableDateOrRelativeDateSequence in fpml-eq-shared.xsd

Custodians sometimes receive the same trade twice, once for each trade side. How can a custodian tell who the message was on behalf of? They can’t look at sender as it may be ent by an agent or proy. Is receiving the same message twice a business process bug I suggest adding a party reference … Continued

Provide partial novation in the contract messages. This came out of the SWIFT CUG.

tradeId version should be made mandatory. This issue arose from the SWIFT CUG, and Andrew Parry and Marc Gratacos.

Add support for sending the master agreement to set up the master defaults. This is necessary for people such as custodians who need a copy of the Master Agreement.

provide a message to request a message cancel. the two possible responses are accept and decline. if the request is declined a business level compensating transaction may be required. NB may

Please add the ability to produce warnings to the validation rules. These are not strict constraints, but things that encourage people to comply idiomatically. For example there should be a warning on times and dates without offsets.

Documentation of Party/account reads: “Accounts serviced by this party. These are not accounts where this party is beneficiary, but instead where they are provided and by this party to the beneficiary party.” Is some text missing e.g. between “provided and” and “by this party”?

“Throughout this document we have assumed that message exchanges will be carried by an asynchronous exchange of messages over a guaranteed transport, such is provided by a messaging queuing system. This form of transport is commonly used today in the finance industry (e.g. FIX engines, SwiftNet Interact ‘Store and Forward’, MSMQ, MQSeries, etc.). [ … … Continued