is datePublished possibly ambiguous?

[ElectricNroff]

cve-schema/schema/v5.0/CVE_JSON_5.0_schema.json

Lines 401 to 403 in fbf54b9

	"datePublished": {
	"$ref": "#/definitions/timestamp",
	"description": "The date/time the CVE Record was first published in the CVE List."

and

cve-schema/schema/v5.0/CVE_JSON_5.0_schema.json

Lines 443 to 445 in fbf54b9

	"datePublished": {
	"$ref": "#/definitions/timestamp",
	"description": "The date/time the CVE Record was first published in the CVE List."

may have been intended to mean "The date/time the CVE Record was first present in the PUBLISHED state on the CVE List." If so, then these should be clarified.

(The schema is not symmetric. If a CVE Record is currently in the REJECTED state but was previously in the PUBLISHED state, then cveMetadata may have both dateRejected and datePublished. However, if a CVE Record is currently in the PUBLISHED state but was previously in the REJECTED state, then cveMetadata is not allowed to have dateRejected. Historically, it has been less common to make a transition from REJECTED to PUBLISHED.)

[chandanbn]

QWG discussed to change this to:
"The date/time the CVE Record was first published to the CVE List in the PUBLISHED state."

[darakian]

@ccoffin was this one of the issue related to the UTC time format conversation?

[alilleybrinker]

Given that this is for the 4-to-5 conversion, can it be closed?