Roadmap

In 0.5

Switch to Gradle -- but still provide Maven artifacts

I have inadvertently fallen prey to a well known Maven limitation, which is more than irritating: a child project's pom.xml file cannot reliably require its parent. Ugh.

This is just too serious an issue to ignore. Maven is too convoluted in general, but this particular misfeature calls for a modern build system to take its place. It will very probably be Gradle.

$ref support rewrite

$ref only works for a few cases, try and generalize it more. Also handle correctly $ref in the presence of other keywords.

IN PROGRESS: $ref now has priority over all other keywords (which fixes a nasty bug with embedded $refs in subschemas). But this is only a small step towards the final goal.

Thread-safe validators

Enough said...

Oust "format" keyword support to a separate package

Two reasons for that:

• it is optional in draft v3, and it will more than likely be gone from draft v4 entirely;
• this sole keyword's Maven-dictated dependencies account for more than 70% of the total project size -- ouch.

IN PROGRESS: code separation is done and works fine, but Maven gets in the way...

And one or more from below

Full draft v4 support

When it comes out...

Streaming validation

Right now the whole instance is read in memory before proceeding -- not a smart move if you want to validate really big stuff. Try and stream the process instead.