W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2000

live properties (was: comments on deltav-10.5 from Yaron Goland, Act One)

From: <Tim_Ellison@uk.ibm.com>
Date: Fri, 22 Dec 2000 09:11:01 +0000
To: ietf-dav-versioning@w3.org
Message-ID: <802569BD.003275CA.00@d06mta07.portsmouth.uk.ibm.com>

      (II.5) Move all DAV:supported-xxx properties to the OPTIONS response.
       Move all DAV:xxx-collection-set properties to the OPTIONS


       Do we need DAV:supported-live-properties?
       Servers are required to protect the names of all live properties
       (whether they support them or not), so PROPPATCH will fail if the
       property is unsupported.
       Servers should not define a live property that it does not support,
       and PROPFIND would return 404 Not Found.

    Since the protocol does not distinguish between dead and
    live properties, a server has no way of knowing whether
    the PROPPATCH was to a dead property or to a live property
    that it doesn't know about.

  I recall that we used to say that servers must protect all defined
  live properties (i.e., names) in the spec, even those properties that
  were unsupported.  I didn't see that statement in a quick scan of the
  latest spec, so has it been dropped?
  If yes, then I presume it is now encumbant upon clients to (a) check
  that a live property is supported before setting it (and expecting it
  to have any effect on the server), and (b) check that a live property
  is supported before getting it to check that some other client didn't
  violate (a).
  It would seem to be less of a burden for the server to protect the
  property name (and effectively enforce (a)) than expect the client to
  do two queries (OPTIONS and PROPPATCH/FIND) for each live property

Received on Friday, 22 December 2000 04:12:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:46 UTC