Re: [urn] I-D Action: draft-ietf-urnbis-rfc2141bis-urn-01.txt

Peter Saint-Andre <stpeter@stpeter.im> Wed, 11 January 2012 23:35 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 0F47E21F853B for <urn@ietfa.amsl.com>; Wed, 11 Jan 2012 15:35:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.726
X-Spam-Level:
X-Spam-Status: No, score=-102.726 tagged_above=-999 required=5 tests=[AWL=-0.127, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 7-37vxEUXy59 for <urn@ietfa.amsl.com>; Wed, 11 Jan 2012 15:35:16 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 60DCA21F8539 for <urn@ietf.org>; Wed, 11 Jan 2012 15:35:16 -0800 (PST)
Received: from normz.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DCD5D40058; Wed, 11 Jan 2012 16:44:17 -0700 (MST)
Message-ID: <4F0E1CB3.8090703@stpeter.im>
Date: Wed, 11 Jan 2012 16:35:15 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Juha Hakala <juha.hakala@helsinki.fi>
References: <201110312002.VAA11600@TR-Sys.de> <4EC25AC6.9060404@helsinki.fi> <4EEBB2B6.5090801@stpeter.im> <4EF303AF.3030807@helsinki.fi>
In-Reply-To: <4EF303AF.3030807@helsinki.fi>
X-Enigmail-Version: 1.3.4
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: urn@ietf.org
Subject: Re: [urn] I-D Action: draft-ietf-urnbis-rfc2141bis-urn-01.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <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: Wed, 11 Jan 2012 23:35:17 -0000

<hat type='AD'/>

On 12/22/11 3:17 AM, Juha Hakala wrote:

> Peter Saint-Andre wrote:
>> Juha Hakala wrote:
>>> In chapter 2 <query> is discussed in the bottom of page 9 & top of the
>>> page 10. We should refer here to RFC2483 (which specifies the resolution
>>> services) and use an example which is based on an existing service. The
>>> current example is a bit puzzling; for the time being it is not possible
>>> to specify the type of metadata wanted because no such service exists.
>>
>> Could you clarify whether your statement refers to that particular
>> example or to resolution services as such?
> 
> I refer to the example in 2141bis. But my comment also makes the point
> that we should revise the URN services in such a way that the user can
> specify the type of metadata desired (the point made above in parenthesis).
>>
>>> A note should be added, saying that the services nailed down in RFC2483
>>> are not sufficient. For instance, it is not possible to specify what
>>> type of metadata is needed (descriptive / administrative / structural)
>>> and in which format (there are plenty of formats for descriptive
>>> metadata, such as MARC21 or Dublin Core). RFC2483 refers to URC (Uniform
>>> Resource Characteristics) which was never implemented in practice. (As
>>> an aside, there are plenty of other reasons for updating that RFC.)
>>
>> Isn't that a matter for RFC 2483 (or 2483bis), not the core URN spec?
>> There is no necessary connection between URNs and resolution, I think.
> 
> There is no need to add the note if revision of RFC 2483 is added to the
> charter of the URNBIS WG ;-). 

As long as I'm the Area Director (which is only through IETF 83), this
WG will not add any new items to its charter because it is already
behind schedule on delivering the work for which it was chartered.

Peter

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