Warning:

Well, I'm getting basically conflicting reasons for why I should
not include Warning 12, "Caching may violate law".  Ted Hardie
says that we shouldn't do a liability-warning unless we do it
right.  Roy says we shouldn't do it because people will use it.

I don't buy Roy's argument, but I don't have time to debate it.
However, Ted's response convinces me that at this point it is
not worth worrying about the legal implications.  So I'm removing
Warning #12 for now.

After thinking about Ted's suggestion for a "Customizable Warning",
I decided to include this:

   98 Customizable warning
                   The warning text may include arbitrary information to
                   be presented to a human user, or logged.  A system
                   receiving this warning SHOULD NOT store the
                   associated response in a cache.

in *addition* to this:

   99 Miscellaneous warning
                   The warning text may include arbitrary information to
                   be presented to a human user, or logged.  A system
                   receiving this warning MUST NOT take any automated
                   action.

The difference between these two warnings is that #99 absolutely does
not affect the behavior of caches, and #98 does.  (Maybe that SHOULD
ought to be a MUST?)

-Jeff

Received on Thursday, 4 April 1996 00:24:17 UTC