Austin Wright

I'd like to see an example of how this is useful for structural validation. JSON Schema generally does not encode valid data ranges; that is to say, if the guest...

I recall suggesting something similar to this, or at least not as part of the spec, but an idea to generate a schema (server-side) based on query-string parameters. In any...

@ssbarnea It's typical these days for properties to be listed by insert order (including in JSON.stringify), maybe just recreate the object in your preferred sort order. Does that make sense?

Is this just for validating instances, or is it for something else (user interfaces)? What would be an example of a schema, and valid and invalid instances?

How would this be different than specifying something like `{"mask": 2047}`, where `instance & mask == instance` in order to validate integer instances?

"type" right now only refers to the six core primitive types defined in JSON. While `type:"integer"` is additionally specified by JSON Schema, it's only provided as an author convenience, it's...

@handrews I mean, in the sense the you can use "oneOf" yeah, you can. But you can't generalize that example to say "for any number `10`"

Yeah, I think there's something to be said for adding keywords as author conveniences. But I'm not sure this would get enough usage to be worth the additional keywords --...

Good points. This does allow any data source to be referenced, I think that flexibility is desirable; I don't want to encourage people to shoehorn in more JSON data into...

I was working on an application and wondering if there's a few standard ways for looking up values, that we could describe; and then allow implementations to offer optimizations/alternative versions....