Re: [Jsonpath] [dispatch] draft-goessner-dispatch-jsonpath-00.txt

This seems reasonable. 

As I mentioned in the session, I think there's a non-trivial amount of risk here that some implementations won't be willing or able to move away from their current behaviours, even if interoperability would improve if they did so. However, there are ways to mitigate that (e.g., a separate 'rfcxxxx compliant' mode). Even so, it will be important to get good participation from as many current implementers as possible.

Two nits in the charter text:

1) I don't think it's necessary to compare this effort to JSONPointer; they do different things (querying a document vs. referring to a particular part of a document), just as XPath and XPointer do different things. Each has a place, it's not a matter of compatibility or supplanting JSONPath. So, 'Other, incompatible approaches exist... but have not succeeded in supplanting JSONPath' should be removed.

2) If this charter is predicated on adopting a specific draft, it should be listed (e.g., as we did in <https://datatracker.ietf.org/doc/charter-ietf-quic/01/>).

Cheers,

> On 14 Sep 2020, at 10:02 am, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
> On Sun, Sep 13, 2020 at 9:39 AM Carsten Bormann <cabo@tzi.org> wrote:
> We now have had the discussion about a proposed charter over at the JSON Path list, and the resulting proposed charter, based on an initial proposal by Tim Bray, is at:
> 
> https://github.com/jsonpath-wg/charter/blob/master/charter.txt
> 
> I have set a reply-to to dispatch@ietf.org.  The IETF mailman recently has been ignoring that, so here’s the manual version: Please keep the discussion that is relevant to the dispatch process on the dispatch list (and keep spinoff threads that are not really relevant to that to the JSONPath list).
> 
> Unless the DISPATCH community has additional feedback over the next week or two, I'll take that text and start it on its journey.
> 
> -MSK
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

--
Mark Nottingham   https://www.mnot.net/