IETF Logo Mail Archive

Re: [apps-discuss] JSON Patch

"Paul C. Bryan" <paul.bryan@forgerock.com> Thu, 24 November 2011 07:55 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 57E3021F8AF5 for <apps-discuss@ietfa.amsl.com>; Wed, 23 Nov 2011 23:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.646
X-Spam-Level:
X-Spam-Status: No, score=-6.646 tagged_above=-999 required=5 tests=[AWL=-0.048, 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 P78u5qjMO+7K for <apps-discuss@ietfa.amsl.com>; Wed, 23 Nov 2011 23:55:06 -0800 (PST)
Received: from eu1sys200aog116.obsmtp.com (eu1sys200aog116.obsmtp.com [207.126.144.141]) by ietfa.amsl.com (Postfix) with SMTP id 337E721F8A96 for <apps-discuss@ietf.org>; Wed, 23 Nov 2011 23:55:06 -0800 (PST)
Received: from mail-gx0-f169.google.com ([209.85.161.169]) (using TLSv1) by eu1sys200aob116.postini.com ([207.126.147.11]) with SMTP ID DSNKTs34RrGCqIeogpMvaYcHtu0xFi/Fuwow@postini.com; Thu, 24 Nov 2011 07:55:06 UTC
Received: by ggnq1 with SMTP id q1so2795431ggn.0 for <apps-discuss@ietf.org>; Wed, 23 Nov 2011 23:54:45 -0800 (PST)
Received: by 10.236.183.52 with SMTP id p40mr39525036yhm.19.1322121285195; Wed, 23 Nov 2011 23:54:45 -0800 (PST)
Received: from [192.168.1.3] (S0106a021b762dbb3.vf.shawcable.net. [174.1.40.184]) by mx.google.com with ESMTPS id q5sm29483544yhm.7.2011.11.23.23.54.43 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Nov 2011 23:54:44 -0800 (PST)
Message-ID: <1322121282.2439.5.camel@neutron>
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: apps-discuss@ietf.org
Date: Wed, 23 Nov 2011 23:54:42 -0800
In-Reply-To: <4ECDEF31.9040801@it.aoyama.ac.jp>
References: <4EB1482E.1040600@adobe.com> <4EB14C2E.8040208@gmx.de> <1320254564.2622.37.camel@neutron> <4EBBA0DD.9020605@gmx.de> <4ECBC843.60900@gmx.de> <CABkgnnUCbMR3YOSu8dBPnrLSukBjMsiCh_rex6ojLc-UgH86OQ@mail.gmail.com> <4ECDEF31.9040801@it.aoyama.ac.jp>
Content-Type: multipart/alternative; boundary="=-DvbNhoxv9sIse3vBrZSQ"
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: Thu, 24 Nov 2011 07:55:07 -0000

After.

On Thu, 2011-11-24 at 16:16 +0900, "Martin J. Dürst" wrote:

> 
> On 2011/11/24 11:03, Martin Thomson wrote:
> > On 23 November 2011 03:05, Julian Reschke<julian.reschke@gmx.de>  wrote:
> >>    The "move" operation moves an existing array element. The "to" member
> >> indicates the array position as integer value. This operation is equivalent
> >> to removing the element identified by "move", an inserting it again at the
> >> position "to".
> >>    A JSON Patch document:
> >>
> >>    [
> >>        { "move": "/foo/1", "to": 2}
> >>    ]
> >
> > A thought occurred.  What about this?
> >
> > [
> >    { "move" : "/foo/1", "to": "/foo/2" }
> > ]
> 
> The syntax looks good. But what is /foo/2 in the "to" part exactly 
> referring to? Is is array position 2 after /foo/1 has been removed? Or 
> before?
> 
> Regards,    Martin.
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

v2.23.0 | Report a Bug | By Email