XML Schema "fpml-confirmation-processes-5-8.xsd"
Target Namespace:
http://www.fpml.org/FpML-5/confirmation
Version:
$Revision: 11695 $
Defined Components:
elements (53 global + 73 local), complexTypes (36), element groups (2)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
D:\Tradeheader\trunk\xml\confirmation\fpml-confirmation-processes-5-8.xsd; see XML source
Includes Schemas (1):
fpml-business-events-5-8.xsd [src]
Included in Schemas (1):
fpml-main-5-8.xsd [src]
Annotation
Confirmation messages.
All Element Summary
allegedEvent
Event (trade post-trade event) asserted by the "other side's" party.
Type:
EventsChoice
Content:
complex, 12 elements
Defined:
locally within ConfirmationStatus complexType; see XML source
allocationAcknowledgement
Type:
EventRequestAcknowledgement
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
allocationApproved
Type:
AllocationApproved
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
allocationException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
allocationRefused
Type:
AllocationRefused
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
allocations (in allocationApproved)
Type:
Allocations
Content:
complex, 2 elements
Defined:
locally within AllocationApproved complexType; see XML source
allocations (in allocationRefused)
Type:
Allocations
Content:
complex, 2 elements
Defined:
locally within AllocationRefused complexType; see XML source
allocations (in requestAllocation)
Type:
Allocations
Content:
complex, 2 elements
Defined:
locally within RequestAllocation complexType; see XML source
allocations (in requestAllocationRetracted)
Type:
Allocations
Content:
complex, 2 elements
Defined:
locally within RequestAllocationRetracted complexType; see XML source
amendment (defined in ExecutionNotification complexType)
Type:
TradeAmendmentContent
Content:
complex, 6 elements
Defined:
locally within ExecutionNotification complexType; see XML source
approvalId (in consentGranted)
An identifer for a specific appoval, to allow the approval to be identified and tracked.
Type:
ApprovalId
Content:
simple, 2 attributes
Defined:
locally within ConsentGranted complexType; see XML source
approvals (in approvalStatusNotification)
All of the approvals for a specific trade.
Type:
Approvals
Content:
complex, 1 element
Defined:
locally within ApprovalStatusNotification complexType; see XML source
approvalStatusNotification
Type:
ApprovalStatusNotification
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
approver (in consentGranted)
The full name or identifiying ID of the relevant approver.
Type:
PersonId
Content:
simple, 1 attribute
Defined:
locally within ConsentGranted complexType; see XML source
approver (in consentRefused)
The full name or identifiying ID of the relevant approver.
Type:
PersonId
Content:
simple, 1 attribute
Defined:
locally within ConsentRefused complexType; see XML source
approver (in requestConsent)
The full name or identifiying ID of the relevant approver.
Type:
PersonId
Content:
simple, 1 attribute
Defined:
locally within RequestConsent complexType; see XML source
approver (in requestConsentRetracted)
The full name or identifiying ID of the relevant approver.
Type:
PersonId
Content:
simple, 1 attribute
Defined:
locally within RequestConsentRetracted complexType; see XML source
approvingPartyReference (in consentGranted)
A pointer style reference to a party defined elsewhere in the document.
Type:
PartyReference
Content:
empty, 1 attribute
Defined:
locally within ConsentGranted complexType; see XML source
approvingPartyReference (in consentRefused)
A pointer style reference to a party defined elsewhere in the document.
Type:
PartyReference
Content:
empty, 1 attribute
Defined:
locally within ConsentRefused complexType; see XML source
approvingPartyReference (in requestConsent)
A pointer style reference to a party defined elsewhere in the document.
Type:
PartyReference
Content:
empty, 1 attribute
Defined:
locally within RequestConsent complexType; see XML source
approvingPartyReference (in requestConsentRetracted)
A pointer style reference to a party defined elsewhere in the document.
Type:
PartyReference
Content:
empty, 1 attribute
Defined:
locally within RequestConsentRetracted complexType; see XML source
assertedEvent
Event (trade or post-trade event) asserted by one of the parties.
Type:
EventsChoice
Content:
complex, 12 elements
Defined:
locally within ConfirmationStatus complexType; see XML source
blockTradeIdentifier (in allocationApproved)
Type:
TradeIdentifier
Content:
complex, 1 attribute, 6 elements
Defined:
locally within AllocationApproved complexType; see XML source
blockTradeIdentifier (in allocationRefused)
Type:
TradeIdentifier
Content:
complex, 1 attribute, 6 elements
Defined:
locally within AllocationRefused complexType; see XML source
blockTradeIdentifier (in requestAllocation)
Type:
TradeIdentifier
Content:
complex, 1 attribute, 6 elements
Defined:
locally within RequestAllocation complexType; see XML source
blockTradeIdentifier (in requestAllocationRetracted)
Type:
TradeIdentifier
Content:
complex, 1 attribute, 6 elements
Defined:
locally within RequestAllocationRetracted complexType; see XML source
change (in tradeChangeAdvice)
Describes the details of the change.
Type:
TradeChangeContent
Content:
complex, 6 elements
Defined:
locally within TradeChangeAdvice complexType; see XML source
change (in tradeChangeAdviceRetracted)
Describes the details of the change being retracted.
Type:
TradeChangeContent
Content:
complex, 6 elements
Defined:
locally within TradeChangeAdviceRetracted complexType; see XML source
cleared (in clearing)
The trades or events generated by the clearing service as a result of clearing.
Type:
TradeWrapper
Content:
complex, 4 elements
Defined:
locally within Clearing complexType; see XML source
clearing
Type:
Clearing
Content:
complex, 2 elements
Defined:
locally within ClearingResults.model group; see XML source
clearingAcknowledgement
Type:
EventRequestAcknowledgement
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
clearingConfirmed
Type:
ClearingConfirmed
Content:
complex, 3 attributes, 19 elements
Defined:
globally; see XML source
Used:
never
clearingException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
clearingRefused
Type:
ClearingRefused
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Used:
never
clearingStatus
Type:
ClearingStatus
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:
ClearingStatusItem
Content:
complex, 8 elements
Defined:
locally within ClearingStatus complexType; see XML source
collateralAllocation
Allocation details
Type:
ProposedCollateralAllocation
Content:
complex, 3 elements
Defined:
locally within RequestCollateralAllocation complexType; see XML source
collateralAllocationAccepted
Type:
CollateralAllocationAccepted
Content:
complex, 3 attributes, 6 elements
Defined:
globally; see XML source
Used:
never
collateralAllocationAcknowledgement
Type:
Acknowledgement
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
collateralAllocationRejected
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
collateralGiverPartyReference
The party paying the margin / issuing the allocation request.
Type:
PartyReference
Content:
empty, 1 attribute
Defined:
locally within RequestCollateralAllocation complexType; see XML source
confirmationAcknowledgement
A business acknowledgement message to indicate that the previously sent message was sucessfully processed.
Type:
EventRequestAcknowledgement
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:
ConfirmationAgreed
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:
ConfirmationDisputed
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:
Exception
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:
ConfirmationStatus
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
consentAcknowledgement
Type:
EventRequestAcknowledgement
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
consentException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
consentGranted
Type:
ConsentGranted
Content:
complex, 3 attributes, 23 elements
Defined:
globally; see XML source
Used:
never
consentRefused
Type:
ConsentRefused
Content:
complex, 3 attributes, 23 elements
Defined:
globally; see XML source
Used:
never
creditLimitInformation (in clearingConfirmed)
Type:
CreditLimitInformation
Content:
complex, 3 elements
Defined:
locally within ClearingConfirmed complexType; see XML source
creditLimitInformation (in consentGranted)
Type:
CreditLimitInformation
Content:
complex, 3 elements
Defined:
locally within ConsentGranted complexType; see XML source
creditLimitInformation (in consentRefused)
Type:
CreditLimitInformation
Content:
complex, 3 elements
Defined:
locally within ConsentRefused complexType; see XML source
deClear (in clearingConfirmed)
A structure describing a declear event.
Type:
DeClear
Content:
complex, 3 elements
Defined:
locally within ClearingResults.model group; see XML source
deClear (in requestClearing)
A structure describing a declear event.
Type:
DeClear
Content:
complex, 3 elements
Defined:
locally within RequestClearing complexType; see XML source
deClear (in requestClearingRetracted)
A structure describing a declear event.
Type:
DeClear
Content:
complex, 3 elements
Defined:
locally within RequestClearingRetracted complexType; see XML source
deClear (in requestConsent)
A structure describing a declear event.
Type:
DeClear
Content:
complex, 3 elements
Defined:
locally within RequestConsent complexType; see XML source
deClear (in requestConsentRetracted)
A structure describing a declear event.
Type:
DeClear
Content:
complex, 3 elements
Defined:
locally within RequestConsentRetracted complexType; see XML source
executionAcknowledgement
Type:
EventRequestAcknowledgement
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
executionAdvice
Type:
ExecutionAdvice
Content:
complex, 3 attributes, 23 elements
Defined:
globally; see XML source
Used:
never
executionAdviceAcknowledgement
Type:
EventRequestAcknowledgement
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
executionAdviceException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
executionAdviceRetracted
Type:
ExecutionAdviceRetracted
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
executionException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
executionNotification
Type:
ExecutionNotification
Content:
complex, 3 attributes, 16 elements
Defined:
globally; see XML source
Used:
never
executionRetracted
Type:
ExecutionRetracted
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
maturityAcknowledgement
Type:
EventRequestAcknowledgement
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
maturityException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
maturityNotification
Type:
MaturityNotification
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
optionExercise (in executionRetracted)
A structure describing an option exercise event.
Type:
OptionExercise
Content:
complex, 24 elements
Defined:
locally within ExecutionRetracted complexType; see XML source
optionExercise (in requestConfirmation)
A structure describing an option exercise event.
Type:
OptionExercise
Content:
complex, 24 elements
Defined:
locally within RequestConfirmation complexType; see XML source
optionExercise (in requestConfirmationRetracted)
A structure describing an option exercise event.
Type:
OptionExercise
Content:
complex, 24 elements
Defined:
locally within ConfirmationRetracted complexType; see XML source
optionExercise (in requestExecution)
A structure describing an option exercise event.
Type:
OptionExercise
Content:
complex, 24 elements
Defined:
locally within RequestExecution complexType; see XML source
optionExercise (in requestExecutionRetracted)
A structure describing an option exercise event.
Type:
OptionExercise
Content:
complex, 24 elements
Defined:
locally within RequestExecutionRetracted complexType; see XML source
optionExpirationNotification
Type:
ExecutionNotification
Content:
complex, 3 attributes, 16 elements
Defined:
globally; see XML source
Used:
never
optionExpiry (in maturityNotification)
Type:
OptionExpiryBase
Content:
complex, 3 elements
Defined:
locally within MaturityNotification complexType; see XML source
originalMessage (defined in EventRequestAcknowledgement complexType)
Type:
UnprocessedElementWrapper
Content:
complex, elem. wildcard
Defined:
locally within EventRequestAcknowledgement complexType; see XML source
paymentDetails (in executionAdvice)
Details of the payments, like amount breakdowns, settlement information.
Type:
PaymentDetails
Content:
complex, 3 elements
Defined:
locally within ExecutionAdvice complexType; see XML source
paymentDetails (in executionAdviceRetracted)
Details of the payments, like amount breakdowns, settlement information.
Type:
PaymentDetails
Content:
complex, 3 elements
Defined:
locally within ExecutionAdviceRetracted complexType; see XML source
paymentDetails (in tradeChangeAdvice)
Details of the payments, like amount breakdowns, settlement information.
Type:
PaymentDetails
Content:
complex, 3 elements
Defined:
locally within TradeChangeAdvice complexType; see XML source
paymentDetails (in tradeChangeAdviceRetracted)
Details of the payments, like amount breakdowns, settlement information.
Type:
PaymentDetails
Content:
complex, 3 elements
Defined:
locally within TradeChangeAdviceRetracted complexType; see XML source
productType (in executionAdvice)
Type:
ProductType
Content:
simple, 1 attribute
Defined:
locally within 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:
EventProposedMatch
Content:
complex, 15 elements
Defined:
locally within ConfirmationStatus complexType; see XML source
reason (in allocationRefused)
Type:
Reason
Content:
complex, 5 elements
Defined:
locally within AllocationRefused complexType; see XML source
reason (in clearingRefused)
Type:
Reason
Content:
complex, 5 elements
Defined:
locally within ClearingRefused complexType; see XML source
reason (in confirmationDisputed)
Type:
Reason
Content:
complex, 5 elements
Defined:
locally within ConfirmationDisputed complexType; see XML source
reason (in consentRefused)
Type:
Reason
Content:
complex, 5 elements
Defined:
locally within ConsentRefused complexType; see XML source
relatedParty (in requestAllocation)
Identifies a related party performing a role within the transaction.
Type:
RelatedParty
Content:
complex, 4 elements
Defined:
locally within RequestAllocation complexType; see XML source
requestAllocation
Type:
RequestAllocation
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
requestAllocationRetracted
Type:
RequestAllocationRetracted
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
requestClearing
Type:
RequestClearing
Content:
complex, 3 attributes, 15 elements
Defined:
globally; see XML source
Used:
never
requestClearingRetracted
Type:
RequestClearingRetracted
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
requestCollateralAllocation
Type:
RequestCollateralAllocation
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Used:
never
requestConfirmation
The confirmation process starts with the requestConfirmation message.
Type:
RequestConfirmation
Content:
complex, 3 attributes, 19 elements
Defined:
globally; see XML source
Used:
never
requestConfirmationRetracted
A requestConfirmation message may be cancelled using the requestConfirmationRetracted message.
Type:
ConfirmationRetracted
Content:
complex, 3 attributes, 18 elements
Defined:
globally; see XML source
Used:
never
requestConsent
Type:
RequestConsent
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Used:
never
requestConsentRetracted
Type:
RequestConsentRetracted
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
requestedAction (in requestCollateralAllocation)
The type of change requested for the collateral allocation.
Type:
RequestedCollateralAllocationAction
Content:
simple, 1 attribute
Defined:
locally within RequestCollateralAllocation complexType; see XML source
requestedAction (in requestConsent)
The reason the consent was requested.
Type:
RequestedAction
Content:
simple, 1 attribute
Defined:
locally within RequestConsent complexType; see XML source
requestExecution
Type:
RequestExecution
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Used:
never
requestExecutionRetracted
Type:
RequestExecutionRetracted
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
requestTradeReferenceInformationUpdate
Type:
RequestTradeReferenceInformationUpdate
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
requestTradeReferenceInformationUpdateRetracted
Type:
RequestTradeReferenceInformationUpdateRetracted
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
serviceName (in requestCollateralAllocation)
The name of the service to which the message applies
Type:
NormalizedString
Content:
simple
Defined:
locally within RequestCollateralAllocation complexType; see XML source
status (in confirmationStatus)
Defines the confirmation status of a trade or post-trade event (e.g.
Type:
EventStatus
Content:
simple, 1 attribute
Defined:
locally within ConfirmationStatus complexType; see XML source
submitted
The original trade or event submitted to the clearing service.
Type:
TradeWrapper
Content:
complex, 4 elements
Defined:
locally within Clearing complexType; see XML source
terminatingEvent (in clearingConfirmed)
This may be used to describe why a trade was terminated.
Type:
TerminatingEvent
Content:
simple, 1 attribute
Defined:
locally within ClearingResults.model group; see XML source
termination (in clearingConfirmed)
Type:
TradeNotionalChange
Content:
complex, 16 elements
Defined:
locally within ClearingResults.model group; see XML source
trade (in approvalStatusNotification)
Type:
Trade
Content:
complex, 1 attribute, 14 elements
Defined:
locally within ApprovalStatusNotification complexType; see XML source
tradeChangeAdvice
Type:
TradeChangeAdvice
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Used:
never
tradeChangeAdviceAcknowledgement
Type:
EventRequestAcknowledgement
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
tradeChangeAdviceException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
tradeChangeAdviceRetracted
Type:
TradeChangeAdviceRetracted
Content:
complex, 3 attributes, 11 elements
Defined:
globally; see XML source
Used:
never
tradeIdentifier (in approvalStatusNotification)
Type:
TradeIdentifier
Content:
complex, 1 attribute, 6 elements
Defined:
locally within ApprovalStatusNotification complexType; see XML source
tradeIdentifier (in tradeChangeAdviceRetracted)
The qualified identifiers of the subject trade.
Type:
PartyTradeIdentifier
Content:
complex, 1 attribute, 11 elements
Defined:
locally within TradeChangeAdviceRetracted complexType; see XML source
tradeMaturity
Type:
TradeMaturity
Content:
complex, 2 elements
Defined:
locally within MaturityNotification complexType; see XML source
tradeReferenceInformationUpdateAcknowledgement
Type:
EventRequestAcknowledgement
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
never
tradeReferenceInformationUpdateException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
type (in consentGranted)
The type of approval (e.g.
Type:
ApprovalType
Content:
simple, 1 attribute
Defined:
locally within ConsentGranted complexType; see XML source
type (in consentRefused)
The type of approval (e.g.
Type:
ApprovalType
Content:
simple, 1 attribute
Defined:
locally within ConsentRefused complexType; see XML source
type (in requestConsent)
The type of approval (e.g.
Type:
ApprovalType
Content:
simple, 1 attribute
Defined:
locally within RequestConsent complexType; see XML source
type (in requestConsentRetracted)
The type of approval (e.g.
Type:
ApprovalType
Content:
simple, 1 attribute
Defined:
locally within RequestConsentRetracted complexType; see XML source
withdrawal (in confirmationAgreed)
Type:
Withdrawal
Content:
complex, 6 elements
Defined:
locally within ConfirmationAgreed complexType; see XML source
withdrawal (in confirmationDisputed)
Type:
Withdrawal
Content:
complex, 6 elements
Defined:
locally within ConfirmationDisputed complexType; see XML source
withdrawal (in requestConfirmation)
Type:
Withdrawal
Content:
complex, 6 elements
Defined:
locally within RequestConfirmation complexType; see XML source
withdrawal (in requestConfirmationRetracted)
Type:
Withdrawal
Content:
complex, 6 elements
Defined:
locally within ConfirmationRetracted complexType; see XML source
Complex Type Summary
AllocationApproved
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:
at 1 location
AllocationRefused
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:
at 1 location
ApprovalStatusNotification
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:
at 1 location
Clearing
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:
at 1 location
ClearingConfirmed
A message indicating that a clearing request has been acted on and as a result a trade has been cleared.
Content:
complex, 3 attributes, 19 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
ClearingRefused
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, 13 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
ClearingStatus
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:
at 1 location
CollateralAllocationAccepted
Content:
complex, 3 attributes, 6 elements
Defined:
globally; see XML source
Used:
at 1 location
ConfirmationAgreed
A message indicating that a confirmation has been agreed by a counterparty.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
ConfirmationDisputed
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:
definitions of 2 elements
Used:
at 1 location
ConfirmationRetracted
A message indicating that a confirmation request has been withdrawn by the submitter.
Content:
complex, 3 attributes, 18 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
ConfirmationStatus
Message for sending matching results.
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
ConsentGranted
A message indicating that the sender grants consent for the recipient to perform the requested action.
Content:
complex, 3 attributes, 23 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
ConsentRefused
A message indicating that the sender does not grant consent for the recipient to perform the requested action.
Content:
complex, 3 attributes, 23 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
EventRequestAcknowledgement
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:
at 9 locations
ExecutionAdvice
A message advising a third party that a trade execution has occurred.
Content:
complex, 3 attributes, 23 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
ExecutionAdviceRetracted
A message that withdraws an advice to a third party that a trade execution has occurred.
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
ExecutionNotification
A message notifying a party that a trade execution has occurred.
Content:
complex, 3 attributes, 16 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 2 locations
ExecutionRetracted
A message retracting a notification to a party that a trade execution has occurred.
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
MaturityNotification
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:
at 1 location
RequestAllocation
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:
at 1 location
RequestAllocationRetracted
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:
at 1 location
RequestClearing
A message requesting that a trade be cleared by a clearing service.
Content:
complex, 3 attributes, 15 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
RequestClearingRetracted
A message withdrawing a request that a trade be cleared by a clearing service.
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
RequestCollateralAllocation
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
RequestConfirmation
A message type defining the start of the confirmation process.
Content:
complex, 3 attributes, 19 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
RequestConsent
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:
definitions of 5 elements
Used:
at 1 location
RequestConsentRetracted
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
Includes:
definitions of 4 elements
Used:
at 1 location
RequestedCollateralAllocationAction
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:
at 1 location
RequestExecution
A message requesting that an order be executed.
Content:
complex, 3 attributes, 13 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
RequestExecutionRetracted
A message withdrawing a request that an order be executed.
Content:
complex, 3 attributes, 12 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
RequestTradeReferenceInformationUpdate
Defines the structure for a message requesting information updates to a trade.
Content:
complex, 3 attributes, 10 elements
Defined:
globally; see XML source
Used:
at 1 location
RequestTradeReferenceInformationUpdateRetracted
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:
at 1 location
TradeChangeAdvice
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:
at 1 location
TradeChangeAdviceRetracted
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:
at 1 location
TradeWrapper
A structure that contains a business event.
Content:
complex, 4 elements
Defined:
globally; see XML source
Used:
at 2 locations
Element Group Summary
ClearingResults.model
Events/Results that are applicable to clearing processes.
Content:
7 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
EventsOrInfo.model
Defines a model group that allows either details of an event or information about a trade to be provided.
Content:
9 elements
Defined:
globally; see XML source
Used:
at 2 locations
XML Source
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2002- 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: 11695 $" 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-8.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 ref="Events.model" minOccurs="0"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<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:group ref="Events.model" minOccurs="0"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<xsd:choice minOccurs="0">
<xsd:group ref="TradingAndPostTradeEvents.model"/>
<xsd:group ref="ChangeEvents.model"/>
<xsd:group ref="OptionsEvents.model"/>
<xsd:element name="withdrawal" type="Withdrawal"/>
</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:group ref="Events.model" minOccurs="0"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<xsd:choice minOccurs="0">
<xsd:group ref="TradingAndPostTradeEvents.model"/>
<xsd:group ref="ChangeEvents.model"/>
<xsd:group ref="OptionsEvents.model"/>
<xsd:element name="withdrawal" type="Withdrawal"/>
</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:group ref="Events.model" minOccurs="0"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<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:element name="withdrawal" type="Withdrawal"/>
</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:group ref="Events.model"/> BPWG2014 Replaced with the below - comment to be deleted before 5.8LCWD -->
<xsd:choice>
<xsd:group ref="TradingAndPostTradeEvents.model"/>
<xsd:group ref="ChangeEvents.model"/>
<xsd:group ref="OptionsEvents.model"/>
</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:group ref="Events.model" minOccurs="0"/> BPWG2014 Replaced with the below - comment to be deleted before 5.8LCWD -->
<xsd:choice>
<xsd:group ref="TradingAndPostTradeEvents.model"/>
<xsd:group ref="ChangeEvents.model"/>
<xsd:group ref="OptionsEvents.model"/>
</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:group ref="Events.model"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<xsd:choice>
<xsd:group ref="TradingEvents.model"/>
<xsd:element name="amendment" type="TradeAmendmentContent"/>
<xsd:group ref="OptionsEvents.model"/>
</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:group ref="Events.model" minOccurs="0"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<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:group ref="Events.model"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<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:group ref="Events.model" minOccurs="0"/> Replaced by the below choice -->
<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:group ref="Events.model"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<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:element name="withdrawal" type="Withdrawal"/>
</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:group ref="Events.model"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<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:group ref="Events.model" minOccurs="0"/> BPWG2014 - Replaced by the below - comment to be deleted before 5.8LCWD -->
<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:group ref="Events.model"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<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:group ref="Events.model" minOccurs="0"/> BPWG2014 Replaced by the below - comment to be deleted before 5.8LCWD -->
<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" minOccurs="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" minOccurs="1" 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="xsd:anyURI"/>
</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="Events.model"/> BPWG2014 the below - comment to be deleted before 5.8LCWD -->
<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:group ref="Events.model"/> BPWG2014 Replaced with the below - comment to be deleted before 5.8LCWD -->
</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.9.0 using DocFlex/XML XSDDoc 2.8.0 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.