# XML Schema Documentation

### Complex Type: Trade

#### [Table of contents]

Super-types: | None
Sub-types: | None

Name | Trade
Used by (from the same schema document) | Complex Type Amendment , Complex Type DataDocument , Model Group TradeOrTradeReference.model
Abstract | no
Documentation | A type defining an FpML trade.

XML Instance Representation
<...
id=" xsd:ID [0..1]">
<tradeHeader> TradeHeader </tradeHeader> [1]

'The information on the trade which is not product specific, e.g. trade date.'

<product> ... </product> [1]
<otherPartyPayment> Payment </otherPartyPayment> [0..*]

'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.'

<brokerPartyReference> PartyReference </brokerPartyReference> [0..*]

'Identifies that party (or parties) that brokered this trade.'

<calculationAgent> CalculationAgent </calculationAgent> [0..1]

'The ISDA Calculation Agent responsible for performing duties associated with an optional early termination.'

<calculationAgentBusinessCenter> BusinessCenter </calculationAgentBusinessCenter> [0..1]

'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.'

<collateral> Collateral </collateral> [0..1]

'Defines collateral obiligations of a Party'

<documentation> Documentation </documentation> [0..1]

'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.'

<governingLaw> GoverningLaw </governingLaw> [0..1]

'Identification of the law governing the transaction.'

<allocations> Allocations </allocations> [0..1]

'"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.'

<tradeSide> TradeSide </tradeSide> [0..2]

'The parties to the Trade are grouped into Trade Sides. Each Trade has as many as two sides. Each side is a buyer or receiver of each leg or stream.'

</...>
Diagram
Schema Component Representation
<xsd:complexType name="Trade">
<xsd:sequence>
<xsd:element name="tradeHeader" type=" TradeHeader "/>
<xsd:element ref=" product "/>
<xsd:element name="otherPartyPayment" type=" Payment " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="brokerPartyReference" type=" PartyReference " minOccurs="0" maxOccurs="unbounded"/>
<xsd:group ref=" CalculationAgent.model "/>
<xsd:element name="collateral" type=" Collateral " minOccurs="0"/>
<xsd:element name="documentation" type=" Documentation " minOccurs="0"/>
<xsd:element name="governingLaw" type=" GoverningLaw " minOccurs="0"/>
<xsd:element name="allocations" type=" Allocations " minOccurs="0"/>
<xsd:element name="tradeSide" type=" TradeSide " minOccurs="0" maxOccurs="2"/>
</xsd:sequence>
<xsd:attribute name="id" type=" xsd:ID "/>
</xsd:complexType>