DD/MM/YYYY also makes no sense because it doesn’t sort lexicographically and each component is big endian but the overall date is little endian.
Only YYYY/MM/DD HH24:MI:SS makes sense. Choose your sepators.
Only YYYY/MM/DD HH24:MI:SS makes sense. Choose your sepators.
YYYY/MM/DD HH:MM:SS has its place as well, but not here.
How do you write the year? Do you put decade before century?
How do you write numbers? Do you put the ones place before the tens?
Toddmorey asked why units don’t go from small to large and I explained that it is inconsistent with how we write numbers.
Thus, there’s no logical reason to do anything other than large to small. Anything other than ISO 8601 is preferred only for familiarity and no such inconsistent format is inherently more correct or logical.
No, because the seconds are rarely important.
>How do you write the year? Do you put decade before century?
No, because that's not how numbers work.
>How do you write numbers? Do you put the ones place before the tens?
Same answer.
>Toddmorey asked why units don’t go from small to large and I explained that it is inconsistent with how we write numbers.
Dates aren't numbers. There is a lot more context and meaning around dates that we need to consider when we verbalise and write them. But, for the purposes of e.g. data storage then absolutely - we can consider them no different from numbers. You have to understand that isn't the case with conversational English, though.
Yes, conversational english is arbitrary. The preference there is the familiar so the listener understands. But both commonly used date formats (MM/DD/YYYY HH:MI:SS and DD/MM/YYYY HH:MI:SS) are inconsistent and arbitrary. You can’t say one makes more sense than the other because that’s just a matter of personal familiarity.
If you need sorting, use a tool that understands dates, simple as that. Many tools do, just some common businesss microsoft tools don't.
Humans think day/month or month/day, they have absolutely no interest in reading the year first.
But this is a conversation about text formatting of dates. The standards for this are well established. Yes, padding is required and assumed.
> Humans think day/month or month/day, they have absolutely no interest in reading the year first.
Humans prefer what is familiar. Speaking as a human, for me that’s ISO 8601.
No need. ISO 2014 was recommended in 1971 and issued in 1973.
If you have chosen any other textual representation of date and time for data interchange you are in a very literal sense doing it wrong.
Hand-written accounting journals, day books, have date ordering built into their physical substrate. It didn't matter how dates were given orally (some places: "today is the 23rd of June 1844"; others: "it's June 23, 1844 today"); nor did it matter that this ordering was transcribed onto the paper, using month numbers rather than the names of the months.
Now we do need to sort dates, so let's turn Japanese.
1. https://en.wikipedia.org/wiki/Date_and_time_notation_in_Japa...