Subject: [apps-discuss] [Errata Rejected] RFC6901 (3981)

From: RFC Errata System <[email-masked]>
Date: Wed, 7 May 2014 09:38:54 -0700 (PDT)

The following errata report has been rejected for RFC6901,
"JavaScript Object Notation (JSON) Pointer".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6901&eid=3981

--------------------------------------
Status: Rejected
Type: Technical

Reported by: David Phillips <[email-masked]>
Date Reported: 2014-05-06
Rejected by: Barry Leiba (IESG)

Section: 3

Original Text
-------------
See Notes

Corrected Text
--------------
The following two examples from section 5 are different:

Original: "/a~1b"
Proposed: "/a//b"

Original: "/m~0n"
Proposed: "/m~n"

The other examples are the same.

Notes
-----
The escape syntax seems weird and confusing. Rather than ~0 and ~1, why not use a repeated (double) slash to escape a slash? This is similar to how SQL escapes single quotes in string literals by using the single quote twice.

We have JSON functions in Presto (prestodb.io) that could benefit from an improved syntax (they currently use JSONPath), but I can't see understanding ~0 and ~1.
 --VERIFIER NOTES-- 
This is a change request, not an errata report.  The suggested change isn't directly acceptable, but could well be useful input into a new version of the specification.  In any case, it's not addressing an error, but a feature change.

--------------------------------------
RFC6901 (draft-ietf-appsawg-json-pointer-09)
--------------------------------------
Title               : JavaScript Object Notation (JSON) Pointer
Publication Date    : April 2013
Author(s)           : P. Bryan, Ed., K. Zyp, M. Nottingham, Ed.
Category            : PROPOSED STANDARD
Source              : Applications Area Working Group
Area                : Applications
Stream              : IETF
Verifying Party     : IESG