FpML Version 4.1 Working Draft, 19 Jul 2004 Errata

About this document

This document lists the known errata to the FpML Version 4.1 Second Working Draft.

How this document is organized

Each erratum entry below has the following information:

The following issues are known in the FpML 4.1 Second Working Draft.


initialValue

Description:

The documentation for initialValue (FxLinkedNotional type) is missing in the schema.

Disposition:

This will be corrected in the Last Call Working Draft. The following documentation will be added for this element: “The initial currency amount for the varying notional.”


 instrumentId

Description:

The “Equity” type contains an “instrumentId” element without a type. The “instrumentId” element should be “InstrumentId” type.

Disposition:

This will be corrected in the Last Call Working Draft. The schema and the documentation will be updated.


Strike

Description:

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

Disposition:

This will be corrected in the Last Call Working Draft. The schema and the documentation will be updated.


PrincipalExchange

Description:

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

Disposition:

This will be corrected in the Last Call Working Draft. The schema and the documentation will be updated.


Circular Reference

Description:

There is a circular reference between fpml-doc-4-1.xsd and fpml-posttrade-4-1.xsd. This means that fpml-doc-4-1.xsd is including fpml-posttrade-4-1.xsd and at the same time, fpml-posttrade-4-1.xsd is including fpml-doc-4-1.xsd. XML editors such as TurboXML complain about the existence of circular references, not considering the subschema files as valid.

Disposition:

The inclusion of fpml-posttrade-4-1.xsd within fpml-doc-4-1.xsd will be eliminated.
This will be corrected in the Last Call Working Draft. The schema will be updated.


BusinessCentersOrReference group

Description:

The use of the BusinessCentersOrReference group is not completely consistent. The types BusinessDateRange and BusinessDayAdjustments have an xsd:choice element with minOccurs=”0” containing the group. The xsd:choice is not needed since these two types could just use the model group with minOccurs=”0”.

Disposition:

The xsd:choice will be removed. BusinessDateRange and BusinessDayAdjustments will use the BusinessCentersOrReference group with minOccurs=”0”.
This will be corrected in the Last Call Working Draft. The schema will be updated.


RelativeDateSequence

Description:

The RelativeDateSequence type could use the BusinessCentersOrReference group instead of replicating its content model.

Disposition:

The existing xsd:choice structure will be replaced by the BusinessCenterOrReference group with minOccurs=”0”.
This will be corrected in the Last Call Working Draft. The schema will be updated.


AdditionalPaymentDate

Description:

The type “AdditionalPaymentDate” appears to be identical to “AdjustableOrRelativeDate”.

Disposition:

AdditionalPaymentDate type will be eliminated and replaced by AdjustableOrRelativeDate.
This will be corrected in the Last Call Working Draft. The schema will be updated.


Last updated on: 17 September, 2004