XML Schema Documentation

Complex Type: OptionBase

[Table of contents]

Super-types: Product < OptionBase (by extension)
Sub-types:
Name OptionBase
Abstract yes
Documentation A type for defining the common features of options
XML Instance Representation
<...
id=" xsd:ID [0..1]">
<productType> ProductType </productType> [0..*]

'A classification of the type of product. FpML defines a simple product categorization using a coding scheme.'

<productId> ProductId </productId> [0..*]

'A product reference identifier allocated by a party. FpML does not define the domain values associated with this element. Note that the domain values for this element are not strictly an enumerated list.'

<buyerPartyReference> PartyOrTradeSideReference </buyerPartyReference> [1]

'A reference to the party that buys this instrument, ie. pays for this instrument and receives the rights defined by it. See 2000 ISDA definitions Article 11.1 (b). In the case of FRAs this the fixed rate payer.'

<sellerPartyReference> PartyOrTradeSideReference </sellerPartyReference> [1]

'A reference to the party that sells (\"writes\") this instrument, i.e. that grants the rights defined by this instrument and in return receives a payment for it. See 2000 ISDA definitions Article 11.1 (a). In the case of FRAs this is the floating rate payer.'

<optionType> OptionTypeEnum </optionType> [1]

'The type of option transaction. From a usage standpoint, put/call is the default option type, while payer/receiver indicator is used for options index credit default swaps, consistently with the industry practice. Straddle is used for the case of straddle strategy, that combine a call and a put with the same strike.'

</...>
Diagram
Schema Component Representation
<xsd:complexType name="OptionBase" abstract="true">
<xsd:complexContent>
<xsd:extension base=" Product ">
<xsd:sequence>
<xsd:group ref=" BuyerSeller.model "/>
<xsd:element name="optionType" type=" OptionTypeEnum "/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>