complexType "FxFixingScheduleSimple"
Namespace:
http://www.fpml.org/FpML-5/reporting
Content:
complex, 6 elements
Defined:
globally in fpml-fx-5-10.xsd; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
Content Model Diagram
XML Representation Summary
<...>
   
Content: 
startDate?, endDate?, dayType?, (businessCentersReference | businessCenters)?, fixingDate*
</...>
Content Model Elements (6):
businessCenters (defined in BusinessCentersOrReference.model group),
businessCentersReference,
dayType (in fixingSchedule defined in FxPerformanceSwap complexType),
endDate (in fixingSchedule defined in FxPerformanceSwap complexType),
fixingDate (in fixingSchedule defined in FxPerformanceSwap complexType),
startDate (in fixingSchedule defined in FxPerformanceSwap complexType)
All Direct / Indirect Based Elements (1):
fixingSchedule (defined in FxPerformanceSwap complexType)
Known Usage Locations
Annotation
Describes the FX fixing schedule, a single continuous observation period which follows the applicable business day schedule for the quoted rate source.
XML Source (w/o annotations (6); see within schema source)
<xsd:complexType name="FxFixingScheduleSimple">
<xsd:sequence>
<xsd:sequence>
<xsd:sequence>
<xsd:element minOccurs="0" name="startDate" type="xsd:date"/>
<xsd:element minOccurs="0" name="endDate" type="xsd:date"/>
</xsd:sequence>
</xsd:sequence>
<xsd:element minOccurs="0" name="dayType" type="DayTypeEnum"/>
<xsd:group minOccurs="0" ref="BusinessCentersOrReference.model"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="fixingDate" type="xsd:date"/>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; defined within this component only; 4/6)
dayType
Type:
DayTypeEnum, simple content
Specifies whether the schedule follows the business or calendar days.
Simple Content
enumeration of xsd:token
Enumeration:
"Business"
 - 
When calculating the number of days between two dates the count includes only business days.
See:  http://www.FpML.org
"Calendar"
 - 
When calculating the number of days between two dates the count includes all calendar days.
See:  http://www.FpML.org
"CommodityBusiness"
 - 
When calculating the number of days between two dates the count includes only commodity business days.
See:  http://www.FpML.org
"CurrencyBusiness"
 - 
When calculating the number of days between two dates the count includes only currency business days.
See:  http://www.FpML.org
"ExchangeBusiness"
 - 
When calculating the number of days between two dates the count includes only stock exchange business days.
See:  http://www.FpML.org
"ScheduledTradingDay"
 - 
When calculating the number of days between two dates the count includes only scheduled trading days.
See:  http://www.FpML.org
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="dayType" type="DayTypeEnum"/>
endDate
Type:
xsd:date, predefined, simple content
The end of the period over which observations are made to determine whether a trigger event has occurred.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="endDate" type="xsd:date"/>
fixingDate
Type:
xsd:date, predefined, simple content
An explicit list of dates in the schedule. For documentation purpose only.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="fixingDate" type="xsd:date"/>
startDate
Type:
xsd:date, predefined, simple content
The start of the period over which observations are made to determine whether a trigger has occurred.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="startDate" type="xsd:date"/>
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.