Re: [Jsonpath] Returning multiple values: (was Controversial issues)

On 2020-11-06, at 00:19, Tim Bray <tbray@textuality.com> wrote:
> 
> In the heavily JSONPath-dependent app I most recently worked on, when applying a JSONPath returned multiple values, we exposed that as a JSON array.  Not religious about this issue, but the return-an-array seemed to surprise nobody and make people happy.

I wasn’t even aware that there is a question here.

https://www.ietf.org/archive/id/draft-goessner-dispatch-jsonpath-00.html#name-return-value

(Clearly, I would get rid of the “false” special case — an empty array is fine.)

Grüße, Carsten

> 
> On Thu, Nov 5, 2020 at 3:10 PM Daniel P <danielaparker@gmail.com> wrote:
> On 5 Nov 2020, at 11:14, Carsten Bormann <cabo@tzi.org> wrote:
> 
> > The underlying problem here is that of a missing model.
> > XPath has nodesets, and we probably need something like that.
> 
> Unlike XPath, where an expression can return items that are
> not XML documents, a JSONPath expression can only return
> JSON values, and a collection of JSON values can be
> returned in a JSON array value. Consequently, introducing
> the idea of node-sets into JSONPath would seem to
> serve no purpose.
> 
> Daniel
> 
> -- 
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath
> -- 
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath