# Backport to support RFC 3339 in Date parsing **URL:** \ **Category:** 💡 Ideas\ **Tags:** temporal\ **Created:** [September 19, 2022, 12:00pm UTC](https://es.discourse.group/t/backport-to-support-rfc-3339-in-date-parsing/1463 "2022-09-19T12:00:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![graphemecluster](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/graphemecluster/32/957_2.png) [@graphemecluster](https://es.discourse.group/u/graphemecluster)\ **Post date:** [September 19, 2022, 12:00pm UTC](https://es.discourse.group/t/backport-to-support-rfc-3339-in-date-parsing/1463/1 "2022-09-19T12:00:39Z")
Temporal already supports using a space instead of a T as a separator between date and time ([Temporal#DateTimeSeparator](https://tc39.es/proposal-temporal/#prod-DateTimeSeparator)), as per the RFC 3339 specification. Is it possible to recognize it officially in the Date Spec ([Spec#Date Time String Format](https://tc39.es/ecma262/#sec-date-time-string-format))? (Currently some browsers/engines already support it, but some don’t. I believe the usage of Date will still be predominant in the nearly future, and many SQL databases use RCF 3339 as the default date format.) I am not expecting Date would parse everything Temporal could parse; just supporting the space would be enough, at least for me. ---
**Author:** ![ljharb](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/ljharb/32/8_2.png) [@ljharb](https://es.discourse.group/u/ljharb)\ **Post date:** [September 19, 2022, 4:30pm UTC](https://es.discourse.group/t/backport-to-support-rfc-3339-in-date-parsing/1463/2 "2022-09-19T16:30:15Z")
Unless the majority of browsers support it already, I highly doubt the committee will have an appetite for making any changes to Date whatsoever. If that's the case, a PR to the spec with supporting web reality data would probably be warranted.