XML Schema "fpml-recordkeeping-processes-5-8.xsd"
Target Namespace:
http://www.fpml.org/FpML-5/recordkeeping
Version:
$Revision: 7629 $
Defined Components:
elements (4 global + 14 local), complexTypes (2)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
D:\Tradeheader\last-trunk\xml\recordkeeping\fpml-recordkeeping-processes-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
asOfDate (in nonpublicExecutionReport)
The date for which this document reports positions and valuations.
Type:
Content:
simple, 1 attribute
Defined:
asOfTime (in nonpublicExecutionReport)
The time for which this report was generated (i.e., the cut-off time of the report).
Type:
xsd:time
Content:
simple
Defined:
eventIdentifier (in nonpublicExecutionReportRetracted)
Individual parties should only use a single event identifier to identify a retraction.
Type:
Content:
complex, 1 attribute, 3 elements
Defined:
nonpublicExecutionReport
Type:
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Used:
never
nonpublicExecutionReportAcknowledgement
Type:
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
nonpublicExecutionReportException
Type:
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
nonpublicExecutionReportRetracted
Type:
Content:
complex, 3 attributes, 24 elements
Defined:
globally; see XML source
Used:
never
originatingEvent (in nonpublicExecutionReport)
Type:
Content:
simple, 1 attribute
Defined:
originatingEvent (in nonpublicExecutionReportRetracted)
Type:
Content:
simple, 1 attribute
Defined:
primaryAssetClass (in nonpublicExecutionReportRetracted)
Type:
Content:
simple, 1 attribute
Defined:
relatedParty (in nonpublicExecutionReportRetracted)
This may be used to identify one or more parties that perform a role within the transaction.
Type:
Content:
complex, 4 elements
Defined:
trade (in nonpublicExecutionReport)
Type:
Content:
complex, 1 attribute, 13 elements
Defined:
trade (in nonpublicExecutionReportRetracted)
Type:
Content:
complex, 1 attribute, 13 elements
Defined:
tradeIdentifier (in nonpublicExecutionReportRetracted)
Type:
Content:
complex, 1 attribute, 11 elements
Defined:
tradingEvent (in nonpublicExecutionReport)
This is provided to support snapshot reporting that requires trading history.
Type:
Content:
complex, 6 elements
Defined:
tradingEvent (in nonpublicExecutionReportRetracted)
This is provided to support snapshot reporting that requires trading history.
Type:
Content:
complex, 6 elements
Defined:
withdrawal (in nonpublicExecutionReport)
Type:
Content:
complex, 6 elements
Defined:
withdrawal (in nonpublicExecutionReportRetracted)
Type:
Content:
complex, 6 elements
Defined:
Complex Type Summary
Content:
complex, 3 attributes, 25 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
Content:
complex, 3 attributes, 24 elements
Defined:
globally; see XML source
Includes:
definitions of 8 elements
Used:
XML Source
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2002-2015 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-8.xsd"/>
<xsd:complexType name="NonpublicExecutionReport">
<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:element minOccurs="0" name="asOfTime" type="xsd:time">
<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:group minOccurs="0" ref="PortfolioReferenceBase.model">
<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:element name="trade" type="Trade"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="tradingEvent" type="TradingEventSummary">
<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:group ref="PostTradeEvents.model"/>
<xsd:group ref="ChangeEvents.model"/>
<xsd:group ref="OptionsEvents.model"/>
<xsd:element name="withdrawal" type="Withdrawal"/>
</xsd:choice>
<xsd:group minOccurs="0" ref="EventValuation.model"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="NonpublicExecutionReportRetracted">
<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:element name="trade" type="Trade"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="tradingEvent" type="TradingEventSummary">
<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:group ref="PostTradeEvents.model"/>
<xsd:group ref="ChangeEvents.model"/>
<xsd:group ref="OptionsEvents.model"/>
<xsd:element name="withdrawal" type="Withdrawal"/>
</xsd:choice>
<xsd:sequence>
<xsd:element minOccurs="0" name="primaryAssetClass" type="AssetClass"/>
<xsd:element minOccurs="0" name="tradeIdentifier" type="PartyTradeIdentifier"/>
<xsd:element maxOccurs="2" minOccurs="0" name="eventIdentifier" type="BusinessEventIdentifier">
<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:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty">
<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:group minOccurs="0" ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="nonpublicExecutionReportException" type="Exception"/>
</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.