JavaScript Object Notation (JSON) Path
draft-normington-jsonpath-00
Document | Type |
Replaced Internet-Draft
(jsonpath WG)
Expired & archived
|
|
---|---|---|---|
Authors | Glyn Normington , Edward Surov , Marko Mikulicic , Stefan Gössner | ||
Last updated | 2020-12-22 (Latest revision 2020-12-07) | ||
Replaces | draft-goessner-dispatch-jsonpath | ||
Replaced by | draft-ietf-jsonpath-base | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-jsonpath-base | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
JSONPath defines a string syntax for identifying values within a JavaScript Object Notation (JSON) document. Note *This document is a work in progress and has not yet been published as an Internet Draft* (which needs to be fixed soon). Contributing This document picks up the popular JSONPath specification dated 2007-02-21 and provides a normative definition for it. In its current state, it is a strawman document showing what needs to be covered. Comments and issues can be directed at the github repository _insert repo here_ as well as (for the time when the more permanent home is being decided) at the dispatch@ietf.org mailing list.
Authors
Glyn Normington
Edward Surov
Marko Mikulicic
Stefan Gössner
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)