In rules FX-39, 39b, 40 and 40b there is reference to valueDate1 and valueDate2 e.g. fx-39 The value of fxSingleLeg/valueDate or the value of both fxSingleLeg/valueDate1 and fxSingleLeg/valueDate2 > tradeHeader/tradeDate. it should say The value of fxSingleLeg/valueDate or the value of both fxSingleLeg/currency1ValueDate and fxSingleLeg/currency2ValueDate > tradeHeader/tradeDate
The default value for the determination method scheme in the 4.6 and 4.7 schemas (I have not checked earlier schemas yet) is ‘http://www.fpml.org/determination-method’. It should be ‘http://www.fpml.org/coding-scheme/determination-method’.
The default URL associated with the ‘tzLocationScheme’ attribute, ‘http://www.fpml.org/coding-scheme/external/tzdatabase’, does not follow the pattern specified in the Architecture specification for external URL’s. A better URL would be something like ‘http://www.fpml.org/ext/timezone-location’. In addition the name of the attribute itself should be changed to ‘timezoneLocationScheme’ rather than use an abbreviation.
The URL pattern ‘http://www.fpml.org/coding-scheme/external/incoterms’ is not consistent with the Architecture specification for external schemes. ‘http://www.fpml.org/ext/incoterms’ would be more consistent with other external schemes such as currency ‘http://www.fpml.org/ext/iso3166’.
The complex type ‘CoalQualityAdjustments’ defines an attribute called ‘commodityCoalProductTypeScheme’ but I suspect this should be ‘commodityCoalQualityAdjustmentsScheme’. It looks as if type ‘CoalProductType’ has been copied and renamed by the changes to the attribute name were missed.
Should be ‘commodityCoalProductSourceScheme’
The changeEvent element in the fpml-contract-notification-4-6 schema is abstract and has a default value set. I don’t think this default is inherited by any substitutes of changeEvent so isn’t the default redundant? Perhaps more importantly is default=”ChangeEvent” just a typo and should it read type=”ChangeEvent” which would make a great deal more sense.
As of March 2009, EMTA-ISDA recommended market practice for BRL CDI swaps is to include the future value notional amount in trade documentation. Jamie Orme at Goldman Sachs brought a proposal to the Interest Rate Derivatives Working Group, to add a Future Value Notional amount in the FpML rates model. The IRD-WG has now agreed … Continued
I can’t find any CNY rate index in floating-rate-index scheme. The 2006 ISDA definition supplement 15 lists two : CNY-Semi-Annual Swap Rate-11:00-BGCANTOR, CNY-Semi-Annual Swap Rate-Reference Banks; however Swapswire has another index called CNY-CFXSREPOFIX01-Reuters.. I don’t even know if it refers to a valid one based on the most current 2006 definitions. May I suggest that … Continued
The IRD rules define two conditions: isFloating and hasInitialStub, but they are not used in the rules themselves. I am looking at FpML 4.6.4 LCWD-1. For example, I suggest to change rule ird-59 from: XPath Description: Context: InterestRateStream (complex type) [exists(resetDates)] id(resetDates/calculationPeriodDatesReference/@href) is calculationPeriodDates to: XPath Description: Context: InterestRateStream (complex type) [isFloating] id(resetDates/calculationPeriodDatesReference/@href) is calculationPeriodDates … Continued