4 ms·

RFC3339. ISO 8601 allows for 2 or 6 digit years. Truncating to 2 is just incorrect, and 6 digits is absurd. And you can read the RFC without paying ISO - and y

RFC3339. ISO 8601 allows for 2 or 6 digit years. Truncating to 2 is just incorrect, and 6 digits is absurd. And you can read the RFC without paying ISO - and you can discuss the RFC with people who have also read it instead of relying on people using the Wikipedia page to interpret and explain ISO 8601. I have a scheduling service at work and I keep getting requests for implementing ISO 8601 timestamps but I ignore them. RFC3339 is the way forward.

account42 1y ago
Plus RFC3339 allows you to use a space instead of the ugly T delimiter between the date and time.
jcul 1y ago
There's this handy venn diagram that I've seen floating around for a long time. Just found a random link to it with an image search: https://gyazo.com/d8517f72e24c38f055e17182842b991c/max_size/1000 https://gyazo.com/d8517f72e24c38f055e17182842b991c/max_size/... ISO 8601 does have some strange formats...
- badmintonbaseba 1y ago
  That's a screenshot of this website: https://ijmacd.github.io/rfc3339-iso8601/ https://ijmacd.github.io/rfc3339-iso8601/
  - jcul 1y ago
    Thanks! That's where I remember it from.
- skissane 1y ago
  > ISO 8601 does have some strange formats... Not that I’ve ever really had cause to use it in anger, but I like the idea of ISO week dates. Effectively, the ISO weak year (often differs from the calendar year in the last week of December / first week of January), ISO week number and day of week form a leap week calendar - instead of having 365 days in a common year and 366 in a leap year, it has 364 days in a common year and 371 in a leap week year, with leap weeks (obviously) being less frequent than leap days. The Sym454 calendar [0] takes this idea further to create a perpetual calendar, with 12 months of 4 or 5 weeks; in leap years the 12th month is 5 weeks instead of 4 weeks long. However, the leap week rule proposed by Sym454 is different from that proposed by ISO 8601; the author of Sym454 argues his proposed rule has theoretical advantages (simple calculation and more uniform distribution of leap weeks). That said, there is a variant of Sym454 which uses the ISO 8601 leap week rule. [0] https://kalendis.free.nf/symmetry.htm?i=1 https://kalendis.free.nf/symmetry.htm?i=1
Y_Y 1y ago
I believe two-digit years haven't been allowed for a while: > 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. (That's from https://en.wikipedia.org/wiki/ISO_8601 https://en.wikipedia.org/wiki/ISO_8601 - I don't have the standards handy, ironically.) Honestly I'm happy with either the RFC or ISO, but it seems like most normies haven't heard of RFCs so ISO is my default.
- fnord123 1y ago
  I believe you. But I haven't paid ISO for the pleasure of reading the actual spec so that passed me by.
deleted 1y ago
[deleted]
realaleris149 1y ago
> 6 digit years Totally insufficient for capturing important future events like the dead of the sun.

account42 1y ago

Plus RFC3339 allows you to use a space instead of the ugly T delimiter between the date and time.

jcul 1y ago

There's this handy venn diagram that I've seen floating around for a long time. Just found a random link to it with an image search: https://gyazo.com/d8517f72e24c38f055e17182842b991c/max_size/1000 https://gyazo.com/d8517f72e24c38f055e17182842b991c/max_size/... ISO 8601 does have some strange formats...

badmintonbaseba 1y ago
That's a screenshot of this website: https://ijmacd.github.io/rfc3339-iso8601/ https://ijmacd.github.io/rfc3339-iso8601/
- jcul 1y ago
  Thanks! That's where I remember it from.
skissane 1y ago
> ISO 8601 does have some strange formats... Not that I’ve ever really had cause to use it in anger, but I like the idea of ISO week dates. Effectively, the ISO weak year (often differs from the calendar year in the last week of December / first week of January), ISO week number and day of week form a leap week calendar - instead of having 365 days in a common year and 366 in a leap year, it has 364 days in a common year and 371 in a leap week year, with leap weeks (obviously) being less frequent than leap days. The Sym454 calendar [0] takes this idea further to create a perpetual calendar, with 12 months of 4 or 5 weeks; in leap years the 12th month is 5 weeks instead of 4 weeks long. However, the leap week rule proposed by Sym454 is different from that proposed by ISO 8601; the author of Sym454 argues his proposed rule has theoretical advantages (simple calculation and more uniform distribution of leap weeks). That said, there is a variant of Sym454 which uses the ISO 8601 leap week rule. [0] https://kalendis.free.nf/symmetry.htm?i=1 https://kalendis.free.nf/symmetry.htm?i=1

Y_Y 1y ago

I believe two-digit years haven't been allowed for a while: > 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. (That's from https://en.wikipedia.org/wiki/ISO_8601 https://en.wikipedia.org/wiki/ISO_8601 - I don't have the standards handy, ironically.) Honestly I'm happy with either the RFC or ISO, but it seems like most normies haven't heard of RFCs so ISO is my default.

fnord123 1y ago
I believe you. But I haven't paid ISO for the pleasure of reading the actual spec so that passed me by.

deleted 1y ago

[deleted]

realaleris149 1y ago

> 6 digit years Totally insufficient for capturing important future events like the dead of the sun.