Skip to content

Conversation

legobeat
Copy link

@legobeat legobeat commented Oct 15, 2024

Having the timezone be ambiguous and open to interpretation is not ideal, IMO. Localtime can also be ambiguous. Hence I propose that when timezone information is not provided, the default is changed from localtime to UTC, and switching a SHALL to MUST.

@legobeat legobeat marked this pull request as ready for review October 15, 2024 22:46
@legobeat legobeat requested review from a team, Montoya and ziad-saab as code owners October 15, 2024 22:46
Copy link
Contributor

@hmalik88 hmalik88 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think I agree here. We should treat omitted timezone as UTC and all together not require the Z identifier. Quoting the wiki: "While it may be safe to assume local time when communicating in the same time zone, it is ambiguous when used in communicating across different time zones"

@legobeat
Copy link
Author

Something to consider would be to make the timezone required - this would reduce the likelihood of bugs arising due to incorrect implementations naively using (non-UTC) defaults in some library other than UTC, at the cost of making the Z required for UTC.

@legobeat
Copy link
Author

@Montoya ping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants