Greg Dennis
Greg Dennis
> Is this not crossing resource boundaries, just as #/`$defs/bar/$defs/item` is? `#/$defs/bar/$defs/item` crosses from `foo` (root) to `bar` to `item`, each having an `$id`. `bar#/$defs/item` crosses from `bar` to `item` ...
... this conversation isn't about pointers crossing resource boundaries. It's about a `$dynamicRef` resolving to a deeply nested schema resource. Pointers crossing boundaries has been identified as an ill-advised practice,...
Whether `bar#/$defs/items` crosses a resource boundary is not relevant to this discussion because this discussion is about what ends up in the dynamic scope. We've already both [agreed](https://github.com/json-schema-org/JSON-Schema-Test-Suite/issues/719#issuecomment-1939660968) that `bar`...
No worries. I was on mobile and hadn't checked other tests. Sorry for the confusion.
I've run these against my implementation, and they pass.
Happy to accept simplifications, but this is the smallest I could come up with.
@karenetheridge try again, please.
> Where should the re-location be done? "Re-locate" here means "locate again;" as opposed to "relocate" which means "move". English is dumb. The point is that the reader of the...
JSON Path now has an RFC! https://www.rfc-editor.org/rfc/rfc9535.html
Yeah, I understand having a large client like that can drive features. Let's hope they get on board. We're also putting together a [test suite](https://github.com/jsonpath-standard/jsonpath-compliance-test-suite). I don't think it can...