Schema "fpml-confirmation-processes-5-3.xsd"
Target Namespace:
http://www.fpml.org/FpML-5/confirmation
Version:
$Revision: 9008 $
Defined Components:
48 global elements, 39 local elements, 33 complexTypes, 2 element groups
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Irina-Local\SVN-FpML\branches\FpML-5-3-6-REC-1\xml\confirmation\fpml-confirmation-processes-5-3.xsd; see XML source
Includes Schema:
fpml-business-events-5-3.xsd [src]
Included in Schema:
fpml-main-5-3.xsd [src]
Annotation
Confirmation messages.
All Element Summary
allegedEvent Event (trade post-trade event) asserted by the "other side's" party.
Type:
Content:
complex, 12 elements
Defined:
locally witnin ConfirmationStatus complexType; see XML source
allocationAcknowledgement
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
allocationApproved
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
allocationException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
allocationRefused
Type:
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
allocations (in allocationApproved)
Type:
Content:
complex, 1 element
Defined:
locally witnin AllocationApproved complexType; see XML source
allocations (in allocationRefused)
Type:
Content:
complex, 1 element
Defined:
locally witnin AllocationRefused complexType; see XML source
allocations (in requestAllocation)
Type:
Content:
complex, 1 element
Defined:
locally witnin RequestAllocation complexType; see XML source
allocations (in requestAllocationRetracted)
Type:
Content:
complex, 1 element
Defined:
assertedEvent Event (trade or post-trade event) asserted by one of the parties.
Type:
Content:
complex, 12 elements
Defined:
locally witnin ConfirmationStatus complexType; see XML source
blockTradeIdentifier (in allocationApproved)
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin AllocationApproved complexType; see XML source
blockTradeIdentifier (in allocationRefused)
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin AllocationRefused complexType; see XML source
blockTradeIdentifier (in requestAllocation)
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin RequestAllocation complexType; see XML source
blockTradeIdentifier (in requestAllocationRetracted)
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
change (in tradeChangeAdvice) Describes the details of the change.
Type:
Content:
complex, 6 elements
Defined:
locally witnin TradeChangeAdvice complexType; see XML source
change (in tradeChangeAdviceRetracted) Describes the details of the change being retracted.
Type:
Content:
complex, 6 elements
Defined:
cleared (in clearing) The trades or events generated by the clearing service as a result of clearing.
Type:
Content:
complex, 3 elements
Defined:
locally witnin Clearing complexType; see XML source
clearing
Type:
Content:
complex, 2 elements
Defined:
clearingAcknowledgement
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
clearingConfirmed
Type:
Content:
complex, 3 attributes, 24 elements
Defined:
globally; see XML source
Used:
never
clearingException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
clearingRefused
Type:
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Used:
never
clearingStatus
Type:
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
clearingStatusItem Describes the status of the clearing process relating to the identified trade.
Type:
Content:
complex, 7 elements
Defined:
locally witnin ClearingStatus complexType; see XML source
clearingStatusValue The status of the clearing process for the identified trade.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin ClearingStatusItem complexType; see XML source
confirmationAcknowledgement 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
confirmationAgreed 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, 20 elements
Defined:
globally; see XML source
Used:
never
confirmationDisputed 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, 21 elements
Defined:
globally; see XML source
Used:
never
confirmationException 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
confirmationStatus 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
consentAcknowledgement
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
consentException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
consentGranted
Type:
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Used:
never
consentRefused
Type:
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Used:
never
executionAcknowledgement
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
executionAdvice
Type:
Content:
complex, 3 attributes, 24 elements
Defined:
globally; see XML source
Used:
never
executionAdviceAcknowledgement
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
executionAdviceException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
executionAdviceRetracted
Type:
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Used:
never
executionException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
executionNotification
Type:
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Used:
never
executionRetracted
Type:
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
maturityAcknowledgement
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
maturityException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
maturityNotification
Type:
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
optionExpirationNotification
Type:
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Used:
never
optionExpiry (in maturityNotification)
Type:
Content:
complex, 3 elements
Defined:
locally witnin MaturityNotification complexType; see XML source
originalMessage (defined in EventRequestAcknowledgement complexType)
Type:
Content:
complex, elem. wildcard
Defined:
paymentDetails (in executionAdvice) Details of the payments, like amount breakdowns, settlement information.
Type:
Content:
complex, 3 elements
Defined:
locally witnin ExecutionAdvice complexType; see XML source
paymentDetails (in executionAdviceRetracted) Details of the payments, like amount breakdowns, settlement information.
Type:
Content:
complex, 3 elements
Defined:
paymentDetails (in tradeChangeAdvice) Details of the payments, like amount breakdowns, settlement information.
Type:
Content:
complex, 3 elements
Defined:
locally witnin TradeChangeAdvice complexType; see XML source
paymentDetails (in tradeChangeAdviceRetracted) Details of the payments, like amount breakdowns, settlement information.
Type:
Content:
complex, 3 elements
Defined:
productType (in executionAdvice)
Type:
Content:
simple, 1 attribute
Defined:
locally witnin ExecutionAdvice complexType; see XML source
proposedMatch "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, 15 elements
Defined:
locally witnin ConfirmationStatus complexType; see XML source
reason (in allocationRefused)
Type:
Content:
complex, 5 elements
Defined:
locally witnin AllocationRefused complexType; see XML source
reason (in clearingRefused)
Type:
Content:
complex, 5 elements
Defined:
locally witnin ClearingRefused complexType; see XML source
reason (in clearingStatusItem) Supporting information which may be produced to explain the clearing process status.
Type:
Content:
complex, 5 elements
Defined:
locally witnin ClearingStatusItem complexType; see XML source
reason (in confirmationDisputed)
Type:
Content:
complex, 5 elements
Defined:
locally witnin ConfirmationDisputed complexType; see XML source
reason (in consentRefused)
Type:
Content:
complex, 5 elements
Defined:
locally witnin ConsentRefused complexType; see XML source
relatedParty (in requestAllocation) Identifies a related party performing a role within the transaction.
Type:
Content:
complex, 4 elements
Defined:
locally witnin RequestAllocation complexType; see XML source
requestAllocation
Type:
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
requestAllocationRetracted
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
requestClearing
Type:
Content:
complex, 3 attributes, 23 elements
Defined:
globally; see XML source
Used:
never
requestClearingRetracted
Type:
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
requestConfirmation The confirmation process starts with the requestConfirmation message.
Type:
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Used:
never
requestConfirmationRetracted A requestConfirmation message may be cancelled using the requestConfirmationRetracted message.
Type:
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
requestConsent
Type:
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Used:
never
requestConsentRetracted
Type:
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
requestedAction (in requestConsent) The reason the consent was requested.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin RequestConsent complexType; see XML source
requestExecution
Type:
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Used:
never
requestExecutionRetracted
Type:
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
requestTradeReferenceInformationUpdate
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
requestTradeReferenceInformationUpdateRetracted
Type:
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
status (in confirmationStatus) Defines the confirmation status of a trade or post-trade event (e.g.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin ConfirmationStatus complexType; see XML source
statusAppliesTo Reference to parties currently in this status, e.g. parties for which we are awaiting approval.
Type:
Content:
empty, 1 attribute
Defined:
locally witnin ClearingStatusItem complexType; see XML source
submitted The original trade or event submitted to the clearing service.
Type:
Content:
complex, 3 elements
Defined:
locally witnin Clearing complexType; see XML source
trade (in clearingStatusItem) Complete economics of the trade
Type:
Content:
complex, 1 attribute, 12 elements
Defined:
locally witnin ClearingStatusItem complexType; see XML source
tradeChangeAdvice
Type:
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
tradeChangeAdviceAcknowledgement
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
tradeChangeAdviceException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
tradeChangeAdviceRetracted
Type:
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
tradeIdentifier (in clearingStatusItem) Identifier(s) for the trade which is the subject of the clearing request to which this status relates.
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin ClearingStatusItem complexType; see XML source
tradeIdentifier (in tradeChangeAdviceRetracted) The qualified identifiers of the subject trade.
Type:
Content:
complex, 1 attribute, 10 elements
Defined:
tradeMaturity (in maturityNotification)
Type:
Content:
complex, 2 elements
Defined:
locally witnin MaturityNotification complexType; see XML source
tradeReferenceInformationUpdateAcknowledgement
Type:
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
tradeReferenceInformationUpdateException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
updatedDateTime When the clearing status changed to the current value.
Type:
xsd:dateTime
Content:
simple
Defined:
locally witnin ClearingStatusItem complexType; see XML source
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 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, 24 elements
Defined:
globally; see XML source
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, 22 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:
A component of a clearing status report.
Content:
complex, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
A message indicating that a confirmation has been agreed by a counterparty.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
A message indicating that a confirmation has not been agreed by a counterparty.
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message indicating that a confirmation request has been withdrawn by the submitter.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
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, 22 elements
Defined:
globally; see XML source
Used:
A message indicating that the sender does not grant consent for the recipient to perform the requested action.
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
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, 24 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A message that withdraws an advice to a third party that a trade execution has occurred.
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message notifying a party that a trade execution has occurred.
Content:
complex, 3 attributes, 22 elements
Defined:
globally; see XML source
Used:
A message retracting a notification to a party that a trade execution has occurred.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
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, 23 elements
Defined:
globally; see XML source
Used:
A message withdrawing a request that a trade be cleared by a clearing service.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
A message type defining the start of the confirmation process.
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Used:
A message requesting that the sender be authorized by the recipient to peform an action.
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A message withdrawing a request that the sender be authorized by the recipient to peform an action.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
A message requesting that an order be executed.
Content:
complex, 3 attributes, 21 elements
Defined:
globally; see XML source
Used:
A message withdrawing a request that an order be executed.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
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, 3 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:
definition of 1 element
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) 2002-2012 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: 9008 $" 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-business-events-5-3.xsd"/>
<xsd:complexType name="AllocationApproved">
<xsd:annotation>
<xsd:documentation>
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>
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="Clearing">
<xsd:annotation>
<xsd:documentation>
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>
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:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ClearingRefused">
<xsd:annotation>
<xsd:documentation>
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="Events.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>
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>
Describes the status of the clearing process relating to the identified trade.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--<xsd:group ref="Events.model" minOccurs="0"/>-->
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ClearingStatusItem">
<xsd:annotation>
<xsd:documentation>
A component of a clearing status report. This provides the clearing status for a single trade.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:element maxOccurs="unbounded" name="tradeIdentifier" type="TradeIdentifier">
<xsd:annotation>
<xsd:documentation>
Identifier(s) for the trade which is the subject of the clearing request to which this status relates.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Identifying information for the trade which is the subject of the clearing request to which this status relates.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:element name="trade" type="Trade">
<xsd:annotation>
<xsd:documentation>Complete economics of the trade</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element name="clearingStatusValue" type="ClearingStatusValue">
<xsd:annotation>
<xsd:documentation>
The status of the clearing process for the identified trade. For example, Received, Pending (Approval), Registered (i.e. cleared), Rejected, etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="updatedDateTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
When the clearing status changed to the current value. This is mostly useful if the clearing status messages could be delayed from when the status actually changes; this could be important if the status date is used as the basis of any settlement calculations.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reason" type="Reason">
<xsd:annotation>
<xsd:documentation>
Supporting information which may be produced to explain the clearing process status. This may be a business reason e.g. failed eligibility criteria for a trade in Rejected status.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="2" minOccurs="0" name="statusAppliesTo" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Reference to parties currently in this status, e.g. parties for which we are awaiting approval. For example, if a trade is in "Pending" status, this would identify which parties' approval the trade was pending.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ConfirmationAgreed">
<xsd:annotation>
<xsd:documentation>
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:group minOccurs="0" ref="Events.model"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConfirmationDisputed">
<xsd:annotation>
<xsd:documentation>
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:group minOccurs="0" ref="Events.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="ConfirmationRetracted">
<xsd:annotation>
<xsd:documentation>
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:group minOccurs="0" ref="Events.model"/>
<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>
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:group minOccurs="0" ref="PortfolioReferenceBase.model"/>
<xsd:group minOccurs="0" ref="EventsOrInfo.model"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConsentRefused">
<xsd:annotation>
<xsd:documentation>
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:group minOccurs="0" ref="EventsOrInfo.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="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>
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"/>
<!-- added 2010-09 for Option Excercise / Expiry -->
<xsd:group ref="Events.model"/>
<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>
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:group minOccurs="0" ref="Events.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 minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ExecutionNotification">
<xsd:annotation>
<xsd:documentation>
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:group ref="Events.model"/>
<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>
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:group minOccurs="0" ref="Events.model"/>
<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>
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>
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>
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:group ref="Events.model"/>
<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>
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:group minOccurs="0" ref="Events.model"/>
<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:group ref="Events.model"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestConsent">
<xsd:annotation>
<xsd:documentation>
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>The reason the consent was requested.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="PortfolioReference.model"/>
<xsd:group minOccurs="0" ref="Compression.model"/>
<xsd:group ref="Events.model"/>
<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>
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:group minOccurs="0" ref="Events.model"/>
<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestExecution">
<xsd:annotation>
<xsd:documentation>A message requesting that an order be executed.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:group ref="Events.model"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestExecutionRetracted">
<xsd:annotation>
<xsd:documentation>
A message withdrawing a request that an order be executed.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:group minOccurs="0" ref="Events.model"/>
<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="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 minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeChangeAdvice">
<xsd:annotation>
<xsd:documentation>
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>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>
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>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>
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>A structure that contains a business event.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="TradeOrInfo.model"/>
</xsd:sequence>
</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="Events.model"/>
<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:group ref="Events.model"/>
</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"/>
<!--Option Exercise / Expiry -->
</xsd:schema>

XML schema documentation generated with DocFlex/XML 1.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.