Re: [Json] JSON merge alternatives
Nico Williams <nico@cryptonector.com> Thu, 20 March 2014 00:05 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 684DD1A0836 for <json@ietfa.amsl.com>; Wed, 19 Mar 2014 17:05:18 -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 FMugxEfBW44W for <json@ietfa.amsl.com>; Wed, 19 Mar 2014 17:05:17 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (unknown [69.163.253.172]) by ietfa.amsl.com (Postfix) with ESMTP id C197B1A0843 for <json@ietf.org>; Wed, 19 Mar 2014 17:05:17 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTP id 1BFFD350090 for <json@ietf.org>; Wed, 19 Mar 2014 17:05:09 -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=fvsf2VPrjzh+NLI/+71r SvafoWc=; b=EXlZYmjidKspT7yukAPWDtp5Vogry64eIYmVbzsS59pKLtELYKKN hdODsedYAKcgzTCC6rATxarPpvYCenAc5mJOWOiezOClVf3QyZfxum/iBNasot28 eTiQq6YCw+GBvthjQXC2guJBwY3xrg01/3gJuC0Bg3zYE40k2shEGic=
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTPSA id C385435008F for <json@ietf.org>; Wed, 19 Mar 2014 17:05:08 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id p61so55244wes.41 for <json@ietf.org>; Wed, 19 Mar 2014 17:05:07 -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=rtk94h5CAxjPf2Npe7D7VYDsBlxhfsdBRKfgWfv9zC8=; b=bOZ5ylAabvJL1lrvlrM5CjSHQAn4DBNhDeK+Yr40r/bbOESSN71bIFlnOk70xHKL8k 9K0w/OOyHh5CgTLWK90BFwb0wYl9gZiFXxBTHn1yvGgv1MxHydD+ad73uD62XdWhL2qT sgoDXvQb4Z7SKo81noMtfWR9+UDDfSpi2WJRc6brubnUFq20FSEs8fKYGCrGkRgbV1IX /PY74tJneQ2aLvqUAKUTdTvkKY8K+jJuSvdBWAHXvv4hU2uTckPKu5gs/YE1TeYXygI6 dSpV/i6nTXDqdjmJQt3+AgiR7FQXPqp85sea/vDDODg4J18nwlUNVeoUaZGKpyfA1D7O lONg==
MIME-Version: 1.0
X-Received: by 10.180.163.206 with SMTP id yk14mr22209319wib.5.1395273907764; Wed, 19 Mar 2014 17:05:07 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Wed, 19 Mar 2014 17:05:07 -0700 (PDT)
In-Reply-To: <8489D083-3871-4516-8FD3-32749645DBB4@mnot.net>
References: <20140319234549.GA3471@localhost> <8489D083-3871-4516-8FD3-32749645DBB4@mnot.net>
Date: Wed, 19 Mar 2014 19:05:07 -0500
Message-ID: <CAK3OfOgygcru6fHNH_niEN8gxx7LfmOizkGjJM9ZvEHux_za-w@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/vk16_r0K83fTNXlDq7VKpSWalC4
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:05:18 -0000
I was responding to the question about whether the JSON WG should re-charter to include JSON merge as a work item. 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. Nico --
- [Json] JSON merge alternatives Nico Williams
- Re: [Json] JSON merge alternatives Mark Nottingham
- Re: [Json] JSON merge alternatives Nico Williams
- Re: [Json] JSON merge alternatives Nico Williams
- Re: [Json] JSON merge alternatives Mark Nottingham
- Re: [Json] JSON merge alternatives Nico Williams
- Re: [Json] JSON merge alternatives Mark Nottingham
- Re: [Json] JSON merge alternatives Manger, James
- Re: [Json] JSON merge alternatives Nico Williams
- Re: [Json] JSON merge alternatives Manger, James
- Re: [Json] JSON merge alternatives Nico Williams
- Re: [Json] JSON merge alternatives Julian Reschke
- Re: [Json] JSON merge alternatives Stefan Drees
- Re: [Json] JSON merge alternatives Paul Hoffman