[apps-discuss] [Technical Errata Reported] RFC6902 (4596)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 21 January 2016 05:23 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 14C651B2F65 for <apps-discuss@ietfa.amsl.com>; Wed, 20 Jan 2016 21:23:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 oQiPYT3mLYs5 for <apps-discuss@ietfa.amsl.com>; Wed, 20 Jan 2016 21:23:46 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id B273F1B2F64 for <apps-discuss@ietf.org>; Wed, 20 Jan 2016 21:23:46 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2C2DC180092; Wed, 20 Jan 2016 21:22:33 -0800 (PST)
To: pbryan@anode.ca, mnot@mnot.net, barryleiba@computer.org, superuser@gmail.com, alexey.melnikov@isode.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160121052233.2C2DC180092@rfc-editor.org>
Date: Wed, 20 Jan 2016 21:22:33 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/XtKu1jbpUQ3SsrozHZy-fXEnu6g>
Cc: jeromem@ca.ibm.com, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
Subject: [apps-discuss] [Technical Errata Reported] RFC6902 (4596)
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: Thu, 21 Jan 2016 05:23:48 -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=4596

--------------------------------------
Type: Technical
Reported by: Missing 'Append' operation <jeromem@ca.ibm.com>

Section: GLOBAL

Original Text
-------------
Its value MUST be one of "add", "remove", "replace", 
"move", "copy", or "test"; other values are errors. 

Corrected Text
--------------
Its value MUST be one of "add", "append", "remove", 
"replace", "move", "copy", or "test"; other values are errors. 

... and more text to add the 'append' op description.

Notes
-----
There is a key missing piece to this RFC.  You can do { "op": "add", "path": "/attr", "value": "val"}, which will add or modify the 'attr' attribute, if it exists or not.  However, you cannot add an item to a potentially non-existing array.  Updating an array that may or may not exists, forces the client to always call GET on the resource.   See this API spec:  https://orchestrate.io/docs/apiref#keyvalue-patch  which implements the op 'append', which would solve this problem.

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