<!--
== Copyright (c) 2002-2007. 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 xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.fpml.org/2007/FpML-4-4" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:fpml="http://www.fpml.org/2007/FpML-4-4" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" ecore:nsPrefix="fpml" ecore:package="org.fpml" ecore:documentRoot="FpML" targetNamespace="http://www.fpml.org/2007/FpML-4-4" version="$Revision: 2350 $" attributeFormDefault="unqualified" elementFormDefault="qualified">
<xsd:include schemaLocation="fpml-msg-4-4.xsd" />
<xsd:complexType name="CancelTradeConfirmation">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model for a message requesting that a previously requested TradeConfirmation process be cancelled.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="RequestMessage">
<xsd:sequence>
<xsd:element 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 name="party" type="Party">
<xsd:annotation>
<xsd:documentation xml:lang="en">A legal entity or a subdivision of a legal entity.</xsd:documentation>
<xsd:documentation xml:lang="en">Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConfirmationCancelled">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model for the message generated in response to a CancelConfirmation request under normal circumstances.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:element name="tradeIdentifier" type="TradeIdentifier">
<xsd:annotation>
<xsd:documentation xml:lang="en">An instance of a unique trade identifier.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="party" type="Party">
<xsd:annotation>
<xsd:documentation xml:lang="en">A legal entity or a subdivision of a legal entity.</xsd:documentation>
<xsd:documentation xml:lang="en">Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ConfirmTrade">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model for a message that indicates acceptance of a previously matched trade.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="RequestMessage">
<xsd:sequence>
<xsd:element 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 name="party" type="Party">
<xsd:annotation>
<xsd:documentation xml:lang="en">A legal entity or a subdivision of a legal entity.</xsd:documentation>
<xsd:documentation xml:lang="en">Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ModifyTradeConfirmation">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model for a message requesting that the details of a trade previously sent for confirmation be changed.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="RequestMessage">
<xsd:sequence>
<xsd:element 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="party" type="Party" minOccurs="2" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">A legal entity or a subdivision of a legal entity.</xsd:documentation>
<xsd:documentation xml:lang="en">Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RequestTradeConfirmation">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model for a message requesting that the contained trade be put forward for matching and confirmation.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="RequestMessage">
<xsd:sequence>
<xsd:element 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="party" type="Party" minOccurs="2" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">A legal entity or a subdivision of a legal entity.</xsd:documentation>
<xsd:documentation xml:lang="en">Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeAffirmation">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model for a message that indicates that a trade is considered affirmed by the sender.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NotificationMessage">
<xsd:sequence>
<xsd:element 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="party" type="Party" minOccurs="2" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">A legal entity or a subdivision of a legal entity.</xsd:documentation>
<xsd:documentation xml:lang="en">Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeAffirmed">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model for a message generated when a party confirms that a trade is affirmed.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:element name="tradeIdentifier" type="TradeIdentifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">An instance of a unique trade identifier.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="party" type="Party" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">A legal entity or a subdivision of a legal entity.</xsd:documentation>
<xsd:documentation xml:lang="en">Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeAlreadyAffirmed">
<xsd:annotation>
<xsd:documentation xml:lang="en">An error response message indicating that a trade has already been affirmed.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="TradeErrorResponse" />
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeAlreadyConfirmed">
<xsd:annotation>
<xsd:documentation xml:lang="en">An error response message indicating that a trade has already been confirmed.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="TradeErrorResponse" />
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="TradeConfirmed">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model of a message generated when a trade is determined to be confirmed.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NotificationMessage">
<xsd:sequence>
<xsd:element 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="party" type="Party" minOccurs="2" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">A legal entity or a subdivision of a legal entity.</xsd:documentation>
<xsd:documentation xml:lang="en">Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
|
XSD Schema Code: