-
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
Unclear rules on uniqueness of record #847
Comments
Related to #1264 |
Merging #1264 into this issue: The implications of this statement are unclear. For example, cases that are allowed:
Cases that we want to disallow:
As such, we might need a paragraph to explain that it is per contracting process per distribution (in the sense of DCAT), where a distribution might be a specific API endpoint or a specific bulk download file. In reviewing the Primer draft, @JachymHercher wrote:
|
I suggest updating the first sentence of https://standard.open-contracting.org/staging/1.2-dev/en/schema/records_reference/ to read:
To account for old records and API methods with an "as of" argument, we might need to clarify the following requirements:
Variations on those requirements appear in several places:
One option is to add 'at the time of publication', which is already used to describe a compiled release in https://standard.open-contracting.org/staging/1.2-dev/en/schema/records_reference/#record-structure. @jpmckinney, what do you think? We should also update the following sentence from https://standard.open-contracting.org/staging/1.2-dev/en/getting_started/releases_and_records/:
to
|
All sounds good. I think "at the time of publication" works well. |
At many locations, it's recommended that there be only one record per process. However:
As such, it's clear that there isn't only one record per process.
What we really want is for it to be clear which record is the most up-to-date and complete. We should update the documentation to be clearer about this.
Need to update
releases_and_records.md
andrecords_reference.md
among others.The text was updated successfully, but these errors were encountered: