Re: FW: A question about branching, merging

Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Thu, 9 Dec 1999 17:45:09 -0500 

Date: Thu, 9 Dec 1999 17:45:09 -0500
Message-Id: <9912092245.AA02728@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <1999Dec08.105200.1250.1410691@otismtp.ott.oti.com>
Subject: Re: FW: A question about branching, merging


   From: Tim_Ellison@oti.com (Tim Ellison OTT)

   <gc>
   ..  the spec. should be simplified by replacing
   the four properties:
     DAV:predecessor, DAV:successors, DAV:merge-predecessors, 
   DAV:merge-sucessors
   with the two properties:
     DAV:predecessors, DAV:successors.
   </gc>

   <tim>
   to be clear, you're proposing:

   DAV:predecessors (collection)
       A new working resource will initially have a single member which is the 
   revision checked out to create this working resource.  Any member may be 
   removed or added to the predecessors collection to reflect merging that 
   produced this resource.  (Removing the inital member would be unusual but 
   permissible.)

Yes.  I'll save this paragraph for use in the spec.

   DAV:successors (mutable, collection)
       Contains the revisions whose predecessors are this revision.

Yes.

   These properties are not associated with <Activity> extensions.

Yes.

   <gc/>Note: I will interpret silence to mean consent that we simplify (:-).
   Ok, I'm silent<g>
   </tim>

Great!  (The consent, not the silence :-).

Cheers,
Geoff