W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2001

RE: Removing the DAV:activity and DAV:version-history and DAV:bas eline resource type values

From: Julian F. Reschke <julian.reschke@greenbytes.de>
Date: Wed, 6 Jun 2001 23:57:12 +0200
To: "Clemm, Geoff" <gclemm@rational.com>, "DeltaV \(E-mail\)" <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCKEGHCGAA.julian.reschke@greenbytes.de>
> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Clemm, Geoff
> Sent: Wednesday, June 06, 2001 5:07 PM
> To: DeltaV (E-mail)
> Subject: RE: Removing the DAV:activity and DAV:version-history and
> DAV:bas eline resource type values
>
> Just as a reminder, DAV:version-controlled-resource, DAV:version,
> DAV:working-resource, DAV:checked-in, and DAV:checked-out as a value
> in DAV:resourcetype will make that resource appear to be a folder in
> the (large number of) Microsoft WebDAV clients that are currently
> deployed.  Now I know that Microsoft's misreading of the spec is
> reprehensible to the extreme, but for those of us that have to deal
> with that unfortunate reality, we may be forced for market reasons to
> leave out those particular DAV:resourcetype values from our server
> implementations until that bug has been fixed in a widely deployed
> replacement for those buggy clients.
>
> Can anyone from Microsoft that is following this list give us a clue
> as to whether this bug will be fixed anytime soon?

Geoff,

could you expand a bit on what the bug is? Are they treating anything with a
non-empty resourcetype as collection?
Received on Wednesday, 6 June 2001 17:57:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:41 GMT