W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2001

Re: RFC2518 (WebDAV) / RFC2396 (URI) inconsistency

From: Mark Baker <distobj@acm.org>
Date: Sun, 25 Nov 2001 20:28:52 -0500 (EST)
Message-Id: <200111260128.UAA30872@markbaker.ca>
To: fielding@ebuilt.com (Roy T. Fielding)
Cc: LMM@acm.org (Larry Masinter), duerst@w3.org ('Martin Duerst'), stefan.eissing@greenbytes.de ('Stefan Eissing'), w3c-dist-auth@w3.org ('WebDAV'), uri@w3.org
Roy,

> > but have left out the following possibilities:
> > 
> > * Change the XML namespace spec to allow "scheme-name:" as
> >   a namespace name, even though it isn't a legal URI
> >   (This isn't such a big deal, since XML namespace names allow
> >    IRIs with non-ASCII characters anyway, not really URIs)
> 
> In case anyone is wondering, "scheme:" is not allowed in the URI syntax
> because Web browsers and client libraries do interpret it as a form of
> relative URI due to a loophole in CERN's original partial URI algorithm.
> People never used it, but the loophole makes it impossible for such an
> identifier to be interoperable.
> 
> OTOH, I have found at least one other example -- the "about:" URL in
> Netscape Navigator -- so I guess this could be changed in a future revision
> of 2396.

Interesting.  Just to clarify, what are you suggesting be changed?
That "foo:" be a valid absolute URI reference, or a valid relative
one?

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com
Received on Sunday, 25 November 2001 20:30:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:59 GMT