RE: Properties and enforceability

We could try to enumerate every possible combination of policy into the
protocol but clients wouldn't be written to support them all so
interoperability goes out the window. Especially in the case you specify
below where you essentially need transactioning or some sort of composite
method in order to guarantee the policy is properly enforced.

If you desperately need this policy, if you must have it or you just can't
work, then DAV isn't for you.

However, there is nothing which stops your clients from performing
PUT/CHECKIN followed by a PROPPATCH. But if you are to use DAV then your
server must also be able to handle clients who don't necessarily PROPPATCH
the properties your need.

This, unfortunately, is one of the compromises that having an open
interoperable standard requires.

		Yaron

> -----Original Message-----
> From: Bruce Cragun [mailto:BCragun.ORM2-1.OREM2@GW.Novell.com]
> Sent: Monday, December 14, 1998 2:04 PM
> To: w3c-dist-auth@w3.org
> Subject: Properties and enforceability
> 
> 
> Is it possible to require certain properties be supplied when 
> creating a
> resource using WebDAV?  For instance, in a CM world, requiring that
> every new source file revision have an accompanying comment.  
> Or in the
> DMS world, that every document have an author and document 
> type?  How do
> you enforce this if it requires a PROPPATCH that is separate from the
> PUT or CHECKIN?
>

Received on Monday, 14 December 1998 14:51:42 UTC