IETF Logo Mail Archive

Re: [urn] URN fragments

Jonathan A Rees <rees@mumble.net> Thu, 21 February 2013 13:56 UTC

Return-Path: <jonathan.rees@gmail.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 A84FE21F8AD8 for <urn@ietfa.amsl.com>; Thu, 21 Feb 2013 05:56:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 cIPHxjCSLIo2 for <urn@ietfa.amsl.com>; Thu, 21 Feb 2013 05:56:31 -0800 (PST)
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by ietfa.amsl.com (Postfix) with ESMTP id C06D021F841C for <urn@ietf.org>; Thu, 21 Feb 2013 05:56:19 -0800 (PST)
Received: by mail-wg0-f43.google.com with SMTP id e12so7518812wge.22 for <urn@ietf.org>; Thu, 21 Feb 2013 05:56:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2VVOomGSESeKEUDoqxh+JglpFt6LEjxpZrAk4ms/fRo=; b=rDxDWi2y7P9OdmrKhTBoB1MnOElgjU09PItl79gwMPaX8Jhr0qlEEeeTlkqRHY8ka3 Xqv60TTf5/t7b7zAGqyD1fqftfEfTG3rrMhKsroLPh8Xr7e80hKh2Pc1W4NuHOMzeMOl e6+C1l9cLuHfkudy5/FGraC1Lx7ylmYlDFE5+M08hdChzeEuG5bf06RtRoEWJtdDXTDc kT45Ngc0ATJ1LRFk9CEm6W0k/+vNnQgQKYJSsCuZSbXZJweBCKjxvty7yjW1pq8YRKGd 2VGsMP1iZfv1CwT1c7rpC9WM3HX6LQ2sWWIoAdOz7XCSaHpl06VP2Kn23pLIpE+GmDJz giAA==
MIME-Version: 1.0
X-Received: by 10.180.8.197 with SMTP id t5mr41640116wia.27.1361454978891; Thu, 21 Feb 2013 05:56:18 -0800 (PST)
Sender: jonathan.rees@gmail.com
Received: by 10.216.114.200 with HTTP; Thu, 21 Feb 2013 05:56:18 -0800 (PST)
In-Reply-To: <512606BC.7020902@helsinki.fi>
References: <512606BC.7020902@helsinki.fi>
Date: Thu, 21 Feb 2013 08:56:18 -0500
X-Google-Sender-Auth: QghKVBt_GoQU8_WXUJXHapCiaN4
Message-ID: <CAGnGFM+xKsW1F+pbBbX-98dCDTLXFX3OpfZo_W3Re9KAc_piXQ@mail.gmail.com>
From: Jonathan A Rees <rees@mumble.net>
To: Juha Hakala <juha.hakala@helsinki.fi>
Content-Type: multipart/alternative; boundary="f46d0442824065007f04d63c70f5"
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: Thu, 21 Feb 2013 13:56:34 -0000

On Thu, Feb 21, 2013 at 6:36 AM, Juha Hakala <juha.hakala@helsinki.fi>wrote:

>  Hello Peter; all,
>
> When fragment usage was last discussed on the list, the IETF community disapproved of the idea (if I remember correctly) on the basis that URNs will not be bound to a single manifestation of a resource, such as a PDF version of a book. When the file format changes, the probability that the fragment no longer works is too close for comfort to 1.
>
> That is not my recollection. The problem with defining fragment ids in the
urn: registration is that fragment id semantics comes from RFC 3986 and
simply cannot be changed or overridden by any URI scheme registration.
Quoth 3986:

   Fragment identifier semantics are independent of the
   URI scheme and thus cannot be redefined by scheme specifications.

Jonathan

v2.23.0 | Report a Bug | By Email