Re: public/catalog [was: Re: ERB Decisions of March 26th]

Gavin Nicol wrote:
> >You need public identifiers to overcome the location shifts so prevelant in
> >modern nucleated systems. Without public identifiers, and catalogs to
> >intepret them, you cannot create any valid WWW document set with a realistic
> >lifespan of more than 2-3 years as that is the average lifespan of the
> >underlying system, and a new system typically means a revised file
> >structure.
> I disagree with the assertion that we *need* PUBLIC. You can accomplish
> the same thing using aliasing of SYSTEM ID's. There is no requirement
> that a URL be a file path.

You don't always own the server of the resources you are referring to.
You may also want the name of the object to be independent of any
particular server.

 Paul Prescod