date in URN

Michael Shapiro (mshapiro@ncsa.uiuc.edu)
Thu, 22 Jun 1995 08:49:51 -0500 (CDT)


From: mshapiro@ncsa.uiuc.edu (Michael Shapiro)
Message-Id: <9506221349.AA06507@void.ncsa.uiuc.edu>
Subject: date in URN
To: uri@bunyip.com
Date: Thu, 22 Jun 1995 08:49:51 -0500 (CDT)
In-Reply-To: <95Jun22.011116pdt.2761@golden.parc.xerox.com> from "Larry Masinter" at Jun 22, 95 01:11:10 am

Is the idea to require a syntax that has a date?
	dns-urn:netloc/date/doc-id
or would it just be part of the OS
	dns-urn:netloc/OS           (where OS = date/doc-id)

Also, would you elaborate on the difficulties with potential reuse of
identifiers and how this solves them. If URNs will have a date in them,
then the RFC should say something about why they are needed.

Larry Masinter wrote:
|
|>The more I think about it, the more convinced I am that if URNs are to be as
|>persistent as possible, that they should be numeric (or alphanumeric codes
|>like the LoC numbers or British/Canadian postal code system).  If you use
|>human-readable names like "proper" or "ibm" people will get emotional and/or
|>possessive about them, making it much harder to prevent the URNs containing
|>them from changing over time.
|
|At the last URI meeting, it was suggested that adding a date stamp to
|a DNS name might circumvent the impermanence of DNS names. The
|granularity of the date stamp need not be small, e.g., just a year
|might do, and certainly year/month.
|
|dns-urn:ibm.com/1995/<ibm-document-id>
|
|This would solve a variety of difficulties with potential reuse of
|identifiers. 
|


-- 
Michael Shapiro                   mshapiro@ncsa.uiuc.edu
NCSA                              (217) 244-6642
605 E Springfield Ave. RM 152CAB  fax: (217) 333-5973
Champaign, IL 61820