All Element Summary |
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
The date for which this document reports positions and valuations.
|
||||||||||
|
||||||||||
The time for which this report was generated (i.e., the cut-off time of the report).
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
Individual parties should only use a single event identifier to identify a retraction.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
The currency amount of the payment.
|
||||||||||
The payment date.
|
||||||||||
A classification of the type of fee or additional payment, e.g. brokerage, upfront fee etc.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
This may be used to identify one or more parties that perform a role within the transaction.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
This is provided to support snapshot reporting that requires trading history.
|
||||||||||
This is provided to support snapshot reporting that requires trading history.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
Complex Type Summary |
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
A type for defining payments.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
Simple Type Summary |
||||||
|
Element Group Summary |
||||||||||
|
<?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="" 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-business-events-5-9.xsd"/>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="asOfDate" type="IdentifiedDate">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The date for which this document reports positions and valuations.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The time for which this report was generated (i.e., the cut-off time of the report).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Allows a reference to porftfolio request to be included, such as a portfolio compression request. NOTE: this is an element that is under assessment and may not be available in a subsequent working draft.
</xsd:documentation>
</xsd:annotation>
</xsd:group>
<xsd:choice minOccurs="0">
<xsd:sequence>
<xsd:element minOccurs="0" name="originatingEvent" type="OriginatingEvent"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
This is provided to support snapshot reporting that requires trading history. Some implementations are using the "trade" event to report the current snapshot of a contract. In these cases it may also be necessary to report the most recent trading event to support regulatory reporting mandates. For this reason the tradingEvent is provided to allow that event to be attached to the trade report.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:choice minOccurs="0">
<xsd:sequence>
<xsd:element minOccurs="0" name="originatingEvent" type="OriginatingEvent"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
This is provided to support snapshot reporting that requires trading history. Some implementations are using the "trade" event to report the current snapshot of a contract. In these cases it may also be necessary to report the most recent trading event to support regulatory reporting mandates. For this reason the tradingEvent is provided to allow that event to be attached to the trade report.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
<xsd:sequence>
<xsd:element minOccurs="0" name="primaryAssetClass" type="AssetClass"/>
<xsd:annotation>
<xsd:documentation xml:lang="en">
Individual parties should only use a single event identifier to identify a retraction. Platforms providing services on behalf of both parties in a transaction may provide event identifiers for both parties; in this case it is up to the recipient (the trade repository) to validate that the event IDs refer to the same event.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
This may be used to identify one or more parties that perform a role within the transaction. If this is within a partyTradeInformation block, the related party performs the role with respect to the party identifie by the "partyReference" in the partyTradeInformation block.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation/>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="asOfDate" type="IdentifiedDate">
</xsd:element>
</xsd:element>
</xsd:group>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:annotation/>
<xsd:sequence>
<xsd:element minOccurs="0" name="tradeDate" type="IdentifiedDate"/>
<xsd:choice>
<xsd:element name="uniqueSwapIdentifier" type="PartyTradeIdentifier"/>
<xsd:sequence>
</xsd:sequence>
</xsd:choice>
<xsd:choice>
<xsd:sequence>
</xsd:sequence>
<xsd:sequence>
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="name" type="ReportingRegimeName"/>
<xsd:choice minOccurs="0">
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="executionDateTime" type="ExecutionDateTime"/>
<xsd:choice minOccurs="0">
<xsd:sequence>
</xsd:sequence>
<xsd:sequence>
</xsd:sequence>
</xsd:choice>
<xsd:choice minOccurs="0">
</xsd:choice>
<!-- should be enumeration, Principall/Agent -->
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="intentToClear" type="xsd:boolean"/>
<xsd:choice minOccurs="0">
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="intentToAllocate" type="xsd:boolean"/>
<xsd:choice minOccurs="0">
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="collateralizationType" type="CollateralizationType"/>
<!-- change to ID? -->
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="masterAgreementId" type="MasterAgreementId"/>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:sequence>
</xsd:sequence>
<xsd:sequence>
<xsd:group ref="RegulatorReportGenericProductInformation.model"/>
<xsd:choice minOccurs="0">
</xsd:choice>
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A type for defining payments. In Transparency view, normally the payer and receiver party references are not used; however they may be provided if necessary for administrative activities such as Reporting Party Determination in FX.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="PaymentBase">
<xsd:sequence>
<xsd:group minOccurs="0" ref="PayerReceiver.model">
<xsd:annotation/>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
The payment date. This date is subject to adjustment in accordance with any applicable business day convention.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation xml:lang="en">
A classification of the type of fee or additional payment, e.g. brokerage, upfront fee etc. FpML does not define domain values for this element.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="reportingPartyPaysType" type="xsd:token"/>
<!-- needs type -->
<!-- needs type -->
</xsd:sequence>
</xsd:complexType>
<xsd:restriction base="xsd:token">
<xsd:pattern value="[1-2]?[0-9][DWMY]"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:complexType>
<xsd:sequence>
<xsd:group ref="Product.model"/>
<!-- should be token - buyer, seller, payer, receiver -->
<!-- should be token - buyer, seller, payer, receiver -->
</xsd:sequence>
</xsd:group>
<xsd:complexContent>
</xsd:complexContent>
</xsd:complexType>
<xsd:sequence>
<xsd:choice minOccurs="0">
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<!--
<xsd:element name="regulatorReportRetracted" type="RegulatorReportRetracted" /> --> </xsd:schema>
|
XML schema documentation generated with DocFlex/XML 1.9.0 using DocFlex/XML XSDDoc 2.8.0 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.
|