• To: <xml-dev@l...>
• Subject: Re: How did "public identifier" get its name...
• From: "Thomas B. Passin" <tpassin@c...>
• Date: Thu, 31 Jul 2003 20:21:32 -0400
• References: <15725CF6AFE2F34DB8A5B4770B7334EE022DC70A@h...>

[Bullard, Claude L (Len)]

> The PUBLIC identifier, as you know, can have interesting
> information in it that has nothing to do with dereferencing
> a representation from a resource over a network protocol.
> Are you saying the URI in the PUBLIC id would point to a document
> for getting that information?
>
> That would also mean that nothing can be done with XML unless
> it is done "on the web".  PUBLIC IDs are a way to hook up
> to other systems.  You would be legislating away that right.
>

I just took it that John meant to use a __non-dereferenceable__ URI as an
identifier, since using URIs as has become standard practice by now (xslt,
RDF, OWL...).  Now you could really confuse people by using a retrievable
http: URL for the Public Identifier!

Cheers,

Tom P

• References:
  • RE: How did "public identifier" get its name...
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: Re: reaching humans (was Re: Extract A Subset of a W3C XML Schema?)
• Next by Date: RE: reaching humans (was Re: Extract A Subsetof a W3C XML Schema?)
• Previous by thread: RE: How did "public identifier" get its name...
• Next by thread: (Updated) Categories of Mismatches between Producer and Consumer
• Index(es):
  • Date
  • Thread