-
Notifications
You must be signed in to change notification settings - Fork 1
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
README.md: add guidance on expressions of interest #54
Conversation
4baffb5
to
995bf2e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we should pause this PR until the points discussed in open-contracting/ocds-extensions#41 are settled (whether to add a discriminator field, whether to rename Bid
to Response
etc.) as that will likely impact the content of the documentation and examples.
I'll follow up - thanks for the reminder. |
Let's add a discriminator field and do the renaming, but we can discuss details in open-contracting/ocds-extensions#41 |
7ef071e
to
6fbd346
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to also modify the title and description of the Bid definition.
It would be difficult to modify its machine-name to Submission, as other extensions modify the Bid definition (requirements, subcontracting).
Edit:
Schema
Need to add "expression of interest" wording to bids
(reword as "Information about ..." and copy the wording of the extension metadata), Bids
(and fields), Bid
fields, etc. Can maybe consider "submission" to reduce wordiness. Please address style guide issues like "An array of" while making edits.
bidStatus
Need to probably also modify bidStatus to use "bid or expression of interest". Noting that "evaluated" can be used both in the context of qualification criteria and award criteria, e.g. from UNCITRAL:
The procuring entity shall evaluate the qualifications of suppliers or con- tractors in accordance with the qualification criteria and procedures set out in the pre-qualification or pre-selection documents
That said, we probably need to remove "in order to be evaluated" as that's being used to mean "against award criteria" which isn't the case for EOIs.
We can also update "requirements" to "criteria".
statistic
For consistency, in statistic.csv
, we should change requests to participate to expressions of interest. We can leave the requests
code as-is as it has been present since the first version.
Change the Category for requests
to expressionsOfInterest
- bids array is not only for received submissions (e.g. can be invited) - Merge related paragraphs
5e16c0b
to
a84ae2f
Compare
Co-authored-by: James McKinney <[email protected]>
@jpmckinney Re.
|
If we didn’t need such codes for eForms, then I think no jurisdiction tracks such statistics. |
… and contracts should relate to bids, and only to EOIs if bids are not published
…would be too repetitive to do this consistently)
…tics", consistently
… in the definition's description.
…t is true for any field.
…. Parenthesize it in `value`, as EOIs mostly don't have values.
…angelog entry to match heading.
c546ba3
to
1020d28
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made some other changes. Ready to merge.
closes open-contracting/ocds-extensions#41