complexType "RequestRegulatoryReportingStatusMessage"
Namespace:
http://www.fpml.org/FpML-5/confirmation
Content:
complex, 3 attributes, 6 elements
Defined:
globally in fpml-reg-reporting-5-11.xsd; see XML source
Includes:
definitions of 5 elements
Used:
never
Content Model Diagram
XML Representation Summary
<...
   
fpmlVersion
 = 
xsd:token
expectedBuild
 = 
xsd:positiveInteger
actualBuild
 = 
"3"
   
>
   
Content: 
header, onBehalfOf[0..4], tradeIdentifier?, primaryAssetClass?, relatedParty*, party*
</...>
Content Model Elements (6):
header (defined in AddressedMessage complexType),
onBehalfOf (defined in RequestRegulatoryReportingStatusMessage complexType),
party (defined in RequestRegulatoryReportingStatusMessage complexType),
primaryAssetClass (defined in RequestRegulatoryReportingStatusMessage complexType),
relatedParty (defined in RequestRegulatoryReportingStatusMessage complexType),
tradeIdentifier (defined in RequestRegulatoryReportingStatusMessage complexType)
Type Definition Detail
Type Derivation Tree
Document (extension)
  Message (extension)
      AddressedMessage (extension)
          RequestRegulatoryReportingStatusMessage
XML Source (w/o annotations (5); see within schema source)
<xsd:complexType name="RequestRegulatoryReportingStatusMessage">
<xsd:complexContent>
<xsd:extension base="AddressedMessage">
<xsd:sequence>
<xsd:element maxOccurs="4" minOccurs="0" name="onBehalfOf" type="OnBehalfOf"/>
<xsd:element minOccurs="0" name="tradeIdentifier" type="PartyTradeIdentifier"/>
<xsd:element minOccurs="0" name="primaryAssetClass" type="AssetClass"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty"/>
<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; 5/6)
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"/>
primaryAssetClass
Type:
AssetClass, simple content
The asset class of the underlying product.
Simple Content
xsd:normalizedString
maxLength:
255
minLength:
0
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="primaryAssetClass" type="AssetClass"/>
relatedParty
Type:
RelatedParty, complex content
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty"/>
tradeIdentifier
Type:
PartyTradeIdentifier, complex content
identifies the affected trade
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="tradeIdentifier" type="PartyTradeIdentifier"/>
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.