Thank you Randall - I have been saying this for ages
It is worth elaborating on this for the hard of thinking...
- We write numbers with the most signifcant parts on the left, even in languages that write right-to-left (I think), so, for example, the number 123 has the hundreds left (100) then the tens (20) and then the units (3). So writing dates in the same order makes sense with year, then month, then date. One could, perhaps, argue that people say "27th February, 2013" and so you should write it that way around, but people are inconsistent, e.g. "February 27th, 2013", and so on. Also, people say "Half past 2" but we know to write times logically as HH:MM:SS.
- There are lots of good reasons to write dates and times with leading zeros as it makes them the same size and line up and so on, so using 02 for Feburary not 2. 2013-2-27 would be messy. It also breaks the following point...
- Using dates in this format you can sort dates alphabetically and get date order. Putting time HH:MM:SS on the right means you can sort date/times.
- This is the format used by SQL
- Y2K has taught us to put a year in full is way better
- Putting a year in full means you know which of the three fields is the year and so immediately know this is not either the "UK" format (DD/MM/YY) or the "US" format (MM/DD/YY) and so avoid any confusion - it has to be ISO format as nobody does YYYY-DD-MM (not even in one of Randall's examples).