ISO 8601

ISO 8601 is an international standard for date and time representations issued by the International Organization for Standardization (ISO). Specifically, the standard is titled "Data elements and interchange formats — Information interchange — Representation of dates and times." The signature feature of ISO 8601 date and time representations is the ordering of date and time values from the most to the least significant or, in plain terms, from the largest (the year) to the smallest (the second).

Example date:

2024-05-20

Example separate date and time in UTC:

2024-05-20 02:33Z

Example combined date and time in UTC:

2024-05-20T02:33Z

Example date with week number:

Template:ISOWEEKDATE

History

The first edition of the ISO 8601 standard was published in 1988. It unified and replaced a number of older ISO standards on various aspects of date and time notation: ISO 2014, ISO 2015, ISO 2711, ISO 3307, and ISO 4031.<ref name=doc2004>Technical Committee ISO/TC 154, Processes, data elements and documents in commerce, industry and administration. (2004-12-01). "ISO 8601:2004(E)". ISO. Archived from the original on 2008-05-13. Retrieved on 2008-06-08. "Annex A … From that concept representations of all other date and time values were logically derived; thus, ISO 2014, ISO 3307 and ISO 4031 have been superseded. … Identification of a particular date by means of ordinal dates (ISO 2711) and by means of the week numbering system (ISO 2015) were alternative methods that the basic concept of this International Standard could also encompass; thus, ISO 2015 and ISO 2711 have now been superseded."</ref> It has been superseded by a second edition in 2000 and by the current third edition, ISO 8601:2004, published 2004-12-03.

ISO 2014 was the standard that originally introduced the big-endian all-numeric date notation [YYYY]-[MM]-[DD]. The ISO week numbering system was introduced in ISO 2015, and the identification of days by ordinal dates was originally defined in ISO 2711.

It is maintained by ISO Technical Committee TC 154.

Scope and application of the standard

The scope of the standard covers representations for Gregorian dates, time of day, combined date and time of day, and time intervals. Dates can be represented in three forms: 1) year-month-day of month, 2) year-week number-day of week, and 3) year-day of year. Time of day is represented by using the 24-hour clock. Combined date and time is represented by merging both the date and time of day representations to denote a single time point. Time intervals are represented in a number of ways by using a combination of a start point, end point, duration, and context information.

The application of the standard is intended to be very broad. It applies to all written communications that contain dates, times, and time intervals regardless of the communication medium (printed, electronic, or hand written) or the location of the sender and receiver (either within an organization, between organizations, or across international boundaries). The application of the standard was never meant to be limited to dates and times processed, stored, and displayed by computers. It applies to all industries and all forms of human activity where accurate and unambiguous representations of dates, times, and time intervals are needed when communicating internationally, nationally, locally, internally, or even privately.

The standard does not cover worded dates, nor does it preclude the use of worded dates. Worded dates are specifically omitted from the standard mostly because their language dependency can impede international communication.

General principles

• Date and time values are organized from the most to the least significant: year, month (or week), day, hour, minute, second, and fraction of second. The lexicographical order of the representation corresponds to chronological order, except for date representations involving negative years.
• Each date and time value has a fixed number of digits that must be padded with leading zeros.
• Representations can be done in one of two formats—a basic format with a minimal number of separators or an extended format with separators added to enhance human readability.<ref>Numeric representation of Dates and Time </ref> The separator used between date values (year, month, week, and day) is the hyphen, while the colon is used as the separator between time values (hours, minutes, and seconds). For example, the 6th day of the 1st month of the year 2009 may be written as "2009-01-06" in the extended format or simply as "20090106" in the basic format without ambiguity. The extended formats are preferred over the basic formats not only for human readability, but because some basic formats can appear to be ambiguous to those unfamiliar with the standard.
• For reduced accuracy, any number of values may be dropped from any of the date and time representations, but in the order from the least to the most significant. For example, "2004-05" is a valid ISO 8601 date, which indicates the 5th month of the year 2004. This date will never represent the 5th day of some unknown month in 2004.
• When higher precision is needed, the standard supports the addition of a decimal fraction to the smallest time value in the representation.

