IETF Logo Mail Archive

Re: [Json] JSON merge alternatives

Mark Nottingham <mnot@mnot.net> Thu, 20 March 2014 00:13 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA5501A0830 for <json@ietfa.amsl.com>; Wed, 19 Mar 2014 17:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 uS_J08Q4X0KE for <json@ietfa.amsl.com>; Wed, 19 Mar 2014 17:13:09 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 001C51A0821 for <json@ietf.org>; Wed, 19 Mar 2014 17:13:08 -0700 (PDT)
Received: from [192.168.1.55] (unknown [118.209.54.174]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A6BFA22E255; Wed, 19 Mar 2014 20:12:58 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAK3OfOjASHcKqpN5XseawZqSv_G89kf3hr7046qTHH=p4c7__w@mail.gmail.com>
Date: Thu, 20 Mar 2014 11:12:55 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <86C8BE43-5CA4-4F33-AA49-7028C2CDF59B@mnot.net>
References: <20140319234549.GA3471@localhost> <8489D083-3871-4516-8FD3-32749645DBB4@mnot.net> <CAK3OfOjASHcKqpN5XseawZqSv_G89kf3hr7046qTHH=p4c7__w@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/lpW8KdFRhAn3J6Z2kkI6Y7TIDTI
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] JSON merge alternatives
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Mar 2014 00:13:11 -0000

On 20 Mar 2014, at 11:01 am, Nico Williams <nico@cryptonector.com> wrote:

> On Wed, Mar 19, 2014 at 6:56 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>  http://mailarchive.ietf.org/arch/msg/apps-discuss/mvUVvUt41tFTrPSOCfv7sfblTUM
> 
> I.e., draft-ietf-appsawg-json-merge-patch, which has the same problems
> mentioned recently on this list (e.g., using null to mean delete).

... and it's looking for an editor. Why not just take it over and gain consensus there?


> I suppose perhaps you're saying that JSON merge is an Apps area work
> item and should stay in Apps.  But I can't quite tell if that's what
> you meant.

I don't like venue shopping. json-merge-patch is still technically an active item in APPSAWG AIUI, so if you don't like it, you should discuss it over there.

Cheers,


--
Mark Nottingham   http://www.mnot.net/

v2.23.0 | Report a Bug | By Email