group "TradeReferenceInformationContents.model"
Namespace:
http://www.fpml.org/FpML-5/confirmation
Content:
6 elements
Defined:
globally in fpml-business-events-5-4.xsd; see XML source
Includes:
definitions of 6 elements
Used:
never
Content Model Diagram
Complex Content Model
(originatingEvent | terminatingEvent)?, partyTradeIdentifier*, partyTradeInformation*, productType?, productId?
Content Model Elements (6):
originatingEvent (defined in TradeReferenceInformationContents.model group),
partyTradeIdentifier (defined in TradeReferenceInformationContents.model group),
partyTradeInformation (defined in TradeReferenceInformationContents.model group),
productId (defined in TradeReferenceInformationContents.model group),
productType (defined in TradeReferenceInformationContents.model group),
terminatingEvent (defined in TradeReferenceInformationContents.model group)
Annotation
Defines a model group that allows trade identifiers and/or trade information to be represented.
XML Source (w/o annotations (5); see within schema source)
<xsd:group name="TradeReferenceInformationContents.model">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:element name="originatingEvent" type="OriginatingEvent"/>
<xsd:element name="terminatingEvent" type="TerminatingEvent"/>
</xsd:choice>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeInformation" type="PartyTradeInformation"/>
<xsd:element minOccurs="0" name="productType" type="ProductType"/>
<xsd:element minOccurs="0" name="productId" type="ProductId"/>
</xsd:sequence>
</xsd:group>
Content Element Detail (all declarations; defined within this component only; 6/6)
originatingEvent
Type:
OriginatingEvent, simple content
This may be used to describe why a trade was created. This can be used to provide context for a newly created trade that is not part of a post-trade event. For example, it can report that the trade was created as a result of netting activity, or due to a transfer, an allocation process, etc. Omitting this implies that the trade record was created as a result of a negotiated new trade.
Simple Content
xsd:normalizedString
maxLength:
 255
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="originatingEvent" type="OriginatingEvent"/>
partyTradeIdentifier
Type:
PartyTradeIdentifier, complex content
This allows the acknowledging party to supply additional trade identifiers for a trade underlying a request relating to a business event.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
partyTradeInformation
Type:
PartyTradeInformation, complex content
This allows the acknowledging party to supply additional trade information about a trade underlying a request relating to a business event.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="partyTradeInformation" type="PartyTradeInformation"/>
productId
Type:
ProductId, simple content
Simple Content
xsd:normalizedString
maxLength:
 255
XML Source (see within schema source)
<xsd:element minOccurs="0" name="productId" type="ProductId"/>
productType
Type:
ProductType, simple content
Simple Content
xsd:normalizedString
maxLength:
 255
XML Source (see within schema source)
<xsd:element minOccurs="0" name="productType" type="ProductType"/>
terminatingEvent
Type:
TerminatingEvent, simple content
This may be used to describe why a trade was terminated.
Simple Content
xsd:normalizedString
maxLength:
 255
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="terminatingEvent" type="TerminatingEvent"/>
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.