[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Re: [namespaceDocument-8] 14 Theses

• To: 'Patrick Stickler' <patrick.stickler@n...>, ext Michael Brennan <Michael_Brennan@a...>, ext Dare Obasanjo <dareo@m...>, XML DEV <xml-dev@l...>
• Subject: RE: Re: [namespaceDocument-8] 14 Theses
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Wed, 20 Feb 2002 08:32:23 -0600

And that brings one back round to the concept of the 
PUBLIC id.  Why shouldn't PUBLIC ids be used in 
namespace name values?  Because they aren't resolvable 
without the catalog.  So?  It works for SGML.  Oops.
You aren't in a new minority anyway.

Note, that in a classical PUBLIC id, it has different 
information in it than in a URI/URL/URN.  But that 
brings up the weirdness:  if that information is 
different, or extensible, would you rather pack it 
into the local space, or get it by reference. If 
by reference, wouldn't you want a namespace name 
to be a URL, or just a name resolved in a local 
catalog?  How would you find it?

len

-----Original Message-----
From: Patrick Stickler [mailto:patrick.stickler@n...]

The whole namespace bruhaha is directly due, I think, to
overloading the function of namespace URIs.

• Follow-Ups:
  • Re: Re: [namespaceDocument-8] 14 Theses
    • From: John Cowan <cowan@m...>
  • Re: Re: [namespaceDocument-8] 14 Theses
    • From: Patrick Stickler <patrick.stickler@n...>

• Prev by Date: Re: Re: [namespaceDocument-8] 14 Theses
• Next by Date: Re: Re: [namespaceDocument-8] 14 Theses
• Previous by thread: Re: Re: [namespaceDocument-8] 14 Theses
• Next by thread: Re: Re: [namespaceDocument-8] 14 Theses
• Index(es):
  • Date
  • Thread