Skip to content
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

Considering "certificate" as a core extension #39

Closed
mireille-raad opened this issue Jun 12, 2017 · 3 comments
Closed

Considering "certificate" as a core extension #39

mireille-raad opened this issue Jun 12, 2017 · 3 comments

Comments

@mireille-raad
Copy link

mireille-raad commented Jun 12, 2017

In some of the PPPs or some of the "big contracts" there are different types of certificate involved:

  • certificate that the bidder is qualified to participate
  • certificate of completion or certificate of compliance

I haven't seen it in a real life example, but I imagine that sometimes items used need to be certified (think ISO or UL or green energy certification) - or in case of services, people provided them need to certified professionals.

Have you looked at having certificate part of the core extensions? do you think it should be developed separately?

@timgdavies
Copy link
Contributor

There has been some discussion of approvals and certification in open-contracting/standard#403 and the work in the Requirements Extension can potentially be used to model a requirement that a supplier needs to be certified in a particular way.

I don't see this becoming a core extension soon, but if there is more that can be done to document implementation approaches for this based on some real data examples that would make sense.

I would suggest moving this over to https://github.com/open-contracting/standard/issues as a discussion there unless there is a specific extension drafted to propose for inclusion in the registry.

@mireille-raad
Copy link
Author

mireille-raad commented Jun 14, 2017

good to know that you don't think this can be a core extension.

I am not sure about moving this to the standard issues for discussion... i feel sometimes issues need to be "worthy" - otherwise, you will become overwhelmed with issues to filter and think through.

Maybe you will have "github issues fatigue" if every idea that crosses everyone's mind becomes an issue.

@timgdavies
Copy link
Contributor

Good descriptions of use-cases over in the standard repo are always welcome. Useful to just surface who is interested in what - so don't worry about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants