Julian Berman

Can we separate out that one from this ticket which I'm inclined to even close since we got all wrapped up in unrelated things? This one was originally about test...

From a ticket closed as a dupe, sharing [this](https://github.com/json-schema-org/JSON-Schema-Test-Suite/issues/557#issuecomment-1159191199) again below: > According to the specification, JSON Schema definitions are recommended to have a $schema keyword. To me, I don't...

I'm responding quickly not to say I've already understood what you wrote (which yeah thanks! I'll read it carefully) but just because: > as of 2019-09 [...] the absence of...

My reading skills (of the spec) apparently leave what to be desired, since I figured you were referring to that paragraph, but I have up until this moment probably never...

For my own complete clarity, and thanks again for bearing with me until now, I want to also cite something from json-schema-org/json-schema-spec#439 (which I intend to get back to and...

I'll follow that ticket (which I of course haven't read yet), but fair enough, then substitute whatever other behavior is incompatible with the current suite, say choosing to default to...

Let's move any discussion of what the set of valid implementation-defined behaviors are, and whether they include "error out", elsewhere (like the ticket linked) so that this ticket can just...

What we have today is not a heuristic and not cheating :), it's explicitly the test suite *telling* anyone using it "stuff in this folder is written to be run...

> Could you add a mention in the README that the base uri is 'http://localhost:1234/', so tooling that performs their own processing of 'remotes' can do so correctly? Yep, good...

I'm assuming this is good to go now with folks but if not obviously follow up.