[Uri-review] Allow identifying issues with ISSN NID

Kristof Zelechovski <giecrilj@stegny.2a.pl> Tue, 19 May 2009 19:50 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 6B0543A6E00 for <uri-review@core3.amsl.com>; Tue, 19 May 2009 12:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.706
X-Spam-Level: *
X-Spam-Status: No, score=1.706 tagged_above=-999 required=5 tests=[AWL=-1.381, BAYES_50=0.001, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_MESSAGE=0.001]
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 WG3cyyhN93Jb for <uri-review@core3.amsl.com>; Tue, 19 May 2009 12:50:01 -0700 (PDT)
Received: from shark.2a.pl (shark.2a.pl [195.117.102.3]) by core3.amsl.com (Postfix) with ESMTP id E92F53A6B79 for <uri-review@ietf.org>; Tue, 19 May 2009 12:50:00 -0700 (PDT)
Received: from av.2a.pl (av.2a.pl [195.117.102.9]) by shark.2a.pl (Postfix) with ESMTP id E87C42A69B5; Tue, 19 May 2009 21:51:36 +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 r1yz-jw59wHi; Tue, 19 May 2009 21:51:25 +0200 (CEST)
Received: from POCZTOWIEC (unknown [10.8.1.26]) by shark.2a.pl (Postfix) with ESMTPA id 8AB2E2A69DC; Tue, 19 May 2009 21:51:24 +0200 (CEST)
From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
To: 'Slawek Rozenfeld' <rozenfeld@issn.org>
Date: Tue, 19 May 2009 21:51:48 +0200
Message-ID: <35A23FE7952844FBA667A306B8CDC982@POCZTOWIEC>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0065_01C9D8CC.06211850"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcnYuz56CgPTAuKiTEahos1IO3uFHw==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: issnic@issn.org, uri-review@ietf.org
Subject: [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: Tue, 19 May 2009 19:50:08 -0000

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.


Use case


The authorities of Republic of Poland publish the acts of law in a serial
publication called The Journal of Statutes with the corresponding URN
urn:ISSN:0867-3411.  It is common for Web content related to Polish law to
refer to individual acts of law contained within this publication; this URN
is not sufficient for the purpose.


Benefits


Allowing ISSN NID to refer to fragments of particular publications would
allow: 

*	content management systems - to supply the correct human-readable
reference to the fragment,
*	Web browser protocol handlers - to provide textual information about
the availability of the particular issue both in printed and downloadable
form.


Proposed Solution


Allow extended ISSN of the form urn:ISSN:0867-3411:2001:72#747, meaning year
2001, issue 72, position 747, where:

*         The format of the year part is four digits.  

*         The format of the issue number part is generally a number but it
depends on the publication; several publications have several versions of
the same issue with varying components; the versions are distinguished by an
alphabetic suffix appended to the issue number.  Formally, the issue number
can contain any characters allowed in an URI, except the reserved characters
as defined by RFC 3986 and the colon character ":", and can contain
percent-encoded characters in the UTF-8 character set.  The colon character
is not allowed because it is reserved for future development.  

*         The meaning of the fragment identifier depends on the particular
publication and it is not defined by the present specification.  The
fragment identifier is supposed to be the position number for scientific and
legal journals that maintain running position numbers, which constitute the
majority of use cases of references to serial publications.  It should also
be possible to address a range of pages within an issue using the syntax
urn:ISSN:0867-3411:2001:72#pages=247-259 ; this way of identifying a
fragment is deprecated when position numbers are provided by the editor.


Known problems


ISSN URN can resolve to electronic publications available in various media
types as well as printed publications.  The meaning of the fragment
identifier part as defined above is valid for printed publications only.  As
the interpretation of fragment identifiers is different for different media
types, the fragment identifier, if carried over from the ISSN URN without
reinterpretation, need not denote a valid fragment identifier in the sense
of the media type of the resource retrieved.  However, if the human reader
can see the identifier of the fragment that is being referred to, he can
find it in the retrieved resource by reading it as if it were a printed
publication.