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
Bidder eligibility criteria #35
Comments
I believe this could be handled by submissionDetails for now. I am marking this as a documentation issue for the 1.0 release, and then a more detailed proposal can be submitted by a working group if its insufficient moving forward. |
@practicalparticipation i think this was also brought up by mihaly today |
Related to #139 |
I've also added an eligibilityCriteria document to the documentType list. Re-opening this against post 1.0. |
Version 1.0 of the standard has an I've been looking through issues, and thinking over cases we've encountered, to find any other requirements for structured eligibility criteria date. The only two things I can think of are: (1) Cases where only bidders on a given framework are eligible to bid; (2) Cases where only national firms are eligible to bid (I seem to recall an issue on this from procurement analytics, but can't find this right now) I suspect these are best handled as their own issues, so propose creating new issues for frameworks, and national-only eligibility issues, and closing this one. |
Requirement generated from User Research process: R17
There is user demand for fields which would indicate the eligibility criteria in order to be able to bid for a tender.
This requirement was articulated in the context of anti-corruption use-cases, where those involved with contract scrutiny are interested in understanding the complexity of tender requirements as a means of assessing whether particular barriers to bidding are being put in place.
They suggest analysis may look at "Length of eligibility criteria: character length of text defining which bidders are eligible to bid;".
As yet, requirements from firms for structured data on this have not been identified.
The text was updated successfully, but these errors were encountered: