article

--TZ
(when page was sent)
Date and time in UTC

ISO 8601, "Data elements and interchange formats – Information interchange – Representation of dates and times" is an international standard for date and time representations. The signature feature of the ISO 8601 format is that all values are organized from most to least significant. This leads, among others, to the increasingly familiar YYYY-MM-DDThh:mm:ss format seen in international forums.

History of the standard

The first edition of the ISO 8601 standard was published in 1988 and unified and replaced a number of older ISO standards on various aspects of date and time notation: ISO 2014, 2015, 2711, 3307 and 4031. It has since then been superseded by a second edition in 2000 and finally 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.

General principles

Date and time values are organized from most to least significant. Each value (eg, year, month, day, time) has a fixed number of digits which must be padded with leading zeros. For instance, the American notation "4:30 a.m." would be written 04:30. As a result, for each of the several formats of dates and times lexicographical order corresponds to chronological order, except for negative years.

Representation can be done in one of two formats: A basic format with a minimal number of characters, or an extended format with separators to enhance human readability. The standard permits a hyphen separator between date elements, and a colon between hours, minutes, and seconds.[http://lists.ebxml.org/archives/ebxml-core/200104/pdf00005.pdf For example, 2006-01-06 may be written 20060106 without ambiguity. The extended formats are preferred over basic formats because some basic formats are ambiguous.

Any number of fields may be dropped from any of the date and time formats, but the least significant fields must be dropped first. 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.

Finally, the standard supports the addition of a decimal fraction to the smallest time unit, where higher precision is needed.

Dates

The standard uses the leap rule and month sizes of the Gregorian calendar, which is already the de facto standard of international trade.

Years

±YYYY
ISO 8601 prescribes a four-digit year to avoid the year 2000 problem. Years can also be expanded to greater than four digits and then should be preceded by a plus sign (+). Years before the epoch (year zero) are always to be preceded by a minus sign (−).

For purposes of reference ISO 8601 assigns the number 1875 to the year in which the Convention du Mètre was signed in Paris.

Calendar date

YYYY-MM-DD or YYYYMMDD

Calendar dates are the form familiar to most people. As represented above, YYYY indicates a year with century. MM indicates the month of the year, 01 through 12. DD indicates the day of that Julian month, from 01 through 31. For example, "5th of April 1981" may be represented as 1981-04-05 in the extended format, or 19810405 in the basic format.

The standard allows for dates to be written with less precision. For example, you may write 1981-04 to mean "April, 1981". You may simply write 1981 to refer to that year.

The standard also allows for dates which include an implied element, such as an implied century. It is careful to emphasize the importance of clear communication between sender and receiver when implied elements are being used.

Week dates

YYYY-Www-D or YYYYWwwD

A week date specifies a so-called ISO year in the format YYYY, a week number in the format ww prefixed by the letter W, and the weekday number, a digit d from 1 through 7, beginning with Monday and ending with Sunday. This form is popular in manufacturing.

Mutually equivalent definitions for week 01 are:

  • the week with the year's first Thursday in it
  • the week with 4 January in it
  • the first week with the majority (four or more) of its days in the starting year
  • 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.

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

The ISO 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 year number deviates from the number of the normal year (Gregorian year) on, if applicable, a Friday, Saturday, and Sunday, or a Saturday and Sunday, or just a Sunday, at the start of the ordinary year (which are at the end of the previous ISO year) and a Monday, Tuesday and Wednesday, or a Monday and Tuesday, or just a Monday, at the end of the ordinary year (which are in week 01 of the next ISO year). For Thursdays the ISO year number is always equal to the ordinary year number.

Examples:

  • 2008-12-29 is written 2009-W01-1
  • 2010-01-03 is written 2009-W53-7

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 year is needed, while correspondence of lexicographical order and chronological order is preserved.

Ordinal dates

YYYY-DDD or YYYYDDD

Ordinal dates are a simple form for times 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 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 frequently, if incorrectly, referred to as the Julian Date.

Further details about dates

The standard allows for expansion of the year, by agreement between sender and receiver. Expansion means that the year may be written with more than four digits, which addresses the year 10,000 problem, by allowing the standard to specify dates later than AD 10000 or earlier than 10001 BC. Note however that expansion introduces ambiguities if separators are not used. For instance 200406 could either mean the year 200406 or June 2004. The ISO standard suggests that "provisions be made" to prevent such confusions.

Times

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

ISO 8601 uses the 24-hour clock system that is used by much of the world. The basic format is hhmmss 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 date. 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 13:47:30, or 134730.

It is also acceptable to omit elements to reduce precision. hh:mm, hhmm, and hh are all used.

Fractions may also be used with all three of the time elements. These are indicated by using the decimal point (either a comma (which is preferred) or dot). A fraction may only refer to the most precise component of a time representation — that is, to denote "14 hours, 30 and one half minutes", do not include a seconds figure. Represent it as 14:30.5 or 1430.5.

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 the day, and is the most frequently used one. At the end of a day use 24:00. Note that 1981-04-05T24:00 is the same instant as 1981-04-06T00:00.

Time zones

or
or
If no time zone information is given with a time, the time zone is assumed to be in some conventional local timezone. While it may be safe to assume a local zone when used between two people in the same area, it is ambiguous when used in communication between multiple timezones. It is usually preferable to indicate a time zone using the standard’s notation.

UTC
If the time is in UTC, it is very easy to show this. Simply add a Z directly after the time, without a space. "09:30 UTC" is therefore represented as 09:30Z or 0930Z. "14:45:15 UTC" would be 14:45:15Z or 144515Z.

Other time zones
Other time zones are specified by their offset from UTC, in the format ±hh:mm, ±hhmm, or ±hh. So if the time being described is one hour ahead of UTC (such as the time in Berlin during the winter) the offset 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 offset is the actual offset from UTC, and doesn't include any information on daylight saving time. Times expressed in local time for a user in Chicago, Illinois 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.

Combined representations

T

Combining date and time representations is quite simple. It is in the format of T. The and sections are any proper representation of the date and time created by following the standard. A common use could be YYYY-MM-DDThh:mm:ss±hh:mm. 1981-04-05T14:30:30-05:00, for example.

The date and time representations may sometimes appear in proximity, separated by a space or other characters, in which case they occupy two separate fields in a data system, rather than a single combined representation. This is sometimes done for human readability. Unlike the above example, 1981-04-05 14:30:30-05:00 are two separate representations, one for date and the other for time.

Duration

PnYnMnDTnHnMnS
Durations are represented by the format PnYnMnDTnHnMnS (or PnW nW to use the week format.) In this representation replace n with the appropriate number for the element that follows it (leading zeros are optional but may clarify ambiguous durations). The capital letters (P, Y, M, W, D, T, H, M, and S) are used as they are and not replaced. Thus P3Y6M4DT12H30M0S defines "a period of three years, six months, four days, twelve hours, thirty minutes, and zero seconds". Elements may be omitted if their value is zero. To resolve ambiguity, P1M is one month and PT1M is one minute. The smallest value used may also have a decimal fraction, as in P0,5Y to indicate half a year.

Alternately, a format more similar to the combined representation may be used: PYYYY-MM-DDThh:mm:ss. To represent the same duration as above in this format, use P0003-06-04T12:30:00.

Time interval

/
/
/
Time intervals specify an amount of time. They may be specified in four ways:

  1. Start and end, such as 2002-03-01T13:00:00Z/2003-05-11T15:30:00Z
  2. Start and duration, such as 2002-03-01T13:00:00Z/P1Y2M10DT2H30M
  3. Duration and end, such as P1Y2M10DT2H30M/2003-05-11T15:30:00Z
  4. Duration only, such as P1Y2M10DT2H30M

Of these, the first three require two separate values, separated by the interval designator, which is usually a forward slash "/". (The double hyphen (--) is permissible in some applications but is not preferred.) An example using the format from item #1 is 1981-04-05T14:30:30-05:00/2004-07-14T15:30:30-05:00. If any elements are missing from the second value, they are assumed to be the same as the first value, including time zone elements.

Repeating intervals

Repeating intervals are formed by adding Rn/ 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 2002-03-01T13:00:00Z, use R5/2002-03-01T13:00:00Z/P1Y2M10DT2H30M.

Usage

On the Internet, ISO 8601 is used by the W3C, defining a profile of the standard that restricts the supported formats to reduce the chance of error and the complexity of software.Note about Date and Time Formats to W3C from Reuters

RFC 3339 defines a profile of ISO 8601 for the use in Internet protocols and standards. It explicitly excludes durations and dates before the common era. It uses the notation hh:mm:ss-00:00 to indicate an unknown local time zone. The more complex formats like week numbers and ordinal day are indirectly discouraged.

ISO 8601 is referenced by several specifications, but not always is the full range of options of ISO 8601 used. For example the different EPG standards for TV, digital radio etc. do use several formats to describe points in time and durations.

The ISO 8601 week date, as of 2006-01, already appears in its basic form on major brand commercial packaging in the US. Its appearance depends 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 to work weeks, and products can be correctly targeted for recall.

See also

External links

Specific calendars | ISO standards

ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601 | ISO 8601

 

This article is licensed under the GNU Free Documentation License. It uses material from the "ISO 8601".

Home Page • arts • business • computers • games • health • hospitals • home • kids & teens • news • physicians • recreation• reference • regional • science • shopping • society • sports • world