# XML Schema Documentation

### Complex Type: Offset

#### [Table of contents]

Super-types: | Interval < Offset (by extension)
Sub-types: | DateOffset (by extension) RelativeDateOffset (by extension) AdjustedRelativeDateOffset (by extension) RelativeDates (by extension)

Name | Offset
Used by (from the same schema document) | Complex Type DividendPaymentDate
Abstract | no
Documentation | A type defining an offset used in calculating a new date relative to a reference date. Currently, the only offsets defined are expected to be expressed as either calendar or business day offsets.

XML Instance Representation
<...
id=" xsd:ID [0..1]">
<periodMultiplier> xsd:integer </periodMultiplier> [1]

'A time period multiplier, e.g. 1, 2 or 3 etc. A negative value can be used when specifying an offset relative to another date, e.g. -2 days. If the period value is T (Term) then periodMultiplier must contain the value 1.'

<period> PeriodEnum </period> [1]

'A time period, e.g. a day, week, month, year or term of the stream. If the periodMultiplier value is 0 (zero) then period must contain the value D (day).'

<dayType> DayTypeEnum </dayType> [0..1]

'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.'

</...>
Diagram
Schema Component Representation
<xsd:complexType name="Offset">
<xsd:complexContent>
<xsd:extension base=" Interval ">
<xsd:sequence>
<xsd:element name="dayType" type=" DayTypeEnum " minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>