Re: [art] [Technical Errata Reported] RFC6902 (6351)

On Wed, 9 Dec 2020, Ned Freed wrote:

> Maybe I'm missing something, but I don't see any actual error that needs to
> be corrected. Nor do I see it as an actual deficiency, so my recommendation
> is to reject.

I also see "all empty fields" in the report ... (!?), too. It is just the 
note which does no actually report an "error" in the RFC itself.

confused....

>
> 				Ned
>
>
>> The following errata report has been submitted for RFC6902,
>> "JavaScript Object Notation (JSON) Patch".
>
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid6351
>
>> --------------------------------------
>> Type: Technical
>> Reported by: Palle Cogburn <palle@4thex.com>
>
>> Section: GLOBAL
>
>> Original Text
>> -------------
>
>
>> Corrected Text
>> --------------
>
>
>> Notes
>> -----
>
>> If the patch elements included a property "previous" that contained the
>> original value in case of an operation such as "remove" for instance, it would
>> be easy to create the reverse operation - "add". In that way the path elements
>> can be used as audit records and it is easy to revert a path or even a part of
>> a patch, so the document is back to a previous version. All you have to do is
>> apply the reverse patch and also add those elements to the audit trail.
>
>> Is this something to consider adding to this document or is it an
>> implementation detail?
>
>> 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.
>
>> --------------------------------------
>> RFC6902 (draft-ietf-appsawg-json-patch-10)
>> --------------------------------------
>> Title               : JavaScript Object Notation (JSON) Patch
>> Publication Date    : April 2013
>> Author(s)           : P. Bryan, Ed., M. Nottingham, Ed.
>> Category            : PROPOSED STANDARD
>> Source              : Applications Area Working Group APP
>> Area                : Applications
>> Stream              : IETF
>> Verifying Party     : IESG
>
>> _______________________________________________
>> art mailing list
>> art@ietf.org
>> https://www.ietf.org/mailman/listinfo/art
>
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>

------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                         Senior Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

      PGP Key: https://www.cert.garr.it/servizi/informazioni-su-pgp-keys