Author: Admin

The FpML 5 WD1 release contains a redundant file named tmp0000-5-0.xsd. It is in all three of the releases.

I was exchanging messages with a counterparty and we couldn’t agree on the meaning of an optional element. The element is //element(*, Trade)/documentation. It is an optional element. What does it mean when the field is present or not present? Is it: – Whether it is known or not by the sender? – Whether it … Continued

https://dedicated.fpml.org/svn/fpml/branches/FpML-5-0/src/schema/example-extension.xsd The example extension is invalid XSD. It contradicts: http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#src-import. The imported schema has no namespace.

The FpML standard extensions need converting to FpML 5.0: http://www.fpml.org/documents/extensions.html

https://dedicated.fpml.org/svn/fpml/branches/FpML-5-0/src/schema/fpml-variance-swaps.xsd Contains the following: The problem is the targetNamespace of 4-4. It should be the same as the rest of 5-0.

Add maximumClockVariation to the MessageTransportMode. FpML adopted the Message Transport Mode settings from ISO 20022, and is having them registered at ISO 20022, such as the “Bulk Mode” proposed by Marc Gratacos. ISO 20022 now includes maximumClockVariation in the Message Transport Mode. This is defined as: “Clocks must maintain a maximum (inclusive) variance from UTC … Continued

There is a divergence between logic and computer programming on the definition of the term “precondition”. Please read the Wikipedia entry on a precondition: http://en.wikipedia.org/wiki/Precondition We use the term “precondition” widely in the FpML Validation Rules and it is causing confusion. The programmers interpret the term in its computer programming sense, whereas FpML uses the … Continued

Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: FpML shared-12 (Mandatory) … Continued

Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: calculationAgent shared-10 (Mandatory) … Continued

Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: payerPartyReference shared-5 (Mandatory) … Continued