Next message: Jim Whitehead: "Revision-set property: unordered?"
Date: Thu, 29 Jun 2000 08:25:42 -0400 (EDT)
Message-Id: <200006291225.IAA01162@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: State of versioned resource, history resource
For "core versioning", the answer is "C", because in core versioning a
versioned resource just holds a reference to a revision (in the
DAV:default-target property), and there is no history resource.
The DAV:revision-tree-report can be applied to a versioned resource to
get a complete listing of all the revisions that are connected to the
DAV:default-target by the DAV:predecessor-set property, but this is a
report (i.e. a computation on the server based on the state of
multiple resources), not a property of the versioned resource.
In "advanced versioning", the answer is also "C" (but "B" is close :-),
i.e. the versioned resource now also holds a reference to a
history resource (in the DAV:history property). The history resource
has references to all the revisions, in the DAV:revision-set property.
Note that the history resource does not contain the revision
predecessor information -- that is a property of the revisions.
So the bottom line is: the properties and content (and for collections,
the bindings) define the state of a resource.
Cheers,
Geoff
From: Jim Whitehead <ejw@ics.uci.edu>
After reading through the -05 draft:
> http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-05.htm
I was left wondering about what constituted the state of a versioned
resource, and a history resource. It seems that there are two choices:
a) A versioned resource contains all of the revisions (by reference), and
holds all of the pred/succ relationships, and contains any working resources
(by reference) associated with the versioned resource. The history resource
also has these same state items, which are a duplicate of the items on the
versioned resource.
b) A versioned resource only holds a pointer to the history resource. The
history resource contains all of the revisions (by reference), and holds all
of the pred/succ relationships, and contains any working resources (by
reference) associated with the versioned resource.
c) Neither (implying I've misunderstood things).
I'm curious as to which was intended.
- Jim