I think I discovered an ommission in the TradeCancelled message. The tradeIdentifier and party elements have been assigned inappropriate types (xsd:string) instead of the FpML types. This causes errors while validating a valid TradeCancelled message. Here is the origingal XML code: Am I right or this by design?
My initial feedback on 4.0 LCWD is some of the examples aren’t valid: eqd40_ex06_barrier_knockout_rebate.xml /FpML/trade/equityOption/equityExercise/equityValuation/futuresPriceValuationApp licable This contains an EOL and 9 spaces before the valid value of false. ird_ex02_stub_amort_swap.xml /FpML/trade/swap/swapStream/calculationPeriodDates/firstRegularPeriodStartDate For both swapStreams this contains an EOL and 9 spaces before the valid date. ird_ex05_long_stub_swap.xml /FpML/trade/swap/swapStream/calculationPeriodDates/firstRegularPeriodStartDate Again same problems for both dates. ird_ex06_xccy_swap.xml /FpML/trade/swap/swapStream/cashflows/principalExchange/adjustedPrincipalExchang … Continued
DTCC implemented MessageIDScheme as optional in a product in use by or anticipated to be implemented by many member banks of ISDA. This attribute has been optional in all previous WD versions of the 4.0 FpML that DTCC has studied or implemented. DTCC became aware that the MessageIDScheme was being made mandatory on September 22, … Continued
We propose that the tradeHeader be enhanced to allow institutions to record more information about trades, as follows: – add an optional tradeStatus element, of (the existing)type TradeStatusValue. This will allow an FpML user to record the current status of a trade, e.g. in a trade repository or report. – add an optional “description” element, … Continued
At JPM we have been pulling together some feedback on FpML v4-0. We are still awaiting feedback on many areas, however the first set of feedback is listed in the attached document. This feedback mainly concerns the use of Enumerations and Local Element Definitions.
To better support reporting of mismatch details, we propose adding some detail to the TradeMismatched message. See attached file for details. ——————————————————————————–
SwapsWire have reviewed the credit default swap product definition in FpML 4-0 WD#2 and have identified the following issues which we feel need to be addressed in the next Working Draft. Issues related to documenting trades under the 2003 and 1999 Definitions: 1. Settlement Currency. In the current FpML 4-0 WD#2 Schema the Settlement Currency … Continued
From section 3 onwards (Interest Rate Derivatives) the diagrams are not visbile in the HTML documents. This is linked to the fact that the path to the images is incorrect. Please compare the links to images before section 3 width=”526″ height=”198″> and after section 3 header The path separator is “/” not “”. Regards Tim
As a side effect of some work in the Validation WG we discovered that the following elements in FpML 3.0 do not have consistent names. routingIdScheme routingIdTypeSchemeDefault nationalisationOrInsolvencyOrDelistingScheme nationalisationOrInsolvencySchemeDefault masterAgreementSchemeDefault masterAgreementTypeScheme exchangeIdScheme exchangeIdTypeSchemeDefault The names should be routingIdScheme and routingIdSchemeDefault or routingIdTypeScheme and routingIdTypeSchemeDefault similarly for the others. -daniel
The FPML V4.0 schema can not be bound to Java classes using the JAXB compiler that is part of the Java Web Services Developer Pack 1.2. Naming and other conflicts cause the compilation to fail. An error log is attached. There are three options for correcting the problem: 1. Change the naming conventions used by … Continued