[apps-discuss] [Technical Errata Reported] RFC6902 (4419)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 17 July 2015 19:40 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 3E3BE1A009D for <apps-discuss@ietfa.amsl.com>; Fri, 17 Jul 2015 12:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 XSHR7PWyL4ol for <apps-discuss@ietfa.amsl.com>; Fri, 17 Jul 2015 12:40:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id DBEA21A003B for <apps-discuss@ietf.org>; Fri, 17 Jul 2015 12:40:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EF72218046E; Fri, 17 Jul 2015 12:36:24 -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: <20150717193624.EF72218046E@rfc-editor.org>
Date: Fri, 17 Jul 2015 12:36:24 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/9rXLi1qdD97-kE8GuRif1EZKYxg>
Cc: apps-discuss@ietf.org, brettz9@yaho.com, rfc-editor@rfc-editor.org
Subject: [apps-discuss] [Technical Errata Reported] RFC6902 (4419)
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: Fri, 17 Jul 2015 19:40:06 -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=4419 -------------------------------------- Type: Technical Reported by: Brett Zamir <brettz9@yaho.com> Section: A.14 Original Text ------------- An example target JSON document: { "/": 9, "~1": 10 } A JSON Patch document: [ {"op": "test", "path": "/~01", "value": 10} ] The resulting JSON document: { "/": 9, "~1": 10 } Corrected Text -------------- Proper JSON Pointer escaping should occur when resolving paths for application to the target document. An example target JSON document: { "/": 9, "~1": 10 } A JSON Patch document: [ {"op": "add", "path": "/~01", "value": 11} ] The resulting JSON document: { "/": 9, "~1": 11 } Notes ----- At http://tools.ietf.org/html/rfc6902#appendix-A.14 , I have a few issues: 1. Even though JSON Pointer is referenced elsewhere, I think reference ought to be made here to JSON Pointer in order to clarify what meaning "escape ordering" has here. 2. The operation indicated in this section is "test" which is not documented in its respective sections as returning any kind of document at all. I believe "add" or "replace" must have been the intended operation instead. And to make clear that the value of key "~1" would have actually been affected by such a modifying operation, the value in the result ought to differ from that in the original document. 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] [Technical Errata Reported] RFC690… RFC Errata System
- Re: [apps-discuss] [Technical Errata Reported] RF… Mark Nottingham
- Re: [apps-discuss] [Technical Errata Reported] RF… Manger, James
- Re: [apps-discuss] [Technical Errata Reported] RF… Barry Leiba
- Re: [apps-discuss] [Technical Errata Reported] RF… Barry Leiba
- Re: [apps-discuss] [Technical Errata Reported] RF… Mark Nottingham
- [apps-discuss] [Errata Rejected] RFC6902 (4419) RFC Errata System