FpML 5.4 Recommendation#2, 13 August 2013 Errata (Master View)
1 About this document
2 How this document is organized
3 Issues
3.1 fpml-genreric.xsd Non-Backward Compatible change in 5.5 LCWD for the element dayCountFraction in Generic Product
3.2 Recordkeeping View: fpml-com.xsd -> 'SettlementPeriods'
3.3 Transparency View : fpml-ird.xsd - > add 'settlementProvision' --> 'SettlementCurrency' element
3.4 Transparency View: fpml-com.xsd -> Commodity Option Strike Price
3.5 Confirmation View: fpml-doc.xsd -> Supervisor Registration
4 Build Number
This document lists the known errata to the FpML 5.4 Recommendation#2, 13 August 2013.
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.4 Recommendation#2, 13 August 2013:
- ID: 1
- Date Added:2012-04-24 (fpml-5-3-5-TR-1)
- Severity: Major
- Version: FpML-5-5-2-LCWD-1 (published on 2013-02-28)-> All Views
- Location: All Views- > fpml-generic.xsd schema -> Generic Product
- Description:Part 43 requires reporting on both the fixed as well as floating leg for the dayCountFraction element. The Standards committee agreed to the removal with the assumption that it would not break any critical implementation.
- Disposition:This Non-Backward Copatible change will be implemented in FpML-5-5-1-LCWD-1
- ID: 2
- Date Added: 2013-03-25
- Severity: Minor
- Version: FpML-5-3-1-WD-1 (publication date - 2011-09-29) -> Recordkeeping View
- Location: "http://www.fpml.org/FpML-5/recordkeeping" - > fpml-com.xsd -> 'SettlementPeriods'.
- Description: In the Recordkeeping View, the "SettlementPeriods's" "startDate" element's status changed from "optional" to "mandatory". Rationale: Fix - to prevent the submission of the "endDate" without the "startDate". The change was agreed by the Commodity WG and approved by the Standards Committee on March-11-2013.
- Disposition: Non-backward compatible changes in added FpML-5-5-5-REC-1 Recordkeeping View.
- ID: 3
- Date Added:2012-03-11 (fpml-5-5-4-TR-1)
- Severity: Minor
- Version: FpML-5-5-4-TR-1 (published on 2013-03-12)-> Transparency View.
- Location: Transparency View- > fpml-ird.xsd schema -> SettlementProvision
- Description:In-order to determine the notional currency for Non-deliverable IR swaps, settlementCurrency is required to be reported in the transparency View.The Standards committe and Reporting Working Group agreed this was an oversight and should have been added in the previous versions for reporting.
- Disposition:This Non-Backward Compatible change in the Transparency View will be implemented in FpML-5-5-4-TR-1.
- ID: 4
- Date Added: 2014-07-09
- Severity: Major
- Version: FpML-5-3-3-WD-3 (publication date - 2012-02-15) -> Transparency View
- Location: "http://www.fpml.org/FpML-5/transparency" - > fpml-com.xsd -> CommodityFinancialOption.model -> choice of CommodityStrikePrice and CommodityFloatingStrikePrice.model .
- Description: In the Transparency View, fpml-com.xsd -> CommodityOption -> CommodityFinancialOption.model -> CommodityStrikePrice or CommodityFloatingStrikePrice.model is required for CFTC Part 43 reporting.
- Disposition: This Non-Backward compatible change in the Transparency View has been implemented in FpML-5-7-5-REC-1 (publication date - 2014-07-08).
- ID: 5
- Date Added: 2014-07-09
- Severity: Major
- Version: FpML-5-3-4-LCWD-1 (publication date - 2012-03-21) -> Confirmation View
- Location: "http://www.fpml.org/FpML-5/confirmation" - > fpml-doc.xsd -> partyTradeInformation -> reportingRegime -> sequence of name and supervisorRegistration.
- Description: In the Confirmation View, supervisorRegistration is mandatory in error. It should be optional.
- Disposition: This Non-Backward compatible change in the Confirmation View has been implemented in FpML-5-7-5-REC-1 (publication date - 2014-07-08).
- ID: 6
- Date Added: 2019-12-17
- Severity: Major
- Version: FpML-5-10-5-REC-1 (publication date - 2018-02-12) -> All Views (except Legal); FpML-5-9-7-REC-2 (publication date - 2017-03-20) -> All Views (except Legal); FpML-5-8-9-REC-2 (publication date - 2016-07-26) -> All Views (except Pretrade and Legal); FpML-5-7-9-REC-4 (publication date - 2015-07-15) -> All Views (except Pretrade and Legal); FpML-5-6-8-REC-3 (publication date - 2015-07-15) -> All Views (except Pretrade); FpML-5-5-10-REC-3 (publication date - 2015-07-15) -> All Views (except Pretrade); FpML-5-4-6-REC-2 (publication date - 2013-08-13) -> All Views; FpML-5-3-9-REC-2 (publication date - 2012-10-19) -> All Views; FpML-5-2-6-REC-2 (publication date - 2012-02-17) -> All Views; FpML-5-1-9-REC-3 (publication date - 2012-02-17) -> All Views; FpML-5-0-9-REC-2 (publication date - 2010-07-07) -> All Views
- Location: "http://www.fpml.org/FpML-5/confirmation||recordkeeping||pretrade||transparency||reporting" - > fpml-ird.xsd -> Fra
- Description: Made fra/indexTenor maxOccurs equals to 2. This is to solve issue https://www.fpml.org/ticket/1030/. There is no business reason to produce more than two instances of fra/indexTenor. This change was approved by the Standards Committee on 2013 but it was not implemented.
- Disposition: This Non-Backward compatible change has been implemented in FpML-5-11-7-rec-1 (publication date - 2019-12-17) Build 7 (all views except legal).
- ID: 7
- Date Added: 2019-12-17
- Severity: Major
- Version: FpML-5-10-5-REC-1 (publication date - 2018-02-12) -> All Views (except Legal); FpML-5-9-7-REC-2 (publication date - 2017-03-20) -> All Views; FpML-5-8-9-REC-2 (publication date - 2016-07-26) -> All Views; FpML-5-7-9-REC-4 (publication date - 2015-07-15) -> All Views; FpML-5-6-8-REC-3 (publication date - 2015-07-15) -> All Views; FpML-5-5-10-REC-3 (publication date - 2015-07-15) -> All Views; FpML-5-4-6-REC-2 (publication date - 2013-08-13) -> All Views; FpML-5-3-9-REC-2 (publication date - 2012-10-19) -> All Views; FpML-5-2-6-REC-2 (publication date - 2012-02-17) -> All Views; FpML-5-1-9-REC-3 (publication date - 2012-02-17) -> All Views; FpML-5-0-9-REC-2 (publication date - 2010-07-07) -> All Views
- Location: "http://www.fpml.org/FpML-5/confirmation||recordkeeping||pretrade||transparency||reporting" - > fpml-shared.xsd -> Currency; EntityId; EntityName; ExchangeId
- Description: Removed the version string from the external coding scheme URIs, which are implemented as default URIs in the FpML schema (see initial Issue ticket 1220.). The changes are backward-incompatible for those users who are using default URIs and have hard-coded their application to expect these values. The assumption is that not many implementers have constrained themselves in this way. Below is the list of the coding scheme URIs affecred by the change:
- currencyScheme - http://www.fpml.org/coding-scheme/external/iso4217
- entityIdScheme - http://www.fpml.org/coding-scheme/external/entity-id-RED
- entityNameScheme - http://www.fpml.org/coding-scheme/external/entity-name-RED
- exchangeIdScheme - "http://www.fpml.org/coding-scheme/external/exchange-id-MIC
- Disposition: This Non-Backward compatible change has been implemented in FpML-5-11-7-rec-1 (publication date - 2019-12-17) Build 7 (all views).
The current build number for FpML 5.4 Recommendation#2, 13 August 2013. is: 6
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: 09/07/2014 16:55:59,03
