Three dateUpdated fields, all set by Services

[zmanion]

dateUpdated for the CVE record

dateUpdated for the CNA container
Timestamp to be set by the system of record at time of submission. If dateUpdated is provided to the system of record it will be replaced by the current timestamp at the time of submission.

dateUpdated for the ADP container, same treatment as 2.

As noted in 2., if CNAs or ADPs provide dateUpdated, it gets stomped by the Services. So consider not allowing submission of these fields.

[zmanion]

Copied from/duplicate of CVEProject/automation-working-group#120 since this issue involves an interaction between CVE Record Format and CVE Services.

[jayjacobs]

Not exactly clear what the request of the QWG is here. If anything this seems like a documentation update? The schema can't enforce what to submit or not, and the overwriting would be done in cve services.

[jayjacobs]

Related to #378.

[ccoffin]

Current providerMetaData\dateUpdated description has the following description:
"Timestamp to be set by the system of record at time of submission. If dateUpdated is provided to the system of record it will be replaced by the current timestamp at the time of submission." We should verify with AWG that this date time stamp does in fact get overwritten as described. dateUpdated also exists in cveMetadataPublished and this should not be part of a CNA or ADP submission as it is at the CVE Record level. We may want to document this in the schema.