DAV:predecessors vs. DAV:predecessor/DAV:merge-predecessors
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Sun, 19 Dec 1999 22:42:33 -0500
Date: Sun, 19 Dec 1999 22:42:33 -0500
Message-Id: <9912200342.AA07352@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: DAV:predecessors vs. DAV:predecessor/DAV:merge-predecessors
A couple of weeks ago, I proposed simplifying the spec by unifying
a revision's DAV:predecessor/DAV:merge-predecessors into a single
DAV:predecessors. The discussion has been generally supportive of
this change, but there have been folks who didn't like it.
I'd like to ask anyone who *doesn't* like the change to please submit
a use case where this change produces a loss in functionality.
If none can be identified, I'd like to make the simplification.
Note that we can always add a DAV:predecessor property afterwards if
we discover a need for it, but for now, I'd like to simplify the
protocol as much as possible, unless the use case is a key one.
Cheers,
Geoff