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

Re: Namespace URI question

• To: Jeff Lowery <jlowery@s...>
• Subject: Re: Namespace URI question
• From: Tim Bray <tbray@t...>
• Date: Fri, 13 Dec 2002 12:10:01 -0800
• Cc: 'Richard Tobin' <richard@c...>, xml-dev@l...
• In-reply-to: <879123D97A01D711B0F500508B4464E402776E@l...>
• References: <879123D97A01D711B0F500508B4464E402776E@l...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130

Jeff Lowery wrote:

> I came across this namespace declaration in a someone else's document (which
> I told him to change), but got stuck on the meaning of file:///foo.xsd.  I
> see now that the third slash means "localhost", which of course I should
> have known but I got mentally blocked on file path representations.  Now I'm
> back aboard the clue train.

There's also the general principle that file: URIs generally [expletive deleted]. 
Aside from the obvious portability problems, it seems like the syntax 
and semantics are different for every browser and class library out 
there, e.g. the orginally-netscape weirdness of file:|// or whatever 
with the pipe character in it.  Every time I've tried to use them 
they've given me severe grief.  I kind of suspect it's bogus to try to 
pretend a filename is a URI -Tim

• Follow-Ups:
  • Re: Namespace URI question
    • From: "Bill Kearney" <wkearney99@h...>

• References:
  • RE: Namespace URI question
    • From: Jeff Lowery <jlowery@s...>

• Prev by Date: RE: Namespace URI question
• Next by Date: RE: xml-dev@l...
• Previous by thread: RE: Namespace URI question
• Next by thread: Re: Namespace URI question
• Index(es):
  • Date
  • Thread