Latest Posts

A value of “ISDA2006Inflation” is required to refer to the “2006 ISDA Inflation Derivatives Definitions”

Very odd content model with nested choice, as we wrote this it had only the inner choice group as per Loan, which appears correct tag: FpML-4-3-5-WD-4 file: fpml-asset.xsd Applicable to the case of default swaps on MBS terms. For specifying the insurer name, when applicable (when the element is not present, it signifies that the … Continued

It is available in a branch and it should be published in the new extensions page http://www.fpml.org/documents/extensions.html

We would need a tool in the build system to check whether and where circular includes are present at the Schemata. Circular includes are explicitly allowed in the W3C Schema 1.0 spec but they cause many problems to tools.

XML Spy is complianing that dec:deprecatedReason is invalid, and I then had to comment out the Forward value to make the schema XML valid. I do not know at this point if it is an issue with the tool, and would be interested in your view on this. DEPRECATED value which will be removed in … Continued

All, We have a simple type that we use for exercise times called HourMinuteTime A type defining a time specified in hh:mm:ss format where the second component must be ’00’, e.g. 11am would be represented as 11:00:00. Shouldnt this type allow the support for time offsets (i.e. +00:00)?

The validation rules bp-1 is missing examples. Please add at least one valid and one invalid example.

Andrew P Parry/JPMCHASE 17/07/2007 16:40 To Matthew D Rawlings/JPMCHASE@JPMCHASE cc MGratacos@isda.org Subject Another Tool, Resolution Re: Dependency Visualisation Matthew This tool which generates Python data structures http://www.rexx.com/~dkuhlman/generateDS.html works fine when you do not have circular includes, but breaks on the latest FpML-4-3-4-WD-2 I want to this to be fixed, and make sure that it goes … Continued

Adding a dec namespace declaration on the enumeration value “Forward” in the “OptionTypeEnum” is invalid because it contradicts the following XSD rule: http://www.w3.org/TR/xmlschema-1/#coss-particle The solution is to move all the “dec” namespace declarations to the xsd:schema element of each FpML document.

the FpML annotations are prefixed with “dec”. Everything in the schema is declared, so as a prefix it is not distinctive. Ecore traditionally uses the prefix “ecore”. FpML should follow suit and use the prefix “fpml” in the schema.