> Why express paths as a string if you have the ability to encode it as an array in json? Probably because it's mimicking XPath, which was the analogous string

> Why express paths as a string if you have the ability to encode it as an array in json? Probably because it's mimicking XPath, which was the analogous string but for XML. Think regex as well, which is a string.