Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require full ISO 8601 timestamps #6

Open
ivanr opened this issue May 18, 2020 · 0 comments
Open

Require full ISO 8601 timestamps #6

ivanr opened this issue May 18, 2020 · 0 comments

Comments

@ivanr
Copy link

ivanr commented May 18, 2020

[Continuing here from https://github.com/w3c/reporting/issues/209]

One of the fields in deprecation reports is "anticipatedRemoval", defined as "A JavaScript Date object (rendered as an ISO 8601 string)". The example contains "2020-01-01" as a possible value.

ISO 8601 supports many different date, time, and timestamp formats. Deprecation Reporting is vague on exactly which formats can be used. From a report processor perspective, it's onerous to handle everything. I suggest picking only one format.

In my opinion, it's best to use the full timestamp, even for this case when full precision is not required. Just zero-out the unnecessary parts.

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

No branches or pull requests

1 participant