element <step> (local)
Namespace:
http://www.fpml.org/FpML-5/confirmation
Type:
Step
Content:
complex, 1 attribute, 2 elements
Defined:
locally within Schedule complexType in fpml-shared-5-8.xsd; see XML source
Content Model Diagram
XML Representation Summary
<step
   
 = 
xsd:ID
   
>
   
Content: 
</step>
Content model elements (2):
stepValue (defined in Step complexType)
Included in content model of elements (22):
accrualFactor,
capRateSchedule,
feeAmountSchedule,
feeRateSchedule,
fixedRate (in underlyer defined in GenericProduct complexType),
fixedRateSchedule (in calculation in calculationPeriodAmount),
fixedRateSchedule (in repo),
floatingRateMultiplierSchedule,
floorRateSchedule,
knownAmountSchedule,
level (defined in FxConditionLevel.model group),
pivot,
rate (defined in FxPayoffCap complexType),
ratio (in payoffLeverage defined in FxVanillaPayoffRegion complexType),
ratio (in payoffLeverage in vanillaPayoffRegion in fxAccrualForward),
spreadSchedule (defined in FloatingRate complexType),
spreadSchedule (in underlyerFinancing),
strike (defined in FxVanillaPayoffRegion complexType),
strike (defined in StrikeOrStrikeReference.model group),
triggerRate (defined in FxAccrualKnockoutBarrier.model group),
triggerRate (defined in FxAccrualKnockoutBarrier.model group),
triggerRate (defined in FxBarrier.model group)
Annotation
The schedule of step date and value pairs. On each step date the associated step value becomes effective A list of steps may be ordered in the document by ascending step date. An FpML document containing an unordered list of steps is still regarded as a conformant document.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="step" type="Step"/>
XML schema documentation generated with DocFlex/XML 1.9.0 using DocFlex/XML XSDDoc 2.8.0 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.