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

RE: Problem with Adobe GoLive 5.0's parsing of PROPFIND

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 24 May 2001 23:49:24 +0200
To: "Laurie Harper" <zodiac@holoweb.net>, "Julian Reschke" <julian.reschke@gmx.de>
Cc: "Hartmut Warncke" <hwarncke@Adobe.COM>, <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEEDCFAA.julian.reschke@gmx.de>
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Laurie Harper
> Sent: Tuesday, May 22, 2001 6:07 PM
> To: Julian Reschke
> Cc: Hartmut Warncke; w3c-dist-auth@w3.org
> Subject: Re: Problem with Adobe GoLive 5.0's parsing of PROPFIND
> Julian Reschke wrote:
> >         <julian>
> >           <href>mailto:fax@greenbytes.de</href>
> >         </julian>
> Just to be clear: the element 'julian' appears in the default namespace,
> which is the DAV namespace.  Since that namespace doesn't define
> an element
> named 'julian' this is likely to cause trouble.
> You probably want to place that element in a different namespace, one
> controlled by you.

Contrary to some big company in Redmond, I am well aware of the fact that
the DAV: namespace shouldn't be abused with proprietary extensions. This was
just an example.

Moving it to some other namespace doesn't change GoLive's behaviour (and
even if it would, it would still be a problem for GoLive because other
WebDAV specs (ACL for instance) *do* use DAV:href in DAV properties where
GoLive doesn't expect them).
Received on Thursday, 24 May 2001 17:50:03 UTC

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