Re: [Json] Another problematic JSON Schema use-case

[Carsten Bormann <[e-mail]>]

Tim Bray wrote:
> So, to close the loop, here's how I worked around the problem. I
> auto-processed my large schema with a Ruby script to generate a small
> schema for each of the "Type":"Animal/Vegetable/Mineral" variations,
> then if the large schema reports any errors, I run through the objects
> validating each with the appropriate micro-schema.  This way, I almost
> always get a human-comprehensible error message.

>From a grammar validation point of view, you believe the type field more
than the other fields, so if there is a conflict between them, the type
field wins and the other fields can thus be flagged as wrong.

In a definite clause grammar (DCG), cuts can be used to elicit similar
behavior.  There are proposals for cut points in parse expression
grammars (PEGs); maybe that is a good subject for further evaluation.

Grüße, Carsten