IETF Logo Mail Archive

Re: [apps-discuss] Confusing JSON Pointer

"Paul C. Bryan" <pbryan@anode.ca> Wed, 28 March 2012 02:46 UTC

Return-Path: <pbryan@anode.ca>
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 8C50521F86AB for <apps-discuss@ietfa.amsl.com>; Tue, 27 Mar 2012 19:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 UEww0wyOfI5p for <apps-discuss@ietfa.amsl.com>; Tue, 27 Mar 2012 19:46:24 -0700 (PDT)
Received: from maple.anode.ca (maple.anode.ca [72.14.183.184]) by ietfa.amsl.com (Postfix) with ESMTP id C994A21F86A0 for <apps-discuss@ietf.org>; Tue, 27 Mar 2012 19:46:24 -0700 (PDT)
Received: from [10.71.9.110] (adsl-75-55-201-218.dsl.pltn13.sbcglobal.net [75.55.201.218]) by maple.anode.ca (Postfix) with ESMTPSA id 460ED6456 for <apps-discuss@ietf.org>; Wed, 28 Mar 2012 02:46:23 +0000 (UTC)
Message-ID: <1332902780.2403.3.camel@neutron>
From: "Paul C. Bryan" <pbryan@anode.ca>
To: apps-discuss@ietf.org
Date: Tue, 27 Mar 2012 19:46:20 -0700
In-Reply-To: <CAJO=iut0J4wNDqtTcdPT14nkrw+x0nJiOPGNx2L+bk2vR9Ruew@mail.gmail.com>
References: <CAJO=ius8siusDXemCFQKy9=HOXs6L9eX108u7-OW3Rvu+L9qDw@mail.gmail.com> <4F7172FE.6060207@gmx.de> <CAJO=iuv2b1J8D=k5mTEYU3f564cYnXuiL=-83qKFm-kGAjSZOw@mail.gmail.com> <4F71CD46.5070603@gmx.de> <CAJO=iusKZo9DKynBL3vR11yL40t7X-DsndjXqQCRUUjMcxyE+w@mail.gmail.com> <1332898587.10875.5.camel@neutron> <CAJO=iut0J4wNDqtTcdPT14nkrw+x0nJiOPGNx2L+bk2vR9Ruew@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-qHStMg/hjpDtJBr2Kn7v"
X-Mailer: Evolution 3.2.2-1
Mime-Version: 1.0
Subject: Re: [apps-discuss] Confusing JSON Pointer
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: Wed, 28 Mar 2012 02:46:25 -0000

On Wed, 2012-03-28 at 11:04 +0900, 지송원 James Songwon Chi wrote:


> We have URI encoding and JSON String encoding. Why do we need another
> escape or encoding for JSON Pointer?


JSON Pointer needs a separator character to separate reference tokens.
The slash '/' character has proven to be the most intuitive separator to
date. If this character appears in a token, however, it needs to be
escaped so as not to be interpreted as a separator.

Paul

v2.46.0 | Report a Bug | By Email | System Status