Re: [Json] String comparisons -- LAST CHANCE ON PROPOSALS

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 12 June 2013 01:02 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97FCD21F9B8A for <json@ietfa.amsl.com>; Tue, 11 Jun 2013 18:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.54
X-Spam-Level:
X-Spam-Status: No, score=-103.54 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 vUSaekSNTQMA for <json@ietfa.amsl.com>; Tue, 11 Jun 2013 18:02:33 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id EEB4221F9B8B for <json@ietf.org>; Tue, 11 Jun 2013 18:02:31 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r5C12RHN020625; Wed, 12 Jun 2013 10:02:27 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 30bc_9158_bfc28dec_d2fb_11e2_80c1_001e6722eec2; Wed, 12 Jun 2013 10:02:26 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 3359CC00D8; Wed, 12 Jun 2013 10:01:14 +0900 (JST)
Message-ID: <51B7C896.40008@it.aoyama.ac.jp>
Date: Wed, 12 Jun 2013 10:02:14 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <0FBD58CE-748D-419A-8578-CCBF3FDF97CE@vpnc.org>
In-Reply-To: <0FBD58CE-748D-419A-8578-CCBF3FDF97CE@vpnc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] String comparisons -- LAST CHANCE ON PROPOSALS
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 12 Jun 2013 01:02:38 -0000

I prefer the second proposal (no surprise, I proposed it, and you can 
find the reasons for why I prefer it in the mail where I proposed it).
Of course, fixing key/keys to name/names to align terminology as pointed 
out by Stefan is great.

Regards,   Martin.

On 2013/06/12 2:44, Paul Hoffman wrote:
> Greetings again. The following thread has died off, with two proposals. If none of "leave the text in the draft as-is" or the following proposals would be acceptable to you, please propose specific text that would be acceptable.
>
> --Paul Hoffman
>
> Proposal 1
> ==========
> In Section 2.5. Strings, immediately before the ABNF add:
>
> For purpose of establishing key equality, comparisons MUST be conducted, after all unescaping is done, by comparing numeric character code points. There is to be no modification of any kind to the characters in keys, including case-changing or combining-form normalization.
>
> For example, the following four keys MUST be considered equivalent:
>
> * "\u002F"
> * "\u002f"
> * "\/"
> * "/"
>
> Proposal 2
> ==========
> In Section 2.5. Strings, immediately before the ABNF add:
>
> For purpose of establishing key equality, comparisons MUST be conducted, after all unescaping is done, by comparing numeric character code points. There MUST NOT be any modification of any kind to the characters in keys, including change of case or change between precomposed and decomposed forms.
>
> For example, the following four keys MUST be considered equivalent:
>
> * "\u002F"
> * "\u002f"
> * "\/"
> * "/"
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>