Extended Date Time Format

ISO 8601 is an international standard covering the worldwide exchange and communication of date and time-related data. It is maintained by the International Organization for Standardization (ISO) and was first published in 1988, with updates in 1991, 2000, 2004, and 2019, and an amendment in 2022. The standard provides a well-defined, unambiguous method of representing calendar dates and times in worldwide communications, especially to avoid misinterpreting numeric dates and times when such data is transferred between countries with different conventions for writing numeric dates and times.

ISO 8601 applies to these representations and formats: ''dates'', in the Gregorian calendar (including the proleptic Gregorian calendar); ''times'', based on the 24-hour timekeeping system, with optional UTC offset; '' time intervals''; and combinations thereof.ISO 8601:2004 section 1 Scope The standard does not assign specific meaning to any element of the dates/times represented: the meaning of any element depends on the context of its use. Dates and times represented cannot use words that do not have a specified numerical meaning within the standard (thus excluding names of years in the Chinese calendar), or that do not use computer characters (excludes images or sounds).

In representations that adhere to the ISO 8601 ''interchange standard'', dates and times are arranged such that the greatest temporal term (typically a year) is placed at the left and each successively lesser term is placed to the right of the previous term. Representations must be written in a combination of Arabic numerals and the specific computer characters (such as "", ":", "T", "W", "Z") that are assigned specific meanings within the standard; that is, such commonplace descriptors of dates (or parts of dates) as "January", "Thursday", or "New Year's Day" are not allowed in interchange representations within the standard.

History

The first edition of the ISO 8601 standard was published as ''ISO 8601:1988'' 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. It has been superseded by a second edition ''ISO 8601:2000'' in 2000, by a third edition ''ISO 8601:2004'' published on 1 December 2004, and withdrawn and revised by ''ISO 8601-1:2019'' and ''ISO 8601-2:2019'' on 25 February 2019. ISO 8601 was prepared by, and is under the direct responsibility of, ISO Technical Committee TC 154.

ISO 2014, though superseded, is the standard that originally introduced the all-numeric date notation in most-to-least-significant order . The ISO week numbering system was introduced in ISO 2015, and the identification of days by ordinal dates was originally defined in ISO 2711.

Issued in February 2019, the fourth revision of the standard ISO 8601-1:2019 represents slightly updated contents of the previous ISO 8601:2004 standard, whereas the new ISO 8601-2:2019 defines various extensions such as uncertainties or parts of the Extended Date/Time Format (EDTF).

An amendment to ISO 8601-1 was published in October 2022 featuring minor technical clarifications and attempts to remove ambiguities in definitions. The most significant change, however, was the reintroduction of the "24:00:00" format to refer to the instant at the ''end'' of a calendar day.

An amendment to ISO 8601-2 was published in January 2025.

General principles

*Date and time values are ordered from the largest to smallest unit of time: year, month (or week), day, hour, minute, second, and fraction of second. The lexicographical order of the representation thus corresponds to chronological order, except for date representations involving negative years or time offset. This allows dates to be naturally sorted by, for example, file systems.
*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 formatsa ''basic format'' with a minimal number of separators or an ''extended format'' with separators added to enhance human readability.ISO:
ISO 8601 — Date and time format
. . The standard notes that "The basic format should be avoided in plain text." 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 in the extended format or as "20090106" in the basic format without ambiguity.
* For reduced precision,Earlier versions of ISO 8601 used the word ''accuracy'', not ''precision'', in the relevant section, e.g: 2.3.7 representation with reduced accuracy. This was corrected in ISO 8601-1:2019. 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 May (the fifth month) 2004. This format will never represent the 5th day of an unspecified month in 2004, nor will it represent a time-span extending from 2004 into 2005.
*If necessary for a particular application, the standard supports the addition of a decimal fraction to the smallest time value in the representation.

Dates

The standard uses the Gregorian calendar, which "serves as an international standard for civil use".

ISO 8601 allows Gregorian dates from the introduction of the calendar on 15 October 1582. For earlier (pre-Gregorian) dates, the calendar may be extended before its introduction (the proleptic Gregorian calendar) by explicit agreement of the parties involved. Such proleptic dates may not be adjusted to reconcile them with Julian dates.

Years

ISO 8601 prescribes, as a minimum, a four-digit year YYYto avoid the year 2000 problem. It therefore represents years from 0000 to 9999, year 0000 being equal to 1 BC and all others AD, similar to astronomical year numbering. However, years before 1583 (the first full year following the introduction of the Gregorian calendar) are not automatically allowed by the standard. Instead, the standard states that "values in the range 000through 582shall only be used by mutual agreement of the partners in information interchange".

