Jason Desrosiers

I couldn't help writing up what the spec might look like without bookending or initial resolution (#1142). It makes the concept much easier to describe. Personally, I think it's easier...

Here is an example using the hyper-schema links schema that shows what is lost by removing the initial resolution step. In this case we want "submissionSchema" to be extendible with...

@handrews Thanks for looking this over. Your timing is perfect because I was hoping to get back to working on this issue soon. Your example is pretty much what I...

> 1. The target of these particular `$refs` is the resource root, so there's no need for a fragment at all Yep > 2. If we did need a fragment,...

I think we can just change it. We aren't committed to no backwards compatible changes yet. This is definitely something we want to get in before we consider this feature...

To be clear, the bookending requirement was already removed in https://github.com/json-schema-org/json-schema-spec/pull/1139. This proposal is in addition to that change.

What about this example do you think won't work? The `else` is dead code and can be removed. The initial resolution to "inner_scope" exists only to satisfy the bookending requirement,...

@handrews I found all of that very difficult to follow. I think what you now think I'm proposing is correct, although I'm really only certain that the end result is...

@handrews I know this isn't exactly what you asked for, but it was the best I could come up with. I'm just not sure this approach meshes well with the...

@karenetheridge That occurred to me as well. I like the idea, but decided the trade-offs weren't worth it. Retrieving the meta-schema is a secondary purpose. The main purpose of using...