# XML Schema Documentation

### Model Group: PricingInputDates.model

#### [Table of contents]

Name | PricingInputDates.model
Used by (from the same schema document) | Complex Type PricingStructureValuation
Documentation | The dates that might be relevant for a pricing input, e.g. what valuation date it applies to, when it was built, when the data comes from, etc..

XML Instance Representation
<baseDate> IdentifiedDate </baseDate> [1]

'The base date for which the structure applies, i.e. the curve date. Normally this will align with the valuation date.'

<spotDate> IdentifiedDate </spotDate> [0..1]

'The spot settlement date for which the structure applies, normally 0-2 days after the base date. The difference between the baseDate and the spotDate is termed the settlement lag, and is sometimes called \"days to spot\".'

<inputDataDate> IdentifiedDate </inputDataDate> [0..1]

'The date from which the input data used to construct the pricing input was obtained. Often the same as the baseDate, but sometimes the pricing input may be \"rolled forward\", in which input data from one date is used to generate a curve for a later date.'

<endDate> IdentifiedDate </endDate> [0..1]

'The last date for which data is supplied in this pricing input.'

<buildDateTime> xsd:dateTime </buildDateTime> [0..1]

'The date and time when the pricing input was generated.'

Diagram
Schema Component Representation
<xsd:group name="PricingInputDates.model">
<xsd:sequence>
<xsd:element name="baseDate" type=" IdentifiedDate "/>
<xsd:element name="spotDate" type=" IdentifiedDate " minOccurs="0"/>
<xsd:element name="inputDataDate" type=" IdentifiedDate " minOccurs="0"/>
<xsd:element name="endDate" type=" IdentifiedDate " minOccurs="0"/>
<xsd:element name="buildDateTime" type=" xsd:dateTime " minOccurs="0"/>
</xsd:sequence>
</xsd:group>