complexType "FxFixingScheduleSimple"
Namespace:
http://www.fpml.org/FpML-5/confirmation
Content:
complex, 7 elements
Defined:
globally in fpml-fx-5-8.xsd; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
Content Model Diagram
XML Representation Summary
<...>
   
Content: 
</...>
Content Model Elements (7):
businessCenters (defined in BusinessCentersOrReference.model group),
businessCentersReference,
dayType (in fixingSchedule defined in FxPerformanceSwap complexType),
fixingTime (defined in FxSpotRateSource complexType),
observationSchedule (in fixingSchedule defined in FxPerformanceSwap complexType),
primaryRateSource (defined in FxSpotRateSource complexType),
secondaryRateSource (defined in FxSpotRateSource complexType)
All Direct / Indirect Based Elements (1):
fixingSchedule (defined in FxPerformanceSwap complexType)
Known Usage Locations
Annotation
Descibes the FX fixing schedule, a single continuous observation period which is based on business days for the quoted rate
Type Definition Detail
Type Derivation Tree
FxSpotRateSource (extension)
  FxFixingScheduleSimple
XML Source (w/o annotations (3); see within schema source)
<xsd:complexType name="FxFixingScheduleSimple">
<xsd:complexContent>
<xsd:extension base="FxSpotRateSource">
<xsd:sequence>
<!--Q?- can you specified dayType without BusinessCenters or vice versa? -->
<xsd:sequence minOccurs="0">
<xsd:element name="dayType" type="DayTypeEnum"/>
</xsd:sequence>
<xsd:element name="observationSchedule" type="FxObservationScheduleBase"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Content Element Detail (all declarations; defined within this component only; 2/7)
dayType
Type:
DayTypeEnum, simple content
In the case of an offset specified as a number of days, this element defines whether consideration is given as to whether a day is a good business day or not. If a day type of business days is specified then non-business days are ignored when calculating the offset. The financial business centers to use for determination of business days are implied by the context in which this element is used. This element must only be included when the offset is specified as a number of days. If the offset is zero days then the dayType element should not be included.
Simple Content
enumeration of xsd:token
Enumeration:
"Business"
 - 
When calculating the number of days between two dates the count includes only business days.
"Calendar"
 - 
When calculating the number of days between two dates the count includes all calendar days.
"CommodityBusiness"
 - 
When calculating the number of days between two dates the count includes only commodity business days.
"CurrencyBusiness"
 - 
When calculating the number of days between two dates the count includes only currency business days.
"ExchangeBusiness"
 - 
When calculating the number of days between two dates the count includes only stock exchange business days.
"ScheduledTradingDay"
 - 
When calculating the number of days between two dates the count includes only scheduled trading days.
minLength:
0
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="dayType" type="DayTypeEnum"/>
observationSchedule
Type:
FxObservationScheduleBase, complex content
Parametric schedule of rate observations.
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="observationSchedule" type="FxObservationScheduleBase"/>
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.