Re: Check-in policy

jamsden@us.ibm.com
Tue, 7 Dec 1999 16:20:07 -0500 

From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <85256840.00756B59.00@d54mta03.raleigh.ibm.com>
Date: Tue, 7 Dec 1999 16:20:07 -0500
Subject: Re: Check-in policy








"Geoffrey M. Clemm" <geoffrey.clemm@rational.com> on 12/07/99 03:55:22 PM

To:   ietf-dav-versioning@w3.org
cc:

Subject:  Re: Check-in policy




   From: Tim_Ellison@oti.com (Tim Ellison OTT)

   3.6.2 DAV:checkin-policy
   ...
   2) The DTD allows for ANY element as a checkin-policy.  The spec should
   state what a server should do if it does not support the checkin policy,
   and  which are mandatory.

   <gmc/>
   I'd be inclined to say that a server MUST fail an attempt to set
   a checkin-policy that cannot be provided for that working resource
   (one reason for which would be that the server does not support
   that checkin policy at all).
   If nobody disagrees, I'll make this update to the protocol.

Note: An alternative would be to say that any checkin-policy can be
set, and only require that checkin-policy be verified at CHECKIN time.
This makes life easier for servers, but is less friendly to clients.
<jra>
This would make the checkin policy on checkout useless as it turns out to
be just parameters on checkin. If this is appealing, then we can remove the
checkin policy all together, something that I would be willing to consider.
</jra>

Cheers,
Geoff