complexType "RegulatoryDisclosure"
Namespace:
Content:
complex, 3 attributes, 22 elements
Defined:
Includes:
definitions of 15 elements
Used:
Content Model Diagram
XML Representation Summary
<...
   
 = 
xsd:token
 = 
xsd:positiveInteger
 = 
"9"
   
>
   
Content: 
</...>
Content Model Elements (22):
applicableRegulations,
asOfDate (in regulatoryDisclosure),
asOfTime (in regulatoryDisclosure),
changeInNotional,
changeInNumberOfOptions (defined in ReportingNotionalChange.model group),
changeInQuantity,
collateralization (in regulatoryDisclosure),
counterPartyReference,
cpmiIoscoCDE,
eventId (in regulatoryDisclosure),
eventTimestamps,
eventType (in regulatoryDisclosure),
header (defined in AddressedMessage complexType),
isCorrection (in regulatoryDisclosure),
notionalChange,
onBehalfOf (in regulatoryDisclosure),
party (in regulatoryDisclosure),
payment (in regulatoryDisclosure),
quote (in regulatoryDisclosure),
regulationSpecificInformation,
reportingPartyReference,
trade (in regulatoryDisclosure)
All Direct / Indirect Based Elements (1):
regulatoryDisclosure
Known Usage Locations
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 Definition Detail
Type Derivation Tree
Document (extension)
  Message (extension)
      AddressedMessage (extension)
          RegulatoryDisclosure
XML Source (w/o annotations (16); see within schema source)
<xsd:complexType name="RegulatoryDisclosure">
<xsd:complexContent>
<xsd:extension base="AddressedMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="isCorrection" type="xsd:boolean"/>
<xsd:element maxOccurs="4" minOccurs="0" name="onBehalfOf" type="OnBehalfOf"/>
<xsd:element minOccurs="0" name="asOfDate" type="IdentifiedDate"/>
<xsd:element minOccurs="0" name="asOfTime" type="xsd:time"/>
<xsd:element minOccurs="0" name="eventId" type="EventId"/>
<xsd:element name="eventType" type="EventTaxonomy"/>
<xsd:element name="eventTimestamps" type="EventTimestamps"/>
<xsd:group minOccurs="0" ref="ReportingNotionalChange.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="payment" type="NonNegativePayment"/>
<xsd:element minOccurs="0" name="applicableRegulations" type="ApplicableRegulations"/>
<xsd:element minOccurs="0" name="regulationSpecificInformation" type="RegulationDetails"/>
<xsd:element minOccurs="0" name="cpmiIoscoCDE" type="RegReporting.CDE"/>
<xsd:element name="trade" type="Trade"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="quote" type="BasicQuotation"/>
<xsd:element maxOccurs="2" minOccurs="0" name="collateralization" type="RegulatoryReportingCollateralization"/>
<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)
applicableRegulations
Type:
ApplicableRegulations, complex content
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)
<xsd:element minOccurs="0" name="applicableRegulations" type="ApplicableRegulations"/>

asOfDate
Type:
IdentifiedDate, simple content
The date for which this document reports positions and valuations.
Simple Content
xsd:date
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="asOfDate" type="IdentifiedDate"/>

asOfTime
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"/>

collateralization
Type:
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="2" minOccurs="0" name="collateralization" type="RegulatoryReportingCollateralization"/>

cpmiIoscoCDE
Type:
RegReporting.CDE, complex content
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)
<xsd:element minOccurs="0" name="cpmiIoscoCDE" type="RegReporting.CDE"/>

eventId
Type:
EventId, simple content
A unique event identifier.
Simple Content
xsd:normalizedString
maxLength:
255
minLength:
1
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="eventId" type="EventId"/>

eventTimestamps
Type:
EventTimestamps, complex content
Various timestamps related to the event.
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="eventTimestamps" type="EventTimestamps"/>

eventType
Type:
EventTaxonomy, simple content
A structured code indicating the event type.
Simple Content
xsd:normalizedString
maxLength:
255
minLength:
1
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="eventType" type="EventTaxonomy"/>

isCorrection
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"/>

onBehalfOf
Type:
OnBehalfOf, complex content
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)
<xsd:element maxOccurs="4" minOccurs="0" name="onBehalfOf" type="OnBehalfOf"/>

party
Type:
Party, complex content
The supporting party definitions.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" name="party" type="Party"/>

payment
Type:
NonNegativePayment, complex content
Payments in settlement of the event
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="payment" type="NonNegativePayment"/>

quote
Type:
BasicQuotation, complex content
Pricing information for the trade.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="quote" type="BasicQuotation"/>

regulationSpecificInformation
Type:
RegulationDetails, complex content
All the regulations that this trade should be reported under.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="regulationSpecificInformation" type="RegulationDetails"/>

trade
Type:
Trade, complex content
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)
<xsd:element name="trade" type="Trade"/>

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.