Rationale:

This repo currently tests that each of the example JSON files are valid. Verifying that non-conformant examples are in fact not valid would improve the quality of extensions in several ways:

• It would allow testing limits such as maximum length.
• It would allow testing types such as putting a string value where an integer is expected.
• It could help end users which are not JSON Schema experts to understand the extension better.

Some considerations:

• Should not introduce a lot of extra complexity, so we should probably reuse the current testing mechanism and language.
• Should be easily ignored in the repo, so it should probably be in a separate directory like "non-examples".

I'm currently working in a group which is considering how to do this in our STAC extensions, but I'd be interested to hear your opinions and whether you'd be interested in upstreaming such a change.