The date format should support different timezone and Daylight saving issues.

  • 2
    please add context info: programminglanguage / database-system / type of api / usecase – k3b Apr 17 '18 at 14:00
  • 2
    See ISO 8601 and RFC 3339 – mouviciel Apr 17 '18 at 14:02

ISO8601. It's not just "preferable", it should be the only format you consider.

| improve this answer | |
  • 1
    without an explanation, this answer may become useless in case if someone else posts an opposite opinion. For example, if someone posts a claim like "Abstain of ISO8601. It's not just not "preferable", it should be the only format you ignore.", how would this answer help reader to pick of two opposing opinions? Consider editing it into a better shape, to meet How to Answer guidelines – gnat Apr 17 '18 at 14:53
  • 3
    @gnat Given that the opposing answer would be heavily down-voted, it would remain clear to future visitors to this question which was the “correct” answer. I answer the question. Additional words would just be waffle. – David Arno Apr 17 '18 at 15:14
  • as far as I can tell moderators at this site tend to delete answers that appear like voting-based popularity contest, see eg Top answers duplicated on community wiki question – gnat Apr 17 '18 at 15:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.