complexType "FxSchedule"

Namespace:	http://www.fpml.org/FpML-5/reporting
Content:	complex, 1 attribute, 12 elements
Defined:	globally in fpml-fx-targets-5-10.xsd; see XML source
Includes:	definitions of 1 attribute, 4 elements
Used:	at 2 locations

Content Model Diagram

XML Representation Summary

<...

xsd:ID

Content:

</...>

Content Model Elements (12):

adjustedDate (defined in FxSchedule complexType),

businessCenters (defined in BusinessCentersOrReference.model group),

businessCentersReference,

dateAdjustments (defined in FxSchedule complexType),

dateAdjustments (defined in ParametricSchedule.model group),

dateOffset (defined in FxSchedule complexType),

dayType (defined in ParametricSchedule.model group),

endDate (defined in ParametricSchedule.model group),

observationFrequency,

startDate (defined in ParametricSchedule.model group)

Known Direct Subtypes (2):

FxExpirySchedule, FxSettlementSchedule

All Direct / Indirect Based Elements (4):

expirySchedule (defined in FxExpiryDateOrSchedule.model group),

expirySchedule (in fxTargetKnockoutForward),

settlementSchedule (defined in FxSettlementDateOrSchedule.model group),

settlementSchedule (in fxTargetKnockoutForward)

Known Usage Locations

In derivations of other global types (2):

FxExpirySchedule (as extension base),

FxSettlementSchedule (as extension base)

Annotation

The FxSchedule may be expressed as explicit adjusted dates, or a parametric representation plus optional adjusted dates, or as an offset plus optional adusted dates.

XML Source (w/o annotations (6); see within schema source)

<xsd:complexType name="FxSchedule">

<xsd:choice>

<xsd:sequence>

<xsd:element minOccurs="0" name="dateAdjustments" type="BusinessDayAdjustments"/>

<xsd:element maxOccurs="unbounded" name="adjustedDate" type="xsd:date"/>

</xsd:sequence>

<xsd:sequence>

<xsd:choice>

<xsd:group ref="ParametricSchedule.model"/>

<xsd:element name="dateOffset" type="FxDateOffset"/>

</xsd:choice>

<xsd:element maxOccurs="unbounded" minOccurs="0" name="adjustedDate" type="xsd:date"/>

</xsd:sequence>

</xsd:choice>

<xsd:attribute name="id" type="xsd:ID"/>

</xsd:complexType>

Attribute Detail (all declarations; defined within this component only; 1/1)

Type:	xsd:ID, predefined
Use:	optional

XML Source (see within schema source)

<xsd:attribute name="id" type="xsd:ID"/>

Content Element Detail (all declarations; defined within this component only; 4/12)

adjustedDate

Type:

xsd:date, predefined, simple content

List of schedule dates. These dates have been subject to adjustments based on the dateAdjustments structure.

XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="unbounded" name="adjustedDate" type="xsd:date"/>

adjustedDate

Type:

xsd:date, predefined, simple content

List of schedule dates. These dates have been subject to adjustments based on the dateAdjustments structure.

XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="adjustedDate" type="xsd:date"/>

dateAdjustments

Type:

BusinessDayAdjustments, complex content

Date adjustments applied to the adjusted dates including the business day convention and the business centers.

XML Source (w/o annotations (1); see within schema source)

<xsd:element minOccurs="0" name="dateAdjustments" type="BusinessDayAdjustments"/>

dateOffset

Type:

FxDateOffset, complex content

The representation of the schedule as an offset relative to another schedule. For example, the settlement schedule may be relative to the expiry schedule by an FxForward offset.

XML Source (w/o annotations (1); see within schema source)

<xsd:element name="dateOffset" type="FxDateOffset"/>

XML schema documentation generated with DocFlex/XML 1.10b5 using DocFlex/XML XSDDoc 2.8.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.