complexType "PublicDisclosure"
Namespace:
http://www.fpml.org/FpML-5/transparency
Content:
complex, 3 attributes, 15 elements
Defined:
globally in fpml-transparency-processes-5-13.xsd; see XML source
Includes:
definitions of 10 elements
Used:
at 1 location
Component Diagram
XML Representation Summary
<...
   
fpmlVersion
 = 
xsd:token
expectedBuild
 = 
xsd:positiveInteger
actualBuild
 = 
"4"
   
>
   
Content: 
header?, isCorrection?, onBehalfOf[0..4], eventId?, eventType, eventTimestamp, (notionalChange?, (changeInNotional* | changeInNumberOfOptions* | changeInQuantity*)?)?, applicableRegulations, regulationSpecificInformation?, trade, quote*, party*
</...>
Content Model Elements (15):
applicableRegulations,
changeInNotional,
changeInNumberOfOptions (defined in ReportingNotionalChange.model group),
changeInQuantity,
eventId (in publicDisclosure),
eventTimestamp,
eventType,
header (defined in AddressedMessage complexType),
isCorrection (in publicDisclosure),
notionalChange,
onBehalfOf (in publicDisclosure),
party (in publicDisclosure),
quote (in publicDisclosure),
regulationSpecificInformation,
trade (in publicDisclosure)
All Direct / Indirect Based Elements (1):
publicDisclosure
Known Usage Locations
Type Definition Detail
Type Derivation Tree
Document (extension)
  Message (extension)
      AddressedMessage (extension)
          PublicDisclosure
XML Source (w/o annotations (11); see within schema source)
<xsd:complexType name="PublicDisclosure">
<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="eventId" type="EventId"/>
<xsd:element name="eventType" type="EventTaxonomy"/>
<xsd:element name="eventTimestamp" type="xsd:dateTime"/>
<xsd:group minOccurs="0" ref="ReportingNotionalChange.model"/>
<xsd:element name="applicableRegulations" type="ApplicableRegulations"/>
<xsd:element minOccurs="0" name="regulationSpecificInformation" type="PublicRegulationDetails"/>
<xsd:element name="trade" type="Trade"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="quote" type="BasicQuotation"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="party" type="Party"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Content Element Detail (all declarations; defined within this component only; 10/15)
applicableRegulations
Type:
ApplicableRegulations, complex content
All the regulator that applies to this trade.
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="applicableRegulations" type="ApplicableRegulations"/>
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"/>
eventTimestamp
Type:
xsd:dateTime, predefined, simple content
When the reported event happened.
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="eventTimestamp" type="xsd:dateTime"/>
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" minOccurs="0" name="party" type="Party"/>
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:
PublicRegulationDetails, 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="PublicRegulationDetails"/>
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 FlexDoc/XML 1.12.2 using FlexDoc/XML XSDDoc 2.9.1 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit.