In fpml-reporting-4-9.xsd RequestPositionReportasOfDate has no type. In fpml-reconciliation-4-9.xsd RequestPortfolioasOfDate has no type. Presume xsd:date is wanted in both cases.
Purely by chance I spotted another example of an untyped element – similar to http://www.fpml.org/issues/view.php?id=1065 In this case additionalCommoditySwapLeg should be of type Leg as an abstract base. Although seen in 4-9 – it goes further back to at least 4-8, possibly 4-7 (not present in 4-6)
Scheme http://www.fpml.org/coding-scheme/collateral-response-reason-code has been renamed to: http://www.fpml.org/coding-scheme/collateral-response-reason In doing so the CanonicalVersionUri has not been correctly edited. http://www.fpml.org/coding-scheme/collateral-response-reason-code-1-0 should now be: http://www.fpml.org/coding-scheme/collateral-response-reason-1-0
In confirmation view the Events.model has an additionalEvent element defined as This in turn is defined as: Is this meant to be a sustitution point? None of the other ‘Events’ are built from any sort of abstract event model.
[Per Last Call Working Draft – July 29, 2011 (build 3)] The ClearingStatus message model is confusing: – is it the status of clearing as a whole or specific item(s) within clearing that is the subject matter? The wording clearingStatusItem suggests the latter; the specification documentation the former. – clearingStatusValue is unusual naming – without … Continued
Element has no Type. Also the samples seem to have no equivalent of td-ex03-dual-currency-deposit-strategy.xml
a)Incorrect versioning of CanonicalUri and CanonicalVersionUri collateral-dispute-resolution-method-code.xml collateral-interest-response-reason-code.xml collateral-margin-call-response-reason-code.xml collateral-response-reason-code.xml collateral-retraction-reason-code.xml collateral-substitution-response-reason-code.xml b) collateral-margin-call-response-reason-code.xml – Whitespaces are not allowed in coding scheme values (found “Valuation Date Mismatch”)
Moving from 4-6-7-rec-1 to 4-7-7-rec-2 the issues were incountered in change management documentation and versioning of schemes inappropriately. Similar issues were previously seen in moving from 4-2 to 4-6 (unreported) – suggesting procedural problems. It is vital that changes between releases are accurately summarised, and versioning correctly applied.
FpML:ElectricityDeliverydelivery has untyped compleyType content: … …. This exists in FpML from at least version 4.6 This needs to be defined in a type, e.g. ElectricityDeliveryDeliveryConditions
The values used in commodity-reference-price-1-0.xml for Codes use a string and not a code value: e.g. “COCOA-GBP-EURONEXT LIFFE” and “BENZENE-CONTRACT BENZENE (FOB USGC/GAL)-GALLON-B&D” Ditto: floating-rate-index-2-1.xml: “CAD-ISDA-Swap Rate” commodity-business-calendar-2-2.xml: “BM&F” – possibly others. Is there a technical justification for departure from a Code? I can see our internal infrastructure needing major surgery to cater for this. … Continued