Check-in policy
Tim Ellison OTT (Tim_Ellison@oti.com)
Tue, 16 Nov 1999 11:04:04 -0500
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: ietf-dav-versioning@w3.org (DAV Versioning)
Message-ID: <1999Nov16.110000.1250.1386390@otismtp.ott.oti.com>
Date: Tue, 16 Nov 1999 11:04:04 -0500
Subject: Check-in policy
3.6.2 DAV:checkin-policy
1) "if the resource is identical to"
How is identical going to be defined? That there has been no
PUT/PROPPATCH's successfully applied to the resource, or that props and
content are bytewise indistinguishable ... or server defined?
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.
<jra>
Identical defined by same GUID? Note that some live properties can change
without the resource state changing as they depend on things that happen in
other resources.
ANY is required to allow extensibility for checkout policies.
</jra>
<tim>
So who manages the GUID? Same problem.
My point about ANY was only that if I send checking policy <astrological>
what should your response be as a server (assuming that you have no idea
what I meant by that :-)
</tim>