IETF Logo Mail Archive

Re: [apps-discuss] draft-pbryan-zyp-json-pointer: name syntax for non-ASCII

"Paul C. Bryan" <paul.bryan@forgerock.com> Mon, 21 November 2011 20:14 UTC

Return-Path: <paul.bryan@forgerock.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 40B3E11E80E1 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.675
X-Spam-Level:
X-Spam-Status: No, score=-6.675 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 1jLBD2pK-dKk for <apps-discuss@ietfa.amsl.com>; Mon, 21 Nov 2011 12:14:25 -0800 (PST)
Received: from eu1sys200aog103.obsmtp.com (eu1sys200aog103.obsmtp.com [207.126.144.115]) by ietfa.amsl.com (Postfix) with SMTP id 1AC7811E80DF for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:14:24 -0800 (PST)
Received: from mail-yx0-f174.google.com ([209.85.213.174]) (using TLSv1) by eu1sys200aob103.postini.com ([207.126.147.11]) with SMTP ID DSNKTsqxIA/0fUtkTlTVLt7UenRRS2WtwYLU@postini.com; Mon, 21 Nov 2011 20:14:25 UTC
Received: by yenq3 with SMTP id q3so5121812yen.19 for <apps-discuss@ietf.org>; Mon, 21 Nov 2011 12:14:23 -0800 (PST)
Received: by 10.50.217.195 with SMTP id pa3mr16019148igc.12.1321906463190; Mon, 21 Nov 2011 12:14:23 -0800 (PST)
Received: from [192.168.1.3] (S0106a021b762dbb3.vf.shawcable.net. [174.1.40.184]) by mx.google.com with ESMTPS id l28sm50191979ibc.3.2011.11.21.12.14.22 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Nov 2011 12:14:22 -0800 (PST)
Message-ID: <1321906460.1990.30.camel@neutron>
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: IETF Apps Discuss <apps-discuss@ietf.org>
Date: Mon, 21 Nov 2011 12:14:20 -0800
In-Reply-To: <n8blc7pieuu5kv58j096g6hnmjqea1qjl5@hive.bjoern.hoehrmann.de>
References: <4ECA5C66.1040305@gmx.de> <1321903463.1990.16.camel@neutron> <2n9lc79c8or4de9dpvi4s1s8vd186mosj8@hive.bjoern.hoehrmann.de> <1321905297.1990.20.camel@neutron> <n8blc7pieuu5kv58j096g6hnmjqea1qjl5@hive.bjoern.hoehrmann.de>
Content-Type: multipart/alternative; boundary="=-xIU4Iyro7SwF46Gf9fqh"
X-Mailer: Evolution 3.0.3-2
Mime-Version: 1.0
Subject: Re: [apps-discuss] draft-pbryan-zyp-json-pointer: name syntax for non-ASCII
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: Mon, 21 Nov 2011 20:14:26 -0000

Point taken. The intent of SHOULD in the text was to allow "/Björn" as a
JSON Pointer in a JSON string. Sounds like I should have separate
sections for expressing a JSON Pointer in JSON string vs. URI fragment,
and have clearer rules regarding the encoding of such values.

Paul

On Mon, 2011-11-21 at 21:09 +0100, Bjoern Hoehrmann wrote:

> If I recommended "When writing a new crime novel, reveal the perpetrator
> towards the end" then the author would still have to write the part, and
> the reader would still have to read through the novel to find out where
> the perpetrator is revealed, since the author might not be following the
> recommendation. Besides, the draft does not define a new scheme. This is
> just a matter of using the right incantation, but I don't know why, say,
> "/Björn" isn't allowed, so I can't make a good suggestion at the moment.

v2.23.0 | Report a Bug | By Email