IETF Logo Mail Archive

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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Fri, 11 July 2014 05:51 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 1C7E41A0B13; Thu, 10 Jul 2014 22:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.013
X-Spam-Level: **
X-Spam-Status: No, score=2.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_ADOBE2=2.455, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] 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 qBXWwO6zmKC5; Thu, 10 Jul 2014 22:51:45 -0700 (PDT)
Received: from scintmta01-14.scbb.aoyama.ac.jp (scintmta.scbb.aoyama.ac.jp [133.2.253.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8A4201B280F; Thu, 10 Jul 2014 22:51:45 -0700 (PDT)
Received: from scmeg01-14.scbb.aoyama.ac.jp (scmeg01-14.scbb.aoyama.ac.jp [133.2.253.15]) by scintmta01-14.scbb.aoyama.ac.jp (Postfix) with ESMTP id 7DA1332E579; Fri, 11 Jul 2014 14:51:44 +0900 (JST)
Received: from itmail2.it.aoyama.ac.jp (unknown [133.2.206.134]) by scmeg01-14.scbb.aoyama.ac.jp with smtp id 4291_ce3f_45620044_8123_442e_88c4_e6f970a3cb88; Fri, 11 Jul 2014 14:51:43 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id BAA8CBFBD3; Fri, 11 Jul 2014 14:51:43 +0900 (JST)
Message-ID: <53BF7B51.3000208@it.aoyama.ac.jp>
Date: Fri, 11 Jul 2014 14:51:13 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>, Larry Masinter <masinter@adobe.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> <4e1c044bf224420f94d1ebfb584f40ff@BL2PR02MB307.namprd02.prod.outlook.com> <7B8DAF84-E799-46A5-BC55-5BF34000A548@vpnc.org> <4ee005b6cf4043b6b5cbe8493e82f14f@BL2PR02MB307.namprd02.prod.outlook.com> <4554206C-0046-4AF2-A893-55949EA9DCF5@vpnc.org >
In-Reply-To: <4554206C-0046-4AF2-A893-55949EA9DCF5@vpnc.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/json/jonZbZRitl5jvV3a5IicfMRIKbc
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: Fri, 11 Jul 2014 05:51:47 -0000

On 2014/07/11 03:53, Paul Hoffman wrote:
> On Jul 10, 2014, at 10:47 AM, Larry Masinter <masinter@adobe.com> wrote:

>> Here's an attempt:
>> ===
>>   The MergePatch operation is defined to operate at an object level,
>> not a textual level. There is no expectation that the MergePatch operation
>> will preserve  textual representation-level features such as white space,
>> member ordering, number precision beyond what is available in the
>> target's implementation, and so forth.
>>
>> In addition, even if the target implementation allows multiple name/value pairs
>> with the same name, the result of the patch operation on such
>> objects is not defined.
>> ===
>
> The first sentence uses "object" incorrectly because JSON uses that term for something else. It could bee better worded as "The MergePatch operation is defined to operate at the level of data items, not at the level of data representation."

Very much agreed about the "object" bit, but can we do
s/data representation/textual representation/,
please? "data items" and "data representation" sound too much like the 
same to me.

Regards,   Martin.

v2.23.0 | Report a Bug | By Email