Re: [Uri-review] Allow identifying issues with ISSN NID

Kristof Zelechovski <giecrilj@stegny.2a.pl> Wed, 20 May 2009 07:53 UTC

Return-Path: <giecrilj@stegny.2a.pl>
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 988F728C1E4 for <uri-review@core3.amsl.com>; Wed, 20 May 2009 00:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.051
X-Spam-Level: **
X-Spam-Status: No, score=2.051 tagged_above=-999 required=5 tests=[AWL=-1.035, BAYES_50=0.001, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpdhFjg6UyHF for <uri-review@core3.amsl.com>; Wed, 20 May 2009 00:53:22 -0700 (PDT)
Received: from shark.2a.pl (shark.2a.pl [195.117.102.3]) by core3.amsl.com (Postfix) with ESMTP id 65AD63A70EE for <uri-review@ietf.org>; Wed, 20 May 2009 00:53:21 -0700 (PDT)
Received: from av.2a.pl (av.2a.pl [195.117.102.9]) by shark.2a.pl (Postfix) with ESMTP id 389492A6A21; Wed, 20 May 2009 09:54:57 +0200 (CEST)
X-Virus-Scanned: amavisd-new at 2a.pl
Received: from shark.2a.pl ([195.117.102.3]) by av.2a.pl (av.2a.pl [195.117.102.9]) (amavisd-new, port 10024) with ESMTP id 2sv5BUmiT6zr; Wed, 20 May 2009 09:54:50 +0200 (CEST)
Received: from POCZTOWIEC (unknown [10.8.1.26]) by shark.2a.pl (Postfix) with ESMTPA id D1EA52A69E9; Wed, 20 May 2009 09:54:42 +0200 (CEST)
From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
To: 'David Booth' <david@dbooth.org>
References: <35A23FE7952844FBA667A306B8CDC982@POCZTOWIEC> <1242770385.12336.386.camel@dbooth-laptop>
Date: Wed, 20 May 2009 09:55:10 +0200
Message-ID: <B7FB6772505B40DB9AF8AA1E119240B4@POCZTOWIEC>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1242770385.12336.386.camel@dbooth-laptop>
Thread-Index: AcnY1Zg0WCzfg0q6TWOkp4k/KMHOhgASQeMg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: 'Slawek Rozenfeld' <rozenfeld@issn.org>, issnic@issn.org, uri-review@ietf.org
Subject: Re: [Uri-review] Allow identifying issues with ISSN NID
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 May 2009 07:53:23 -0000

Well said, but the only authority to provide such a PURL is ISSN.org, isn't
it?  (WorldCat.org does not allow to hyperlink to specific issues either.)
Until ISSN.org provides such functionality, there is no way to encode such
information in URL.  ISSN.org is big, it may take them three years to set
things up, if they ever consider it worth doing.
OTOH, an URN has the following advantages:
1.  It is not that arbitrary.  While I am unable to tell what the ISSN.org
prefix will be, I can imagine what form the URN should take.
2.  Until that happens, using a http prefix leads to HTTP 404, which is
uninformative and cannot be easily intercepted by a browser protocol
handler.
What do you think?
Chris

-----Original Message-----
From: David Booth [mailto:david@dbooth.org] 
Sent: Wednesday, May 20, 2009 12:00 AM
To: Kristof Zelechovski
Cc: 'Slawek Rozenfeld'; issnic@issn.org; uri-review@ietf.org
Subject: Re: [Uri-review] Allow identifying issues with ISSN NID

I don't see any reason why a URN should not be used to name a set of
resources.  That URN would have to be different from the URNs used to
name the individual members of that set though.  What document is
recommending otherwise?

However, I personally believe that http URIs are, in virtually all
cases, superior to URNs.  In essence, http URIs can serve the exact same
naming functions of URNs, but with the added benefit of *potentially*
being dereferenceable via an extremely widely implemented protocol --
HTTP.  This is further explained here:
http://dbooth.org/2006/urn2http/

David Booth



On Tue, 2009-05-19 at 21:51 +0200, Kristof Zelechovski wrote:
> Problem statement
> The ISSN NID syntax, as defined in RFC 3044, does not allow to
> identify specific issues of a serial publication.  It only identifies
> a serial publication, as a set of past and future issues.  This is an
> abstract entity and it is not in line with the prevailing URN practice
> that URN should be used to name concrete resources and not sets
> thereof.  While the present state of affairs is acceptable, the
> ability to identify specific issues is missing.