TIMESTAMP_FORMAT should not use ZZZZ for tenths of milliseconds

[ElectricNroff]

cve-services/src/middleware/errorMessages.js

Line 5 in a05a3d4

TIMESTAMP_FORMAT: 'Bad date, or invalid timestamp format: valid format is yyyy-MM-ddTHH:mm:ss or yyyy-MM-ddTHH:mm:ss.ZZZZ'

is potentially confusing because the letters ZZZZ are not ordinarily used to denote fractions of a second, and the reader may be misled into thinking that this is the "time zone" syntax ('Z' for "zone"). Also, ZZZZ is confusing because sub-second time precision is ordinarily either milliseconds (three digits after the dot) or microseconds (six digits after the dot), and hardly ever tenths of milliseconds (four digits after the dot).

RFC3339 refers to the part after mm:ss as time-secfrac, and thus .FFF could be used ('F' for "fraction").

A typical time would be one of these:

1. 2023-01-01T12:34:56.789
2. 2023-01-01T12:34:56.789Z
3. 2023-01-01T12:34:56.789-05:00

where option 1 is discouraged because it is not allowed by RFC3339 and is, more or less, a bespoke syntax for the CVE JSON 5.0 schema.

It could be reworded in multiple ways, possibly including:

OLD: valid format is yyyy-MM-ddTHH:mm:ss or yyyy-MM-ddTHH:mm:ss.ZZZZ

NEW: example valid formats are yyyy-MM-ddTHH:mm:ssZ or yyyy-MM-ddTHH:mm:ss.fff-zh:zm

[slubar]

@ElectricNroff this is the format used in the JSON 5.0 schema

[slubar]

On line 5 of the errorMessages.js file mentioned above, change 'yyyy-MM-ddTHH:mm:ss.ZZZZ' to 'yyyy-MM-ddTHH:mm:ssZZZZ' to remove the dot between ss and ZZZZ