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

Re: proposed client and server options

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Wed, 20 Dec 2000 15:03:26 -0500 (EST)
Message-Id: <200012202003.PAA05710@tantalum.atria.com>
To: ietf-dav-versioning@w3.org

   From: Greg Stein <gstein@lyra.org>

   Isn't this stuff considered "non-normative" and, therefore, not supposed to
   be included in an RFC?

I believe that you can put non-normative stuff in an appendix, but if
we keep this appendix (the current consensus is to *not* keep it),
we should confirm this.

   Putting this on the www.webdav.org/deltav/ site a definite must. But within
   the RFC seems a bit strange.

That does appear to be the consensus.  Just to provide some background
on what led to my proposing it:

- At various times, folks have asked for the definition of an "intermediate"
level (between "just core" and "all options").  Their intermediate level
was inevitably the set of options they were intending on implementing.
Having folks just declare "what they are planning on implementing"
would short circuit debate on "what should the intermediate level be".

- At other times, folks have asked for some idea about what would be
a "reasonable" set of options to support.  This appendix would also be
of use to those folks, while avoiding contention over what set of
options is "reasonable".


   On Tue, Dec 19, 2000 at 04:06:57PM -0500, Geoffrey M. Clemm wrote:
   > I propose that we add the following appendix to the protocol.
   > I believe this should help address the concern that there are
   > too many combinations of options.  In fact, if we get enough
   > entries in this section, we might be able to trim down or combine
   > some of the existing options.
   > Any objections, or suggestions for improving the wording?
   > Cheers,
   > Geoff
   > -----------------------------------------------------------
   > Although a server can implement any combination of versioning options,
   > it is expected that certain options will commonly be implemented
   > together.  In order to provide guidance to both client and server
   > implementers, this appendix enumerates the option combinations
   > currently being planned for client and server versioning
   > implementations.
   > A client will have certain options that it requires and others that it
   > supports.  The difference is that a client will simply give up on a
   > server that does not provide options that it requires, while it will
   > just not use options that it supports but which the server does not.
   > Note that this is just a statement of intent, and does NOT represent a
   > commitment by any individual or organization to provide the specified
   > versioning implementation.  An up-to-date version of this appendix can
   > be found at <http://www.webdav.org/deltav/implementations.html>.
   > 24.1 Client AA
   > - required options
   > - supported options
   > 24.2 Server BB
   > 24.3 Server CC
   > 24.4 ...

   Greg Stein, http://www.lyra.org/
Received on Wednesday, 20 December 2000 15:04:13 UTC

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