Next message: Greg Stein: "Re: MERGE response body"
Message-ID: <3906C56A7BD1F54593344C05BD1374B15342DB@SUS-MA1IT01>
From: "Clemm, Geoff" <gclemm@rational.com>
To: ietf-dav-versioning@w3.org
Date: Tue, 29 Aug 2000 23:42:26 -0400
Subject: RE: MERGE response body
From: Greg Stein [mailto:gstein@lyra.org]
In Subversion, I'm planning to MERGE an activity into the (version
selector)
collection(s). (no workspaces) However, the response body isn't
quite as
rich as I'd like.
Specifically, consider the MERGE body right now: it returns a set of
URLs of
the resources that were affected. But it says nothing more. You must
turn
around and issue a set of PROPFIND or REPORT requests to find out
the state
of the repository after the MERGE.
To be concrete: I want the MERGE to return the DAV:getetag and
DAV:target
values for each affected resource.
I would suggest that we change the MERGE request body to something
like
this:
<!ELEMENT merge (no-auto-merge?, prop?)>
[ note the current draft is missing the "?" on no-auto-merge ]
Fixed.
The DAV:prop element would be similar to a PROPFIND/prop: it is
merely
specifying names of properties to return.
That would be fine with me.
The MERGE response then becomes:
<!ELEMENT merge-response (update-set?, ignored-set?)>
<!ELEMENT update-set (response*)>
<!ELEMENT ignored-set (href*)>
The DAV:response element follows that of RFC 2518 and the PROPFIND
response.
That's fine with me as well.
[ note the current draft does not include "?" in the merge-response
child
elements ]
I was inclined to make the update-set and ignored-set elements required
(they
can have 0 elements because of the "*"), just to make life marginally easier
for
the parser. But if anyone cares, I can make them optional.
Cheers,
Geoff