IETF Logo Mail Archive

Re: [apps-discuss] Confusing JSON Pointer

지송원 James Songwon Chi <chi880466@gmail.com> Wed, 28 March 2012 03:33 UTC

Return-Path: <chi880466@gmail.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 8945E21E80CB for <apps-discuss@ietfa.amsl.com>; Tue, 27 Mar 2012 20:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.81
X-Spam-Level: *
X-Spam-Status: No, score=1.81 tagged_above=-999 required=5 tests=[AWL=-0.541, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1]
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 YtB1rCs+6vkf for <apps-discuss@ietfa.amsl.com>; Tue, 27 Mar 2012 20:33:12 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id F027121E801A for <apps-discuss@ietf.org>; Tue, 27 Mar 2012 20:33:11 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so497925vcb.31 for <apps-discuss@ietf.org>; Tue, 27 Mar 2012 20:33:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=8nH2vW+E4PA3+bH+bNksZSj9vwF4HYzrafpbaPl/0jo=; b=Zuilh8eIgEd0+V08QR/SD4ZYeVpewZdDwLpZTS3Nwe4h8nNtuAh7ijAAyLTUQPF3f1 +d9SAxk890SykXoVYDUwqrjmpztlqP90CQSWztuNggHeTJtShi3y6+hp/WHCK12MYpAQ DCOf7tNEt8iyX3EWIp6gznWNmpEJ3R7bbyVyZoSFx39LhCN0e5JezSDzS2VRmkSdznqr 4LpssLRD2uZMuaqhvP6xM/JbsdWrSNTb+R+JOzoryeBCcVtW+wsTukBrCyn79+BcQkcb 0EOPCDnrYFd199ZELJW6G7VD/+GD5QkaNpdZVQ8OSxPc/E3sqhZ7OSlMDds1hBGffaHk 6dXw==
MIME-Version: 1.0
Received: by 10.52.19.196 with SMTP id h4mr10998422vde.91.1332905591216; Tue, 27 Mar 2012 20:33:11 -0700 (PDT)
Received: by 10.220.1.4 with HTTP; Tue, 27 Mar 2012 20:33:11 -0700 (PDT)
In-Reply-To: <1332902780.2403.3.camel@neutron>
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> <1332902780.2403.3.camel@neutron>
Date: Wed, 28 Mar 2012 12:33:11 +0900
Message-ID: <CAJO=iusjfQEtrTvGm9+8G88TQac03raLEA6qkiQjpPy_shhoNQ@mail.gmail.com>
From: 지송원 James Songwon Chi <chi880466@gmail.com>
To: "Paul C. Bryan" <pbryan@anode.ca>
Content-Type: text/plain; charset="EUC-KR"
Content-Transfer-Encoding: quoted-printable
Cc: apps-discuss@ietf.org
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 03:33:12 -0000

2012년 3월 28일 오전 11:46, Paul C. Bryan <pbryan@anode.ca>님의 말:
> 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.

I prefer '/' as a reference-token separator. What I don't like is
using a caret(^) as a escape character.
In the draft 00, the escape character was a reverse solidus(\) but it
is changed to caret(^) in draft 01.
Is there something that I missed?

>
> Paul
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

--
James Chi

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