RFC 3339 vs. ISO 8601
It&#x27;s &quot;funny&quot; how both RFC 3339 and ISO 8601 standards include a huge number of redundant DT formats with often overlapping purposes, yet &quot;2023-09-01 15:30:59&quot;, which is by far most used DT format (because it&#x27;s fucking obvious!) across all systems is included in neither.<p>Also, both standards are very unclear on how to represent DTs BC, and how to represent DTs after 9999-12-31 (or before -9999-01-01), and most commonly used libraries often just cannot handle them at all. And even when they can, the behavior of 00-01-01 is basically undefined (may I remind you, that Gregorian calendar is stupid, and the next year after 1 BC is 1 CE). In short, basically no software except for specialized astronomical software handles anything beyond near-future unix-time, even though for most purposes (like, uniformly representing DOB&#x2F;DOD of Emperor Augustus) it&#x27;s really not rocket science (we are really ok with just storing strings) and just needs to be clearly defined in some standard!