IETF Logo Mail Archive

Re: [apps-discuss] JSON Patch

"Paul C. Bryan" <paul.bryan@forgerock.com> Wed, 23 November 2011 17:19 UTC

Return-Path: <paul.bryan@forgerock.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08C2621F8B27 for <apps-discuss@ietfa.amsl.com>; Wed, 23 Nov 2011 09:19:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.654
X-Spam-Level:
X-Spam-Status: No, score=-6.654 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E2YBMZmEM9G2 for <apps-discuss@ietfa.amsl.com>; Wed, 23 Nov 2011 09:19:29 -0800 (PST)
Received: from eu1sys200aog116.obsmtp.com (eu1sys200aog116.obsmtp.com [207.126.144.141]) by ietfa.amsl.com (Postfix) with SMTP id D65CA1F0C3F for <apps-discuss@ietf.org>; Wed, 23 Nov 2011 09:19:28 -0800 (PST)
Received: from mail-yw0-f47.google.com ([209.85.213.47]) (using TLSv1) by eu1sys200aob116.postini.com ([207.126.147.11]) with SMTP ID DSNKTs0rDvZcw9+2S8gh7NmaeQ/ushhwygVw@postini.com; Wed, 23 Nov 2011 17:19:29 UTC
Received: by mail-yw0-f47.google.com with SMTP id 20so1634609ywb.20 for <apps-discuss@ietf.org>; Wed, 23 Nov 2011 09:19:10 -0800 (PST)
Received: by 10.236.129.244 with SMTP id h80mr36288519yhi.130.1322068750696; Wed, 23 Nov 2011 09:19:10 -0800 (PST)
Received: from [192.168.1.3] (S0106a021b762dbb3.vf.shawcable.net. [174.1.40.184]) by mx.google.com with ESMTPS id m29sm25960146yhi.20.2011.11.23.09.19.07 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Nov 2011 09:19:08 -0800 (PST)
Message-ID: <1322068744.6133.1.camel@neutron>
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: apps-discuss@ietf.org
Date: Wed, 23 Nov 2011 09:19:04 -0800
In-Reply-To: <4ECCE93C.406@gmx.de>
References: <4EB1482E.1040600@adobe.com> <4EB14C2E.8040208@gmx.de> <1320254564.2622.37.camel@neutron> <4EBBA0DD.9020605@gmx.de> <4ECBC843.60900@gmx.de> <1321986297.2091.1.camel@neutron> <4ECCE93C.406@gmx.de>
Content-Type: multipart/alternative; boundary="=-rxW4rLNaKXEsVKQheAq7"
X-Mailer: Evolution 3.0.3-2
Mime-Version: 1.0
Subject: Re: [apps-discuss] JSON Patch
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Nov 2011 17:19:30 -0000

I'm now inclined to simply make "to" a JSON pointer as well.
Semantically it's clear, It's easy to apply, and JSON diff
implementations can be smart if they want and notice something moved
from one node in the graph to another.

Paul  

On Wed, 2011-11-23 at 13:38 +0100, Julian Reschke wrote:

> On 2011-11-22 19:24, Paul C. Bryan wrote:
> > Looks good to me. I don't think "end" is needed, as the end index can be
> > explicitly specified.
> > ...
> 
> Ack.
> 
> Also, we may want to say that to="" currently only allows an array 
> index; and that anything else is reserved for future use (such as moving 
> things around in the tree).
> 
> Best regards, Julian

v2.23.0 | Report a Bug | By Email