Dates

Template:CURRENTCALENDAR The standard uses the Gregorian calendar, which is the most widely used calendar in the world and is already the de facto standard of international trade.

As a point of interest, ISO 8601 fixes a reference calendar date to the Gregorian calendar of 1875-05-20 as the date the Convention du Mètre was signed in Paris. However, ISO calendar dates before the Convention are still compatible with the Gregorian calendar all the way back to the official introduction of the Gregorian calendar on 1582-10-15. Earlier dates, in the proleptic Gregorian calendar, may be used by mutual agreement of the partners exchanging information.

Years

YYYY

±YYYYY

ISO 8601 prescribes, as a minimum, a four-digit year [YYYY] to avoid the year 2000 problem.

To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation [±YYYYY], but only by prior agreement between the sender and the receiver.<ref>Technical Committee ISO/TC 154, Processes, data elements and documents in commerce, industry and administration. (2004-12-01). "ISO 8601:2004(E)". ISO. Retrieved on 2008-06-08. "3.5 Expansion … By mutual agreement of the partners in information interchange, it is permitted to expand the component identifying the calendar year, which is otherwise limited to four digits. This enables reference to dates and times in calendar years outside the range supported by complete representations, i.e. before the start of the year [0000] or after the end of the year [9999]."</ref> An expanded year representation must have an agreed upon number of extra year digits beyond the four-digit minimum and is always prefixed with a + or − sign with the convention that year 0 is positive.

Calendar dates

YYYY-MM-DD	or	YYYYMMDD
YYYY-MM	(but not YYYYMM)

Calendar date representations are in the form as shown in the box to the right. [YYYY] indicates a four-digit year, 0000 through 9999. [MM] indicates a two-digit month of the year, 01 through 12. [DD] indicates a two-digit day of that month, 01 through 31. For example, "the 5th of April 1981" may be represented as either "1981-04-05" in the extended format or "19810405" in the basic format.

The standard also allows for calendar dates to be written with reduced accuracy. For example, one may write "1981-04" to mean "1981 April", and one may simply write "1981" to refer to that year or "19" to refer to that century.

Although the standard allows both the YYYY-MM-DD and YYYYMMDD formats for complete calendar date representations, if the day [DD] is omitted then only the YYYY-MM format is allowed. By disallowing dates of the form YYYYMM, the standard avoids confusion with the truncated representation YYMMDD (still often used).

Week dates

YYYY-Www	or	YYYYWww
YYYY-Www-D	or	YYYYWwwD

Week date representations are in the format as shown in the box to the right. [YYYY] indicates the ISO week-numbering year which is slightly different to the calendar year (see below). [Www] is the week number prefixed by the letter 'W', from W01 through W53. [D] is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday. This form is popular in the manufacturing industries.

There are mutually equivalent descriptions of week 01:

• the week with the year's first Thursday in it (the formal ISO definition),
• the week with 4 January in it,
• the first week with the majority (four or more) of its days in the starting year, and
• the week starting with the Monday in the period 29 December – 4 January.

If 1 January is on a Monday, Tuesday, Wednesday or Thursday, it is in week 01. If 1 January is on a Friday, Saturday or Sunday, it is in week 52 or 53 of the previous year. 28 December is always in the last week of its year.

The week number can be described by counting the Thursdays: week 12 contains the 12th Thursday of the year.

The ISO week-numbering year starts at the first day (Monday) of week 01 and ends at the Sunday before the new ISO year (hence without overlap or gap). It consists of 52 or 53 full weeks. The ISO week-numbering year number deviates from the number of the calendar year (Gregorian year) on a Friday, Saturday, and Sunday, or a Saturday and Sunday, or just a Sunday, at the start of the calendar year (which are at the end of the previous ISO week-numbering year) and a Monday, Tuesday and Wednesday, or a Monday and Tuesday, or just a Monday, at the end of the calendar year (which are in week 01 of the next ISO week-numbering year). For Thursdays, the ISO week-numbering year number is always equal to the calendar year number.

