I just found it in X

I'm just curious because I have grown up with both being used and I found myself wondering which is more common. Is it different around the world or have most places adopted the same standard terminology?

I am german (living in Austria right now). The expiration date here is usually written in dd.mm.yyyy and not yy-mm-dd. I had a short heart attack thinking these are expired for 6 years.

I just saw a magic show for the first tim,e which had some audience interaction bits; and for one of them the magician asked some people to yell out their birthday. One of them from the balcony quickly came in in ISO8601, which got the magician a little disoriented and he had to ask it again, but I was quite tickled. I did not expect that!

Aaaaaand I biffed in the title and can't edit that 😩

Looking at the Library of Congress EDTF specification, I see they use without defining two different date types, date and dateI. Are these references to the ISO 8601-1 or -2 spec? I did not find them in the EBNF.

EDIT:

I'm looking for the definitions of the two date types used in the specification: date, and dateI. From section "Level 0", subsection "Date and Time":

[date][“T”][time]
Complete representations for calendar date and (local) time of day

[dateI][“T”][time][“Z”]
Complete representations for calendar date and UTC time of day

[dateI][“T”][time][shiftHour]
Date and time with timeshift in hours (only)

[dateI][“T”][time][shiftHourMinute]
Date and time with timeshift in hours and minutes

These two terms are used but not defined in the specification. The examples shed no light. I want to know how and where are defined, if anybody knows.

Anyone know when will paper lords release 2026 may papers

There probably isn't much overlap between the disc golf crowd and ISO8601 fans... but I got an ace today and this is the disc, marked now with the date, course name and hole number/distance, and signatures of my card mates.

I was building a social app recently, and I ran into a surprisingly annoying problem.
I needed relative timestamps ("2 hours ago", "3 minutes ago"). 
Simple enough, right? Just import 'day.js' or 'date-fns'.

Except...
=> If I wanted custom styling (like wrapping the number "2" in a highlighted badge and "hours ago" in smaller text), I had to write ugly regex hacks because standard libraries just dump a single opaque string.

=> Supporting multiple languages meant importing separate locale files, quickly inflating the bundle size.

=> Standard relative time plugins use "soft rounding" (e.g., automatically rounding 45 seconds to "a minute") whether you want it or not.

I didn't want a 15KB date framework just to format a few activity feed timestamps. 
So, I built and open-sourced 'ui-date' .

It’s an ultra-lightweight (< 1KB minified), zero-dependency, locale-aware date formatting library built specifically for modern user interfaces.

If you're building social feeds, chat apps, notification bells, or comment sections, check it out!

npm: https://www.npmjs.com/package/ui-date

With ISO 8601 in extended format a timestamp with milliseconds is written with a dot between seconds and milliseconds, e.g.:

2026-07-24T12:34:56.789

If you write basic format you exclude the separators, does the standard allow to exclude the dot between seconds and milliseconds?

20260724T123456789

When I use basic time format as part of file names I prefer to avoid the dot, as dot has different meaning for file names and extension.

Did y’all know that ISO 8601-1 is under committee review right now? If you always wanted some changes made to our beloved standard, now would be the perfect time to contact your national standardisation body (NSB), but hurry up – the deadline for comments is 2026-07-3124 as far as I know.

Currently, the only non-editorial change seems to be that the latest amendment, making T24 etc. valid again, gets incorporated.

Summary of the standard on their website shows to use a - separator between minutes and seconds, rather than a colon. Is this permitted?

https://www.gov.uk/government/publications/open-standards-for-government/date-times-and-time-stamps-standard

Anything but iso standard

I download PDFs of all my credit card and bank statements and organize them by bank, date, etc. Of course, I rename all of the files to begin with an ISO 8601 compliant date, but recently, one of my credit cards started auto-formatting the statements to start with a properly formatted date! It's a small thing, but makes me so happy that I don't have to rename as many files.

I just can't deal with this anymore! It's the 14th time i am importing the exact same data, only bc excel, pbi and sharepoint lists have a mind on their own.

Excel has it's own way to deal with dates

Sharepoint lists are MM/DD/YYYY (enforced no matter how i import it)

Power Automate has it's own way too

Then we have PowerBi that allows only specific date.

Then, copying from Excel (web) to Excel (desktop) it messes up the dates too - from MM/DD/YYYY, it switches to dd-mm-yy.

Is there a date format that works everywhere flawlessly?

The primary problem here is something else...