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

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

From: Jim Whitehead <ejw@cse.ucsc.edu>
Date: Wed, 21 Nov 2001 09:34:50 -0800
To: "WebDAV" <w3c-dist-auth@w3.org>
Accidentally caught by the spam filer. I've added
"Patrick.Stickler@nokia.com" to the accept2 list.

- Jim

-----Original Message-----
From: Patrick.Stickler@nokia.com [mailto:Patrick.Stickler@nokia.com]
Sent: Wednesday, November 21, 2001 12:49 AM
To: distobj@acm.org; ejw@cse.ucsc.edu
Cc: w3c-dist-auth@w3.org; uri@w3.org
Subject: [Moderator Action] RE: RFC2518 (WebDAV) / RFC2396 (URI)

> IMO, a URI scheme has identity, and so should be able to be identified
> by a URI reference.

Right. Insofar as RDF is concerned, which provides for a
concatenative mapping from qname to URI, you could do the

   <dav:creationdate xmlns:dav="dav:"/>

Where "dav:" is both a URI denoting the URI scheme, and an xmlns
prefix. Which is which is 100% clear in the XML syntax.

This gives the (RDF) URI "dav:creationdate" as desired and
provides for consistency between URI and qname representation.


Though this doesn't help much in a non-RDF context where a
given qname is interpreted as just "{namespace}name" rather
than the concatenation "namespacename".




Patrick Stickler              Phone: +358 50 483 9453
Senior Research Scientist     Fax:   +358 7180 35409
Nokia Research Center         Email: patrick.stickler@nokia.com
Received on Wednesday, 21 November 2001 12:35:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:24 UTC