complexType "GenericProduct"
Namespace:
Content:
complex, 1 attribute, 21 elements
Defined:
Includes:
definitions of 11 elements
Used:
Content Model Diagram
XML Representation Summary
<...
   
 = 
xsd:ID
    >
   
Content: 
(primaryAssetClass?, secondaryAssetClass*, productType*, productId*, assetClass*, embeddedOptionType[0..2])?, multiLeg?, ((buyerPartyReference?, buyerAccountReference?, sellerPartyReference?, sellerAccountReference?) | counterpartyReference[0..2])?, premium?, effectiveDate?, expirationDate?, terminationDate?, underlyer*, notional*, optionType?, settlementCurrency*, dayCountFraction*
</...>
Content Model Elements (21):
assetClass (defined in Product.model group),
dayCountFraction (defined in GenericProduct complexType),
effectiveDate (defined in GenericProduct complexType),
expirationDate (defined in GenericProduct complexType),
notional (defined in GenericProduct complexType),
optionType (defined in GenericProduct complexType),
premium (defined in GenericProduct complexType),
primaryAssetClass (defined in Product.model group),
productId (defined in Product.model group),
productType (defined in Product.model group),
settlementCurrency (defined in GenericProduct complexType),
terminationDate (defined in GenericProduct complexType),
underlyer (defined in GenericProduct complexType)
All Direct / Indirect Based Elements (2):
genericProduct, nonSchemaProduct
Known Usage Locations
Annotation
Simple product representation providing key information about a variety of different products. Generic products - for use in Transparency reporting to define a product that represents an OTC derivative transaction whose economics are not fully described using an FpML schema. In other views, generic products are present for convenience to support internal messaging and workflows that are cross-product. Generic products are not full trade representations as such they are not intended to be used for confirming trades.
Type Definition Detail
Type Derivation Tree
Product (extension)
  GenericProduct
XML Source (w/o annotations (11); see within schema source)
<xsd:complexType name="GenericProduct">
<xsd:complexContent>
<xsd:extension base="Product">
<xsd:sequence>
<xsd:element minOccurs="0" name="multiLeg" type="xsd:boolean"/>
<xsd:choice minOccurs="0">
<xsd:group ref="BuyerSeller.model"/>
<xsd:element maxOccurs="2" minOccurs="0" name="counterpartyReference" type="PartyReference"/>
</xsd:choice>
<xsd:element minOccurs="0" name="premium" type="SimplePayment"/>
<xsd:element minOccurs="0" name="effectiveDate" type="AdjustableDate2"/>
<xsd:element minOccurs="0" name="expirationDate" type="AdjustableDate2"/>
<xsd:element minOccurs="0" name="terminationDate" type="AdjustableDate2"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="underlyer" type="TradeUnderlyer2"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="notional" type="CashflowNotional"/>
<!-- BAL 2012-02-17 set option type to a coding scheme for flexibility-->
<xsd:element minOccurs="0" name="optionType" type="OptionType"/>
<!-- LL 9/14/11 commented out pending WG/SC decision on how to proceed with generic properties, reverted to original definitions from 5.2TR
<xsd:element name="exerciseStyle" type="GenericExerciseStyle" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">For options, whether the option is a put or call option.</xsd:documentation>
</xsd:annotation>
</xsd:element>
-->
<xsd:element maxOccurs="unbounded" minOccurs="0" name="settlementCurrency" type="IdentifiedCurrency"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="dayCountFraction" type="DayCountFraction"/>
<!--
<xsd:group ref="GenericProductProperty.model" minOccurs="0" maxOccurs="unbounded" />
-->
<!-- Removed 2012-01 BAL because this duplicates information contained in SDR execution notification messages
<xsd:element name="quote" type="BasicQuotation" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation xml:lang="en">Valutions (observed or calculated prices or other values) for the product.</xsd:documentation>
<xsd:appinfo>
<view:override view="transparency" minOccurs="1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
-->
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Content Element Detail (all declarations; defined within this component only; 11/21)
counterpartyReference
Type:
PartyReference, empty content
XML Source (see within schema source)
<xsd:element maxOccurs="2" minOccurs="0" name="counterpartyReference" type="PartyReference"/>

dayCountFraction
Type:
DayCountFraction, simple content
Specifies a day count fraction or fractions that apply to the trade; this is provided to meet regulatory reporting requirements, but is not sufficient to to fully represent the economics of the trade..
Simple Content
xsd:normalizedString
maxLength:
255
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="dayCountFraction" type="DayCountFraction"/>

effectiveDate
Type:
AdjustableDate2, complex content
The earliest of all the effective dates of all constituent streams.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="effectiveDate" type="AdjustableDate2"/>

expirationDate
Type:
AdjustableDate2, complex content
For options, the last exercise date of the option.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="expirationDate" type="AdjustableDate2"/>

multiLeg
Type:
xsd:boolean, predefined, simple content
Indicates whether this transaction has multiple components, not all of which may be reported. The use of this field is not recommended, and it may be deprecated in a future version of this standard.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="multiLeg" type="xsd:boolean"/>

notional
Type:
CashflowNotional, complex content
The notional or notionals in effect on the last day of the last calculation period in each stream.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="notional" type="CashflowNotional"/>

optionType
Type:
OptionType, simple content
For options, what type of option it is (e.g. butterfly).
Simple Content
xsd:normalizedString
maxLength:
255
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="optionType" type="OptionType"/>

premium
Type:
SimplePayment, complex content
XML Source (see within schema source)
<xsd:element minOccurs="0" name="premium" type="SimplePayment"/>

settlementCurrency
Type:
IdentifiedCurrency, simple content
The currency or currencies in which the product can settle.
Simple Content
xsd:normalizedString
maxLength:
255
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="settlementCurrency" type="IdentifiedCurrency"/>

terminationDate
Type:
AdjustableDate2, complex content
The latest of all of the termination (accrual end) dates of the constituent or underlying streams.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="terminationDate" type="AdjustableDate2"/>

underlyer
Type:
TradeUnderlyer2, complex content
The set of underlyers to the trade that can be used in computing the trade's cashflows. If this information is needed to identify the trade, all of the trade's underlyers should be specified, whether or not they figure into the cashflow calculation. Otherwise, only those underlyers used to compute this particular cashflow need be supplied.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="underlyer" type="TradeUnderlyer2"/>

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.