Latest Posts

The Business Rule Validation tool is out of date. Need to update the tool to be able to check FpML examples. FpML publishing examples need to be correct according to the FpML validation rules.

fpml-ird-4-x.xsd There is a typo in the annotation of element settlementCurrency, child of NonDeliverableSettlement. The word “in” appears twice, when only one instance is required … “The currency in which the swap stream is denominated in” should be: “The currency which the swap stream is denominated in” or: “The currency in which the swap stream … Continued

FpML Architecture 3.0, Section 2.3.9.3 Ordering within Repetitions In the opening sentence the word “of” is superfluous (and incorrect): “Many of the elements that comprise *of* the FpML schema are allowed to repeat (i.e. their ‘maxOccurs’ attribute has a value greater than one or is ‘unbound’).” should read: “Many of the elements that comprise … … Continued

Please add support for rebate features to FX Options.

Please add support for the Rebate Notification business process as a result of FX Rebate Options touching and triggering a Rebate. The business process involves advising on the touch and the rebate payment.

The dates relating to valuation are adjusted by exchange holiday calendars, rather than currency holiday calendars, so in some examples (e.g. eqs-ex16-forward-starting-post-european-interdealer-share-swap-short-form.xml) we use those values (GER – corresponds to the German XETRA) instead of the values defined in the businessCenterScheme, but using businessCenters container. The question is – should the businessCenterScheme codes contain exchanges … Continued

LCH reported an issue with 5.x (Reporting vew) “TimeDimension” complex type. It restricts structure allowing to use either date or tenor but not both which is allowed in 4.x.

When Andrew J raised the related issue about time zones, Tony Coates noted that perhaps the timezone should not be indicated in a date when also businessCenter is present.

shared-27 currently reads as follows: Context: Document (complex type) All timezones must be the same. +00:00, -00:00, and Z are considered equivalent. Comment: This rule ensures that date and datetime comparisons behave as expected because they’re expressed in the same timezone. NB That the XSD specification uses the term “timezone”, but that they are not … Continued

FpML supports Basket Amount, yet we can’t find this in the ISDA 2002 Equity Master Definitions, nor in the ISDA Confirmations templates. We have never seen this in ISDA documentation or otherwise, we weight on basket percentage ( relative weight ) or open units ( absolute weight ), both of which are stable expression. We … Continued