Re: [urn] I-D Action: draft-ietf-urnbis-rfc3188bis-nbn-urn-04

Alfred Hönes <ah@TR-Sys.de> Mon, 22 October 2012 11:32 UTC

Return-Path: <A.Hoenes@TR-Sys.de>
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 E267121F8BAF for <urn@ietfa.amsl.com>; Mon, 22 Oct 2012 04:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.107
X-Spam-Level:
X-Spam-Status: No, score=-98.107 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, J_CHICKENPOX_33=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1YiSiHJL6uW1 for <urn@ietfa.amsl.com>; Mon, 22 Oct 2012 04:32:57 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1C221F8BB1 for <urn@ietf.org>; Mon, 22 Oct 2012 04:32:55 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA148485442; Mon, 22 Oct 2012 13:30:42 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id NAA29431; Mon, 22 Oct 2012 13:30:40 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201210221130.NAA29431@TR-Sys.de>
To: urn@ietf.org
Date: Mon, 22 Oct 2012 13:30:40 +0200 (MESZ)
In-Reply-To: <20121022112342.29635.28788.idtracker@ietfa.amsl.com> from "internet-drafts@ietf.org" at Oct "22, " 2012 "04:23:42" am
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 7bit
Subject: Re: [urn] I-D Action: draft-ietf-urnbis-rfc3188bis-nbn-urn-04
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: Mon, 22 Oct 2012 11:32:58 -0000

URNbis folks,  (again speaking as the draft editor)

we have arrived at uploading a new version of the URN:NBN draft,
which accommodates discussion since the last draft version in
spring and the implications from the "A way forward ..." changes
to the rfc2141bis and rfc3406bis draft versions already submitted
this week.

Juha did the bulk of the work, but again, I should be blamed for
all the nasty nits and flaws still buried in the document.
Juha will speak up and supply additional information ASAP.

For a quick summary of changes, please see below.

Text parts of this memo related to query directives will need
to be revisited after consolidation with NBN stakeholders;
we hope that there will be progress in this matter soon, once
the expected discussion on the core documents settles.

Please study this draft in detail and send draft text related
comments.  The plan is to issue one or two additional draft
versions (also depending on progress with the two core documents)
before proceeding to WG Last Call for this document.


A few minutes ago, internet-drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Uniform Resource Names, Revised
> Working Group of the IETF.
>
>    Title     : Using National Bibliography Numbers as Uniform Resource Names
>    Author(s) : Juha Hakala
>                Alfred Hoenes
>    Filename  : draft-ietf-urnbis-rfc3188bis-nbn-urn-04.txt
>    Pages     : 20
>    Date      : 2012-10-22
>
> Abstract:
>    National Bibliography Numbers, NBNs, are used by the national
>    libraries and other organizations in order to identify various
>    resources such as digitized monographs.  Generally, NBNs are applied
>    to resources that do not have an established (standard) identifier
>    system of their own.
>
>    A URN (Uniform Resource Names) namespace for NBNs was established in
>    2001 in RFC 3188.  Since then, several European national libraries
>    have implemented URN:NBN-based systems.
>
>    This document replaces RFC 3188 and defines how NBNs can be supported
>    within the updated URN framework.  A revised namespace registration
>    (version 4) compliant to the RFC 3406bis draft is included.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc3188bis-nbn-urn
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-urnbis-rfc3188bis-nbn-urn-04
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-urnbis-rfc3188bis-nbn-urn-04
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>


This new draft version contains the following incremental change
summary as an Appendix:

-------- snip --------

B.5.  draft-ietf-urnbis-rfc3188bis-nbn-urn-03 to -04

   -  specification of how to use URN query and fragment part based on
      the revised versions of rfc2141bis and rfc3406bis;
   -  various textual improvements and clarifications, including:
   -  textual alignments with rfc3187bis draft vers. -03;
   -  multiple editorial fixes and improvements.

-------- snip --------


Another Appendiz of the I-D contains the updated summary of essential
changes since RFC 3188:

-------- snip --------

Appendix A.  Significant Changes from RFC 3188

   Numerous clarifications based on a decade of experience with
   RFC 3188.

   Non-ISO 3166 (country code) based NBNs have been removed due to lack
   of usage.

   In accordance with established practice, the whole NBN prefix is now
   declared case-insensitive.

   Updated URN:NBN Namespace Registration template for IANA; whole
   document adapted to new URN Syntax document, RFC 2141bis, and new URN
   Namespace Registration document, RFC 3406bis.

   Use of query directives and fragment parts with this Namespace is now
   specified, in accordance with the aforementioned RFCs.

-------- snip --------


Best regards,
  Alfred.

~