To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation but only by prior agreement between the sender and the receiver. An expanded year representation �YYYYYmust have an agreed-upon number of extra year digits beyond the four-digit minimum, and it must be prefixed with a + or − sign instead of the more common AD/BC (or CE/BCE) notation; by convention 1 BC is labelled +0000, 2 BC is labeled −0001, and so on.

Calendar dates

Calendar date representations are in the form shown in the adjacent box. YYYindicates a four-digit year, 0000 through 9999. Mindicates a two-digit month of the year, 01 through 12. Dindicates a two-digit day of that month, 01 through 31. For example, "5 April 1981" may be represented as either in the ''extended format'' or "19810405" in the ''basic format''.

The standard also allows for calendar dates to be written with reduced precision. For example, one may write to mean "1981 April". One may simply write "1981" to refer to that year, "198" to refer to the decade from 1980 to 1989 inclusive, or "19" to refer to the century from 1900 to 1999 inclusive. Although the standard allows both the and YYYYMMDD formats for complete calendar date representations, if the day Dis omitted then only the format is allowed. By disallowing dates of the form YYYYMM, the standard avoids confusion with the truncated representation YYMMDD (still often used). The 2000 version also allowed writing the truncation to mean "April 5" but the 2004 version does not allow omitting the year when a month is present.

Examples:

* 7 January 2000 can be written as "2000-01-07" or "20000107"

Week dates

Week date representations are in the formats as shown in the adjacent box. YYYindicates the ''ISO week-numbering year'' which is slightly different from the traditional Gregorian calendar year (see below). wwis the '' week number'' prefixed by the letter ''W'', from W01 through W53. is the ''weekday number'', from 1 through 7, beginning with Monday and ending with Sunday.

There are several mutually equivalent and compatible descriptions of week 01:
* the week with the first business day in the starting year (considering that Saturdays, Sundays and 1 January are non-working days),
* the week with the starting 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 to 4 January.

As a consequence, 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 (there is no week 00). 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 first ISO week of a year may have up to three days that are actually in the Gregorian calendar year that is ending; if three, they are Monday, Tuesday and Wednesday. Similarly, the last ISO week of a year may have up to three days that are actually in the Gregorian calendar year that is starting; if three, they are Friday, Saturday, and Sunday. The Thursday of each ISO week is always in the Gregorian calendar year denoted by the ISO week-numbering year.

Examples:
* is written ""
* is written ""

Ordinal dates

An ''ordinal date'' is an ordinal format for the multiples of a day elapsed since the start of year.
It is represented as "YYYY-DDD" (or YYYYDDD), where YYYindicates a year and DDis the "day of year", from 001 through 365 (366 in leap years). For example, is the same as .

This simple form is preferable 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.
This format is used with simple hardware systems that have a need for a date system, but where including full calendar calculation software may be a significant nuisance. This system is sometimes referred to as "Julian Date", but this can cause confusion with the astronomical Julian day, a sequential count of the number of days since day 0 beginning Greenwich noon, Julian proleptic calendar (or noon on ISO date which uses the Gregorian proleptic calendar with a year 0000).

Times

ISO 8601 uses the 24-hour clock system. As of ISO 8601-1:2019, the ''basic format'' is T hmm] sand the ''extended format'' is T h m s Earlier versions omitted the T (representing time) in both formats.
* hrefers to a zero-padded hour between 00 and 24.
* mrefers to a zero-padded minute between 00 and 59.
* srefers to a zero-padded second between 00 and 60 (where 60 is only used to denote an added leap second).
So a time might appear as either "T134730" in the ''basic format'' or "T13:47:30" in the ''extended format''. ISO 8601-1:2019 allows the T to be omitted in the extended format, as in "13:47:30", but only allows the T to be omitted in the basic format when there is no risk of confusion with date expressions.

Either the seconds, or the minutes and seconds, may be omitted from the basic or extended time formats for greater brevity but decreased precision; the resulting reduced precision time formats are:
*T hmm] in ''basic format'' or T h min ''extended format'', when seconds are omitted.
*T h when both seconds and minutes are omitted.

