Re: [Jsonpath] JSONPath or JMESPath

Sounds like JMESPath is already reasonably well-defined. JSONPath isn't.
JSONPath is widely adopted and in my most recent job, lack of a
standardized definition was a real problem. So it sounds to me like there's
more value for the IETF to add with JSONPath.

On Tue., Aug. 11, 2020, 10:22 a.m. Stefan Hagen, <stefan@dilettant.eu>
wrote:

>
> Am 11.08.2020 um 18:30 schrieb Carsten Bormann <cabo@tzi.org>:
>
> On 2020-08-11, at 18:17, Davide Bettio <davide.bettio@ispirata.com>
> wrote:
>
>
> Hello,
>
>
> Darrel Miller on dispatch@ietf.org started a "JSONPath or JMESPath"
>
> thread,
>
>
> Right, please find (and read) the thread here:
>
> https://mailarchive.ietf.org/arch/msg/dispatch/FoCwaHJVIqJP78GdHT-IaDH32ks/
>
> The reasons he gave for choosing JMESPath are exactly the ones that made
> me propose the activity this mailing list has been created for.
>
> I think we should take a decision on this topic before making
>
> any other decision.
>
>
> It is a bit outside the scope, as this mailing list was created for
> standardizing JSONPath, but we certainly don’t want to expend the effort
> for that if JMESPath is already the solution.
> I can’t reach https://www.jmespath.org/ at the moment, so
>
>
> Try without the www: https://jmespath.org/ works for me while the above
> URL does not.. Or one can start from pypi or
> https://github.com/jmespath/jmespath.py
>
>
> If we go for JMESPath, discussing JSONPath here would be useless, so
>
> can we prioritise this topic?
>
>
> Sure.  So what are the advantages of JMESPath over JSONPath that are not
> about what we’ve set out to do here?
>
> Grüße, Carsten
>
> --
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath
>
>
> Best,
> Stefan
> --
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath
>