Next message: Geoffrey M. Clemm: "Re: draft-ietf-deltav04.5 now available"
To: "Clemm, Geoff" <gclemm@rational.com>
Cc: ietf-dav-versioning@w3.org
Message-ID: <OF55B58DE8.0A5CCE00-ON852568E3.006F02B7@ott.oti.com>
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Thu, 18 May 2000 16:27:11 -0400
Subject: RE: Stable Href's of collections
If I may modify your example slightly,
PROPFIND /repo/vr/id178/rev/id122
Depth:1
and say that this returns a report with the information:
<href> /repo/vr/id178/rev/id122/foo.html </href>
[requested properties]
<href> /repo/vr/id178/rev/id122/bar/ </href>
[requested properties]
i.e. the target resource is a collection that has a member 'bar' bound to a
versioned collection.
Now the implication is that I can request:
PROPFIND /repo/vr/id178/rev/id122/bar/
Depth: 1
to find its members.
How do we describe the URL /repo/vr/id178/rev/id122/bar/ ?
It is "partially-stable" since it does not participate in dynamic revision
selection for all segments up to but not including 'bar'.
Suppose that we did not have a workspace that had an opinion for the
revision of 'bar'. I'm assuming that we could proceed with " browsing "
the repository by issuing a PROPFIND where the target selector is a
versioned resource looking at the revision set. If we did have a workspace
that had an opinion for 'bar' we could proceed by issuing a PROPFIND where
the target selector was a workspace.
Tim
"Clemm, Geoff"
<gclemm@rational.com> To: ietf-dav-versioning@w3.org
Sent by: cc:
ietf-dav-versioning-requ Subject: RE: Stable Href's of collections
est@w3.org
06/04/00 12:33 AM
The members of a collection revision are the versioned resources
that are bound into that revision of the collection. If you do a
PROPFIND Depth:1 on the stable URL to the collection revision,
you will get a list of stable URL's to each of those versioned
resources, but the binding name of each URL will be name of the
that member.
For example, assuming /repo/vr/id178/rev/id122 is a stable URL for
a revision of a collection, then:
PROPFIND /repo/vr/id178/rev/id122
Depth:1
will return a report with the information:
<href> /repo/vr/id178/rev/id122/foo.html </href>
[requested properties]
<href> /repo/vr/id178/rev/id122/bar.html </href>
[requested properties]
where each of the href's is bound to a versioned resource.
Note that this means that there are multiple bindings to a
versioned resource: a "canonical" one of the form /repo/vr/idxxx,
and additional bindings from each of the collection
revisions that contain that versioned resource.
Cheers,
Geoff
-----Original Message-----
From: Tim Ellison/OTT/OTI [mailto:Tim_Ellison@oti.com]
Sent: Monday, April 03, 2000 12:40 PM
To: ietf-dav-versioning@w3.org
Subject: Stable Href's of collections
I seem to remember that we agreed that deep operations on a collection's
stable Href would return responses in terms of stable Hrefs. Makes sense.
Now, assume that I have a stable Href to a collection and would like to
know the names of the collection's members. Previously I'd have used
PROPFIND depth 1 on some property, and got the answer as a "side-effect",
in the <href> tags. However, stable <href>'s cannot be used to extract the
names.
Hmm,
Tim