Subject: [art] [Errata Held for Document Update] RFC6902 (4787)

From: RFC Errata System <[email-masked]>
Date: Thu, 23 Feb 2017 07:31:35 -0800 (PST)

The following errata report has been held for document update 
for RFC6902, "JavaScript Object Notation (JSON) Patch". 

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

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Daniel Frey <[email-masked]>
Date Reported: 2016-08-25
Held by: Alexey Melnikov (IESG)

Section: 4.2

Original Text
-------------
The "remove" operation removes the value at the target location.

The target location MUST exist for the operation to be successful.

For example:

{ "op": "remove", "path": "/a/b/c" }

If removing an element from an array, any elements above the
specified index are shifted one position to the left.

Corrected Text
--------------
The "remove" operation removes the value at the target location.

The target location MUST exist for the operation to be successful.

For example:

{ "op": "remove", "path": "/a/b/c" }

If removing an element from an array, any elements above the
specified index are shifted one position to the left.

The target location MUST NOT be a reference to the root. It is an
error in this document:

{ "op": "remove", "path": "" }

Notes
-----
The semantics of { "op": "remove", "path": "" } are never specified. If we allow to remove the root element, what would the result be? It would no longer be a valid JSON document, hence I propose to explicitly require the path of the "remove" operation to not reference the root.

Mark Nottingham: This isn't an errata; it would require gaining consensus and updating the document. See also: https://github.com/json-patch/json-patch2

--------------------------------------
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