Support of 2019-09 draft (aka draft-08)

[jgarver]

I know it's a big ask; just letting you know I'm pretty excited about the new draft and am eagerly awaiting support.

Thanks for all you do!

[christian-weiss]

https://github.com/json-schema-org/JSON-Schema-Test-Suite writes: "Draft 2019-09 support is under development. Contributions are very welcome,..."

So i guess Julian will wait until Test Suite is "well enough" to implement against it.

[thierryreding]

I've implemented a rough proof of concept for unevaluatedProperties in a fork here:

https://github.com/thierryreding/jsonschema/tree/master

which I've been using as part of some work to convert some of the device tree bindings in the Linux kernel to use json-schema. Some of the bindings that I've been working on are a bit complex and rely heavily on conditionals, so "unevaluatedProperties: false" is necessary to validate that we don't end up with extra properties in device tree files.

Anyway, the implementation is by no means complete, but it seems to do what it's supposed to, so I wanted to run it by you to get some feedback on the implementation. There's a bit of an API break in there, though it should be fairly easy to make it backwards-compatible if that's a requirement.

[Julian]

@thierryreding nice! Thanks for doing that, I'm sure I'll have a look as I try to get this in place.

[Julian]

(I don't know yet just how quickly that'll be, jsonschema is at best a spare time project at this point, which is exceeeedingly small :(, but yeah to anyone watching this ticket, draft2019/draft2020 support will definitely come at some point.)

[jnsnow]

(I don't know yet just how quickly that'll be, jsonschema is at best a spare time project at this point, which is exceeeedingly small :(, but yeah to anyone watching this ticket, draft2019/draft2020 support will definitely come at some point.)

Is there a good list that explains the features missing for 2019-09 support? I've noticed that most implementations of json-schema have not yet implemented support for it. Is 'unevaluatedProperties' the big sticking point that inhibits adoption?

I might be open to helping push this forwards, but I'm suspecting there's some reason that 2019-09 was not widely adopted.

[Julian]

I am toying with the idea of doing a Twitch stream to discuss/start that process (and really motivate allocating some time for this).

My personal guess is that the introduction of annotations may actually be more annoying, but yeah unevaluatedProperties probably will be a bit annoying too. The best list is the changelog on the schema spec site.

I'd possibly say 2019-09 wasn't as widely adopted partially due to my shortcomings too :( because I haven't given enough energy to the language-agnostic test suite as it needs either, which hinders other implementations.

But the 2020/2021 draft is now out as well.

[jugaadi]

OpenAPI 3.1 got released today. It adds support for jsonschema v2020-12 natively.

[anuj9196]

When the support for the 2019-09 draft will be released?

[handrews]

@anuj9196 @jugaadi @Julian I'd tend to recommend going straight to 2020-12 given the OAS 3.1 integration. If 2019-09 happens to get done along the way, great, but some things (like $recursiveRef) are kind of awkward in 2019-09 and don't carry over to 2020-12 anyway.

[Julian]

That's almost certainly how things will go (thanks for the advice Henry). In light of that going to close this one and combine it with #782 even though it's newer, but yeah these will either land simultaneously or only 2020-12 may land. Keep an eye on the other ticket if you want updates folks.