Re: [Json] JSON merge alternatives
Julian Reschke <julian.reschke@gmx.de> Thu, 20 March 2014 07:23 UTC
Return-Path: <julian.reschke@gmx.de>
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 77D1F1A03DF for <json@ietfa.amsl.com>; Thu, 20 Mar 2014 00:23:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 ejAR8y9Q9DWS for <json@ietfa.amsl.com>; Thu, 20 Mar 2014 00:23:48 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 09CF51A0069 for <json@ietf.org>; Thu, 20 Mar 2014 00:23:48 -0700 (PDT)
Received: from [192.168.2.117] ([84.187.48.148]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M1iGk-1XEWNj3uOo-00tm0u; Thu, 20 Mar 2014 08:23:34 +0100
Message-ID: <532A9772.7050508@gmx.de>
Date: Thu, 20 Mar 2014 08:23:30 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>, Mark Nottingham <mnot@mnot.net>
References: <20140319234549.GA3471@localhost> <8489D083-3871-4516-8FD3-32749645DBB4@mnot.net> <CAK3OfOgygcru6fHNH_niEN8gxx7LfmOizkGjJM9ZvEHux_za-w@mail.gmail.com>
In-Reply-To: <CAK3OfOgygcru6fHNH_niEN8gxx7LfmOizkGjJM9ZvEHux_za-w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:yFNhXsUMh4caOUl6Ne8gZoAn+hdJhOOTG7qm50F4UDGIP7Hjcy+ V2RdGMTfMRX696DJsKk3r1I9Da3UNTISNnkpCEbX57YyBLVlRZ+ViLpvOrzWjyNDDZmzttL W1DfgjKQVOCOlB2WRjj89SDBPcynmVTo9ZCh9HpMbQKY5oxR1wjFG7H/A8hq7q10FUeePxB iJKg6lzllSAvxh0P/bMvw==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/RdEmH6yaRbDQ7QclgHn9k6m0MEU
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 07:23:49 -0000
On 2014-03-20 01:05, Nico Williams wrote: > 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 For the record: I believe this work is needed, but that it should happen over here. This WG has the necessary JSON expertise. Best regards, Julian
- [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