• Deestan@lemmy.world
    link
    fedilink
    arrow-up
    14
    ·
    4 days ago

    After all the self-important blowhards in the committe were satisified that they had put their fingerprint on the ISO8601 document with bullshit like “year-month-week” format support and signed off, they went home.

    The rest stayed behind, waited a few minutes to be safe, and then quickly made RFC3339 like a proper standard.

    This is what RFC3339 vs ISO8601 feels like.

    • kata1yst@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      4 days ago

      Let’s not forget that technically you have to pay for ISO8601, despite it being nearly useless as a standard because it allows several incompatible formats to coexist.

      Fucking wild.

      • Deestan@lemmy.world
        link
        fedilink
        arrow-up
        7
        ·
        4 days ago

        While a fucking stupid concept, it’s nice that this particular format has a monetary deterrent.

      • Vinstaal0@feddit.nl
        link
        fedilink
        arrow-up
        1
        ·
        3 days ago

        Only if you want to say you have the certification for it, you can use it if you want, that is fine

    • Vinstaal0@feddit.nl
      link
      fedilink
      arrow-up
      2
      ·
      3 days ago

      ISO8601 is YYYY-MM-DD nothing to do with weeks and isn;t the only difference of RFC3339 that you can use a space instead of a T in between the date and time? Also RFC3339 is only an internet standard while ISO is a generally international standard?