From: Tim_Ellison@oti.com (Tim Ellison OTT) To: ietf-dav-versioning@w3.org (ietf-dav-versioning) Message-ID: <1999Dec08.105200.1250.1410691@otismtp.ott.oti.com> Date: Wed, 08 Dec 1999 10:55:08 -0500 Subject: FW: A question about branching, merging <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.) DAV:successors (mutable, collection) Contains the revisions whose predecessors are this revision. These properties are not associated with <Activity> extensions. <gc/>Note: I will interpret silence to mean consent that we simplify (:-). Ok, I'm silent<g> </tim>