Re: [Json] JSON merge alternatives

Nico Williams <nico@cryptonector.com> Thu, 20 March 2014 00:42 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 430631A0835 for <json@ietfa.amsl.com>; Wed, 19 Mar 2014 17:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.753
X-Spam-Level: *
X-Spam-Status: No, score=1.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.793] 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 gOekNDq4D7_Q for <json@ietfa.amsl.com>; Wed, 19 Mar 2014 17:42:29 -0700 (PDT)
Received: from homiemail-a54.g.dreamhost.com (unknown [69.163.253.168]) by ietfa.amsl.com (Postfix) with ESMTP id 5899D1A0827 for <json@ietf.org>; Wed, 19 Mar 2014 17:42:29 -0700 (PDT)
Received: from homiemail-a54.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTP id AD9F040122422 for <json@ietf.org>; Wed, 19 Mar 2014 17:42:20 -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:content-transfer-encoding; s= cryptonector.com; bh=Jq59DQ53l0b+Ch97DksDwdMxYkI=; b=NT0nayssxdf YdSoppTBZSKapZmG/1dcqD5o0JsqkAZ7hlSExgHWYSmoOHOyubKE9S6bgWLnoPDT ldiOoB046hYzV+PQOD433KgFrH3cjk2YAIXQ/4Cis+3cm52Xgnqovod2cD58s9fk +Hez18DR6xCYzz2HGO6kR54O3kyrbeF0=
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTPSA id 5D9B8400F8A2A for <json@ietf.org>; Wed, 19 Mar 2014 17:42:20 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id p61so73180wes.27 for <json@ietf.org>; Wed, 19 Mar 2014 17:42:19 -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:content-transfer-encoding; bh=X6iyD1cEsDfbijk75je1gDK/iFBGgpT/+Chb8BKxlUw=; b=b23ehlAaGdR0czKCJzJlyvaUld7oBhAZxGQZ+451U/h3drYj8ygvX9ObzJZIdB0cPf L02DQPpSd5WKsoptGqBkw7StwllVBbH5mzfrTy17bIvAk2BEZONTU2UbhkfcSjk7Z2kv W89Lwe9ZKBKquSDfQCaIwKDZ+gzw9aGjS8vObhEzkTJUFRsBk/t5GmMligsMA7Sb89cF ru4jCfbVSzMx7/I2zS9Wg4Eiy54yj8Dmd40zlAcFBIR56qqtCoOdVUg6it+PAyf+ZA1d MHiwdl7wywDyRX84oGsIuI82W+lAl/4RxAlGZevw3ybU7k4irCqgRswTJFVGLq8/hhgD XfFQ==
MIME-Version: 1.0
X-Received: by 10.180.77.74 with SMTP id q10mr21781663wiw.39.1395276139379; Wed, 19 Mar 2014 17:42:19 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Wed, 19 Mar 2014 17:42:19 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E115406DAAF6@WSMSG3153V.srv.dir.telstra.com>
References: <20140319234549.GA3471@localhost> <255B9BB34FB7D647A506DC292726F6E115406DAAF6@WSMSG3153V.srv.dir.telstra.com>
Date: Wed, 19 Mar 2014 19:42:19 -0500
Message-ID: <CAK3OfOhfosk6Meue+cS7uiy5O1CqxPzCqUHddjTw1j+UMSY8rQ@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"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/json/TilVskwe1UJHZrR4pfuO8piZR-c
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:42:30 -0000

On Wed, Mar 19, 2014 at 7:35 PM, Manger, James
<James.H.Manger@team.telstra.com> wrote:
> RFC 6902 "JavaScript Object Notation (JSON) Patch" looks quite close to proposal 2.
> Media type: application/json-patch+json
> Operations: add, remove, replace, move, copy, test

Perfect.  Now I don't have to edit any I-Ds for this.

> draft-ietf-appsawg-json-merge-patch "JSON Merge Patch" is a simpler subset of proposal 1. It is designed to work well with JSON objects, and objects nested in objects etc. Its main limitation (compared to proposal 1) is that it doesn't support insert/replace for individual array elements.

Right.  Why not just drop draft-ietf-appsawg-json-merge-patch?

> Adding a "merge" operation to RFC 6902 would be another way to get the best of both these approaches.

Maybe, but I don't need it.

Thanks for the pointer to RFC6902!

Nico
--