Schema "fpml-doc-5-3.xsd"
Target Namespace:
http://www.fpml.org/FpML-5/confirmation
Version:
$Revision: 9146 $
Defined Components:
global elements, 152 local elements, 66 complexTypes, 1 simpleType, 8 element groups, 1 attribute group
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Irina-Local\SVN-FpML\branches\FpML-5-3-6-REC-1\xml\confirmation\fpml-doc-5-3.xsd; see XML source
Includes Schema:
fpml-asset-5-3.xsd [src]
Included in Schemas (3):
fpml-mktenv-5-3.xsd [src], fpml-msg-5-3.xsd [src], fpml-riskdef-5-3.xsd [src]
All Element Summary
accountReference (defined in AccountReferenceOrPartyReference.model group) Reference to the subaccount definition in the Party list.
Type:
Content:
empty, 1 attribute
Defined:
allocatedFraction The fractional allocation (0.45 = 45%) of the notional and "block" fees to this particular client subaccount.
Type:
xsd:decimal
Content:
simple
Defined:
locally witnin Allocation complexType; see XML source
allocatedNotional The notional allocation (amount and currency) to this particular client account.
Type:
Content:
complex, 1 attribute, 2 elements
Defined:
locally witnin Allocation complexType; see XML source
allocation
Type:
Content:
complex, 10 elements
Defined:
locally witnin Allocations complexType; see XML source
allocations (defined in Trade complexType) "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.
Type:
Content:
complex, 1 element
Defined:
locally witnin Trade complexType; see XML source
allocationsCompleted When allocations for this trade were completely processed.
Type:
xsd:dateTime
Content:
simple
Defined:
allocationsSubmitted When allocations for this trade were submitted or received by this party.
Type:
xsd:dateTime
Content:
simple
Defined:
allocationStatus Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
allocationsUpdated When allocations for this trade were most recently corrected.
Type:
xsd:dateTime
Content:
simple
Defined:
allocationTradeId (defined in PartyTradeIdentifier complexType) The trade id of the allocated trade.
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin PartyTradeIdentifier complexType; see XML source
allocationTradeId (in allocation) Unique ID for the allocation.
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin Allocation complexType; see XML source
amendmentEffectiveDate The date on which the Amendment becomes effective
Type:
xsd:date
Content:
simple
Defined:
amendmentTradeDate The date on which the the parties enter into the Amendment transaction
Type:
xsd:date
Content:
simple
Defined:
approval
Type:
Content:
complex, 3 elements
Defined:
locally witnin Approvals complexType; see XML source
approvals A container for approval states in the workflow.
Type:
Content:
complex, 1 element
Defined:
approver The full name or identifiying ID of the relevant approver.
Type:
xsd:normalizedString
Content:
simple
Defined:
locally witnin Approval complexType; see XML source
basePath XPath to the element in the base object.
Type:
xsd:string
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
baseValue The value of the element in the base object.
Type:
xsd:string
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
blockTradeId The trade id of the block trade.
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin PartyTradeIdentifier complexType; see XML source
brokerPartyReference Identifies that party (or parties) that brokered this trade.
Type:
Content:
empty, 1 attribute
Defined:
locally witnin Trade complexType; see XML source
calculationAgent (defined in CalculationAgent.model group) The ISDA calculation agent responsible for performing duties as defined in the applicable product definitions.
Type:
Content:
complex, 2 elements
Defined:
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.
Type:
Content:
simple, 2 attributes
Defined:
category (defined in PartyTradeInformation complexType) Used to categorize trades into user-defined categories, such as house trades vs. customer trades.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
cleared (in timestamps) When this trade was cleared.
Type:
xsd:dateTime
Content:
simple
Defined:
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).
Type:
Content:
simple, 1 attribute
Defined:
locally witnin TradeHeader complexType; see XML source
clearingStatus (defined in PartyTradeInformation complexType) Describes the status with respect to clearing (e.g.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
collateral (defined in Trade complexType) Defines collateral obiligations of a Party
Type:
Content:
complex, 1 element
Defined:
locally witnin Trade complexType; see XML source
collateral (in allocation) The sum that must be posted upfront to collateralize against counterparty credit risk.
Type:
Content:
complex, 1 element
Defined:
collateralizationType Specifies whether this party posts collateral.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
confirmationMethod Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
confirmed When this trade was confirmed.
Type:
xsd:dateTime
Content:
simple
Defined:
contractId (defined in ContractIdentifier complexType) A contract id which is not version aware.
Type:
Content:
simple, 2 attributes
Defined:
locally witnin ContractIdentifier complexType; see XML source
contractId (in versionedContractId)
Type:
Content:
simple, 2 attributes
Defined:
locally witnin VersionedContractId complexType; see XML source
creditChargeAmount Special credit fee assessed to certain institutions.
Type:
Content:
complex, 1 attribute, 2 elements
Defined:
creditDocument What arrangements will be made to provide credit?
Type:
Content:
simple, 1 attribute
Defined:
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.
Type:
xsd:boolean
Content:
simple
Defined:
determiningParty The party referenced is the ISDA Determination Party that specified in the related Confirmation as Determination Party.
Type:
Content:
empty, 1 attribute
Defined:
locally witnin Trade complexType; see XML source
differences An optional set of detailed difference records.
Type:
Content:
complex, 10 elements
Defined:
locally witnin BestFitTrade complexType; see XML source
differenceSeverity An indication of the severity of the difference.
Type:
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
differenceType The type of difference that exists.
Type:
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
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.
Type:
Content:
complex, 8 elements
Defined:
locally witnin Trade complexType; see XML source
element The name of the element affected.
Type:
xsd:string
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
endUserException Specifies whether the trade is not obligated to be cleared via a derivative clearing organization because the "End User Exception" was invoked.
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin PartyTradeInformation complexType; see XML source
endUserExceptionDeclaration Claims an end user exception and provides supporting evidence.
Type:
Content:
complex, 4 elements
Defined:
locally witnin PartyTradeInformation complexType; see XML source
executionDateTime (defined in PartyTradeInformation complexType) Trade execution date time, for example as provided by a central execution facility.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
executionType Used to describe how the trade was executed, e.g. via voice or electronically.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
executionVenueType Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
extraElement Element(s) that are extraneous in the other object.
Type:
xsd:string
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
governingLaw (defined in Trade complexType) Identification of the law governing the transaction.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin Trade complexType; see XML source
gross Value excluding fees and commissions.
Type:
xsd:decimal
Content:
simple
Defined:
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.
Type:
Content:
empty, 1 attribute
Defined:
locally witnin Trade complexType; see XML source
independentAmount Independent Amount is an amount that usually less creditworthy counterparties are asked to provide.
Type:
Content:
complex, 5 elements
Defined:
locally witnin Collateral complexType; see XML source
instrumentTradeDetails A type to hold trades of multiply-traded instruments.
Type:
Content:
complex, 1 attribute, 14 elements
Subst.Gr:
may substitute for element product
Defined:
globally; see XML source
Used:
never
intentToAllocate Specifies whether the trade is anticipated to be allocated.
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin PartyTradeInformation complexType; see XML source
intentToClear Specifies whether the trade is anticipated to be cleared via a derivative clearing organization
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin PartyTradeInformation complexType; see XML source
isAccountingHedge Specifies whether the trade used to hedge a risk for accounting purposes for the specified party.
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin PartyTradeInformation complexType; see XML source
issuer
Type:
Content:
simple, 1 attribute
Defined:
locally witnin TradeIdentifier complexType; see XML source
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.
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin PartyTradeInformation complexType; see XML source
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.
Type:
Content:
simple, 2 attributes
Defined:
locally witnin PartyTradeIdentifier complexType; see XML source
mandatorilyClearable Whether the particular trade type in question is required by this regulator to be cleared.
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin ReportingRegime complexType; see XML source
masterConfirmationDate (in allocation) The date of the confirmation executed between the parties and intended to govern the allocated trade between those parties.
Type:
xsd:date
Content:
simple
Defined:
message A human readable description of the problem.
Type:
xsd:string
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
missingElement Element(s) that are missing in the other trade.
Type:
xsd:string
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
name (in reportingRegime) Identifies the reporting regime under which this data is reported.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin ReportingRegime complexType; see XML source
net (in principalAmount in principal in instrumentTradeDetails) Value including fees and commissions.
Type:
xsd:decimal
Content:
simple
Defined:
net (in principalAmount in principal in instrumentTradeDetails) Value including fees and commissions.
Type:
xsd:decimal
Content:
simple
Defined:
nominal The monetary value of the security (eg. fixed income security) that was traded).
Type:
Content:
complex, 1 attribute, 2 elements
Defined:
nonpubliclyReported When the non-public report of this was created or received by this party.
Type:
xsd:dateTime
Content:
simple
Defined:
nonpublicReportUpdated When the non-public report of this was most recently corrected or corrections were received by this party.
Type:
xsd:dateTime
Content:
simple
Defined:
nonStandardTerms Indicates that the trade has price-affecting characteristics in addition to the standard real-time reportable terms.
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin PartyTradeInformation complexType; see XML source
notionalAmountReference A reference to the notional amount.
Type:
Content:
empty, 1 attribute
Defined:
locally witnin PercentageRule complexType; see XML source
number (in quantity in instrumentTradeDetails) The (absolute) number of units of the underlying instrument that were traded.
Type:
xsd:decimal
Content:
simple
Defined:
offMarketPrice Indicates that the price does not reflect the current market.
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin PartyTradeInformation complexType; see XML source
onBehalfOf (defined in DataDocument complexType) Indicates which party (and accounts) a trade is being processed for.
Type:
Content:
complex, 2 elements
Defined:
locally witnin DataDocument complexType; see XML source
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).
Type:
xsd:dateTime
Content:
simple
Defined:
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.
Type:
xsd:dateTime
Content:
simple
Defined:
organizationCharacteristic Allows the organization to specify which categories or characteristics apply to it for end-user exception determination.
Type:
Content:
simple, 1 attribute
Defined:
originatingEvent (defined in DataDocument complexType)
Type:
Content:
simple, 1 attribute
Defined:
locally witnin DataDocument complexType; see XML source
originatingTradeId (defined in PartyTradeIdentifier complexType) 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.
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin PartyTradeIdentifier complexType; see XML source
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.
Type:
Content:
complex, 2 attributes, 10 elements
Defined:
locally witnin Trade complexType; see XML source
otherPath XPath to the element in the other object.
Type:
xsd:string
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
otherValue Value of the element in the other trade.
Type:
xsd:string
Content:
simple
Defined:
locally witnin TradeDifference complexType; see XML source
partyPortfolioName The name of the portfolio together with the party that gave the name.
Type:
Content:
complex, 1 attribute, 2 elements
Defined:
locally witnin Portfolio complexType; see XML source
partyReference (defined in AccountReferenceOrPartyReference.model group) Reference to the party definition.
Type:
Content:
empty, 1 attribute
Defined:
partyReference (defined in ContractIdentifier complexType) A pointer style reference to a party identifier defined elsewhere in the document.
Type:
Content:
empty, 1 attribute
Defined:
locally witnin ContractIdentifier complexType; see XML source
partyReference (in partyPortfolioName) A pointer style reference to a party identifier defined elsewhere in the document.
Type:
Content:
empty, 1 attribute
Defined:
locally witnin PartyPortfolioName complexType; see XML source
partyTradeIdentifier (defined in PartyTradeIdentifiers complexType)
Type:
Content:
complex, 1 attribute, 10 elements
Defined:
locally witnin PartyTradeIdentifiers complexType; see XML source
partyTradeIdentifier (defined in Portfolio complexType)
Type:
Content:
complex, 1 attribute, 10 elements
Defined:
locally witnin Portfolio complexType; see XML source
partyTradeIdentifier (in tradeHeader) The trade reference identifier(s) allocated to the trade by the parties involved.
Type:
Content:
complex, 1 attribute, 10 elements
Defined:
locally witnin TradeHeader complexType; see XML source
partyTradeInformation (in tradeHeader) Additional trade information that may be provided by each involved party.
Type:
Content:
complex, 27 elements
Defined:
locally witnin TradeHeader complexType; see XML source
paymentAmount (in paymentDetail) A fixed payment amount.
Type:
Content:
complex, 1 attribute, 2 elements
Defined:
locally witnin PaymentDetail complexType; see XML source
paymentAmount (in paymentDetail) A fixed payment amount.
Type:
Content:
complex, 1 attribute, 2 elements
Defined:
locally witnin PaymentDetail complexType; see XML source
paymentDate (in paymentDetail) Payment date.
Type:
Content:
complex, 1 attribute, 2 elements
Defined:
locally witnin PaymentDetail complexType; see XML source
paymentDetail A container element allowing a schedule of payments associated with the Independent Amount.
Type:
Content:
complex, 1 attribute, 4 elements
Defined:
locally witnin IndependentAmount complexType; see XML source
paymentPercent A percentage of the notional amount.
Type:
xsd:decimal
Content:
simple
Defined:
locally witnin PercentageRule complexType; see XML source
paymentRule A type defining the calculation rule.
Type:
Content:
empty
Defined:
locally witnin PaymentDetail complexType; see XML source
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.
Type:
xsd:boolean
Content:
simple
Defined:
portfolio (defined in DataDocument complexType) An arbitary grouping of trade references (and possibly other portfolios).
Type:
Content:
complex, 1 attribute, 4 elements
Defined:
locally witnin DataDocument complexType; see XML source
portfolio (defined in Portfolio complexType) An arbitary grouping of trade references (and possibly other portfolios).
Type:
Content:
complex, 1 attribute, 4 elements
Defined:
locally witnin Portfolio complexType; see XML source
portfolioName (in partyPortfolioName)
Type:
Content:
simple, 2 attributes
Defined:
locally witnin PartyPortfolioName complexType; see XML source
premiumProductReference Indicates which product within a strategy represents the premium payment.
Type:
Content:
empty, 1 attribute
Defined:
locally witnin Strategy complexType; see XML source
pricing The price paid for the instrument.
Type:
Content:
complex, 1 element
Defined:
locally witnin InstrumentTradeDetails complexType; see XML source
principal (in instrumentTradeDetails) The value, in instrument currency, of the amount of the instrument that was traded.
Type:
Content:
complex, 1 element
Defined:
locally witnin InstrumentTradeDetails complexType; see XML source
principalAmount (in principal in instrumentTradeDetails) The net and/or gross value of the amount traded in native currency.
Type:
Content:
complex, 3 elements
Defined:
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.
Type:
xsd:boolean
Content:
simple
Defined:
publiclyReported When the public report of this was created or received by this party.
Type:
xsd:dateTime
Content:
simple
Defined:
publicReportUpdated When the public report of this was most recently corrected or corrections were sent or received by this party.
Type:
xsd:dateTime
Content:
simple
Defined:
quantity (in instrumentTradeDetails) A description of how much of the instrument was traded.
Type:
Content:
complex, 2 elements
Defined:
locally witnin InstrumentTradeDetails complexType; see XML source
queryParameter
Type:
Content:
complex, 3 elements
Defined:
locally witnin QueryPortfolio complexType; see XML source
queryParameterId
Type:
Content:
simple, 2 attributes
Defined:
locally witnin QueryParameter complexType; see XML source
queryParameterOperator
Type:
Content:
simple, 2 attributes
Defined:
locally witnin QueryParameter complexType; see XML source
queryParameterValue
Type:
xsd:normalizedString
Content:
simple
Defined:
locally witnin QueryParameter complexType; see XML source
quote (in pricing)
Type:
Content:
complex, 1 attribute, 15 elements
Defined:
locally witnin InstrumentTradePricing complexType; see XML source
registrationNumber The ID assigned by the regulator (e.g.
Type:
Content:
simple, 1 attribute
Defined:
relatedBusinessUnit Provides information about a unit/division/desk etc. that executed or supports this trade
Type:
Content:
complex, 2 elements
Defined:
locally witnin PartyTradeInformation complexType; see XML source
relatedParty (defined in PartyTradeInformation complexType) This may be used to identify one or more parties that perform a role within the transaction.
Type:
Content:
complex, 4 elements
Defined:
locally witnin PartyTradeInformation complexType; see XML source
relatedParty (in allocation) Specifies any relevant parties to the allocation which should be referenced.
Type:
Content:
complex, 4 elements
Defined:
relatedPerson Provides information about a person that executed or supports this trade
Type:
Content:
complex, 2 elements
Defined:
locally witnin PartyTradeInformation complexType; see XML source
reportingPurpose The reason this message is being sent, for example Snapshot, PET, Confirmation, RealTimePublic.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin ReportingRegime complexType; see XML source
reportingRegime Allows the organization to specify which if any relevant regulators or other supervisory bodies this is relevant for, and what reporting rules apply.
Type:
Content:
complex, 6 elements
Defined:
locally witnin PartyTradeInformation complexType; see XML source
reportingRole (defined in PartyTradeInformation complexType) Identifies the role of this party in reporting this trade (e.g. originator, counterparty).
Type:
Content:
simple, 2 attributes
Defined:
locally witnin PartyTradeInformation complexType; see XML source
reportingRole (in reportingRegime) Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
Type:
Content:
simple, 2 attributes
Defined:
locally witnin ReportingRegime complexType; see XML source
status (in approval) The current state of approval (.e.g preapproved, pending approval, etc.)
Type:
xsd:normalizedString
Content:
simple
Defined:
locally witnin Approval complexType; see XML source
strategy A strategy product.
Type:
Content:
complex, 1 attribute, 8 elements
Subst.Gr:
may substitute for element product
Defined:
globally; see XML source
Used:
never
submittedForClearing When this trade was supplied to a clearing service for clearing.
Type:
xsd:dateTime
Content:
simple
Defined:
submittedForConfirmation When this trade was supplied to a confirmation service or counterparty for confirmation.
Type:
xsd:dateTime
Content:
simple
Defined:
supervisorRegistration (in endUserExceptionDeclaration) Allows the organization to specify which if any relevant regulators it is registered with, and if so their identification number.
Type:
Content:
complex, 2 elements
Defined:
supervisorRegistration (in reportingRegime) Identifies the specific regulator or other supervisory body for which this data is produced.
Type:
Content:
complex, 2 elements
Defined:
locally witnin ReportingRegime complexType; see XML source
supervisorRegistration (in reportingRegime) Identifies the specific regulator or other supervisory body for which this data is produced.
Type:
Content:
complex, 2 elements
Defined:
locally witnin ReportingRegime complexType; see XML source
supervisoryBody The regulator or other supervisory body the organization is registered with (e.g.
Type:
Content:
simple, 1 attribute
Defined:
timestamp Other timestamps for this trade.
Type:
Content:
complex, 2 elements
Defined:
timestamps Allows timing information about a trade to be recorded.
Type:
Content:
complex, 16 elements
Defined:
locally witnin PartyTradeInformation complexType; see XML source
trade (defined in DataDocument complexType) The root element in an FpML trade document.
Type:
Content:
complex, 1 attribute, 12 elements
Defined:
locally witnin DataDocument complexType; see XML source
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
Type:
Content:
complex, 1 attribute, 12 elements
Defined:
tradeDate The trade date.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin TradeHeader complexType; see XML source
tradeHeader The information on the trade which is not product specific, e.g. trade date.
Type:
Content:
complex, 4 elements
Defined:
locally witnin Trade complexType; see XML source
tradeId (defined in Portfolio complexType)
Type:
Content:
simple, 2 attributes
Defined:
locally witnin Portfolio complexType; see XML source
tradeId (defined in TradeIdentifier complexType)
Type:
Content:
simple, 2 attributes
Defined:
locally witnin TradeIdentifier complexType; see XML source
tradeId (defined in TradeIdentifier complexType)
Type:
Content:
simple, 2 attributes
Defined:
locally witnin TradeIdentifier complexType; see XML source
tradeId (in versionedTradeId)
Type:
Content:
simple, 2 attributes
Defined:
locally witnin VersionedTradeId complexType; see XML source
tradeIdentifier (defined in BestFitTrade complexType) The identifier for the trade compared against.
Type:
Content:
complex, 1 attribute, 6 elements
Defined:
locally witnin BestFitTrade complexType; see XML source
trader Identifies the person or persons who assumed the role of trader for this trade.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
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.
Type:
Content:
complex, 1 element
Defined:
transactionCharacteristic Allows the relevant transaction level categories or characteristics to be recorded for end-user exception determination.
Type:
Content:
simple, 1 attribute
Defined:
type (in approval) The type of approval (e.g.
Type:
xsd:normalizedString
Content:
simple
Defined:
locally witnin Approval complexType; see XML source
type (in timestamp)
Type:
Content:
simple, 1 attribute
Defined:
locally witnin TradeTimestamp complexType; see XML source
unit (defined in PartyTradeInformation complexType) Identifies the unit/division/desk etc. that executed or supports this trade
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
updatedForClearing When the most recent correction to this trade was supplied to a clearing service for clearing.
Type:
xsd:dateTime
Content:
simple
Defined:
updatedForConfirmation When the most recent correction to this trade was supplied to a confirmation service or counterparty for confirmation.
Type:
xsd:dateTime
Content:
simple
Defined:
validation A list of validation sets the sender asserts the document is valid with respect to.
Type:
Content:
simple, 1 attribute
Defined:
value (in timestamp)
Type:
xsd:dateTime
Content:
simple
Defined:
locally witnin TradeTimestamp complexType; see XML source
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.
Type:
Content:
simple, 1 attribute
Defined:
locally witnin PartyTradeInformation complexType; see XML source
versionedContractId A contract id which is version aware.
Type:
Content:
complex, 3 elements
Defined:
locally witnin ContractIdentifier complexType; see XML source
versionedTradeId A trade identifier accompanied by a version number.
Type:
Content:
complex, 3 elements
Defined:
locally witnin TradeIdentifier complexType; see XML source
Complex Type Summary
Content:
complex, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Code that describes what type of allocation applies to the trade.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A specific approval state in the workflow.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A type used to record the differences between the current trade and another indicated trade.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
never
The current status value of a clearing request.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type for defining the obligations of the counterparty subject to credit support requirements.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Code that describes what type of collateral is posted by a party to a transaction.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type used to represent the type of mechanism that can be used to confirm a trade.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A contact id identifier allocated by a party.
Content:
simple, 2 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
A type defining a contract identifier issued by the indicated party.
Content:
complex, 1 attribute, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 3 elements
Used:
never
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
A credit arrangement used in support of swaps trading.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
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.
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
The abstract base type from which all FpML compliant messages and documents must be derived.
Content:
empty, 3 attributes
Abstract:
(cannot be assigned directly to elements used in instance XML documents)
Defined:
globally; see XML source
Used:
Records supporting information justifying an end user exception under 17 CFR part 39.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
A type defining the trade execution date time and the source of it.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type used to represent the type of market where a trade can be executed.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type used to represent the type of market where a trade can be executed.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
Content:
complex, 5 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
The economics of a trade of a multiply traded instrument.
Content:
complex, 1 attribute, 14 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
A structure describing the price paid for the instrument.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A structure describing the value in "native" currency of an instrument that was traded.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A structure describing the amount of an instrument that was traded.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
The data type used for issuer identifiers.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
The data type used for link identifiers.
Content:
simple, 2 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
A structure including a net and/or a gross amount and possibly fees and commissions.
Content:
complex, 3 elements
Defined:
globally; see XML source
Used:
A characteristic of an organization used in declaring an end-user exception.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type to represent a portfolio name for a particular party.
Content:
complex, 1 attribute, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 2 elements
Used:
A type defining one or more trade identifiers allocated to the trade by a party.
Content:
complex, 1 attribute, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 18 locations
A type containing multiple partyTradeIdentifier.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
A type defining party-specific additional information that may be recorded against a trade.
Content:
complex, 27 elements
Defined:
globally; see XML source
Includes:
definitions of 25 elements
Used:
Content:
complex, 1 attribute, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
The abstract base type from which all calculation rules of the independent amount must be derived.
Content:
empty
Abstract:
(cannot be assigned directly to elements used in instance XML documents)
Defined:
globally; see XML source
Used:
A type defining a content model for a calculation rule defined as percentage of the notional amount.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
never
A type representing an arbitary grouping of trade references.
Content:
complex, 1 attribute, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 4 elements
Used:
The data type used for portfolio names.
Content:
simple, 2 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
A type representing criteria for defining a query portfolio.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
A type representing an identifier for a parameter describing a query portfolio.
Content:
simple, 2 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
A type representing an operator describing the relationship of a value to its corresponding identifier for a parameter describing a query portfolio.
Content:
simple, 2 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
A type representing a portfolio obtained by querying the set of trades held in a repository.
Content:
complex, 1 attribute, 5 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
never
An ID assigned by a regulator to an organization registered with it.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A value that explains the reason or purpose that information is being reported.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
Provides information about how the information in this message is applicable to a regulatory reporting process.
Content:
complex, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
An identifier of an reporting regime or format used for regulatory reporting, for example DoddFrankAct, MiFID, HongKongOTCDRepository, etc.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type containing a code representing the role of a party in a report, e.g. the originator, the recipient, the counterparty, etc.
Content:
simple, 2 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
A type defining a group of products making up a single trade.
Content:
complex, 1 attribute, 8 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Provides information about a regulator or other supervisory body that an organization is registered with.
Content:
complex, 2 elements
Defined:
globally; see XML source
Used:
An identifier of an organization that supervises or regulates trading activity, e.g.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
The type or meaning of a timestamp.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type defining an FpML trade.
Content:
complex, 1 attribute, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 10 elements
Used:
at 16 locations
A scheme used to categorize positions.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type used to record the details of a difference between two business objects/
Content:
complex, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 10 elements
Used:
A type defining trade related information which is not product specific.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
A trade reference identifier allocated by a party.
Content:
simple, 2 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
A type defining a trade identifier issued by the indicated party.
Content:
complex, 1 attribute, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 4 elements
Used:
at 14 locations
Allows timing information about when a trade was processed and reported to be recorded.
Content:
complex, 16 elements
Defined:
globally; see XML source
Includes:
definitions of 16 elements
Used:
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A generic trade timestamp
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A characteristic of a transaction used in declaring an end-user exception.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A reference identifying a rule within a validation scheme.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
A type used to represent the type of mechanism that can be used to verify a trade.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
Contract Id with Version Support
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Trade Id with Version Support
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Simple Type Summary
A type representing a value corresponding to an identifier for a parameter describing a query portfolio.
Defined:
globally; see XML source
Used:
never
Element Group Summary
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
never
Content:
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
never
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
A group including a net and/or a gross amount.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
Provides information about a regulator or other supervisory body that an organization is registered with.
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Choice between identification and representation of trade execution.
Content:
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
Content:
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
Attribute Group Summary
Set of attributes that define versioning information.
Content:
Defined:
globally; see XML source
Includes:
definitions of 3 attributes
Used:
XML Source
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2002-2012 All rights reserved.
== Financial Products Markup Language is subject to the FpML public license.
== A copy of this license is available at http://www.fpml.org/license/license.html
-->
<xsd:schema attributeFormDefault="unqualified" ecore:documentRoot="FpML" ecore:nsPrefix="conf" ecore:package="org.fpml.confirmation" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/confirmation" version="$Revision: 9146 $" xmlns="http://www.fpml.org/FpML-5/confirmation" 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-3.xsd"/>
<xsd:simpleType name="QueryParameterValue">
<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:complexType name="Allocation">
<xsd:sequence>
<xsd:element name="allocationTradeId" type="TradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">Unique ID for the allocation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<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:element maxOccurs="2" name="allocatedNotional" type="Money">
<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:group ref="AllocationContent.model"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Allocations">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="allocation" type="Allocation"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Approval">
<xsd:annotation>
<xsd:documentation xml:lang="en">A specific approval state in the workflow.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="type" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation xml:lang="en">The type of approval (e.g. "Credit").</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="status" type="xsd:normalizedString">
<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:element minOccurs="0" name="approver" type="xsd:normalizedString">
<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:complexType name="Approvals">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="approval" type="Approval"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="BestFitTrade">
<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:element name="tradeIdentifier" type="TradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">The identifier for the trade compared against.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="differences" type="TradeDifference">
<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:complexType name="Collateral">
<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:element name="independentAmount" type="IndependentAmount">
<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:complexType name="ContractId">
<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 base="Scheme">
<xsd:attribute name="contractIdScheme" type="xsd:anyURI" use="required"/>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="ContractIdentifier">
<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:element 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 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:element maxOccurs="unbounded" name="contractId" type="ContractId">
<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" 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:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:complexType name="CreditDerivativesNotices">
<xsd:sequence>
<xsd:element name="creditEvent" type="xsd:boolean">
<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:element name="publiclyAvailableInformation" type="xsd:boolean">
<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:element name="physicalSettlement" type="xsd:boolean">
<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:complexType name="DataDocument">
<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>
<xsd:group ref="Validation.model"/>
<!--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:element minOccurs="0" name="originatingEvent" type="OriginatingEvent"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="trade" type="Trade">
<xsd:annotation>
<xsd:documentation xml:lang="en">The root element in an FpML trade document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--
<xsd:element name="priceNotation" type="BasicQuotation" minOccurs="0" >
<xsd:annotation>
<xsd:documentation xml:lang="en">Pricing information for the trade.</xsd:documentation>
<xsd:appinfo>
<view:exclusive view="transparency" />
<view:exclusive view="recordkeeping" />
<view:exclusive view="confirmation" />
<view:exclusive view="reporting" />
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
-->
<xsd:element maxOccurs="unbounded" minOccurs="0" name="portfolio" type="Portfolio">
<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:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType abstract="true" name="Document">
<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:attributeGroup ref="VersionAttributes.atts"/>
</xsd:complexType>
<xsd:complexType name="ExecutionDateTime">
<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:complexType name="FirstPeriodStartDate">
<xsd:simpleContent>
<xsd:extension base="xsd:date">
<xsd:attribute ecore:reference="Party" name="href" type="xsd:IDREF" use="required"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="IndependentAmount">
<xsd:sequence>
<xsd:group ref="PayerReceiver.model"/>
<xsd:element maxOccurs="unbounded" name="paymentDetail" type="PaymentDetail">
<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:complexType name="InstrumentTradeDetails">
<xsd:annotation>
<xsd:documentation>
The economics of a trade of a multiply traded instrument.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="Product">
<xsd:sequence>
<xsd:group ref="BuyerSeller.model"/>
<xsd:element ref="underlyingAsset">
<xsd:annotation>
<xsd:documentation xml:lang="en">The FpML asset description for the asset.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="quantity" type="InstrumentTradeQuantity">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A description of how much of the instrument was traded.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="pricing" type="InstrumentTradePricing">
<xsd:annotation>
<xsd:documentation xml:lang="en">The price paid for the instrument.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="principal" type="InstrumentTradePrincipal">
<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:complexType name="InstrumentTradeQuantity">
<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:element name="nominal" type="Money">
<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:complexType name="InstrumentTradePricing">
<xsd:annotation>
<xsd:documentation>
A structure describing the price paid for the instrument.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="quote" type="BasicQuotation"/>
</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:complexType name="InstrumentTradePrincipal">
<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:complexType name="LinkId">
<xsd:annotation>
<xsd:documentation xml:lang="en">The data type used for link identifiers.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:attribute name="linkIdScheme" type="xsd:anyURI" use="required"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="NetAndGross">
<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:group ref="NetAndOrGross.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">Net and/or gross amount.</xsd:documentation>
</xsd:annotation>
</xsd:group>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="PartyPortfolioName">
<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 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:element maxOccurs="unbounded" name="portfolioName" type="PortfolioName"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:complexType name="PartyTradeIdentifier">
<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>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="linkId" type="LinkId">
<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:element maxOccurs="unbounded" minOccurs="0" name="allocationTradeId" type="TradeIdentifier">
<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:element minOccurs="0" name="blockTradeId" type="TradeIdentifier">
<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:element maxOccurs="unbounded" minOccurs="0" name="originatingTradeId" type="TradeIdentifier">
<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:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="PartyTradeIdentifiers">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type containing multiple partyTradeIdentifier.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="PartyTradeInformation">
<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: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: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>
<!-- RPTWG 2009-09-04 begin-->
<xsd:element minOccurs="0" name="reportingRole" type="ReportingRole">
<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>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="unit" type="Unit">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identifies the unit/division/desk etc. that executed or supports this trade
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- 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:element maxOccurs="unbounded" minOccurs="0" name="relatedPerson" type="RelatedPerson">
<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:element minOccurs="0" name="isAccountingHedge" type="xsd:boolean">
<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:element maxOccurs="unbounded" minOccurs="0" name="category" type="TradeCategory">
<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 -->
<xsd:element maxOccurs="unbounded" minOccurs="0" name="trader" type="Trader">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identifies the person or persons who assumed the role of trader for this trade.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="executionDateTime" type="ExecutionDateTime">
<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:element minOccurs="0" name="timestamps" type="TradeProcessingTimestamps">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Allows timing information about a trade to be recorded.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="intentToAllocate" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Specifies whether the trade is anticipated to be allocated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="allocationStatus" type="AllocationReportingStatus">
<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:element minOccurs="0" name="intentToClear" type="xsd:boolean">
<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:element minOccurs="0" name="clearingStatus" type="ClearingStatusValue">
<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>
<!-- added BAL 2011-10-18 for DTCC gap analysis -->
<!-- modified BAL 2012-01-23 for CFTC final rules -->
<xsd:element minOccurs="0" name="collateralizationType" type="CollateralizationType">
<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>
<!-- added BAL 2012-01-23 for CFTC final rules -->
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reportingRegime" type="ReportingRegime">
<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>
<!-- end BAL 2011-10-18 additions for DTCC gap analysis -->
<xsd:choice>
<xsd:element minOccurs="0" name="endUserException" type="xsd:boolean">
<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:element minOccurs="0" name="endUserExceptionDeclaration" type="EndUserExceptionDeclaration">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Claims an end user exception and provides supporting evidence.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<!-- end BAL 2011-10-18 additions for DTCC gap analysis -->
<xsd:element minOccurs="0" name="nonStandardTerms" type="xsd:boolean">
<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:element minOccurs="0" name="offMarketPrice" type="xsd:boolean">
<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:element minOccurs="0" name="largeSizeTrade" type="xsd:boolean">
<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:element minOccurs="0" name="executionType" type="ExecutionType">
<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:element minOccurs="0" name="executionVenueType" type="ExecutionVenueType">
<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:element minOccurs="0" name="verificationMethod" type="VerificationMethod">
<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:element minOccurs="0" name="confirmationMethod" type="ConfirmationMethod">
<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:complexType name="AllocationReportingStatus">
<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:complexType name="ClearingStatusValue">
<xsd:annotation>
<xsd:documentation>The current status value of a clearing request.</xsd:documentation>
</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>
<!-- added BAL 2012-01-23 for CFTC final rules -->
<xsd:complexType name="CollateralizationType">
<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:complexType name="EndUserExceptionDeclaration">
<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:complexType name="CreditDocument">
<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:complexType name="OrganizationCharacteristic">
<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:complexType name="TransactionCharacteristic">
<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:complexType name="ReportingPurpose">
<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:complexType name="SupervisorRegistration">
<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:group ref="SupervisorRegistration.model"/>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="SupervisorRegistration.model">
<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:element minOccurs="0" name="registrationNumber" type="RegulatorId">
<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:complexType name="ReportingRegime">
<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" 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:element maxOccurs="unbounded" 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:choice>
<xsd:element minOccurs="0" name="reportingRole" type="ReportingRole">
<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:element maxOccurs="unbounded" minOccurs="0" name="reportingPurpose" type="ReportingPurpose">
<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>
<!-- 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:element name="publiclyReportable" type="xsd:boolean" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">Whether the particular trade type in question is required to be publicly by this regulator. Note that this just says whether the regulator requires public reporting; use reportingPurpose to indicate whether the message is intended to provide public reporting.</xsd:documentation>

</xsd:annotation>
</xsd:element>
-->
<xsd:element minOccurs="0" name="mandatorilyClearable" type="xsd:boolean">
<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:sequence>
</xsd:complexType>
<xsd:complexType name="RegulatorId">
<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 base="Scheme">
<xsd:attribute name="regulatorIdScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="TradeProcessingTimestamps">
<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: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:element minOccurs="0" name="orderSubmitted" type="xsd:dateTime">
<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:element minOccurs="0" name="publiclyReported" type="xsd:dateTime">
<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:element minOccurs="0" name="publicReportUpdated" type="xsd:dateTime">
<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:element minOccurs="0" name="nonpubliclyReported" type="xsd:dateTime">
<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:element minOccurs="0" name="nonpublicReportUpdated" type="xsd:dateTime">
<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:element minOccurs="0" name="submittedForConfirmation" type="xsd:dateTime">
<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:element minOccurs="0" name="updatedForConfirmation" type="xsd:dateTime">
<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:element minOccurs="0" name="confirmed" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation xml:lang="en">When this trade was confirmed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="submittedForClearing" type="xsd:dateTime">
<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:element minOccurs="0" name="updatedForClearing" type="xsd:dateTime">
<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:element minOccurs="0" name="cleared" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation xml:lang="en">When this trade was cleared.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="allocationsSubmitted" type="xsd:dateTime">
<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:element minOccurs="0" name="allocationsUpdated" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation xml:lang="en">
When allocations for this trade were most recently corrected.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="allocationsCompleted" type="xsd:dateTime">
<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:element maxOccurs="unbounded" minOccurs="0" name="timestamp" type="TradeTimestamp">
<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:complexType name="TradeTimestamp">
<xsd:annotation>
<xsd:documentation xml:lang="en">A generic trade timestamp</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="type" type="TimestampTypeScheme"/>
<xsd:element name="value" type="xsd:dateTime"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="TimestampTypeScheme">
<xsd:annotation>
<xsd:documentation xml:lang="en">The type or meaning of a timestamp.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute name="timestampScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!--
<xsd:complexType name="CounterpartyTypes">
<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 base="Scheme">
<xsd:attribute name="counterpartyTypesScheme" type="xsd:anyURI" />
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
-->
<xsd:complexType name="ReportingRegimeName">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An identifier of an reporting regime or format used for regulatory reporting, for example DoddFrankAct, MiFID, HongKongOTCDRepository, etc.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-regime" name="reportingRegimeNameScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="SupervisoryBody">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An identifier of an organization that supervises or regulates trading activity, e.g. CFTC, SEC, FSA, ODRF, etc.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/supervisory-body" name="supervisoryBodyScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- added BAL 2011-02-20 to address CFTC reporting requirements -->
<xsd:complexType name="ExecutionVenueType">
<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>
<!-- added BAL 2011-06-13 to address CFTC reporting requirements -->
<xsd:complexType name="ExecutionType">
<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>
<!-- end BAL 2011-02-20 -->
<xsd:complexType name="ConfirmationMethod">
<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>
<xsd:complexType name="VerificationMethod">
<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:complexType name="PaymentDetail">
<xsd:complexContent>
<xsd:extension base="PaymentBase">
<xsd:sequence>
<xsd:element minOccurs="0" name="paymentDate" type="AdjustableOrRelativeDate">
<xsd:annotation>
<xsd:documentation xml:lang="en">Payment date.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element name="paymentAmount" type="Money">
<xsd:annotation>
<xsd:documentation xml:lang="en">A fixed payment amount.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:sequence>
<xsd:element name="paymentRule" type="PaymentRule">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the calculation rule.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="paymentAmount" type="Money">
<xsd:annotation>
<xsd:documentation xml:lang="en">A fixed payment amount.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType abstract="true" name="PaymentRule">
<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:complexType name="PercentageRule">
<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 name="paymentPercent" type="xsd:decimal">
<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:complexType name="Portfolio">
<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>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="tradeId" type="TradeId"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
</xsd:choice>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="portfolio" type="Portfolio">
<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:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:complexType name="PortfolioName">
<xsd:annotation>
<xsd:documentation xml:lang="en">The data type used for portfolio names.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:attribute name="portfolioNameScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="QueryParameter">
<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:element name="queryParameterId" type="QueryParameterId"/>
<xsd:element minOccurs="0" name="queryParameterValue" type="xsd:normalizedString"/>
<xsd:element minOccurs="0" name="queryParameterOperator" type="QueryParameterOperator"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="QueryParameterId">
<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 base="Scheme">
<xsd:attribute name="queryParameterIdScheme" type="xsd:anyURI" use="required"/>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="QueryParameterOperator">
<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:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/query-parameter-operator" name="queryParameterOperatorScheme" type="xsd:anyURI"/>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="QueryPortfolio">
<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:extension base="Portfolio">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="queryParameter" type="QueryParameter"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ReportingRole">
<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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Strategy">
<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:extension base="Product">
<xsd:sequence>
<xsd:element minOccurs="0" name="premiumProductReference" type="ProductReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates which product within a strategy represents the premium payment.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" ref="product"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="Trade">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining an FpML trade.</xsd:documentation>
</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>
<xsd:element ref="product"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="otherPartyPayment" type="Payment">
<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:element maxOccurs="unbounded" minOccurs="0" name="brokerPartyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identifies that party (or parties) that brokered this trade.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="CalculationAgent.model"/>
<xsd:element maxOccurs="2" minOccurs="0" name="determiningParty" type="PartyReference">
<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:element maxOccurs="2" minOccurs="0" name="hedgingParty" type="PartyReference">
<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:element minOccurs="0" name="collateral" type="Collateral">
<xsd:annotation>
<xsd:documentation xml:lang="en">Defines collateral obiligations of a Party</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="documentation" type="Documentation">
<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:element minOccurs="0" name="governingLaw" type="GoverningLaw">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Identification of the law governing the transaction.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="allocations" type="Allocations">
<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:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:complexType name="TradeCategory">
<xsd:annotation>
<xsd:documentation xml:lang="en">A scheme used to categorize positions.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/org-type-category" name="categoryScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="TradeDifference">
<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:element name="differenceType" type="DifferenceTypeEnum">
<xsd:annotation>
<xsd:documentation xml:lang="en">The type of difference that exists.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="differenceSeverity" type="DifferenceSeverityEnum">
<xsd:annotation>
<xsd:documentation xml:lang="en">An indication of the severity of the difference.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="element" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">The name of the element affected.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="basePath" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">XPath to the element in the base object.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="baseValue" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">The value of the element in the base object.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="otherPath" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">XPath to the element in the other object.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="otherValue" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">Value of the element in the other trade.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="missingElement" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">Element(s) that are missing in the other trade.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="extraElement" type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Element(s) that are extraneous in the other object.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="message" type="xsd:string">
<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:complexType name="TradeHeader">
<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: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:element name="tradeDate" type="IdentifiedDate">
<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:element minOccurs="0" name="clearedDate" type="IdentifiedDate">
<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:complexType name="TradeId">
<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 base="Scheme">
<xsd:attribute name="tradeIdScheme" type="xsd:anyURI" use="required"/>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="TradeIdentifier">
<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>
<xsd:sequence>
<xsd:element name="issuer" type="IssuerId"/>
<xsd:element name="tradeId" type="TradeId"/>
</xsd:sequence>
<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">
<xsd:element name="tradeId" type="TradeId"/>
<xsd:element name="versionedTradeId" type="VersionedTradeId">
<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:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:complexType name="IssuerId">
<xsd:annotation>
<xsd:documentation xml:lang="en">The data type used for issuer identifiers.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute name="issuerIdScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Trader">
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute name="traderScheme" type="xsd:anyURI" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="Validation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A reference identifying a rule within a validation scheme.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute name="validationScheme" type="xsd:anyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="VersionedContractId">
<xsd:annotation>
<xsd:documentation xml:lang="en">Contract Id with Version Support</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="contractId" type="ContractId"/>
<xsd:group ref="VersionHistory.model">
<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:complexType name="VersionedTradeId">
<xsd:annotation>
<xsd:documentation xml:lang="en">Trade Id with Version Support</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="tradeId" type="TradeId"/>
<xsd:group ref="VersionHistory.model">
<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:attributeGroup name="VersionAttributes.atts">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Set of attributes that define versioning information.
</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="fpmlVersion" use="required">
<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:attribute name="expectedBuild" type="xsd:positiveInteger">
<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:attribute fixed="6" name="actualBuild" type="xsd:positiveInteger">
<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:element name="strategy" substitutionGroup="product" type="Strategy">
<xsd:annotation>
<xsd:documentation xml:lang="en">A strategy product.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element name="accountReference" type="AccountReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Reference to the subaccount definition in the Party list.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="partyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">Reference to the party definition.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<xsd:group name="AllocationContent.model">
<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:element minOccurs="0" name="creditChargeAmount" type="Money">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Special credit fee assessed to certain institutions.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="approvals" type="Approvals">
<xsd:annotation>
<xsd:documentation xml:lang="en">A container for approval states in the workflow.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="masterConfirmationDate" type="xsd:date">
<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:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty">
<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:group name="AmendmentDetails.model">
<xsd:sequence>
<xsd:element name="amendmentTradeDate" type="xsd:date">
<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:element name="amendmentEffectiveDate" type="xsd:date">
<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:group name="CalculationAgent.model">
<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:element minOccurs="0" name="calculationAgentBusinessCenter" type="BusinessCenter">
<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:group name="NetAndOrGross.model">
<xsd:annotation>
<xsd:documentation>A group including a net and/or a gross amount.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element name="net" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">Value including fees and commissions.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:sequence>
<xsd:element name="gross" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">Value excluding fees and commissions.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="net" type="xsd:decimal">
<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:group name="TradeOrTradeReference.model">
<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:element name="tradeReference" type="PartyTradeIdentifiers">
<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.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.