Henry Andrews

@Julian now I'm realizing that the remotes need draft-specific `$schema` updating. I'll work on that and update this PR, unless you'd prefer to merge this and I'll do the remotes...

OK, I've looked into the remotes situation, including how `bin/jsonschema_suite` works with the remotes, and @Julian I could use a bit of advice on how to proceed. I see two...

@Julian so should I implement option 1 for now, or put this on hold until the necessary support for Option 2 (whoever ends up implementing it) is in place? Regarding...

@Julian good to know. I will try to wrap this PR as soon as I can up since it is touching so many files. As far as the `format` tests...

@Julian I know that `localhost:1234` is where the `remotes` directory is mounted, but what is `localhost:4242`? It appears in `tests/2019-09/recursiveRef.json`?

@Julian a lot of files reference localhost. What should they be referencing instead? I can fix that (at least for 2019-09, 2020-12 and draft-next) if you'd like, but mostly I'm...

I think this is now complete — @gregsdennis if you'd be willing to run the suite with your validator again that would be fantastic. I still don't have anything set...

@Julian yes, I was just waiting to make sure you were OK with the further work on the remotes and draft-next. Let's defer the sanity check and other cleanup to...

Both of these cases are [implemented](https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/main/tests/draft2020-12/id.json#L110). However, I don't remember why _`"$id": "#"` is a no-op_ is a test case. Here is the case as implemented: ```JSON { "description": "Identifier...

@Julian sounds good, I'll make a PR for that. The test as it stands runs afoul of [§9.1.2 "Loading a referenced schema"](https://www.ietf.org/archive/id/draft-bhutton-json-schema-01.html#section-9.1.2) (last paragraph): > A schema MAY (and likely...