Re: [Json] [apps-discuss] merge-patch in APPSA and i-json in JSON
Paul Hoffman <paul.hoffman@vpnc.org> Tue, 08 July 2014 17:36 UTC
Return-Path: <paul.hoffman@vpnc.org>
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 2D7131A0395; Tue, 8 Jul 2014 10:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.108
X-Spam-Level: *
X-Spam-Status: No, score=1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_ADOBE2=2.455, HELO_MISMATCH_COM=0.553] 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 2n2wCs85XP-B; Tue, 8 Jul 2014 10:36:41 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79CAA1A0376; Tue, 8 Jul 2014 10:36:41 -0700 (PDT)
Received: from [10.20.30.90] (50-1-51-60.dsl.dynamic.fusionbroadband.com [50.1.51.60]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s68HaaZG049779 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 8 Jul 2014 10:36:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-51-60.dsl.dynamic.fusionbroadband.com [50.1.51.60] claimed to be [10.20.30.90]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <13c1732c5d504e84b80cd82e5e8f05ab@BL2PR02MB307.namprd02.prod.outlook.com>
Date: Tue, 08 Jul 2014 10:36:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE7ECD34-F035-46CC-B0B0-571039A86F3F@vpnc.org>
References: <13c1732c5d504e84b80cd82e5e8f05ab@BL2PR02MB307.namprd02.prod.outlook.com>
To: Larry Masinter <masinter@adobe.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/u8eHH1J3F5gbyZe203P7SAzb9IA
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] [apps-discuss] merge-patch in APPSA and i-json in JSON
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: Tue, 08 Jul 2014 17:36:42 -0000
On Jul 8, 2014, at 10:27 AM, Larry Masinter <masinter@adobe.com> wrote: > - Does application/merge-patch+json require/default to the i-json profile? No. draft-ietf-appsawg-json-merge-patch doesn't mention I-JSON. > - Is merge operation defined for target JSON that isn't i-json? Yes. The merge operation is defined for all targets, regardless of the targets' profile of JSON. > - If so, does it preserve i-json? (is the result i-json if the original was i-json? There is no assurance of that; it is orthogonal. draft-ietf-appsawg-json-merge-patch doesn't do anything special for any profile of JSON. > - Or is merge required to, or allowed to, ALWAYS produce i-json? No. draft-ietf-appsawg-json-merge-patch doesn't mention I-JSON. > You'd think it should be easy to answer these questions given the two documents. It is easy: draft-ietf-appsawg-json-merge-patch doesn't mention I-JSON. > Perhaps I'm missing the obvious. It seems that you are. draft-ietf-appsawg-json-merge-patch doesn't mention I-JSON. > If there's a problem, I'm not sure which one would need to change. Possibly both. Could we see some editorial collaboration to make the answers clearer? There is no reason for draft-ietf-appsawg-json-merge-patch to consider any profile of JSON. --Paul Hoffman
- [Json] merge-patch in APPSA and i-json in JSON Larry Masinter
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Paul Hoffman
- Re: [Json] [apps-discuss] merge-patch in APPSA an… John Cowan
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Paul Hoffman
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Carsten Bormann
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Paul Hoffman
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Larry Masinter
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Paul Hoffman
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Carsten Bormann
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Larry Masinter
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Paul Hoffman
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Larry Masinter
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Joe Hildebrand (jhildebr)
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Martin J. Dürst
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Martin J. Dürst
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Carsten Bormann
- Re: [Json] [apps-discuss] merge-patch in APPSA an… Carsten Bormann