>>Unfortunately, the case at the moment is that we don't seem to be able to >>consume valid JSON, as per Sandro's example. Though I agree we should be >>robust enough to consume non-compliant output as well. > >Again, it's not the JSON that's invalid. It's the path he's using (which isn't >actually even part of the JSON standard).
Just to clarify - what I mean here is that the JavaScript-style paths Pivot uses aren't part of the JSON standard. I.E. the ability to write something like this: a.b["c"] is not part of JSON. However, it will most likely be familiar to anyone knowledgeable in JavaScript and is a convenient means of accessing access nested values in deserialized JSON objects. I look at it as a way to provide a feature similar to XPath, but for JSON data.
