Transition to HTTPS July 19 – Be advised that the FpML website has transitioned to secure HTTP on July 19. URLs are now forwarded to HTTPS automatically. Please make sure you update any internal implementation relying on HTTP URLs accordingly. For further information please email firstname.lastname@example.org
FpML 5.3 Recommendation 2
FpML 5.3 Recommendation 2
October 19, 2012 - Build 9
FpML Transparency View backward compatibility: As described in more detail in the errata sections, different working groups are looking at changes to the Transparency view that might turn out to be not backward compatible with version 5.3. The FpML standards committee decided to move forward with the publication of the Recommendation for version 5.3 which is critical for the implementation of various reporting requirements and accept potential non backward compatible changes in version 5.4. This was preferred over a delay of the 5.3 publication. In anticipation of these non-backwardly compatible changes in 5.4, the implementers of the transparency view, should not assume backward compatibility between minor versions for Transparency view in commodity, equity, and possibly other asset classes (in some of the cases the changes could be to the components that are shared across asset class and may have an effect on other asset classes, e.g. to loosen elements or to make them available when they were not before).
Used for confirming the precise details of contracts and post-trade business events. It is intended to have similar characteristics to the FpML 1-4 product representation, i.e. a very detailed product representation capturing the details needed for a transaction confirmation.
Used for reporting price forming information about executed transactions to the public by reporting parties and execution platforms. It is intended to provide only the key product economics that are appropriate for standardized transactions, and not customizations and detailed information not required for price discovery, for example details of date adjustment rules and the like.
Used for reporting the Primary Economic Terms of derivative transactions to Swaps Data Repositories from entities including market participants, execution platforms, and clearing or confirmation services. This view is intended to have similar characteristics to the FpML "confirmation view" product representation, i.e. a very detailed product representation capturing the details needed for a transaction valuation; it may not include all documentation and legal terms.
Used for reporting trading and business activities and positions (including as part of STP flows), as well as processes such as reconciliation. This view has a moderately loose product representation; it requires key economic information such as the notional, key dates, and parties, but leaves other information optional.