Examples:

• 2008-12-29 is written "Template:ISOWEEKDATE"
• 2010-01-03 is written "Template:ISOWEEKDATE"

For an overview of week numbering systems see week number. The US system has weeks from Sunday through Saturday, and partial weeks at the beginning and the end of the year. An advantage is that no separate year numbering like the ISO week-numbering year is needed, while correspondence of lexicographical order and chronological order is preserved.

Ordinal dates

YYYY-DDD

or

YYYYDDD

An Ordinal date is a simple form for occasions when the arbitrary nature of week and month definitions are more of an impediment than an aid, for instance, when comparing dates from different calendars. As represented above, [YYYY] indicates a year. [DDD] is the day of that year, from 001 through 365 (366 in leap years). For example, "1981-04-05" is also "1981-095".

This format has particular use for simple hardware systems that have need of a date system, but where including full calendar calculation software may be a significant nuisance. This system is sometimes, though incorrectly, referred to as the Julian Date.

Times

hh:mm:ss	or	hhmmss
hh:mm	or	hhmm
hh

ISO 8601 uses the 24-hour clock system. The basic format is [hh][mm][ss] and the extended format is [hh]:[mm]:[ss].

• [hh] refers to a zero-padded hour between 00 and 24, where 24 is only used to notate the midnight at the end of a calendar day.
• [mm] refers to a minute between 00 and 59.
• [ss] refers to a second between 00 and 59 (or 60 in the exceptional case of an added leap second).

So a time might appear as either "134730" in the basic format or "13:47:30" in the extended format.

It is also acceptable to omit lower order time elements for reduced accuracy: [hh]:[mm], [hh][mm] and [hh] are all used.

Midnight is a special case and can be referred to as both "00:00" and "24:00". The notation "00:00" is used at the beginning of a calendar day and is the more frequently used. At the end of a day use "24:00". Note that "2007-04-05T24:00" is the same instant as "2007-04-06T00:00" (see Combined date and time representations below).

Decimal fractions may also be added to any of the three time elements. A decimal point, either a comma or a dot (without any preference as stated most recently in resolution 10 of the 22nd General Conference CGPM in 2003) , is used as a separator between the time element and its fraction. A fraction may only be added to the lowest order time element in the representation. To denote "14 hours, 30 and one half minutes", do not include a seconds figure. Represent it as "14:30,5" or "1430,5". There is no limit on the number of decimal places for the decimal fraction. However, the number of decimal places needs to be agreed to by the communicating parties.

Time zone designators

Z
±hh:mm	or	±hhmm
±hh

If no time zone information is given with a time representation, the time is assumed to be in local time. While it may be safe to assume local time when communicating in the same time zone, it is ambiguous when used in communicating across different time zones. It is usually preferable to indicate a time zone (zone designator) using the standard’s notation.

UTC

If the time is in UTC, add a 'Z' directly after the time without a space. 'Z' is the zone designator for the zero UTC offset. "09:30 UTC" is therefore represented as "09:30Z" or "0930Z". "14:45:15 UTC" would be "14:45:15Z" or "144515Z".

UTC time is also known as 'Zulu' time, since 'Zulu' is the NATO phonetic alphabet word for 'Z'.

Other time zones

The zone designator for other time zones is specified by the offset from UTC in the format ±[hh]:[mm], ±[hh][mm], or ±[hh]. So if the time being described is one hour ahead of UTC (such as the time in Berlin during the winter), the zone designator would be "+01:00", "+0100", or simply "+01". This is appended to the time in the same way that 'Z' was above. Note that the zone designator is the actual offset from UTC and does not include any information on daylight saving time. The zone designator or UTC offset for a user in Chicago, therefore, would be "−06:00" for the winter (Central Standard Time) and "−05:00" for the summer (Central Daylight Time). The following times all refer to the same moment: "18:30Z", "22:30+04", "1130−0700", and "15:00−03:30". Nautical time zone letters are not used with the exception of Z.

