# URN Requirements

Andrew Pam (avatar@notebook.aus.xanadu.com)
Sat, 14 May 94 23:13:01 EST

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jared_Rhine@hmc.edu: "URN Requirements"
- Previous message: Jared_Rhine@hmc.edu: "URN Requirements"

    Message-Id: <9405141121.AA0071@notebook.aus.xanadu.com>

    Date: Sat, 14 May 94 23:13:01 EST

    From: avatar@notebook.aus.xanadu.com (Andrew Pam)

    To: uri@bunyip.com

    Subject: URN Requirements

One of the requirements I am contemplating in the Xanadu equivalent of URNs
is that resources can be uniquely named on networks or machines not connected
to each other, which may become connected at a later stage. In other words
that the resource names must be unique without any knowledge of other names
being assigned elsewhere, and with no central naming authority.

I believe that this could be implemented by ensuring that the resource
identifiers are always stored relative to the local server, and are
canonicalised immediately whenever transferred from another server. My
question is, how would this model of URNs fit into the proposed URI system?

Share and enjoy,
*** AVATAR ***

Andrew Pam avatar@notebook.aus.xanadu.com
Manager, Serious Cybernetics avatar@jolt.mpx.com.au
Coordinator, Xanadu Australia <http://www.aus.xanadu.com/>
P.O. Box 409, Canterbury VIC 3126 Australia gopher gopher.aus.xanadu.com

- Next message: Jared_Rhine@hmc.edu: "URN Requirements"
- Previous message: Jared_Rhine@hmc.edu: "URN Requirements"