The draft parameter seems to have a limited effect on the interpretation of the schema

[chipilov]

The draft parameter seems to have a limited effect on the interpretation of the supplied schema.

I assume that if draft 4 is passed as parameter and the supplied schema contains features which are NOT supported in draft 4, either an exception will be thrown OR the features which are NOT part of the draft will be ignored.

For example, if I specify draft 4 and use unevaluatedProperties (which was introduced with 2019-09), I still get an error if the data contains properties which are NOT explicitly specified in the schema.

Is this expected and if so - what exactly is the purpose of the draft parameter?

VERSION:
"1.12.0"

[jdanyow]

Currently draft use is limited to ensuring rules and keywords which have evolved like minimum, maximum, and $ref behave as specified in the selected draft.

It wouldn't be too hard to disable keywords based on draft. What's your use case?

Related #154