draft-ietf-jsonpath-base

draft-ietf-jsonpath-base copied to clipboard

Inspired by a StackOverflow question, I think a singular path could be a viable selector.

The example given is

addresses[productData.products[0].addressRefId].storeName

I see this as taking the value in productData.products[0].addressRefId as the selector value.

This would, for example, allow the data to contain the index of an array (or the key of an object) to select, amongst other similar functionality.

If we could work out a way to support multi-value paths, that'd be cool, but I think singular paths are simple enough to do.