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

RE: Issue: PROP_ATTR

From: Julian F. Reschke <julian.reschke@gmx.de>
Date: Mon, 16 Apr 2001 16:39:58 +0200
To: "WebDAV WG" <w3c-dist-auth@w3.org>
Message-ID: <AFEIKENBELCNEGJFCENGEEJFDCAA.julian.reschke@gmx.de>
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Kevin Wiggen
> Sent: Monday, April 16, 2001 4:30 PM
> To: Greg Stein; WebDAV WG
> Subject: RE: Issue: PROP_ATTR
> ...
> >They're SOL with (at least) mod_dav. It doesn't preserve
> prefixes. That is
> >potentially another issue for the RFC 2518 issues list (I have
> an opinion,
> >but that can occur under a separate issue thread).
>
> DAV servers cannot preserve the namespace prefix.  What would

What do you mean by "cannot"? Preserving something doesn't necessarily mean
that it needs to contribute to the property's uniquess criteria (like
xml:lang).

> happen if two
> proppatch's told the same resource to store properties with the same
> prefixes but differing namespaces?  When the server went to
> output info on a
> propfind, it would not be consistent.

I think this is a misunderstatement. We were talking about prefix
preservation *inside* property values, like:

<prop xlmns="DAV:">
	<stylesheet xmlns="foo">
		<xsl:transform version="1.0" xmlns:xsl="http...">
			...
		</xsl:/transform>
	</stylesheet>
</prop>

However, whether the prefix of the property *itself* needs to be preserved
(although it does not contribute to the key) is yet another open question...

Julian
Received on Monday, 16 April 2001 10:40:08 GMT

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