The "tilde" (`e` not `a`, btw) and "slash" ones are slightly problematic.

AFAIK, the JSON Pointer spec doesn't say that you *aren't* allowed to encode the slash characters when using a JSON Pointer as a fragment.  I mean, there's no reason why you need to, but I don't think it's banned.

As such - I think that `#%2FsomeProperty` could reasonably be interpreted as a JSON Pointer fragment, which means that `#/slash%2ffield` could equally be decoded into the JSON Pointer fragment `/slash/field`.

Now, v3 doesn't use JSON Pointer - but it means that the "tilde" and "slash" examples here are still relevant to the compatability discussion.