Latest Posts

The cardinality of tradeSide under trade ( //trade/tradeSide), should be “0..2”. Currently the cardinality is 0 to unlimited.

MessageHeader.partyMessageInformation (fpml-msg-4-2.xsd) is never accessible because all of the types which restrict this base class don’t restate it! partyMessageInformation element needs to be added to the following types: NotificationMessageHeader RequestMessageHeader ResponseMessageHeader

DSWG requests support for Non-deliverable currencies at the Swaption product. The CashSettlement type has been extended to allow reporting of settlement rate options and fixing dates for non-deliverable currencies. These are represented using the previously defined SettlementRateOption type and the FpML AdjustableDates type.

We are actually working to implement data exchange with external entities and suppose to use FpML as standard to such. In fact, there is no schema implemented to Futures Operations and same for NDF (Non-deliverable Futures). Basic fields necessary to implement these operations are: – legal entity id – client id – broker id – … Continued

The public website only hosts the latest version of each release. I have a client with whom we standardized on FpML 4.1 TR. This version is no longer hosted. Please could you retain WD, CR, TR, and REC versions. i.e. Please retain old versions of releases.

I request a unique build number. At the moment there is no unique identifier (such as a build number) to identify each release. For example FpML 4.2 WD#2 went through 3 releases due to errata. It is currently impossible to distinguish each version of the errata. This caused me problems with a vendor. The vendor … Continued

Please provide support for Credit Spread Options in FpML.

The tradeSide elements that are party references must refer to a party id. This rule is missing from the shared rules. Please add the missing rule for tradeSide.

The existing constraints are ignoring the partyTradeSide feature added in FpML 4.2. A buyerPartyReference and a sellerPartyReference may point either to a tradeSide or a Party. This is the decision of the MWG. However the schema constraint rules say it must always be a party. The incorrect rules are shared-12 and shared-13. The correct rule … Continued

Changes to the Validation rules are missing from FpML 4.2 WD#2 Within the document section: http://www.fpml.org/spec/2005/wd-fpml-4-2-2005-10-12/html/fpml-4-2-intro.html#s11 I would expect to see listed the changes made to the static schema constraints. A good example is the addition of the pre-condition that currencies must be equal.