Re: Versioning spec review - 02.3
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Wed, 27 Oct 1999 12:00:29 -0400
Date: Wed, 27 Oct 1999 12:00:29 -0400
Message-Id: <9910271600.AA26211@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <85256817.004E2D0A.00@d54mta03.raleigh.ibm.com>
Subject: Re: Versioning spec review - 02.3
From: jamsden@us.ibm.com
You use a PROPFIND with the workspace as the target selector to get
the DAV:revisions property of the DAV:versioned-resource property of
the revision. With the DAV:revisions collection, you can select any
revision of that versioned resource that you want.
<jra>
Completely unacceptible.
Again, it is the server's responsibility to do
this name mapping, not the client. That's why we have human meaningful
names.
</jra>
The client is a computer program, and computer programs are really
good at parsing XML and concatenating strings.
Users don't issue PROPFIND requests ... clients (computer programs)
do, and all they need is a well defined syntax to get their work done.
I'm not sure what you mean by "translate URL and revision names into
server generated revision URL's". If you mean, concatenate the
DAV:labeled-revisions URL with a "/" and a label, then I find that
totally acceptable. That's exactly what a client does for a user whenever
a specific member of a collection is requested.
<jra>
What I'm saying is that it is unacceptible for the client to have to do a
PROPFIND, get a server URL and hand it back. So what I want to do is have
the client give the server a workspace for resolving URL path segments,
with an option to provide a revision name to override the selection of the
last item in the path.
The client is not some poor overworked human trying to match XML angle
brackets (:-). It is a computer program which could care less if the
strings it is sending back and forth are "human meaningful".
Cheers,
Geoff