FpML Version 4.0 Recommendation, 2 Apr 2004 Errata

About this document

This document lists the known errata to the FpML Version 4.0 Recommendation.

How this document is organized

Each erratum entry below has the following information:

The following issues are known in the FpML 4.0 recommendation.


cutNameScheme

Description:

The cutNameScheme attribute should have a default value "http://www.fpml.org/spec/2002/cut-name-1-0".

Disposition:

This has been corrected in the Recommendation. The schema has been updated.


sequence

Description:

The sequence element has no type; this causes generation problems. It should be integer.

Disposition:

This has been corrected in the Recommendation. The schema has been updated.


Messaging Section

Description:

There are missing diagrams in the PDF version of FpML 4.0 Recommendation (Messaging section).

Disposition:

This has been corrected in the Recommendation. The fpml-4-0-intro.pdf file has been updated.


initialValue

Description:

The documentation for initialValue is missing in the schema.

Disposition:

This has been corrected in the Recommendation. The schema has been updated.


Strike

Description:

The Strike type contains a mandatory id attribute. The id attribute should be optional.

Disposition:

This has been corrected in the Recommendation. The schema has been updated.

 


PrincipalExchange

Description:

The PrincipalExchange type doesn’t have an optional id attribute. The id attribute should be present.

Disposition:

This has been corrected in the Recommendation. The schema has been updated.

 


Schema html documentation

Description:

The html documentation for the subschemas is not showing the multiplicity of the xsd:choice structures. It is not displaying the names for global elements either.

Disposition:

This has been corrected in the Recommendation. The html files listed above (Location) have been updated.

 


MandatoryEarlyTermination

Description:

The annotation on MandatoryEarlyTermination/calculationAgent is wrong in fpml-ird-4-0.xsd. It said “A pointer style reference to a party identifier defined elsewhere in the document. The party referenced is the ISDA Calculation Agent for the trade. If more than one party is referenced then the parties are assumed to be co-calculation agents, i.e. they have joint responsibility.” But it should say “The ISDA Calculation Agent responsible for performing duties associated with an optional early termination.”

Disposition:

This has been corrected in the Recommendation. The description has been replaced. The fpml-ird-4-0.xsd has been corrected.

 


OptionalEarlyTermination

Description:

The followUpConfirmation element was made optional within the FpML_OptionalEarlyTermination entity in the FpML 2.0 Trial Recommendation dated 30th August 2002 (see http://www.fpml.org/spec/2002/tr-fpml-2-0-2002-08-30) but that change was ever migrated across into FpML 3.0 and hence never made it into FpML 4.0 either.

Disposition:

This has been corrected in the 4.0 Recommendation. The followUpConfirmation element (inside the type OptionalEarlyTermination) is optional now. The fpml-ird-4-0.xsd has been corrected.

 


Stub Field population - examples ird02 and ird05

Description:

When FpML 1.0 was defined for interest rate swaps we defined the rule that firstPaymentDate "must only be included if there is an initial stub". This definition remains in the FpML 4.x standard today for interest rate components.

The rationale was that for vanilla swaps (without stubs) we wanted to make the FpML representation as simple as possible to generate, i.e.
without needing to implement any date logic to calculate payment schedules.

firstPaymentDate is missing from the IRD example 5 (and also example 2).

Disposition:

This has been corrected in the 4.0 Recommendation. The ird_ex02_stub_amort_swap.xml and ird_ex05_long_stub_swap.xml examples have been updated.


fra/indexTenor cardinality is incorrect

Description:

The fra/indexTenor content model cardinality is incorrect in FpML 4.x versus FpML 1.0/2.0. In FpML 1.0/2.0 the fra/indexTenor cardinality is 'one or more' but in FpML 4.x it is 'zero or one'.

The 'one or more' cardinality is the correct one since it's possible to have linear interpolation between 2 different index tenors on a FRA.

Disposition:

This has been corrected in the 4.0 Recommendation. The fpml-ird-4-0.xsd has been updated changing the cardinality of fra/indexTenor to maxOccurs unbounded.


Last updated on: 1 September, 2006