Re: [Json] JSON merge alternatives

Nico Williams <nico@cryptonector.com> Thu, 20 March 2014 02:35 UTC

Return-Path: <nico@cryptonector.com>
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 63D461A0648 for <json@ietfa.amsl.com>; Wed, 19 Mar 2014 19:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 k5CwQV6gAsBc for <json@ietfa.amsl.com>; Wed, 19 Mar 2014 19:35:03 -0700 (PDT)
Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) by ietfa.amsl.com (Postfix) with ESMTP id E5AFB1A063F for <json@ietf.org>; Wed, 19 Mar 2014 19:35:03 -0700 (PDT)
Received: from homiemail-a30.g.dreamhost.com (unknown [69.163.253.160]) by hapkido.dreamhost.com (Postfix) with ESMTP id 3B78883FD8 for <json@ietf.org>; Wed, 19 Mar 2014 19:34:26 -0700 (PDT)
Received: from homiemail-a30.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a30.g.dreamhost.com (Postfix) with ESMTP id D01E021DE6A for <json@ietf.org>; Wed, 19 Mar 2014 19:34:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=YYZSIHRRPOCuhB94vjIX fycUxqI=; b=jMpJ4NpZv09je4jvd2kZ9EPj1jOAWytNla26PoBzzaui/p2GBeWS HJPphxm5ifjwp8nefqadYyT4sbCLQN0NfDhyoIVXulrGrfMIwblPv9MDu2Kp25HT 0fNmeYkW1ojhr/Bv6gvLS4LKtuWhFo42KGazrpnKS82FFF3eRk0oQtw=
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a30.g.dreamhost.com (Postfix) with ESMTPSA id 6D38821DE65 for <json@ietf.org>; Wed, 19 Mar 2014 19:34:25 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id hm4so5546718wib.2 for <json@ietf.org>; Wed, 19 Mar 2014 19:34:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7iH51efUP5x9D/PPoJlUIbPN+hbFhZL2/EPOosZufqw=; b=jvQprCP9d8FwYlFjT1lyjQdRULo6xfVsETWrd8F9uLsAd7a1TDMKrk544NgXodSPpF 9yScvEjuMTb9rH9D0A7QmvvgvwlwniBlOBTJcP/vWlLb1WtdWH884j6YXzMOncA5j2fk zXWogedKzAbn0tv97cD1ANep0g+wytNbsHmSIDWtUMU/pAJiVhAI9HPiDhVRvY0NdvEE vcSZvX7cM3jBX6RfyEN6c6ESi/LABfRXF45HKYx15cgZPyWsDkKmQelkmnjnlxMRtQNu 28E/SbpPQXH/g88hDL+SLR5CeH+qtGJa0sIUvccEDtSAFhG/OKI/ResJ1qaGNYi8TE8S SQpw==
MIME-Version: 1.0
X-Received: by 10.194.157.41 with SMTP id wj9mr32041001wjb.34.1395282864109; Wed, 19 Mar 2014 19:34:24 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Wed, 19 Mar 2014 19:34:24 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E115406DABA3@WSMSG3153V.srv.dir.telstra.com>
References: <20140319234549.GA3471@localhost> <255B9BB34FB7D647A506DC292726F6E115406DAAF6@WSMSG3153V.srv.dir.telstra.com> <CAK3OfOhfosk6Meue+cS7uiy5O1CqxPzCqUHddjTw1j+UMSY8rQ@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E115406DABA3@WSMSG3153V.srv.dir.telstra.com>
Date: Wed, 19 Mar 2014 21:34:24 -0500
Message-ID: <CAK3OfOjDBj4SyVyqzLsVHitzfzxsrCxE4Jdq67uTQcBMginOkQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "Manger, James" <James.H.Manger@team.telstra.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/Yhr5JgkkfF3waSSZoR7OCp2bmKw
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 02:35:05 -0000

On Wed, Mar 19, 2014 at 7:55 PM, Manger, James
<James.H.Manger@team.telstra.com> wrote:
>> Right.  Why not just drop draft-ietf-appsawg-json-merge-patch?
>
> Because it is creates intuitive and succinct patches for many most common cases.

Well, sure, but it should be possible to take an original and a patch
written in one style and convert to the other style locally, then
PATCH using the one style.

Having just one JSON PATCH schema is more likely to interop than having two.

Of course, the alternative style might still be useful even if it were
only useful locally.

I'll leave it to someone else, methinks, at least for now.

Nico
--