Re: [Json] JSON merge alternatives

Stefan Drees <stefan@drees.name> Thu, 20 March 2014 07:32 UTC

Return-Path: <stefan@drees.name>
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 C1E841A03DF for <json@ietfa.amsl.com>; Thu, 20 Mar 2014 00:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, 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 7AJbW_UALZ9I for <json@ietfa.amsl.com>; Thu, 20 Mar 2014 00:32:12 -0700 (PDT)
Received: from mout.web.de (mout.web.de [212.227.15.14]) by ietfa.amsl.com (Postfix) with ESMTP id 485BF1A0069 for <json@ietf.org>; Thu, 20 Mar 2014 00:32:12 -0700 (PDT)
Received: from newyork.local.box ([80.187.107.94]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0McFcd-1Wj2JS3lhv-00JYiw; Thu, 20 Mar 2014 08:32:02 +0100
Message-ID: <532A9970.9070606@drees.name>
Date: Thu, 20 Mar 2014 08:32:00 +0100
From: Stefan Drees <stefan@drees.name>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>, 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> <532A9772.7050508@gmx.de>
In-Reply-To: <532A9772.7050508@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:ImSDYR4MW+hPg1ycD+QLq3h9AoTdI0A9zRjaIoCuUBDi3MQEWUx DX898ZCvNzV5kDcdqBuPZ/vtmv8a9/LYXWcIAhBisoS8Gi6FXWAh2EH6YMTNT/l1OmThHVA lJKILdaJNya1j+ZZy1L+BGXDyVWVJlxy1mxoyLgZUoYUeW+EvWto/giDspbW2i4DvaoiXBK uV3KXx6B+DYQuWw9/HxUw==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/R4p_btcs46vyZJs3yiZc3gu1i0o
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
Reply-To: stefan@drees.name
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:32:14 -0000

On 2014-03-20 08:23 +01:00, Julian Reschke wrote:
> 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. ...

+1 for necessary format expertise when fiddling with format differencing

All the best,
Stefan.