Reinstate validation of JSON Schemas (and examples) in build process

[MikeRalphson]

This issue is a place-holder to ensure this action isn't forgotten.

If we want to validate OAS instances beyond compliance with our JSON schemas, we would need to make a choice on which validator(s) to use - this would not be an endorsement.

Can occur after the resolution of #1270 / #1236

[MikeRalphson]

Script to validate JSON Schema instances against JSON Schema metaschema has been written and tested. Will be included in PR for HTML spec / registry go live.

[MikeRalphson]

Also script to validate examples against OAS schema instances, ditto.

[MikeRalphson]

Bump. Should this be reworked into a GitHub action?

[Bellangelo]

@MikeRalphson I can make the script to run in a Github action.

[handrews]

@Bellangelo we do have this github workflow which might actually do at least some of what is needed? I think the first step is to see what we are and aren't doing, as some work on GitHub automation might not have updated this issue. If you can take a look at that, a PR adding anything we're still missing would be most welcome.

[handrews]

@Bellangelo btw if you are looking for other automation/build-ish ways to contribute, you might want to check out our Automation & Infrastructure Project.

[Bellangelo]

Hi @handrews, sorry for the late reply but things got busy. You are indeed correct that some thing are now covered. I have opened a PR with a detailed explanation of what is missing and what it isn't.

btw if you are looking for other automation/build-ish ways to contribute, you might want to check out our Automation & Infrastructure Project.

Thank you. This is also where I found this issue originally.