All Element Summary |
||||||||
The fractional allocation (0.45 = 45%) of the notional and "block" fees to this particular client subaccount.
|
||||||||
The notional allocation (amount and currency) to this particular client account.
|
||||||||
|
||||||||
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.
|
||||||||
Unique ID for the allocation.
|
||||||||
|
||||||||
An identifer for a specific appoval, to allow the approval to be identified and tracked.
|
||||||||
A container for approval states in the workflow.
|
||||||||
A pointer style reference to a party defined elsewhere in the document.
|
||||||||
The full name or identifiying ID of the relevant approver.
|
||||||||
A pointer style reference to a party defined elsewhere in the document.
|
||||||||
The party referenced is specified in the related Confirmation as Barrier Determination Agent.
|
||||||||
The ISDA calculation agent responsible for performing duties as defined in the applicable product definitions.
|
||||||||
The city in which the office through which ISDA Calculation Agent is acting for purposes of the transaction is located The short-form confirm for a trade that is executed under a Sovereign or Asia Pacific Master Confirmation Agreement ( MCA ), does not need to specify the Calculation Agent.
|
||||||||
Describes the status with respect to clearing (e.g.
|
||||||||
Describes the status with respect to clearing (e.g.
|
||||||||
The sum that must be posted upfront to collateralize against counterparty credit risk.
|
||||||||
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.
|
||||||||
A reference to a component of the strategy (typically a product).
|
||||||||
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.
|
||||||||
The date interest started accruing for the accrued interest calculation on an interest bearing security.
|
||||||||
Special credit fee assessed to certain institutions.
|
||||||||
What arrangements will be made to provide credit?
|
||||||||
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization because the "End User Exception" was invoked.
|
||||||||
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization because the "End User Exception" was invoked.
|
||||||||
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.
|
||||||||
The date when a distribution of dividends or interest is deducted from a securities asset, or set aside for payment to the original bondholders.
|
||||||||
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.
|
||||||||
Value excluding fees and commissions.
|
||||||||
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
|
||||||||
Specifies whether this trade is between affiliated organizations.
|
||||||||
Specifies whether this trade is a result of compression activity.
|
||||||||
|
||||||||
|
||||||||
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.
|
||||||||
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.
|
||||||||
Whether the particular trade type in question is required by this regulator to be cleared.
|
||||||||
The date of the confirmation executed between the parties and intended to govern the allocated trade between those parties.
|
||||||||
Identifies the reporting regime under which this data is reported.
|
||||||||
Value including fees and commissions.
|
||||||||
Value including fees and commissions.
|
||||||||
The monetary value of the security (eg. fixed income security) that was traded).
|
||||||||
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.
|
||||||||
A reference to the notional amount.
|
||||||||
The (absolute) number of units of the underlying instrument that were traded.
|
||||||||
Indicates that the price does not reflect the current market.
|
||||||||
Indicates that the price does not reflect the current market.
|
||||||||
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).
|
||||||||
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.
|
||||||||
Allows the organization to specify which categories or characteristics apply to it for end-user exception determination.
|
||||||||
|
||||||||
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 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.
|
||||||||
|
||||||||
The trade reference identifier(s) allocated to the trade by the parties involved.
|
||||||||
|
||||||||
Additional trade information that may be provided by each involved party.
|
||||||||
A percentage of the notional amount.
|
||||||||
An arbitary grouping of trade references (and possibly other portfolios).
|
||||||||
|
||||||||
Indicates which product within a strategy this ID is associated with.
|
||||||||
The net and/or gross value of the amount traded in native currency.
|
||||||||
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.
|
||||||||
|
||||||||
The ID assigned by the regulator (e.g.
|
||||||||
Specifies any relevant parties to the allocation which should be referenced.
|
||||||||
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.
|
||||||||
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.
|
||||||||
Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
|
||||||||
The current state of approval (.e.g preapproved, pending approval, etc.)
|
||||||||
Allows the organization to specify which if any relevant regulators it is registered with, and if so their identification number.
|
||||||||
Identifies the specific regulator or other supervisory body for which this data is produced.
|
||||||||
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.
|
||||||||
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
|
||||||||
The root element in an FpML trade document.
|
||||||||
The trade date.
|
||||||||
Whether the accrued interest in included when the trade settles.
|
||||||||
The information on the trade which is not product specific, e.g. trade date.
|
||||||||
|
||||||||
|
||||||||
|
||||||||
|
||||||||
|
||||||||
A reference to a party trade ID.
|
||||||||
Additional trade information that is shared by all parties.
|
||||||||
A container since an individual trade can be referenced by two or more different partyTradeIdentifier elements - each allocated by a different party.
|
||||||||
Allows the relevant transaction level categories or characteristics to be recorded for end-user exception determination.
|
||||||||
The type of approval (e.g.
|
||||||||
|
||||||||
A list of validation sets the sender asserts the document is valid with respect to.
|
||||||||
|
||||||||
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 |
||||||||||
|
||||||||||
Code that describes what type of allocation applies to the trade.
|
||||||||||
|
||||||||||
A specific approval state in the workflow.
|
||||||||||
An approval identifier allocated by a party.
|
||||||||||
|
||||||||||
A type that qualifies the type of approval.
|
||||||||||
The current status value of a clearing request.
|
||||||||||
Code that describes what type of collateral is posted by a party to a transaction.
|
||||||||||
A type used to represent the type of mechanism that can be used to confirm a trade.
|
||||||||||
A credit arrangement used in support of swaps trading.
|
||||||||||
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.
|
||||||||||
Records supporting information justifying an end user exception under 17 CFR part 39.
|
||||||||||
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.
|
||||||||||
|
||||||||||
A structure describing the price paid for the instrument.
|
||||||||||
A structure describing the value in "native" currency of an instrument that was traded.
|
||||||||||
A structure describing the amount of an instrument that was traded.
|
||||||||||
The data type used for issuer identifiers.
|
||||||||||
The data type used for link identifiers.
|
||||||||||
A structure including a net and/or a gross amount and possibly fees and commissions.
|
||||||||||
A characteristic of an organization used in declaring an end-user exception.
|
||||||||||
A type to represent a portfolio name for a particular party.
|
||||||||||
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 defining a content model for a calculation rule defined as percentage of the notional amount.
|
||||||||||
A type representing an arbitary grouping of trade references.
|
||||||||||
The data type used for portfolio names.
|
||||||||||
Deprecated: A type defining a USI for the a subproduct component of a strategy.
|
||||||||||
An ID assigned by a regulator to an organization registered with it.
|
||||||||||
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 containing a code representing the role of a party in a report, e.g. the originator, the recipient, the counterparty, etc.
|
||||||||||
Associates trade identifiers with components of a strategy.
|
||||||||||
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 type defining trade related information which is not product specific.
|
||||||||||
A trade reference identifier allocated by a party.
|
||||||||||
A type defining a trade identifier issued by the indicated party.
|
||||||||||
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.
|
||||||||||
A generic trade timestamp
|
||||||||||
A characteristic of a transaction used in declaring an end-user exception.
|
||||||||||
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
|
Element Group Summary |
||||||||||
|
||||||||||
|
||||||||||
A group including a net and/or a gross amount.
|
||||||||||
Provides information about a regulator or other supervisory body that an organization is registered with.
|
||||||||||
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) 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="trnsp" ecore:package="org.fpml.transparency" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/transparency" version="$Revision: 10804 $" 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-7.xsd"/>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="allocationTradeId" type="TradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Unique ID for the allocation. Multiple allocation trade IDs are provided to allow for the use of USI/UTI representations along with party-specific trade identifiers.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice minOccurs="0">
<xsd:element name="allocatedFraction" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The fractional allocation (0.45 = 45%) of the notional and "block" fees to this particular client subaccount.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The notional allocation (amount and currency) to this particular client account.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Code that describes what type of allocation applies to the trade. Options include Unallocated, PreAllocation, PostAllocation.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/allocation-reporting-status" name="allocationReportingStatusScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="type" type="ApprovalType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The type of approval (e.g. "pre-clearing credit").
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The current state of approval (.e.g preapproved, pending approval, etc.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The full name or identifiying ID of the relevant approver.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party defined elsewhere in the document. The party referenced has approved the specified item (e.g. trade or allocation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A pointer style reference to a party defined elsewhere in the document. The party referenced was approved for the specified item (e.g. trade or allocation) by the approving party (if specified).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
An identifer for a specific appoval, to allow the approval to be identified and tracked.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
An approval identifier allocated by a party. FpML does not define the domain values associated with this element.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/approval-type" name="approvalTypeScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/clearing-status" name="clearingStatusScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Code that describes what type of collateral is posted by a party to a transaction. Options include Uncollateralized, Partial, Full, One-Way.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/collateral-type" name="collateralTypeScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type used to represent the type of mechanism that can be used to confirm a trade.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/confirmation-method" name="confirmationMethodScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!--View Generation: SKIPPED CreditDerivativesNotices - Unsupported-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
A credit arrangement used in support of swaps trading.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/credit-document" name="creditDocumentScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:complexContent>
<xsd:extension base="Document">
<xsd:sequence>
<!--View Generation: SKIPPED - Documentation-->
<!--View Generation: Removed a degenerate choice.-->
<xsd:sequence>
<xsd:element minOccurs="0" name="onBehalfOf" type="OnBehalfOf">
<xsd:annotation>
<xsd:documentation>
Indicates which party (and accounts) a trade is being processed for.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--View Generation: SKIPPED portfolio - Unsupported-->
</xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The abstract base type from which all FpML compliant messages and documents must be derived.
</xsd:documentation>
</xsd:annotation>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Records supporting information justifying an end user exception under 17 CFR part 39.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="creditDocument" type="CreditDocument">
<xsd:annotation>
<xsd:documentation xml:lang="en">
What arrangements will be made to provide credit? (e.g. CSA, collateral pledge, guaranty, available resources, financing).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="organizationCharacteristic" type="OrganizationCharacteristic">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Allows the organization to specify which categories or characteristics apply to it for end-user exception determination. Examples include "FinancialEntity", "CaptiveFinanceUnit", "BoardOfDirectorsApproval".
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="transactionCharacteristic" type="TransactionCharacteristic">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Allows the relevant transaction level categories or characteristics to be recorded for end-user exception determination. Examples include "BoardOfDirectorsApproval", "HedgesCommercialRisk".
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisorRegistration" type="SupervisorRegistration">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Allows the organization to specify which if any relevant regulators it is registered with, and if so their identification number. For example, it could specify that it is SEC registered and provide its Central Index Key.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type describing the entity of a party, for example Financial, NonFinancial etc.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/entity-classification" name="entityClassificationScheme" type="xsd:anyURI" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:dateTime">
<xsd:attribute name="executionDateTimeScheme" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identification of the source (e.g. clock id) generating the execution date time.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type used to represent the type of market where a trade can be executed.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/execution-type" name="executionTypeScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type used to represent the type of market where a trade can be executed.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/execution-venue-type" name="executionVenueTypeScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:date">
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!--View Generation: SKIPPED InstrumentTradeDetails - Unsupported-->
<xsd:annotation>
<xsd:documentation>
A structure describing the amount of an instrument that was traded.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element name="number" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The (absolute) number of units of the underlying instrument that were traded.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The monetary value of the security (eg. fixed income security) that was traded).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="quote" type="BasicQuotation"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The date interest started accruing for the accrued interest calculation on an interest bearing security.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The date when a distribution of dividends or interest is deducted from a securities asset, or set aside for payment to the original bondholders. From the ex-date, any dividends that are owing on the security are paid to the original owner. As a consequence of this, on the ex-date, the securities price typically drops by the amount of the distribution (plus or minus any market activity).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Whether the accrued interest in included when the trade settles. ("true" means accrued interest is not included when the trade settles.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
A structure describing the value in "native" currency of an instrument that was traded.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="principalAmount" type="NetAndGross">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The net and/or gross value of the amount traded in native currency.
</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:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
A structure including a net and/or a gross amount and possibly fees and commissions.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A characteristic of an organization used in declaring an end-user exception.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/organization-characteristic" name="organizationCharacteristicScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type to represent a portfolio name for a particular party.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="partyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:complexContent>
<xsd:extension base="TradeIdentifier">
<xsd:sequence>
<!--View Generation: SKIPPED linkId - PartySpecific-->
<!--View Generation: SKIPPED allocationTradeId - PartySpecific-->
<!--View Generation: SKIPPED blockTradeId - PartySpecific-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<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:documentation xml:lang="en">
Deprecated: The USIs of the components of this trade, when this trade contains a strategy.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">A type containing multiple partyTradeIdentifier.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type defining party-specific additional information that may be recorded against a trade.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group minOccurs="0" ref="PartyAndAccountReferences.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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>
<!--View Generation: SKIPPED reportingRole - PartySpecific-->
<!--View Generation: SKIPPED unit - PartySpecific-->
<!--View Generation: SKIPPED relatedBusinessUnit - PartySpecific-->
<!--View Generation: SKIPPED relatedPerson - PartySpecific-->
<!--View Generation: SKIPPED isAccountingHedge - Documentation-->
<!--View Generation: SKIPPED category - PartySpecific-->
<!--View Generation: SKIPPED trader - PartySpecific-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
Allows timing information about a trade to be recorded.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether the trade is anticipated to be allocated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether the trade is anticipated to be cleared via a derivative clearing organization
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes the status with respect to clearing (e.g. Submitted, Pending, Cleared, RejectedForClearing, etc.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
Provides a name, code, or other identifier for the collateral portfolio to which this belongs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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>
<!--View Generation: Removed a degenerate choice.-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization because the "End User Exception" was invoked. 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:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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. Normally this will only be applicable for off-facility trades.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Used to describe how the trade was executed, e.g. via voice or electronically.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
Specifies whether this trade is between affiliated organizations.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether this trade is a result of compression activity.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!--Do not delete this orphan. This is used as an example for defining a different content model for a calculation rule-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type defining a content model for a calculation rule defined as percentage of the notional amount.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="PaymentRule">
<xsd:sequence>
<xsd:element minOccurs="0" name="paymentPercent" type="xsd:decimal">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type representing an arbitary grouping of trade references.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="partyPortfolioName" type="PartyPortfolioName">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The name of the portfolio together with the party that gave the name.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice minOccurs="0">
<xsd:element maxOccurs="unbounded" minOccurs="0" name="tradeId" type="TradeId"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
</xsd:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">
An arbitary grouping of trade references (and possibly other portfolios).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-purpose" name="reportingPurposeScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Provides information about how the information in this message is applicable to a regulatory reporting process.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<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" minOccurs="0" name="supervisorRegistration" type="SupervisorRegistration">
<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: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:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
The reason this message is being sent, for example Snapshot, PET, Confirmation, RealTimePublic.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Whether the particular trade type in question is required by this regulator to be cleared.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates whether the counterparty exceeds the volume threshold above which trades are required to be cleared.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-role" name="reportingRoleScheme" type="xsd:anyURI" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!--View Generation: SKIPPED Strategy - Unsupported-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
Associates trade identifiers with components of a strategy.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="tradeIdentifierReference" type="PartyTradeIdentifierReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A reference to a party trade ID. If there are multiple trade IDs for a single component (e.g. USI, UTI, party-specific identifier), create a single "strategyComponentIdentifier" with a reference to the component, and multiple tradeIdentifierReferences, one referencing each applicable identifier.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A reference to a component of the strategy (typically a product).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Provides information about a regulator or other supervisory body that an organization is registered with.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="tradeHeader" type="TradeHeader">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The information on the trade which is not product specific, e.g. trade date.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--View Generation: SKIPPED otherPartyPayment - Unsupported-->
<!--View Generation: SKIPPED brokerPartyReference - PartySpecific-->
<!--View Generation: SKIPPED - PartySpecific-->
<!--View Generation: SKIPPED determiningParty - PartySpecific-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
The party referenced is specified in the related Confirmation as Barrier Determination Agent.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--View Generation: SKIPPED hedgingParty - PartySpecific-->
<!--View Generation: SKIPPED collateral - PartySpecific-->
<!--View Generation: SKIPPED documentation - Documentation-->
<!--View Generation: SKIPPED governingLaw - Documentation-->
<!--View Generation: SKIPPED allocations - PartySpecific-->
<!--View Generation: SKIPPED approvals - Unsupported-->
</xsd:sequence>
</xsd:complexType>
<!--View Generation: SKIPPED TradeCategory - Unsupported-->
<!--View Generation: SKIPPED TradeDifference - Unsupported-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type defining trade related information which is not product specific.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="partyTradeIdentifier" type="PartyTradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The trade reference identifier(s) allocated to the trade by the parties involved.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Additional trade information that is shared by all parties.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeInformation" type="PartyTradeInformation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Additional trade information that may be provided by each involved party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:element>
<!--View Generation: SKIPPED clearedDate - Other-unavailable for this view-->
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A trade 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 type defining a trade identifier issued by the indicated party.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:sequence>
</xsd:sequence>
<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:choice maxOccurs="unbounded" minOccurs="0">
<xsd:element name="tradeId" type="TradeId"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:element>
</xsd:choice>
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Added in error. Leftover from earlier proposal" name="ProductComponentIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Deprecated: A type defining a USI for the a subproduct component of a strategy.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="premiumProductReference" type="ProductReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates which product within a strategy this ID is associated with.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type defining additional information that may be recorded against a trade.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty">
<xsd:annotation>
<xsd:documentation xml:lang="en">
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>
<!--View Generation: SKIPPED reportingRole - PartySpecific-->
<!--View Generation: SKIPPED unit - PartySpecific-->
<!--View Generation: SKIPPED relatedBusinessUnit - PartySpecific-->
<!--View Generation: SKIPPED relatedPerson - PartySpecific-->
<!--View Generation: SKIPPED isAccountingHedge - Documentation-->
<!--View Generation: SKIPPED category - PartySpecific-->
<!--View Generation: SKIPPED trader - PartySpecific-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
Allows timing information about a trade to be recorded.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether the trade is anticipated to be allocated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether the trade is anticipated to be cleared via a derivative clearing organization
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Describes the status with respect to clearing (e.g. Submitted, Pending, Cleared, RejectedForClearing, etc.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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>
<!--View Generation: Removed a degenerate choice.-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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. Normally this will only be applicable for off-facility trades.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Used to describe how the trade was executed, e.g. via voice or electronically.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Allows timing information about when a trade was processed and reported to be recorded.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="orderEntered" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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>
<!--View Generation: SKIPPED nonpubliclyReported - Other-unavailable for this view-->
<!--View Generation: SKIPPED nonpublicReportUpdated - Other-unavailable for this view-->
<!--View Generation: SKIPPED submittedForConfirmation - Other-unavailable for this view-->
<!--View Generation: SKIPPED updatedForConfirmation - Other-unavailable for this view-->
<!--View Generation: SKIPPED confirmed - Other-unavailable for this view-->
<!--View Generation: SKIPPED submittedForClearing - Other-unavailable for this view-->
<!--View Generation: SKIPPED updatedForClearing - Other-unavailable for this view-->
<!--View Generation: SKIPPED cleared - Other-unavailable for this view-->
<!--View Generation: SKIPPED allocationsSubmitted - Other-unavailable for this view-->
<!--View Generation: SKIPPED allocationsUpdated - Other-unavailable for this view-->
<!--View Generation: SKIPPED allocationsCompleted - Other-unavailable for this view-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:element>
</xsd:sequence>
</xsd:complexType>
<!--View Generation: SKIPPED Trader - PartySpecific-->
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A characteristic of a transaction used in declaring an end-user exception.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/transaction-characteristic" name="transactionCharacteristicScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A reference identifying a rule within a validation scheme.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type used to represent the type of mechanism that can be used to verify a trade.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/verification-method" name="verificationMethodScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="tradeId" type="TradeId"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The version of the trade id. The tradeId is versioned and not the trade.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Set of attributes that define versioning information.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicate which version of the FpML Schema an FpML message adheres to.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="5-[0-9]+"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:attribute>
</xsd:attributeGroup>
<!--View Generation: SKIPPED instrumentTradeDetails - Unsupported-->
<!--View Generation: SKIPPED strategy - Unsupported-->
<xsd:sequence>
<xsd:element minOccurs="0" name="collateral" type="Collateral">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The sum that must be posted upfront to collateralize against counterparty credit risk.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Special credit fee assessed to certain institutions.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">A container for approval states in the workflow.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The date of the confirmation executed between the parties and intended to govern the allocated trade between those parties.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies any relevant parties to the allocation which should be referenced.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="calculationAgent" type="CalculationAgent">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The ISDA calculation agent responsible for performing duties as defined in the applicable product definitions.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The city in which the office through which ISDA Calculation Agent is acting for purposes of the transaction is located The short-form confirm for a trade that is executed under a Sovereign or Asia Pacific Master Confirmation Agreement ( MCA ), does not need to specify the Calculation Agent. However, the confirm does need to specify the Calculation Agent City. This is due to the fact that the MCA sets the value for Calculation Agent but does not set the value for Calculation Agent City.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
<xsd:choice>
<xsd:element name="net" type="xsd:decimal">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:sequence>
<xsd:element name="gross" type="xsd:decimal">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Provides 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:annotation>
<xsd:documentation xml:lang="en">
The ID assigned by the regulator (e.g. SEC's Central Index Key).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Choice between identification and representation of trade execution.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element name="trade" type="Trade">
<xsd:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
<xsd:documentation xml:lang="en">
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:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<xsd:group fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Replaced by Implementation Specification in msg header" name="Validation.model">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="validation" type="Validation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A list of validation sets the sender asserts the document is valid with respect to.
</xsd:documentation>
</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.
|