XML Schema "fpml-repo-5-8.xsd"
Target Namespace:
http://www.fpml.org/FpML-5/confirmation
Version:
$Revision: 11232 $
Defined Components:
elements (1 global + 49 local), complexTypes (14), element groups (3)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
D:\Tradeheader\FpML-5-8-8-REC-1-branch\xml\confirmation\fpml-repo-5-8.xsd; see XML source
Includes Schemas (1):
fpml-business-events-5-8.xsd [src]
Included in Schemas (1):
fpml-main-5-8.xsd [src]
All Element Summary
accruals
Accruals, relationship is clean price and accruals equals dirty price, all prices are expressed in percentage points, 100 is the initial value of the bond.
Type:
xsd:decimal
Content:
simple
Defined:
locally within BondPriceAndYield.model group; see XML source
accrualsAmount
Accruals expressed as amount.
Type:
Money
Content:
complex, 1 attribute, 2 elements
Defined:
locally within BondCollateral.model group; see XML source
allInPrice
Bond all-in-price which is a price that includes all relevant price adjustments (i.e. accrued interest, haircut or margin ratio, inflation factor,etc.).
Type:
xsd:decimal
Content:
simple
Defined:
locally within BondPriceAndYield.model group; see XML source
assetReference (defined in CollateralValuation complexType)
A reference to explicitly identify which asset is being valued.
Type:
AssetReference
Content:
empty, 1 attribute
Defined:
locally within CollateralValuation complexType; see XML source
assetReference (in margin)
A reference to the collateral asset to which the margin requirement applies.
Type:
AssetReference
Content:
empty, 1 attribute
Defined:
locally within InitialMarginCalculation complexType; see XML source
callDate
Defines the latest date when the open repo transaction can be exercised (and no later than which it must be exercised) on demand by a party to the trade indicated in the electingParty element (or in the Master Agreement, if the electingParty element has AsDefinedInMasterAgreement value).
Type:
AdjustableOrRelativeDate
Content:
complex, 1 attribute, 2 elements
Defined:
locally within Repo complexType; see XML source
callingParty
A party to the open repo transaction that has a right to demand for exercise of far leg of the open repo transaction.
Type:
CallingPartyEnum
Content:
simple
Defined:
locally within Repo complexType; see XML source
cleanPrice
Bond clean price, expressed in percentage points, 100 is the initial value of the bond.
Type:
xsd:decimal
Content:
simple
Defined:
locally within BondPriceAndYield.model group; see XML source
collateral (in farLeg in repo)
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.
Type:
CollateralValuation
Content:
complex, 13 elements
Defined:
locally within RepoFarLeg complexType; see XML source
collateral (in nearLeg in repo)
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.
Type:
CollateralValuation
Content:
complex, 13 elements
Defined:
locally within RepoNearLeg complexType; see XML source
collateralProfile
The collateral profile specified at the tri-party agent.
Type:
CollateralProfile
Content:
simple, 1 attribute
Defined:
locally within TriParty complexType; see XML source
collateralType
The collateral type, which is a restriction of the collateral deemed acceptable for the purpose of the transaction.
Type:
CollateralType
Content:
simple, 1 attribute
Defined:
locally within TriParty complexType; see XML source
dayCountFraction (in repo)
The day count fraction.
Type:
DayCountFraction
Content:
simple, 1 attribute
Defined:
locally within Repo complexType; see XML source
deliveryDate (in farLeg in repo)
Delivery Date for the transaction.
Type:
AdjustableOrRelativeDate
Content:
complex, 1 attribute, 2 elements
Defined:
locally within RepoFarLeg complexType; see XML source
deliveryDate (in nearLeg in repo)
Delivery Date for the transaction.
Type:
AdjustableOrRelativeDate
Content:
complex, 1 attribute, 2 elements
Defined:
locally within RepoNearLeg complexType; see XML source
deliveryMethod (in farLeg in repo)
Specifies a delivery method for the security transaction.
Type:
DeliveryMethod
Content:
simple, 1 attribute
Defined:
locally within RepoFarLeg complexType; see XML source
deliveryMethod (in nearLeg in repo)
Specifies a delivery method for the security transaction.
Type:
DeliveryMethod
Content:
simple, 1 attribute
Defined:
locally within RepoNearLeg complexType; see XML source
dirtyPrice (defined in BondPriceAndYield.model group)
Bond dirty price, expressed in percentage points, 100 is the initial value of the bond.
Type:
xsd:decimal
Content:
simple
Defined:
locally within BondPriceAndYield.model group; see XML source
dirtyPrice (defined in BondPriceAndYield.model group)
Bond dirty price, expressed in percentage points, 100 is the initial value of the bond.
Type:
xsd:decimal
Content:
simple
Defined:
locally within BondPriceAndYield.model group; see XML source
duration (in repo)
A duration code for the repo transaction.
Type:
RepoDurationEnum
Content:
simple
Defined:
locally within Repo complexType; see XML source
farLeg (in repo)
The far leg of the repo contract, i.e. the repurchase transaction.
Type:
RepoFarLeg
Content:
complex, 1 attribute, 12 elements
Defined:
locally within Repo complexType; see XML source
fixedRateSchedule (in repo)
The fixed repo rate.
Type:
Schedule
Content:
complex, 1 attribute, 2 elements
Defined:
locally within Repo complexType; see XML source
floatingRateCalculation (in repo)
The floating rate index and tenor, with additional definitions relating to the calculation of floating rate amounts, including spread and multiplier.
Type:
FloatingRateCalculation
Content:
complex, 1 attribute, 11 elements
Defined:
locally within Repo complexType; see XML source
fxRate (in farLeg in repo)
Indicates the rate of a currency conversion that is used to compute settlement amount for cross-currency transactions.
Type:
FxRate
Content:
complex, 2 elements
Defined:
locally within RepoFarLeg complexType; see XML source
fxRate (in nearLeg in repo)
Indicates the rate of a currency conversion that is used to compute settlement amount for cross-currency transactions.
Type:
FxRate
Content:
complex, 2 elements
Defined:
locally within RepoNearLeg complexType; see XML source
haircut
An element defining a haircut expressed as the percentage difference between the Market Value of the collateral and the Purchase Price of the repo and calculated as 100 multiplied by a ratio of the difference between the Market Value of the collateral and the Purchase Price of the repo to the Market Value of the collateral.
Type:
xsd:decimal
Content:
simple
Defined:
locally within InitialMarginCalculation complexType; see XML source
haircutThreshold
An element defining a haircut percentage threshold which is the value above (when it's lower than initial haircut) or below (when it's higher than initial haircut) which parties agree they will not call a margin from each other.
Type:
xsd:decimal
Content:
simple
Defined:
locally within InitialMarginCalculation complexType; see XML source
inflationFactor
The inflation factor is specified for inflation-linked products which require some additional elements to calculate prices correctly.
Type:
xsd:decimal
Content:
simple
Defined:
locally within BondPriceAndYield.model group; see XML source
initialMargin
Defines initial margin applied to a repo transaction.
Type:
InitialMargin
Content:
complex, 4 elements
Defined:
locally within Repo complexType; see XML source
margin
Initial margin calculation for a collateral asset.
Type:
InitialMarginCalculation
Content:
complex, 5 elements
Defined:
locally within InitialMargin complexType; see XML source
marginRatio
An element defining an initial margin expressed as a ratio of the Market Value of the collateral to the Purchase Price.
Type:
xsd:decimal
Content:
simple
Defined:
locally within InitialMarginCalculation complexType; see XML source
marginRatioThreshold
An element defining a margin ratio threshold which is the value above (when it's lower than initial margin ratio) or below (when it's higher than initial margin ratio) which parties agree they will not call a margin from each other.
Type:
xsd:decimal
Content:
simple
Defined:
locally within InitialMarginCalculation complexType; see XML source
marginThreshold
An element defining a margin threshold which is the Net Exposure of a trade below which parties agree they will not call a margin from each other.
Type:
NonNegativeMoney
Content:
complex, 1 attribute, 2 elements
Defined:
locally within InitialMargin complexType; see XML source
marginType
An element defining the type of assets (cash or securities) specified to apply as margin to the repo transaction.
Type:
MarginTypeEnum
Content:
simple
Defined:
locally within InitialMargin complexType; see XML source
minimumTransferAmount
An element defining a minimum transfer amount which is the minimum margin call parties will make once the margin threshold (or margin ratio threshold / haircut threshold) has been exceeded.
Type:
NonNegativeMoney
Content:
complex, 1 attribute, 2 elements
Defined:
locally within InitialMargin complexType; see XML source
nearLeg (in repo)
A repo contract is modeled as two purchase/repurchase transactions which are called legs.
Type:
RepoNearLeg
Content:
complex, 1 attribute, 10 elements
Defined:
locally within Repo complexType; see XML source
nominalAmount
Total nominal amount of the given bonds used as collateral.
Type:
Money
Content:
complex, 1 attribute, 2 elements
Defined:
locally within BondCollateral.model group; see XML source
noticePeriod (in partyNoticePeriod)
Notice period for open repo transactions in number of days.
Type:
AdjustableOffset
Content:
complex, 1 attribute, 5 elements
Defined:
locally within PartyNoticePeriod complexType; see XML source
noticePeriod (in repo)
Notice period for open repo transactions in number of days.
Type:
AdjustableOffset
Content:
complex, 1 attribute, 5 elements
Defined:
locally within Repo complexType; see XML source
partyNoticePeriod
Notice period for open repo transactions referenced to a party to the trade, in number of days.
Type:
PartyNoticePeriod
Content:
complex, 2 elements
Defined:
locally within Repo complexType; see XML source
partyReference (in partyNoticePeriod)
A reference to a party who has the right to request exercise of the open repo trade and for whom noticePeriod is defined.
Type:
PartyReference
Content:
empty, 1 attribute
Defined:
locally within PartyNoticePeriod complexType; see XML source
relativePrice
Bond price relative to a Benchmark.
Type:
RelativePrice
Content:
complex, 4 elements
Defined:
locally within BondPriceAndYield.model group; see XML source
repo
Global element representing a Repo.
Type:
Repo
Content:
complex, 1 attribute, 20 elements
Subst.Gr:
may substitute for element product
Defined:
globally; see XML source
Used:
never
repoInterest
The repo interest is basically the difference between the settlement amounts at spot and forward date.
Type:
xsd:decimal
Content:
simple
Defined:
locally within RepoFarLeg complexType; see XML source
settlementAmount (in nearLeg in repo)
Settlement Amount
Type:
Money
Content:
complex, 1 attribute, 2 elements
Defined:
locally within RepoNearLeg complexType; see XML source
settlementDate (defined in RepoLegBase complexType)
Settlement or Payment Date for the transaction.
Type:
AdjustableOrRelativeDate
Content:
complex, 1 attribute, 2 elements
Defined:
locally within RepoLegBase complexType; see XML source
spread (in relativePrice)
Basis Point spread over a Benchmark.
Type:
xsd:decimal
Content:
simple
Defined:
locally within RelativePrice complexType; see XML source
triParty
Type:
TriParty
Content:
complex, 3 elements
Defined:
locally within Repo complexType; see XML source
triPartyAgent
The reference to the tri-party agent.
Type:
PartyReference
Content:
empty, 1 attribute
Defined:
locally within TriParty complexType; see XML source
yieldToMaturity
Yield to Maturity.
Type:
xsd:decimal
Content:
simple
Defined:
locally within BondPriceAndYield.model group; see XML source
Complex Type Summary
AdjustableOffset
An adjustable offset can be used to specify a number of days, business or calendar, for example in a notice period.
Content:
complex, 1 attribute, 5 elements
Defined:
globally; see XML source
Used:
at 2 locations
CollateralProfile
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 1 location
CollateralType
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 1 location
CollateralValuation
This type is used in Repo trades, to specify the valuation of a specific piece of collateral in the transaction.
Content:
complex, 13 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 2 locations
DeliveryMethod
Specifies delivery methods for securities transactions.
Content:
simple, 1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 2 locations
InitialMargin
Defines initial margin applied to a repo transaction.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
InitialMarginCalculation
Defines the initial margin calculation applicable to a single piece of collateral.
Content:
complex, 5 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
PartyNoticePeriod
A type to represent agreed period of notice to be given in advance before exercise of the open repo trade by a party requesting such exercise and reference to that party.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
RelativePrice
A type which represents Pricing relative to a Benchmark.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
Repo
A Repo, modeled as an FpML:Product.
Content:
complex, 1 attribute, 20 elements
Defined:
globally; see XML source
Includes:
definitions of 12 elements
Used:
at 1 location
RepoFarLeg
A transaction leg for a repo is equivalent to a single cash transaction.
Content:
complex, 1 attribute, 12 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
RepoLegBase
A transaction leg for a repo is equivalent to a single cash transaction.
Content:
complex, 1 attribute, 5 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 2 locations
RepoNearLeg
A transaction leg for a repo is equivalent to a single cash transaction.
Content:
complex, 1 attribute, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
TriParty
The tri-party terms.
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
Element Group Summary
BondCollateral.model
A group which has Collateral elements.
Content:
10 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
BondEquity.model
A model group that allows us to specify that a repo contract can reference bond or equity instruments.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 2 locations
BondPriceAndYield.model
A group which has either Bond Price or Yield elements.
Content:
8 elements
Defined:
globally; see XML source
Includes:
definitions of 8 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2002-2016 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 attributeFormDefault="unqualified" ecore:documentRoot="FpML" ecore:nsPrefix="conf" ecore:package="org.fpml.confirmation" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/confirmation" version="$Revision: 11232 $" xmlns="http://www.fpml.org/FpML-5/confirmation" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:fpml-annotation="http://www.fpml.org/annotation" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation="fpml-business-events-5-8.xsd"/>
<xsd:complexType name="AdjustableOffset">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An adjustable offset can be used to specify a number of days, business or calendar, for example in a notice period.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="Offset">
<xsd:sequence>
<xsd:group minOccurs="0" ref="BusinessCentersOrReference.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--2015-04-13:FpML SecWG added support for TriParty-->
<xsd:complexType name="CollateralProfile">
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute name="collateralProfileScheme" type="NonEmptyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!--2015-04-13:FpML SecWG added support for TriParty-->
<xsd:complexType name="CollateralType">
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute name="collateralTypeScheme" type="NonEmptyURI"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="CollateralValuation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
This type is used in Repo trades, to specify the valuation of a specific piece of collateral in the transaction.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:group ref="BondCollateral.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
When the instrument being used in a transaction is a bond, the group above should be used to properly value the instrument, in terms of price, accruals and notional.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:group ref="UnitContract.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
When the instrument being used in a transaction is an equity, or any contract traded in units, this group should be used to define the quantity, price and valuation of the instrument.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
</xsd:choice>
<xsd:element name="assetReference" type="AssetReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A reference to explicitly identify which asset is being valued.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--2015-04-13:FpML SecWG - removed from collateral-->
<!--<xsd:group ref="MarginRatioOrHaircut.model" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">A group which has a choice between initial margin ratio and haircut. This is used to define initial margin ratio or haircut on per asset basis.</xsd:documentation>
</xsd:annotation>
</xsd:group>-->
</xsd:sequence>
<!--2015-02-23: Sec WG: agreed to remove element "cash" of type “Money" used for security Lending. Rationale: sec lending is not currently in scope -->
</xsd:complexType>
<!--12-08-2014: SecWG agreed to convert DeliveryMethodEnum into deliveryMethodScheme coding scheme-->
<xsd:complexType name="DeliveryMethod">
<xsd:annotation>
<!--<xsd:documentation xml:lang="en">This enumeration defines the possible delivery methods for securities.</xsd:documentation>-->
<xsd:documentation xml:lang="en">
Specifies delivery methods for securities transactions. This coding-scheme defines the possible delivery methods for securities.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
<xsd:attribute default="http://www.fpml.org/coding-scheme/delivery-method" name="deliveryMethodScheme" type="NonEmptyURI"/>
</xsd:extension>
</xsd:simpleContent>
<!--Create deliveryMethodScheme coding scheme with values:
"DeliveryVersusPayment" - "Indicates that a securities delivery must be made against payment in simultaneous transmissions and stipulate each other."
"FreeOfPayment" - "Indicates that a securities delivery can be made without a simultaneous cash payment in exchange and not depending on if payment obligations are fulfilled or not and vice versa."
"PreDelivery" - Indicates that a payment in full amount must be made before the securities delivery; fulfillment of securities delivery obligations depends on payment obligations fulfillment."
"PrePayment" - Indicates that a securities delivery must be made in full before the payment for the securities; fulfillment of payment obligations depends on securities delivery obligations fulfillment.-->
</xsd:complexType>
<xsd:complexType name="InitialMargin">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines initial margin applied to a repo transaction. Initial margin is an agreed premium to the Purchase Price of a repo to determine the required Market Value of the collateral to be delivered on the Purchase Date. It reflects quality of the collateral. Its aim is to calculate the risk-adjusted or liquidation value of collateral.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="marginType" type="MarginTypeEnum">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An element defining the type of assets (cash or securities) specified to apply as margin to the repo transaction. See GMRA 2011 paragraph 2(h) for "Cash Margin" and GMRA 2011 paragraph 2(cc) for "Margin Securities".
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--2015-04-13:FpML SecWG agreed to replace a choice of MarginRatioOrHaircut.model and isSpecifiedForCollateralPieces boolean indicator with "margin" place holder which would group {1 - unbounded} MarginRatioOrHaircut's elements and an optional assetReference to support the cases when the margin is provided per collateral asset.-->
<xsd:element maxOccurs="unbounded" name="margin" type="InitialMarginCalculation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Initial margin calculation for a collateral asset. Initial margin requirements may be specified for multiple pieces of collateral.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--09-29-2014: SecWG agreed agreed on the substance of this model, but model might be refined later own to give the control over the elements to the schema -->
<!--09-29-2014: SecWG agreed to remove container margin call details-->
<xsd:element minOccurs="0" name="marginThreshold" type="NonNegativeMoney">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An element defining a margin threshold which is the Net Exposure of a trade below which parties agree they will not call a margin from each other.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="minimumTransferAmount" type="NonNegativeMoney">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An element defining a minimum transfer amount which is the minimum margin call parties will make once the margin threshold (or margin ratio threshold / haircut threshold) has been exceeded.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="InitialMarginCalculation">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines the initial margin calculation applicable to a single piece of collateral.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<!--2015-04-13:FpML SecWG replaced "MarginRatioOrHaircut.model" with direct elements from the model-->
<!--09-29-2014: SecWG: agreed to a choice of initialMarginRatio (renamed from marginFactor) and haircut-->
<xsd:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A choice between initial margin ratio and haircut.
</xsd:documentation>
</xsd:annotation>
<!--11-10-2014: SecWG: agreed to grouping of "initialMarginRatio" and "marginRatioThreshold" -->
<xsd:sequence>
<!--11-24-2014: SecWG: reverted back the renaming "initialMarginRatio” from marginRatio. The currently agreed name of the element - marginRatio-->
<xsd:element name="marginRatio" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An element defining an initial margin expressed as a ratio of the Market Value of the collateral to the Purchase Price. A default value of initial margin ratio of 1.00 means there is no margin and thus no risk related with the collateral. See GMRA 2000 paragraph 2(z) and GMRA 2011 paragraph 2(bb).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="2" minOccurs="0" name="marginRatioThreshold" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An element defining a margin ratio threshold which is the value above (when it's lower than initial margin ratio) or below (when it's higher than initial margin ratio) which parties agree they will not call a margin from each other.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<!--11-10-2014: SecWG: agreed to grouping of "haircutPercentage" and "haircutThreshold" -->
<xsd:sequence>
<xsd:element name="haircut" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An element defining a haircut expressed as the percentage difference between the Market Value of the collateral and the Purchase Price of the repo and calculated as 100 multiplied by a ratio of the difference between the Market Value of the collateral and the Purchase Price of the repo to the Market Value of the collateral. Haircut is alternative way to adjust the value of collateral sold in a repurchase agreement to initial margin ratio. Because an initial margin is a percentage of the Purchase Price, while a haircut is a percentage of the Market Value of collateral, the arithmetic of initial margins and haircuts is slightly different. For example, an initial margin of 102% is not equivalent to a haircut of 2%, but to 1.961% (ie 100/102%). See GMRA 2011 paragraph 2(aa).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="2" minOccurs="0" name="haircutThreshold" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
An element defining a haircut percentage threshold which is the value above (when it's lower than initial haircut) or below (when it's higher than initial haircut) which parties agree they will not call a margin from each other.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
<!--2015-04-13:FpMLSecWG: agreed to add "assetReference" to link the MarginRatioOrHaircut.model with the asset it referes to-->
<xsd:element minOccurs="0" name="assetReference" type="AssetReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A reference to the collateral asset to which the margin requirement applies. This element should be produced in the case where margin requirements are specified for multiple pieces of collateral, and may be omitted otherwise.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!--2015-03-16:FpML Sec+RPT WGs: within PartyNoticePeriod made partyReference and PartyNoticePeriod required as in the confirmation view-->
<!--Sec WG: agreed to rename NoticePeriodPartyReference to PartyNoticePeriod to make sense and to be consistent with FpML naming standards – element name with partyNoticePeriod – associated type name “PartyNoticePeriod” -->
<xsd:complexType name="PartyNoticePeriod">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type to represent agreed period of notice to be given in advance before exercise of the open repo trade by a party requesting such exercise and reference to that party.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="partyReference" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A reference to a party who has the right to request exercise of the open repo trade and for whom noticePeriod is defined.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="noticePeriod" type="AdjustableOffset">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Notice period for open repo transactions in number of days. This element represents agreed period of notice to be given in advance before exercise of the repo trade by a party requesting such exercise.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="RelativePrice">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type which represents Pricing relative to a Benchmark.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="spread" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">Basis Point spread over a Benchmark.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group maxOccurs="unbounded" ref="BondEquity.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The benchmark being referred to; either a bond or equity product.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
</xsd:sequence>
</xsd:complexType>
<!--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: Added Relaxed content of Money type to be used within FarRepoTransactionLeg-->
<!--<xsd:complexType name="RelaxedMoney">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type defining a currency amount.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="MoneyBase">
<xsd:annotation>
<xsd:appinfo>
<view:override view="transparency" minOccurs="1"/>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="amount" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">The monetary quantity in currency units.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>-->
<xsd:complexType name="Repo">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A Repo, modeled as an FpML:Product. Note: this Repo model is a candidate model for further industry input.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="Product">
<xsd:sequence>
<xsd:choice>
<xsd:element name="fixedRateSchedule" type="Schedule">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The fixed repo rate. It is usually fixed for the duration of the agreement but can be changed with mid-life events (rate changes) except for sell/buy-back trades.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The floating rate index and tenor, with additional definitions relating to the calculation of floating rate amounts, including spread and multiplier. It is used for floating rate repos. For example, floating rate repos on European markets are made against EONIA.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element name="dayCountFraction" type="DayCountFraction">
<xsd:annotation>
<xsd:documentation xml:lang="en">The day count fraction.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element name="duration" type="RepoDurationEnum">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A duration code for the repo transaction. This defines a type of a repo transaction with fixed duration.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--SecWG agreed on Jan-26 to this model-->
<xsd:sequence>
<xsd:element name="callingParty" type="CallingPartyEnum">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A party to the open repo transaction that has a right to demand for exercise of far leg of the open repo transaction. This element represents an enumerated list that includes InitialBuyer, InitialSeller, Either, AsDefinedInMasterAgreement. In the default case either party can call for closing open repo transaction, unless otherwise specified. If electing parties are not defined in open repo confirmation, when they are defined by default in the Master Agreement, AsDefinedInMasterAgreement value should be used. Exact buyer/seller related parties, including any third parties who can demand exercise of open repo transactions on behalf of the parties to the trade (calculation agent, executing broker, etc.), can be defined in the relatedParty element (tradeHeader/partyTradeInformation).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="callDate" type="AdjustableOrRelativeDate">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines the latest date when the open repo transaction can be exercised (and no later than which it must be exercised) on demand by a party to the trade indicated in the electingParty element (or in the Master Agreement, if the electingParty element has AsDefinedInMasterAgreement value). For instance, in the open repo transaction with callDate agreed as business day one year after the trade date far leg can be settled on any day after the near leg settlement date and before and including the callDate. If the call date is not defined in trade terms and / or not included into trade confirmation this element can be omitted.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--Nov-07-2014: RTS Proposal: to make noticePeriod - optional and move it after electingParty-->
<xsd:choice minOccurs="0">
<xsd:element name="noticePeriod" type="AdjustableOffset">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Notice period for open repo transactions in number of days. This element represents agreed period of notice to be given in advance before exercise of the repo trade by a party requesting such exercise.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--Sec WG: agreed to rename NoticePeriodPartyReference to PartyNoticePeriod to make sense and to be consistent with FpML naming standards – element name with partyNoticePeriod – associated type name “PartyNoticePeriod” -->
<xsd:element maxOccurs="2" name="partyNoticePeriod" type="PartyNoticePeriod">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Notice period for open repo transactions referenced to a party to the trade, in number of days. This element represents agreed period of notice to be given in advance before exercise of the repo trade by a party requesting such exercise and reference to that party.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:choice>
<!--2015-04-13:FpML SecWG agreed to make "initialMargin" optional to support the "triParty" cases when the initialMargin is not provided-->
<!--2015-03-16:FpML Sec+RPT WGs: make initialMargin required, currently is not required for CBR reporting-->
<!--Nov-10-2014: SecWG agreed to renaming element "margin" and type "Margin" to element "initialMargin" and type "InitialMargin"-->
<xsd:element minOccurs="0" name="initialMargin" type="InitialMargin">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Defines initial margin applied to a repo transaction.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--2015-04-07: Sec WG: agreed to rename the type to RepoNearLeg from RepoTransactionNearLeg-->
<!--SecWG agreed to rename spotLeg to nearLeg on May-19-->
<xsd:element name="nearLeg" type="RepoNearLeg">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A repo contract is modeled as two purchase/repurchase transactions which are called legs. This is the near leg, i.e. the transaction that will be executed on the near settlement date of the contract.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--2015-04-07: Sec WG: agreed to rename the type to RepoFarLeg from RepoTransactionFarLeg-->
<!--SecWG agreed to rename forwardLeg to farLeg on May-19-->
<xsd:element minOccurs="0" name="farLeg" type="RepoFarLeg">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The far leg of the repo contract, i.e. the repurchase transaction. The BuyerSeller model in the far leg must be the exact opposite of the one found in the near leg.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--2015-04-13:FpML SecWG agreed to add "triParty" ofType "TriParty" as a choice to "BondEquity.model", a collateral asset model -->
<xsd:choice>
<!--2015-03-16:FpML Sec WG: Agreed to move repoDeliveryMethod from Repo level to the leg level-->
<xsd:group maxOccurs="unbounded" ref="BondEquity.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A list of the financial instruments that the repo contract may reference.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:element name="triParty" type="TriParty"/>
<!--SecWG agreed to move "settlementTransfer" block to RepoTransactionLeg-->
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--2015-04-07: Sec WG: agreed to rename the type to RepoFarLeg from RepoTransactionFarLeg-->
<!--2015-02-25: Sec WG: Renamed to RepoTransactionFarLeg from FarRepoTransactionLeg-->
<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: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 minOccurs="0" name="fxRate" type="FxRate">
<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 minOccurs="0" name="deliveryDate" type="AdjustableOrRelativeDate">
<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 maxOccurs="unbounded" name="collateral" type="CollateralValuation">
<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 &#8220;TriPartyRepo&#8221; 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 minOccurs="0" name="repoInterest" type="xsd:decimal">
<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>
<!--2015-04-14:FpML SecWG moved deliveryMethod, deliveryDate to each repo leg grouping with collateral-->
<!--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.-->
<xsd:complexType name="RepoLegBase">
<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-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="Leg">
<xsd:sequence>
<!--2015-02-23: Sec WG: agreed to remove element "id" of type “RepoLegId" until we have requirement for identifying the leg -->
<!--<xsd:element name="id" type="RepoLegId" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">A reference to a party transaction ID. This is provided in case the message creator wishes to record that the repo leg is associated with a particular trade identifier; typically this can be used for identifying a UTI associated with the leg.</xsd:documentation>
</xsd:annotation>
</xsd:element>-->
<xsd:group ref="BuyerSeller.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
References to the buyer and the seller of this leg of the repo contract.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<!--<xsd:annotation>
<xsd:documentation xml:lang="en">A group which has cash settlement elements.</xsd:documentation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>-->
<xsd:element name="settlementDate" type="AdjustableOrRelativeDate">
<xsd:annotation>
<xsd:documentation xml:lang="en">Settlement or Payment Date for the transaction.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!--2015-04-07: Sec WG: agreed to rename the type to RepoNearLeg from RepoTransactionNearLeg-->
<!--2015-02-25: Sec WG: Renamed to RepoTransactionNearLeg from NearRepoTransactionLeg-->
<!--2015-02-23: Sec WG: agreed to remove element "id" of type “RepoLegId" until we have requirement for identifying the leg -->
<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 minOccurs="0" name="fxRate" type="FxRate">
<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 minOccurs="0" name="deliveryDate" type="AdjustableOrRelativeDate">
<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 maxOccurs="unbounded" name="collateral" type="CollateralValuation">
<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 &#8220;TriPartyRepo&#8221; 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>
<!--2015-03-23: Removed RepoDeliveryMethod place holder -->
<!--2015-03-16:FpML Sec WG: Agreed to move repoDeliveryMethod from Repo level to the leg level; removed "repoLeg" and type "RepoLegEnum" -->
<!--<xsd:complexType name="RepoDeliveryMethod">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type to specify the delivery method for repo transaction. Includes the list of delivery methods for repo near or far leg transactions. Delivery method is defined on per leg basis.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="deliveryMethod" type="DeliveryMethod">
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies the delivery method in securities transactions. Includes the list of possible delivery methods for securities.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>-->
<!--2015-04-13:FpML SecWG added support for TriParty-->
<xsd:complexType name="TriParty">
<xsd:annotation>
<xsd:documentation xml:lang="en">The tri-party terms.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="triPartyAgent" type="PartyReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">The reference to the tri-party agent.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="collateralProfile" type="CollateralProfile">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The collateral profile specified at the tri-party agent.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="collateralType" type="CollateralType">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The collateral type, which is a restriction of the collateral deemed acceptable for the purpose of the transaction.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="repo" substitutionGroup="product" type="Repo">
<xsd:annotation>
<xsd:documentation xml:lang="en">Global element representing a Repo.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group name="BondCollateral.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">A group which has Collateral elements.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="nominalAmount" type="Money">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Total nominal amount of the given bonds used as collateral.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group minOccurs="0" ref="BondPriceAndYield.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A model describing price of the given bonds used as collateral.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:element minOccurs="0" name="accrualsAmount" type="Money">
<xsd:annotation>
<xsd:documentation xml:lang="en">Accruals expressed as amount.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="BondEquity.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A model group that allows us to specify that a repo contract can reference bond or equity instruments.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Most repos are done using Bonds and Bond subclasses as collateral. However in some jurisdictions repos on equities are widely used. It is technically possible to execute a repo on an equity, as long as the mark to market is correctly done during the lifetime of the repo.
</xsd:documentation>
</xsd:annotation>
<xsd:group ref="BondChoice.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A bond, or bond subtype referenced by a repo contract.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:element ref="equity">
<xsd:annotation>
<xsd:documentation xml:lang="en">An equity referenced by a repo contract.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<!--2015-03-16:FpML Sec+RPT WGs: within BondPriceAndYield.model, made choice of required cleanPrice and required dirtyPrice appear as in the confirmation view-->
<xsd:group name="BondPriceAndYield.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A group which has either Bond Price or Yield elements.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<!--12-08-2014: SecWG agreed to Harry proposal to allow to specify dirtyPrice by adding a choice to the exisitng sequence.-->
<xsd:annotation>
<xsd:documentation xml:lang="en">
These elements express a price in terms of percentage of nominal amount.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:annotation>
<xsd:documentation xml:lang="en">One of cleanPrice or dirtyPrice must exist.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="cleanPrice" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Bond clean price, expressed in percentage points, 100 is the initial value of the bond.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="accruals" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Accruals, relationship is clean price and accruals equals dirty price, all prices are expressed in percentage points, 100 is the initial value of the bond.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="dirtyPrice" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Bond dirty price, expressed in percentage points, 100 is the initial value of the bond.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:element name="dirtyPrice" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Bond dirty price, expressed in percentage points, 100 is the initial value of the bond.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:element minOccurs="0" name="relativePrice" type="RelativePrice">
<xsd:annotation>
<xsd:documentation xml:lang="en">Bond price relative to a Benchmark.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="yieldToMaturity" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">Yield to Maturity.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="inflationFactor" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The inflation factor is specified for inflation-linked products which require some additional elements to calculate prices correctly.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--2015-03-16:FpML Sec WG: within BondPriceAndYield.model, allInPrice of type xsd:decimal as an optional element.-->
<xsd:element minOccurs="0" name="allInPrice" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Bond all-in-price which is a price that includes all relevant price adjustments (i.e. accrued interest, haircut or margin ratio, inflation factor,etc.). It expresses a price in terms of percentage of nominal amount.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- <xsd:group name="MarginRatioOrHaircut.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">A group which has a choice between initial margin ratio and haircut.</xsd:documentation>
</xsd:annotation>
<!-\-09-29-2014: SecWG: agreed to a choice of initialMarginRatio (renamed from marginFactor) and haircut-\->
<xsd:choice>
<xsd:annotation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
<!-\-11-10-2014: SecWG: agreed to grouping of "initialMarginRatio" and "marginRatioThreshold" -\->
<xsd:sequence>
<xsd:annotation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
<!-\-11-24-2014: SecWG: reverted back the renaming "initialMarginRatio” from marginRatio. The currently agreed name of the element - marginRatio-\->
<xsd:element name="marginRatio" type="xsd:decimal">
<xsd:annotation>
<!-\-<xsd:documentation xml:lang="en">The margin is expressed as a multiplication factor (default value is 1) to reflect the quality of the collateral. Also called margin ratio as per Section 2, paragraph (z) of the TBMA/ISMA Global Master Repurchase Agreement.</xsd:documentation>-\->
<xsd:documentation xml:lang="en">An element defining an initial margin expressed as a ratio of the Market Value of the collateral to the Purchase Price. A default value of initial margin ratio of 1.00 means there is no margin and thus no risk related with the collateral. See GMRA 2000 paragraph 2(z) and GMRA 2011 paragraph 2(bb).</xsd:documentation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="marginRatioThreshold" type="xsd:decimal" minOccurs="0" maxOccurs="2">
<xsd:annotation>
<xsd:documentation xml:lang="en">An element defining a margin ratio threshold which is the value above (when it's lower than initial margin ratio) or below (when it's higher than initial margin ratio) which parties agree they will not call a margin from each other.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<!-\-11-10-2014: SecWG: agreed to grouping of "haircutPercentage" and "haircutThreshold" -\->
<xsd:sequence>
<xsd:annotation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="haircut" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation xml:lang="en">An element defining a haircut expressed as the percentage difference between the Market Value of the collateral and the Purchase Price of the repo and calculated as 100 multiplied by a ratio of the difference between the Market Value of the collateral and the Purchase Price of the repo to the Market Value of the collateral. Haircut is alternative way to adjust the value of collateral sold in a repurchase agreement to initial margin ratio. Because an initial margin is a percentage of the Purchase Price, while a haircut is a percentage of the Market Value of collateral, the arithmetic of initial margins and haircuts is slightly different. For example, an initial margin of 102% is not equivalent to a haircut of 2%, but to 1.961% (ie 100/102%). See GMRA 2011 paragraph 2(aa).</xsd:documentation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="haircutThreshold" type="xsd:decimal" minOccurs="0" maxOccurs="2">
<xsd:annotation>
<xsd:documentation xml:lang="en">An element defining a haircut percentage threshold which is the value above (when it's lower than initial haircut) or below (when it's higher than initial haircut) which parties agree they will not call a margin from each other.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:group>-->
<!--2015-03-23:FpML SecWG: the content of the Settlement.model was placed directly into Near and Far Repo Transaction leg-->
<!-- <xsd:group name="Settlement.model">
<xsd:annotation>
<xsd:documentation xml:lang="en">A group which has cash settlement elements.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="settlementDate" type="AdjustableOrRelativeDate">
<xsd:annotation>
<xsd:documentation xml:lang="en">Settlement or Payment Date for the transaction.</xsd:documentation>
<xsd:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<!-\-2015-03-23:FpML SecWG: agreed to move here from being after the settlement method group-\->
<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>
<!-\-2015-03-16:FpML Sec+RPT WDs: within Settlement.model, made deliveryDate optional as in the confirmation view. This element is required by CBR, but if omitted, the settlement date would be assumed also a delivery date.-\->
<!-\-01-26-2015: Sec WG: agreed to add-\->
<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: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:appinfo>
<view:override view="recordkeeping" minOccurs="1"/>
</xsd:appinfo>
</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>
</xsd:sequence>
</xsd:group>-->
</xsd:schema>
XML schema documentation generated with DocFlex/XML 1.10b5 using DocFlex/XML XSDDoc 2.8.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.