Add a messageAccepted message. messageAccepted is the opposite of messageRejected. For each business message the response is either messageRejected or messageAccepted. A response must be given so that the completion of this exchange is observable. Today when a businessMessage is sent the response can either a messageRejected or nothing. The problem with sending nothing is … Continued
Following publication of the 2006 ISDA Definitions the floating rate index coding scheme needs to be updated to include the new Rate Options defined within this publication. In the attached XML file I’ve merged the new codes in with the existing codes and updated the descriptions to reflect whether the code is defined in either … Continued
Add a mechanism to cancel or request the cancellation of a message. JPMC has a proposal put to the AWG as a result of the pilot work in the CUG. This should liaise with existing SW and DTCC implementations.
3. Issue: identification of ‘primary’ contract-id In fact, based on fpml principles the need for this is irrelevant but incremental version-ids are still needed to ensure that messages are processed in the right order. Action: SWIFT & FpML to provide a clear explanation of these basis principles : can you please provide a proposal as … Continued
What is the intended purpose of, and differences between these types ? As an example, consider AssetReference vs AnyAssetReference AssetReference extends type Empty for some reason, whereas AnyAssetReference extends the abstract type Reference as I would expect All Reference types which extend Empty should be removed
fpml-cd.xsd fpml-option-shared.xsd
Add the time offset to all time and date examples because use of the time offset is recommended best practise in FpML, and we should be setting a good example. Add a rule to the build system to check this.
The existing party ID values in the examples in many cases have some meaning (e.g. partyA). This can create the impression that, for example, the id values in an FpML document should be based on some external identifier. It would be better to have non-meaningful identifiers (e.g. “party1”) to avoid this confusion.
Replace the choices of tradeSide or Party with a mandatory tradeSide. Leave this until version 5 because it is not backwards compatible.
In the schema there is confusion between an instance of a FpML Bus and The FpML Bus specification. For example, under MessageAccepted, we have “Message Accepted notification message for the exclusive use of the Message Bus, used to provide notification that the bus has accepted a message for routing to consumers”. “the Message Bus” should … Continued