René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Consider implementing RFC 9535","articleBody":"IETF [RFC 9535](https://www.rfc-editor.org/rfc/rfc9535) defines a proposed standard for JSONPath. Other resources:\r\n\r\n* A partial [Compliance Test Suite](https://github.com/jsonpath-standard/jsonpath-compliance-test-suite).\r\n* Behaviours of various implementations can be checked in the [comparison project](https://cburgmer.github.io/json-path-comparison/). Please note that the JSONPath Reference Implementation referenced in the comparison project is stalled/archived and incomplete.\r\n* At the time of writing, online sandboxes for RFC 9535 are available [in C#](https://json-everything.net/json-path) and [in Rust](https://serdejsonpath.live/).\r\n* For more background and comments on the status of the CTS and RI, see this [this post](https://underlap.org/jsonpath-from-blog-post-to-rfc-in-17-years) (also [here](https://www.ietf.org/blog/jsonpath-rfc/) in the IETF blog).\r\n* Public discussion occurs in the IETF JSONPath Working Group's [mailing list](https://www.ietf.org/mailman/listinfo/jsonpath) ([archive](https://mailarchive.ietf.org/arch/browse/jsonpath/)).\r\n\r\n(See [here](https://underlap.org/implementing-jsonpath-rfc-9535) for updates to this list of resources.)\r\n\r\nValid approaches for this project are to (a) implement the RFC in whole or in part, (b) document its behaviour relative to the RFC, and (c) do nothing.","author":{"url":"https://github.com/glyn","@type":"Person","name":"glyn"},"datePublished":"2024-02-23T03:09:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/205/JSONPath/issues/205"}