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.
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
FpML FX WG is looking for Valid WG advice on how to restrict the values of a new pointsMultiplier element of type ‘PositiveDecimal’ to 10^x (1, 0.1, 0.01, 0.001, 0.0001, etc)
The following validation rules were removed from Confirmation View and will be added to the Reporting View once the validation rules for Reporting View are created: – ref-14, ref-15, ref-16, ref-17 in reconciliation – ref-18 in mktenv – ref- 19, ref-22, ref-23, ref-24, ref-36 – in valuation and riskdef – ref- 20, ref-21 – in … Continued
The 5-x Confirmation View Validation rules ref-10, ref-30, ref-32 need new invalid test cases: the existing invalid cases have the following issues: – invalid-ref-10-01 (currently used in requestValuationReport message) – invalid-ref-30-01 (currently used in valuationDocument message) – invalid-ref-32-01 (currently used in fx product )