complexType "RegulatoryDisclosure"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
|
Used: |
|
XML Representation Summary |
<... |
|
|
= |
xsd:token |
|
= |
xsd:positiveInteger |
|
= |
"9" |
|
|
> |
|
Content: |
header?, isCorrection?, onBehalfOf[0..4], asOfDate?, asOfTime?, eventId?, eventType, eventTimestamps, reportingPartyReference, counterPartyReference, ( notionalChange?, ( changeInNotional* | changeInNumberOfOptions* | changeInQuantity*)?)?, payment*, applicableRegulations?, regulationSpecificInformation?, cpmiIoscoCDE?, trade, quote*, collateralization[0..2], party+ |
|
</...> |
Content Model Elements (22):
-
All Direct / Indirect Based Elements (1):
-
Annotation
A type that defines a message to be used for reporting non-public information to a regulator, typically via a trade repository or other reporting service. CAVEAT: This new regulatory reporting message set is supported by the FpML Standards Committee, and will be present in future versions of the standard. However, there is no absolute guarantee of backward compatibility with future versions of the standard, until such time as the Standards Committee deems that the message set has been extensively adopted in production. The Standards Committee will attempt to maintain full backward compatibility with this version while adjusting as required to take into account implementation experience with the message set. The Standards Committee advises that the areas where there is more likely to be change include the applicableRegulatiorns section, the regulatorionSpecificInformation section, and the regulatoryProductInformation product, which is developed as part of this reporting framework. Feedback or questions can be addressed to ISDA at rptwgchair@fpml.org.
Type Derivation Tree
RegulatoryDisclosure
|
XML Source (w/o annotations (16); see within schema source)
<xsd:complexContent>
<xsd:extension base="AddressedMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="isCorrection" type="xsd:boolean"/>
<xsd:element minOccurs="0" name="asOfTime" type="xsd:time"/>
<xsd:element maxOccurs="unbounded" name="party" type="Party"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
|
Content Element Detail (all declarations; defined within this component only; 15/22)
-
All the regulators to which this trade should be reported. Optional, can be infeerred from the list of regulations to which the trade is submitted.
XML Source (w/o annotations (1); see within schema source)
-
The date for which this document reports positions and valuations.
Simple Content
XML Source (w/o annotations (1); see within schema source)
-
Type: |
xsd:time, predefined, simple content |
The time for which this report was generated (i.e., the cut-off time of the report).
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="asOfTime" type="xsd:time"/>
|
-
XML Source (w/o annotations (1); see within schema source)
-
The revised state of the trade or its final state for a lifecycle ending event
XML Source (w/o annotations (1); see within schema source)
-
A unique event identifier.
Simple Content
maxLength: |
255
|
minLength: |
1
|
XML Source (w/o annotations (1); see within schema source)
-
Various timestamps related to the event.
XML Source (w/o annotations (1); see within schema source)
-
A structured code indicating the event type.
Simple Content
maxLength: |
255
|
minLength: |
1
|
XML Source (w/o annotations (1); see within schema source)
-
Type: |
xsd:boolean, predefined, simple content |
Indicates if this message corrects an earlier submission. If true, the recipient is directed to record information about the most recent lifecycle event affecting the trade as a correction of the previous submission, rather than as a new lifecycle event.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="isCorrection" type="xsd:boolean"/>
|
-
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.
XML Source (w/o annotations (1); see within schema source)
-
The supporting party definitions.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" name="party" type="Party"/>
|
-
Payments in settlement of the event
XML Source (w/o annotations (1); see within schema source)
-
Pricing information for the trade.
XML Source (w/o annotations (1); see within schema source)
-
All the regulations that this trade should be reported under.
XML Source (w/o annotations (1); see within schema source)
-
The revised state of the trade or its final state for a lifecycle ending event
XML Source (w/o annotations (1); see within schema source)