This is basically why I ended up rolling my own text date format for Concise Encoding: - https://github.com/kstenerud/concise-encoding/blob/master/cte-specific

This is basically why I ended up rolling my own text date format for Concise Encoding: - https://github.com/kstenerud/concise-encoding/blob/master/cte-specification.md#temporal-types https://github.com/kstenerud/concise-encoding/blob/master/ct... - https://github.com/kstenerud/concise-encoding/blob/master/ce-structure.md#temporal-types https://github.com/kstenerud/concise-encoding/blob/master/ce... e.g. 2019-8-5 // August 5, 2019 5081-03-30 // March 30, 5081 -300-12-21 // December 21, 300 BC (proleptic Gregorian) 20-01-01 // January 1, 20 (NOT 1920, NOT 2020) 09:04:21 // 9:04:21 UTC 23:59:59.999999999 // 23:59:59 and 999999999 nanoseconds UTC 12:05:50.102/Z // 12:05:50 and 102 milliseconds UTC 4:00:00/Asia/Tokyo // 4:00:00 Tokyo time 17:41:03/-13.54/-172.36 // 17:41:03 Samoa time 9:00:00/L // 9:00:00 local time 2019-01-23/14:08:51.941245 // January 23, 2019, at 14:08:51 and 941245 microseconds, UTC 1985-10-26/01:20:01.105/M/Los_Angeles // October 26, 1985, at 1:20:01 and 105 milliseconds, Los Angeles time 5192-11-01/03:00:00/48.86/2.36 // November 1st, 5192, at 3:00:00, at whatever is in the place of Paris at that time 1985-10-26/01:20:01.105+0700 // October 26, 1985, at 1:20:01 and 105 milliseconds, UTC+7:00 2000-01-14/10:22:00-0200 // January 14, 2000, at 10:22, UTC-2:00 ISO 8601 and RFC 3339 are fine for dates in the recent past, but they're not great as a general time format.