XML Schema "fpml-confirmation-processes-5-11.xsd"
Target Namespace:
Version:
$Revision: 13737 $
Defined Components:
elements (53 global + 69 local), complexTypes (36), element groups (2)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Includes Schemas (1):
Included in Schemas (1):
Annotation
Confirmation messages.
All Element Summary
Event (trade post-trade event) asserted by the "other side's" party.
Type:
Content:
complex, 16 elements
Defined:
locally within ConfirmationStatus complexType; see XML source
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 2 elements
Defined:
locally within AllocationApproved complexType; see XML source
Type:
Content:
complex, 2 elements
Defined:
locally within AllocationRefused complexType; see XML source
Type:
Content:
complex, 2 elements
Defined:
locally within RequestAllocation complexType; see XML source
Type:
Content:
complex, 2 elements
Defined:
amendment (defined in ExecutionNotification complexType)
Type:
Content:
complex, 10 elements
Defined:
locally within ExecutionNotification complexType; see XML source
An identifer for a specific appoval, to allow the approval to be identified and tracked.
Type:
Content:
simple, 2 attributes
Defined:
locally within ConsentGranted complexType; see XML source
All of the approvals for a specific trade.
Type:
Content:
complex, 1 element
Defined:
Type:
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
The full name or identifiying ID of the relevant approver.
Type:
Content:
simple, 1 attribute
Defined:
locally within ConsentGranted complexType; see XML source
The full name or identifiying ID of the relevant approver.
Type:
Content:
simple, 1 attribute
Defined:
locally within ConsentRefused complexType; see XML source
The full name or identifiying ID of the relevant approver.
Type:
Content:
simple, 1 attribute
Defined:
locally within RequestConsent complexType; see XML source
The full name or identifiying ID of the relevant approver.
Type:
Content:
simple, 1 attribute
Defined:
A pointer style reference to a party defined elsewhere in the document.
Type:
Content:
empty, 1 attribute
Defined:
locally within ConsentGranted complexType; see XML source
A pointer style reference to a party defined elsewhere in the document.
Type:
Content:
empty, 1 attribute
Defined:
locally within ConsentRefused complexType; see XML source
A pointer style reference to a party defined elsewhere in the document.
Type:
Content:
empty, 1 attribute
Defined:
locally within RequestConsent complexType; see XML source
A pointer style reference to a party defined elsewhere in the document.
Type:
Content:
empty, 1 attribute
Defined:
Event (trade or post-trade event) asserted by one of the parties.
Type:
Content:
complex, 16 elements
Defined:
locally within ConfirmationStatus complexType; see XML source
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally within AllocationApproved complexType; see XML source
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally within AllocationRefused complexType; see XML source
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally within RequestAllocation complexType; see XML source
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
Describes the details of the change.
Type:
Content:
complex, 6 elements
Defined:
locally within TradeChangeAdvice complexType; see XML source
Describes the details of the change being retracted.
Type:
Content:
complex, 6 elements
Defined:
The trades or events generated by the clearing service as a result of clearing.
Type:
Content:
complex, 4 elements
Defined:
locally within Clearing complexType; see XML source
Type:
Content:
complex, 2 elements
Defined:
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 14 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
Describes the status of the clearing process relating to the identified trade.
Type:
Content:
complex, 8 elements
Defined:
locally within ClearingStatus complexType; see XML source
Allocation details
Type:
Content:
complex, 3 elements
Defined:
Type:
Content:
complex, 3 attributes, 6 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
The party paying the margin / issuing the allocation request.
Type:
Content:
empty, 1 attribute
Defined:
A business acknowledgement message to indicate that the previously sent message was sucessfully processed.
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
The confirmationAgreed message is sent when the matching process returns a proposed match (trade or event) and the Confirmation Requester agrees with it.
Type:
Content:
complex, 3 attributes, 24 elements
Defined:
globally; see XML source
Used:
never
The confirmationDisputed message is sent when the matching process returns a proposed match (trade or event) and the Confirmation Requester disputes it.
Type:
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Used:
never
A message sent to inform another system that some exception has been detected.
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
The confirmationStatus message provides the status of the matching process: matched, mismatched, unmatched, or alleged.
Type:
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 27 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 27 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 elements
Defined:
locally within ClearingConfirmed complexType; see XML source
Type:
Content:
complex, 3 elements
Defined:
locally within ConsentGranted complexType; see XML source
Type:
Content:
complex, 3 elements
Defined:
locally within ConsentRefused complexType; see XML source
A structure describing a declear event.
Type:
Content:
complex, 3 elements
Defined:
A structure describing a declear event.
Type:
Content:
complex, 3 elements
Defined:
locally within RequestClearing complexType; see XML source
A structure describing a declear event.
Type:
Content:
complex, 3 elements
Defined:
A structure describing a declear event.
Type:
Content:
complex, 3 elements
Defined:
locally within RequestConsent complexType; see XML source
A structure describing a declear event.
Type:
Content:
complex, 3 elements
Defined:
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 28 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 18 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
A structure describing an option exercise event.
Type:
Content:
complex, 24 elements
Defined:
locally within ExecutionRetracted complexType; see XML source
A structure describing an option exercise event.
Type:
Content:
complex, 24 elements
Defined:
locally within RequestConfirmation complexType; see XML source
A structure describing an option exercise event.
Type:
Content:
complex, 24 elements
Defined:
locally within ConfirmationRetracted complexType; see XML source
A structure describing an option exercise event.
Type:
Content:
complex, 24 elements
Defined:
locally within RequestExecution complexType; see XML source
A structure describing an option exercise event.
Type:
Content:
complex, 24 elements
Defined:
Type:
Content:
complex, 3 attributes, 18 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 elements
Defined:
locally within MaturityNotification complexType; see XML source
Type:
Content:
complex, elem. wildcard
Defined:
Details of the payments, like amount breakdowns, settlement information.
Type:
Content:
complex, 3 elements
Defined:
locally within ExecutionAdvice complexType; see XML source
Details of the payments, like amount breakdowns, settlement information.
Type:
Content:
complex, 3 elements
Defined:
Details of the payments, like amount breakdowns, settlement information.
Type:
Content:
complex, 3 elements
Defined:
locally within TradeChangeAdvice complexType; see XML source
Details of the payments, like amount breakdowns, settlement information.
Type:
Content:
complex, 3 elements
Defined:
Type:
Content:
simple, 1 attribute
Defined:
locally within ExecutionAdvice complexType; see XML source
"Other side's" event (trade or post-trade event) that meets the minimimum matching criteria and is proposed as match to the event that is being asserted.
Type:
Content:
complex, 19 elements
Defined:
locally within ConfirmationStatus complexType; see XML source
Type:
Content:
complex, 5 elements
Defined:
locally within AllocationRefused complexType; see XML source
Type:
Content:
complex, 5 elements
Defined:
locally within ClearingRefused complexType; see XML source
Type:
Content:
complex, 5 elements
Defined:
locally within ConfirmationDisputed complexType; see XML source
Type:
Content:
complex, 5 elements
Defined:
locally within ConsentRefused complexType; see XML source
Identifies a related party performing a role within the transaction.
Type:
Content:
complex, 4 elements
Defined:
locally within RequestAllocation complexType; see XML source
Type:
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 16 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Used:
never
The confirmation process starts with the requestConfirmation message.
Type:
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Used:
never
A requestConfirmation message may be cancelled using the requestConfirmationRetracted message.
Type:
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 29 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 24 elements
Defined:
globally; see XML source
Used:
never
The type of change requested for the collateral allocation.
Type:
Content:
simple, 1 attribute
Defined:
The reason the consent was requested.
Type:
Content:
simple, 1 attribute
Defined:
locally within RequestConsent complexType; see XML source
Type:
Content:
complex, 3 attributes, 14 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
The name of the service to which the message applies
Type:
Content:
simple
Defined:
Defines the confirmation status of a trade or post-trade event (e.g.
Type:
Content:
simple, 1 attribute
Defined:
locally within ConfirmationStatus complexType; see XML source
The original trade or event submitted to the clearing service.
Type:
Content:
complex, 4 elements
Defined:
locally within Clearing complexType; see XML source
This may be used to describe why a trade was terminated.
Type:
Content:
simple, 1 attribute
Defined:
Type:
Content:
complex, 16 elements
Defined:
Type:
Content:
complex, 1 attribute, 14 elements
Defined:
Type:
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
The qualified identifiers of the subject trade.
Type:
Content:
complex, 1 attribute, 13 elements
Defined:
Type:
Content:
complex, 2 elements
Defined:
locally within MaturityNotification complexType; see XML source
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
The type of approval (e.g.
Type:
Content:
simple, 1 attribute
Defined:
locally within ConsentGranted complexType; see XML source
The type of approval (e.g.
Type:
Content:
simple, 1 attribute
Defined:
locally within ConsentRefused complexType; see XML source
The type of approval (e.g.
Type:
Content:
simple, 1 attribute
Defined:
locally within RequestConsent complexType; see XML source
The type of approval (e.g.
Type:
Content:
simple, 1 attribute
Defined:
Complex Type Summary
A message indicating that a request to allocate a trade has been approved by the sender.
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A message indicating that a request to allocate a trade has been refused by the sender.
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
A message describing the approvals currently applied to the trade and their status (e.g. pending, approved, refused).
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
A structure describing a trade registration event that is part of a clearing process.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A message indicating that a clearing request has been acted on and as a result a trade has been cleared.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message indicating that a clearing request has not been acted on due to a business decision and therefore no trade has been cleared.
Content:
complex, 3 attributes, 14 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message providing the current status of a clearing request.
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Content:
complex, 3 attributes, 6 elements
Defined:
globally; see XML source
Used:
A message indicating that a confirmation has been agreed by a counterparty.
Content:
complex, 3 attributes, 24 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message indicating that a confirmation has not been agreed by a counterparty.
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A message indicating that a confirmation request has been withdrawn by the submitter.
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Message for sending matching results.
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
A message indicating that the sender grants consent for the recipient to perform the requested action.
Content:
complex, 3 attributes, 27 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
A message indicating that the sender does not grant consent for the recipient to perform the requested action.
Content:
complex, 3 attributes, 27 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
Defines the structure for a message acknowledging an event request.
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message advising a third party that a trade execution has occurred.
Content:
complex, 3 attributes, 28 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
A message that withdraws an advice to a third party that a trade execution has occurred.
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A message notifying a party that a trade execution has occurred.
Content:
complex, 3 attributes, 18 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A message retracting a notification to a party that a trade execution has occurred.
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message used to notify another party that a trade has matured.
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A message requesting that a trade be split among several accounts.
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
A message withdrawing a request that a trade be split among several accounts.
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A message requesting that a trade be cleared by a clearing service.
Content:
complex, 3 attributes, 16 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message withdrawing a request that a trade be cleared by a clearing service.
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
A message type defining the start of the confirmation process.
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message requesting that the sender be authorized by the recipient to peform an action.
Content:
complex, 3 attributes, 29 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
A message withdrawing a request that the sender be authorized by the recipient to peform an action.
Content:
complex, 3 attributes, 24 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
A type that describes the type of collateral allocation action that is requested.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A message requesting that an order be executed.
Content:
complex, 3 attributes, 14 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message withdrawing a request that an order be executed.
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Defines the structure for a message requesting information updates to a trade.
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
Defines the structure for a message retracting a request to updated information about trade.
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
Defines the structure for a message indicating that a trade is being changed due to a non-negotiated event.
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Defines the structure for a message retracting a prior change advice.
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
A structure that contains a business event.
Content:
complex, 4 elements
Defined:
globally; see XML source
Used:
Element Group Summary
Events/Results that are applicable to clearing processes.
Content:
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
Defines a model group that allows either details of an event or information about a trade to be provided.
Content:
13 elements
Defined:
globally; see XML source
Used:
XML Source
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2018-2019 All rights reserved.
== Financial Products Markup Language is subject to the FpML public license.
== A copy of this license is available at http://www.fpml.org/license/license.html
-->
<xsd:schema attributeFormDefault="unqualified" ecore:documentRoot="FpML" ecore:nsPrefix="conf" ecore:package="org.fpml.confirmation" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/confirmation" version="$Revision: 13737 $" xmlns="http://www.fpml.org/FpML-5/confirmation" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:fpml-annotation="http://www.fpml.org/annotation" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation="fpml-msg-5-11.xsd"/>
<!--<xsd:include schemaLocation="fpml-reg-reporting.xsd"/>-->
<xsd:complexType name="AllocationApproved">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that a request to allocate a trade has been approved by the sender.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="blockTradeIdentifier" type="TradeIdentifier"/>
<xsd:element minOccurs="0" name="allocations" type="Allocations"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="AllocationRefused">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that a request to allocate a trade has been refused by the sender.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="blockTradeIdentifier" type="TradeIdentifier"/>
<xsd:element minOccurs="0" name="allocations" type="Allocations"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reason" type="Reason"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ApprovalStatusNotification">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message describing the approvals currently applied to the trade and their status (e.g. pending, approved, refused).
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NotificationMessage">
<xsd:sequence>
<xsd:choice>
<xsd:element name="trade" type="Trade"/>
<xsd:element name="tradeIdentifier" type="TradeIdentifier"/>
</xsd:choice>
<xsd:element name="approvals" type="Approvals">
<xsd:annotation>
<xsd:documentation xml:lang="en">All of the approvals for a specific trade.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="Clearing">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a trade registration event that is part of a clearing process.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="submitted" type="TradeWrapper">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The original trade or event submitted to the clearing service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="2" minOccurs="2" name="cleared" type="TradeWrapper">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The trades or events generated by the clearing service as a result of clearing.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ClearingConfirmed">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that a clearing request has been acted on and as a result a trade has been cleared.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NotificationMessage">
<xsd:sequence>
<xsd:group minOccurs="0" ref="Compression.model"/>
<xsd:group minOccurs="0" ref="PortfolioReference.model"/>
<xsd:group minOccurs="0" ref="ClearingResults.model"/>
<xsd:group minOccurs="0" ref="EventValuation.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="creditLimitInformation" type="CreditLimitInformation"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ClearingRefused">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that a clearing request has not been acted on due to a business decision and therefore no trade has been cleared.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NotificationMessage">
<xsd:sequence>
<xsd:group minOccurs="0" ref="TradingEvents.model"/>
<xsd:group minOccurs="0" ref="EventValuation.model"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reason" type="Reason"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ClearingStatus">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message providing the current status of a clearing request.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NotificationMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="clearingStatusItem" type="ClearingStatusItem">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes the status of the clearing process relating to the identified trade.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConfirmationAgreed">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that a confirmation has been agreed by a counterparty.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:group ref="TradingEventsBase.model"/>
<xsd:group ref="PostTradeEventsBase.model"/>
<xsd:group ref="ChangeEventsBase.model"/>
<xsd:group ref="OptionsEventsBase.model"/>
<xsd:element ref="additionalEvent"/>
</xsd:choice>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConfirmationDisputed">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that a confirmation has not been agreed by a counterparty.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:group ref="TradingEventsBase.model"/>
<xsd:group ref="PostTradeEventsBase.model"/>
<xsd:group ref="ChangeEventsBase.model"/>
<xsd:group ref="OptionsEventsBase.model"/>
<xsd:element ref="additionalEvent"/>
</xsd:choice>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reason" type="Reason"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConfirmationRetracted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that a confirmation request has been withdrawn by the submitter.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:group ref="TradingAndPostTradeEvents.model"/>
<xsd:element name="optionExercise" type="OptionExercise">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing an option exercise event. The optionExercise event supports partial exercise (specify the number of options or amount to exercise), full exercise (use fullExercise flag), as well as the option to request options not to be exercised.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConfirmationStatus">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Message for sending matching results. Response message that returns the status of an event that have been submitted for matching.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:element name="status" type="EventStatus">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines the confirmation status of a trade or post-trade event (e.g. Matched, Mismatched, Unmatched, Alleged).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:sequence>
<xsd:element name="assertedEvent" type="EventsChoice">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Event (trade or post-trade event) asserted by one of the parties.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="proposedMatch" type="EventProposedMatch">
<xsd:annotation>
<xsd:documentation xml:lang="en">
"Other side's" event (trade or post-trade event) that meets the minimimum matching criteria and is proposed as match to the event that is being asserted.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:element name="allegedEvent" type="EventsChoice">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Event (trade post-trade event) asserted by the "other side's" party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConsentGranted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that the sender grants consent for the recipient to perform the requested action.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="type" type="ApprovalType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The type of approval (e.g. "pre-clearing credit").
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approver" type="PersonId">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The full name or identifiying ID of the relevant approver.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approvingPartyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party defined elsewhere in the document. The party referenced needs to approve the specified item (e.g. trade or allocation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approvalId" type="ApprovalId">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An identifer for a specific appoval, to allow the approval to be identified and tracked.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="PortfolioReferenceBase.model"/>
<xsd:group minOccurs="0" ref="EventsOrInfo.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="creditLimitInformation" type="CreditLimitInformation"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConsentRefused">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message indicating that the sender does not grant consent for the recipient to perform the requested action.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="type" type="ApprovalType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The type of approval (e.g. "pre-clearing credit").
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approver" type="PersonId">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The full name or identifiying ID of the relevant approver.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approvingPartyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party defined elsewhere in the document. The party referenced needs to approve the specified item (e.g. trade or allocation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="PortfolioReferenceBase.model"/>
<xsd:group minOccurs="0" ref="EventsOrInfo.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="creditLimitInformation" type="CreditLimitInformation"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reason" type="Reason"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="EventRequestAcknowledgement">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines the structure for a message acknowledging an event request.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="originalMessage" type="UnprocessedElementWrapper"/>
<xsd:group minOccurs="0" ref="TradeReferenceInformation.model"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ExecutionAdvice">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message advising a third party that a trade execution has occurred.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="productType" type="ProductType"/>
<xsd:choice>
<xsd:group ref="TradingEventsBase.model"/>
<xsd:group ref="PostTradeEventsBase.model"/>
<xsd:group ref="ChangeEventsBase.model"/>
<xsd:group ref="OptionsEventsBase.model"/>
<xsd:element ref="additionalEvent"/>
</xsd:choice>
<xsd:group minOccurs="0" ref="EventValuation.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="paymentDetails" type="PaymentDetails">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Details of the payments, like amount breakdowns, settlement information.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ExecutionAdviceRetracted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message that withdraws an advice to a third party that a trade execution has occurred.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:group ref="TradingEventsBase.model"/>
<xsd:group ref="PostTradeEventsBase.model"/>
<xsd:group ref="ChangeEventsBase.model"/>
<xsd:group ref="OptionsEventsBase.model"/>
<xsd:element ref="additionalEvent"/>
</xsd:choice>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="paymentDetails" type="PaymentDetails">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Details of the payments, like amount breakdowns, settlement information.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ExecutionNotification">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message notifying a party that a trade execution has occurred. (Typically this is sent by an execution platform to a participant.)
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:choice>
<xsd:group ref="TradingEventsBase.model"/>
<xsd:element name="amendment" type="TradeAmendmentContent"/>
<xsd:group ref="OptionsEventsBase.model"/>
<xsd:element ref="additionalEvent"/>
</xsd:choice>
<xsd:group minOccurs="0" ref="EventValuation.model"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ExecutionRetracted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message retracting a notification to a party that a trade execution has occurred. (Typically this is sent by an execution platform to a participant.)
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:group ref="TradingEvents.model"/>
<xsd:element name="optionExercise" type="OptionExercise">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing an option exercise event. The optionExercise event supports partial exercise (specify the number of options or amount to exercise), full exercise (use fullExercise flag), as well as the option to request options not to be exercised.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="MaturityNotification">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message used to notify another party that a trade has matured. This can be used to report, for example, that a swap has passed its final payment and can be removed, or that an option has expired without being executed.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:choice>
<xsd:element name="optionExpiry" type="OptionExpiryBase"/>
<xsd:element name="tradeMaturity" type="TradeMaturity"/>
</xsd:choice>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestAllocation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message requesting that a trade be split among several accounts.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identifies a related party performing a role within the transaction.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="blockTradeIdentifier" type="TradeIdentifier"/>
<xsd:element name="allocations" type="Allocations"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestAllocationRetracted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message withdrawing a request that a trade be split among several accounts.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="blockTradeIdentifier" type="TradeIdentifier"/>
<xsd:element minOccurs="0" name="allocations" type="Allocations"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestClearing">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message requesting that a trade be cleared by a clearing service.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:group minOccurs="0" ref="PortfolioReference.model"/>
<xsd:choice>
<xsd:group ref="TradingEvents.model"/>
<xsd:element name="deClear" type="DeClear">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a declear event. The deClear event allows a firm to request that a trade be removed from clearing, or a clearing service to request consent for this, or to report that it has been done.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group minOccurs="0" ref="EventValuation.model"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestClearingRetracted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message withdrawing a request that a trade be cleared by a clearing service.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:group ref="TradingEvents.model"/>
<xsd:element name="deClear" type="DeClear">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a declear event. The deClear event allows a firm to request that a trade be removed from clearing, or a clearing service to request consent for this, or to report that it has been done.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestConfirmation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message type defining the start of the confirmation process. The message may be used to request the confirmation of a new trade or any other event supported by FpML such as novation, terminations, amendments, etc.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:choice>
<xsd:group ref="TradingAndPostTradeEvents.model"/>
<xsd:element name="optionExercise" type="OptionExercise">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing an option exercise event. The optionExercise event supports partial exercise (specify the number of options or amount to exercise), full exercise (use fullExercise flag), as well as the option to request options not to be exercised.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestConsent">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message requesting that the sender be authorized by the recipient to peform an action.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="requestedAction" type="RequestedAction">
<xsd:annotation>
<xsd:documentation xml:lang="en">The reason the consent was requested.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="type" type="ApprovalType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The type of approval (e.g. "pre-clearing credit").
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approver" type="PersonId">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The full name or identifiying ID of the relevant approver.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approvingPartyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party defined elsewhere in the document. The party referenced needs to approve the specified item (e.g. trade or allocation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="PortfolioReference.model"/>
<xsd:group minOccurs="0" ref="Compression.model"/>
<xsd:choice>
<xsd:group ref="TradingAndPostTradeEvents.model"/>
<xsd:element name="deClear" type="DeClear">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a declear event. The deClear event allows a firm to request that a trade be removed from clearing, or a clearing service to request consent for this, or to report that it has been done.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group minOccurs="0" ref="EventValuation.model"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestConsentRetracted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message withdrawing a request that the sender be authorized by the recipient to peform an action.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="type" type="ApprovalType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The type of approval (e.g. "pre-clearing credit").
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approver" type="PersonId">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The full name or identifiying ID of the relevant approver.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approvingPartyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party defined elsewhere in the document. The party referenced needs to approve the specified item (e.g. trade or allocation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice minOccurs="0">
<xsd:group ref="TradingAndPostTradeEvents.model"/>
<xsd:element name="deClear" type="DeClear">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a declear event. The deClear event allows a firm to request that a trade be removed from clearing, or a clearing service to request consent for this, or to report that it has been done.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestExecution">
<xsd:annotation>
<xsd:documentation xml:lang="en">A message requesting that an order be executed.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:choice>
<xsd:group ref="TradingEvents.model"/>
<xsd:element name="optionExercise" type="OptionExercise">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing an option exercise event. The optionExercise event supports partial exercise (specify the number of options or amount to exercise), full exercise (use fullExercise flag), as well as the option to request options not to be exercised.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestExecutionRetracted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message withdrawing a request that an order be executed.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:group ref="TradingEvents.model"/>
<xsd:element name="optionExercise" type="OptionExercise">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing an option exercise event. The optionExercise event supports partial exercise (specify the number of options or amount to exercise), full exercise (use fullExercise flag), as well as the option to request options not to be exercised.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines the structure for a message requesting information updates to a trade. The trade reference information should contain at least one trade identifier that the recipient is aware of.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:group ref="TradeReferenceInformation.model"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines the structure for a message retracting a request to updated information about trade.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:group ref="TradeReferenceInformation.model"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeChangeAdvice">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines the structure for a message indicating that a trade is being changed due to a non-negotiated event.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:element name="change" type="TradeChangeContent">
<xsd:annotation>
<xsd:documentation xml:lang="en">Describes the details of the change.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="EventValuation.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="paymentDetails" type="PaymentDetails">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Details of the payments, like amount breakdowns, settlement information.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeChangeAdviceRetracted">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines the structure for a message retracting a prior change advice.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="tradeIdentifier" type="PartyTradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">The qualified identifiers of the subject trade.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="change" type="TradeChangeContent">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes the details of the change being retracted.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="paymentDetails" type="PaymentDetails">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Details of the payments, like amount breakdowns, settlement information.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeWrapper">
<xsd:annotation>
<xsd:documentation xml:lang="en">A structure that contains a business event.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="TradeOrInfo.model"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="RequestCollateralAllocation">
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="serviceName" type="NormalizedString">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The name of the service to which the message applies
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="requestedAction" type="RequestedCollateralAllocationAction">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The type of change requested for the collateral allocation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" name="collateralGiverPartyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The party paying the margin / issuing the allocation request.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" name="collateralAllocation" type="ProposedCollateralAllocation">
<xsd:annotation>
<xsd:documentation xml:lang="en">Allocation details</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestedCollateralAllocationAction">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type that describes the type of collateral allocation action that is requested. The purpose is to allow FCMs to specify how the allocations are to be processed.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/requested-collateral-allocation-action" name="requestedCollateralAllocationActionScheme" type="NonEmptyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="CollateralAllocationAccepted">
<xsd:complexContent>
<xsd:extension base="ResponseMessage"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:group name="ClearingResults.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Events/Results that are applicable to clearing processes.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:group ref="TradingEvents.model"/>
<xsd:sequence>
<xsd:element minOccurs="0" name="terminatingEvent" type="TerminatingEvent">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This may be used to describe why a trade was terminated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="termination" type="TradeNotionalChange"/>
</xsd:sequence>
<xsd:element name="deClear" type="DeClear">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a declear event. The deClear event allows a firm to request that a trade be removed from clearing, or a clearing service to request consent for this, or to report that it has been done.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="clearing" type="Clearing"/>
</xsd:choice>
</xsd:group>
<xsd:group name="EventsOrInfo.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines a model group that allows either details of an event or information about a trade to be provided. Typically this will be used in a response to a request.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
</xsd:choice>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">Confirmation messages.</xsd:documentation>
</xsd:annotation>
<!-- Execution -->
<xsd:element name="requestExecution" type="RequestExecution"/>
<xsd:element name="executionNotification" type="ExecutionNotification"/>
<xsd:element name="executionRetracted" type="ExecutionRetracted"/>
<xsd:element name="executionException" type="Exception"/>
<!-- Execution Advice -->
<xsd:element name="executionAdvice" type="ExecutionAdvice"/>
<xsd:element name="executionAdviceException" type="Exception"/>
<!-- Maturity -->
<xsd:element name="maturityNotification" type="MaturityNotification"/>
<xsd:element name="maturityException" type="Exception"/>
<!-- Trade Info update -->
<!-- Trade Change -->
<xsd:element name="tradeChangeAdvice" type="TradeChangeAdvice"/>
<xsd:element name="tradeChangeAdviceException" type="Exception"/>
<!-- Consent Negotiation -->
<xsd:element name="requestConsent" type="RequestConsent"/>
<xsd:element name="consentException" type="Exception"/>
<xsd:element name="consentGranted" type="ConsentGranted"/>
<xsd:element name="consentRefused" type="ConsentRefused"/>
<!-- Confirmation -->
<xsd:element name="requestConfirmation" type="RequestConfirmation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The confirmation process starts with the requestConfirmation message. The message may be used to request the confirmation of a new trade or any other event supported by FpML such as novation, terminations, amendments, etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A requestConfirmation message may be cancelled using the requestConfirmationRetracted message.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A business acknowledgement message to indicate that the previously sent message was sucessfully processed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="confirmationException" type="Exception">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A message sent to inform another system that some exception has been detected.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="confirmationStatus" type="ConfirmationStatus">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The confirmationStatus message provides the status of the matching process: matched, mismatched, unmatched, or alleged. It may also provide the best fit trade(s) or event(s) as result of the matching process.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="confirmationAgreed" type="ConfirmationAgreed">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The confirmationAgreed message is sent when the matching process returns a proposed match (trade or event) and the Confirmation Requester agrees with it.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="confirmationDisputed" type="ConfirmationDisputed">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The confirmationDisputed message is sent when the matching process returns a proposed match (trade or event) and the Confirmation Requester disputes it.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- Clearing -->
<xsd:element name="requestClearing" type="RequestClearing"/>
<xsd:element name="clearingException" type="Exception"/>
<xsd:element name="clearingRefused" type="ClearingRefused"/>
<xsd:element name="clearingStatus" type="ClearingStatus"/>
<xsd:element name="clearingConfirmed" type="ClearingConfirmed"/>
<!-- Allocation -->
<xsd:element name="requestAllocation" type="RequestAllocation"/>
<xsd:element name="allocationException" type="Exception"/>
<xsd:element name="allocationRefused" type="AllocationRefused"/>
<xsd:element name="allocationApproved" type="AllocationApproved"/>
<!-- Collateral Allocation -->
<xsd:element name="collateralAllocationRejected" type="Exception"/>
<!--Option Exercise / Expiry -->
</xsd:schema>

XML schema documentation generated with DocFlex/XML 1.10b5 using DocFlex/XML XSDDoc 2.8.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.