All Element Summary | ||||||||||||
accountReference (defined in AccountReferenceOrPartyReference.model group) | Reference to the subaccount definition in the Party list.
|
|||||||||||
allocatedFraction | The fractional allocation (0.45 = 45%) of the notional and "block" fees to this particular client subaccount.
|
|||||||||||
allocatedNotional | The notional allocation (amount and currency) to this particular client account.
|
|||||||||||
allocation |
|
|||||||||||
allocations | "Short-form" representation of allocations in which the key block economics are stated once within the trade structure, and the allocation data is contained in this allocations structure.
|
|||||||||||
allocationsCompleted | When allocations for this trade were completely processed.
|
|||||||||||
allocationsSubmitted | When allocations for this trade were submitted or received by this party.
|
|||||||||||
allocationsUpdated | When allocations for this trade were most recently corrected.
|
|||||||||||
allocationTradeId (defined in PartyTradeIdentifier complexType) | The trade id of the allocated trade.
|
|||||||||||
allocationTradeId (in allocation) | Unique ID for the allocation.
|
|||||||||||
amendmentEffectiveDate | The date on which the Amendment becomes effective
|
|||||||||||
amendmentTradeDate | The date on which the the parties enter into the Amendment transaction
|
|||||||||||
approval |
|
|||||||||||
approvals | A container for approval states in the workflow.
|
|||||||||||
approver | The full name or identifiying ID of the relevant approver.
|
|||||||||||
basePath | XPath to the element in the base object.
|
|||||||||||
baseValue | The value of the element in the base object.
|
|||||||||||
blockTradeId | The trade id of the block trade.
|
|||||||||||
brokerPartyReference | Identifies that party (or parties) that brokered this trade.
|
|||||||||||
calculationAgent (defined in CalculationAgent.model group) | The ISDA calculation agent responsible for performing duties as defined in the applicable product definitions.
|
|||||||||||
calculationAgentBusinessCenter | 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.
|
|||||||||||
category (defined in PartyTradeInformation complexType) | Used to categorize trades into user-defined categories, such as house trades vs. customer trades.
|
|||||||||||
cleared (defined in PartyTradeInformation complexType) | Specifies whether the trade is anticipated to be cleared via a derivative clearing organization
|
|||||||||||
cleared (in timestamps) | When this trade was cleared.
|
|||||||||||
clearedDate | If the trade was cleared (novated) through a central counterparty clearing service, this represents the date the trade was cleared (transferred to the central counterparty).
|
|||||||||||
collateral (defined in Trade complexType) | Defines collateral obiligations of a Party
|
|||||||||||
collateral (in allocation) | The sum that must be posted upfront to collateralize against counterparty credit risk.
|
|||||||||||
collateralizationType | Specifies whether the counterparty risk this party incurs is covered by a collateralization payment.
|
|||||||||||
confirmationMethod | Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
|||||||||||
confirmed | When this trade was confirmed.
|
|||||||||||
contractId (defined in ContractIdentifier complexType) | A contract id which is not version aware.
|
|||||||||||
contractId (in versionedContractId) |
|
|||||||||||
creditChargeAmount | Special credit fee assessed to certain institutions.
|
|||||||||||
creditDocument | What arrangements will be made to provide credit?
|
|||||||||||
creditEvent (in creditDerivativesNotices) | This element corresponds to the Credit Event Notice Delivered Under Old Transaction and Deemed Delivered Under New Transaction under the EXHIBIT C to 2004 ISDA Novation Definitions.
|
|||||||||||
determiningParty | The party referenced is the ISDA Determination Party that specified in the related Confirmation as Determination Party.
|
|||||||||||
differences | An optional set of detailed difference records.
|
|||||||||||
differenceSeverity | An indication of the severity of the difference.
|
|||||||||||
differenceType | The type of difference that exists.
|
|||||||||||
documentation (defined in Trade complexType) | Defines the definitions that govern the document and should include the year and type of definitions referenced, along with any relevant documentation (such as master agreement) and the date it was signed.
|
|||||||||||
element | The name of the element affected.
|
|||||||||||
endUserException | Specifies whether the trade is not obligated to be cleared via a derivative clearing organization because the "End User Exception" was invoked.
|
|||||||||||
endUserExceptionDeclaration | Provides supporting evidence when an end user exception is claimed.
|
|||||||||||
executionDateTime (defined in PartyTradeInformation complexType) | Trade execution date time provided by a central execution facility.
|
|||||||||||
executionType | Used to describe how the trade was executed, e.g. via voice or electronically.
|
|||||||||||
executionVenueType | Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
|
|||||||||||
extraElement | Element(s) that are extraneous in the other object.
|
|||||||||||
governingLaw (defined in Trade complexType) | Identification of the law governing the transaction.
|
|||||||||||
gross | Value excluding fees and commissions.
|
|||||||||||
hedgingParty | The party referenced is the ISDA Hedging Party that specified in the related Confirmation as Hedging, or if no Hedging Party is specified, either party to the Transaction.
|
|||||||||||
independentAmount | Independent Amount is an amount that usually less creditworthy counterparties are asked to provide.
|
|||||||||||
instrumentTradeDetails | A type to hold trades of multiply-traded instruments.
|
|||||||||||
isAccountingHedge | Specifies whether the trade used to hedge a risk for accounting purposes for the specified party.
|
|||||||||||
isCancellation | Indicates if this message corrects an earlier request.
|
|||||||||||
isCorrection (defined in ProcessingIndicator.model group) | Indicates if this message corrects an earlier request.
|
|||||||||||
largeSizeTrade | 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.
|
|||||||||||
linkId | A link identifier allowing the trade to be associated with other related trades, e.g. the linkId may contain a tradeId for an associated trade or several related trades may be given the same linkId.
|
|||||||||||
mandatorilyClearable | Whether the particular trade type in question is required to be cleared by this regulator.
|
|||||||||||
masterConfirmationDate (in allocation) | The date of the confirmation executed between the parties and intended to govern the allocated trade between those parties.
|
|||||||||||
message | A human readable description of the problem.
|
|||||||||||
missingElement | Element(s) that are missing in the other trade.
|
|||||||||||
net (in principalAmount in principal in instrumentTradeDetails) | Value including fees and commissions.
|
|||||||||||
net (in principalAmount in principal in instrumentTradeDetails) | Value including fees and commissions.
|
|||||||||||
nominal | The monetary value of the security (eg. fixed income security) that was traded).
|
|||||||||||
nonpubliclyReported | When the non-public report of this was created or received by this party.
|
|||||||||||
nonpublicReportUpdated | When the non-public report of this was most recently corrected or corrections were received by this party.
|
|||||||||||
nonStandardTerms | Specifies whether the trade contains terms that affect pricing that are not represented by the standard reportable data fields, that is, it indicates a bespoke trade that might otherwise appear from its characteristics to be a standardized trade but is really non-standard.
|
|||||||||||
notionalAmountReference | A reference to the notional amount.
|
|||||||||||
number (in quantity in instrumentTradeDetails) | The (absolute) number of units of the underlying instrument that were traded.
|
|||||||||||
offMarketPrice | Indicates that the price does not reflect the current market.
|
|||||||||||
onBehalfOf (defined in DataDocument complexType) | Indicates which party (and accounts) a trade is being processed for.
|
|||||||||||
orderEntered | 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).
|
|||||||||||
orderSubmitted | 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.
|
|||||||||||
organizationCharacteristic | Allows the organization to specify which categories or characteristics apply to it for end-user exception determination.
|
|||||||||||
originatingEvent (defined in DataDocument complexType) |
|
|||||||||||
otherPartyPayment | Other fees or additional payments associated with the trade, e.g. broker commissions, where one or more of the parties involved are not principal parties involved in the trade.
|
|||||||||||
otherPath | XPath to the element in the other object.
|
|||||||||||
otherValue | Value of the element in the other trade.
|
|||||||||||
partyPortfolioName | The name of the portfolio together with the party that gave the name.
|
|||||||||||
partyReference (defined in AccountReferenceOrPartyReference.model group) | Reference to the party definition.
|
|||||||||||
partyReference (defined in ContractIdentifier complexType) | A pointer style reference to a party identifier defined elsewhere in the document.
|
|||||||||||
partyReference (in partyPortfolioName) | A pointer style reference to a party identifier defined elsewhere in the document.
|
|||||||||||
partyTradeIdentifier (defined in PartyTradeIdentifiers complexType) |
|
|||||||||||
partyTradeIdentifier (in tradeHeader) | The trade reference identifier(s) allocated to the trade by the parties involved.
|
|||||||||||
partyTradeInformation (in tradeHeader) | Additional trade information that may be provided by each involved party.
|
|||||||||||
paymentAmount (in paymentDetail) | A fixed payment amount.
|
|||||||||||
paymentDate (in paymentDetail) | Payment date.
|
|||||||||||
paymentDetail | A container element allowing a schedule of payments associated with the Independent Amount.
|
|||||||||||
paymentPercent | A percentage of the notional amount.
|
|||||||||||
paymentRule | A type defining the calculation rule.
|
|||||||||||
physicalSettlement (in creditDerivativesNotices) | This element corresponds to the Notice of Intended Physical Settlement Delivered Under Old Transaction under the EXHIBIT C to 2004 ISDA Novation Definitions.
|
|||||||||||
portfolio (defined in Portfolio complexType) | An arbitary grouping of trade references (and possibly other portfolios).
|
|||||||||||
portfolioName (in partyPortfolioName) |
|
|||||||||||
premiumProductReference | Indicates which product within a strategy represents the premium payment.
|
|||||||||||
priceNotation | Pricing information for the trade.
|
|||||||||||
pricing | The price paid for the instrument.
|
|||||||||||
principal (in instrumentTradeDetails) | The value, in instrument currency, of the amount of the instrument that was traded.
|
|||||||||||
principalAmount (in principal in instrumentTradeDetails) | The net and/or gross value of the amount traded in native currency.
|
|||||||||||
publiclyAvailableInformation (in creditDerivativesNotices) | This element corresponds to the Notice of Publicly Available Information Delivered Under Old Transaction and Deemed Delivered Under New Transaction under the EXHIBIT C to 2004 ISDA Novation Definitions.
|
|||||||||||
publiclyReportable | Whether the particular trade type in question is required to be publicly by this regulator.
|
|||||||||||
publiclyReported | When the public report of this was created or received by this party.
|
|||||||||||
publicReportUpdated | When the public report of this was most recently corrected or corrections were sent or received by this party.
|
|||||||||||
quantity (in instrumentTradeDetails) | A description of how much of the instrument was traded.
|
|||||||||||
queryParameter |
|
|||||||||||
queryParameterId |
|
|||||||||||
queryParameterOperator |
|
|||||||||||
queryParameterValue |
|
|||||||||||
quote (in pricing) |
|
|||||||||||
registrationNumber | The ID assigned by the regulator (e.g.
|
|||||||||||
regulator | The regulator the organization is registered with (e.g.
|
|||||||||||
regulatorRegistration (defined in PartyTradeInformation complexType) | Allows the organization to specify which if any relevant regulators it is registered with, and if so their identification number.
|
|||||||||||
regulatorRegistration (in endUserExceptionDeclaration) | Allows the organization to specify which if any relevant regulators it is registered with, and if so their identification number.
|
|||||||||||
relatedBusinessUnit | Provides information about a unit/division/desk etc. that executed or supports this trade
|
|||||||||||
relatedParty (defined in PartyTradeInformation complexType) | Identifies a related party performing a role within the transaction.
|
|||||||||||
relatedParty (in allocation) | Specifies any relevant parties to the allocation which should be referenced.
|
|||||||||||
relatedPerson | Provides information about a person that executed or supports this trade
|
|||||||||||
reportingRole (defined in PartyTradeInformation complexType) | Identifies the role of this party in reporting this trade (e.g. originator, counterparty).
|
|||||||||||
reportingRole (defined in RegulatorRegistration complexType) | Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
|
|||||||||||
status (in approval) | The current state of approval (.e.g preapproved, pending approval, etc.)
|
|||||||||||
strategy | A strategy product.
|
|||||||||||
submittedForClearing | When this trade was supplied to a clearing service for clearing.
|
|||||||||||
submittedForConfirmation | When this trade was supplied to a confirmation service or counterparty for confirmation.
|
|||||||||||
timestamp | Other timestamps for this trade.
|
|||||||||||
timestamps | Allows timing information about a trade to be recorded.
|
|||||||||||
toBeAllocated | Specifies whether the trade is anticipated to be allocated.
|
|||||||||||
trade (defined in DataDocument complexType) | The root element in an FpML trade document.
|
|||||||||||
trade (in affectedTransactions) | 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
|
|||||||||||
tradeDate | The trade date.
|
|||||||||||
tradeHeader | The information on the trade which is not product specific, e.g. trade date.
|
|||||||||||
tradeId (defined in Portfolio complexType) |
|
|||||||||||
tradeId (defined in TradeIdentifier complexType) |
|
|||||||||||
tradeId (defined in VersionedTradeId complexType) |
|
|||||||||||
tradeIdentifier (defined in BestFitTrade complexType) | The identifier for the trade compared against.
|
|||||||||||
tradeReference (in affectedTransactions) | A container since an individual trade can be referenced by two or more different partyTradeIdentifier elements - each allocated by a different party.
|
|||||||||||
transactionCharacteristic | Allows the relevant transaction level categories or characteristics to be recorded for end-user exception determination.
|
|||||||||||
type (in approval) | The type of approval (e.g.
|
|||||||||||
type (in timestamp) |
|
|||||||||||
updatedForClearing | When the most recent correction to this trade was supplied to a clearing service for clearing.
|
|||||||||||
updatedForConfirmation | When the most recent correction to this trade was supplied to a confirmation service or counterparty for confirmation.
|
|||||||||||
validation | A list of validation sets the sender asserts the document is valid with respect to.
|
|||||||||||
value (in timestamp) |
|
|||||||||||
verificationMethod | 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.
|
|||||||||||
versionedContractId | A contract id which is version aware.
|
Complex Type Summary | ||||||||||
|
||||||||||
|
||||||||||
A specific approval state in the workflow.
|
||||||||||
|
||||||||||
A type used to record the differences between the current trade and another indicated trade.
|
||||||||||
A type for defining the obligations of the counterparty subject to credit support requirements.
|
||||||||||
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 contact id identifier allocated by a party.
|
||||||||||
A type defining a contract identifier issued by the indicated party.
|
||||||||||
The organization types of the counterparties to the transaction.
|
||||||||||
|
||||||||||
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 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.
|
||||||||||
|
||||||||||
|
||||||||||
The economics of a trade of a multiply traded instrument.
|
||||||||||
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 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 additional information that may be recorded against a trade.
|
||||||||||
|
||||||||||
The abstract base type from which all calculation rules of the independent amount must be derived.
|
||||||||||
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.
|
||||||||||
A type representing criteria for defining a query portfolio.
|
||||||||||
A type representing an identifier for a parameter describing a query portfolio.
|
||||||||||
A type representing an operator describing the relationship of a value to its corresponding identifier for a parameter describing a query portfolio.
|
||||||||||
A type representing a portfolio obtained by querying the set of trades held in a repository.
|
||||||||||
An identifier of an organization that regulates trading activity, e.g.
|
||||||||||
An ID assigned by a regulator to an organization registered with it.
|
||||||||||
Provides information about a regulator that an organization is registered with.
|
||||||||||
A type containing a code representing the role of a party in a report, e.g. the originator, the recipient, the counterparty, etc.
|
||||||||||
A type defining a group of products making up a single trade.
|
||||||||||
The type or meaning of a timestamp.
|
||||||||||
A type defining an FpML trade. | ||||||||||
A scheme used to categorize positions.
|
||||||||||
A type used to record the details of a difference between two business objects/
|
||||||||||
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. | ||||||||||
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.
|
||||||||||
Contract Id with Version Support
|
||||||||||
Trade Id with Version Support
|
Simple Type Summary | ||||||
A type representing a value corresponding to an identifier for a parameter describing a query portfolio.
|
Element Group Summary | ||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
A group including a net and/or a gross amount.
|
||||||||||
Elements that describe how this document is intended to be processed (in the absence of a full messaging framework).
|
||||||||||
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-2011 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="" ecore:package="org.fpml.recordkeeping" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/recordkeeping" version="$Revision: 8787 $" xmlns="http://www.fpml.org/FpML-5/recordkeeping" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:fpml-annotation="http://www.fpml.org/annotation" xmlns:view="http://www.fpml.org/views" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:annotation> <xsd:documentation xml:lang="en"> A type representing a value corresponding to an identifier for a parameter describing a query portfolio. </xsd:documentation> </xsd:annotation> <xsd:restriction base="xsd:string"/> </xsd:simpleType> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">Unique ID for the allocation.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:choice> <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:sequence> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en">A specific approval state in the workflow.</xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">The type of approval (e.g. "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:sequence> </xsd:complexType> <xsd:sequence> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type used to record the differences between the current trade and another indicated trade. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">The identifier for the trade compared against.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">An optional set of detailed difference records.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type for defining the obligations of the counterparty subject to credit support requirements. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en"> Independent Amount is an amount that usually less creditworthy counterparties are asked to provide. It can either be a fixed amount or a percentage of the Transaction's value. The Independent Amount can be: (i) transferred before any trading between the parties occurs (as a deposit at a third party's account or with the counterparty) or (ii) callable after trading has occurred (typically because a downgrade has occurred). In situation (i), the Independent Amount is not included in the calculation of Exposure, but in situation (ii), it is included in the calculation of Exposure. Thus, for situation (ii), the Independent Amount may be transferred along with any collateral call. Independent Amount is a defined term in the ISDA Credit Support Annex. ("with respect to a party, the amount specified as such for that party in Paragraph 13; if no amount is specified, zero"). </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A contact id identifier allocated by a party. FpML does not define the domain values associated with this element. </xsd:documentation> </xsd:annotation> <xsd:simpleContent> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type defining a contract identifier issued by the indicated party. </xsd:documentation> </xsd:annotation> <xsd:sequence> <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 contract identifier. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:choice> <xsd:annotation> <xsd:documentation xml:lang="en"> Where the legal activity is to agree a contract of variation then the business process should be to modify a contract. This is a contract in its own right and not a version of a previous contract. Where the business process is to replace and supersede a contract then you have a new contract and a contract version should not be used. </xsd:documentation> </xsd:annotation> <xsd:annotation> <xsd:documentation xml:lang="en">A contract id which is not version aware.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element maxOccurs="unbounded" minOccurs="0" name="versionedContractId" type="VersionedContractId"> <xsd:annotation> <xsd:documentation xml:lang="en">A contract id which is version aware.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:choice> </xsd:sequence> </xsd:complexType> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en"> This element corresponds to the Credit Event Notice Delivered Under Old Transaction and Deemed Delivered Under New Transaction under the EXHIBIT C to 2004 ISDA Novation Definitions. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> This element corresponds to the Notice of Publicly Available Information Delivered Under Old Transaction and Deemed Delivered Under New Transaction under the EXHIBIT C to 2004 ISDA Novation Definitions. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> This element corresponds to the Notice of Intended Physical Settlement Delivered Under Old Transaction under the EXHIBIT C to 2004 ISDA Novation Definitions. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </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:sequence> <!--View Generation: Removed a degenerate choice.--> <xsd:sequence> <xsd:annotation> <xsd:documentation> Indicates which party (and accounts) a trade is being processed for. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">The root element in an FpML trade document.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">Pricing information for the trade.</xsd:documentation> </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"> 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: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:simpleContent> <xsd:extension base="xsd:date"> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en"> A container element allowing a schedule of payments associated with the Independent Amount. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation> The economics of a trade of a multiply traded instrument. </xsd:documentation> </xsd:annotation> <xsd:complexContent> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">The FpML asset description for the asset.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> A description of how much of the instrument was traded. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">The price paid for the instrument.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> The value, in instrument currency, of the amount of the instrument that was traded. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:annotation> <xsd:documentation> A structure describing the amount of an instrument that was traded. </xsd:documentation> </xsd:annotation> <xsd:choice> <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:documentation> A structure describing the price paid for the instrument. </xsd:documentation> </xsd:annotation> <xsd:sequence> </xsd:sequence> <!-- <xsd:choice> <xsd:element name="price" type="NetAndGross" > <xsd:annotation> <xsd:documentation xml:lang="en">The amount of money paid per unit of the traded instrument. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:sequence> <xsd:element name="cleanPrice" type="NetAndGross" > <xsd:annotation> <xsd:documentation xml:lang="en">The amount of money paid per unit of the traded instrument, exclusive of accrued interest.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="dirtyPrice" type="NetAndGross" minOccurs="0"> <xsd:annotation> <xsd:documentation xml:lang="en">The amount of money paid per unit of the traded instrument, inclusive of accrued interest.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> <xsd:element name="dirtyPrice" type="NetAndGross" > <xsd:annotation> <xsd:documentation xml:lang="en">The amount of money paid per unit of the traded instrument, inclusive of accrued interest.</xsd:documentation> <xsd:appinfo> <view:skip view="reporting"/> <view:skip view="transparency"/> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:choice> --> </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: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:documentation xml:lang="en">The data type used for link identifiers.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> </xsd:extension> </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:annotation> <xsd:documentation xml:lang="en">Net and/or gross amount.</xsd:documentation> </xsd:annotation> </xsd:group> </xsd:sequence> </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: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:sequence> <xsd:annotation> <xsd:documentation xml:lang="en"> A link identifier allowing the trade to be associated with other related trades, e.g. the linkId may contain a tradeId for an associated trade or several related trades may be given the same linkId. 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:element> <xsd:annotation> <xsd:documentation xml:lang="en"> The trade id of the allocated trade. This is used by the block trade to reference the allocated trade. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> The trade id of the block trade. This is used by each one of the allocated trades to reference the block trade. This element can also represent the trade id of the parent trade for N-level allocations. In the case, this element is only used to model N-level allocations in which the trade acts as block and allocated trade at the same time. This basically means the ability to allocate a block trade to multiple allocation trades, and then allocate these in turn to other allocation trades (and so on if desired). </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 additional information that may be recorded against a trade. </xsd:documentation> </xsd:annotation> <xsd:sequence> <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"> Identifies a related party performing a role within the transaction. </xsd:documentation> </xsd:annotation> </xsd:element> <!-- RPTWG 2009-09-04 begin--> <xsd:annotation> <xsd:documentation xml:lang="en"> Identifies the role of this party in reporting this trade (e.g. originator, counterparty). </xsd:documentation> </xsd:annotation> </xsd:element> <!--View Generation: SKIPPED unit - PartySpecific--> <!-- BAL 2011-10 - work on modeling people and org units --> <xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedBusinessUnit" type="RelatedBusinessUnit"> <xsd:annotation> <xsd:documentation xml:lang="en"> Provides information about a unit/division/desk etc. that executed or supports this trade </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> Provides information about a person that executed or supports this trade </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> Specifies whether the trade used to hedge a risk for accounting purposes for the specified party. (TODO: do we need to distinguish between asset and liability hedges?) </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> Used to categorize trades into user-defined categories, such as house trades vs. customer trades. </xsd:documentation> </xsd:annotation> </xsd:element> <!-- RPTWG 2009-09-04 end --> <!--View Generation: SKIPPED trader - PartySpecific--> <xsd:annotation> <xsd:documentation xml:lang="en"> Trade execution date time provided by a central execution facility. </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 cleared via a derivative clearing organization </xsd:documentation> </xsd:annotation> </xsd:element> <!-- added BAL 2011-10-18 for DTCC gap analysis --> <!-- modified BAL 2012-01-23 for CFTC final rules --> <xsd:annotation> <xsd:documentation xml:lang="en"> Specifies whether the counterparty risk this party incurs is covered by a collateralization payment. For Recordkeeping, the collateralization type refers to collateral that is posted by this firm's counterparty (not by this firm itself), and One-Way is not meaningful. In other words, if the collateralization type is Full, this trade is fully collateralized by the counterparty. For Transparency view, the options include Full, Partial, Uncollateralized, and One-Way. </xsd:documentation> </xsd:annotation> </xsd:element> <!-- added BAL 2012-01-23 for CFTC final rules --> <xsd:element maxOccurs="unbounded" minOccurs="0" name="regulatorRegistration" type="RegulatorRegistration"> <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> <!-- end BAL 2011-10-18 additions for DTCC gap analysis --> <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"> Provides supporting evidence when an end user exception is claimed. </xsd:documentation> </xsd:annotation> </xsd:element> <!-- end BAL 2011-10-18 additions for DTCC gap analysis --> <xsd:annotation> <xsd:documentation xml:lang="en"> Specifies whether the trade contains terms that affect pricing that are not represented by the standard reportable data fields, that is, it indicates a bespoke trade that might otherwise appear from its characteristics to be a standardized trade but is really non-standard. The flag indicates that the price for this trade is not to be construed as being indicative of the market. </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> <!-- added BAL 2011-10-18 for DTCC gap analysis --> <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> <!-- end BAL 2011-10-18 additions for DTCC gap analysis --> <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> <!-- added BAL 2012-01-23 for CFTC final rules --> <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> </xsd:simpleContent> </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: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="regulatorRegistration" type="RegulatorRegistration"> <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 credit arrangement used in support of swaps trading. </xsd:documentation> </xsd:annotation> <xsd:simpleContent> </xsd:extension> </xsd:simpleContent> </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> </xsd:simpleContent> </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> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> Provides information about a regulator that an organization is registered with. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en"> The regulator 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: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> <!-- NB: the following field is still under discussion in the FpML Reporting Working Group and may be changed in subsquent drafts of the standard --> <xsd:annotation> <xsd:documentation xml:lang="en"> Whether the particular trade type in question is required to be publicly by this regulator. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> Whether the particular trade type in question is required to be cleared by this regulator. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </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:extension> </xsd:simpleContent> </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> <!-- additional DTCC gaps --> <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> <!-- end additional DTCC gaps --> <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> <xsd:annotation> <xsd:documentation xml:lang="en"> When the non-public report of this was created or received by this party. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> When the non-public report of this was most recently corrected or corrections were received by this party. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> When this trade was supplied to a confirmation service or counterparty for confirmation. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> When the most recent correction to this trade was supplied to a confirmation service or counterparty for confirmation. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">When this trade was confirmed.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> When this trade was supplied to a clearing service for clearing. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> When the most recent correction to this trade was supplied to a clearing service for clearing. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">When this trade was cleared.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> When allocations for this trade were submitted or received by this party. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> When allocations for this trade were most recently corrected. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> When allocations for this trade were completely processed. </xsd:documentation> </xsd:annotation> </xsd:element> <!-- TODO: We are currently not including this in SDR reporting views, in order to encourange standardization of timestamp fields --> <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> <xsd:annotation> <xsd:documentation xml:lang="en">A generic trade timestamp</xsd:documentation> </xsd:annotation> <xsd:sequence> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en">The type or meaning of a timestamp.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> The organization types of the counterparties to the transaction. Counterparty types include SD (Swaps Dealer), MSP (Major Swap Participant), Client (non-SD/non-MSP.). Coding scheme values include InterDealer, DealerMSP, InterMSP, DealerClient, MSPClient, and Other. </xsd:documentation> </xsd:annotation> <xsd:simpleContent> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> An identifier of an organization that regulates trading activity, e.g. CFTC, SEC, FSA, etc. </xsd:documentation> </xsd:annotation> <xsd:simpleContent> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <!-- added BAL 2011-02-20 to address CFTC reporting requirements --> <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:attribute default="http://www.fpml.org/coding-scheme/execution-venue-type" name="executionVenueTypeScheme" type="xsd:anyURI"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <!-- added BAL 2011-06-13 to address CFTC reporting requirements --> <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:attribute default="http://www.fpml.org/coding-scheme/execution-type" name="executionTypeScheme" type="xsd:anyURI"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <!-- end BAL 2011-02-20 --> <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:attribute default="http://www.fpml.org/coding-scheme/confirmation-method" name="confirmationMethodScheme" type="xsd:anyURI"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:complexContent> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">Payment date.</xsd:documentation> </xsd:annotation> </xsd:element> <!--View Generation: Removed a degenerate choice.--> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">A type defining the calculation rule.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">A fixed payment amount.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> The abstract base type from which all calculation rules of the independent amount must be derived. </xsd:documentation> </xsd:annotation> </xsd:complexType> <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:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">A percentage of the notional amount.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">A reference to the notional amount.</xsd:documentation> </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: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: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:documentation xml:lang="en">The data type used for portfolio names.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type representing criteria for defining a query portfolio. The criteria are made up of a QueryParameterId, QueryParameterValue and QueryParameterOperator. </xsd:documentation> </xsd:annotation> <xsd:sequence> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type representing an identifier for a parameter describing a query portfolio. An identifier can be anything from a product name like swap to a termination date. </xsd:documentation> </xsd:annotation> <xsd:simpleContent> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type representing an operator describing the relationship of a value to its corresponding identifier for a parameter describing a query portfolio. Possible relationships include equals, not equals, less than, greater than. Possible operators are listed in the queryParameterOperatorScheme. </xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:attribute default="http://www.fpml.org/coding-scheme/query-parameter-operator" name="queryParameterOperatorScheme" type="xsd:anyURI"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type representing a portfolio obtained by querying the set of trades held in a repository. It contains trades matching the intersection of all criteria specified using one or more queryParameters or trades matching the union of two or more child queryPortfolios. </xsd:documentation> </xsd:annotation> <xsd:complexContent> <xsd:sequence> </xsd:sequence> </xsd:extension> </xsd:complexContent> </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> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type defining a group of products making up a single trade. </xsd:documentation> </xsd:annotation> <xsd:complexContent> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en"> Indicates which product within a strategy represents the premium payment. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en">A type defining an FpML trade.</xsd:documentation> </xsd:annotation> <xsd:sequence> <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> <xsd:annotation> <xsd:documentation xml:lang="en"> Other fees or additional payments associated with the trade, e.g. broker commissions, where one or more of the parties involved are not principal parties involved in the trade. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> Identifies that party (or parties) that brokered this trade. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> The party referenced is the ISDA Determination Party that specified in the related Confirmation as Determination Party. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> The party referenced is the ISDA Hedging Party that specified in the related Confirmation as Hedging, or if no Hedging Party is specified, either party to the Transaction. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">Defines collateral obiligations of a Party</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> Defines the definitions that govern the document and should include the year and type of definitions referenced, along with any relevant documentation (such as master agreement) and the date it was signed. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> Identification of the law governing the transaction. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> "Short-form" representation of allocations in which the key block economics are stated once within the trade structure, and the allocation data is contained in this allocations structure. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en">A scheme used to categorize positions.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:attribute default="http://www.fpml.org/coding-scheme/org-type-category" name="categoryScheme" type="xsd:anyURI"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en"> A type used to record the details of a difference between two business objects/ </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">The type of difference that exists.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">An indication of the severity of the difference.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">The name of the element affected.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">XPath to the element in the base object.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">The value of the element in the base object.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">XPath to the element in the other object.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">Value of the element in the other trade.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">Element(s) that are missing in the other trade.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en"> Element(s) that are extraneous in the other object. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">A human readable description of the problem.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <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: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 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> <!-- RPTWG 2009-11-12 begin--> <xsd:annotation> <xsd:documentation xml:lang="en"> If the trade was cleared (novated) through a central counterparty clearing service, this represents the date the trade was cleared (transferred to the central counterparty). </xsd:documentation> </xsd:annotation> </xsd:element> <!-- RPTWG 2009-11-12 end --> </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:extension> </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: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"> <!--View Generation: SKIPPED versionedTradeId - Unsupported--> </xsd:choice> </xsd:sequence> </xsd:complexType> <xsd:simpleContent> </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:extension> </xsd:simpleContent> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en">Contract Id with Version Support</xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en"> The version of the contract id. The contractId is versioned and not the contract. </xsd:documentation> </xsd:annotation> </xsd:group> </xsd:sequence> </xsd:complexType> <xsd:annotation> <xsd:documentation xml:lang="en">Trade Id with Version Support</xsd:documentation> </xsd:annotation> <xsd:sequence> <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:simpleType> <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> <xsd:element name="instrumentTradeDetails" substitutionGroup="product" type="InstrumentTradeDetails"> <xsd:annotation> <xsd:documentation> A type to hold trades of multiply-traded instruments. Typically this will be used to represent the trade resulting from a physically-settled OTC product where the underlying is a security, for example the exercise of a physically-settled option. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">A strategy product.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:choice> <xsd:annotation> <xsd:documentation xml:lang="en"> Reference to the subaccount definition in the Party list. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">Reference to the party definition.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:choice> </xsd:group> <xsd:sequence> <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:annotation> <xsd:documentation xml:lang="en"> The date on which the the parties enter into the Amendment transaction </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">The date on which the Amendment becomes effective</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:group> <xsd:sequence> <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:documentation>A group including a net and/or a gross amount.</xsd:documentation> </xsd:annotation> <xsd:choice> <xsd:annotation> <xsd:documentation xml:lang="en">Value including fees and commissions.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:sequence> <xsd:annotation> <xsd:documentation xml:lang="en">Value excluding fees and commissions.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation xml:lang="en">Value including fees and commissions.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:choice> </xsd:group> <xsd:annotation> <xsd:documentation> Elements that describe how this document is intended to be processed (in the absence of a full messaging framework). </xsd:documentation> </xsd:annotation> <xsd:choice> <xsd:annotation> <xsd:documentation> Indicates if this message corrects an earlier request. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Indicates if this message corrects an earlier request. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:choice> </xsd:group> <xsd:annotation> <xsd:documentation xml:lang="en"> Choice between identification and representation of trade execution. </xsd:documentation> </xsd:annotation> <xsd:choice> <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: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.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration. |