Re: URN Services draft

Terry Allen (terry@ora.com)
Fri, 16 Jun 1995 16:10:29 -0700


From: "Terry Allen" <terry@ora.com>
Message-Id: <9506161610.ZM7236@dmg.west.ora.com>
Date: Fri, 16 Jun 1995 16:10:29 -0700
In-Reply-To: "Ron Daniel Jr." <rdaniel@acl.lanl.gov>
To: rdaniel@acl.lanl.gov, uri@bunyip.com
Subject: Re: URN Services draft

Glad to see this discussion.  I too like the OCLC draft.  Just a note:

Ron says:
>ISBN is a naming authority. DUNS is a naming scheme, a different beast indeed.
and earlier remarked that he didn't expect Dun & Bradstreet to be able to
set policy for everyone who has a DUNS number.

ISBNs are actually names; they are issued in blocks to publishers, and
include the publisher identifier string.  A publisher might use his
publisher identifier as his piece of namespace, and extend it in his
own fashion.  But it would be very useful to specify how ISBNs may
be extended, for all ISBN users (the DUNS issue).  For example, one
could then make a page reference to a printed book in the manner

ISBN:0-944940-00-5p77

if the syntax were standardized by the namespace owner (the agency
that issues the ISBNs).  As the owner of a piece of that namespace
(my publisher ID, 944940), I kinda think I ought to be able to 
extend it however *I* specify.  Thus if ISPID meant publisher id:

ISPID:944940-catalogue.html

could be my URN for for current book catalogue.


Regards,

-- 
Terry Allen  (terry@ora.com)   O'Reilly & Associates, Inc.
Editor, Digital Media Group    101 Morris St.
			       Sebastopol, Calif., 95472

A Davenport Group sponsor.  For information on the Davenport 
  Group see ftp://ftp.ora.com/pub/davenport/README.html
	or  http://www.ora.com/davenport/README.html