W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2002

RE: Clarification: extended baseline semantics of UPDATE

From: Clemm, Geoff <gclemm@rational.com>
Date: Wed, 20 Mar 2002 17:21:51 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B103F8B0A5@SUS-MA1IT01>
To: "Ietf-Dav-Versioning@W3. Org" <ietf-dav-versioning@w3.org>
The UPDATE method explicitly identifies the "update target"
for the "update source", so there is no need for such a rule
(i.e. you can only update a version-controlled-configuration
with a baseline from the baseline history of that 
version-controlled configiguration).

So this statement (which is about how to find the merge target
for a baseline MERGE request) is not needed for UPDATE.

Cheers,
Geoff

-----Original Message-----
From: Roy Seto [mailto:Roy.Seto@oracle.com]
Sent: Wednesday, March 20, 2002 2:34 PM
To: Ietf-Dav-Versioning@W3. Org
Subject: Clarification: extended baseline semantics of UPDATE


Section 12.14, which defines the extended baseline semantics of MERGE,
includes the statement

   If the merge source is a baseline, the merge target is a version-
   controlled configuration for the baseline history of that baseline,
   where the baseline-controlled collection of that version-controlled
   configuration is a member of the collection identified by the
   request-URL.

Section 12.13, which defines the extended baseline semantics of UPDATE, does
not include a similar statement, but I think it should. 

Is this the working group's intention? Would this be a reasonable edit to
make in the next rev of the spec?

Roy
Received on Wednesday, 20 March 2002 17:25:38 GMT

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