[art] [Errata Held for Document Update] RFC6902 (4787)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 23 February 2017 15:31 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B58D1299CF; Thu, 23 Feb 2017 07:31:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4PbYLb0onO_k; Thu, 23 Feb 2017 07:31:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10E621299CD; Thu, 23 Feb 2017 07:31:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 07C79B8105A; Thu, 23 Feb 2017 07:31:35 -0800 (PST)
To: d.frey@gmx.de, pbryan@anode.ca, mnot@mnot.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20170223153135.07C79B8105A@rfc-editor.org>
Date: Thu, 23 Feb 2017 07:31:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/pazwN_P0VYTnQK3pTJnFpArUS_o>
Cc: aamelnikov@fastmail.fm, art@ietf.org, text/plain@rfc-editor.org, charset=UTF-8@rfc-editor.org, rfc-editor@rfc-editor.orgContent-Type, iesg@ietf.org
Subject: [art] [Errata Held for Document Update] RFC6902 (4787)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 15:31:36 -0000
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 <d.frey@gmx.de> 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
- [art] [Errata Held for Document Update] RFC6902 (… RFC Errata System