-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Standardize on a single format of the date/time values with a time zone specified. #135
Comments
My recommendation/ask is to convert all date/time fields to be explicitly in the |
Two action items from today's AWG meeting for @jayjacobs:
Please link both issues here as well so we can conclude the discussion in this issue. Thank you! |
Open issues for related teams (the cve-services already had a very similar issue opened, so pushing that one forward). CVE Services: CVEProject/cve-services#1274 |
Currently date/time is represented as 8 different formats in the data, with 66.3% of all specified date/time fields not specifying a timezone.
Many of the variations are from older CVEs, but even in the last few years there are multiple date/time fields with a variety of formats:
The schema currently has two different date/time objects specified, the "datestamp" and "timestamp", but it appears the "timestamp" is the only one referenced and used. It states, "If timezone offset is not given, GMT (+00:00) is assumed." It's fine to not expect the CNA to always specify it, but it should default to UTC (the "Z" in the current formats represent UTC not GMT), AND the timezone should be set for the CNA if not supplied.
I propose that new date/time values be corrected to always have a timezone, and older stored date/time values are updated to a single format and all include a timezone.
The text was updated successfully, but these errors were encountered: