-
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
GPA alignment of closed codelist descriptions #828
Comments
My attempt to improve the OCDS definitions using the GPA definitions. Electronic auctionGPA:
OCDS (
Proposal:
Qualified supplierGPA:
OCDS Qualification extension (
FYI the definition of
Proposal (not really relevant if
|
@jpmckinney The The difficulty to make a good definition for |
Can you update your comment to specify the precise OCDS fields/codes whose descriptions are being modified? Otherwise, I can't follow.
FYI, I created this tool for schema editors to easily look up fields/codes in registered extensions: https://open-contracting.github.io/editor-tools/ |
I've updated my comment. Thanks, great tool, that will definitely help! |
|
My bad, I first thought I had to study the terms that had an "Open" status.
|
@jpmckinney What's your view on this?
|
I reviewed my old spreadsheet from the issue description: https://docs.google.com/spreadsheets/d/1X4nULP8nhYR_iXra0HjTy5n2v5z2kyzFFT7KTv2GZo0/edit?pli=1#gid=0 I think we might consider (the first two are in open codelists, so might be covered by #827):
|
My understanding of the need is that OCDS definitions work as-is but you want them to be more anchored in a reference terminology. GPA has a worldwide scope and good definitions. Let's give a "GPA touch" to the OCDS definitions:
OCDS 1.1:
GPA:
OCDS 1.2:
James' update: To make it easier to compare versions without copying content, I'll add my suggestion here. I consider the "lays down" metaphor from GPA to be unnecessarily indirect. "Detailed" and "technical" from OCDS 1.1 is clear from the rest of the definition (and the code title). "Tendering requirement" from GPA just raises more questions (what is a "tendering requirement"?). "Documentation" from OCDS suggests the document is more descriptive than prescriptive. I suggest:
Colin's update I find the "; or" not fluid:
|
OCDS 1.1:
GPA:
Proposal:
James' update: Sorry, the text above was from OCDS 1.1.4. OCDS 1.1.5 (#714, PR #725) already changed this to:
I don't know if #571 means that we should change this to "the buyer or the procuring entity". I'm also okay with removing the second sentence, since this can be said for almost any document Colin's update new proposal:
I have removed the second sentence, and replaced "procuring entity" with "buyer". Can we use "supplier" for potential tenderers who haven't even submitted a bid (cf #1149)? We could replace it with "potential tenderers". |
OCDS 1.1:
GPA (commercial goods or services):
OCDS 1.2:
I don't really understand this part (bold) of the GPA definition:
I don't see how the GPA text could improve the definition of 'procurementCategory: services'. |
I guess GPA distinguishes "commercial" goods or services by adding that extra clause ("generally sold or ...") - which I agree is not relevant to our definition. As such, the entire definition is not helpful to us. I think the only change is to switch "electronic" (which tends to be understood as laptops, etc. which are already "physical") to "digital". We should keep "or supplies" since that is an important synonym for "goods". For your other two comments, I added content to your comment, so that all definitions can be read on the same screen for easier comparison. |
That means we agreed on the following definition for procurementCategory:goods:
|
To preserve the same meaning as before, change "The document can also address" to "Or, a document that addresses"
I think it is clear in context. However, it'd be good to have a consistent style guide, e.g.:
This might be for a new issue, in which case we might edit the wording again as part of that issue. |
I saw guidelines on how field descriptions should be written. Where was it? |
@ColinMaudry Is this issue closed by #1280? |
Follow-up to #687 due to versioning policy, to align the
method.csv
andprocurementCategory.csv
code descriptions with GPA text, compared in this spreadsheet.Should also compare to OCDS or EU e-Procurement Ontology glossaries, to satisfy part of #827.
The text was updated successfully, but these errors were encountered: