Re: [Json] [apps-discuss] merge-patch in APPSA and i-json in JSON

Larry Masinter <masinter@adobe.com> Thu, 10 July 2014 15:06 UTC

Return-Path: <masinter@adobe.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 3B4871A0A74; Thu, 10 Jul 2014 08:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 MiQdUHQAfOfr; Thu, 10 Jul 2014 08:06:07 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9265C1A043D; Thu, 10 Jul 2014 08:06:07 -0700 (PDT)
Received: from BL2PR02MB307.namprd02.prod.outlook.com (10.141.91.21) by BL2PR02MB305.namprd02.prod.outlook.com (10.141.91.17) with Microsoft SMTP Server (TLS) id 15.0.980.8; Thu, 10 Jul 2014 15:06:06 +0000
Received: from BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) by BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) with mapi id 15.00.0980.000; Thu, 10 Jul 2014 15:06:06 +0000
From: Larry Masinter <masinter@adobe.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Carsten Bormann <cabo@tzi.org>
Thread-Topic: [Json] [apps-discuss] merge-patch in APPSA and i-json in JSON
Thread-Index: Ac+a0HjpTP2xgtp6TJenjlRnxiyQMgAArESAAAMkzwAAL90UgAAOv/SAAAmD+MA=
Date: Thu, 10 Jul 2014 15:06:06 +0000
Message-ID: <4e1c044bf224420f94d1ebfb584f40ff@BL2PR02MB307.namprd02.prod.outlook.com>
References: <13c1732c5d504e84b80cd82e5e8f05ab@BL2PR02MB307.namprd02.prod.outlook.com> <DE7ECD34-F035-46CC-B0B0-571039A86F3F@vpnc.org> <20140708190635.GD6016@mercury.ccil.org> <4CB92BF6-A5A0-4598-A25F-C3F51E1DFFD5@tzi.org> <7E9AAC20-63CC-48EC-81EE-3F53CB3DEF83@vpnc.org>
In-Reply-To: <7E9AAC20-63CC-48EC-81EE-3F53CB3DEF83@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.184.24.49]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 0268246AE7
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(189002)(199002)(558084003)(92566001)(87936001)(33646001)(93886003)(21056001)(83322001)(66066001)(80022001)(46102001)(76576001)(74502001)(20776003)(85306003)(76482001)(2656002)(99396002)(64706001)(99286002)(95666004)(81342001)(31966008)(81542001)(106356001)(4396001)(107046002)(83072002)(85852003)(86362001)(101416001)(79102001)(77982001)(76176999)(50986999)(74316001)(54356999)(105586002)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR02MB305; H:BL2PR02MB307.namprd02.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
Archived-At: http://mailarchive.ietf.org/arch/msg/json/fdDJCfbUGj-5yp0TWbCF7ighB1s
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: Thu, 10 Jul 2014 15:06:10 -0000

> The MergePatch operation is defined at the level of the JSON data
> model.

This seems reasonable, but where do I find the "JSON data model"
described? I've looked in all of the JSON publications, RFCs, 
internet drafts, ECMA 262, 404.