you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago (1 child)

No idea what you based those claims on, but the spec itself (I have the pdf) and Wikipedia's summary disagree. ISO8601 allows for YYY-MM-DD yes but it allows for a bunch of silly stuff.

https://en.m.wikipedia.org/wiki/ISO_8601

Both "2025-W24-4" and "2025‐163" are valid representations of today's date in ISO8601.

(Also the optional timezone makes it utterly useless.)

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    The omitting of timezones doesn't matter to a vast majority of the world, since most countries only have one time zone so I don't see a reason why that is relevant in most use cases.

    ISO is a general standard, it's in the name and the RFC is created for the internet, that is also in the name/description of the RF.

    Using 2025-164 can be handy, I actually use the day of the year to check what invoices from previous year are open since those are the invoices that are due 164 days or more.

  • source
  • parent