W3C home > Mailing lists > Public > www-tag@w3.org > March 2010

Re: FW: New Version Notification for draft-hakala-rfc3187bis-isbn-urn-00 (fwd)

From: Jonathan Rees <jar@creativecommons.org>
Date: Mon, 22 Mar 2010 11:27:35 -0400
Message-ID: <760bcb2a1003220827l2b4fe2bcyb18576931516dd70@mail.gmail.com>
To: Larry Masinter <LMM@acm.org>
Cc: www-tag@w3.org
cool... more confirmation that people are willing to use http: URIs as names:

   ...URNs are therefore
   expressed in the form http://urn.fi/<URN>.  For example, the URN
   http://urn.fi/URN:ISBN:978-952-10-3937-9 identifies Sami Nurmi's
   doctoral dissertation "Aspects of Inflationary Models at Low Energy
   Scales".

I'm taking this out of context of course, and 'the URN' might be a
typo for 'the URL'. I think what they mean is that if you have an ISBN
and want to turn it into a hyperlink, you have to hunt down a service
(in this case urn.fi) that can "resolve" it and figure out how to make
an http: URI that resolves using the service. Sort of like ARK when
the key's "home" domain has gone south.

   resolving the same URN in multiple locations
   may provide different services; the national bibliography may be able
   to provide bibliographic information only, while the publisher can
   also provide the book itself, on its own terms

This goes back to my earlier question: if a URI 200-resolves to
metadata (or worse, resolves to either metadata or data on whim, as
these URIs and handle system URIs do), how do we feel about the URI
naming or "identifying" the data? The httpRange-14 rule is silent on
this question, but the ISSUE-14 idea that motivated the rule is that
you need distinct names for thing and description of thing. This would
say we want separate URIs in the IR case (e.g. books, journal
articles) just as we do for other resources (e.g. people, classes).
This draft URN registration is a good test of both the coherence and
the marketability of the intended architecture.

Good find, Larry!

Jonathan

On Mon, Mar 22, 2010 at 9:48 AM, Larry Masinter <LMM@acm.org> wrote:
> speaking of persistent naming...
>
> -----Original Message-----
> From: urn-nid-bounces@ietf.org [mailto:urn-nid-bounces@ietf.org] On
> Behalf Of Alfred HÎnes
> Sent: Monday, March 22, 2010 6:27 AM
> To: urn-nid@ietf.org; apps-discuss@ietf.org
> Subject: New Version Notification for
> draft-hakala-rfc3187bis-isbn-urn-00 (fwd)
>
> Folks,
> we have posted a RFC 3187-bis initial draft (see below).
>
> This work is part of the PersID project to establish an international
> network of stable resolution services for Persistent Identifiers
> (URNs),
> in particular for Bibliographic identifiers.
>
> To give this work a more solid ground, updates to the basic
> URN-related
> documents (RFC 2141 and RFC 3406) and URN namespace-specific RFCs are
> planned, and brought to the IETF, in order to bring these documents
> in alignment with current IETF Full Standards and IANA procedures.
>
> The ultimate goal is to establish a dedicated 'urnbis' WG in the IETF,
> hopefully by this summer, with an ambitious schedule to bring revised
> documents initially targetting PS / BCP status to the IESG, with the
> goal of fast progression of RFC 2141-bis on the Standards Track.
>
>
> Kind regards,
>  Alfred HÎnes.
>
> --
>
> +------------------------+--------------------------------------------
> +
> | TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.
> |
> | Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18
> |
> | D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de
> |
> +------------------------+--------------------------------------------
> +
>
>
> ----- Forwarded message from IETF I-D Submission Tool -----
>
>> Message-Id: <20100322130444.4400D28C0F6@core3.amsl.com>
>> Date: Mon, 22 Mar 2010 06:04:44 -0700 (PDT)
>> Subject: New Version Notification for
> draft-hakala-rfc3187bis-isbn-urn-00
>
> A new version of I-D, draft-hakala-rfc3187bis-isbn-urn-00.txt
> has been successfully submitted by Alfred Hoenes and posted
> to the IETF repository.
>
> Filename:  draft-hakala-rfc3187bis-isbn-urn
> Revision:  00
> Title:     Using International Standard Book Numbers as Uniform
> Resource Names
> Creation_date:   2010-03-22
> WG ID:           Independent Submission
> Number_of_pages: 17
>
> Abstract:
>
> The International Standard Book Number, ISBN, is a widely used
> identifier for monographic publications.  Since 2001, there has been
> a URN (Uniform Resource Names) namespace for ISBNs.  The namespace
> registration was performed in RFC 3187 and applies to the ISBN as
> specified in the original ISO Standard 2108-1992.  To allow for
> further growth in use, the successor ISO Standard, ISO 2108-2005, has
> defined an expanded format for the ISBN, known as "ISBN-13".  This
> document replaces RFC 3187 and defines how both the old and new ISBN
> standard can be supported within the URN framework and the syntax for
> URNs defined in RFC 2141.  An updated namespace registration is
> included, which describes how both the old and the new ISBN format
> can share the same namespace.
>
> Discussion
>
> This draft version is the outcome of work started in 2008 and brought
> to the IETF as a contribution to a much larger effort to revise the
> basic URN RFCs, in order to bring them in alignment with the current
> URI Standard (STD 63, RFC 3986), ABNF, and IANA guidelines, and to
> establish a modern URN resolution system for bibliographic
> identifiers.
>
> Until a more specific mailing list is established, comments are
> welcome on the urn-nid@ietf.org mailing list (or sent to the
> authors).
>
>
>
> The IETF Secretariat.
>
> ----- End of forwarded message from IETF I-D Submission Tool -----
>
>
>
>
Received on Monday, 22 March 2010 15:28:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:20 GMT