Re: [apps-discuss] I-D Action: draft-ietf-appsawg-json-patch-01.txt
"Paul C. Bryan" <pbryan@anode.ca> Tue, 13 March 2012 15:18 UTC
Return-Path: <pbryan@anode.ca>
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 4543E21F86F6 for <apps-discuss@ietfa.amsl.com>; Tue, 13 Mar 2012 08:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 fgyf6eV1vhLk for <apps-discuss@ietfa.amsl.com>; Tue, 13 Mar 2012 08:18:53 -0700 (PDT)
Received: from maple.anode.ca (maple.anode.ca [72.14.183.184]) by ietfa.amsl.com (Postfix) with ESMTP id A2D2321F86EF for <apps-discuss@ietf.org>; Tue, 13 Mar 2012 08:18:53 -0700 (PDT)
Received: from [192.168.1.119] (unknown [209.97.219.224]) by maple.anode.ca (Postfix) with ESMTPSA id CB9526456 for <apps-discuss@ietf.org>; Tue, 13 Mar 2012 15:18:52 +0000 (UTC)
Message-ID: <1331651931.3301.6.camel@neutron>
From: "Paul C. Bryan" <pbryan@anode.ca>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Date: Tue, 13 Mar 2012 08:18:51 -0700
In-Reply-To: <9452079D1A51524AA5749AD23E003928086A22@exch-mbx901.corp.cloudmark.com>
References: <20120309212231.16366.52439.idtracker@ietfa.amsl.com> <CAD72A31-5857-4700-8A9A-EBBF21CA4256@gmail.com> <9452079D1A51524AA5749AD23E003928086A22@exch-mbx901.corp.cloudmark.com>
Content-Type: multipart/alternative; boundary="=-qzvdWCsV+BY3dLkJsYYK"
X-Mailer: Evolution 3.2.2-1
Mime-Version: 1.0
Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-json-patch-01.txt
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: Tue, 13 Mar 2012 15:18:54 -0000
I agree with Murray's points. Paul On Mon, 2012-03-12 at 20:55 +0000, Murray S. Kucherawy wrote: > > -----Original Message----- > > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Vadim Zaliva > > Sent: Saturday, March 10, 2012 10:33 PM > > To: apps-discuss@ietf.org > > Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-json-patch-01.txt > > > > I would like to suggest some extensions to this draft. I was trying to > > use proposed syntax in one of my project and found it lacking a couple > > of operations. Please find below my proposed extensions: > > > > Operation "add-unique" > > > > The new value appended the array only if the it presently does not > > contain an element with such value. If an element with such value > > already exists, the duplicate will not be added. > > This feels like feature creep to me. A patch to me is a sequence of steps for moving some content from one known state to another. This proposed capability allows one to move from an uncertain state to a known state. That might be a useful thing to do, but it's not something I think of as a "patch". > > > Operation "remove-all" > > > > This operations removes from array all elements with given value. > > I have the same concern here. > > > Operation "replace-all" > > > > This operations replaces in an array all elements with given value with > > a new value. > > And here. > > -MSK > _______________________________________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss
- [apps-discuss] I-D Action: draft-ietf-appsawg-jso… internet-drafts
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Vadim Zaliva
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Murray S. Kucherawy
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Mike Acar
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Paul C. Bryan
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Paul C. Bryan
- [apps-discuss] feedback on draft-ietf-appsawg-jso… Julian Reschke
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Paul C. Bryan
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Paul C. Bryan
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Paul C. Bryan
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Paul C. Bryan
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Mike Acar
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Murray S. Kucherawy
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Mike Acar
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Paul C. Bryan
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Murray S. Kucherawy
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Martin J. Dürst
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] I-D Action: draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Julian Reschke
- Re: [apps-discuss] feedback on draft-ietf-appsawg… Mark Nottingham