OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: XML Public Indentifier

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 


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

-----Original Message-----
From: mrossi@csc.com [mailto:mrossi@csc.com]

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

Tim Bray

        To:     xml-dev@lists.xml.org




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