Latest Posts

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

file: fpml-asset-4-2.xsd UnderlyingAsset is now correctly an abstract type however an element uses this type directly which results in the following error when validating an XML instance document which uses ConvertibleBond [Error] cboption.xml:145:23: cvc-type.2: The type definition cannot be abstract for element underlyingEquity. cboption.xml: 871 ms (99 elems, 37 attrs, 0 spaces, 1099 chars)

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

We form a Leg Modelling Task Force, which will take the same approach to reviewing and improving Leg Modelling that the Security Option Task Force has taken with Options JPM supports this ( AJ, AP, MR, HMcA )

Ordering is already present in the XML instance document, which should be made clear in the Architecture document, and the schema fpml-shared.xsd(611):

“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

A model group (FloatingRateIndex.model) would keep consistency between types using the floatingRateIndex and the indexTenor elements (floatingRateCalculation, Fra,…) and it would facilitate extensions.