As of ISO 8601-1:2019/Amd 1:2022, "00:00:00" may be used to refer to ''midnight'' corresponding to the instant at the beginning of a calendar day; and "24:00:00" to refer to midnight corresponding to the instant at the end of a calendar day. ISO 8601-1:2019 as originally published removed "24:00:00" as a representation for the end of day although it had been permitted in earlier versions of the standard.

A decimal fraction may be added to the lowest order time element present in any of these representations. A decimal mark, either a comma or a dot on the baseline, is used as a separator between the time element and its fraction. (Following ISO 80000-1 according to ISO 8601:1-2019, it does not stipulate a preference except within International Standards, but with a preference for a comma according to ISO 8601:2004.)
For example, to denote "14 hours, 30 and one half minutes", do not include a seconds figure; represent it as "14:30,5", "T1430,5", "14:30.5", or "T1430.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. For example, in Microsoft SQL Server, the precision of a decimal fraction is 3 for a DATETIME, i.e., "yyyy-mm-ddThh:mm:ss mmm.

Time zone designators

Time zones in ISO 8601 are represented as local time (with the location unspecified), as UTC, or as an offset from UTC.

Local time (unqualified)

If no UTC relation 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. Even within a single geographic time zone, some local times will be ambiguous if the region observes daylight saving time. It is usually preferable to indicate a time zone (zone designator) using the standard's notation.

Coordinated Universal Time (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 "T0930Z". "14:45:15 UTC" would be "14:45:15Z" or "T144515Z".

The ''Z'' suffix in the ISO 8601 time representation is sometimes referred to as "Zulu time" or "Zulu meridian" because the same letter is used to designate the Zulu time zone. However the ACP 121 standard that defines the list of military time zones makes no mention of UTC and derives the "Zulu time" from the Greenwich Mean Time which was formerly used as the international civil time standard. GMT is no longer precisely defined by the scientific community and can refer to either UTC or UT1 depending on context.

Time offsets from UTC

The UTC offset is appended directly to the time instead of "Z" suffix above; other nautical time zone letters are not used. The offset is applied to UTC to get the civil time in the designated time zone in the format '± h m, '± hmm]', or '± h.

A negative UTC offset describes a time zone west of the prime meridian where the civil time is behind UTC. So the zone designation for New York (on standard time) would be "−05:00","−0500", or "−05".
Conversely, a positive UTC offset describes a time zone east of the prime meridian where the civil time is ahead of UTC. So the zone designation for Cairo will be "+02:00","+0200", or "+02".

A time zone where the civil time coincides with UTC is always designated as positive, though the offset is zero (see related specifications below). So the zone designation for London (on standard time) would be " +00:00", " +0000", or " +00".

=Additional examples

=
* " −10:00" for Honolulu
* " −06:00" for Chicago on standard time, or Denver on daylight saving time
* " −03:00" for Brasília
* " +01:00" for London on British Summer Time
* " +04:00" for Dubai
* " +05:30" for India
* " +09:00" for Japan
See List of UTC offsets for other UTC offsets.

=Other time offset specifications

=
It is not permitted to state a zero value time offset with a negative sign, as "−00:00", "−0000", or "−00". The section dictating sign usage states that a plus sign must be used for a positive or zero value, and a minus sign for a negative value. A plus-minus-sign () may also be used if it is available.

Contrary to this rule, RFC 3339, which is otherwise a profile of ISO 8601, permits the use of "−00" with the same denotation as "+00" but a differing connotation: an unknown UTC offset.

To represent a negative offset, ISO 8601 specifies using a minus sign (). If the interchange character set is limited and does not have a minus sign character, then the hyphen-minus should be used (). ASCII does not have a minus sign, so its hyphen-minus character (code 45₁₀) would be used. If the character set has a minus sign, such as in Unicode, then that character should be used. The HTML character entity invocation for is −.

ISO 8601-2:2019 allows for general durations for time offsets. For example, more precision can be added to the time offset with the format '± h m s ss or '± ' as below.

Combined date and time representations

A single point in time can be represented by concatenating a complete date expression, the letter ''"T"'' as a delimiter, and a valid time expression. For example, . In ISO 8601:2004 it was permitted to omit the ''"T"'' character by mutual agreement as in , but this provision was removed in ISO 8601-1:2019.
Separating date and time parts with other characters such as space is not allowed in ISO 8601, but allowed in its profile RFC 3339.

If a time zone designator is required, it follows the combined date and time. For example, or .

Either basic or extended formats may be used, but both date and time must use the same format. The date expression may be calendar, week, or ordinal, and must use a complete representation. The time may be represented using a specified reduced precision format.