Time zone conversions

Conversion between time zones obeys the relationship

"time in zone A" − "UTC offset for zone A" = "time in zone B" − "UTC offset for zone B",

in which each side of the equation is equivalent to UTC. (The more familiar term "UTC offset" is used here rather than the term "zone designator" used by the standard.)

The conversion equation can be rearranged to

"time in zone B" = "time in zone A" − "UTC offset for zone A" + "UTC offset for zone B".

For example, what time is it in Los Angeles (UTC offset= −08) when the New York Stock Exchange opens at 09:30−05?

time in Los Angeles = 09:30 − (−05:00) + (−08:00) = 06:30

In Delhi (UTC offset= +5:30), the New York Stock Exchange opens at

time in Delhi = 09:30 − (−05:00) + (+5:30) = 20:00

Combined date and time representations

<date>T

<date>TZ

Combining date and time representations to represent a single point in time (time point) is quite simple. It is in the format of <date>T where the time designator [T] is used to show the start of the time component of the representation. Both the date and time components of the time point are any proper representations of date and time specified by the standard. For example, "2007-04-05T14:30" uses the extended formats for date and time [YYYY]-[MM]-[DD]T[hh]:[mm], while "20090621T0545Z" uses the basic formats [YYYY][MM][DD]T[hh][mm]Z.

A combined date and time representation can be used to mark any type of event time such as an e-mail delivery, a financial transaction, the start of a medical treatment, or even a natural occurrence (like the summer solstice of 2009 shown above). Combined date and time representations are also used in conjunction with time intervals as discussed later in this article.

The date and time representations may appear in proximity to each other, often separated by a space or sometimes by other characters. In these cases they occupy two separate fields in a data system, rather than a single combined representation. This is usually done for human readability. Unlike the previous examples, "2007-04-05 14:30" is considered two separate, but acceptable, representations—one for date and the other for time. It is then left to the reader to interpret the two separate representations as meaning a single time point based on the context.

Durations

PnYnMnDTnHnMnS

PnW

P<date>T

Durations are a component of time intervals and define the amount of intervening time in a time interval. They should only be used as part of a time interval as prescribed by the standard. Time intervals are discussed in the next section.

Durations are represented by the format P[n]Y[n]M[n]DT[n]H[n]M[n]S or P[n]W as shown to the right. In these representations, the [n] is replaced by the value for each of the date and time elements that follow the [n]. Leading zeros are not required, but the maximum number of digits for each element should be agreed to by the communicating parties. The capital letters 'P', 'Y', 'M', 'W', 'D', 'T', 'H', 'M', and 'S' are designators for each of the date and time elements and are not replaced.

• P is the duration designator (historically called "period") placed at the start of the duration representation.
• Y is the year designator that follows the value for the number of years.
• M is the month designator that follows the value for the number of months.
• W is the week designator that follows the value for the number of weeks.
• D is the day designator that follows the value for the number of days.
• T is the time designator that precedes the time components of the representation.
• H is the hour designator that follows the value for the number of hours.
• M is the minute designator that follows the value for the number of minutes.
• S is the second designator that follows the value for the number of seconds.

For example, "P3Y6M4DT12H30M5S" represents a duration of "three years, six months, four days, twelve hours, thirty minutes, and five seconds". Date and time elements including their designator may be omitted if their value is zero, and lower order elements may also be omitted for reduced precision. For example, "P23DT23H" and "P4Y" are both acceptable duration representations.

