Definition Type: ComplexType
Name: RepoNearLeg
Namespace: http://www.fpml.org/FpML-5/confirmation
Type: nsA:RepoLegBase
Containing Schema: fpml-repo-5-8.xsd
Abstract
Documentation:
A transaction leg for a repo is equivalent to a single cash transaction.
Collapse XSD Schema Diagram:
Drilldown into collateral in schema fpml-repo-5-8_xsd Drilldown into deliveryDate in schema fpml-repo-5-8_xsd Drilldown into deliveryMethod in schema fpml-repo-5-8_xsd Drilldown into fxRate in schema fpml-repo-5-8_xsd Drilldown into settlementAmount in schema fpml-repo-5-8_xsd Drilldown into settlementDate in schema fpml-repo-5-8_xsd Drilldown into sellerAccountReference in schema fpml-shared-5-8_xsd Drilldown into sellerPartyReference in schema fpml-shared-5-8_xsd Drilldown into buyerAccountReference in schema fpml-shared-5-8_xsd Drilldown into buyerPartyReference in schema fpml-shared-5-8_xsd Drilldown into BuyerSeller.model in schema fpml-shared-5-8_xsd Drilldown into id in schema fpml-shared-5-8_xsd Drilldown into Leg in schema fpml-shared-5-8_xsd Drilldown into RepoLegBase in schema fpml-repo-5-8_xsdXSD Diagram of RepoNearLeg in schema fpml-repo-5-8_xsd (Financial products Markup Language (FpML®))
Collapse XSD Schema Code:
<xsd:complexType name="RepoNearLeg">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">A transaction leg for a repo is equivalent to a single cash transaction.</xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
        <!--2015-04-17:FpML Sec WG: Agreed to created a RepoTransactionBaseLeg type to group some of the shared near and far legs' components: "BuyerSeller.model, settlementDate, deliveryMethod, deliveryDate. This base type could be also used in the future securities' products.-->
        <!--2015-02-23: Sec WG: agreed to remove attribute "id", instead extension from base class "Leg" which already includes attribute "id"-->
        <xsd:extension base="RepoLegBase">
            <xsd:sequence>
                <!--2015-03-23:FpML SecWG: Replaced SettlementAmountOrCurrency.model with "settlementAmount" of type "Money" -->
                <xsd:element name="settlementAmount" type="Money">
                    <xsd:annotation>
                        <xsd:documentation xml:lang="en">Settlement Amount</xsd:documentation>
                    </xsd:annotation>
                </xsd:element>
                <!--2015-01-21:SecWG proposal: TBD-->
                <xsd:element name="fxRate" type="FxRate" minOccurs="0">
                    <xsd:annotation>
                        <xsd:documentation xml:lang="en">Indicates the rate of a currency conversion that is used to compute settlement amount for cross-currency transactions.</xsd:documentation>
                    </xsd:annotation>
                </xsd:element>
                <!--2015-04-14:FpML SecWG proposed associate the collateral collection with delivery method and date to create a dependency between deliveryMethod and collateral in a natural way using an optional sequence.-->
                <xsd:sequence minOccurs="0">
                    <xsd:element name="deliveryMethod" type="DeliveryMethod">
                        <xsd:annotation>
                            <xsd:documentation xml:lang="en">Specifies a delivery method for the security transaction.</xsd:documentation>
                        </xsd:annotation>
                    </xsd:element>
                    <xsd:element name="deliveryDate" type="AdjustableOrRelativeDate" minOccurs="0">
                        <xsd:annotation>
                            <xsd:documentation xml:lang="en">Delivery Date for the transaction. Delivery Date can be populated when it is not equal to the Settlement Date.</xsd:documentation>
                        </xsd:annotation>
                    </xsd:element>
                    <xsd:element name="collateral" type="CollateralValuation" maxOccurs="unbounded">
                        <xsd:annotation>
                            <xsd:documentation xml:lang="en">Collateral element is used to carry the quantity and price details that are required to ensure that a repo contract is executed at fair value, with the value of the collateral matching the cash amount of the repo. Collateral is declared as optional here, with multiple cardinalities, since there can be a repo "Multi", with multiple instruments specified, or a "Cash Borrow/Loan" and “TriPartyRepo” with no collateral. In general cases, however it should be specified. This element can be omitted in farLeg.</xsd:documentation>
                        </xsd:annotation>
                    </xsd:element>
                </xsd:sequence>
            </xsd:sequence>
        </xsd:extension>
    </xsd:complexContent>
</xsd:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
buyerPartyReference nsA:buyerPartyReference (1) (1)
buyerAccountReference nsA:buyerAccountReference 0 (1)
sellerPartyReference nsA:sellerPartyReference (1) (1)
sellerAccountReference nsA:sellerAccountReference 0 (1)
settlementDate nsA:settlementDate (1) (1)
settlementAmount nsA:settlementAmount (1) (1)
fxRate nsA:fxRate 0 (1)
deliveryMethod nsA:deliveryMethod (1) (1)
deliveryDate nsA:deliveryDate 0 (1)
collateral nsA:collateral (1) unbounded
<xs:group> nsA:BuyerSeller.model (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
id nsA:id (Optional)
Collapse Derivation Tree:
Collapse References:
nsA:nearLeg