complexType "NonpublicExecutionReportRetracted"

Namespace:	http://www.fpml.org/FpML-5/recordkeeping
Content:	complex, 3 attributes, 29 elements
Defined:	globally in fpml-recordkeeping-processes-5-11.xsd; see XML source
Includes:	definitions of 8 elements
Used:	at 1 location

Content Model Diagram

XML Representation Summary

<...

fpmlVersion	=	xsd:token
expectedBuild	=	xsd:positiveInteger
actualBuild	=	"9"

Content:

</...>

Content Model Elements (29):

eventIdentifier (in nonpublicExecutionReportRetracted),

header (defined in RequestMessage complexType),

increase,

novation,

observation (defined in PostTradeEventsBase.model group),

onBehalfOf (defined in OnBehalfOf.model group),

optionEvent,

optionExercise,

optionExpiry,

originatingEvent (in nonpublicExecutionReportRetracted),

parentCorrelationId,

party (defined in PartiesAndAccounts.model group),

primaryAssetClass (in nonpublicExecutionReportRetracted),

reset (defined in PostTradeEventsBase.model group),

sequenceNumber (defined in Sequence.model group),

terminatingEvent,

termination (defined in PostTradeEventsBase.model group),

trade (in nonpublicExecutionReportRetracted),

tradeIdentifier (in nonpublicExecutionReportRetracted),

tradingEvent (in nonpublicExecutionReportRetracted),

validation,

withdrawal

All Direct / Indirect Based Elements (1):

nonpublicExecutionReportRetracted

Known Usage Locations

As direct type of elements (1):

nonpublicExecutionReportRetracted

Type Definition Detail

Type Derivation Tree

Document (extension)

Message (extension)

RequestMessage (extension)

NonCorrectableRequestMessage (extension)

NonpublicExecutionReportRetracted

XML Source (w/o annotations (4); see within schema source)

<xsd:complexType name="NonpublicExecutionReportRetracted">

<xsd:complexContent>

<xsd:extension base="NonCorrectableRequestMessage">

<xsd:sequence>

<xsd:choice minOccurs="0">

<xsd:sequence>

<xsd:element minOccurs="0" name="originatingEvent" type="OriginatingEvent"/>

<xsd:element name="trade" type="Trade"/>

<xsd:element maxOccurs="unbounded" minOccurs="0" name="tradingEvent" type="TradingEventSummary"/>

</xsd:sequence>

<xsd:group ref="PostTradeEventsBase.model"/>

<xsd:group ref="ChangeEventsBase.model"/>

<xsd:group ref="OptionsEventsBase.model"/>

<xsd:element ref="additionalEvent"/>

</xsd:choice>

<xsd:sequence>

<xsd:element minOccurs="0" name="primaryAssetClass" type="AssetClass"/>

<xsd:element minOccurs="0" name="tradeIdentifier" type="PartyTradeIdentifier"/>

<xsd:element maxOccurs="2" minOccurs="0" name="eventIdentifier" type="BusinessEventIdentifier"/>

<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty"/>

</xsd:sequence>

</xsd:choice>

<xsd:group minOccurs="0" ref="PartiesAndAccounts.model"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

Content Element Detail (all declarations; defined within this component only; 8/29)

additionalEvent

Type:	AdditionalEvent, complex content
Abstract:	(may not be used directly in instance XML documents)

XML Source (see within schema source)

<xsd:element ref="additionalEvent"/>

eventIdentifier

Type:

BusinessEventIdentifier, complex content

Individual parties should only use a single event identifier to identify a retraction. Platforms providing services on behalf of both parties in a transaction may provide event identifiers for both parties; in this case it is up to the recipient (the trade repository) to validate that the event IDs refer to the same event.

XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="2" minOccurs="0" name="eventIdentifier" type="BusinessEventIdentifier"/>

originatingEvent

Type:

OriginatingEvent, simple content

Simple Content

xsd:normalizedString

maxLength:	255
minLength:	0

XML Source (see within schema source)

<xsd:element minOccurs="0" name="originatingEvent" type="OriginatingEvent"/>

primaryAssetClass

Type:

AssetClass, simple content

Simple Content

xsd:normalizedString

maxLength:	255
minLength:	0

XML Source (see within schema source)

<xsd:element minOccurs="0" name="primaryAssetClass" type="AssetClass"/>

relatedParty

Type:

RelatedParty, complex content

This may be used to identify one or more parties that perform a role within the transaction. If this is within a partyTradeInformation block, the related party performs the role with respect to the party identifie by the "partyReference" in the partyTradeInformation block.

XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty"/>

trade

Type:

Trade, complex content

XML Source (see within schema source)

<xsd:element name="trade" type="Trade"/>

tradeIdentifier

Type:

PartyTradeIdentifier, complex content

XML Source (see within schema source)

<xsd:element minOccurs="0" name="tradeIdentifier" type="PartyTradeIdentifier"/>

tradingEvent

Type:

TradingEventSummary, complex content

This is provided to support snapshot reporting that requires trading history. Some implementations are using the "trade" event to report the current snapshot of a contract. In these cases it may also be necessary to report the most recent trading event to support regulatory reporting mandates. For this reason the tradingEvent is provided to allow that event to be attached to the trade report.

XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="tradingEvent" type="TradingEventSummary"/>

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.