Next message: jamsden@us.ibm.com: "Re: "stable" href's"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <85256872.007EC250.00@d54mta03.raleigh.ibm.com>
Date: Wed, 26 Jan 2000 18:00:48 -0500
Subject: Re: DAV:revision-resourcetype
I never thought having MKRESOURCE create a versioned resource was
necessary. The scenarios in the goals document talk about creating a
resource and getting it in some reasonable initial state before committing
it to versioning. The base case is create an initial resource with
MKRESOURCE and then version it with VERSION. Clients can merge these into a
single user operation if they want to. For servers that require every
resource to be versioned, MKRESOURCE will have the implicit behavior of
automatically (effectively) invoking VERSION. Having MKRESOURCE create
versioned resources seems like unnecessary method overload. The fact that
we are having trouble determining the resource type is an indication of the
consequences of such an overload.
"Geoffrey M. Clemm" <geoffrey.clemm@rational.com> on 01/26/2000 02:18:53 PM
To: Jim Amsden/Raleigh/IBM@IBMUS
cc:
Subject: Re: DAV:revision-resourcetype
But what if you want to create a versioned resource without having
first created a corresponding unversioned resource? Or do you propose
that we not allow that?
Cheers,
Geoff
From: jamsden@us.ibm.com
Date: Wed, 26 Jan 2000 11:25:52 -0500
Content-Length: 974
This is the reason for the VERSION method to apply to an existing
unversioned resource which has a known resource type. If this
information
is contained in the versioned resource, then 1) its redundant, and 2) it
makes it impossible for the resource to change its type from say
text/html
to text/xml. Might be the same resource.
"Geoffrey M. Clemm" <geoffrey.clemm@rational.com>@w3.org on 01/20/2000
10:36:49 PM
Sent by: ietf-dav-versioning-request@w3.org
To: ietf-dav-versioning@w3.org
cc:
Subject: DAV:revision-resourcetype
Most versioning systems require that you tell it what kind of
versioned resource you want to create, when you create one.
This means that to use MKRESOURCE, we need to be able to specify,
on creation of a versioned resource, the DAV:resourcetype of the
revisions of that versioned resource.
I propose that we introduce a DAV:revision-resourcetype property
on a versioned resource in order to do so.
Comments?
Cheers,
Geoff