All Element Summary |
||||||||||
|
A reference to the reporting party.
|
||||||||||
|
Specifies the disseminationId used for public reporting.
|
||||||||||
|
Standard FpML message header
|
||||||||||
|
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.
|
||||||||||
|
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.
|
|||||||||
|
||||||||||
|
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 data type used for dissemination identifiers.
|
||||||||||
|
Information related to the public dissemination.
|
||||||||||
|
An identifier of a regulation used for regulatory reporting, for example CFTC_PART43, CFTC_PART45, CSA_2013, 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 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) 2022-2024 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="trnsp" ecore:package="org.fpml.transparency" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/transparency" version="$Revision: 7629 $" xmlns="http://www.fpml.org/FpML-5/transparency" 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-13.xsd"/>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
</xsd:sequence>
Speccifies the list ofregulations the trade is subject to reporting.
</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: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: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 a regulation used for regulatory reporting, for example CFTC_PART43, CFTC_PART45, CSA_2013, etc.
</xsd:documentation>
<xsd:simpleContent>
</xsd:simpleContent>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Speccifies the trade is subject to this regulation.
</xsd:documentation>
<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: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: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:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Model group that references the reporting party and counterparty.
</xsd:documentation>
<xsd:element minOccurs="0" 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 FlexDoc/XML 1.12.2 using FlexDoc/XML XSDDoc 2.9.1 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit. |