Re: History propery: multiple hrefs violate DAV spec
Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Wed, 19 May 1999 04:43:56 -0400
Date: Wed, 19 May 1999 04:43:56 -0400
Message-Id: <9905190843.AA04460@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: jdavis@coursenet.com
Cc: ietf-dav-versioning@w3.org
In-Reply-To: <4.1.19990517161019.00a1e080@192.168.254.128>
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.