group "ClearingResults.model"
Namespace:
http://www.fpml.org/FpML-5/confirmation
Content:
8 elements
Defined:
globally in fpml-confirmation-processes-5-11.xsd; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
Content Model Diagram
Complex Content Model
tradePackage | (originatingEvent?, trade) | additionalEvent | (terminatingEvent?, termination) | deClear | clearing
Content Model Elements (8):
trade (defined in TradingEventsBase.model group),
Known Usage Locations
Annotation
Events/Results that are applicable to clearing processes.
XML Source (w/o annotations (3); see within schema source)
<xsd:group name="ClearingResults.model">
<xsd:choice>
<xsd:group ref="TradingEvents.model"/>
<xsd:sequence>
<xsd:element minOccurs="0" name="terminatingEvent" type="TerminatingEvent"/>
<xsd:element name="termination" type="TradeNotionalChange"/>
</xsd:sequence>
<xsd:element name="deClear" type="DeClear"/>
<xsd:element name="clearing" type="Clearing"/>
</xsd:choice>
</xsd:group>
Content Element Detail (all declarations; defined within this component only; 4/8)
clearing
Type:
Clearing, complex content
XML Source (see within schema source)
<xsd:element name="clearing" type="Clearing"/>
deClear
Type:
DeClear, complex content
A structure describing a declear event. The deClear event allows a firm to request that a trade be removed from clearing, or a clearing service to request consent for this, or to report that it has been done.
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="deClear" type="DeClear"/>
terminatingEvent
Type:
TerminatingEvent, simple content
This may be used to describe why a trade was terminated.
Simple Content
xsd:normalizedString
maxLength:
255
minLength:
0
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="terminatingEvent" type="TerminatingEvent"/>
termination
Type:
TradeNotionalChange, complex content
XML Source (see within schema source)
<xsd:element name="termination" type="TradeNotionalChange"/>
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.