Subject: Re: [Jsonpath] [art] [Editorial Errata Reported] RFC6901 (5745)

From: Carsten Bormann <[email-masked]>
Date: Mon, 7 Dec 2020 14:04:25 +0100

So should this now be processed (as rejected, I presume)?

(We are looking at the relationship between JSON Pointer and JSONPath in the jsonpath WG, and it would be nice to have an errata-free status of RFC 6901 to work from.)

Grüße, Carsten

> On 2019-06-06, at 04:24, Mark Nottingham <[email-masked]> wrote:
> 
> Sven,
> 
> That section of the specification is specifically about representing JSON pointers in JSON strings, which does require such escaping.
> 
> Recommend REJECT.
> 
> Cheers,
> 
>> On 5 Jun 2019, at 5:17 am, RFC Errata System <[email-masked]> wrote:
>> 
>> The following errata report has been submitted for RFC6901,
>> "JavaScript Object Notation (JSON) Pointer".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata/eid5745
>> 
>> --------------------------------------
>> Type: Editorial
>> Reported by: Sven Willenbücher <[email-masked]>
>> 
>> Section: 5
>> 
>> Original Text
>> -------------
>> The following JSON strings evaluate to the accompanying values:
>> 
>>   "/i\j"      5
>>   "/k\"l"      6
>> 
>> Corrected Text
>> --------------
>> The following JSON strings evaluate to the accompanying values:
>> 
>>   /i\j      5
>>   /k"l      6
>> 
>> Notes
>> -----
>> In JSON itself some special characters like the backslash and the double quote character can be escaped using a backslash. A similar escaping was not described for JSON pointers. Therefore it is not clear to me why such an escaping is needed in JSON pointers too. Maybe the additional double quotes around the example JSON pointers enforce this. In the corrected text I have stated my view on this.
>> 
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party  
>> can log in to change the status and edit the report, if necessary. 
>> 
>> --------------------------------------
>> 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 APP
>> Area                : Applications
>> Stream              : IETF
>> Verifying Party     : IESG
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 
> _______________________________________________
> art mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/art
> 
>