VERSION
From: Tim Ellison/OTT/OTI (Tim_Ellison@oti.com)
Date: Thu, May 18 2000
Next message: Tim Ellison/OTT/OTI: "Date props"
To: ietf-dav-versioning@w3.org
Message-ID: <OF91B30736.B8CFDB04-ON852568E3.005753E0@ott.oti.com>
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Thu, 18 May 2000 11:54:08 -0400
Subject: VERSION
I would like to reopen the issue of bringing a resource under version
control. The intention would be to resolve the asymmetry of creating a new
resource and bringing it under version control in the cases where the
resource is bound to an unversioned collection compared to when the
resource is bound to a versioned collection.
When creating a new (data) resource in an unversioned collection the client
is required to issue a PUT followed by a VERSION. When creating a new
resource in a versioned collection the client simply says PUT.
It would seem preferable to have a consistent mechanism for this
fundamental capability. An alternative would be to allow unversioned
resources inside versioned collections (again).
Tim