# Re: Registrar & URNs pointing to "current" documents

Rob Raisch (raisch@ora.com)
Wed, 14 Jul 1993 12:51:53 -0400 (EDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Rob Raisch: "Re: Registrar"
- Previous message: Larry Masinter: "Re: Registrar"

    Date: Wed, 14 Jul 1993 12:51:53 -0400 (EDT)

    From: Rob Raisch <raisch@ora.com>

    Subject: Re: Registrar & URNs pointing to "current" documents

    To: Dirk Herr-Hoyman <hoymand@joe.uwex.edu>

    In-Reply-To: <9307141427.AA06921@joe.uwex.edu>

    Message-Id: <Pine.3.03.9307141135.C6476-c100000@ruby.ora.com>

----------------------------Original message----------------------------

Micheal Mealling brings up the idea that a URN might refer to a service,
which by its very nature is dynamic. There is a distinction here, I feel,
between a service and its content. The service itself is static -- it exists
over time and does not change. So the reference to the service is static.
The content of a service is the dynamic part.

I think what I am trying for here is that the service itself is the
product, one which provides access to other potential products. As a
product, the service can be assigned a URN, but that URN cannot guarantee
the content of that service.
__________________________________________________________________
Could be a service, or it could be a permanent pointer to a regular
edition of a document; e.g., "Today's New York Times" or "Current
Edition of The Chronicle of Higher Ed" or "This Month's Esquire".

Should there be a specially-denoted URN for this purpose? It seems
there is tension between the idea of a "handle" for a document that
applies as long as content doesn't change, and a pointer to a "current"
edition of a document.

/rich

- Next message: Rob Raisch: "Re: Registrar"
- Previous message: Larry Masinter: "Re: Registrar"