Durations

Durations define the amount of intervening time in a time interval and are represented by the format P T or P as shown on the aside. In these representations, the is replaced by the value for each of the date and time elements that follow the 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 (for ''period'') placed at the start of the duration representation.
**''Y'' is the year designator that follows the value for the number of calendar years.
**''M'' is the month designator that follows the value for the number of calendar 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 calendar 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. However, at least one element must be present, thus "P" is not a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however, are both valid and represent the same duration.

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. This decimal fraction may be specified with either a comma or a full stop, as in "P0,5Y" or "P0.5Y". 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. But keep in mind that "PT36H" is not the same as "P1DT12H" when switching from or to Daylight saving time.

Alternatively, 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 . For example, the first duration shown above would be . However, individual date and time values cannot exceed their moduli (e.g. a value of 13 for the month or 25 for the hour would not be permissible).

The standard describes a duration as part of time intervals, which are discussed in the next section. The duration format on its own is ambiguous regarding the total number of days in a calendar year and calendar month. The number of seconds in a calendar day is also ambiguous because of leap seconds. For example "P1M" on its own could be 28, 29, 30, or 31 days. There is no ambiguity when used in a time interval. Using example "P2M" duration of two calendar months:

* interval 2003-02-15T00:00:00Z/P2M ends two calendar months later at 2003-04-15T00:00:00Z which is 59 days later
* interval 2003-07-15T00:00:00Z/P2M ends two calendar months later at 2003-09-15T00:00:00Z which is 62 days later
The duration format (or a subset thereof) is widely used independent of time intervals, as with the Java 8 Duration class which supports a subset of the duration format.

Time intervals

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:

#Start and end, such as "2007-03-01T13:00:00Z/2008-05-11T15:30:00Z"
#Start and duration, such as "2007-03-01T13:00:00Z/P1Y2M10DT2H30M"
#Duration and end, such as "P1Y2M10DT2H30M/2008-05-11T15:30:00Z"
#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 (more commonly referred to as a forward slash "/"). Section 3.2.6 of ISO 8601-1:2019 notes that "A solidus may be replaced by a double hyphen --"by mutual agreement of the communicating partners", and previous versions used notations like "2000--2002". Use of a double hyphen instead of a solidus allows inclusion in computer filenames; in common operating systems, a solidus is a reserved character and is not allowed in a filename.

For / 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 shown as "2007-12-14T13:30/15:30", where "/15:30" implies "/2007-12-14T15:30" (the same date as the start), or the beginning and end dates of a monthly billing period as "2008-02-15/03-14", where "/03-14" implies "/2008-03-14" (the same year as the start).

If greater precision is desirable to represent the time interval, then more time elements can be added to the representation. An interval denoted can start at any time on and end at any time on , whereas includes the start and end times.
To explicitly include all of the start and end dates, the interval would be represented as .

Repeating intervals

Repeating intervals are specified in clause "4.5 Recurring time interval". They are formed by adding "R " to the beginning of an interval expression, where ''R'' is used as the letter itself and is replaced by the number of repetitions. Leaving out the value for or specifying a value of -1, means an unbounded number of repetitions. A value of 0 for means the interval is not repeated.

If the interval specifies the start (forms 1 and 2 above), then this is the start of the repeating interval. If the interval specifies the end but not the start (form 3 above), then this is the end of the repeating interval. For example, to repeat the interval of "P1Y2M10DT2H30M" five times starting at , use .

Truncated representations (deprecated)

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 as well as the ambiguous formats YY-MM-DD and YYMMDD. This provision was removed in ISO 8601:2004.

The first and seventh examples given above omit the leading - for century. Other formats have one leading - per omitted century, year, month, week, hour and minute as necessary to disambiguate the format.

Standardised extensions

ISO 8601-2:2019 defines a set of standardised extensions to the ISO 8601 date and time formats.

Extended Date/Time Format (EDTF)

The EDTF is given as an example of a profile of ISO 8601 in Part 2. It comes in three levels, where level 0 is a subset of Part 1 restricted to extended month-day notation, CCYY-MM-DD, similar to RFC 3339, and levels 1 and 2 build upon that.

