FpML 5.11 Recommendation 17 December 2019 (Master View)
1 About this document
2 How this document is organized
3 Issues
4 Build Number
This document lists the known errata to the FpML 5.11 Recommendation, 17 December 2019.
Each erratum entry below has the following information:
- A unique entry number.
- The date that it was added to the errata page.
- Whether the entry is considered an important error, a minor typographical error, a clarification, or a known problem with the document itself.
- The document version and section referred to.
- The location of the error.
- A description of the problem and correction if applicable.
- When the error is going to be fixed and whether it affects the build number.
The document publishes the build number.
The following issues are known in the FpML 5.11 Recommendation, 17 December 2019:
- ID: 1
- Date Added: 2020-05-04
- Severity: Major
- Version: FpML-5-11-7-REC-1 (publication date - 2019-12-17) -> Recordkeeping and Transparency; FpML-5-11-5-TR-1 (publication date - 2019-10-31) -> Recordkeeping and Transparency; FpML-5-11-4-LCWD-2 (publication date - 2019-08-29) -> Recordkeeping and Transparency; FpML-5-11-3-LCWD-1 (publication date - 2019-08-02) -> Recordkeeping and Transparency; FpML-5-11-2-WD-2 (publication date - 2019-02-13) -> Recordkeeping and Transparency; FpML-5-11-1-WD-1 (publication date - 2018-10-16) -> Recordkeeping and Transparency
- Location: "http://www.fpml.org/FpML-5/recordkeeping||transparency" - > fpml-ird.xsd -> MandatoryEarlyTermination.model
- Description: The mandatoryEarlyTerminationDateTenor and mandatoryEarlyTermination elements are now part of a structure that allows one of the elements or both to be present. This solves the issue 1267 by not requiring the presence of the two elements, which was a non-backward compatible change introduced in version 5.11.
- Disposition: This change has been implemented in FpML-5-11-8-REC-1 (publication date - 2019-12-17) Build 8 (Recordkeeping and Transparency views).
The current build number for FpML 5.11 Recommendation, 17 December 2019. is: 7
Every time there is a change on the schema, validation rules, or examples within a version the actual build number is incremented. If no changes have been made between releases within a version (i.e. from Trial Recommendation to Recommendation) the actual build number stays the same. The build number is published at:
- This errata page
- First page of the specification
- FpML Schema: actualBuild attribute within fpml-doc subschema file.
Last Updated: 06/02/2020 12:33:27,19
