Re: [urn] query component in URNs

Keith Moore <moore@network-heretics.com> Mon, 25 February 2013 14:41 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 861F921F939A for <urn@ietfa.amsl.com>; Mon, 25 Feb 2013 06:41:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level:
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id beMZAAi0ogvr for <urn@ietfa.amsl.com>; Mon, 25 Feb 2013 06:40:59 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 881B621F9398 for <urn@ietf.org>; Mon, 25 Feb 2013 06:40:59 -0800 (PST)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D86ED20C22; Mon, 25 Feb 2013 09:40:58 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 25 Feb 2013 09:40:58 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=BaC2Y3pFJlph5bG7cV9xUo Tz1Lw=; b=GM4ZhpVqAtBNMB8F6vLAqGqbTsSckPnyHSi7vSilK7OpziunPKd0sP fqrJTHSBJjUsVATmjeNCPAMj6JNqV3ftnrpTbW285eVxqNdUP3GtOsKugZk5uPHW 3qt/uGemLcfAED3US0cFh+Kbqva7BaJqlPcZCQF7HAn7A5vLdtShc=
X-Sasl-enc: Tg3yAyySnoX1QkPH9H9qkLn/HfgWQRat4q44Ay8nHNh0 1361803258
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 36A5848277C; Mon, 25 Feb 2013 09:40:58 -0500 (EST)
Message-ID: <512B77F9.6060908@network-heretics.com>
Date: Mon, 25 Feb 2013 09:40:57 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Juha Hakala <juha.hakala@helsinki.fi>
References: <5125A74A.4030301@stpeter.im> <51298FD3.9030405@network-heretics.com> <512B2C81.3090901@helsinki.fi>
In-Reply-To: <512B2C81.3090901@helsinki.fi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: urn@ietf.org
Subject: Re: [urn] query component in URNs
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 14:41:00 -0000

On 02/25/2013 04:18 AM, Juha Hakala wrote:
> Hello,
>
> On 24.2.2013 5:58, Keith Moore wrote:
>>
>> Why should query semantics for URNs be different than for other URIs?
>
> Query semantics for URN will be richer than for other URIs due to 
> extra functionality supported by resolution services. Queries specific 
> to the URN will be processed by the appropriate URN resolution 
> service, which will not pass them on as such. Instead they will be 
> mapped to the form supported by the appropriate target system.

Uh, no.   The entire space of URI queries is specific to the target system.

In general, any resource (not just those named by URNs) is potentially 
able to have different services requested from it. That the URI syntax 
doesn't support a way to ask for each service is perhaps unfortunate, 
but for better or worse, that's the way it was designed.   Making the 
URI syntax work differently for URNs than the way it works for other 
resource names is not a good idea.

Keith