[apps-discuss] [Editorial Errata Reported] RFC6902 (4460)
RFC Errata System <rfc-editor@rfc-editor.org> Sat, 29 August 2015 09:42 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52AC51AD06A for <apps-discuss@ietfa.amsl.com>; Sat, 29 Aug 2015 02:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 Tr1b5FgjoK2J for <apps-discuss@ietfa.amsl.com>; Sat, 29 Aug 2015 02:42:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id CE5AC1ACF60 for <apps-discuss@ietf.org>; Sat, 29 Aug 2015 02:42:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9D27F180478; Sat, 29 Aug 2015 02:41:48 -0700 (PDT)
To: pbryan@anode.ca, mnot@mnot.net, barryleiba@computer.org, superuser@gmail.com, alexey.melnikov@isode.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150829094148.9D27F180478@rfc-editor.org>
Date: Sat, 29 Aug 2015 02:41:48 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/E9dlgSIQP2E1nAtAPAcPnypR8S0>
Cc: hairmare@purplehaze.ch, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
Subject: [apps-discuss] [Editorial Errata Reported] RFC6902 (4460)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Aug 2015 09:42:11 -0000
The following errata report has been submitted 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=4460 -------------------------------------- Type: Editorial Reported by: Lucas Bickel <hairmare@purplehaze.ch> Section: 4.1 Original Text ------------- However, the object itself or an array containing it does need to exist, and it remains an error for that not to be the case. For example, an "add" with a target location of "/a/b" starting with this document: { "a": { "foo": 1 } } is not an error, because "a" exists, and "b" will be added to its value. It is an error in this document: { "q": { "bar": 2 } } because "a" does not exist. Corrected Text -------------- However, the object itself or an array containing it does need to exist, and it remains an error for that not to be the case. For example, an "add" with a target location of "/a/b" starting with this document: { "a": { "foo": 1 } } is not an error, because "a" exists, and "b" will be added to its value. It is an error in this document: { "q": { "bar": 2 } } because "a" does not exist. Considering a target location of "/a/1" it should be not be an error in this document: { "a": [ "foo" ] } while the same "add" into this document will be an error: { "a": [ ] } because "/a/0" does not exist. Notes ----- Adding to an object has such a nice example that explains the error cases. I think adding to a sequential array should have one as well. To my understanding this is already pretty clear from RFC6901, I feel it will make the spec easier to implement if we have an example right here. 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 (IESG) 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
- [apps-discuss] [Editorial Errata Reported] RFC690… RFC Errata System
- Re: [apps-discuss] [Editorial Errata Reported] RF… Barry Leiba
- [apps-discuss] [Errata Rejected] RFC6902 (4460) RFC Errata System