All Element Summary |
||||||||
actionType (defined in ReportingRegime complexType) |
Reports a regulator-specific code for the action associated with this submission.
|
|||||||
actionType (defined in ReportingRegimeIdentifier complexType) |
Reports a regulator-specific code for the action associated with this submission.
|
|||||||
additionalData (defined in Reason complexType) |
Any string of additional data that may help the message processor, for example in a rejection message this might contain a code value or the text of any one of the messages (within a CDATA section).
|
|||||||
|
Date and time of the admission to trading on the trading venue or the date and time when the instrument was first traded or an order or quote was first received by the trading venue.
|
||||||||
|
||||||||
|
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
|
||||||||
|
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
|
||||||||
|
Date and time the issuer has approved admission to trading or trading in its financial instruments on a trading venue.
|
||||||||
|
||||||||
|
The party referenced is specified in the related Confirmation as Barrier Determination Agent.
|
||||||||
base64Binary (defined in AdditionalData complexType) |
Provides extra information as binary contents coded in base64.
|
|||||||
|
For on-facility trades, indicator of whether an election has been made to report the swap transaction as a block transaction by the reporting counterparty or as calculated by either the swap data repository acting on behalf of the reporting counterparty or by using a third party.
|
||||||||
|
Describes the status with respect to clearing (e.g.
|
||||||||
|
Describes the status with respect to clearing (e.g.
|
||||||||
|
Specifies whether this party posts collateral.
|
||||||||
|
Specifies whether this party posts collateral.
|
||||||||
|
Provides a name, code, or other identifier for the collateral portfolio to which this belongs.
|
||||||||
|
Provides a name, code, or other identifier for the initial margin collateral portfolio to which this belongs.
|
||||||||
|
Provides a name, code, or other identifier for the variation margin collateral portfolio to which this belongs.
|
||||||||
|
Specifies whether this trade is a result of compression activity.
|
||||||||
|
Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
||||||||
|
Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
||||||||
|
Reports a regulator-specific code classifying the currency pair in the trade into risk categories such as Major Currencies or Emerging Markets.
|
||||||||
description (defined in Reason complexType) |
Plain English text describing the associated error condition
|
|||||||
endUserException (defined in EndUserException.model group) |
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization, i.e. whether there is an exemption from clearing.
|
|||||||
|
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization because the "End User Exception" was invoked.
|
||||||||
|
Specifies a reason that the trade is exempted from a clearing requirement.
|
||||||||
entityClassification (defined in ReportingRegime complexType) |
Indicates the category or classification or business role of the organization referenced by the partyTradeInformation with respect to this reporting regime, for example Financial, NonFinancial etc.
|
|||||||
|
Indicates the category or classification or business role of the organization referenced by the partyTradeInformation with respect to this reporting regime, for example Financial, NonFinancial etc.
|
||||||||
|
Indicates whether the counterparty exceeds the volume threshold above which trades are required to be cleared.
|
||||||||
|
Trade execution date time, for example as provided by a central execution facility.
|
||||||||
|
Trade execution date time, for example as provided by a central execution facility.
|
||||||||
|
Used to describe how the trade was executed, e.g. via voice or electronically.
|
||||||||
|
Used to describe how the trade was executed, e.g. via voice or electronically.
|
||||||||
|
Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
|
||||||||
|
Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
|
||||||||
|
||||||||
hexadecimalBinary (defined in AdditionalData complexType) |
Provides extra information as binary contents coded in hexadecimal.
|
|||||||
|
DEPRECATED.
|
||||||||
|
Specifies whether the trade is anticipated to be allocated.
|
||||||||
|
Specifies whether the trade is anticipated to be allocated.
|
||||||||
|
Specifies whether the trade is anticipated to be cleared via a derivative clearing organization
|
||||||||
|
Specifies whether the trade is anticipated to be cleared via a derivative clearing organization
|
||||||||
|
Whether the transaction reduces risk in an objectively measurable way.
|
||||||||
|
Used to report whether the trade is in dispute
|
||||||||
|
||||||||
|
||||||||
|
Whether the transaction falls within the scope of activity but is exempted from reporting under [Securities Financing Transactions Regulation]
|
||||||||
|
||||||||
largeSizeTrade (defined in BlockTrade.model group) |
For off-facility trades, specifies whether the sender of this trade considers it to be a large notional trade or block trade for reporting purposes, and thus eligible for delayed public reporting.
|
|||||||
|
A value indicating the location of the problem within the subject message.
|
||||||||
|
Whether the particular trade type in question is required by this regulator to be cleared.
|
||||||||
|
Whether the particular product must be executed on a SEF or DCM.
|
||||||||
|
Specifies whether the party invoked exception to not execute the trade on facility such as SEF and DCM even though the particular product is mandated to execute on a SEF.
|
||||||||
mimeType (defined in AdditionalData complexType) |
Indicates the type of media used to provide the extra information. mimeType is used to determine the software product(s) that can read the content.
|
|||||||
name (defined in ReportingRegime complexType) |
Identifies the reporting regime under which this data is reported.
|
|||||||
name (defined in ReportingRegimeIdentifier complexType) |
Identifies the reporting regime under which this data is reported.
|
|||||||
|
Indicates that the trade has price-affecting characteristics in addition to the standard real-time reportable terms.
|
||||||||
|
Indicates that the trade has price-affecting characteristics in addition to the standard real-time reportable terms.
|
||||||||
|
How the notional amount should be reported for the reporting regime.
|
||||||||
|
Indicates that the price does not reflect the current market.
|
||||||||
|
Indicates that the price does not reflect the current market.
|
||||||||
onBehalfOf (in dataDocument) |
Indicates which party (and accounts) a trade is being processed for.
|
|||||||
|
When an order was first generated, as recorded for the first time when it was first entered by a person or generated by a trading algorithm (i.e., the first record of the order).
|
||||||||
|
||||||||
|
Unique identifier of the order that generated the trade package.
|
||||||||
|
The time when an order is submitted by a market participant to an execution facility, as recorded based on the timestamp of the message that was sent by the participant.
|
||||||||
originalMessage (defined in AdditionalData complexType) |
Provides the content of the original message.
|
|||||||
|
||||||||
|
Information about the trade package if any that the trade originated from.
|
||||||||
|
The trade id of the trade(s) upon which this was based, for example the ID of the trade that was submitted for clearing if this is a cleared trade, or of the original trade if this was novated or cancelled and rebooked, or the list of trades that were netted or compressed together in the case of a compression event.
|
||||||||
|
Classification of the OTC transaction.
|
||||||||
|
Unique identifier of the trade package.
|
||||||||
|
Specifies the package type.
|
||||||||
|
Indicates the category or classification or business role of a trade party with respect to this reporting regime, for example Financial, NonFinancial, Dealer, Non-Dealer, LocalParty, etc.
|
||||||||
|
The name of the portfolio together with the party that gave the name.
|
||||||||
|
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.
|
||||||||
|
||||||||
|
The trade reference identifier(s) allocated to the trade by the parties involved.
|
||||||||
|
The trade reference identifier(s) allocated to the trade by the parties involved.
|
||||||||
|
||||||||
|
Additional trade information that may be provided by each involved party.
|
||||||||
|
An arbitary grouping of trade references (and possibly other portfolios).
|
||||||||
|
||||||||
postPricedIndicator (defined in ReportingRegime complexType) |
|
|||||||
|
Reports that this trade was executed prior to the enactment of the relevant reporting regulation.
|
||||||||
|
Indicates which product within a strategy this ID is associated with.
|
||||||||
|
Describes why the price of this trade does not reflect the current market price.
|
||||||||
|
Describes why the price of this trade does not reflect the current market price.
|
||||||||
|
Deprecated: The USIs of the components of this trade, when this trade contains a strategy.
|
||||||||
|
||||||||
|
When the public report of this was created or received by this party.
|
||||||||
|
When the public report of this was most recently corrected or corrections were sent or received by this party.
|
||||||||
|
When the public report of this was first accepted for submission to a regulator.
|
||||||||
|
A machine interpretable error code.
|
||||||||
|
The ID assigned by the regulator (e.g.
|
||||||||
relatedParty (defined in ReportingRegime complexType) |
This may be used to identify one or more parties that perform a role within the transaction.
|
|||||||
|
This may be used to identify one or more parties that perform a role within the transaction.
|
||||||||
|
This may be used to identify one or more parties that perform a role within the transaction.
|
||||||||
|
||||||||
reportingPurpose (defined in ReportingRegime complexType) |
The reason this message is being sent, for example Snapshot, PET, Confirmation, RealTimePublic.
|
|||||||
|
Allows the organization to specify which if any relevant regulators or other supervisory bodies this is relevant for, and what reporting rules apply.
|
||||||||
|
Allows the organization to specify which if any relevant regulators or other supervisory bodies this is relevant for, and what reporting rules apply.
|
||||||||
reportingRole (defined in ReportingRegime complexType) |
Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
|
|||||||
reportingRole (defined in ReportingRegimeIdentifier complexType) |
Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
|
|||||||
|
Date and time of the request for admission to trading on the trading venue.
|
||||||||
|
Whether the issuer of the financial instrument has requested or approved the trading or admission to trading of their financial instruments on a trading venue.
|
||||||||
|
The trade id of a resulting trade (beta or gamma trade) that resulted from this trade during a clearing or similar operation (e.g. prime brokerage).
|
||||||||
seniority (in productSummary) |
DEPRECATED.
|
|||||||
|
Sequence number is used to identify the ordinal position of the trade within the enclosing package, e.g. number 1 of 3, 2 of 3, etc, where 3 equals package size.
|
||||||||
|
Added to support CFTC Amendments to Part 43/45 (Published November 2020)
|
||||||||
|
||||||||
|
Classification of the transaction as a short sale or not and, if short, of the type of transaction.
|
||||||||
|
Size of the trade package.
|
||||||||
string (defined in AdditionalData complexType) |
Provides extra information as string.
|
|||||||
supervisorRegistration (defined in ReportingRegime complexType) |
Identifies the specific regulator or other supervisory body for which this data is produced.
|
|||||||
supervisorRegistration (defined in ReportingRegime complexType) |
Identifies the specific regulator or other supervisory body for which this data is produced.
|
|||||||
supervisorRegistration (defined in ReportingRegimeIdentifier complexType) |
Identifies the specific regulator or other supervisory body for which this data is produced.
|
|||||||
supervisorRegistration (defined in ReportingRegimeIdentifier complexType) |
Identifies the specific regulator or other supervisory body for which this data is produced.
|
|||||||
supervisoryBody (defined in SupervisorRegistration.model group) |
The regulator or other supervisory body the organization is registered with (e.g.
|
|||||||
|
Date and time when the financial instrument ceases to be traded or to be admitted to trading on the trading venue.
|
||||||||
|
Other timestamps for this trade.
|
||||||||
|
Allows timing information about a trade to be recorded.
|
||||||||
|
Allows timing information about a trade to be recorded.
|
||||||||
|
An element that allows the full details of the trade to be used as a mechanism for identifying the trade for which the post-trade event pertains
|
||||||||
trade (in dataDocument) |
The root element in an FpML trade document.
|
|||||||
|
The trade date.
|
||||||||
|
The information on the trade which is not product specific, e.g. trade date.
|
||||||||
tradeId (defined in TradeIdentifier complexType) |
|
|||||||
|
||||||||
|
||||||||
tradeId (in versionedTradeId) |
|
|||||||
|
Additional trade information that is shared by all parties.
|
||||||||
|
Indicates how the parties to the trade (the counterparties) are related to each other with respect to this reporting regime, e.g.
|
||||||||
|
A container since an individual trade can be referenced by two or more different partyTradeIdentifier elements - each allocated by a different party.
|
||||||||
|
||||||||
|
Classification of the pre-trade waiver, if any, that the transaction was executed under.
|
||||||||
|
||||||||
|
||||||||
|
||||||||
|
||||||||
|
||||||||
|
A reference identifying a rule within a validation scheme
|
||||||||
|
||||||||
|
Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
||||||||
|
Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
||||||||
|
A trade identifier accompanied by a version number.
|
||||||||
Complex Type Summary |
||||||||||
|
Provides extra information not represented in the model that may be useful in processing the message i.e. diagnosing the reason for failure.
|
||||||||||
|
Information about whether and when a product was admitted to trading on a facility.
|
||||||||||
|
Code that describes what type of allocation applies to the trade.
|
||||||||||
|
The reason a trade is exempted from a clearing mandate.
|
||||||||||
|
The current status value of a clearing request.
|
||||||||||
|
A type used to represent the type of mechanism that can be used to confirm a trade.
|
||||||||||
|
A type containing a code representing the risk classification of a currency pair, as specified by a regulator.
|
||||||||||
|
A type defining a content model that is backwards compatible with older FpML releases and which can be used to contain sets of data without expressing any processing intention.
|
||||||||||
|
The abstract base type from which all FpML compliant messages and documents must be derived.
|
||||||||||
|
A type describing the entity of a party, for example Financial, NonFinancial etc.
|
||||||||||
|
A type defining the trade execution date time and the source of it.
|
||||||||||
|
A type used to represent the type of market where a trade can be executed.
|
||||||||||
|
A type used to represent the type of market where a trade can be executed.
|
||||||||||
|
How a notional is to be reported for this reporting regime.
|
||||||||||
|
A type that an identifier for an order.
|
||||||||||
|
A type that an order's identifier(s).
|
||||||||||
|
Indicator as to the type of transaction in accordance with Articles 20(3)(a) and 21(5)(a) of Regulation (EU) 600/2014.
|
||||||||||
|
Summary information about a trade package.
|
||||||||||
|
A type that describes what thpe of package this is, e.g.
|
||||||||||
|
A type that specifies the classification of a party.
|
||||||||||
|
A type to represent a portfolio name for a particular party.
|
||||||||||
|
A type containing a code representing how two parties are related, e.g.
|
||||||||||
|
A type defining one or more trade identifiers allocated to the trade by a party.
|
||||||||||
|
A type containing multiple partyTradeIdentifier.
|
||||||||||
|
A type defining party-specific additional information that may be recorded against a trade.
|
||||||||||
|
A type representing an arbitary grouping of trade references.
|
||||||||||
|
The data type used for portfolio names.
|
||||||||||
|
The reason a trade's price does not reflect the current market price.
|
||||||||||
|
Provides a lexical location (i.e. a line number and character for bad XML) or an XPath location (i.e. place to identify the bad location for valid XML).
|
||||||||||
|
Deprecated: A type defining a USI for the a subproduct component of a strategy.
|
||||||||||
|
Summary information about the product that was traded.
|
||||||||||
|
A type defining a content model for describing the nature and possible location of a error within a previous message.
|
||||||||||
|
Defines a list of machine interpretable error codes.
|
||||||||||
|
An ID assigned by a regulator to an organization registered with it.
|
||||||||||
|
How a Boolean value is to be reported for this regulator.
|
||||||||||
|
A type containing a code representing the level at which this is reported (e.g.
|
||||||||||
|
A value that explains the reason or purpose that information is being reported.
|
||||||||||
|
Provides information about how the information in this message is applicable to a regulatory reporting process.
|
||||||||||
|
A type that provides identification for reporting regimes.
|
||||||||||
|
A type containing a code representing the role of a party in a report, e.g. the originator, the recipient, the counterparty, etc.
|
||||||||||
|
A short sale concluded by an investment firm on its own behalf or on behalf of a client, as described in Article 11.
|
||||||||||
|
Provides information about a regulator or other supervisory body that an organization is registered with.
|
||||||||||
|
The type or meaning of a timestamp.
|
||||||||||
|
A type defining an FpML trade.
|
||||||||||
|
A scheme used to categorize positions.
|
||||||||||
|
A type defining trade related information which is not product specific.
|
||||||||||
|
A type defining a trade identifier issued by the indicated party.
|
||||||||||
|
A type defining a trade identifier with a reference to the party that this trade is associated with.
|
||||||||||
|
A type defining additional information that may be recorded against a trade.
|
||||||||||
|
Allows timing information about when a trade was processed and reported to be recorded.
|
||||||||||
|
Summary information about the trade.
|
||||||||||
|
A generic trade timestamp
|
||||||||||
|
Indication as to whether the transaction was executed under a pre-trade waiver in accordance with Articles 4 and 9 of Regulation (EU) 600/2014.
|
||||||||||
|
A type holding a structure that is unvalidated
|
||||||||||
|
A reference identifying a rule within a validation scheme.
|
||||||||||
|
A type used to represent the type of mechanism that can be used to verify a trade.
|
||||||||||
|
Trade Id with Version Support
|
||||||||||
Simple Type Summary |
||||||
|
||||||
Element Group Summary |
||||||||||
|
||||||||||
|
||||||||||
|
Types that globally and uniquely identify trade across counterparties, for regulatory reporting and other purposes.
|
||||||||||
|
Provides information about a regulator or other supervisory body that an organization is registered with.
|
||||||||||
|
Identification options for trades
|
||||||||||
|
Choice between identification and representation of trade execution.
|
||||||||||
|
||||||||||
Attribute Group Summary |
||||||||||
|
Set of attributes that define versioning information.
|
||||||||||
|
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2022-2024 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="trnsp" ecore:package="org.fpml.transparency" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/transparency" version="$Revision: 14891 $" xmlns="http://www.fpml.org/FpML-5/transparency" 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-asset-5-13.xsd"/>
</xsd:simpleType>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides extra information not represented in the model that may be useful in processing the message i.e. diagnosing the reason for failure.
</xsd:documentation>
<xsd:element minOccurs="0" name="mimeType" type="MimeType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates the type of media used to provide the extra information. mimeType is used to determine the software product(s) that can read the content. MIME Types are described in RFC 2046.
</xsd:documentation>
<xsd:element name="string" type="NonEmptyString">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides extra information as string. In case the extra information is in XML format, a CDATA section must be placed around the source message to prevent its interpretation as XML content.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides extra information as binary contents coded in hexadecimal.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides extra information as binary contents coded in base64.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Information about whether and when a product was admitted to trading on a facility.
</xsd:documentation>
<xsd:element minOccurs="0" name="requested" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Whether the issuer of the financial instrument has requested or approved the trading or admission to trading of their financial instruments on a trading venue.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Date and time of the request for admission to trading on the trading venue.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Date and time the issuer has approved admission to trading or trading in its financial instruments on a trading venue.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Date and time of the admission to trading on the trading venue or the date and time when the instrument was first traded or an order or quote was first received by the trading venue.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Date and time when the financial instrument ceases to be traded or to be admitted to trading on the trading venue.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Code that describes what type of allocation applies to the trade. Options include Unallocated, PreAllocation, PostAllocation.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/allocation-reporting-status" name="allocationReportingStatusScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">The current status value of a clearing request.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/clearing-status" name="clearingStatusScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The reason a trade is exempted from a clearing mandate.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/clearing-exception-reason" name="clearingExceptionReasonScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type used to represent the type of mechanism that can be used to confirm a trade.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/confirmation-method" name="confirmationMethodScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type containing a code representing the risk classification of a currency pair, as specified by a regulator.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/esma-currency-pair-classification" name="currencyPairClassificationScheme" type="NonEmptyURI" use="optional"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining a content model that is backwards compatible with older FpML releases and which can be used to contain sets of data without expressing any processing intention.
</xsd:documentation>
<xsd:complexContent>
<xsd:extension base="Document">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:sequence>
</xsd:sequence>
<xsd:element minOccurs="0" name="onBehalfOf" type="OnBehalfOf">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates which party (and accounts) a trade is being processed for.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The abstract base type from which all FpML compliant messages and documents must be derived.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type describing the entity of a party, for example Financial, NonFinancial etc.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/entity-classification" name="entityClassificationScheme" type="NonEmptyURI" use="optional"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining the trade execution date time and the source of it. For use inside containing types which already have a Reference to a Party that has assigned this trade execution date time.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="xsd:dateTime">
</xsd:simpleContent>
<xsd:attribute name="executionDateTimeScheme" type="NonEmptyURI">
</xsd:extension>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identification of the source (e.g. clock id) generating the execution date time.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type used to represent the type of market where a trade can be executed.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/execution-type" name="executionTypeScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type used to represent the type of market where a trade can be executed.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/execution-venue-type" name="executionVenueTypeScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
How a notional is to be reported for this reporting regime. E.g. for ESMA EMIR, it would be Nominal or Monetary Amount
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/notional-type" name="notionalTypeScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:simpleContent>
</xsd:simpleContent>
<xsd:annotation>
</xsd:annotation>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicator as to the type of transaction in accordance with Articles 20(3)(a) and 21(5)(a) of Regulation (EU) 600/2014.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/esma-mifir-otc-classification" name="otcClassificationScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:element minOccurs="0" name="packageIdentifier" type="IssuerTradeId">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Unique identifier of the order that generated the trade package.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies the package type. Domain is defined within the packageTypeScheme and includes values such as: Butterfly, CalendarRoll, CalendarSpread, etc. The complete list is available at: http://www.fpml.org/coding-scheme/package-type
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Sequence number is used to identify the ordinal position of the trade within the enclosing package, e.g. number 1 of 3, 2 of 3, etc, where 3 equals package size. It’s intended to assist with ordering and reconciliation.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type that describes what thpe of package this is, e.g. Butterfly.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/package-type" name="packageTypeScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type that specifies the classification of a party.
</xsd:documentation>
<xsd:element name="partyReference" type="PartyReference">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A pointer style reference to a party identifier defined elsewhere in the document. The party referenced has the classification in the associated "entityClassification" element below.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates the category or classification or business role of the organization referenced by the partyTradeInformation with respect to this reporting regime, for example Financial, NonFinancial etc.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type to represent a portfolio name for a particular party.
</xsd:documentation>
<xsd:element minOccurs="0" name="partyReference" type="PartyReference">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A pointer style reference to a party identifier defined elsewhere in the document. The party referenced has allocated the trade identifier.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type containing a code representing how two parties are related, e.g. Affiliated, Intragroup, None.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/party-relationship-type" name="partyRelationshipTypeScheme" type="NonEmptyURI" use="optional"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining one or more trade identifiers allocated to the trade by a party. A link identifier allows the trade to be associated with other related trades, e.g. trades forming part of a larger structured transaction. It is expected that for external communication of trade there will be only one tradeId sent in the document per party.
</xsd:documentation>
<xsd:complexContent>
<xsd:extension base="TradeIdentifier">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="resultingTradeId" type="TradeIdentifierExtended">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The trade id of a resulting trade (beta or gamma trade) that resulted from this trade during a clearing or similar operation (e.g. prime brokerage). For new implementations, the use of the "linkedTrade" element is preferred.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The trade id of the trade(s) upon which this was based, for example the ID of the trade that was submitted for clearing if this is a cleared trade, or of the original trade if this was novated or cancelled and rebooked, or the list of trades that were netted or compressed together in the case of a compression event. The originatingEvent will explain why the trade was created; the existence and number of originatingTradeId elements should correspond to the originatingEvent, and they should be interpreted using that field. If the trade is inside a business event structure (such as a novation or a compression event) this element shuld not be populated; instead the event shoudl be used to represent the other trades. For new implementations, the use of the "linkedTrade" element is preferred.
</xsd:documentation>
<xsd:element fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Added in error. Leftover from earlier proposal" maxOccurs="unbounded" minOccurs="0" name="productComponentIdentifier" type="ProductComponentIdentifier">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Deprecated: The USIs of the components of this trade, when this trade contains a strategy.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">A type containing multiple partyTradeIdentifier.</xsd:documentation>
</xsd:annotation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
</xsd:sequence>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining party-specific additional information that may be recorded against a trade.
</xsd:documentation>
<xsd:group minOccurs="0" ref="PartyAndAccountReferences.model">
</xsd:sequence>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies that party that has ownership of this information. For shared trade information, this will reference the originator of the date (for example, an execution facility or clearinghouse).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
This may be used to identify one or more parties that perform a role within the transaction. If this is within a partyTradeInformation block, the related party performs the role with respect to the party identifie by the "partyReference" in the partyTradeInformation block.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Trade execution date time, for example as provided by a central execution facility. Normally this refers to the original execution time of the trade, not the execution time of any post-trade events that may have affeted it. However, in the case of a post trade event that reports the new version of the trade (for example, the novation trade in an novation event, or the amended trade in an amendment event), the execution date time may contain the time that the newly created or modified trade was created or modified.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Allows timing information about a trade to be recorded.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be allocated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be cleared via a derivative clearing organization
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Describes the status with respect to clearing (e.g. AwaitingAcceptance, Pending, Accepted, Rejected, etc.)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether this party posts collateral. For Recordkeeping, the collateralization type refers to collateral that is posted by this firm, and One-Way is not meaningful. In other words, if the collateralization type is Full, this trade is fully collateralized by this party. For Transparency view, the options include Full, Partial, Uncollateralized, and One-Way.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides a name, code, or other identifier for the collateral portfolio to which this belongs.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides a name, code, or other identifier for the initial margin collateral portfolio to which this belongs. Added to support CFTC Amendments to Part 43/45 (Published November 2020).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides a name, code, or other identifier for the variation margin collateral portfolio to which this belongs. Added to support CFTC Amendments to Part 43/45 (Published November 2020).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Allows the organization to specify which if any relevant regulators or other supervisory bodies this is relevant for, and what reporting rules apply.
</xsd:documentation>
<xsd:group fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Group moved to ReportingRegime structure to allow it to be jurisdiction specific. (RPTWG decision 2022-11-02)" minOccurs="0" ref="EndUserException.model">
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
DEPRECATED. Group moved to ReportingRegime structure to allow it to be jurisdiction specific. (RPTWG decision 2022-11-02)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates that the trade has price-affecting characteristics in addition to the standard real-time reportable terms. The flag indicates that the price for this trade is not to be construed as being indicative of the market for standardised trades with otherwise identical reportable terms.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates that the price does not reflect the current market. For example, in a credit trade where the two counterparties are not of equal credit standing, there is no initial margin and one party pays collateral to the other in the form of an add-on to the price (say a price that would otherwise be 100 at the market is struck at 105 to include the collateral, resulting in a very off-market looking price.)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Describes why the price of this trade does not reflect the current market price. For example, the trade may have been traded off-market as part of a termination or compression operation.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was executed, e.g. via voice or electronically.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation. This affect the timing of real-time reporting requirements. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation. This affects the process flow for confirmation messages. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether this trade is a result of compression activity.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--Do not delete this orphan. This is used as an example for defining a different content model for a calculation rule-->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type representing an arbitary grouping of trade references.
</xsd:documentation>
<xsd:element minOccurs="0" name="partyPortfolioName" type="PartyPortfolioName">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The name of the portfolio together with the party that gave the name.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="tradeId" type="TradeId"/>
</xsd:choice>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
An arbitary grouping of trade references (and possibly other portfolios).
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:simpleContent>
</xsd:simpleContent>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The reason a trade's price does not reflect the current market price.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/pricing-context" name="pricingContextScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides a lexical location (i.e. a line number and character for bad XML) or an XPath location (i.e. place to identify the bad location for valid XML).
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="NormalizedString">
</xsd:simpleContent>
<xsd:attribute name="locationType" type="Token">
</xsd:extension>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The value of the locationType attribute defines which type of location has been given. It may take the values 'lexical' or 'xpath'.
</xsd:documentation>
<xsd:complexType fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Added in error. Leftover from earlier proposal" name="ProductComponentIdentifier">
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Deprecated: A type defining a USI for the a subproduct component of a strategy.
</xsd:documentation>
<xsd:element minOccurs="0" name="premiumProductReference" type="ProductReference">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates which product within a strategy this ID is associated with.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Summary information about the product that was traded. This is intended primarily for trade reporting by TRs.
</xsd:documentation>
<xsd:element minOccurs="0" name="finalSettlementDate" type="xsd:date"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Added to support CFTC Amendments to Part 43/45 (Published November 2020)
</xsd:documentation>
<xsd:element fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Use instead the field within credit products: indexReferenceInformation/seniority" minOccurs="0" name="seniority" type="CreditSeniority">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
DEPRECATED. Use instead the field within credit products: indexReferenceInformation/seniority (RPTWG decision 2017-09)
</xsd:documentation>
<xsd:element fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Use instead the field within credit products: indexReferenceInformation/indexFactor" minOccurs="0" name="indexFactor" type="xsd:decimal">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
DEPRECATED. Use instead the field within credit products: indexReferenceInformation/indexFactor (RPTWG decision 2017-09)
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
An ID assigned by a regulator to an organization registered with it. (NOTE: should this just by represented by an alternate party ID?)
</xsd:documentation>
<xsd:simpleContent>
</xsd:simpleContent>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
How a Boolean value is to be reported for this regulator. Typically "true" or "false", but for ESMA "X" is also allowed, to indicate not supplied.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-boolean" name="reportingBooleanScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A value that explains the reason or purpose that information is being reported. Examples might include RealTimePublic reporting, PrimaryEconomicTerms reporting, Confirmation reporting, or Snapshot reporting.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-purpose" name="reportingPurposeScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides information about how the information in this message is applicable to a regulatory reporting process.
</xsd:documentation>
<xsd:choice>
</xsd:sequence>
<xsd:sequence>
</xsd:choice>
<xsd:element name="name" type="ReportingRegimeName">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the reporting regime under which this data is reported. For example, Dodd-Frank, MiFID, HongKongOTCDRepository, ODRF
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisorRegistration" type="SupervisorRegistration">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
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:documentation xml:lang="en">
</xsd:annotation>
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:documentation xml:lang="en">
</xsd:annotation>
Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The reason this message is being sent, for example Snapshot, PET, Confirmation, RealTimePublic.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Whether the particular trade type in question is required by this regulator to be cleared.
</xsd:documentation>
<xsd:element minOccurs="0" name="mandatoryFacilityExecution" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Whether the particular product must be executed on a SEF or DCM. See to Dodd-Frank section 723(a)(8).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the party invoked exception to not execute the trade on facility such as SEF and DCM even though the particular product is mandated to execute on a SEF.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates whether the counterparty exceeds the volume threshold above which trades are required to be cleared.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
This may be used to identify one or more parties that perform a role within the transaction. If this is within a partyTradeInformation block, the related party performs the role with respect to the party identifie by the "partyReference" in the partyTradeInformation block.
</xsd:documentation>
<xsd:element name="entityClassification" type="EntityClassification">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates the category or classification or business role of the organization referenced by the partyTradeInformation with respect to this reporting regime, for example Financial, NonFinancial etc.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" name="partyEntityClassification" type="PartyEntityClassification">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates the category or classification or business role of a trade party with respect to this reporting regime, for example Financial, NonFinancial, Dealer, Non-Dealer, LocalParty, etc.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates how the parties to the trade (the counterparties) are related to each other with respect to this reporting regime, e.g. Affiliated, Intragroup, etc..
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reports a regulator-specific code for the action associated with this submission. Used, for example, to report the ESMA action type.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reports that this trade was executed prior to the enactment of the relevant reporting regulation.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
How the notional amount should be reported for the reporting regime. For example, for ESMA MiFIR it would be Nominal or MonetaryAmount.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reports a regulator-specific code classifying the currency pair in the trade into risk categories such as Major Currencies or Emerging Markets.
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Choice containing all information regarding an end user exception.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type containing a code representing the role of a party in a report, e.g. the originator, the recipient, the counterparty, etc. This is used to clarify which participant's information is being reported.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-role" name="reportingRoleScheme" type="NonEmptyURI" use="optional"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type containing a code representing the level at which this is reported (e.g. Trade or Position)
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-level" name="reportingLevelScheme" type="NonEmptyURI" use="optional"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type that provides identification for reporting regimes.
</xsd:documentation>
<xsd:choice>
</xsd:sequence>
<xsd:sequence>
</xsd:choice>
<xsd:element name="name" type="ReportingRegimeName">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the reporting regime under which this data is reported. For example, Dodd-Frank, MiFID, HongKongOTCDRepository, ODRF
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisorRegistration" type="SupervisorRegistration">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
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:documentation xml:lang="en">
</xsd:annotation>
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:documentation xml:lang="en">
</xsd:annotation>
Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reports a regulator-specific code for the action associated with this submission. Used, for example, to report the ESMA action type.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining a content model for describing the nature and possible location of a error within a previous message.
</xsd:documentation>
<xsd:element minOccurs="0" name="reasonCode" type="ReasonCode">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A value indicating the location of the problem within the subject message.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Plain English text describing the associated error condition
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A reference identifying a rule within a validation scheme
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Any string of additional data that may help the message processor, for example in a rejection message this might contain a code value or the text of any one of the messages (within a CDATA section).
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Defines a list of machine interpretable error codes.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/reason-code" name="reasonCodeScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A short sale concluded by an investment firm on its own behalf or on behalf of a client, as described in Article 11.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/esma-mifir-short-sale" name="shortSaleScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
</xsd:sequence>
Provides information about a regulator or other supervisory body that an organization is registered with.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:simpleContent>
</xsd:simpleContent>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:element name="tradeHeader" type="TradeHeader">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The information on the trade which is not product specific, e.g. trade date.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The party referenced is specified in the related Confirmation as Barrier Determination Agent.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/org-type-category" name="categoryScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining trade related information which is not product specific.
</xsd:documentation>
<xsd:group ref="TradeIdentifiers.model"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Additional trade information that is shared by all parties.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeInformation" type="PartyTradeInformation">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Additional trade information that may be provided by each involved party.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Information about the trade package if any that the trade originated from.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The trade date. This is the date the trade was originally executed. In the case of a novation, the novated part of the trade should be reported (by both the remaining party and the transferee) using a trade date corresponding to the date the novation was agreed. The remaining part of a trade should be reported (by both the transferor and the remaining party) using a trade date corresponding to the original execution date.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining a trade identifier issued by the indicated party.
</xsd:documentation>
<xsd:choice minOccurs="0">
</xsd:sequence>
<xsd:group ref="IssuerTradeId.model"/>
</xsd:choice>
<xsd:group ref="PartyAndAccountReferences.model">
</xsd:sequence>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
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:element name="tradeId" type="TradeId"/>
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A trade identifier accompanied by a version number. In regulatory reporting views, this should be avoided except for internal mnessaging.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining a trade identifier with a reference to the party that this trade is associated with.
</xsd:documentation>
<xsd:complexContent>
</xsd:complexContent>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining additional information that may be recorded against a trade.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
This may be used to identify one or more parties that perform a role within the transaction. If this is within a partyTradeInformation block, the related party performs the role with respect to the party identifie by the "partyReference" in the partyTradeInformation block.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Trade execution date time, for example as provided by a central execution facility. Normally this refers to the original execution time of the trade, not the execution time of any post-trade events that may have affeted it. However, in the case of a post trade event that reports the new version of the trade (for example, the novation trade in an novation event, or the amended trade in an amendment event), the execution date time may contain the time that the newly created or modified trade was created or modified.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Allows timing information about a trade to be recorded.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be allocated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be cleared via a derivative clearing organization
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Describes the status with respect to clearing (e.g. AwaitingAcceptance, Pending, Accepted, Rejected, etc.)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether this party posts collateral. For Recordkeeping, the collateralization type refers to collateral that is posted by this firm, and One-Way is not meaningful. In other words, if the collateralization type is Full, this trade is fully collateralized by this party. For Transparency view, the options include Full, Partial, Uncollateralized, and One-Way.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Allows the organization to specify which if any relevant regulators or other supervisory bodies this is relevant for, and what reporting rules apply.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization because the "End User Exception" was invoked.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates that the trade has price-affecting characteristics in addition to the standard real-time reportable terms. The flag indicates that the price for this trade is not to be construed as being indicative of the market for standardised trades with otherwise identical reportable terms.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates that the price does not reflect the current market. For example, in a credit trade where the two counterparties are not of equal credit standing, there is no initial margin and one party pays collateral to the other in the form of an add-on to the price (say a price that would otherwise be 100 at the market is struck at 105 to include the collateral, resulting in a very off-market looking price.)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Describes why the price of this trade does not reflect the current market price. For example, the trade may have been traded off-market as part of a termination or compression operation.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was executed, e.g. via voice or electronically.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation. This affect the timing of real-time reporting requirements. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation. This affects the process flow for confirmation messages. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Allows timing information about when a trade was processed and reported to be recorded.
</xsd:documentation>
<xsd:element minOccurs="0" name="orderEntered" type="xsd:dateTime">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
When an order was first generated, as recorded for the first time when it was first entered by a person or generated by a trading algorithm (i.e., the first record of the order).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The time when an order is submitted by a market participant to an execution facility, as recorded based on the timestamp of the message that was sent by the participant. If the participant records this time (i.e. it is in the participant's party trade information), it will be the time the message was sent. If the execution facility records this time (i.e. it is in the facility's party trade information), it will be the time the message was received.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
When the public report of this was created or received by this party. If the participant records this time (i.e. it is in the participant's party trade information), it will be the time the message was sent. If the execution records this time (i.e. it is in the facility's party trade information), it will be the time the message was received.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
When the public report of this was most recently corrected or corrections were sent or received by this party.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
When the public report of this was first accepted for submission to a regulator.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Other timestamps for this trade. This is provisional in Recordkeeping and Transparency view and may be reviewed in a subsequent draft.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indication as to whether the transaction was executed under a pre-trade waiver in accordance with Articles 4 and 9 of Regulation (EU) 600/2014.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/esma-mifir-trading-waiver" name="tradingWaiverScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A reference identifying a rule within a validation scheme.
</xsd:documentation>
<xsd:simpleContent>
</xsd:simpleContent>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type used to represent the type of mechanism that can be used to verify a trade.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/verification-method" name="verificationMethodScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:element minOccurs="0" name="tradeId" type="TradeId"/>
</xsd:sequence>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The version of the trade id. The tradeId is versioned and not the trade.
</xsd:documentation>
<xsd:annotation>
</xsd:attributeGroup>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Set of attributes that define versioning information.
</xsd:documentation>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicate which version of the FpML Schema an FpML message adheres to.
</xsd:documentation>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation xml:lang="en">
</xsd:annotation>
This optional attribute can be supplied by a message creator in an FpML instance to specify which build number of the schema was used to define the message when it was generated.
</xsd:documentation>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The specific build number of this schema version. This attribute is not included in an instance document. Instead, it is supplied by the XML parser when the document is validated against the FpML schema and indicates the build number of the schema file. Every time FpML publishes a change to the schema, validation rules, or examples within a version (e.g., version 4.2) the actual build number is incremented. If no changes have been made between releases within a version (i.e. from Trial Recommendation to Recommendation) the actual build number stays the same.
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
</xsd:choice>
Types that globally and uniquely identify trade across counterparties, for regulatory reporting and other purposes. Includes a USI and/or a UTI.
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides information about a regulator or other supervisory body that an organization is registered with.
</xsd:documentation>
<xsd:element name="supervisoryBody" type="SupervisoryBody">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The regulator or other supervisory body the organization is registered with (e.g. SEC).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The ID assigned by the regulator (e.g. SEC's Central Index Key).
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
</xsd:choice>
<xsd:annotation/>
</xsd:sequence>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Trade identifiers agreed across parties to uniquely and globally identify trades for regulatory and other purposes.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeIdentifier" type="PartyTradeIdentifier">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The trade reference identifier(s) allocated to the trade by the parties involved.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The trade reference identifier(s) allocated to the trade by the parties involved.
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Choice between identification and representation of trade execution.
</xsd:documentation>
<xsd:element name="trade" type="Trade">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
An element that allows the full details of the trade to be used as a mechanism for identifying the trade for which the post-trade event pertains
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A container since an individual trade can be referenced by two or more different partyTradeIdentifier elements - each allocated by a different party.
</xsd:documentation>
<xsd:sequence>
</xsd:group>
<xsd:element minOccurs="0" name="isSecuritiesFinancing" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the transaction falls within the scope of activity but is exempted from reporting under [Securities Financing Transactions Regulation]
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Classification of the OTC transaction. Note: Coding scheme definition to encapsulate: Articles 20(3)(a) and 21(5)(a) of Regulation (EU) 600/2014. e.g. default="http://www.fpml.org/coding-scheme/esma-mifir-otc-classification"
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Classification of the pre-trade waiver, if any, that the transaction was executed under. Note: Coding scheme to encapsulate: Articles 4 and 9 of Regulation (EU) 600/2014. e.g. default="http://www.fpml.org/coding-scheme/esma-mifir-trading-waiver"
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Classification of the transaction as a short sale or not and, if short, of the type of transaction. Note: Coding scheme to encapsulate: Article 11 of Regulation (EU) 600/2014. e.g. default="http://www.fpml.org/coding-scheme/esma-mifir-short-sale"
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the transaction reduces risk in an objectively measurable way. Only applicable for commodity derivative transactions.
</xsd:documentation>
<xsd:choice>
</xsd:group>
<xsd:annotation>
</xsd:choice>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Choice containing all information regarding an end user exception.
</xsd:documentation>
<xsd:element name="endUserException" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization, i.e. whether there is an exemption from clearing. For historical reasons this is called "end-user exception", but this may be used to indication any exception from normal clearing mandates caused by the type of the partiees or their relationship, such as inter-affiliate trades. If a relatedParty block with a role of ClearingExceptionParty is present, that related party indicates which party is claiming the end user exception.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="endUserExceptionReason" type="ClearingExceptionReason">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies a reason that the trade is exempted from a clearing requirement. This exemption may be an end-user exception, or another type such as in inter-affiliate trade.
</xsd:documentation>
<xsd:sequence>
</xsd:group>
<xsd:choice minOccurs="0">
</xsd:sequence>
<xsd:element name="largeSizeTrade" type="xsd:boolean">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
For off-facility trades, specifies whether the sender of this trade considers it to be a large notional trade or block trade for reporting purposes, and thus eligible for delayed public reporting. This element is used to supply CFTC Large notional off-facility swap election indicator.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
For on-facility trades, indicator of whether an election has been made to report the swap transaction as a block transaction by the reporting counterparty or as calculated by either the swap data repository acting on behalf of the reporting counterparty or by using a third party. This element is used to provide CFTC 93 Block Trade Election Indicator.
</xsd:documentation>
</xsd:schema>
|
XML schema documentation generated with FlexDoc/XML 1.12.2 using FlexDoc/XML XSDDoc 2.9.1 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit. |