this post was submitted on 12 Dec 2023
636 points (95.2% liked)

Memes

45894 readers
1475 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 
  • ISO 8601 is paywalled
  • RFC allows a space instead of a T (e.g. 2020-12-09 16:09:...) which is nicer to read.
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 24 points 1 year ago (4 children)

ISO 8601 also allows for some weird shit. Like 2023-W01-1 which actually means 2022-12-31. There's a lot of cruft in that standard.

[–] SirQuackTheDuck 8 points 1 year ago (1 children)

Doesn't the ISO also includes time periods? Because if it does, those are amazing.

Without any explanation, you should be able to decypher these periods just by looking at them:

  • P1Y
  • P6M2D
  • P1DT4H
  • PT42M
[–] [email protected] 1 points 1 year ago (1 children)

Hmm I don't get the T there tbh

[–] SirQuackTheDuck 1 points 1 year ago (1 children)

It makes the difference between M meaning month or M meaning minute. Small differences.

[–] [email protected] 1 points 1 year ago (1 children)

So it's redundant in P1DT4H? Or is it a mandatory separator between ymd and hms?

[–] SirQuackTheDuck 1 points 1 year ago

It's mandatory, which also makes it nice and predictable.

[–] EnderMB 8 points 1 year ago

This is the killer for me. Most people promote ISO 8601 as a "definitive" date structure, when it actually supports a lot of different formats. What they actually want is usually RFC 3339.

[–] [email protected] 3 points 1 year ago

Week numbers are convenient for projects in which key delivery dates are often expressed in his many weeks out they are.

[–] [email protected] 2 points 1 year ago

wtf what is that gross