Next message: Geoffrey M. Clemm: "Re: Versioning TeleConf Agenda, 6/5/00 (Monday) 2pm-3pm EST"
Date: Sat, 24 Jun 2000 21:41:40 -0400 (EDT)
Message-Id: <200006250141.VAA01113@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Versioning TeleConf Agenda, 6/5/00 (Monday) 2pm-3pm EST
From: jamsden@us.ibm.com
The proposal below promotes the use of the history URL to get the
versioning history of a versioned resource which is usually
referenced using a versioned resource URL, the one the user knows,
is familiar with, and would recognize on a printed piece of paper
he encounters at some later time. Why not stick with the
"Target-Selector: versioned-resource" to access the meta-data, and
minimize the use of the history URL? Versioning unaware clients
are going to have to deal with a lot more confusion than this when
navigating the versioning space.
In the current (04.8) protocol, core versioning provides a
"revision-tree" report that gives you the revisions of a versioned
resource as a set of nested XML elements. The "history resource" is
introduced by advanced versioning.
This allows a very simple mechanism for core versioning (the history
report) and a more powerful/flexible mechanism for advanced versioning
(the history resource).
Cheers,
Geoff