MKRESOURCE results
Tim Ellison OTT (Tim_Ellison@oti.com)
Mon, 20 Dec 1999 13:39:22 -0500
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: ietf-dav-versioning@w3.org (ietf-dav-versioning)
Message-ID: <1999Dec20.133835.1250.1423429@otismtp.ott.oti.com>
Date: Mon, 20 Dec 1999 13:39:22 -0500
Subject: MKRESOURCE results
I'd like to open the debate (if anyone is interested :-) into the effect of
MKRESOURCE for a versionable resource.
Presently, if a versionable resource is created in a versioned collection,
the created resource is necessarily versioned. Presumably if the same type
is created outside a versioned collection it is not versioned.
When the new resource is versioned what is the state of the resource? Is
there one revision and no working resources (i.e., requiring MKRESOURCE,
CHECKOUT, PUT, CHECKIN) or is there no revision and one working resource.
At the moment the protocol allows setting properties via MKRESOURCE so that
sufficies for some cases where the resource can just be created in it's
final form; however, configurations are an example where subsequent,
immediate updates will be most likely.
Would having a working resource with no revisions be a bad idea?
Tim