[urn] Fate of SICI namespace ?
Alfred Hönes <ah@TR-Sys.de> Wed, 17 November 2010 16:50 UTC
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@core3.amsl.com
Delivered-To: urn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E01628C0CE for <urn@core3.amsl.com>; Wed, 17 Nov 2010 08:50:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.735
X-Spam-Level:
X-Spam-Status: No, score=-97.735 tagged_above=-999 required=5 tests=[AWL=0.414, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 zKZxp6UlpF+T for <urn@core3.amsl.com>; Wed, 17 Nov 2010 08:50:08 -0800 (PST)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 7E9343A6936 for <urn@ietf.org>; Wed, 17 Nov 2010 08:50:07 -0800 (PST)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA239062636; Wed, 17 Nov 2010 17:50:36 +0100
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id RAA12594; Wed, 17 Nov 2010 17:50:35 +0100 (MEZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <201011171650.RAA12594@TR-Sys.de>
To: urn@ietf.org
Date: Wed, 17 Nov 2010 17:50:35 +0100
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 7bit
Subject: [urn] Fate of SICI namespace ?
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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, 17 Nov 2010 16:50:09 -0000
URN folks, As recalled in the Introduction of draft-hakala-rfc3187bis-isbn-urn and equally in the Introduction of draft-hakala-rfc3188bis-nbn-urn, RFC 2288 in February 1998 informally discussed the suitability of the SICI namespace as a URN namespace, amongst ISBN and ISBN. For the latter two bibliographic namespaces, a formal URN namespace definition has been produced each, but not for SICI. The aforementioned drafts, which are input for the URNBIS WG, have indicated the intent to "Update" RFC 2288. Working on the initial WG versions of the rfc3187bis-isbn-urn and rfc3188bis-nbn-urn I-Ds, we revisited this point and considered whether it would make more sense to move RFC 2288 to "Historic" status during the planned process of approval for RFC publication of rfc3187bis and rfc3188bis. Please have a look at RFC 2288 (if you haven't done so recently; it's a short RFC of only ~7 pages of text, and it's a good-to-know background for the upcoming discussion on the ISBN and NBN namespaces as well) and state your opinions on the list wrt the following point: (1) Is there any chance that an URN:SICI namespace will be defined and used in the foreseeable future? If "no" for (1), ... (2) Would it indeed make sense to declare RFC 2288 as "Historic" and/or "Obsoleted" by the new namespace definitions ? And: (3) Is there any content in RFC 2288 related to ISBNs and URN:ISBN that is still current and useful but not covered by draft-hakala-rfc3187bis-isbn-urn, and hence should be carried over into the WG version of that draft? (4) Is there any content in RFC 2288 related to ISSNs and URN:ISSN that is still current and useful but not covered by RFC 3044 and hence should be carried over into the revision of that RFC (that we are chartered to produce soon) ? The draft authors would appreciate affirmative answers to (3) and (4) being accompanied by suggested text snippets and an indication of where to add these! Kind regards, Alfred. _____ For ease of reference, here are URIs of HTML versions of the aforementioned documents and the other core documents we are going to work on, as well as the intended draft names for the upcoming working group documents: RFCs: http://tools.ietf.org/html/rfc2141 http://tools.ietf.org/html/rfc3406 http://tools.ietf.org/html/rfc2288 http://tools.ietf.org/html/rfc3044 http://tools.ietf.org/html/rfc3187 http://tools.ietf.org/html/rfc3188 (Don't forget to consider any RFC Errata linked from the headings of these pages!) Existing individual drafts (already formally expired or going to formally expire soon, awaiting to be replaced by WG drafts): http://tools.ietf.org/html/draft-ah-rfc2141bis-urn-02 http://tools.ietf.org/html/draft-hakala-rfc3187bis-isbn-urn-00 http://tools.ietf.org/html/draft-hakala-rfc3188bis-nbn-urn-00 Planned draft names for the chartered/upcoming WG drafts: draft-ietf-urnbis-rfc2141bis-urn draft-ietf-urnbis-rfc3406bis-urn-ns-reg draft-ietf-urnbis-rfc3044bis-issn-urn draft-ietf-urnbis-rfc3187bis-isbn-urn draft-ietf-urnbis-rfc3188bis-nbn-urn
- [urn] Fate of SICI namespace ? Alfred Hönes