IETF Logo Mail Archive

Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard

John C Klensin <john@jck.com> Sun, 16 December 2012 23:53 UTC

Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D938021F843A; Sun, 16 Dec 2012 15:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ESgJaY8cmme; Sun, 16 Dec 2012 15:53:31 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5980121F8430; Sun, 16 Dec 2012 15:53:31 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1TkO1O-0005ra-Iz; Sun, 16 Dec 2012 18:53:26 -0500
X-Vipre-Scanned: 034D352B002C31034D3678-TDI
Date: Sun, 16 Dec 2012 18:53:25 -0500
From: John C Klensin <john@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Mark Nottingham <mnot@mnot.net>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
Message-ID: <5C6A104276F197129659DF24@[192.168.1.128]>
In-Reply-To: <CAC4RtVDRt5xkvcpf54x0tkZpQcK6=r-WuhVPW5zisJD2pyn=-Q@mail.gmail.com>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net> <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com> <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net> <CAC4RtVCdE5jK4hm_wgzfrOQZ3edmYosyRz=xck06Hxz068AK_Q@mail.gmail.com> <CAC4RtVDRt5xkvcpf54x0tkZpQcK6=r-WuhVPW5zisJD2pyn=-Q@mail.gmail.c om>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 23:53:32 -0000

--On Sunday, December 16, 2012 18:12 -0500 Barry Leiba
<barryleiba@computer.org> wrote:

> Anyone have any comments on what I suggested below?

How about "+1" --complete agreement.  The terminology, if
interpreted in a "normal English" context, lies somewhere
between confusing and misleading and a precise local definition
is the more efficient fix.

   john

>...
> On Tue, Dec 11, 2012 at 11:25 PM, Barry Leiba
> <barryleiba@computer.org> wrote:
>>> Personally -- to me, it seems like you're getting hung up on
>>> the word "add."
>> ...
>>> "add" means what the format definition says it means,
>>> because otherwise we have to rationalise all of the
>>> different systems people might use it with to make sense.
>> 
>> OK, I'll buy that.  Then let's take a different approach, and
>> make it clearer that it's Humpty Dumpty's version of "add",
>> so maybe neither I nor Alice will get hung up on it:
>...

v2.23.0 | Report a Bug | By Email