Kyle Hargraves

@iainbeeston I think the correct way for us to parse values is `JSON.load('1', nil, :create_additions => false)`. We need to disable create_additions because it's a security issue with untrusted data:...

Seems okay. I don't really grok why a schema would ever define a fragment as its top-level id, tho. I find it very difficult to reason about the Correct Behavior...

multi_json is mostly dying, as can be seen by nearly all large projects slowing dropping their dependency on it. I rather liked the idea of multi_json, but so it goes....

The registered schemas all get an empty fragment because we use `uri.fragment = ''` when we create them: ``` uri = Addressable::URI.parse('http://example.com/hi') uri.to_s #=> "http://example.com/hi" uri.fragment = '' uri.to_s #=>...

I have a half-baked branch I was tinkering with that drops support for multijson and yajl, I can send a PR later today. Do you think we should also release...

Tangentially, has anyone found a tool to do the opposite? eg, given a schema, generate random JSON values that would satisfy it? It'd be handy for fuzzing tests. Definitely non-trivial,...

Coincidentally, when I joined #ruby-json-schema @ freenode today, a new person was idling; checked if their nick was also what they used on Github and found @jphastings' [genny](https://github.com/jphastings/genny) project which...

What is setting the `file://localhost/...` URI ? It doesn't really make sense for a URI to include both a hostname _and_ an absolute file path -- DNS is not at...

Had a chance to dig up the spec, it's true that `file://localhost/foo/bar` should always be treated as equivalent to `file:///foo/bar`. [RFC 1738 § 3.10](http://tools.ietf.org/html/rfc1738#section-3.10) and [RFC 3986 § 3.2.2](https://tools.ietf.org/html/rfc3986#section-3.2.2). And...

:thumbsup: on the i18n tactic. I kept drawing a blank when trying to think of a reasonable way to implement this.