ISO 8601 _Data elements and interchange formats – Information interchange – Representation of dates and times_ is an international standard covering the exchange of date and time -related data. It was issued by the International Organization for Standardization (ISO) and was first published in 1988. The purpose of this standard is to provide an unambiguous and well-defined method of representing dates and times, so as to avoid misinterpretation of numeric representations of dates and times, particularly when data are transferred between countries with different conventions for writing numeric dates and times.
In general, ISO 8601 applies to representations and formats of dates in the Gregorian (and potentially proleptic Gregorian ) calendar, times based on the 24-hour timekeeping system (including optional time zone information), time intervals and combinations thereof. The standard does not assign any specific meaning to elements of the date/time to be represented; the meaning will depend on the context of its use. In addition, dates and times to be represented cannot include words with no specified numerical meaning in the standard (e.g., names of years in the Chinese calendar ) or that do not use characters (e.g., images, sounds).
In representations for interchange, dates and times are arranged so the largest temporal term (the year) is placed to the left and each successively smaller term is placed to the right of the previous term. Representations must be written in a combination of Arabic numerals and certain characters (such as "-", ":", "T", "W", and "Z") that are given specific meanings within the standard; the implication is that some commonplace ways of writing parts of dates, such as "January" or "Thursday", are not allowed in interchange representations.
Date and time (current at page generation, purge ? to refresh) expressed according to ISO 8601:
Combined date and time in UTC : 2017-07-31T00:18:30+00:00 2017-07-31T00:18:30Z 20170731T001830Z
Date with week number: 2017-W31-1
Date without year: --07-31
Ordinal date: 2017-212
* 1 History * 2 General principles
* 3 Dates
* 4 Times
* 4.1 Time zone designators
* 5 Combined date and time representations * 6 Durations
* 7 Time intervals
* 7.1 Repeating intervals
* 8 Truncated representations * 9 Usage * 10 Related standards * 11 See also * 12 Notes and references * 13 External links
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 and by the current third edition _ISO 8601:2004_ published on 1 December 2004. 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.
* 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. 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 formats – a basic format with a minimal number of separators or an extended format with separators added to enhance human readability. 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 "2009-01-06" in the extended format or simply as "20090106" in the basic format without ambiguity. * 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 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.
July 2017 WEEK MON TUE WED THU FRI SAT SUN
W26 26 27 28 29 30 01 02
W27 03 04 05 06 07 08 09
W28 10 11 12 13 14 15 16
W29 17 18 19 20 21 22 23
W30 24 25 26 27 28 29 30
W31 31 01 02 03 04 05 06
The standard uses the Gregorian calendar , which serves as an international standard for civil use.
ISO 8601 fixes a reference calendar date to the Gregorian calendar of 20 May 1875 as the date the _Convention du Mètre_ ( Metre Convention ) 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. The standard states that every date must be consecutive, so usage of the Julian calendar would be contrary to the standard (because at the switchover date, the dates would not be consecutive).
ISO 8601 prescribes, as a minimum, a four-digit year to avoid the year 2000 problem . It therefore represents years from 0000 to 9999, year 0000 being equal to 1 BC and all others AD . However, years prior to 1583 are not automatically allowed by the standard. Instead "values in the range through shall 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 must 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.
YYYY-MM-DD _or_ YYYYMMDD
YYYY-MM (_but not_ YYYYMM)
--MM-DD _or_ --MMDD
Calendar date representations are in the form shown in the adjacent box. indicates a four-digit year, 0000 through 9999. indicates a two-digit month of the year, 01 through 12. indicates a two-digit day of that month, 01 through 31. For example, "5 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". The 2000 version allowed writing "--04-05" to mean "April 5" but the 2004 version does not allow omitting the year when a month is present. One may simply write "1981" to refer to that year or "19" to refer to the century from 1900 to 1999 inclusive. Although the standard allows both the YYYY-MM-DD and YYYYMMDD formats for complete calendar date representations, if the day 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).
Main article: ISO week date
YYYY-Www _or_ YYYYWww
YYYY-Www-D _or_ YYYYWwwD
Week date representations are in the format as shown in the adjacent box. indicates the _ISO week-numbering year_ which is slightly different from the traditional Gregorian calendar year (see below). is 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 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.
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 Friday, Saturday, and Sunday. 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 Monday, Tuesday and Wednesday. The Thursday of each ISO week is always in the Gregorian calendar year denoted by the ISO week-numbering year.
* Monday 29 December 2008 is written "2009-W01-1" * Sunday 3 January 2010 is written "2009-W53-7"
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, indicates a year. 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 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 1 January 4713 BC Greenwich noon, Julian proleptic calendar (or noon on ISO date -4713-11-24 which uses the Gregorian proleptic calendar with a year ).
hh:mm:ss.sss _or_ hhmmss.sss
hh:mm:ss _or_ hhmmss
hh:mm _or_ hhmm
* refers to a zero-padded hour between 00 and 24 (where 24 is only used to denote midnight at the end of a calendar day). * refers to a zero-padded minute between 00 and 59. * refers 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 "134730" in the _basic format_ or "13:47:30" in the _extended format_.
Either the seconds, or the minutes and seconds, may be omitted from the basic or extended time formats for greater brevity but decreased accuracy: :, and are the resulting reduced accuracy time formats.
_ Midnight _ is a special case and may be referred to as either "00:00" or "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". "2007-04-05T24:00" is the same instant as "2007-04-06T00:00" (see _Combined date and time representations _ below).
Decimal fractions may be added to any of the three time elements. However, a fraction may only be added to the lowest order time element in the representation. A decimal mark , either a comma or a dot (without any preference as stated in resolution 10 of the 22nd General Conference CGPM in 2003, but with a preference for a comma according to ISO 8601:2004) is used as a separator between the time element and its fraction. To denote "14 hours, 30 and one half minutes", do not include a seconds figure. Represent it as "14:30,5", "1430,5", "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
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.
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".
Time Offsets From UTC
The offset from UTC is appended to the time in the same way that 'Z' was above, in the form ±:, ±, or ±. 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". To represent a time behind UTC the offset is negative. For example, the time in New York during standard (not daylight saving) hours is UTC−05:00 . For other time offsets see List of UTC time offsets . To represent a negative offset, ISO 8601 specifies using either a hyphen–minus or a minus sign character. 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 is 45 decimal or 2D hexadecimal) would be used. If the character set has a minus sign, then that character should be used. Unicode has a minus sign, and its character code is U+2212 (2212 hexadecimal); the HTML character entity invocation is -.
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. To calculate UTC time one has to subtract the offset from the local time, e.g. for "15:00−03:30" do 15:00 − (−03:30) to get 18:30 UTC.
An offset of zero, in addition to having the special representation "Z", can also be stated numerically as "+00:00", "+0000", or "+00". However, it is not permitted to state it numerically with a negative sign, as "−00:00", "−0000", or "−00". The section dictating sign usage (section 3.4.2 in the 2004 edition of the standard) states that a plus sign must be used for a positive or zero value, and a minus sign for a negative value. 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.
ISO 8601 permits the hyphen (-) to be used as the minus (−) character when the character set is limited. In contrast, RFC 3339 explicitly requires the hyphen (-) symbol to represent negative offsets and does not allow for use of the minus (−) symbol.
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, "2007-04-05T14:30".
If a time zone designator is required, it follows the combined date and time. For example, "2007-04-05T14:30Z" or "2007-04-05T12:30-02:00".
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 accuracy format. It is permitted to omit the 'T' character by mutual agreement.
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 PYMDTHMS or PW as shown to the right. 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 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. 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 P--T::. For example, the first duration shown above would be "P0003-06-04T12:30:05". 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).
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 4.4.2 of the standard notes that: "In certain application areas a double hyphen is used as a separator instead of a solidus." The standard does not define the term "double hyphen", but previous versions used notations like "2000--2002". Use of a double hyphen instead of a solidus allows inclusion in computer filenames . A solidus is a reserved character and not allowed in a filename in common operating systems.
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 simply 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 "2007-11-13/15" can start at any time on 2007-11-13 and end at any time on 2007-11-15, whereas "2007-11-13T09:00/15T17:00" includes the start and end times. To explicitly include all of the start and end dates, the interval would be represented as "2007-11-13T00:00/15T24:00".
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 means an unbounded number of repetitions. 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 "2008-03-01T13:00:00Z", use "R5/2008-03-01T13:00:00Z/P1Y2M10DT2H30M".
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.
On the Internet , the World Wide Web Consortium (W3C) uses 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.
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 timezone 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 timezone, 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.
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 Generalized Time makes use of another subset of ISO 8601.
The ISO 8601 week date , as of 2006, appeared 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 to work weeks, and products can be correctly targeted for recall.
AUSTRALIA AS ISO 8601-2007
AUSTRIA ÖNORM ISO 8601 (replaced ÖNORM EN 28601)
BELGIUM NBN EN 28601 (1993)
BRAZIL NBR 5892:1989
CANADA CSA Z234.5:1989
COLOMBIA NTC 1034:2014 Source ICONTEC (This standard is identical to ISO 8601:2004)
CHINA GB/T 7408-2005
CZECH REPUBLIC ČSN ISO 8601 (replaced ČSN EN 28601)
DENMARK DS/ISO 8601:2005 (replaced DS/EN 28601)
EUROPEAN NORM EN ISO 8601, EN 28601:1992 (cancelled 7 October 2011)
FINLAND SFS-EN 28601
FRANCE NF Z69-200; NF EN 28601:1993-06-01 (cancelled)
GERMANY DIN ISO 8601:2006-09 (replaced DIN EN 28601:1993-02); related: DIN 5008:2011-04 (replaced DIN 5008:2005-05, DIN 5008:2001-11, DIN 5008:1996-05)
GREECE ELOT EN 28601
HUNGARY MSZ ISO 8601:2003
ICELAND IST EN 28601:1992
INDIA IS 7900:2001
IRELAND IS/EN 28601:1993
ITALY UNI EN 28601 (1993)
JAPAN JIS X 0301:2002
KOREA, REPUBLIC OF KS X ISO 8601
LATVIA Ministru kabineta noteikumi Nr.916
LITHUANIA LST ISO 8601:2006 (replaced LST ISO 8601:1997)
LUXEMBOURG ITM-EN 28601
NETHERLANDS NEN ISO 8601, NEN EN 28601 (1994), NEN 2772
NORWAY NS-ISO 8601
POLAND PN-90/N-01204 (removed, outdated)
PORTUGAL NP EN 28601
RUSSIA ГОСТ ИСО 8601-2001 (current), ГОСТ 7.64-90 (obsolete)
SOUTH AFRICA SANS 8601:2009
SPAIN UNE EN 28601:1995
SWEDEN SS- ISO 8601 (replaced SS-EN 28601 (1991))
SWITZERLAND SN ISO 8601:2005-08 (replaced SN-EN 28601:1994)
TAIWAN CNS 7648
THAILAND TIS 1111:2535 (1992)
TURKEY TS ISO 8601
UKRAINE ДСТУ ISO 8601:2010
UNITED KINGDOM BS ISO 8601:2004, BS EN 28601 (1989-06-30)
UNITED STATES ANSI INCITS 30-1997 (R2008) and NIST FIPS PUB 4-2
VIETNAM TCVN 6398-1:1998
Media related to ISO 8601 at Wikimedia Commons
NOTES AND REFERENCES
* ^ _A_ _B_ ISO 8601:2004 section 1 Scope * ^ _ISO 8601:2004(E)_, ISO , 2004-12-01, 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. * ^ _ISO 8601:2004(E)_. ISO . 2004-12-01. p. iv Foreword. * ^ TC 154 Processes, data elements and documents in commerce, industry and administration, Technical committees – ISO * ^ _A_ _B_ ISO, FAQ: _Numeric representation of Dates and Time_ * ^ "Date and Time Formats". * ^ ISO 8601:2004 section 2.3.3 basic format * ^ _A_ _B_ _C_ ISO 8601 uses the word _accuracy_, not _precision_, in the relevant section, e.g: 2.3.7 representation with reduced accuracy. * ^ Doggett, L. E. (1992). "Calendars". In P. K. Seidelmann. _Explanatory Supplement to the Astronomical Almanac_. Sausalito, California: University Science Books. p. 580. ISBN 0-935702-68-7 . Archived from the original on 2004-04-01. The Gregorian calendar today serves as an international standard for civil use. * ^ _ISO 8601:2004(E)_. ISO . 2004-12-01. section 188.8.131.52 General. * ^ _ISO 8601:2004(E)_. ISO . 2004-12-01. 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 or after the end of the year . * ^ ISO 8601:2004 sections 3.4.2, 184.108.40.206 * ^ For example, see Annex B.1.1 of the standard. * ^ "RFC 6350 - vCard Format Specification". IETF . August 2011. Retrieved 2016-06-29. Truncated representation, as specified in , Sections 220.127.116.11 d), e), and f), is permitted. * ^ ISO 8601:2004 section 18.104.22.168 Representations with reduced accuracy * ^ "NIST TechBeat 2006-11-22". NIST . 2006-11-22. Retrieved 2012-05-06. Decimals Score a Point on International Standards ... It soon may be possible to write international standards documents with decimal points in them. * ^ _ISO 8601:2004(E)_, ISO , 2004-12-01, 22.214.171.124 ... the decimal fraction shall be divided from the integer part by the decimal sign specified in ISO 31-0, i.e. the comma or full stop . Of these, the comma is the preferred sign. * ^ RFC 3339 – Unknown local offset convention * ^ ISO 8601 §3.4.1 stating, "In an environment where use is made of a character repertoire based on ISO/IEC 646, 'hyphen' and 'minus' are both mapped onto 'hyphen-minus'. Representations with a 'plus-minus' shall only be used in such environment if the interchange repertoire includes 'plus-minus'." * ^ https://tools.ietf.org/html/rfc3339#section-5.6 time-numoffset defined with hyphen symbol * ^ "ISO 8601:2004(E)". ISO . 2004-12-01. 4.3.2 NOTE: By mutual agreement of the partners in information interchange, the character may be omitted in applications where there is no risk of confusing a date and time of day representation with others defined in this International Standard. Missing or empty url= (help ) * ^ ISO 8601:2004 section 126.96.36.199 Alternative format * ^ "Info on ISO 8601, the date and time representation standard". Cs.tut.fi. Retrieved 2012-08-29. * ^ " ISO 8601 - Getting with the Times (and Dates)". Hydrogold. 2012-01-01. Retrieved 2013-08-13. * ^ Note about Date and Time Formats to W3C from Reuters * ^ RFC 3339 , section 5.6 * ^ Nilsson, M. (2000-11-01). " ID3 tag version 2.4.0 - Main Structure". id3.org. pp. §4. Retrieved 2009-09-27.
* ISO\'s catalog entry for ISO 8601:2004 * The