Re: FW: A question about branching, merging

jamsden@us.ibm.com
Wed, 8 Dec 1999 13:57:15 -0500 

From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <85256841.0068630C.00@d54mta03.raleigh.ibm.com>
Date: Wed, 8 Dec 1999 13:57:15 -0500
Subject: Re: FW: A question about branching, merging



This sounds like it breaks the revision history of a versioned resource.
Don't think we want to allow that.





Tim_Ellison@oti.com (Tim Ellison OTT) on 12/08/99 10:55:08 AM

To:   ietf-dav-versioning@w3.org (ietf-dav-versioning)
cc:

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>