Re: URL's for specific revisions
jamsden@us.ibm.com
Tue, 5 Oct 1999 17:15:28 -0400
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <85256801.0074DD86.00@d54mta03.raleigh.ibm.com>
Date: Tue, 5 Oct 1999 17:15:28 -0400
Subject: Re: URL's for specific revisions
Very interesting! I'd like to think about this one a little more though. We
should try it on some scenarios and see how it works. What would it break?
Tim_Ellison@oti.com (Tim Ellison OTT) on 10/05/99 04:37:28 PM
To: ietf-dav-versioning@w3.org (ietf-dav-versioning)
cc:
Subject: URL's for specific revisions
I propose that we define the URL to a specific revision to be:
revision_URL = history_resource_URL "/" <revision_identifier>
Since history resources are non-versionable resources, the
history_resource_URL is not subject to selection rules.
This means that clients can 'globally' use a revision_URL to refer to a
specific versioned resource revision.
[Since the spec is quiet about where history resources are stored in the
namespace, I offer the following examples assuming that the server chooses
to store history resources as /history/<versioned_resource_id>,
then:
revision_URL = /history/<versioned_resource_id>/<revision_identifier>]
For example:
http://foo.com/history/res23/rev42
http://foo.com/history/res81/rev1
further, if a revision is a collection, then 'slashing though' it would be
allowed, and subject to the regular Target-Selection procedure, for
versioned collections,
for example (assume res23 is a collection)
http://foo.com/history/res23/rev42/member1/index.html
This would make revisions members of a history resource rather than
properties.
Tim