You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the just released 5.1 schema, field timestamp is type string with an unspecified format (while 5.0 had format date-time). Is there a reason for this?
Also, timestamp description is actually wrong:
Date/time format based on RFC3339 and ISO ISO8601, with an optional timezone in the format 'yyyy-MM-ddTHH:mm:ss[+-]ZH:ZM'
The text was updated successfully, but these errors were encountered:
ostefano
changed the title
5.1 format has inconsistent timestamp, wrong description, and lacks string format
5.1.0 format has inconsistent timestamp, wrong description, and lacks string format
May 22, 2024
In the just released 5.1 schema, field
timestamp
is typestring
with an unspecified format (while 5.0 had formatdate-time
). Is there a reason for this?Also,
timestamp
description is actually wrong:While the regex (and actual timestamp values, see here for example https://raw.githubusercontent.com/CVEProject/cvelistV5/09b7c787c45c0193ce24c1fdcb98930c562741ef/cves/2024/31xxx/CVE-2024-31340.json) matches another format:
yyyy-MM-ddTHH:mm:ss
with optionalZ
orZ[+-]HH:mm
(regex(Z|[+-][0-9]{2}:[0-9]{2})?
).The text was updated successfully, but these errors were encountered: