Re: [urn] URN fragments

[Peter Saint-Andre <[e-mail]>]

-----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-----