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

RFC2518 (WebDAV) / RFC2396 (URI) inconsistency

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 19 Nov 2001 22:32:39 +0100
To: <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCMEOKDHAA.julian.reschke@gmx.de>
(copy of post to <mailto:uri@w3.org>).

Hi.

(1) RFC2518 (WebDAV) is based on XML + namespaces and has chosen to use the
namespace name "DAV:" to identify it's elements. Note that "DAV:" *is* a
properly registered URI scheme (see [1])

(2) The XML namespaces recommendation says that an XML namespace is
identified by a URI reference as defined in RFC2396.

(3) RFC2396 gives the following grammar for absolute URIs:

absoluteURI   = scheme ":" ( hier_part | opaque_part )
opaque_part   = uric_no_slash *uric

"DAV:" doesn't seem to be a valid "opaque_part", because "opaque_part" MUST
start with "uric_no_slash", thus it may not be empty.

(4) I became aware of this mismatch when trying to develop a RELAG NG schema
for WebDAV. James Clark's JING validator rejects the namespace name "DAV:"
as invalid URI. So this has become a real-world problem (maybe it was "just"
academic before).

I think this means that either RFC2396 or RFC2518 need to be fixed.

Feedback appreciated.

Julian


[1] <http://www.iana.org/assignments/uri-schemes>
Received on Monday, 19 November 2001 16:38:44 GMT

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