To resolve ambiguity, "P1M" is a one-month duration and "PT1M" is a one-minute duration (note the time designator, T, that precedes the time value). The smallest value used may also have a decimal fraction, as in "P0.5Y" to indicate half a year. The standard does not prohibit date and time values in a duration representation from exceeding their "carry-over points" except as noted below. Thus, "PT36H" could be used as well as "P1DT12H" for representing the same duration.

Alternately, a format for duration based on combined date and time representations may be used by agreement between the communicating parties either in the basic format PYYYYMMDDThhmmss or in the extended format P[YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]. For example, the same duration as shown above would be "P0003-06-04T12:30:05". However, individual date and time values cannot exceed their "carry-over point" (ex., a value of "13" for the month or "25" for the hour would not be permissible).

Time intervals

<start>/<end>

<start>/<duration>

<duration>/<end>

<duration>

A time interval is the intervening time between two time points. The amount of intervening time is expressed by a duration (as described in the previous section). The two time points (start and end) are expressed by either a combined date and time representation or just a date representation.

There are four ways to express a time interval:

1. Start and end, such as "2007-03-01T13:00:00Z/2008-05-11T15:30:00Z"
2. Start and duration, such as "2007-03-01T13:00:00Z/P1Y2M10DT2H30M"
3. Duration and end, such as "P1Y2M10DT2H30M/2008-05-11T15:30:00Z"
4. Duration only, such as "P1Y2M10DT2H30M", with additional context information

Of these, the first three require two values separated by an interval designator which is usually a solidus or forward slash "/". In certain applications, a double hyphen (--) can be used as a separator instead of a solidus (see Section 4.4.2 of the standard).

For <start>/<end> expressions, if any elements are missing from the end value, they are assumed to be the same as for the start value including the time zone. This feature of the standard allows for concise representations of time intervals. For example, the date of a two-hour meeting including the start and finish times could be simply shown as "2007-12-14T13:30/15:30", or the beginning and end dates of a monthly billing period as "2008-02-15/03-14".

If greater precision is desirable to represent the time interval, then more time elements can be added to the representation. An observation period that has a duration of approximately three days, for example, can be succinctly shown as "2007-11-13/15". If the exact start and end of the observation period need to be shown either for clarity or for measurement and recording purposes, the same time interval representation could be expanded to "2007-11-13T00:00/15T24:00".

Repeating intervals

Rnn/<interval>

R/<interval>

Repeating intervals are specified in section "4.5 Recurring time interval". They are formed by adding "R[n]/" to the beginning of an interval expression, where 'R' is used as the letter itself and [n] is replaced by the number of repetitions. Leaving out the value for [n] means an unbounded number of repetitions. So, to repeat the interval of "P1Y2M10DT2H30M" five times starting at "2008-03-01T13:00:00Z", use "R5/2008-03-01T13:00:00Z/P1Y2M10DT2H30M". It is left open when the repetition takes place.

Truncated representations

ISO 8601:2000 allowed truncation (by agreement), where leading components of a date or time are omitted. Notably, this allowed two-digit years to be used and the ambiguous formats YY-MM-DD and YYMMDD. This provision was removed in ISO 8601:2004.

See also

• Date and time notation by country
• ISO 8601 usage
• RFC 3339, Date and Time on the Internet, 2002-July

Notes

<references group=""></references>

External links

• Current date in week date and ordinal date format
• Template:Dmoz
• ISO 8601:2004(E) from ISO (zip-pdf, 228KB)
• ISO 8601 summary by Markus Kuhn
• Summary of 8601 by ISO
• Technical Committee ISO/TC 154, Processes, data elements and documents in commerce, industry and administration.
• The Mathematics of the ISO 8601 Calendar
• W3C Specification about UTC Date and Time and IETF Internet standard RFC 3339, based on ISO 8601

Implementations

• An implementation in Java (Joda-Time)
• Converting and implementing
• Setting Your Personal Computer for ISO 8601 (guide for Microsoft Windows computers)

Template:Time measurement and standards