Compliance stamp

[kinlane]

Investigate and enact a lightweight but slightly more formal compliance process for spec adoption. This is important in encouraging adoption and celebrating those who implement the new standards. It should not be onerous, but at the very least there should be a self declaration of compliance with a list of features supported. This then hosted on the OAI website - with compliant tools showcased. Stage 1) investigate what other bodies are doing these days, 2) make a proposal which is as lightweight as possible but still valuable, 3) if acceptd - enact it.

[paraskakis]

GitHub badge would be good

[MikeRalphson]

@kinlane Think this is the issue where you mentioned Postman's support of the spec. I found this checklist useful in ensuring spec compliance / completeness: https://github.com/temando/open-api-renderer/blob/master/docs/open-api-v3-support.md

[kinlane]

I would like to take the list above suggested by Mike and merge with this work (https://github.com/api-evangelist/openapi-support/blob/master/openapi-features.md) to create a self-self, or 3rd party filled out form for tools. Not quite certification, but would be nice to have as checklist. Then maybe next step is badging / certification.