IETF Logo Mail Archive

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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Fri, 11 July 2014 05:41 UTC

Return-Path: <jhildebr@cisco.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 D357C1A8BB5; Thu, 10 Jul 2014 22:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.697
X-Spam-Level:
X-Spam-Status: No, score=-12.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 aAvqmCw1Hh15; Thu, 10 Jul 2014 22:41:20 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4409F1A0B13; Thu, 10 Jul 2014 22:41:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=786; q=dns/txt; s=iport; t=1405057286; x=1406266886; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uAB6O7awMc4ur25NEVgfhvfRp3Y2zSossxqaEpN5qJE=; b=UgU2VZIXggHA79vf/xq5wYxEyt54dn29doVLo7Co58DC/XHw7ciU5ns4 hbBy8SFbYACXsscENMSyIBMzd3yvk0h+3pt8cDuvx+H7blQgQZHoTY6Af V2foItVD7c4eLtFFQSbiq8m8s3PPG8r/SPILaJGZJfHX/Gv75+WdQTVX3 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AloFAI13v1OtJA2J/2dsb2JhbABZgw6BLIJxxAGBQwEZcBZ1hAQBAQQjEUUQAgEIGgImAgICMBUQAgQBDQWIQq0QmQYXgSyIUIUXMweCd4FMAQSbBZQbg0SCMA
X-IronPort-AV: E=Sophos;i="5.01,642,1400025600"; d="scan'208";a="59981383"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-2.cisco.com with ESMTP; 11 Jul 2014 05:41:25 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s6B5fJYg002986 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 11 Jul 2014 05:41:19 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Fri, 11 Jul 2014 00:41:19 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Larry Masinter <masinter@adobe.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Thread-Topic: [Json] [apps-discuss] merge-patch in APPSA and i-json in JSON
Thread-Index: AQHPnHA9h6TupY8iqkSHgrqZ5k9WgZuaGV0AgAC4lwA=
Date: Fri, 11 Jul 2014 05:41:18 +0000
Message-ID: <CFE5454D.5320D%jhildebr@cisco.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> <f1a0f112b4dc4fd0a0fe334272c9a996@BL2PR02MB307.namprd02.prod.outlook.com>
In-Reply-To: <f1a0f112b4dc4fd0a0fe334272c9a996@BL2PR02MB307.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.61.164.231]
Content-Type: text/plain; charset="utf-8"
Content-ID: <82C291942E022B4BB42788C320CAC40B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/json/5nyYyYc4KWQQDH6Y_vPP8-5visk
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:41:22 -0000

On 7/10/14, 10:40 PM, "Larry Masinter" <masinter@adobe.com> wrote:

>If most cases of JSON application specifications that
>need 'clean JSON input required for results to be
>meaningful' profiles can't use I-JSON as a basis
>for 'clean', it casts doubts as to defining I-JSON as
>a category, rather than just a set of best practices.

+1

I'd support having merge/patch both be valid I-JSON as well as only
operating on valid I-JSON (which are two separate requirements).

I don't care if that means you can't patch crufty JSON.

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email