All Element Summary |
||||||||||||
|
||||||||||||
The additionalEvent element is an extension/substitution point to customize FpML and add additional events.
|
||||||||||||
The date on which the change was agreed.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
A container for approval states in the workflow.
|
||||||||||||
Describes a change due to change in composition of basket underlyer
|
||||||||||||
|
||||||||||||
|
||||||||||||
Abstract substitutable place holder for specific change details.
|
||||||||||||
|
||||||||||||
|
||||||||||||
Specifies the fixed amount by which the Notional Amount changes.
|
||||||||||||
|
||||||||||||
|
||||||||||||
Specifies the fixed amount by which the Number of Options changes
|
||||||||||||
|
||||||||||||
Specifies the fixed amount by which the Number of Units changes
|
||||||||||||
|
||||||||||||
The status of the clearing process for the identified trade.
|
||||||||||||
|
||||||||||||
Compression information for the trade.
|
||||||||||||
|
||||||||||||
The definitions (such as those published by ISDA) that will define the terms of the novation transaction.
|
||||||||||||
A contractual supplement (such as those published by ISDA) that will apply to the trade.
|
||||||||||||
Describes a change due to a corporate action
|
||||||||||||
This element should be specified if one or more of either a Credit Event Notice, Notice of Publicly Available Information, Notice of Physical Settlement or Notice of Intended Physical Settlement, as applicable, has been delivered by or to the Transferor or the Remaining Party.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
A structure describing a declear event.
|
||||||||||||
A type used to record the details of a difference between two sides of a business event.
|
||||||||||||
The date on which the change become effective.
|
||||||||||||
The date on which the change become effective
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
The date and time at which the negotiated change to the terms of the original contract was agreed, such as via telephone or electronic trading system (i.e., agreement date/time).
|
||||||||||||
The date and time at which the change was agreed.
|
||||||||||||
|
||||||||||||
|
||||||||||||
Specifies the fixed amount by which the option should be exercised expressed as notional amount.
|
||||||||||||
Specifies the fixed amount by which the option should be exercised expressed as notional amount.
|
||||||||||||
Specifies the amount by which the option should be exercised expressed as notional schedule.
|
||||||||||||
Specifies the fixed amount by which the option should be exercised expressed as number of options.
|
||||||||||||
Specifies the fixed amount by which the option should be exercised expressed as number of options.
|
||||||||||||
Specifies the fixed amount by which the option should be exercised express as number of units.
|
||||||||||||
Specifies the fixed amount by which the option should be exercised express as number of units.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
Indicates the original trade between the transferor and the remaining party.
|
||||||||||||
Indicates a reference to the implied trade (the "fee trade") that the associated novation fee based on.
|
||||||||||||
Element that is used to be able to make sense of the “new transaction” without requiring reference back to the “old transaction”.
|
||||||||||||
|
||||||||||||
This element corresponds to the applicability of the Full First Calculation Period as defined in the 2004 ISDA Novation Definitions, section 1.20.
|
||||||||||||
|
||||||||||||
Describes a change due to an index component being adjusted.
|
||||||||||||
|
||||||||||||
Identification of the underlying asset, using public and/or private identifiers.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
Standard code to indicate which type of credit line is being referred to - i.e.
|
||||||||||||
A unique identifier assigned by the matching service to each set of matched positions.
|
||||||||||||
Numeric score to represent the quality of the match.
|
||||||||||||
Identifies the reporting regime under which this data is reported.
|
||||||||||||
|
||||||||||||
Indicates the new trade between the transferee and the remaining party.
|
||||||||||||
Indicates a reference to the new trade between the transferee and the remaining party.
|
||||||||||||
This element corresponds to the non-Reliance section in the 2004 ISDA Novation Definitions, section 2.1 (c) (i).
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
The amount which represents the portion of the Old Contract being novated.
|
||||||||||||
The number of options which represent the portion of the Old Contract being novated.
|
||||||||||||
The number of options which represent the portion of the Old Contract being novated.
|
||||||||||||
|
||||||||||||
|
||||||||||||
Specifies the date that one party's legal obligations with regard to a trade are transferred to another party.
|
||||||||||||
Specifies the date the parties agree to assign or novate a Contract.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
The original trade details.
|
||||||||||||
Indicates the original trade between the transferor and the remaining party.
|
||||||||||||
The original qualified trade identifier.
|
||||||||||||
Indicates a reference to the original trade between the transferor and the remaining party.
|
||||||||||||
|
||||||||||||
A structure describing an option exercise event.
|
||||||||||||
A structure describing an option expiring event (i.e. passing its last exercise time and becoming worthless.)
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
Fully describes the original trade (prior to the exercise).
|
||||||||||||
Fully describes the original trade (prior to the exercise).
|
||||||||||||
|
||||||||||||
This may be used to describe why a trade was created.
|
||||||||||||
This may be used to describe why a package was created.
|
||||||||||||
This may be used to describe why a trade was created.
|
||||||||||||
|
||||||||||||
|
||||||||||||
A pointer style reference to a party identifier defined elsewhere in the document.
|
||||||||||||
|
||||||||||||
A pointer style reference to a party identifier defined elsewhere in the document.
|
||||||||||||
|
||||||||||||
|
||||||||||||
Specifies the Notional amount after the Change
|
||||||||||||
|
||||||||||||
Specifies the Notional amount after the Change
|
||||||||||||
Specifies the Notional amount after the Change
|
||||||||||||
|
||||||||||||
Specifies the Notional schedule after the Change
|
||||||||||||
Specifies the Number of Options after the Change.
|
||||||||||||
|
||||||||||||
Specifies the Number of Options after the Change.
|
||||||||||||
Specifies the Number of Options after the Change.
|
||||||||||||
Specifies the Number of Units
|
||||||||||||
|
||||||||||||
Specifies the Number of Units
|
||||||||||||
Specifies the Number of Units
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
This allows the acknowledging party to supply additional trade identifiers for a trade underlying a request relating to a business event.
|
||||||||||||
|
||||||||||||
This allows the acknowledging party to supply additional trade information about a trade underlying a request relating to a business event.
|
||||||||||||
Describes a payment made in settlement of the change.
|
||||||||||||
Describes a payment made in settlement of the change.
|
||||||||||||
Describes a payment made in settlement of the novation.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
Pricing information for the trade.
|
||||||||||||
Supporting information which may be produced to explain the clearing process status.
|
||||||||||||
|
||||||||||||
|
||||||||||||
The amount which represents the portion of the Old Contract not being novated.
|
||||||||||||
The number of options which represent the portion of the Old Contract not being novated.
|
||||||||||||
The number of options which represent the portion of the Old Contract not being novated.
|
||||||||||||
A pointer style reference to a party identifier defined elsewhere in the document.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
The supervisor/regulator to which this withdrawal applies
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
The trade that resulted from the physical settlement.
|
||||||||||||
The ID of the trade that resulted from the physical settlement.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
Specifies the Number of Units
|
||||||||||||
Reference to parties currently in this status, e.g. parties for which we are awaiting approval.
|
||||||||||||
Identifies the specific regulator or other supervisory body for which this data is produced.
|
||||||||||||
The regulator or other supervisory body the organization is registered with (e.g.
|
||||||||||||
The maximum allowed tenor for a trade under this limit.
|
||||||||||||
This may be used to describe why a trade was terminated.
|
||||||||||||
This may be used to describe why a trade was terminated.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
A full description of the amended trade.
|
||||||||||||
|
||||||||||||
|
||||||||||||
A full description of the amended trade (i.e. the trade after the amendment).
|
||||||||||||
Complete economics of the trade
|
||||||||||||
|
||||||||||||
|
||||||||||||
Identifier(s) for the trade which is the subject of the clearing request to which this status relates.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
Information about a trade.
|
||||||||||||
A pointer style reference to a party identifier defined elsewhere in the document.
|
||||||||||||
|
||||||||||||
A pointer style reference to a party identifier defined elsewhere in the document.
|
||||||||||||
|
||||||||||||
|
||||||||||||
When the clearing status changed to the current value.
|
||||||||||||
|
||||||||||||
|
Complex Type Summary |
||||||||||||
Abstract base type for all events.
|
||||||||||||
|
||||||||||||
Abstract base type for an extension/substitution point to customize FpML and add additional events.
|
||||||||||||
A structure indicating that the basket underlyer of the trade has changed due to client trading activity
|
||||||||||||
A type defining an event identifier issued by the indicated party.
|
||||||||||||
Abstract base type for non-negotiated trade change descriptions
|
||||||||||||
|
||||||||||||
A component of a clearing status report.
|
||||||||||||
A type that shows how multiple trades have been combined into a result.
|
||||||||||||
A type that identifies the type of trade amalgamation, for example netting or portfolio compression.
|
||||||||||||
A structure indicating that a trade has changed due to a corporate action
|
||||||||||||
A type that describes what type of corporate action occurred.
|
||||||||||||
A structure describing a credit limit with applicability constraints.
|
||||||||||||
A structure describing a basic credit limit.
|
||||||||||||
|
||||||||||||
A structure describing a declear event.
|
||||||||||||
A type that describes why a trade was removed from clearing.
|
||||||||||||
A post-trade event reference identifier allocated by a party.
|
||||||||||||
A structure that describes a proposed match between trades or post-trade event reports.
|
||||||||||||
|
||||||||||||
A structure describing the effect of a change to an index.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
A structure describing an option exercise.
|
||||||||||||
|
||||||||||||
A structure describing an option expiring (i.e. passing its last exercise time and becoming worthless.)
|
||||||||||||
A structure describing an option expiring.
|
||||||||||||
A structure that describes how an option settles into a physical trade.
|
||||||||||||
A type that provides identification for reporting regimes.
|
||||||||||||
A type that describes whether a trade is to be cleared.
|
||||||||||||
A type that describes what the requester would like to see done to implement the withdrawal, e.g.
|
||||||||||||
Provides identification information about a regulator or other supervisory body that an organization is registered with.
|
||||||||||||
A type that describes why a trade terminated.
|
||||||||||||
A structure describing a negotiated amendment.
|
||||||||||||
A structure describing a trade change.
|
||||||||||||
A structure describing a non-negotiated trade resulting from a market event.
|
||||||||||||
A structure describing a change to the size of a single leg or stream of a trade.
|
||||||||||||
A structure describing a change to the size of a single leg or stream of a trade.
|
||||||||||||
A structure describing a trade maturing.
|
||||||||||||
A structure describing a change to the size of a trade.
|
||||||||||||
A structure describing a novation.
|
||||||||||||
A bundle of trades collected together into a single unit for reporting.
|
||||||||||||
Identifying information for a tradePackage (a bundle of trades).
|
||||||||||||
Defines a type that allows trade identifiers and/or trade information to be represented for a trade.
|
||||||||||||
|
||||||||||||
A structure describing the removal of a trade from a service, such as a reporting service.
|
||||||||||||
A type that describes why a trade was withdrawn.
|
Element Group Summary |
||||||||||
A model group defining agreement and effective dates.
|
||||||||||
A model group holding information about compressions affecting this trade/event.
|
||||||||||
Choice between a trade and a post-trade event.
|
||||||||||
A model group holding valuation information for an event.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
The roles of the parties involved in the novation.
|
||||||||||
Documentation and other terms (such as date terms) specific to this novation event.
|
||||||||||
|
||||||||||
|
||||||||||
A structure that describes a potential match for a trade or event, together with descriptors of that match (quality, etc.).
|
||||||||||
A model group defining a payment structure.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
DEPRECATED.
|
||||||||||
Defines a model group that allows either details of an event or information about a trade to be provided.
|
||||||||||
Defines a model group that allows information about a trade to be represented.
|
<?xml version="1.0" encoding="utf-8"?>
<!-- edited with XMLSpy v2013 rel. 2 (x64) (http://www.altova.com) by Lyteck Lynhiavu (ISDA) -->
<!--
== Copyright (c) 2002-2014 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: 11250 $" xmlns="http://www.fpml.org/FpML-5/confirmation" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:fpml-annotation="http://www.fpml.org/annotation" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation="fpml-msg-5-7.xsd"/>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="eventIdentifier" type="BusinessEventIdentifier"/>
</xsd:sequence>
</xsd:complexType>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Abstract base type for an extension/substitution point to customize FpML and add additional events.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure indicating that the basket underlyer of the trade has changed due to client trading activity
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ChangeEvent">
<!--View Generation: Skipped an empty sequence.-->
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type defining an event identifier issued by the indicated party.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="PartyAndAccountReferences.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party identifier and optionally an account identifier defined elsewhere in the document. The party referenced has allocated the trade identifier.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Abstract base type for non-negotiated trade change descriptions
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractEvent">
<!--View Generation: Skipped an empty sequence.-->
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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 xml:lang="en">
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 xml:lang="en">
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:annotation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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: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:sequence>
<xsd:element minOccurs="0" name="requestedClearingAction" type="RequestedClearingAction"/>
<xsd:element minOccurs="0" name="requestedClearingOrganizationPartyReference" type="PartyReference"/>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type that shows how multiple trades have been combined into a result.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="compressionType" type="CompressionType"/>
<xsd:choice>
<xsd:sequence>
<xsd:element minOccurs="0" name="replacementTradeIdentifier" type="TradeIdentifier"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="originatingTradeIdentifier" type="TradeIdentifier"/>
</xsd:sequence>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation xml:lang="en">
This option is deprecated in favour of the first choice.
</xsd:documentation>
</xsd:annotation>
<xsd:element fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Deprecated in favor of replacementTradeIdentifier" minOccurs="0" name="replacementTradeId" type="TradeId"/>
<xsd:element fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Deprecated in favor of originatingTradeIdentifier" maxOccurs="unbounded" minOccurs="0" name="originatingTradeId" type="TradeId"/>
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type that identifies the type of trade amalgamation, for example netting or portfolio compression.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/compression-type" name="compressionTypeScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure indicating that a trade has changed due to a corporate action
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type that describes what type of corporate action occurred.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="limitId" type="LimitId"/>
<xsd:annotation>
<xsd:documentation>
The maximum allowed tenor for a trade under this limit. When this structure is used as part of a suspendCredit message, this tenor imposes a temporary tenor limit on allowed trade types.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a credit limit with applicability constraints.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="CreditLimitBase">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!--View Generation: SKIPPED CreditLimitReference - Unsupported -->
<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 is has been done.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type that describes why a trade was removed from clearing.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/declear-reason" name="declearReasonScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A post-trade event reference identifier allocated by a party. FpML does not define the domain values associated with this element. Note that the domain values for this element are not strictly an enumerated list.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure that describes a proposed match between trades or post-trade event reports.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing the effect of a change to an index.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ChangeEvent">
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="limitType" type="LimitType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Standard code to indicate which type of credit line is being referred to - i.e. IM, DV01, PV01, CS01, Notional, Clip Size, Notional, maximumOrderQuantity
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/credit-limit-type" name="creditLimitTypeScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing an option exercise. The OptionExercise type 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:complexContent>
<xsd:extension base="AbstractEvent">
<xsd:sequence>
<xsd:element minOccurs="0" name="optionSeller" type="PartyReference"/>
<xsd:choice>
<xsd:element name="originalTrade" type="Trade">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Fully describes the original trade (prior to the exercise).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:choice>
</xsd:choice>
<xsd:choice minOccurs="0">
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:choice>
<xsd:sequence>
<xsd:element minOccurs="0" name="notionalReference" type="NotionalReference"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the option should be exercised expressed as notional amount.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element minOccurs="0" name="notionalScheduleReference" type="NotionalReference"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the amount by which the option should be exercised expressed as notional schedule.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies the Notional schedule after the Change</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element minOccurs="0" name="numberOfOptionsReference" type="NumberOfOptionsReference"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the option should be exercised expressed as number of options.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies the Number of Options after the Change.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element minOccurs="0" name="numberOfUnitsReference" type="NumberOfUnitsReference"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the option should be exercised express as number of units.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing an option expiring (i.e. passing its last exercise time and becoming worthless.)
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractEvent">
<xsd:sequence>
<xsd:choice>
<xsd:element name="originalTrade" type="Trade">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Fully describes the original trade (prior to the exercise).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure that describes how an option settles into a physical trade.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element name="resultingTradeIdentifier" type="PartyTradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The ID of the trade that resulted from the physical settlement.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The trade that resulted from the physical settlement.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type that provides identification for reporting regimes.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="name" type="ReportingRegimeName">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identifies the reporting regime under which this data is reported. For example, Dodd-Frank, MiFID, HongKongOTCDRepository, ODRF
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" name="supervisorRegistration" type="SupervisorRegistrationIdentification">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identifies the specific regulator or other supervisory body for which this data is produced. For example, CFTC, SEC, UKFSA, ODRF, SFC, ESMA.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type that describes whether a trade is to be cleared.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/requested-clearing-action" name="requestedClearingActionScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type that describes what the requester would like to see done to implement the withdrawal, e.g. ExpungeRecords, RetainRecords.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/requested-withdrawal-action" name="requestedWithdrawalActionScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Provides identification information about a regulator or other supervisory body that an organization is registered with.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="supervisoryBody" type="SupervisoryBody">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The regulator or other supervisory body the organization is registered with (e.g. SEC).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/terminating-event" name="terminatingEventScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractEvent">
<xsd:sequence>
<xsd:element name="trade" type="Trade">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A full description of the amended trade (i.e. the trade after the amendment).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractEvent">
<xsd:sequence>
<xsd:choice>
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a non-negotiated trade resulting from a market event.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:element name="oldTradeIdentifier" type="PartyTradeIdentifier">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes a payment made in settlement of the change.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a change to the size of a single leg or stream of a trade.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:element name="priceReference" type="Reference"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identification of the underlying asset, using public and/or private identifiers.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a change to the size of a single leg or stream of a trade.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
</xsd:choice>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing a change to the size of a trade.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="TradeChangeBase">
<xsd:sequence>
<xsd:choice>
<xsd:group fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="The model could not provide support for linking notionals with product legs. Also, there was limitation in the existing increase and termination events which don’t allow the reporting of both change of units or change of notional amount as required for dividend swaps, for example. Instead, sizeChange, should be used." ref="TradeNotionalChange.model"/>
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractEvent">
<xsd:sequence>
<xsd:choice>
<!--View Generation: Removed a degenerate choice.-->
<xsd:sequence>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Choice between identification and representation of the old contract.
</xsd:documentation>
</xsd:annotation>
</xsd:sequence>
<xsd:sequence>
</xsd:sequence>
</xsd:choice>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The dates and times associated with the novation event.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The amounts novated and remaining. These are optional in some reporting views because when reporting standalone fee trades this information would be duplicated.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Documentation and other terms relating to the novation.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes a payment made in settlement of the novation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A bundle of trades collected together into a single unit for reporting.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="packageHeader" type="TradePackageHeader"/>
<xsd:choice>
</xsd:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">A container for approval states in the workflow.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identifying information for a tradePackage (a bundle of trades).
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="packageIdentifier" type="IssuerTradeId"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
This may be used to describe why a package was created. This can be used to provide context for a newly created package that is not part of a post-trade event. For example, it can report that the package was created as a result of netting activity, or due to a transfer, an allocation process, etc.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines a type that allows trade identifiers and/or trade information to be represented for a trade.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:element name="originatingEvent" type="OriginatingEvent">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This may be used to describe why a trade was created. This can be used to provide context for a newly created trade that is not part of a post-trade event. For example, it can report that the trade was created as a result of netting activity, or due to a transfer, an allocation process, etc. Omitting this implies that the trade record was created as a result of a negotiated new trade.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<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:choice>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="partyTradeIdentifier" type="PartyTradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This allows the acknowledging party to supply additional trade identifiers for a trade underlying a request relating to a business event.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeInformation" type="PartyTradeInformation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This allows the acknowledging party to supply additional trade information about a trade underlying a request relating to a business event.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure describing the removal of a trade from a service, such as a reporting service.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reportingRegime" type="ReportingRegimeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The supervisor/regulator to which this withdrawal applies
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">A type that describes why a trade was withdrawn.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/withdrawal-reason" name="withdrawalReasonScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The additionalEvent element is an extension/substitution point to customize FpML and add additional events.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes a change due to change in composition of basket underlyer
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Abstract substitutable place holder for specific change details.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes a change due to an index component being adjusted.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A model group defining agreement and effective dates.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="agreementDate" type="xsd:date">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The date and time at which the negotiated change to the terms of the original contract was agreed, such as via telephone or electronic trading system (i.e., agreement date/time).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A model group holding information about compressions affecting this trade/event.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="compressionActivity" type="CompressionActivity">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
<xsd:choice>
<xsd:element name="tradePackage" type="TradePackage"/>
<xsd:sequence>
</xsd:sequence>
<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:sequence>
<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:annotation>
<xsd:documentation xml:lang="en">
A structure describing an option expiring event (i.e. passing its last exercise time and becoming worthless.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<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:annotation>
<xsd:documentation xml:lang="en">
The additionalEvent element is an extension/substitution point to customize FpML and add additional events.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A model group holding valuation information for an event.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="quote" type="BasicQuotation">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:choice>
<xsd:element name="feeTradeIdentifier" type="PartyTradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates a reference to the implied trade (the "fee trade") that the associated novation fee based on. This is equivalent to the new trade that is created by the novation (between the transferee and the remaining party), but is between the transferor and the transferee.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates the original trade between the transferor and the remaining party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<xsd:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Choice between identification and representation of the new contract.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates a reference to the new trade between the transferee and the remaining party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates the new trade between the transferee and the remaining party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
</xsd:group>
<xsd:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Choice for expressing the novated amount as either a money amount, number of options, or number of units, according the the financial product which is being novated.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="novatedAmount" type="Money">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The amount which represents the portion of the Old Contract being novated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The amount which represents the portion of the Old Contract not being novated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="novatedNumberOfOptions" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The number of options which represent the portion of the Old Contract being novated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The number of options which represent the portion of the Old Contract not being novated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="novatedNumberOfUnits" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The number of options which represent the portion of the Old Contract being novated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The number of options which represent the portion of the Old Contract not being novated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:group>
<xsd:sequence>
<xsd:element name="novationDate" type="xsd:date">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the date that one party's legal obligations with regard to a trade are transferred to another party. It corresponds to the Novation Date section of the 2004 ISDA Novation Definitions, section 1.16.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">The date and time at which the change was agreed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the date the parties agree to assign or novate a Contract. If this element is not specified, the novationContractDate will be deemed to be the novationDate. It corresponds to the Novation Trade Date section of the 2004 ISDA Novation Definitions, section 1.17.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The roles of the parties involved in the novation.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="transferor" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party identifier defined elsewhere in the document. In a three-way novation the party referenced is the Transferor (outgoing party) in the novation. The Transferor means a party which transfers by novation to a Transferee all of its rights, liabilities, duties and obligations with respect to a Remaining Party. In a four-way novation the party referenced is Transferor 1 which transfers by novation to Transferee 1 all of its rights, liabilities, duties and obligations with respect to Transferor 2. ISDA 2004 Novation Term: Transferor (three-way novation) or Transferor 1 (four-way novation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party identifier defined elsewhere in the document. In a three-way novation the party referenced is the Transferee (incoming party) in the novation. Transferee means a party which accepts by way of novation all rights, liabilities, duties and obligations of a Transferor with respect to a Remaining Party. In a four-way novation the party referenced is Transferee 1 which accepts by way of novation the rights, liabilities, duties and obligations of Transferor 1. ISDA 2004 Novation Term: Transferee (three-way novation) or Transferee 1 (four-way novation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party identifier defined elsewhere in the document. In a five-way novation the party referenced is the Transferee's legal entity that is involved in the settlement of the fee leg of the novation transaction (this might be a different legal entity than the one that assumes the novation trade). NB: this element has been added pending confirmation of the business need/context in which it would be used, and might not appear in a subsequent draft of this schema.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party identifier defined elsewhere in the document. In a three-way novation the party referenced is the Remaining Party in the novation. Remaining Party means a party which consents to a Transferor's transfer by novation and the acceptance thereof by the Transferee of all of the Transferor's rights, liabilities, duties and obligations with respect to such Remaining Party under and with respect of the Novated Amount of a transaction. In a four-way novation the party referenced is Transferor 2 per the ISDA definition and acts in the role of a Transferor. Transferor 2 transfers by novation to Transferee 2 all of its rights, liabilities, duties and obligations with respect to Transferor 1. ISDA 2004 Novation Term: Remaining Party (three-way novation) or Transferor 2 (four-way novation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party identifier defined elsewhere in the document. This element is not applicable in a three-way novation and should be omitted. In a four-way novation the party referenced is Transferee 2. Transferee 2 means a party which accepts by way of novation the rights, liabilities, duties and obligations of Transferor 2. ISDA 2004 Novation Term: Transferee 2 (four-way novation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Documentation and other terms (such as date terms) specific to this novation event.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="fullFirstCalculationPeriod" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This element corresponds to the applicability of the Full First Calculation Period as defined in the 2004 ISDA Novation Definitions, section 1.20.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Element that is used to be able to make sense of the “new transaction” without requiring reference back to the “old transaction”. In the case of interest rate products there are potentially 2 “first period start dates” to reference – one with respect to each party to the new transaction. For Credit Default Swaps there is just the one with respect to the party that is the fixed rate payer.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
This element corresponds to the non-Reliance section in the 2004 ISDA Novation Definitions, section 2.1 (c) (i). The element appears in the instance document when non-Reliance is applicable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
This element should be specified if one or more of either a Credit Event Notice, Notice of Publicly Available Information, Notice of Physical Settlement or Notice of Intended Physical Settlement, as applicable, has been delivered by or to the Transferor or the Remaining Party. The type of notice or notices that have been delivered should be indicated by setting the relevant boolean element value(s) to true. The absence of the element means that no Credit Event Notice, Notice of Publicly Available Information, Notice of Physical Settlement or Notice of Intended Physical Settlement, as applicable, has been delivered by or to the Transferor or the Remaining Party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="contractualDefinitions" type="ContractualDefinitions">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The definitions (such as those published by ISDA) that will define the terms of the novation transaction.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="contractualTermsSupplement" type="ContractualTermsSupplement">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A contractual supplement (such as those published by ISDA) that will apply to the trade.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:choice>
<xsd:element maxOccurs="unbounded" name="oldTradeIdentifier" type="PartyTradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates a reference to the original trade between the transferor and the remaining party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates the original trade between the transferor and the remaining party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<xsd:choice>
<xsd:element name="exerciseAction" type="ExerciseActionEnum"/>
<xsd:sequence>
<xsd:element name="exerciseInNotionalAmount" type="Money">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the option should be exercised expressed as notional amount.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="exerciseInNumberOfOptions" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the option should be exercised expressed as number of options.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies the Number of Options after the Change.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="exerciseInNumberOfUnits" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the option should be exercised express as number of units.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A structure that describes a potential match for a trade or event, together with descriptors of that match (quality, etc.).
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="matchId" type="MatchId">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A unique identifier assigned by the matching service to each set of matched positions.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type used to record the details of a difference between two sides of a business event.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Numeric score to represent the quality of the match.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="payment" type="Payment">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes a payment made in settlement of the change. Normally there will be a single fee, but there could be additional payments such as principal exchanges resulting from the termination.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="notionalScheduleReference" type="NotionalReference"/>
<!-- in the future perhaps this should allow a notional schedule to be put in here instead of a single value -->
</xsd:sequence>
</xsd:group>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
<xsd:group fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="The model could not provide support for linking notionals with product legs. Also, there was limitation in the existing increase and termination events which don’t allow the reporting of both change of units or change of notional amount as required for dividend swaps, for example. Instead, sizeChange, should be used." name="TradeNotionalChange.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
DEPRECATED. A structure describing a change to the trade notional.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="changeInNotionalAmount" type="NonNegativeMoney">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the Notional Amount changes. The direction of the change (increase or decrease) is specified by the event type (Termination => reduction, Increase => greater.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="changeInNumberOfOptions" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the Number of Options changes
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies the Number of Options after the Change.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="changeInNumberOfUnits" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies the fixed amount by which the Number of Units changes
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:group>
<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:sequence>
<xsd:element minOccurs="0" name="originatingEvent" type="OriginatingEvent">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This may be used to describe why a trade was created. This can be used to provide context for a newly created trade that is not part of a post-trade event. For example, it can report that the trade was created as a result of netting activity, or due to a transfer, an allocation process, etc. Omitting this implies that the trade record was created as a result of a negotiated new trade.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines a model group that allows information about a trade to be represented.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="tradeReferenceInformation" type="TradeReferenceInformation">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
</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.
|