Re: History propery: multiple hrefs violate DAV spec

Chris Kaler (ckaler@Exchange.Microsoft.com)
Thu, 20 May 1999 10:06:55 -0700 

Message-ID: <FD7A762E588AD211A7BC00805FFEA54B01C297E6@HYDRANT>
From: "Chris Kaler (Exchange)" <ckaler@Exchange.Microsoft.com>
To: "'Geoffrey M. Clemm'" <gclemm@tantalum.atria.com>, jdavis@coursenet.com
Cc: ietf-dav-versioning@w3.org
Date: Thu, 20 May 1999 10:06:55 -0700
Subject: RE: History propery: multiple hrefs violate DAV spec


I personally dislike the standard collection approach because it isn't very
extensible.  That is, I only have one way to view the history.

Jim, when I wrote this up, I took a shortcut that I shouldn't have.  I split
each revision into an href and revisionid.  What I should have done is
returned the href for the specific revision and included a vresourceid and
revisionid as well.  This would meet the RFC requirements.

Chris

-----Original Message-----
From: Geoffrey M. Clemm [mailto:gclemm@tantalum.atria.com]
Sent: Wednesday, May 19, 1999 1:44 AM
To: jdavis@coursenet.com
Cc: ietf-dav-versioning@w3.org
Subject: Re: History propery: multiple hrefs violate DAV spec



The 01.1 draft proposes that the defaulthistory report be replaced
with a standard collection that contains all the revisions of a
versioned-resource.  Then a "defaulthistory report" is obtained by
just doing a PROPFIND on this collection.  This would remove the need
for a special report format, and would avoid the kind of error that
Jim Davis discovered.

Cheers,
Geoff

   X-Sender: jdavis@192.168.254.128
   X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
   Date: Mon, 17 May 1999 16:21:47 -0700
   From: "Jim Davis" <jdavis@coursenet.com>
   Mime-Version: 1.0
   Resent-From: ietf-dav-versioning@w3.org
   X-Mailing-List: <ietf-dav-versioning@w3.org> archive/latest/182
   X-Loop: ietf-dav-versioning@w3.org
   Sender: ietf-dav-versioning-request@w3.org
   Resent-Sender: ietf-dav-versioning-request@w3.org
   Precedence: list
   Content-Type: text/plain; charset="us-ascii"
   Content-Length: 413

   The defaulthistory report (and perhaps others) produces a PROPFIND result
   that is in violation of the WebDAV spec. RFC 2518 12.9.1 says

   A particular href MUST NOT appear more than once as the child of a
response
   XML element under a multistatus XML element.

   But in the defaulthistory report,  the href appears once for each
revisionid

   I've only just joined the deltaV list, sorry if this has already come up.