-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify release.date field description #854
Labels
Schema
Relating to other changes in the JSON Schema (renamed fields, schema properties, etc.)
Milestone
Comments
jpmckinney
added
the
Schema
Relating to other changes in the JSON Schema (renamed fields, schema properties, etc.)
label
Apr 1, 2019
yolile
added a commit
that referenced
this issue
Mar 25, 2020
ref #854 Signed-off-by: Yohanna Lisnichuk <yohanitalisnichuk@gmail.com>
I might also suggest a slight rewording: "first recorded in, or published by, any system". |
yolile
added a commit
that referenced
this issue
Mar 25, 2020
ref #854 Signed-off-by: Yohanna Lisnichuk <yohanitalisnichuk@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Schema
Relating to other changes in the JSON Schema (renamed fields, schema properties, etc.)
One publisher was updating the release date for all releases relating to a contracting process whenever anything changed. Other publishers have used it for the date when they generated the release, not when the process was made or first published in their local system. The current description is ambiguous, allowing for the above behaviors:
The field value should be the date on which the information contained in the release was first created or published in any system.
Related #848 and #849
The text was updated successfully, but these errors were encountered: