<xsd:complexType name="TradeAlleged">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining the content model for a message sent by a confirmation provider when it believes that one party has been tardy in providing its side of a transaction.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="NotificationMessage">
<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="bestFitTradeId" type="TradeIdentifier" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">A trade identifier for a transaction that closely resembles the characteristics of the trade under consideration.</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 Schema Diagram:
