Scott Brim <scott.brim@xxxxxxxxx> wrote: > These technical answers are all great "for use in Internet protocols" > [3339] but the scope of the question is web pages destined for humans to > read and understand ... and some humans don't understand them. You > could justify what's there now and ignore their problem, or (if your > goal is communication) you could figure out how to write dates in ways > that ordinary humans find unambiguous. I usually write something like > "2010 Jan 02". It's not sortable but it's understood even by non-IETFers. I've been using YYYY-MM-DD dates everywhere I can for many years, and the email that opened this thread was the first time I had ever heard of anyone ever finding such a date ambiguous. Given the various advantages of such dates, I think we need to be convinced that there's an actual problem before considering changing them. Humans and scripts often access the same data, BTW. Easy-to-parse dates are advantageous. Matching international standards is also of some value. -- Cos _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf