Testing and validating JSON APIs is an important aspect of running a quality web service, but managing checks for large and diverse response bodies can be difficult.
Using JSON Schema to construct a model of your API response makes it easier to validate your API is returning the data is should.
We are also planning on adding more features to user accounts in the future, such as more advanced comparison options.
I release this library on the assumption that if I needed it, others might too.I may add support for more of JSON Schema, and I will certainly take pull requests (so long as they don't cause excessive bloat).Those that weren't tended to break in the contexts in which I was using them, and were generally rather larger and more complex than my needs.It turned out to be simpler to just write a validator that matches my needs.Example schemata: It is also possible to define union types, which is to say, cases in which validation will be tried against multiple type definitions until one matches or the list of options in the union is exhausted.
The JSON Schema project intends to shepherd the Core, Validation, and Hyper-Schema specifications to RFC status.
In the meantime, publication of Internet-Draft documents can be tracked through the IETF: Internet-Drafts expire after six months, so our goal is to publish often enough to always have a set of unexpired drafts available.
There may be brief gaps as we wrap up each draft and finalize the text.
Progress on the next set of Internet-Drafts can be tracked on Git Hub.
The draft-08 milestone will track the evolving scope of the draft You can apply constraints on an instance by adding validation keywords to the schema.
For example, the “type” keyword can be used to restrict an instance to an object, array, string, number, boolean, or null: JSON Schema is hypermedia ready, and ideal for annotating your existing JSON-based HTTP API.