Definition Type: ComplexType
Name: TradeMatched
Namespace: http://www.fpml.org/2008/FpML-4-5
Type: fpml:NotificationMessage
Containing Schema: fpml-matching-status-4-5.xsd
Abstract False
Documentation:
A type defining the content model for a message indicating that a correlation has been made between two transactions.
Collapse XSD Schema Diagram:
Drilldown into party Drilldown into differences Drilldown into tradeIdentifier Drilldown into validation Drilldown into header Drilldown into actualBuild Drilldown into expectedBuild Drilldown into version Drilldown into Document Drilldown into Message Drilldown into NotificationMessageXSD Diagram of TradeMatched
Collapse XSD Schema Code:
<xsd:complexType name="TradeMatched">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">A type defining the content model for a message indicating that a correlation has been made between two transactions.</xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
        <xsd:extension base="NotificationMessage">
            <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="differences" type="TradeDifference" minOccurs="0" maxOccurs="unbounded" />
                <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>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
header fpml:header (1) (1)
validation fpml:validation 0 unbounded
tradeIdentifier fpml:tradeIdentifier (1) unbounded
differences fpml:differences 0 unbounded
party fpml:party (1) unbounded
<xs:group> fpml:Validation.model (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
version fpml:version Required
expectedBuild fpml:expectedBuild (Optional)
actualBuild fpml:actualBuild (Optional)
Collapse Derivation Tree:
Collapse Comments:
blog comments powered by Disqus