W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2001

RE: Confusion: Removing a resource from version control

From: Lisa Dusseault <lisa@xythos.com>
Date: Wed, 13 Jun 2001 14:33:55 -0700
To: "Clemm, Geoff" <gclemm@rational.com>, <ietf-dav-versioning@w3.org>
Message-ID: <HPELJFCBPHIPBEJDHKGKEELFCGAA.lisa@xythos.com>
> A versioning aware client needs to do what the
> versioning aware user wants (not just some random behavior selected by
> a versioning server implementer).  So that means if the versioning
> aware user wants the versions to be deleted, the versioning aware
> client needs to somehow delete those versions.  Similarly, if the
> versioning aware user wants the versions to be kept, the versioning
> aware client needs to somehow save those versions.

It seems to me that this is an inconsistent position with respect to other
implementor-dependent behaviour already allowed by DeltaV.

You might also say "A versioning aware client needs to do what the
versioning aware user wants (not just some random behaviour selected by a
versioning server implementer).  So that means if the versioning aware user
wants the resource to be created as a regular resource, the versioning aware
client needs to somehow be able to create the resource as a regular
resource.  Similarly, if the versioning aware user wants the resource to be
created as a version-controlled resource, the versioning aware client needs
to somehow be able to achieve that."

Yet, the deltaV specification allows implementations to create resources
that are versioned in response to a PUT to a non-existent, or to create
resources that are not versioned.  That's "some random behavior selected by
a versioning server implementer."

I could probably come up with some more examples!

lisa
Received on Wednesday, 13 June 2001 17:35:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:41 GMT