• ISO 8601 is paywalled
  • RFC allows a space instead of a T (e.g. 2020-12-09 16:09:…) which is nicer to read.
  • treadful@lemmy.zip
    link
    fedilink
    English
    arrow-up
    17
    ·
    11 months ago

    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@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      11 months ago

      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
    • EnderMB@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      11 months 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.

    • baltakatei@sopuli.xyz
      link
      fedilink
      arrow-up
      2
      ·
      11 months ago

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