Free versions of the actual specs: https://www.loc.gov/standards/datetime/iso-tc154-wg5_n0038_i... https://www.loc.gov/standards/datetime/iso-tc154-wg5_n0039_i... Or https://www.iso.org/obp/ui/#iso:std:iso:8601:-1:ed-1:v1:en The ISO8601 yyyy-mm-dd format is fine and intuitive. What trips people up all the time is the ISO8601 yyyy-www-d format (year-week-weekday)[1]. People who know it well can appreciate the benefits…
The "week date" format (yyyy-www-d) in ISO8601 is IMHO why it's usually better to refer to RFC3339, which doesn't allow the week date format. So many people are unaware that the ISO8601 format allows "week date" and/or don't understand its quirks, and articles like this one, which don't even mention that ISO8601 dates can appear in this format, compound the problem.
ISO 8601: a better date format
281–290 of 437 posts
Re: ISO 8601: a better date format
#282Re: ISO 8601: a better date format
#283Earlier quoted context omitted.
No. Every human likely encounters date sorting at some point. And feet and inches aren’t really any more human or natural than 4x5x2 dm or 40x50x20cm. Dividing by 10 isn’t more human either, but adding/removing zeroes or moving a decimal point is certainly easier for the human brain.
Is dm used widely wherever you’re located?
Re: ISO 8601: a better date format
#284The article is missing one of the best features of iso 8601: it‘s string form is naturally sortable. You don‘t need any specific logic for sorting, so e.g. your filesystem will automatically sort files correctly if you prefix them with a iso 8601 date.
Re: ISO 8601: a better date format
#285Re: ISO 8601: a better date format
#286The article is missing one of the best features of iso 8601: it‘s string form is naturally sortable. You don‘t need any specific logic for sorting, so e.g. your filesystem will automatically sort files correctly if you prefix them with a iso 8601 date.
Which is a side effect of being consistent with the way we write all other numbers, with the value represented by each digit declining as we go left to right.
Re: ISO 8601: a better date format
#287At the risk of nitpicking, I prefer RFC 3339, which is a profile of ISO 8601. ISO 8601 provides room for things you typically don't want, e.g. dropping time zone offsets. While I'm typing this I realise that I've never actually read the ISO 8601 spec, like probably most people here, because it's not free. I cannot even be sure it really exists.
For me, more significant reason to prefer RFC 3339 constrained profile is that ISO 8601 does not only mean YYYY-MM-DDTHH:MM:SS.sss but also includes bunch of alternate syntaxes like YYYY-DDD. And I have one big issue with RFC3339: there are cases when the "don't care about timezone" ISO 8601 syntax is actually useful.
Re: ISO 8601: a better date format
#288Earlier quoted context omitted.
M/D/Y is a bit like the German way of reading numbers. 328 become three hundred, eight and twenty. Terrible
How about french? 99 is four twenties nineteen, 79 is sixty nineteen. Languages are fun and fascinating.
Re: ISO 8601: a better date format
#289Re: ISO 8601: a better date format
#290Earlier quoted context omitted.
>English has ~1100 million total speakers but only 318 millon native speakers, while Chinese has 918 million native speakers Why would that matter? Arguably the ideal lingua franca should have no native speakers at all as those have an unfair advantage.
> Why would that matter? Arguably the ideal lingua franca should have no native speakers at all as those have an unfair advantage. I share your vision of an explicitly taught universal language which gives no group or individual an unfair advantage. We obviously need more equality in the world. From the perspective of trying to maximize how many people with whom you are able to communicate, however, on a practical ba…