confusion about ssZZZZ in date-time format #210
Description
seem to imply that a timezone in the format 0000 can be used immediately after the seconds in a date-time value. Actually, there needs to be a plus or minus first, and also a colon between the hours and the minutes. It perhaps could be better represented as:
with an optional timezone in the format 'yyyy-MM-ddTHH:mm:ss[+-]ZZ:ZZ'. If timezone offset is not given, GMT (+00:00) is assumed. (line 79)
with an optional timezone. yyyy-MM-ddTHH:mm:ss[+-]ZZ:ZZ - if the timezone offset is not given, GMT (+00:00) is assumed. (line 955)
or
with an optional timezone in the format 'yyyy-MM-ddTHH:mm:ss[+-]ZH:ZM'. If timezone offset is not given, GMT (+00:00) is assumed. (line 79)
with an optional timezone. yyyy-MM-ddTHH:mm:ss[+-]ZH:ZM - if the timezone offset is not given, GMT (+00:00) is assumed. (line 955)
I realize that this is inconsequential for most schema users, because they will be using standard library functions to construct date-time values within CVE Records, and all, or nearly all, common languages/frameworks are able to construct date-time values that comply with the schema.
The issue is relevant because the date-time format is also used in some CVE Services API commands such as:
GET /api/cve-id?time_reserved.lt=2023-01-01T12:34:56-05:00
and users realistically type such timestamps manually (without using a library function). I realize that the cve-schema repo maintainers aren't responsible for the API. However, the CVE Services API maintainers told me they want their date-time documentation example to be exactly the same as the cve-schema date-time documentation example. So, I was hoping that the cve-schema repo maintainers could help me out by changing the above two occurrences of ssZZZZ and the above two occurrences of 0000 to something that is more accurate.