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

RE: XML Public Indentifier

• From: "Bullard, Claude L (Len)" <clbullar@i...>
• To: xml-dev@l...
• Date: Wed, 05 Sep 2001 13:56:20 -0500

If the author of the namespace spec can say 
on one hand that it is just a label, and on 
the other hand can say he won't use a URN 
that can't be dereferenced,  isn't that a 
contradiction?

Len 
http://www.mp3.com/LenBullard

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: mrossi@c... [mailto:mrossi@c...]

Why would you even try to dereference a name when it doesn't reference
anything in the first place? 
 

Tim Bray


        To:     xml-dev@l...

 

 

 

At 08:15 AM 05/09/01 -0700, David Brownell wrote:

>A better solution is to use only URNs as system IDs in XML, using
>some URN resolution mechanism.

There's a chicken-and-egg problem here.  I am reluctant to start
stuffing URNs in XML until there's a good chance that they can
be dereferenced and used to retrieve things.  At the moment, my
own computer contains no URN dereferencing software that I'm aware
of.  On the other hand, I don't see a big chance that URN
resolution software is going to become ubiquitous until there's
a killer app for URNs; I suspect XML entity retrieval isn't it.

So I'd say we're stuck with URLs for the moment.  Using URNs
in the PUBLIC ID slot seems plausible though. -Tim

• Follow-Ups:
  • RE: XML Public Indentifier
    • From: Tim Bray <tbray@t...>

• Prev by Date: Re: XML Public Indentifier
• Next by Date: Re: XML Public Indentifier
• Previous by thread: Re: XML Public Indentifier
• Next by thread: RE: XML Public Indentifier
• Index(es):
  • Date
  • Thread