FpML 5.6 Recommendation #3, 15 July 2015 Errata (Master View)
1 About this document
2 How this document is organized
3 Issues
3.1 Transparency View: fpml-com.xsd -> Commodity Option Strike Price
3.2 Confirmation View: fpml-doc.xsd -> Supervisor Registration
3.3 Pretrade View: fpml-pretrade.xsd -> Credit Limit Response Message
4 Build Number
This document lists the known errata to the FpML 5.6 Recommendation #3, 15 July 2015.
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.6 Recommendation #3, 15 July 2015:
- ID: 1
- 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: 2
- 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: 3
- Date Added: 2014-07-09
- Severity: Major
- Version: FpML-5-5-1-WD-1 (publication date - 2013-01-23) -> Pretrade View
- Location: "http://www.fpml.org/FpML-5/pretrade" - > fpml-pretrade.xsd -> creditLimitResponse
- Description: In the Pretrade View, within the set of Credit limit check messages, the creditLimitResponse message is missing parties and accounts referenced by the onBehalfOf element.
- Disposition: This fix has been implemented in FpML-5-7-5-REC-1 (publication date - 2014-07-08).
- ID: 4
- 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: 5
- 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).
- ID: 6
- Date Added: 2020-07-28
- Severity: Major
- Version: (Confirmation) FpML-5-10-5-REC-1; FpML-5-9-7-REC-2; FpML-5-8-9-REC-2; FpML-5-7-9-REC-4; FpML-5-6-8-REC-3
- Location: "http://www.fpml.org/FpML-5/confirmation" - > fpml-shared.xsd -> RateObservation -> observationWeight
- Description: Made observationWeight optional within RateObservation. Having observationWeight required was making implementations more difficult since in most cases the value is always set to one and it doesn't have to be populated.
- Disposition: This backward compatible change has been implemented in FpML-5-11-9-rec-1 (Confirmation view) and FpML-5-5-11-rec-3 (Confirmation view). However it has not been implemented yet in the versions in between 5.5 and 5.11, creating backward incompatibility for those who want to update their version from FpML-5-5-11-REC-3 to any versions between 5.5 and 5.10. If a firm has the need for this change to be included in one of the intermediate versions, please send an email to info@fpml.org
- ID: 7
- Date Added: 2020-07-28
- Severity: Major
- Version: (Recordkeeping) FpML-5-10-5-REC-1; FpML-5-9-7-REC-2; FpML-5-8-9-REC-2; FpML-5-7-9-REC-4; FpML-5-6-8-REC-3
- Location: http://www.fpml.org/FpML-5/recordkeeping -> fpml-business-events.xsd
- Description: In order to support EMIR REFIT Mandatory Delegated Reporting requirements, the category element was added to the WithdrawalPartyTradeInformation type. The information needed to be made available in the withdrawal message for compliance with regulators, because some Trade Repositories (TRs) use that to determine how to report the withdrawal to the regulators.
- Disposition: This backward compatible change has been implemented in FpML-5-11-9-rec-1 (Recordkeeping view) and FpML-5-5-11-rec-3 (Recordkeeping view). However it has not been implemented yet in the versions in between 5.5 and 5.11. If a firm has the need for this change to be included in one of the intermediate versions, please send an email to info@fpml.org
The current build number for FpML 5.6 Recommendation #3, 15 July 2015. is: 8
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: Wed 07/08/2015 1:28:57.79
