Danyel Ceccaldi (dceccald@elaine.crcg.edu)
Fri, 9 Jun 1995 12:04:41 -0400

Date: Fri, 9 Jun 1995 12:04:41 -0400
From: dceccald@elaine.crcg.edu (Danyel Ceccaldi)
Message-Id: <9506091604.AA00912@hornbill.crcg.edu>
To: uri@bunyip.com
Subject: URN -> URL

Subject URN -> URL
Reply-To dceccaldi@crcg.edu

Hi folks,

I hope that is the right place for my problem and
you can help me or give a hint who can help me.

Following scenario:*1

An Internet Data Provider wants to support
it's customers by writing a CD-ROM which contains
the long-life-datas and big datas (mpeg, ...) of his server.

Is it conform (In the sense of a future final release of URN's)
to store a flat database on the cd-rom (or updates in the cache),
calculated by the Server*2, containing
a resolution betwenn an URN, a refering URL and the location
on the CD-ROM. The URL should contain the current version
of the data or a request should reply information, where
you can find the changed or moved data.

An example:

extract from database-file:

# every block begins with an URN, comments begins with '#'.
URN urn:server-isbn:/data/grouped/path/and/name/here/imgs/server
# The URN-Syntax doesn't matter, because only a stringcomparison
# will be done by the database.
URL http://www.example.server.com/img/server.gif
LOCATION /imgs/server.gif

*1 (Following scenario):
I'm developing a mechanism which fits in the scenario,
and want to create a solution, which is valid for a time.

*2 (calculated by the server):
Perhaps the Server has an URN/URC resolver and extract an URL
from the URC.

Please comment my problem or ask for details.