All Element Summary |
||||||||||
beneficiaryPartyReference (defined in RegulatoryReportingCollateralization complexType) |
|
|||||||||
cash (in postedCollateral) |
Represents the amount of cash posted as collateral.
|
|||||||||
collateralizationType (defined in RegulatorReportCollateralInfo.model group) |
Specifies how the transaction is collateralized by this party, fully or partially, or uncollateralized.
|
|||||||||
Whether the trade collateralized exposure is calculated at the individual (single) trade aggregation level or the net (multiple trades) aggregation level.
|
||||||||||
A reference to the reporting party.
|
||||||||||
Specifies the disseminationId used for public reporting.
|
||||||||||
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.
|
||||||||||
Standard FpML message header
|
||||||||||
|
||||||||||
marginRatio (in nonCash) |
An element defining an initial margin expressed as a ratio of the Market Value of the collateral to the Purchase Price.
|
|||||||||
Represents the type and the amount of security (non-cash) posted as collateral.
|
||||||||||
Indicates which party (or parties) (and accounts) a trade or event is being processed for.
|
||||||||||
Reference information about parties, business units, and persons involed in the trade.
|
||||||||||
The supporting party definitions.
|
||||||||||
Provides code, or other identifier for the collateral portfolio to which this belongs.
|
||||||||||
Information about the amount of collateral actually posted by the posting party as of a particular value date.
|
||||||||||
A party that can post the collateral.
|
||||||||||
The asset class of the underlying product.
|
||||||||||
The date and time the public report is projected to be disseminated.
|
||||||||||
The date and time the public report was disseminated.
|
||||||||||
Describes the extent to which this trade is being reported to the regime (e.g.
|
||||||||||
reason (defined in ReportingStatus complexType) |
Used to describe and validation errors or warnings associated with the message for the regime.
|
|||||||||
Identifies the reporting regime under which this data is reported.
|
||||||||||
regulation (defined in ReportingStatus complexType) |
Identifies the reporting regime under which this data is reported.
|
|||||||||
|
||||||||||
|
||||||||||
Used to report the status of reporting on a trade to any regulators.
|
||||||||||
|
||||||||||
A reference to the reporting party.
|
||||||||||
reportingPurpose (defined in ReportingStatus complexType) |
The reason this message is being sent, for example Snapshot, PET, Confirmation, RealTimePublic.
|
|||||||||
reportingRole (defined in ReportingStatus complexType) |
>Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
|
|||||||||
Information about how the position is being reported to regulators.
|
||||||||||
Used to request the status of reporting on a trade to any regulators.
|
||||||||||
status (defined in ReportingStatus complexType) |
Describes the extent to which this trade is being reported to the regime (e.g.
|
|||||||||
supervisoryBody (defined in ReportingStatus complexType) |
Identifies the specific regulator or other supervisory body for which this data is produced.
|
|||||||||
|
||||||||||
Represents aggregated Market / Fair Value amount.
|
||||||||||
identifies the affected trade
|
||||||||||
identifies the affected trade
|
||||||||||
|
||||||||||
The date and time the public report was withdrawn from the public tape.
|
Complex Type Summary |
||||||||||
Speccifies the list ofregulations the trade is subject to reporting.
|
||||||||||
The CollateralPortfolio component provides the ability to specify the collateral in support of the transaction reporting as of a particular value date.
|
||||||||||
|
||||||||||
|
||||||||||
The data type used for dissemination identifiers.
|
||||||||||
Information related to the public dissemination.
|
||||||||||
An identifier of an reporting regime or format used for regulatory reporting, for example DoddFrankAct, MiFID, HongKongOTCDRepository, etc.
|
||||||||||
Speccifies the trade is subject to this regulation.
|
||||||||||
A type that can be used to identify the reporting status of a transaction.
|
||||||||||
A type defining collateral information to be reported.
|
||||||||||
A type defining message that can be used for returning the regulatory reporting status of a trade.
|
||||||||||
|
||||||||||
|
Element Group Summary |
||||||||||
|
||||||||||
Model group that references the reporting party and counterparty.
|
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2018-2020 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="" ecore:package="org.fpml.recordkeeping" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/recordkeeping" version="$Revision: 7629 $" xmlns="http://www.fpml.org/FpML-5/recordkeeping" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" 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-msg-5-11.xsd"/>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Speccifies the list ofregulations the trade is subject to reporting.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<xsd:annotation>
</xsd:complexType>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The CollateralPortfolio component provides the ability to specify the collateral in support of the transaction reporting as of a particular value date. It includes unbounded choice of cash or nonCash collateral. This model would allow mixing cash and non-cash collateral without any regards to order. In real life transaction, you almost always see some cash or a collection of non-cash collateral blocs.
</xsd:documentation>
<xsd:sequence>
<xsd:element name="valueDate" type="xsd:date"/>
</xsd:sequence>
<xsd:choice maxOccurs="unbounded" minOccurs="0">
<xsd:element name="cash" type="PositiveMoney">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Represents the amount of cash posted as collateral. The cash collateral component is simple, just an instance of PositiveMoney type.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Represents the type and the amount of security (non-cash) posted as collateral. The nonCash collateral component uses SecurityValuation.model to state what security it is, how much and the current dirty price. It also includes optional ability to specify the margin or haircut that applies to this piece of collateral.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:complexContent>
</xsd:complexType>
<xsd:extension base="SecurityValuation">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:annotation>
</xsd:annotation>
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
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:documentation xml:lang="en">
</xsd:annotation>
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:complexType>
<xsd:documentation xml:lang="en">The data type used for dissemination identifiers.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="disseminationId" type="DisseminationId">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies the disseminationId used for public reporting.
</xsd:documentation>
<xsd:choice>
<xsd:element minOccurs="0" name="publicationTime" type="xsd:dateTime">
</xsd:choice>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The date and time the public report was disseminated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The date and time the public report is projected to be disseminated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The date and time the public report was withdrawn from the public tape.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
An identifier of an reporting regime or format used for regulatory reporting, for example DoddFrankAct, MiFID, HongKongOTCDRepository, etc.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-regime" name="reportingRegimeNameScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Speccifies the trade is subject to this regulation.
</xsd:documentation>
<xsd:sequence>
<xsd:element minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:group>
<xsd:documentation>
</xsd:annotation>
Use the reportingParty, counterParty references at the root of the message to identify the reporting party and counterparty. If the same message is going to multiple regulators and they will have different roles, the roles can be overridden at the regulator-level (if they differ from the roles specified at the root of the message)
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:sequence>
</xsd:sequence>
<xsd:element name="postingPartyReference" type="PartyReference">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A group that includes information about activities related to credit support and collateral related to a trade.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Information about the amount of collateral actually posted by the posting party as of a particular value date.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type that can be used to identify the reporting status of a transaction. Examples include FullyReported, ReportedWithWarnings, NotReported, etc.
</xsd:documentation>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/reporting-status" name="reportingStatusScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining message that can be used for returning the regulatory reporting status of a trade.
</xsd:documentation>
<xsd:complexContent>
<xsd:extension base="Message">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element minOccurs="0" name="header" type="ResponseMessageHeader">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Information about how the position is being reported to regulators.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reference information about parties, business units, and persons involed in the trade.
</xsd:documentation>
<xsd:annotation/>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="regimeName" type="ReportingRegimeName">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the reporting regime under which this data is reported. For example, Dodd-Frank, EMIR, MiFID, HongKongOTCDRepository, ODRF
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the specific regulator or other supervisory body for which this data is produced. For example, CFTC, SEC, UKFSA, ODRF, SFC, ESMA.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the reporting regime under which this data is reported. For example, Dodd-Frank, EMIR, MiFID, HongKongOTCDRepository, ODRF
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
>Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The reason this message is being sent, for example Snapshot, PET, Confirmation, RealTimePublic.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Describes the extent to which this trade is being reported to the regime (e.g. Not reported, reported with warnings, fully reported).
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="publicDissemination" type="PublicDissemination">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Describes the extent to which this trade is being reported to the regime (e.g. Not reported, reported with warnings, fully reported).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe and validation errors or warnings associated with the message for the regime.
</xsd:documentation>
<xsd:annotation/>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="AddressedMessage">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="4" minOccurs="0" name="onBehalfOf" type="OnBehalfOf">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates which party (or parties) (and accounts) a trade or event is being processed for. Normally there will only be a maximum of 2 parties, but in the case of a novation there could be a transferor, transferee, remaining party, and other remaining party. Also, in the context of a trade package there could be several parties for which limit check is requested, necessitating multiple onBehalfOf elements. Except for these cases, there should be no more than two onBehalfOf references in a message.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to report the status of reporting on a trade to any regulators.
</xsd:documentation>
<xsd:element name="requestRegulatoryReportingStatus" type="RequestRegulatoryReportingStatusMessage">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to request the status of reporting on a trade to any regulators.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:sequence>
<xsd:element minOccurs="0" name="collateralizedExposureGrouping" type="CollateralizedExposureGrouping">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Whether the trade collateralized exposure is calculated at the individual (single) trade aggregation level or the net (multiple trades) aggregation level.
</xsd:documentation>
SFTR description of the field: Collateralization of net exposure - Indicates whether the collateral has been provided for a net exposure, rather than for a single transaction ('true' or 'false').
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies how the transaction is collateralized by this party, fully or partially, or uncollateralized. For Transparency view, the options include Full, Partial, Uncollateralized, and One-Way. For Recordkeeping, the collateralization type refers to collateral that is posted by this firm, and One-Way option is not meaningful. In other words, if the collateralization type is Full, this trade is fully collateralized by this party.
</xsd:documentation>
SFTR description of the field: Uncollateralised SL flag - Indicates whether the securities lending transaction is uncollateralised ('true' or 'false'). Uncollateralised SL will be 'true', if collateralizationType = 'Uncollateralized'.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides code, or other identifier for the collateral portfolio to which this belongs. The collateral portfolio describes how trades are aggregated for collateral calculation purposes. All trades that are aggregated together for collateral calculation purposes will share the same collateral portfolio code. This code may come from different sources depending on the level of aggregation defined in the CSA (e.g. it may be the LEI of a counterparty or a desk identifier).
</xsd:documentation>
SFTR description of this field: Portfolio code - If the transaction is cleared and is included in a portfolio of transactions for which margins are exchanged, this portfolio should be identified by a unique code determined by the reporting counterparty. 52 alphanumeric character code including four special characters: .- _. Special characters are not allowed at the beginning and at the end of the code. No space allowed.
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Model group that references the reporting party and counterparty.
</xsd:documentation>
<xsd:sequence>
<xsd:element name="reportingPartyReference" type="PartyReference">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</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.
|