Re: [Json] JSON Schema Language

[Anders Rundgren <[e-mail]>]

On 2019-05-06 09:22, Austin Wright wrote:
<snip>
> 
> Can you elaborate on this? My point is primarily concerned with JSON parsers, not JSON the media type.
> 
> Suppose a string were too large to store in memory, most ECMAScript engines would bail with an uncatchable error. The suggestion is to implement this more robustly, like throw an error if a string would be too long, or if a number has too many significant figures; instead of either crashing or silently approximating the number.

I don't understand this.  A JSON schema is a description of a JSON document.  If the description is incompatible with implementations that are supposed to parse compliant documents all bets are off.


> But also, why not build a parser that uses a schema to influence how values are parsed? Suppose you have a dynamically typed language, and want to parse some value, e.g. sometimes as an int, sometimes as a bignum, depending on the property. You might provide a JSON Schema to specify this behavior.

This sounds like an edge-case but it could be supported by an "any" type (although don't particularly see how this could work in a cross-platform scenario).

I would rather consider looking into more down-to-earth requirements such as supporting common numeric types and dealing with alternative already widely deployed serialization options for those.

https://github.com/json-schema-org/json-schema-spec/issues/736

Anders