FpML 5-3 transparency View - CHANGES IN THIS VERSION

15 CHANGES IN THIS VERSION

15.1 Changes compared to FpML 5.3 WD #1

In multiple views:
- Added support for modeling people (such as employees) and business units within parties, and added detail to the partyTradeInformation block to allow their role within a transaction to be recorded. (This is still in progress and may be adjusted in a future draft.)
- Added several fields to the partyTradeInformation to support SDR reporting (these are mostly needed for recordkeeping view, but are available in other views as well. Fields include "collateralized" indicator, a "boardOfDirectorsApproval", field, and a verificationPurpose field. Also renamed confirmationType to confirmationPurpose. (This is still in progress and may be adjusted in a future draft.)
- Adjusted the "attachment" element in "documentation" to support multiple attachements per trade.
Transparency:
- In partyTradeInformation, enabled generic timestamps and added timestamps related to orders
The following issues have been resolved:

View PDF for details on schema changes

View SCHEME DEFINITIONS for details on coding schemes changes

15.2 Changes compared to FpML 5.2 Trial Recommendation

Message Framework:
- Added a requestRetransmission message to allow a part of a portfolio or a report to be requested again.
- Made the upper bound on the "onBehalfOf" field be 4, to support reporting on behalf of all parties in a novation event.
- Added an optional "parentCorrelationId" to allow the parent process of a nested process to be recorded.
- Enhanced the requestEventStatus message to support additional event identifiers, and to allow the business process to be specified.
- Added support for modeling people (such as employees) and business units within parties, and added detail to the partyTradeInformation block to allow their role within a transaction to be recorded. (This is still in progress and may be adjusted in a future draft.)
- Added several fields to the partyTradeInformation to support SDR reporting (these are mostly needed for recordkeeping view, but are available in other views as well. Fields include "collateralized" indicator, a "boardOfDirectorsApproval", field, and a verificationPurpose field. Also renamed confirmationType to confirmationPurpose. (This is still in progress and may be adjusted in a future draft.)
- Adjusted the "attachment" element in "documentation" to support multiple attachements per trade.
Transparency:
- Restored transparency view, which had been removed from the Trial Recommendation of 5.2 for scheduling reasons
- Added support for basis commodity swaps.
- For equity derivatives, replaced long-form product element names with short forms.
- In partyTradeInformation, enabled generic timestamps and added timestamps related to orders

15.3 Incompatible changes compared to FpML 5.2

None.

15.4 Changes compared to FpML 5.1 Recommendation (build 7)

Reporting and Business Process:
- Added two new views, "Transparency" and "Recordkeeping", to support public and nonpublic reporting into swaps data repositories (SDRs).
- Trade and Termination Events
  - Added the optional "originatingEvent" element to generic messages when the event is a new Trade. This element allows the sender to provide additional explanation as to why the new trade was created. Also added a corresponding coding scheme.
  - Added the optional "terminatingEvent" element to generic messages when the event is a Termination. This element allows the sender to provide additional explanation as to why the new trade was terminated. Also added a corresponding coding scheme.
- Consent Negotiation
  - Added the optional "requestedAction" element to indicate why consent is being sought, and a corresponding coding scheme.
  - Added documentation to describe how the consent negotiation messages can be used to request consent for clearing a trade.
- Maturity Notification
  - Added a new message that can report on trades that have matured. This can be used for options that have expired or any trade that has passed its final event and can be removed from the active portfolio.
- Message Framework:
  - Correlation IDs and sequence numbers have been made optional for initial requests and notifications.
  - Increased the maximum multiplicity of correlation IDs to 2 to allow services to return their own correlation ID to correspond to the submitter's correlation ID.
  - Allowed exception messages to include the original message as unvalidated XML.
  - Allowed acknowledgement messages to include the original message as unvalidated XML.
  - Added enhancements to better report trade amalgamation (netting, compression).
  - Added enhancements to handle portfolio requests (portfolio-type business processes).

15.5 Incompatible changes compared to FpML 5.1

None.