Re: [urn] Finalizing items from IETF 83

Juha Hakala <juha.hakala@helsinki.fi> Thu, 28 June 2012 11:53 UTC

Return-Path: <juha.hakala@helsinki.fi>
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 8309521F85A8 for <urn@ietfa.amsl.com>; Thu, 28 Jun 2012 04:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iFCwG-sTxMuJ for <urn@ietfa.amsl.com>; Thu, 28 Jun 2012 04:53:00 -0700 (PDT)
Received: from smtp-rs1-vallila2.fe.helsinki.fi (smtp-rs1-vallila2.fe.helsinki.fi [128.214.173.75]) by ietfa.amsl.com (Postfix) with ESMTP id AC76521F85A5 for <urn@ietf.org>; Thu, 28 Jun 2012 04:52:58 -0700 (PDT)
Received: from [128.214.91.90] (kkkl25.lib.helsinki.fi [128.214.91.90]) by smtp-rs1.it.helsinki.fi (8.14.4/8.14.4) with ESMTP id q5SBqrbV007339 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 28 Jun 2012 14:52:54 +0300
Message-ID: <4FEC4595.1020609@helsinki.fi>
Date: Thu, 28 Jun 2012 14:52:53 +0300
From: Juha Hakala <juha.hakala@helsinki.fi>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.5) Gecko/20120605 Thunderbird/10.0.5
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <234FA8E3-C00D-4DA9-AD6C-41A3AC2548E4@hxr.us> <4FEBF708.9030604@helsinki.fi> <24637769D123E644A105A0AF0E1F92EF246915EE@dnbf-ex1.AD.DDB.DE> <4FEC2B8C.4070604@gmx.de>
In-Reply-To: <4FEC2B8C.4070604@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] Finalizing items from IETF 83
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, 28 Jun 2012 11:53:00 -0000

Hello,

On 28.6.2012 13:01, Julian Reschke wrote:
> On 2012-06-28 11:42, Svensson, Lars wrote:

>> I'll second that RFC 2141bis says that fragment identifiers are
>> allowed in URNs but that they are not part of the NSS. Further, RFCs
>> for new namespaces must specify if they allow the use of fragment
>> identifiers or not but I guess that is something for RFC 3406bis.
>
> No.
>
> Namespace specifications define the namespace-specific part; nothing
> else. Fragment syntax and semantics are defined by RFC 3986.
>
> A spec *can* point out that the URN does not identify something from
> which a payload + media type can be retrieved, in which fragment
> identifiers are not applicable. But that's different from disallowing them.

OK. It should be possible to adjust the text in rfc2141bis to say that 
there are namespaces in which fragment usage is not applicable since the 
resources which can be identified within than namespace - say, textual 
works as abstract entities in URN:ISTC - will not have fragments in the 
RFC 3986 sense of the word.

As far as I am concerned, it does no harm if the namespace registration 
request confirms that it is possible to use fragment to augment the 
functionality of the URNs from that particular namespace. For instance, 
I asked a permission from the ISBN Registration Authority to use 
fragments in the URN:ISBN namespace. Since this point will be made in 
the namespace registration request the national ISBN agencies and other 
ISBN users do not need to ask if fragments are allowed. And while some 
examples could be given in the namespace registration request it is 
definitely up to the URI Generic Syntax and other relevant technical 
documents to provide the necessary details for each document format.

All the best,

Juh
>
> Best regards, Julian

-- 

  Juha Hakala
  Senior advisor, standardisation and IT

  The National Library of Finland
  P.O.Box 15 (Unioninkatu 36, room 503), FIN-00014 Helsinki University
  Email juha.hakala@helsinki.fi, tel +358 50 382 7678