element <floatingRate> (local)

Namespace: | http://www.fpml.org/FpML-5/confirmation
Type: | FloatingRate
Content: | complex, 1 attribute, 7 elements
Defined: | locally witnin StubValue complexType in fpml-shared-5-3.xsd; see XML source

Content Model Diagram

XML Representation Summary
<floatingRate
id | = | xsd:ID
| >
Content: | floatingRateIndex, indexTenor?, floatingRateMultiplierSchedule?, spreadSchedule*, rateTreatment?, capRateSchedule*, floorRateSchedule*
</floatingRate>

Content model elements (7):

  capRateSchedule,
  floatingRateIndex (defined in FloatingRateIndex.model group),
  floatingRateMultiplierSchedule,
  floorRateSchedule,
  indexTenor (defined in FloatingRateIndex.model group),
  rateTreatment,
  spreadSchedule (defined in FloatingRate complexType)

Included in content model of elements (6):

  finalStub (in stubCalculationPeriod), finalStub (in stubCalculationPeriod), finalStub (in stubCalculationPeriodAmount), | finalStub (in stubCalculationPeriodAmount), initialStub (in stubCalculationPeriod), initialStub (in stubCalculationPeriodAmount)

Annotation
The rates to be applied to the initial or final stub may be the linear interpolation of two different rates. While the majority of the time, the rate indices will be the same as that specified in the stream and only the tenor itself will be different, it is possible to specift two different rates. For example, a 2 month stub period may use the linear interpolation of a 1 month and 3 month rate. The different rates would be specified in this component. Note that a maximum of two rates can be specified. If a stub period uses the same floating rate index, including tenor, as the regular calculation periods then this should not be specified again within this component, i.e. the stub calculation period amount component may not need to be specified even if there is an initial or final stub period. If a stub period uses a different floating rate index compared to the regular calculation periods then this should be specified within this component. If specified here, they are likely to have id attributes, allowing them to be referenced from within the cashflows component.
XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="2" name="floatingRate" type="FloatingRate"/>

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.