Re: [urn] URN fragments

Peter Saint-Andre <stpeter@stpeter.im> Tue, 26 February 2013 17:10 UTC

Return-Path: <stpeter@stpeter.im>
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 EC00E21F89E1 for <urn@ietfa.amsl.com>; Tue, 26 Feb 2013 09:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level:
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 MXDX3Vbodc34 for <urn@ietfa.amsl.com>; Tue, 26 Feb 2013 09:10:26 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D382921F86FA for <urn@ietf.org>; Tue, 26 Feb 2013 09:10:26 -0800 (PST)
Received: from [10.0.0.2] (unknown [24.9.182.250]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DEBD14004E; Tue, 26 Feb 2013 10:18:13 -0700 (MST)
Message-ID: <512CEC80.8020702@stpeter.im>
Date: Tue, 26 Feb 2013 10:10:24 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <512606BC.7020902@helsinki.fi> <5126E7D6.6050301@stpeter.im> <512716C6.4090308@helsinki.fi> <512CDC48.9070703@gmx.de>
In-Reply-To: <512CDC48.9070703@gmx.de>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] URN fragments
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: Tue, 26 Feb 2013 17:10:28 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/26/13 9:01 AM, Julian Reschke wrote:
> On 2013-02-22 07:57, Juha Hakala wrote:
>> Hi,
>> 
>> On 22.2.2013 5:36, Peter Saint-Andre wrote:
>>> Hi Juha, this model sounds similar to what you described for
>>> the query component: the fragment can be "added to the URN".
>>> I'm not sure what that means. When you add a query component or
>>> a fragment identifier to the URN, is that now a different URN
>>> (which wasn't assigned by the minting organization or in
>>> accordance with the minting algorithm)? Or is "a URN with some
>>> additional data appended" and therefore not really a URN
>>> anymore? Or is actually a URI (such as an HTTP URI) whose path 
>>> is the URN itself as just a string of characters embedded in
>>> the broader URI?
>> 
>> Despite the addition of fragment and query the URN itself remains
>> the same, even though the HTTP URI changes. ...
> 
> Well, it's a different string, thus a different URN.

Correct. As Martin suggested, one might refer to the
organizationally-assigned or algorithmically-determined URN as an
"absolute URN", but that doesn't change the fact that absolute+query
or absolute+fragment is still a different URN.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRLOx/AAoJEOoGpJErxa2p9aMQAKoZUm0Uq0Sa0xQ23TsmKqhL
i7C4PKkYJ8dpjKWJ65SVFTKn1jCr+td2oR+qNMny7MqGm58GTcmmkYmTPlCx39I8
UhpAXw3jL9HXScLpdUCGtV3IPPuiMVT+FLHfqVdXm/sbew/ICe9KwDVmCYKEve0y
fMzlW3PdQPPjncBjTFdHsPpmAVS/gn7NZ4sX7hD8q2bMn3Cym+bSjRRK8L4k/it8
h+xGPOXi6waOE4EfZJcL2Sme+4u5uN98aSE6lBxa1J1J9L8ZzNU7z1hhdrv+iztH
1yT1QaS2jEj5uN7V8dhI6LkRf3yy883j8WKyBs4BvLYQG++C+hboQgyAuh/O7+O5
LmHQtsLPQWjsNoawa2lceAs+MNcLVH3+PPkT6jJ3rxPDITYay/d/0Byr6SAPYs6Y
mfiWg5w+1A69KSEu+n9nJnpPyqoUZBjJ8YfiiwIr1F/Ft1NjFD2+vpTKGFsj06Ry
0xwZH5WMinlpMhXLnztKvWBgx/9d0RbLlxsYNvzw7+v1NM0dMmaAWfmr90g1Xiyq
h4t6RIaYRxkYsmEx3AEWDGw7jtV+rgUtI3Jf1qn8iS6R/BmIWYpyiKvuwVRu1Lke
apGp7nFROuv7g2AntWPi7Ur8av6TfZijllcmKSwhxAVHeKj5JU+BHz+BeZvlN5js
UbAwq+ORA7UFM8MtGlnR
=EMFB
-----END PGP SIGNATURE-----