element <tradingEvent> (local)

Namespace: | http://www.fpml.org/FpML-5/recordkeeping
Type: | TradingEventSummary
Content: | complex, 6 elements
Defined: | locally witnin Events.model group in fpml-business-events-5-5.xsd; see XML source

Content Model Diagram

XML Representation Summary
<tradingEvent>
Content: | eventIdentifier*, eventType, agreementDate?, executionDateTime?, effectiveDate?, payment?
</tradingEvent>

Content model elements (6):

  agreementDate,
  effectiveDate (defined in AgreementAndEffectiveDates.model group),
  eventIdentifier (in tradingEvent),
  eventType,
  executionDateTime (defined in AgreementAndEffectiveDates.model group),
  payment (in tradingEvent)

Included in content model of elements (3):

  history, nonpublicExecutionReport, nonpublicExecutionReportRetracted

Annotation
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.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.