While it superficially looks like paths, it’s actually not completely compatible because of the “…” syntax. I think standards that *look* similar but actually have subtle differences are traps for the unwary.
As an alternative, have you seen this proposal for Relative JSON Pointers?? Instead of a dot for each level you go up, it starts with an integer.
Plus it has an interesting JSON-specific feature: if the value following the initial integer is not a JSON Pointer, but actually “#”, then the value returned is the value of the *key or index* that many levels up – so
"0#" would mean the key/index most directly associated with that data.