What's new

Introduction

This page mentions what is new in version 2.0.x compared to the latest stable 1.6.x

New features

Dependency on json-schema-core

This is the main and more impacting change. It means you have the full power of what json-schema-core offers at your disposal. See here for more information.

Note that the validation processor being a processor, it means you can use this processor (which you can retrieve using the .getProcessor() method of JsonSchemaFactory) in your own chains.

Separate syntax validation

You can now validate schemas using a dedicated validator. This was not possible with 1.x.

format validation can be disabled

The validation draft requires that it be possible. This library offers this possibility.

Draft v4 is now the default

In 1.x, it was draft v3.

Behavior changes

No more hyper schema syntax validation

This will be reintroduced in a separate package. Unless someone writes a processor for that before I do...

Not possible to register a keyword without a syntax validator anymore

This was possible with 1.x.

Not possible to override validation for core meta schemas

With 1.x, you could decide to override validation of JSON Schema's official meta schema URIs with your own. This is now forbidden.