<xsd:complexType name="RepoFarLeg">
<xsd:annotation>
<xsd:documentation xml:lang="en">A transaction leg for a repo is equivalent to a single cash transaction. It is augmented here to carry some values that are of interest for the repo. Also note that the BuyerSeller model in this transaction must be the exact opposite of the one found in the near leg.</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: extends "leg" type-->
<!--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-04-07:FpML SecWG: agreed to revert back to SettlementAmountOrCurrency.model within RepoFarLeg, instead of "RelaxedMoney", a Money type with relaxed amount-->
<!--2015-03-23:FpML SecWG: Within FarRepoTransactionLeg, settlementAmount to have Relaxed content of Money-->
<xsd:group ref="SettlementAmountOrCurrency.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">Settlement amount of the securities transaction. When the exact financial amount to the transaction is not known (for instance in far leg of a floating rate repo), this structure allows participants to state the currency of the transaction.</xsd:documentation>
</xsd:annotation>
</xsd:group>
<!--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" minOccurs="0">
<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" minOccurs="0" 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:element name="repoInterest" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">The repo interest is basically the difference between the settlement amounts at spot and forward date. It is a fully figured amount, but it does not have to be specified in the message. It is not a 'Money' amount as it is implicitly expressed in the settlement currency.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
|