# Re urn2urc-00

Terry Allen (terry@ora.com)
Tue, 19 Apr 1994 06:42:14 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Mitra: "Re: Re urn2urc-00"
- Previous message: pays@faugeres.inria.fr: "Re: URN allocation and resolution"
- Next in thread: Mitra: "Re: Re urn2urc-00"
- Maybe reply: Mitra: "Re: Re urn2urc-00"
- Maybe reply: Peter Deutsch: "Re: Re urn2urc-00"
- Maybe reply: Mitra: "Re: Re urn2urc-00"

    Message-Id: <199404191342.GAA11366@rock>

    From: Terry Allen <terry@ora.com>

    Date: Tue, 19 Apr 1994 06:42:14 PDT

    To: uri@bunyip.com

    Subject: Re urn2urc-00

Mitra, you write in draft-ietf-uri-urn2urc-00.txt, at (3),
that the client locates a URN > URC resolution service to
get from a URN to a URL. But you never explain why this
is the way to go. I have imagined URCs as collections
of information that would allow one to choose among URNs;
the question of locating specific instances (URLs) of
URNs should be much simpler. Would you expand on why you
think this is reasonable?

And (1st para under (3)), you write that the URN needs
to contain enough info within it to locate the resolution
service. This clearly isn't going to work. A publisher
(he who assigns the URN) cannot know of services that
spring up after the publication date, and shouldn't be
relied upon to know of existing services.

Regards,

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

- Next message: Mitra: "Re: Re urn2urc-00"
- Previous message: pays@faugeres.inria.fr: "Re: URN allocation and resolution"
- Next in thread: Mitra: "Re: Re urn2urc-00"
- Maybe reply: Mitra: "Re: Re urn2urc-00"
- Maybe reply: Peter Deutsch: "Re: Re urn2urc-00"
- Maybe reply: Mitra: "Re: Re urn2urc-00"