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

DAV:merge-preview Report, MERGE and UPDATE responses

From: Roy Seto <Roy.Seto@oracle.com>
Date: Thu, 27 Sep 2001 14:22:04 +0100
Message-ID: <3BB327FC.99E49195@oracle.com>
To: ietf-dav-versioning@w3.org
The DAV:merge-preview Report's response used to look like
the responses of MERGE and UPDATE, but then DAV:ignore-set
was dropped from MERGE and UPDATE, and MERGE and UPDATE's
responses were brought in line with Multi-Status format
following Tim Ellison's suggestion on August 21:


Does it make sense to bring the DAV:merge-preview Report
request and response format in line with the current format

Also, as of draft-18, DAV:merge-preview Report identifies
the common ancestor version for merge targets that need
logical content merging by clients, but MERGE does not
(though of course of client can still request a
DAV:version-tree Report and compute the common ancestor
itself). Does it make sense to introduce a mechanism (such
as a property) for the server to identify common ancestor
versions after a MERGE?

Received on Thursday, 27 September 2001 09:18:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:47 UTC