EDTF is mostly tailored to bibliographic and historiographic needs. Some of its features are:
* Uncertain and approximate qualifiers, '?' and '~', as well as their combined used, '%'; they can be applied to the whole date or to individual components.
* Time intervals with an open (unbounded) or unknown end or start, e.g. "../2025" or "2024/".
* Exponential ('E') and significant figure ('S') notation in years with a new 'Y' prefix, e.g. "Y-1.25E6S2".
* Special "month" values indicating sub-year groupings such as seasons and quarters, e.g. "2025-26" for summer in the Northern hemisphere.
* Syntax for serializing a list of dates within brackets '[]' for single choices or braces '' for inclusive lists.

The EDTF features are described in the "Date and Time Extensions" section of ISO 8601-2:2019, and the profile itself is found as Annex A. It is virtually identical to the prior specification pioneered by the US Library of Congress.

Repeat rules for recurring time intervals

ISO 8601-2:2019 also defines a format to constrain repeating intervals based on syntax from iCalendar, i.e. IETF RFC 5545.

Implementations

GNU CoreUtils's date command has implement a
--iso-8601 option
among other formating patterns:

$ date --iso-8601=ns

2025-02-16T12:03:17,646296349+01:00

$ date -u --rfc-3339=ns

2025-02-16 10:58:44.966864492+00:00

$ date -u +"%Y-%m-%dT%H:%M:%S.%6NZ"

2025-02-16T10:58:44.965071Z

Usage

On the Internet, the World Wide Web Consortium (W3C) uses the IETF standard based on ISO 8601 in defining a profile of the standard that restricts the supported date and time formats to reduce the chance of error and the complexity of software. The very simple specification is based on a draft of the RFC 3339 mentioned below.

ISO 8601 is referenced by several specifications, but the full range of options of ISO 8601 is not always used. For example, the various electronic program guide standards for TV, digital radio, etc. use several forms to describe points in time and durations. The ID3 audio meta-data specification also makes use of a subset of ISO 8601.
The X.690 encoding standard's GeneralizedTime makes use of another subset of ISO 8601.

Commerce

As of 2006, the ISO week date appears in its basic form on major brand commercial packaging in the United States. Its appearance depended on the particular packaging, canning, or bottling plant more than any particular brand. The format is particularly useful for quality assurance, so that production errors can be readily traced.

RFCs

IETF RFC 3339 defines a profile of ISO 8601 for use in Internet protocols and standards. It explicitly excludes durations and dates before the common era. The more complex formats such as week numbers and ordinal days are not permitted.

RFC 3339 deviates from ISO 8601 in allowing a zero time zone offset to be specified as "-00:00", which ISO 8601 forbids. RFC 3339 intends "-00:00" to carry the connotation that it is not stating a preferred time zone, whereas the conforming "+00:00" or any non-zero offset connotes that the offset being used is preferred. This convention regarding "-00:00" is derived from earlier RFCs, such as RFC 2822 which uses it for timestamps in email headers. RFC 2822 made no claim that any part of its timestamp format conforms to ISO 8601, and so was free to use this convention without conflict.

Building upon the foundations of RFC 3339, the IETF introduced the Internet Extended Date/Time Format (IXDTF) in RFC 9557. This format extends the timestamp representation to include additional information such as an associated time zone name. The inclusion of time zone names is particularly useful for applications that need to account for events like daylight saving time transitions. Furthermore, IXDTF maintains compatibility with pre-existing syntax for attaching time zone names to timestamps, providing a standardized and flexible approach to timestamp representation on the internet. Example:

1996-12-19T16:39:57-08:00 merica/Los_Angeles/code>


Adoption as national standards

See also

*Astronomical year numbering
*Date and time representation by country
* List of date formats by country
* Chronometry
* ISO 8601 and computing differences between dates on Wikiversity

Notes and references

External links

ISO's catalog entry for ISO 8601:2004

Preview of ISO 8601-1:2019
from ISO

Preview of ISO 8601-2:2019
from ISO

The 2016 prototype of ISO 8601-1 (ISO/TC 154 N) (archived)

The 2016 prototype of ISO 8601-2 (ISO/TC 154 N) (archived)

Use international date format (ISO) – Quality Web Tips
The World Wide Web Consortium (W3C)


by Dr. Markus Kuhn from Cambridge University
*

The Mathematics of the ISO 8601 Calendar
from the website of R.H. van Gent of Utrecht University

W3C "NOTE": Date and Time Formats
specifying a profile of ISO 8601:1988

RFC 3339 vs ISO 8601
— Venn diagram illustrating the difference between the two standards.

Implementation overview

ISO 8601 Implementation Around The World (1998)

{{ISO standards

Calendaring standards
Date and time representation
#08601
Specific calendars
Time measurement systems