Jason Desrosiers

> if you `$dynamicRef: #foo` and there's an `$anchor: foo` in the current resource, it should find that, and stop, and never examine the dynamic reference. Or at least that's...

@handrews, now I see where you're coming from. To express the problem as code, you expect anchor information to be collected like this, ```javascript // "$dynamicAnchor": "aaa" anchors["aaa"] = {...

Good point. Maybe that should probably say "any schema **resource** intended for use as a meta-schema". If I understand the terminology used in the spec correctly, the example as a...

The `draft-next` branch has been merged and is now closed. The merge target for this PR has been changed to `main`. Here are the recommended steps to get your branch...

If I understand this correctly, this looks like it maps to the current `$recursiveAnchor`/`$recursiveRef` behavior with one important difference. It seems to me that `$extends` is like setting `"$recursiveAnchor": true`...

> I do think that the issue raised by @jdesrosiers is a concern. Then you didn't understand the point I was making because you proceeded to make almost exactly the...

@handrews Ha! Sorry, I read that wrong.

Yes, I've implemented everything from draft-04 to draft 2019-09 (plus OAS 3.1) with the exception of `format`. That includes vocabularies and `$recursiveAnchor`/`$recursiveRef`. It was difficult to understand these keywords, but...

I'm not sure I see the problem. JSON Schema defines how schemas are identified (RFC-3986) and leaves it as an implementation detail how to store and retrieve those schemas. >...

That explanation makes sense for a long lived distributed system with no centralized control, but that's not what JSON Schema is. When JSON Schema says that the identifier for the...