{
"a": {
"b": {
"c": []
}
}
}
{
"makes": {
"toyota": {
"models: [ ... ]
}
}
}
Or
"Toyota came out with a new Camry, I need to update the Camry object within Toyota's models."
Both, JSONPath or JMESPath, support query expressions whereas JSON Pointer does not.
The point is that this is a data structure and not a web server. It's using a convention from one domain in a different one. Relatively minor in the scope of possible quibbles, but it's just one more thing to remember/one more trivial mistake to make. I'm sure much collective time will be lost to many people using dots where the spec says to use slashes, and not realizing it because it looks right in every other context with dots. Dots also makes copy/pasting easier, because you wouldn't have to migrate the format after pasting.
URIs are not only used on web servers though, they're all over the place, probably most notable your filesystem is using `/` as a path separator, so it wouldn't be completely out of place to use it as a path separator elsewhere.