Iain Beeston

Oh I see your point. I think you're misunderstanding here. Your schema definition says you expect a string, formatted as a uri. However, when you pass 'http://foo.bar/?baz=qux#quux' as data, json...

Basically, if you pass json schema a string, and it's not valid json (any arbitrary string is not necessarily valid json, to my knowledge - it must start with "{"...

I imagine it's for convenience (@hoxworth?) Right now, whether JSON schema can validate an arbitrary string depends on the json parser used. But I think this is a wider problem...

That's a really interesting point. I've double checked the ietf spec and it's explicitly for validating json objects, not just arbitrary data. Which means that many of the common test...

@fge My mistake - you're right. I confused JSON data with JSON objects. If I read through it again and look up every definition: 1. 'JSON Schema is a JSON...

Also, (just for completeness, in case this ever helps anyone find the definition of what valid JSON is) RFC4627 has been superseded by RFC7159, which replaces point 4 with: >...

I think that (maybe for v3) validate should assume it's a string to be validated. I think if the user wants to load a url they should have to be...

While we’re on the subject of loading strings that happen to be a uri, it might be worth noting that if the string is interpreted (by URI.parse()) as a relative...

@pd I've been thinking about this, and now I agree completely. Ideally, we shouldn't try to parse json at all - there are already good libraries to do that -...

@fge Unfortunately all of the ruby json parsers that I'm aware of default to parsing json text, not json values. However, I've just discovered that Ruby JSON has a "quirks...