zlacker

Most often I see this as an example of ISO 8061 date, https://www.iso.org/iso-8601-date-and-time-format.html .

"Looking for an unambiguous calendar-and-clock format that is internationally understood? It’s time for ISO 8601."

"ISO 8601 tackles this uncertainty by setting out an internationally agreed way to represent dates:

YYYY-MM-DD

For example, September 27, 2012 is represented as 2012-09-27."

>>avmich+(OP)
Yes, yes, yes, please use ISO 8601! Big-endian is the only rational way to sort dates and it combines nicely with time-of-day as well.

>>avmich+(OP)
Yep. Although I don’t use ISO8601 for time stamps when communicating online (for 2021-03-01T00:00Z is more confusing to me than 2021-03-01 16:00 PST8PDT), it’s easier to use for dates when discussing in an online forum where people may be from outside of the US.

>>sargun+kh
nit: ISO8601 permits offsets: you don't need to always use UTC/Z. 2021-03-01T16:00-0800 works just fine.

>>grzm+Sh
I can’t remember the time zone offset between PST and PDT, and when the switch happens.

>>titzer+y7
Big endian is also much easier to read as someone who reads from left to right.

>>sargun+cr
Well, I'm with you there :) I'm all for getting rid of twice-yearly (biannual? semi-annual? perhaps hemi-annual?) offset changes!