From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: jsonpath@ietf.org
Reply-To: iesg@ietf.org
Subject: WG Review: JSON Path (jsonpath)
A new IETF WG has been proposed in the Applications and Real-Time Area. The
IESG has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send your
comments to the IESG mailing list (iesg@ietf.org) by 2020-10-19.
JSON Path (jsonpath)
-----------------------------------------------------------------------
Current status: Proposed WG
Chairs:
TBD
Assigned Area Director:
Murray Kucherawy <superuser@gmail.com>
Applications and Real-Time Area Directors:
Barry Leiba <barryleiba@computer.org>
Murray Kucherawy <superuser@gmail.com>
Mailing list:
Address: jsonpath@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/jsonpath
Archive: https://mailarchive.ietf.org/arch/browse/jsonpath/
Group page: https://datatracker.ietf.org/group/jsonpath/
Charter: https://datatracker.ietf.org/doc/charter-ietf-jsonpath/
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:
Feb 2021 - Standards Track document defining JSON Path to the IESG
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: jsonpath-chairs@ietf.org,
jsonpath@ietf.org,
The IESG <iesg@ietf.org>
Subject: WG Action: Formed JSON Path (jsonpath)
A new IETF WG has been formed in the Applications and Real-Time Area. For
additional information, please contact the Area Directors or the WG Chair.
JSON Path (jsonpath)
-----------------------------------------------------------------------
Current status: Proposed WG
Chairs:
Tim Bray <tbray@textuality.com>
Assigned Area Director:
Murray Kucherawy <superuser@gmail.com>
Applications and Real-Time Area Directors:
Barry Leiba <barryleiba@computer.org>
Murray Kucherawy <superuser@gmail.com>
Mailing list:
Address: jsonpath@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/jsonpath
Archive: https://mailarchive.ietf.org/arch/browse/jsonpath/
Group page: https://datatracker.ietf.org/group/jsonpath/
Charter: https://datatracker.ietf.org/doc/charter-ietf-jsonpath/
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:
Jun 2021 - Standards Track document defining JSON Path to the IESG