Re: [Json] JSON Schema Language

[Phillip Hallam-Baker <[e-mail]>]

On Wed, May 29, 2019 at 10:59 AM Nico Williams <[e-mail]>
wrote:

> On Tue, May 28, 2019 at 08:47:16PM -0700, Tim Bray wrote:
> > TBH, what I want from a schema system is (a) useful error messages and
> (b)
> > ability to drive code generation, classes and serializer/deserializers
> and
> > so on.
>
> This is all I want as well.  Validation and codegen.
>


I use mine for code generation and for document generation. The drafts are
produced by the same source that generates the code used to create the
examples.

Validation is another issue entirely. I don't think it is actually useful
beyond 'can the data be deserialized'. It is problematic if someone sends a
string in a field where I really need an integer, but additional fields I
will simply ignore unless they are in some SAML Conditions like structure
which MUST be understood. But the only reason to use that approach is when
you require a means of signalling a breaking change.

The tools I am currently using are on Github and they work on Windows, OSX
and Linux.

This is not the approach I would use if I was going to propose a standard.
There are a half dozen different schema systems that vary by small degrees
for different purposes that I think could be merged.


https://github.com/hallambaker/PHB-Build-Tools