W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2001

RE: Basic Property Behavior

From: Jim Whitehead <ejw@cse.ucsc.edu>
Date: Fri, 15 Jun 2001 09:47:30 -0700
To: <ietf-dav-versioning@w3.org>
Message-ID: <AMEPKEBLDJJCCDEJHAMIAEJBDAAA.ejw@cse.ucsc.edu>
I agree with this decision as well.

At present, DeltaV *already* has too many options. It is my opinion that the
benefit to be gained by adding another option concerning versioning of
properties is swamped by the interoperability problems it would raise.

If a server needed to maintain property whose semantics required it to be
the same across all revisions, then this could be made into a live property
with that behavior. But, a client should have the expectation that arbitrary
dead properties are versioned along with the resource contents.

- Jim

> Yes, this issue was raised and debated a couple of IETF's ago,
> and the consensus was that the implementation burden on a server
> to support versioned dead properties was not sufficient to
> introduce a major source of
> interoperability problems (i.e. clients that expected to be
> able to version properties would not interoperate effectively
> with servers that did not, and vica versa).
>
> Note that the server defines the versioning behavior of any
> server defined (and therefore, live) properties, so a server is
> certainly free to make all of its server defined properties
> non-versioned.
Received on Friday, 15 June 2001 12:49:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:41 GMT