Re: Extension Relation Type Comparison - LC Comment on draft-nottingham-http-plink-header-07

Mark Nottingham <mnot@mnot.net> Thu, 28 January 2010 04:27 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A77D3A697D for <apps-discuss@core3.amsl.com>; Wed, 27 Jan 2010 20:27:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.604
X-Spam-Level:
X-Spam-Status: No, score=-3.604 tagged_above=-999 required=5 tests=[AWL=-1.005, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JFylkBgfNUk for <apps-discuss@core3.amsl.com>; Wed, 27 Jan 2010 20:27:26 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 677D13A693C for <apps-discuss@ietf.org>; Wed, 27 Jan 2010 20:27:26 -0800 (PST)
Received: from chancetrain-lm.mnot.net (unknown [118.209.167.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id E594422E1F1; Wed, 27 Jan 2010 23:27:35 -0500 (EST)
Subject: Re: Extension Relation Type Comparison - LC Comment on draft-nottingham-http-plink-header-07
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343788056821@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Thu, 28 Jan 2010 15:27:32 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABA7C88D-17AC-46DB-BC71-3B7C9F829285@mnot.net>
References: <90C41DD21FB7C64BB94121FBBC2E72343788056821@P3PW5EX1MB01.EX1.SECURESERVER.NET>
To: Eran Hammer-Lahav <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1077)
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 28 Jan 2010 04:27:27 -0000

On 26/01/2010, at 4:03 AM, Eran Hammer-Lahav wrote:

> The current text about comparing extension relation types is unclear:
> 
>   When extension relation types are compared, they MUST be compared as
>   URIs in a case-insensitive fashion, character-by-character.  Because
>   of this, all-lowercase URIs SHOULD be used for extension relations.
> 
> What does it mean "compared as URIs"?
> 
> It is clear that these two URIs would be deemed equivalent:
> 
> http://example.com/rel/type
> HTTP://example.COM/rel/TYPE
> 
> But are they also equivalent to:
> 
> http://example.com:80/rel/type

None of those are equivalent; it specifies case-insensitive, character-by-character. "As URIs" alludes to the fact that an extension type might be serialised in a non-URI form; e.g., as a CURIE, if that's your cup of tea. 

I'll try to clarify this in the next draft.

Cheers,


--
Mark Nottingham     http://www.mnot.net/