https://datatracker.ietf.org/wg/jsonpath/about/ Toggle navigation IETF Logo Datatracker Enable Javascript for full functionality. * Groups + By area/parent + Apps & Realtime + General + Internet + Ops & Mgmt + Routing + Security + Transport + IAB + IRTF + IETF LLC + Other o Active AGs o Active Areas o Active Directorates o Active Programs o Active RAGs o Active Teams o RSOC + + New work + Chartering groups + BOFs + BOF Requests + + Other groups + Concluded groups + Non-WG lists * Documents + Search + Recent drafts + Draft submission + + RFC streams + IAB + IRTF + ISE * Meetings + Next meeting + Agenda + Materials + Floor plan + Registration + Important dates + Request a session + Session requests + + Upcoming meetings + Upcoming meetings + + Past meetings + Past meetings + Meeting proceedings * Other + IPR disclosures + Liaison statements + IESG agenda + NomComs + Downref registry + Statistics o Drafts/RFCs o Meetings + Tutorials + API Help + Release notes + + Report a bug * User + Sign in + Password reset + Preferences + Handling of personal information + New account Sign in [ ] JSON Path (jsonpath) * About * Documents * Meetings * History * Photos * Email expansions * List archive >> WG Name JSON Path Acronym jsonpath Area Applications and Real-Time Area (art) State Active Charter charter-ietf-jsonpath-01 Approved Dependencies Document dependency graph (SVG) Additional - GitHub Organization Resources Personnel Chairs James Gruessing Tim Bray Area Director Francesca Palombini Mailing Address jsonpath@ietf.org list To subscribe https://www.ietf.org/mailman/listinfo/ jsonpath Archive https://mailarchive.ietf.org/arch/browse /jsonpath/ Jabber Room address xmpp:jsonpath@jabber.ietf.org?join chat Logs https://jabber.ietf.org/logs/jsonpath/ Charter for Working Group JSONPath is a syntax, originally based on the XML "XPath" design, which selects fields and values from a JSON document. It is used in a variety of applications which rely on JSON message formats. JSONPath was originally described by Stefan Goessner [1] but has never had an official specification of any kind, and the 39+ implementations, while mostly compatible, differ in certain behaviors. Note that while JSON Pointer (RFC 6901) is already standardised, it is designed to provide a reference to a single, specific part of a JSON document, whereas JSONPath provides the ability to query a document and potentially return multiple values. The WG will develop a standards-track JSONPath specification that is technically sound and complete, based on the common semantics and other aspects of existing implementations. Where there are differences, the working group will analyze those differences and make choices that rough consensus considers technically best, with an aim toward minimizing disruption among the different JSONPath implementations. Possible input documents are: * https://datatracker.ietf.org/doc/draft-goessner-dispatch-jsonpath/ * https://jsonpath-standard.github.io/internet-draft/ [1] https://goessner.net/articles/JsonPath/ Milestones Date Milestone 1 Jun 2021 Standards Track document defining JSON Path to the IESG --------------------------------------------------------------------- RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement About | IETF Datatracker | Version 7.41.0.p1 | 2021-12-10 | Report a bug: Tracker: Email: Python 3.6.12 | Django 2.2.25