Re: [apps-discuss] JSON Patch
"Manger, James H" <James.H.Manger@team.telstra.com> Sun, 27 November 2011 22:50 UTC
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F9A21F8C3A for <apps-discuss@ietfa.amsl.com>; Sun, 27 Nov 2011 14:50:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.428
X-Spam-Level:
X-Spam-Status: No, score=-2.428 tagged_above=-999 required=5 tests=[AWL=-2.127, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_14=0.6, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V5Sw8c-OkK2U for <apps-discuss@ietfa.amsl.com>; Sun, 27 Nov 2011 14:50:28 -0800 (PST)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE6A21F8C39 for <apps-discuss@ietf.org>; Sun, 27 Nov 2011 14:50:28 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.69,579,1315144800"; d="scan'208";a="55469919"
Received: from unknown (HELO ipcbvi.tcif.telstra.com.au) ([10.97.217.204]) by ipocvi.tcif.telstra.com.au with ESMTP; 28 Nov 2011 09:50:25 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6543"; a="43536354"
Received: from wsmsg3701.srv.dir.telstra.com ([172.49.40.169]) by ipcbvi.tcif.telstra.com.au with ESMTP; 28 Nov 2011 09:50:25 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3701.srv.dir.telstra.com ([172.49.40.169]) with mapi; Mon, 28 Nov 2011 09:50:25 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 28 Nov 2011 09:50:25 +1100
Thread-Topic: [apps-discuss] JSON Patch
Thread-Index: Acyrct3D1DZ3usldS5mC8VX3ZowDygB4J88w
Message-ID: <255B9BB34FB7D647A506DC292726F6E11389A699D1@WSMSG3153V.srv.dir.telstra.com>
References: <4EB1482E.1040600@adobe.com> <4EB14C2E.8040208@gmx.de> <1320254564.2622.37.camel@neutron> <4EBBA0DD.9020605@gmx.de> <4ECBC843.60900@gmx.de> <255B9BB34FB7D647A506DC292726F6E113884047C4@WSMSG3153V.srv.dir.telstra.com> <CABkgnnWMWL43cjBYpXP2tfxUCwLbt5Q2hYvBvtK3A6BKKhm=BA@mail.gmail.com> <4ECDEEC4.3050007@it.aoyama.ac.jp> <255B9BB34FB7D647A506DC292726F6E113885C474E@WSMSG3153V.srv.dir.telstra.com> <4ECF927D.4070809@gmx.de>
In-Reply-To: <4ECF927D.4070809@gmx.de>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] JSON Patch
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Nov 2011 22:50:29 -0000
>> JSON pointer theoretically needs a proper escaping mechanism since it reserves 1 char as a delimiter. However, choosing 1 char not to support avoids a fair amount of inevitable confusion and complexity. I chose U+FFFD REPLACEMENT CHARACTER. If you don’t like that choice, how about U+001F INFOMATION SEPARATOR ONE. > I like that; it avoids adding a whole new escaping sequence, and I think it's ok to sacrifice compatibility with identifiers that contain control characters. >> Not supporting pointers for names with, say, a U+FFFD char is not ideal but hinders almost no practical uses. >> Escaping '/' with '\/' could be worse. It seems certain to cause significant confusion. You can no longer simply split a pointer on '/' characters, but need to use, say, a regular expression to parse a pointer. A / can be legitimately escaped in a JSON string as "\/", and apparently often is [http://stackoverflow.com/questions/1580647/json-why-are-forward-slashes-escaped] so developers will read and write 0, 1, 2, or 3 backslashes (but only 1 %2F), when they are dealing with a name with a '/', or a '\'. Will "\x" be undefined when x isn’t \ or /? >> >> Object member name: >> Logically: Bjørn/Carsten and bar >> In JSON : "Bjørn/Carsten" and "bar" >> Or : "Bjørn\/Carsten" and "bar" >> >> JSON pointer: >> Logically: Bjørn\/Carsten/bar >> In JSON : "Bjørn\\/Carsten/bar" >> Or : "Bjørn\\\/Carsten\/bar" >> In IRI : Bjørn%2F/Carsten/bar >> ... > Not sure I get the example. Sorry for the confusing example, Julian. I meant to show a JSON pointer with 2 references. Eg a pointer to the value 3 in this JSON example: {"Bjørn/Carsten":{"bar":3}} I didn't get it quite right as I omitted the leading "/" that all pointers start with. -- James Manger
- [apps-discuss] JSON Patch Paul C. Bryan
- Re: [apps-discuss] JSON Patch Enrico Marocco
- Re: [apps-discuss] JSON Patch Graham Klyne
- Re: [apps-discuss] JSON Patch Mark Nottingham
- Re: [apps-discuss] JSON Patch Michael Dürig
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Paul C. Bryan
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Martin Thomson
- Re: [apps-discuss] JSON Patch Mark Nottingham
- Re: [apps-discuss] JSON Patch Paul C. Bryan
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Martin Thomson
- Re: [apps-discuss] JSON Patch Manger, James H
- Re: [apps-discuss] JSON Patch Graham Klyne
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Paul C. Bryan
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Paul C. Bryan
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Martin Thomson
- Re: [apps-discuss] JSON Patch Martin Thomson
- Re: [apps-discuss] JSON Patch Tony Hansen
- Re: [apps-discuss] JSON Patch Martin J. Dürst
- Re: [apps-discuss] JSON Patch Martin J. Dürst
- Re: [apps-discuss] JSON Patch Paul C. Bryan
- Re: [apps-discuss] JSON Patch Manger, James H
- Re: [apps-discuss] JSON Patch Julian Reschke
- Re: [apps-discuss] JSON Patch Manger, James H