17.16.5.13 DATE

Description: The current date and time. If no calendar is specified via a field-specific-switch or date-and-time- formatting-switch,the Gregorian calendar [ISO 8601, 3.2.1]is used. As specified in 17.16.4.1, if no date-and- time-formatting-switch is present, a date or time result is formatted in an implementation-defined manner.

Field Value: The current date and time.

Switches: Zero or one date-and-time-formatting-switch and zero or one of the following field-specific-switches.

\h

Use the Hijri Lunar or Hebrew Lunar calendar, depending on the language specified by the lang element (17.3.2.20).

\l

When a field update is performed, if no date-and-time-formatting-switch is used, this switch is an instruction specifying that the field shall use the date-and-time- formatting-switch last used by the hosting application when inserting a new DATE field. If there is no last-used date format available, then the date-and-time-formatting- switch used is implementation-defined.

\s

Use the Saka Era calendar.

[Example: Consider the case in which the following fields are updated in a US-English context by an application with a default date-and-time-formatting-switch of M/d/yyyy on 2006-01-05T19:09:01:

DATE DATE @ “dddd, MMMM dd, yyyy HH:mm:ss” DATE @ “dddd, MMMM dd, yyyy HH:mm:ss” \h DATE @ “dddd, MMMM dd, yyyy HH:mm:ss” \s

the results are:

1/5/2006
Thursday, January 05, 2006 19:09:01
AlKhamis, Thoul Hijjah 05, 1426 19:09:01
Bruhaspathivara, Pausa 15, 1927 19:09:01

end example]

[Note: For some date-and-time-formatting-switches, the DATE and TIME (17.16.5.65) fields can produce the same result. end note]

Syntax: